Search Results get_dist_type_lookup_code

Overview

AP_RETRO_PRICING_UTIL_PKG is a utility package in the APPS schema that supports the Oracle Payables retroactive pricing feature set in Oracle E-Business Suite 12.1.1 and 12.2.2. Retroactive pricing allows Payables to recalculate invoice distributions when price or quantity corrections are received after an invoice has been matched, validated, or accounted. This package provides the structural and validation services that the primary retroactive pricing driver package, AP_RETRO_PRICING_PKG, depends upon. Its API classification is OTHER, meaning it is not a public, externally supported integration interface; it is an internal component invoked by Oracle's own retroactive pricing engine.

The dependency metadata confirms a tightly coupled, internal design: AP_RETRO_PRICING_UTIL_PKG references AP_RETRO_PRICING_PKG and the SYS STANDARD package, and is itself referenced both by AP_RETRO_PRICING_PKG and recursively by its own package body. All 24 documented procedures and functions are dedicated to interrogating invoice and distribution state, validating eligibility for retroactive adjustment, resolving identifiers, and constructing the temporary PPA (Payables Price Adjustment) staging records used during processing.

Key Procedures and Functions

The documented API surface divides into validation predicates, lookup helpers, and record construction routines.

• Validation predicates: ARE_ORIGINAL_INVOICES_VALID, ARE_HOLDS_OK, and IS_SEQUENCE_ASSIGNED gate whether retroactive pricing may proceed by confirming the source invoices are eligible, that no blocking holds exist, and that document sequences have been assigned.
• Existence checks: PPA_ALREADY_EXISTS, IPV_DISTS_EXISTS, ERV_DISTS_EXISTS, ADJ_CORR_EXISTS, CORRECTIONS_EXISTS, TIPV_EXISTS, and TERV_DISTS_EXISTS detect whether price variance, exchange rate variance, adjustment, correction, or tax-related distributions already exist, preventing duplicate processing.
• Identifier and attribute resolvers: GET_INVOICE_DISTRIBUTION_ID, GET_CCID, GET_DIST_TYPE_LOOKUP_CODE, GET_MAX_PPA_LINE_NUM, GET_EXCHANGE_RATE, GET_INVOICE_AMOUNT, and GET_CORRESPONDING_RETRO_DISTID retrieve keys, code combinations, lookup codes, sequence values, currency rates, amounts, and matched distribution references.
• Record construction routines: CREATE_LINE, GET_BASE_MATCH_LINES, and CREATE_PPA_INVOICE assemble the adjustment line rows, resolve the originating match lines, and build the price adjustment invoice structures staged for downstream processing.

Because parameter signatures are not exposed in the documentation, consumers must not assume a callable contract; these routines are intended for internal invocation only.

Tables Accessed

The package operates across the core Payables invoice and distribution tables through APPS synonyms. AP_INVOICES_ALL, AP_INVOICES_S, and AP_INVOICES_INTERFACE supply invoice headers, while AP_INVOICE_DISTRIBUTIONS_ALL and AP_INVOICE_DISTRIBUTIONS_S provide distribution lines for validation and reconstruction. AP_INVOICE_LINES, AP_INVOICE_LINES_ALL, AP_INVOICE_LINES_INTERFACE, and AP_INVOICE_LINES_INTERFACE_S support line-level matching detail. AP_HOLDS_ALL is queried to determine hold status. AP_SYSTEM_PARAMETERS_ALL and AP_ALLOCATION_RULE_LINES provide system configuration and allocation rules. The global temporary tables AP_PPA_INVOICES_GT, AP_PPA_INVOICE_DISTS_GT, and AP_PPA_INVOICE_LINES_GT serve as the staging area for the price adjustment records generated during processing.

Usage Notes

This package is invoked indirectly. It is not called from Oracle Payables forms or standard concurrent programs by user action; rather, it is exercised by AP_RETRO_PRICING_PKG and, per the metadata, referenced by only one other package. Retroactive pricing processing is typically triggered through the Payables price adjustment and retroactive pricing workflows after a correction is approved. Customizations should avoid direct calls, as the package is unsupported for external use and is subject to change. Developers diagnosing retroactive pricing issues should review these routines for hold, variance, and existence conditions before extending behavior. In both 12.1.1 and 12.2.2 the object resides in APPS and is documented as VALID.