Results for “qp_default_price_list”

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

Overview

QP_DEFAULT_PRICE_LIST is an Oracle Advanced Pricing (QP) PL/SQL package owned by the APPS schema and declared with AUTHID CURRENT_USER. It belongs to the pricing engine layer of Oracle E-Business Suite and is classified in the ETRM metadata as an "OTHER" API rather than a public business API. Its purpose is to derive a default price list record for a given price list context, supplying the pricing engine with the currency, language, and list header information required when a caller does not supply an explicit price list definition. In practical terms, the package encapsulates the resolution logic that determines which currency list, currency details, and list header defaults apply to a pricing transaction. Because the specification is small (a single documented procedure) and the header dates to 2005 (QPXDPLHS.pls, version 120.1), the package is a legacy but still referenced component that supports the Advanced Pricing module across both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The ETRM metadata documents exactly one callable unit in this package:

• Attributes — The sole documented procedure. It accepts a price list record as input (defaulted to the public "missing" price list record constant from QP_Price_List_PUB) together with an iteration number, and returns a corresponding price list record through an OUT NOCOPY parameter. The procedure is used to populate or resolve default attribute values for a price list record, allowing callers to obtain a fully formed price list structure when only partial context is available. Its dependence on QP_Price_List_PUB.Price_List_Rec_Type indicates it operates directly on the public price list record type used throughout the Advanced Pricing APIs.

No other procedures or functions are documented in the package specification, so the entire public surface area of QP_DEFAULT_PRICE_LIST is this single Attributes routine.

Tables Accessed

The package reads from the following tables through APPS synonyms, as recorded in the ETRM metadata:

• FND_LANGUAGES — supplies the installed language definitions used when resolving language-dependent list attributes.
• FND_CURRENCIES — provides currency code and validity information for the price list currency.
• QP_CURRENCY_DETAILS and QP_CURRENCY_DETAILS_S — hold currency-specific pricing parameters and their translation/security shadow tables, used to resolve currency-level list defaults.
• QP_CURRENCY_LISTS_B, QP_CURRENCY_LISTS_B_S, and QP_CURRENCY_LISTS_TL — the base, shadow, and translation tables for currency lists, which link a price list to its permitted currencies.
• QP_LIST_HEADERS_B_S — the shadow table for price list headers, providing the header defaults (name, currency, rounding, and related attributes) applied to the returned record.
• DUAL — used for single-row selection and constant evaluation.

These accesses confirm that the procedure's role is to read reference and setup data in order to construct a default price list record, rather than to perform transactional writes to pricing data.

QP_DEFAULT_PRICE_LIST is an internal helper rather than an end-user-facing API. It is not typically invoked directly from Oracle Forms or concurrent programs; instead it is called by other pricing packages during price list resolution. The ETRM metadata records that the package is referenced by one other package, confirming its role as a dependency within the Advanced Pricing code base. In custom development, it may be called when a programmatic price list creation or lookup requires EBS-standard defaults, but because it depends on QP_Price_List_PUB record types and returns a NOCOPY OUT parameter, callers must work within the same PL/SQL record structures used by the public pricing APIs. Given the AUTHID CURRENT_USER declaration, execution is subject to the privileges of the calling schema, so the APPS synonyms listed above must be accessible. Developers targeting 12.1.1 or 12.2.2 should treat this package as a stable legacy object and prefer documented public APIs such as QP_Price_List_PUB for new integrations, invoking QP_DEFAULT_PRICE_LIST only where the existing pricing logic already depends on it.