Search Results jtf_perz_query_param_s

Overview

JTF_PERZ_QUERY_PVT is a private PL/SQL package body in the APPS schema that implements the persistence and retrieval logic for the Oracle E-Business Suite Personalization (PERZ) query framework. Commonly associated with the jtf_perz_query_param_s and related tables, the package supports the definition, storage, and reuse of user-defined and seeded queries that drive personalization regions, folders, and dashboards. Rather than exposing an interface directly to callers, the body realizes the contract declared by JTF_PERZ_QUERY_PVT and is invoked indirectly through the public wrapper JTF_PERZ_QUERY_PUB. The package depends on FND_API, FND_GLOBAL, and FND_MSG_PUB for application programming interface conventions, session context, and message handling, and on JTF_PERZ_PROFILE_PUB/PVT for profile resolution. Its classification as a PVT package confirms it is an internal implementation layer, not a supported public API.

Key Procedures and Functions

• CREATE_PERZ_QUERY — Persists a newly defined personalization query, including its identifying attributes and associated metadata, into the underlying query tables.
• GET_PERZ_QUERY — Retrieves a single query definition by its identifying key so that calling components can reconstruct and execute the stored query.
• GET_PERZ_QUERY_SUMMARY — Returns an abbreviated or summarized representation of a query, typically for list-of-values and selection screens where full detail is unnecessary.
• UPDATE_PERZ_QUERY — Applies modifications to an existing query definition, preserving referential integrity across the query, order-by, parameter, and raw-SQL child records.
• DELETE_PERZ_QUERY — Removes a query definition and its dependent child rows from the personalization query tables.
• SAVE_PERZ_QUERY — Persists a complete query structure, coordinating the header plus its parameters, ordering, and raw SQL components in a single logical operation.

The procedures follow EBS API conventions, relying on FND_API for standardized return status and FND_MSG_PUB for error messaging. No parameter signatures are documented in the ETRM metadata and none are asserted here.

Tables Accessed

The package operates across the core personalization query model. JTF_PERZ_QUERY and its synonym JTF_PERZ_QUERY_S hold the query header. JTF_PERZ_QUERY_PARAM and JTF_PERZ_QUERY_PARAM_S store parameter bindings, while JTF_PERZ_QUERY_ORDER_BY and JTF_PERZ_QUERY_ORDER_BY_S hold sort specifications. JTF_PERZ_QUERY_RAW_SQL and JTF_PERZ_QUERY_RAW_SQL_S retain the underlying SQL text. PLITBLM, the standard PL/SQL integer table type, is used for array-style processing of multi-row collections. Access is read/write for the query and child tables, supporting full CRUD lifecycle management.

Usage Notes

JTF_PERZ_QUERY_PVT is not intended for direct invocation by customers or integrators. It is called by JTF_PERZ_QUERY_PUB, and the ETRM metadata records that it is referenced by two other database objects. Typical invocation paths include Personalization framework forms and concurrent processing where users create, edit, or reuse saved queries. Custom code should call the public PUB layer rather than this private body, since PVT packages may change between releases without notice. In 12.1.1 and 12.2.2, the package remains VALID and unchanged in classification, underscoring its role as stable internal infrastructure for the personalization query subsystem.