Search Results validate_qp_flexfield

Overview

QP_UTIL_W is a public PL/SQL package owned by APPS in the Oracle E-Business Suite, declared with AUTHID CURRENT_USER and typically associated with the Oracle Advanced Pricing (QP) module. Its name and the _W suffix indicate that it functions as a wrapper package, sitting above the core QP_UTIL package to expose selected internal routines to external callers, Java/BC4J layers, and the Rosetta integration stack. In Oracle EBS 12.1.1 and 12.2.2, the package provides a stable API surface for validating descriptive flexfield definitions used in pricing contexts and for retrieving flexfield segment metadata used by pricing setup and runtime processing.

The package is classified in ETRM documentation as OTHER and is not designated a formal public API, but it is exposed as an APPS synonym and is referenced through the standard QP utility layer. It contains twelve documented procedures, most of which support the Rosetta table-copy pattern used to marshal PL/SQL collections across JTF typed tables.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P1 / ROSETTA_TABLE_COPY_OUT_P1 — Convert data in and out of the qp_util.v_segs_upg_tab collection type, mapping the four JTF typed-table columns into and out of that record structure.
• ROSETTA_TABLE_COPY_IN_P41 / ROSETTA_TABLE_COPY_OUT_P41 — Marshalling routines for qp_util.create_context_out_tbl, used when returning context information from pricing LOV processing.
• ROSETTA_TABLE_COPY_IN_P43 / ROSETTA_TABLE_COPY_OUT_P43 — Marshalling routines for qp_util.create_attribute_out_tbl, handling attribute-level output.
• VALIDATE_QP_FLEXFIELD — The primary entry point of interest when searching for validate_qp_flexfield. It validates a supplied flexfield value against a named flexfield, context, and attribute, using an application short name to resolve the owning application. It returns flags for context, attribute, and value validity, together with datatype, precedence, and an error code. A check_enabled input controls whether enablement checks are applied.
• GET_SEGS_FOR_FLEX — Returns the segment definitions (name, value, and related columns) for a given flexfield and application short name, with an error code output.
• GET_SEGS_FLEX_PRECEDENCE — Returns segment precedence information, ordering segments according to the pricing flexfield precedence rules.
• CORRECT_ACTIVE_DATES — Adjusts active date ranges, typically used to normalize start/end dates in pricing flexfield setup data.
• WEB_CREATE_CONTEXT_LOV — Supplies the list of values for pricing flexfield contexts in a web/HTML interface.
• WEB_CREATE_ATTRIBUTE_LOV — Supplies the list of values for pricing flexfield attributes in a web/HTML interface.

Tables Accessed

The ETRM metadata documents a single referenced table, PLITBLM, accessed via an APPS synonym. PLITBLM is the standard Oracle EBS PL/SQL table (index-by table) used by forms and web-based LOV processing to stage list-of-values query results. Its presence here is consistent with the WEB_CREATE_CONTEXT_LOV and WEB_CREATE_ATTRIBUTE_LOV procedures, which populate LOV data for the pricing descriptive flexfield user interface. Other flexfield metadata is resolved internally through the standard FND flexfield views and the QP_UTIL package, rather than through tables directly listed in the ETRM metadata.

Usage Notes

QP_UTIL_W is normally invoked indirectly. The validation routines are called by pricing forms, by the online pricing setup UI, and by custom code that needs to confirm a flexfield value before persisting it into a pricing entity such as a price list line, modifier, or qualifier. The validate_qp_flexfield procedure is the practical entry point when a developer needs to check whether a given context, attribute, and value combination is valid for a named pricing flexfield.

The Rosetta copy procedures are intended for use by generated integration code and should not normally be called by hand. The package is not referenced by any other documented package, so it is a leaf dependency in the pricing stack. Because it is declared with AUTHID CURRENT_USER, callers must hold the necessary privileges on the underlying flexfield views and PLITBLM; responsibility for privilege resolution therefore rests with the invoking schema rather than with APPS. This makes the package suitable for direct invocation from custom schemas that have been granted access to the QP flexfield metadata.