Search Results qp_default_pricing_attr




Overview
Explore in AI Chat

Overview

QP_DEFAULT_PRICING_ATTR is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Advanced Pricing (QP) module and is classified in the E-Business Suite Technical Reference Manual (ETRM) under the API classification "OTHER." The package provides defaulting logic for pricing attribute records used within the Oracle Pricing engine. In Advanced Pricing, a pricing attribute identifies the qualifier context against which modifiers, price lists, and qualifiers are evaluated — for example, item, customer, order type, or currency. When a pricing transaction is processed and one or more attribute values are not explicitly supplied, the pricing engine requires a mechanism to populate or default those attributes consistently. QP_DEFAULT_PRICING_ATTR encapsulates that defaulting behavior, allowing callers to obtain a fully or partially defaulted pricing attribute record rather than assembling it manually. The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the invoking schema rather than the definer, a common convention for Oracle EBS public APIs.

Key Procedures and Functions

The ETRM metadata documents a single public program unit within this package:

  • Attributes — A procedure that returns a defaulted pricing attribute record. Based on the documented signature, it accepts an input pricing attribute record (using the QP_Modifiers_PUB.Pricing_Attr_Rec_Type record type) together with an iteration number, and returns an output pricing attribute record of the same type. The input record typically carries caller-supplied attribute values, and the procedure fills in missing or standard values. The iteration parameter supports repeated invocation, allowing the defaulting logic to be applied progressively across successive passes. The default value for the input record is QP_Modifiers_PUB.G_MISS_PRICING_ATTR_REC, which represents an empty or unpopulated record, indicating that the procedure can be called without an initial record to obtain baseline defaults.

No additional procedures or functions are documented in the ETRM extract beyond this single entry point.

Tables Accessed

The package references the following tables through APPS synonyms:

  • QP_PRICING_ATTRIBUTES_S — The base sequence-bearing table that stores pricing attribute definitions. This is the primary source from which valid pricing attribute values and their properties are read during defaulting.
  • QP_PRICING_ATTR_GROUP_NO_S — Stores attribute group numbering information used to organize and sequence pricing attributes. It supports the defaulting logic by supplying group ordering context.
  • DUAL — The standard Oracle single-row utility table, typically used for simple lookups, validations, or constant expressions within the package body.

The use of these tables indicates that the procedure reads pricing attribute configuration and group numbering data to determine appropriate default values, rather than performing extensive transactional writes.

Usage Notes

QP_DEFAULT_PRICING_ATTR is an internal utility package rather than a full public pricing API. It is referenced by one other package in the ETRM dependency metadata, indicating that it is primarily invoked from within the Oracle Pricing code base — most likely from QP_Modifiers_PUB or related modifier processing packages — rather than being called directly by end users.

Typical invocation scenarios include:

  • Pricing engine processing during order entry, where modifier qualification requires a complete pricing attribute record.
  • Custom extensions or integrations that need to replicate standard Advanced Pricing defaulting behavior when constructing pricing attribute records for calls to QP_Modifiers_PUB.
  • Concurrent or batch pricing programs that evaluate large volumes of pricing transactions and require consistent attribute defaulting.

Because the package is documented as AUTHID CURRENT_USER and classified as OTHER, developers who invoke it directly should ensure the calling schema has appropriate execute privileges and access to the underlying synonyms. The presence of the p_iteration parameter suggests that callers may need to iterate defaulting where attribute values are resolved in stages; each pass would refine the record until no further defaults apply. Given the limited number of documented procedures and the internal classification, this package should be treated as a supporting component of the Advanced Pricing engine rather than a standalone integration API.