Search Results rosetta_table_copy_in_p39

Overview

The APPS.QP_UTIL_OA package is a utility package within the Oracle E-Business Suite Advanced Pricing (QP) module, specifically designed to support the Oracle Application Framework (OA) / HTML-based user interface layer. Its primary business function is to bridge the gap between the PL/SQL business logic housed in the QP_UTIL package and the presentation-layer LOV (List of Values) and table-copy requirements of the OA Framework pages used for pricing setup, such as the attribute and context management screens within the Pricing Manager. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the package owner, which is typical for utility and wrapper packages in the APPS schema.

The naming convention and the presence of numerous ROSETTA_TABLE_COPY procedures indicate that this package serves as an adaptor layer. In the OA Framework, PL/SQL collections must be marshalled between Java table structures and PL/SQL types, and the Rosetta-family procedures perform precisely this conversion. The WEB_CREATE_*_LOV procedures provide the data sources for dynamic List of Values components, notably WEB_CREATE_ATTRIBUTE_LOV, which the user searched for. This procedure is the LOV data source that populates the attribute selection list during pricing attribute creation or qualification setup.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P1 / OUT_P1 — Convert the v_segs_upg_tab collection type to and from the JTF table types. These handle segment-upgrade related data used during pricing setup migration and flexfield segment processing.
• ROSETTA_TABLE_COPY_IN_P39 / OUT_P39 — Convert the create_context_out_tbl collection. These support the context creation LOV, transferring context name (VARCHAR2_100) and description (VARCHAR2_300) data between the Java and PL/SQL layers.
• ROSETTA_TABLE_COPY_IN_P41 / OUT_P41 — Convert the create_attribute_out_tbl collection, which carries attribute name, description, context, and numeric identifiers. This is the data-backing structure for the attribute LOV.
• VALIDATE_QP_FLEXFIELD — Validates a pricing flexfield context/attribute/value combination against the specified flexfield, returning flags for context, attribute, value, datatype, precedence, and an error code. It is the core server-side validation routine for pricing flexfield input.
• GET_SEGS_FOR_FLEX — Retrieves the segment collections associated with a given flexfield and application, returning segment identifiers and related values.
• GET_SEGS_FLEX_PRECEDENCE — Returns segment precedence information for a flexfield, used to order or resolve pricing attribute segments.
• WEB_CREATE_CONTEXT_LOV — Provides the LOV data source for pricing context selection within the web UI.
• WEB_CREATE_ATTRIBUTE_LOV — Provides the LOV data source for pricing attribute selection. This is the procedure referenced by the user's search term and is the catalog source invoked when a user opens the attribute LOV on a pricing setup page.

Tables Accessed

The only documented table reference is PLITBLM, accessed via an APPS synonym. PLITBLM is the standard EBS table used for the temporary storage of PL/SQL index-by or nested-table collections—particularly relevant for the JTF table types passed in and out of the Rosetta procedures and the LOV population routines. The package does not directly document reads or writes to core pricing tables such as QP_ATTRIBUTES or QP_CONTEXTS; instead it relies on the underlying QP_UTIL routines to perform that work, using PLITBLM as the transport mechanism for collection data.

Usage Notes

QP_UTIL_OA is an internal support package and is not intended for direct invocation by end users or typical customizations. It is invoked by the OA Framework-based Pricing pages through the standard JTF/BC4J integration that passes JTF table types between the middle tier and the database. Because it is catalogued with an API classification of OTHER rather than PUBLIC, Oracle does not support it as a formal public API, and its signatures may change without notice across patches.

The package is referenced by zero other packages per the ETRM metadata, confirming its role as a leaf-level wrapper invoked directly from the web tier rather than from other PL/SQL units. In Oracle EBS 12.1.1 and 12.2.2, the header note ($Header: ozfaqpus.pls 115.0 ...) and the file-name convention ozfaqpus.pls indicate this code originated in the legacy Oracle Pricing codebase and has remained largely stable across releases. Developers extending pricing LOVs or customizing attribute validation should call the corresponding QP_UTIL routines or public pricing APIs rather than QP_UTIL_OA, which exists solely to service the delivered web user interface.