Search Results pricing_context




Overview
Explore in AI Chat

Overview

OE_PRICE_ADJ_ATTRIBS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, categorized under the ONT – Order Management product family. Its documented purpose is straightforward: it presents the contents of the base table OE_PRICE_ADJ_ATTRIBS in a read-only, query-friendly form. In ETRM 12.2.2 the view is listed with status VALID and is defined as a synonym-referenced layer over OE_PRICE_ADJ_ATTRIBS.

Functionally, the view exposes the attribute-level qualifiers attached to price adjustments. Where OE_PRICE_ADJUSTMENTS stores the header of a modifier or adjustment (for example, a discount or surcharge applied to a pricing context), the attribute rows captured here define the conditions under which that adjustment fires — the specific pricing attribute, its comparison operator, and the from/to value range. The view therefore serves as the bridge between pricing setup data and the business rules evaluated during order pricing in Oracle Advanced Pricing, surfaced through Order Management reporting and interfaces. For users searching on the term "pricing_attribute," this view is the canonical place to inspect the PRICING_ATTRIBUTE and PRICING_CONTEXT columns that determine qualifier behavior.

Underlying Base Objects

The view is defined exclusively over a single documented base object: the synonym OE_PRICE_ADJ_ATTRIBS, which resolves to the APPS.OE_PRICE_ADJ_ATTRIBS table. The view text performs a direct SELECT of all listed columns with no joins, aggregations, filters, or transformations. Because there is no WHERE clause or decoding logic, the row count and content of the view mirror the base table exactly at query time.

This one-to-one relationship means the view is purely a naming and access abstraction rather than a business-logic consolidation. It inherits the base table's indexes, constraints, and DML characteristics; no materialization or caching is applied. Reports and concurrent programs reference the view to avoid hard-coding the base table name, and any insert, update, or delete performed through the view flows directly to OE_PRICE_ADJ_ATTRIBS subject to the standard who-columns and program context columns present in the projection.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which attributes qualify a given price adjustment, tracing why a modifier did or did not apply to an order line, and feeding pricing setup data into integration or data-warehouse extracts. A representative query joining the view to its parent adjustment table is:

  • SELECT a.price_adj_attrib_id, a.price_adjustment_id, a.pricing_context, a.pricing_attribute, a.comparison_operator, a.pricing_attr_value_from, a.pricing_attr_value_to FROM oe_price_adj_attribs_v a WHERE a.price_adjustment_id = :adjustment_id; — retrieves all qualifiers for one adjustment.
  • SELECT * FROM oe_price_adj_attribs_v WHERE pricing_attribute = 'CUSTOMER_CLASS'; — isolates qualifiers for a specific pricing attribute.
  • SELECT price_adjustment_id, COUNT(*) FROM oe_price_adj_attribs_v GROUP BY price_adjustment_id; — profiles qualifier density across adjustments.

Because the view is a direct projection of OE_PRICE_ADJ_ATTRIBS, it is safe for both interactive diagnostics and batch extraction in 12.1.1 and 12.2.2, provided access is granted to the APPS-owned object or through a custom GRANT to the querying schema.