Search Results modifier_header_id

Overview

OKX_QTE_PRC_ADJMNTS_V is a reporting and integration view owned by the APPS schema within the OKX – Contracts Integration product. It exposes Oracle Advanced Pricing adjustment data that is consumed by Oracle Quoting and related contract integration flows. The view is defined as a simple projection over a synonym that resolves to ASO_PRICE_ADJUSTMENTS, and, as such, it presents the full set of price adjustment attributes in a read-oriented access path suitable for EBS 12.1.1 and 12.2.2 environments.

The object status is VALID, confirming that the view compiles cleanly in the reference environment. Because the view performs no joins, aggregation, or filtering, it is primarily a convenience and access-layer object rather than a transformation object. Its principal value is in exposing pricing adjustment records—including modifiers, discounts, rebates, and charge adjustments—with the parent-child relationship carried by PARENT_ADJUSTMENT_ID, which is the attribute most commonly searched when users need to trace adjustment hierarchies.

Underlying Base Objects

The documented base object is ASO_PRICE_ADJUSTMENTS, referenced through a synonym. In a standard EBS installation, ASO_PRICE_ADJUSTMENTS is the principal Advanced Pricing table storing price adjustment definitions generated through pricing modifiers. It is created and maintained by the pricing engine and supports both header-level and line-level adjustments.

Because the view is a direct column mapping with no WHERE clause or join, it inherits the row population of ASO_PRICE_ADJUSTMENTS exactly. Insert, update, or delete operations are not possible directly through the view. Any modification must be performed against the base table, typically via supported pricing APIs (for example, QP_Price_List_PUB or modifier maintenance APIs) rather than direct DML. Referential integrity, concurrency control, and WHO/TCA audit columns are governed entirely by the base table.

Key Columns

• PARENT_ADJUSTMENT_ID – Identifier of the parent adjustment, establishing the hierarchical relationship between an adjustment and its parent. This is the primary key used to track adjustment nesting.
• PRICE_ADJUSTMENT_ID – Unique identifier for the adjustment record itself; the de facto primary key of the view.
• MODIFIER_HEADER_ID / MODIFIER_LINE_ID – Pointers to the pricing modifier header and line that generated the adjustment.
• MODIFIER_MECHANISM_TYPE_CODE / MODIFIER_LINE_TYPE_CODE – Indicate the type of modifier and its mechanism (for example, discount, surcharge, or promotional).
• LIST_HEADER_ID / LIST_LINE_ID – Link the adjustment to a price list header and line when applicable.
• OPERAND, ARITHMETIC_OPERATOR, ADJUSTED_AMOUNT – Define the value and arithmetic behavior of the adjustment.
• AUTOMATIC_FLAG, APPLIED_FLAG, UPDATED_FLAG, UPDATE_ALLOWABLE_FLAG, ON_INVOICE_FLAG, INVOICED_FLAG – Status flags governing behavior and lifecycle state.
• PRICING_PHASE_ID, PRICING_GROUP_SEQUENCE – Control where in the pricing phase sequence the adjustment applies.
• QUOTE_HEADER_ID / QUOTE_LINE_ID – Link the adjustment to the quoting context, which is central to the OKX Contracts Integration product.
• CHARGE_TYPE_CODE, CHARGE_SUBTYPE_CODE – Classify charges where the adjustment represents a charge rather than a discount.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the pricing engine.
• ATTRIBUTE1 through ATTRIBUTE15 – Flexfield-style descriptive attributes available for extension.

Common Use Cases and Queries

The view is typically queried to reconcile adjustments with their parents, to audit modifier behavior within quoting flows, and to integrate adjustment data into downstream reporting. A representative query following the searched term is shown below:

• SELECT price_adjustment_id, parent_adjustment_id, modifier_header_id, modifier_line_id, adjusted_amount FROM apps.okx_qte_prc_adjmnts_v WHERE parent_adjustment_id = :parent_id;
• SELECT price_adjustment_id, parent_adjustment_id, automatic_flag, applied_flag FROM apps.okx_qte_prc_adjmnts_v WHERE modifier_header_id = :modifier_header_id ORDER BY parent_adjustment_id;
• SELECT a.price_adjustment_id, a.parent_adjustment_id, a.adjusted_amount FROM apps.okx_qte_prc_adjmnts_v a WHERE a.quote_header_id = :quote_header_id;
• SELECT child.price_adjustment_id, parent.price_adjustment_id AS parent_id FROM apps.okx_qte_prc_adjmnts_v child, apps.okx_qte_prc_adjmnts_v parent WHERE child.parent_adjustment_id = parent.price_adjustment_id;

These queries illustrate adjustment hierarchy walks, modifier-level audits, and quote-oriented extraction. For high-volume reporting, joining to the base table for indexed access may be preferable, since the view provides no additional indexing or performance optimization.