Results for “qp_value_to_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QP_VALUE_TO_ID is an Oracle Advanced Pricing (QP) PL/SQL package body owned by the APPS schema. It is classified under the ETRM metadata as an "OTHER" API type, meaning it is an internal utility rather than a formally published public API. The package resolves qualifier values—such as customer, item, currency, ship method, or pricing context attributes—into the internal identifiers used by the pricing engine. Its role is to translate human-readable or flexible-value-set values into the IDs that Oracle Advanced Pricing stores on qualifier rules, price list lines, and modifiers. This translation is essential for qualifier matching, where the pricing engine must compare incoming transaction attribute values against the stored qualifier definitions during price and modifier evaluation.

Key Procedures and Functions

The documented package exposes roughly ninety procedures and functions, each responsible for resolving a specific qualifier context or pricing attribute to its internal identifier. Representative entries include:

• GET_ATTR_TBL — returns the attribute mapping table used to drive generic value-to-ID resolution across qualifier contexts.
• KEY_FLEX — resolves key flexfield segment values, typically inventory item or accounting flexfield combinations, into their internal IDs.
• AUTOMATIC and GENERATE_USING_FORMULA — support automatic and formula-driven qualifier or modifier value determination.
• CURRENCY, BASE_UOM, and LIST_PRICE_UOM — resolve currency codes and unit of measure values to their internal identifiers.
• SHIP_METHOD and FREIGHT_TERMS — resolve shipping method and freight term lookup values.
• DISCOUNT_LINES, PRORATE, TERMS, and AGREEMENT_SOURCE — support modifier line, proration, terms, and agreement source qualifier resolution.
• LIST_HEADER, LIST_LINE, LIST_LINE_TYPE, and LIST_TYPE — resolve price list header, line, line type, and list type values.
• MODIFIER_LEVEL, INVENTORY_ITEM, and ORGANIZATION — resolve modifier level, inventory item, and organization qualifiers.

Collectively these routines provide uniform conversion logic so that pricing qualifiers are consistently interpreted regardless of the source attribute.

Tables Accessed

The package body references two documented tables through APPS synonyms: QP_QUALIFIER_RULES and PLITBLM. QP_QUALIFIER_RULES stores the qualifier rule definitions that drive qualifier matching, and it is the primary structure against which resolved IDs are compared. PLITBLM is the PL/SQL index-by table type (PL/SQL table of binary integers with a mapping) used pervasively in EBS as an in-memory structure for passing ID mappings and multi-value sets between procedural layers; it is referenced here to carry resolved identifier collections and value lists during resolution. The dependency listing additionally shows references to QP_PRICE_LIST_LINE_UTIL, QP_UTIL, FND_API, FND_FLEX_EXT, FND_MESSAGE, FND_VSET, OE_MSG_PUB, OE_SHIP_METHODS_V, and QP_LOOKUPS, indicating reliance on flexfield extraction, flexfield value set validation, and shipping method views during resolution.

Usage Notes

QP_VALUE_TO_ID is not referenced by any database object according to the metadata, confirming that it is invoked internally by the Advanced Pricing engine rather than being a top-level integration point. It is referenced by 36 other packages, which underscores its foundational role: pricing forms, concurrent programs, and internal pricing routines call these procedures to convert qualifier values before evaluating price lists, modifiers, and qualifier rules. Custom code should treat this package as internal and unsupported; developers requiring qualifier resolution should prefer the documented public Advanced Pricing APIs. Because the package depends on FND_FLEX_EXT and FND_VSET, resolution honors flexfield value set validation, and any change to flexfield definitions or qualifier setup can affect its behavior. The STANDARD, FND_API, and QP_UTIL dependencies indicate that error handling follows the standard EBS API message stack.