Search Results validate_context_code




Overview

QP_UTIL is a utility package in the Oracle E-Business Suite Advanced Pricing module (QP). It provides shared helper routines that other pricing APIs, forms, and concurrent programs depend on for resolving descriptive flexfield context metadata, validating pricing attributes and qualifiers, determining the operational status of the pricing engine, and translating internal entity identifiers into their user-facing names. Its source header (QPXUTILS.pls 120.9) indicates it has been a long-standing component, and the documented metadata lists 52 procedures and functions plus references from 111 other packages, confirming its role as a foundational library rather than an end-user API. The package is classified as UTIL under the APPS schema in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The GET_ENTITYNAME function, the object most commonly located by name, accepts an entity identifier and returns its descriptive name, allowing callers to convert stored foreign keys into human-readable labels. GET_ENTITYVALUE performs the complementary lookup by returning a numeric identifier for a given attribute code.

Tables Accessed

QP_UTIL reads metadata from FND_DESCR_FLEX_CONTEXTS, FND_DESCR_FLEX_COLUMN_USAGES, and FND_FLEX_VALUE_SETS to resolve flexfield structure, context types, and value sets. QP_LIST_HEADERS_B, QP_LIST_LINES, QP_PRC_CONTEXTS_B, QP_PRC_CONTEXTS_TL, QP_CURRENCY_DETAILS, QP_LIMITS, and QP_LIMIT_ATTRIBUTES supply pricing list, context, currency, and limit definitions. AK_OBJECT_ATTRIBUTES_TL and OE_AK_OBJ_ATTR_EXT provide attribute manager and order-entry attribute metadata used for entity and attribute resolution. FND_APPLICATION and FND_USER support application and user lookups, while MTL_SYSTEM_ITEMS_B underpins item category validation. All access occurs through APPS synonyms.

Usage Notes

QP_UTIL is invoked primarily by other PL/SQL packages, pricing forms, and concurrent programs rather than by end users directly. Typical custom-code scenarios include resolving an entity name during report generation, checking pricing module status before invoking pricing APIs, validating flexfield context values prior to insert, and determining whether a code represents a qualifier or a pricing attribute. Because the package is referenced by 111 other packages and is documented as an internal utility, direct modification is not supported; callers should treat its signatures as stable interfaces and rely on the documented procedures for metadata resolution.