Search Results oe_price_adj_attribs_pk

Overview

The OE_PRICE_ADJ_ATTRIBS table is a core data object within the Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically for releases 12.1.1 and 12.2.2. It serves as a detailed supporting table for the pricing engine, capturing the specific qualifiers and pricing attributes that were evaluated and satisfied to apply a particular price adjustment to an order line. When the system calculates discounts, promotions, or other price modifications, this table stores the granular "why" behind each adjustment, linking the final adjusted price back to the precise business rules and product or customer attributes that triggered it. Its role is critical for auditability, pricing transparency, and troubleshooting complex pricing setups.

Key Information Stored

The table's primary function is to store attribute and qualifier data for price adjustments. While the full column list is not detailed in the provided metadata, its structure is defined by its relationships. The key documented column is PRICE_ADJ_ATTRIB_ID, which serves as the unique primary key for each record. The most critical foreign key column is PRICE_ADJUSTMENT_ID, which links each attribute record to its parent price adjustment in the OE_PRICE_ADJUSTMENTS table. The table's description indicates it holds columns for qualifier and pricing attribute information, which would typically include fields like ATTRIBUTE_CODE, ATTRIBUTE_VALUE, CONTEXT, and potentially columns identifying the specific pricing qualifier group or pricing attribute that was matched during the pricing engine's execution.

Common Use Cases and Queries

This table is primarily accessed for in-depth pricing analysis and audit reports. A common use case is generating a report to explain all discounts applied to a specific sales order, detailing not just the adjustment amount but the exact product category, customer class, or promotional code that qualified the line for the discount. Another critical scenario is troubleshooting when an expected price adjustment is not applied; analysts can query this table to see which attributes were evaluated for a given adjustment line. A sample query pattern would join this table to the price adjustments and order lines to retrieve the adjustment rationale.

SELECT ola.line_number,
       opa.adjustment_type_code,
       opa.adjusted_amount,
       opaa.attribute_code,
       opaa.attribute_value
FROM oe_price_adj_attribs opaa,
     oe_price_adjustments opa,
     oe_order_lines_all ola
WHERE opaa.price_adjustment_id = opa.price_adjustment_id
  AND opa.line_id = ola.line_id
  AND ola.header_id = <P_HEADER_ID>;

Related Objects

The OE_PRICE_ADJ_ATTRIBS table has a direct and essential relationship with the core price adjustments table. As documented in the provided metadata:

• Primary Key: OE_PRICE_ADJ_ATTRIBS_PK on column PRICE_ADJ_ATTRIB_ID.
• Foreign Key (References): The table OE_PRICE_ADJ_ATTRIBS contains a foreign key constraint where its column PRICE_ADJUSTMENT_ID references the OE_PRICE_ADJUSTMENTS table. This enforces that every attribute record must be associated with a valid parent price adjustment line.

Given its function, this table is also conceptually related to the pricing engine's setup tables, such as those defining qualifiers (OE_QUALIFIERS) and pricing attributes, though these are not documented as direct foreign key constraints in the provided excerpt.