Search Results range_break_quantity

Overview

The view APPS.OKX_ORD_PRC_ADJMNTS_V is a Contracts Integration (OKX) object in Oracle E-Business Suite. It is a reporting and integration view that exposes the columns of the order price adjustment entity, providing a read interface into Oracle Order Management price adjustment data for downstream contracts and pricing integration processes. Its status is VALID in the EBS 12.1.1 and 12.2.2 data dictionary, and it is owned by the APPS schema.

Functionally, the view surfaces the full set of attributes applicable to price adjustments — including list price references, pricing phases, modifiers, charge types, rebate and accrual indicators, and change tracking columns. Because the underlying table is the foundation of the pricing engine for sales orders, the view is typically consumed by pricing analysis reports, order-to-contract reconciliations, and integrations that must extract adjustment detail without depending directly on the base table structure. In the context of a search for change_reason_code, this view is the exposure point for the adjustment reason code and its associated free-text reason, allowing audit reporting on why a price adjustment row was modified.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over a single referenced base object:

• OE_PRICE_ADJUSTMENTS (accessed via a SYNONYM in the APPS schema)

The view text is a direct projection: a flat SELECT of all columns from OE_PRICE_ADJUSTMENTS with no joins, filters, or transformations. Consequently, the view preserves the grain of the base table — one row per price adjustment record — and inherits its indexing and column semantics unchanged. This direct-projection design means any DML or column-level change on the underlying table is automatically reflected, and the view carries no override logic that could alter values.

Key Columns

The view exposes the entire price adjustment structure. Significant columns include:

• PRICE_ADJUSTMENT_ID — primary key of the adjustment row.
• HEADER_ID — owning order header.
• LINE_ID — order line to which the adjustment applies.
• DISCOUNT_ID / DISCOUNT_LINE_ID — modifier and modifier line references from the pricing model.
• LIST_HEADER_ID / LIST_LINE_ID / LIST_LINE_TYPE_CODE / LIST_LINE_NO — price list and price list line context.
• PERCENT, OPERAND, ARITHMETIC_OPERATOR, OPERAND_PER_PQTY — the adjustment calculation definition.
• ADJUSTED_AMOUNT, ADJUSTED_AMOUNT_PER_PQTY, APPLIED_FLAG, UPDATED_FLAG, INVOICED_FLAG, ESTIMATED_FLAG — values and status flags for the applied adjustment.
• CHANGE_SEQUENCE, MODIFIED_FROM, MODIFIED_TO, UPDATE_ALLOWED — change tracking control columns.
• CHANGE_REASON_CODE, CHANGE_REASON_TEXT — the reason code and descriptive text recorded when the adjustment is modified.
• PRICING_PHASE_ID, MODIFIER_LEVEL_CODE, CHARGE_TYPE_CODE, CHARGE_SUBTYPE_CODE, PRICE_BREAK_TYPE_CODE, SUBSTITUTION_ATTRIBUTE — pricing qualification and modifier context.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
• Rebate/accrual columns (ACCRUAL_FLAG, ACCRUAL_CONVERSION_RATE, REBATE_TRANSACTION_TYPE_CODE, REBATE_PAYMENT_SYSTEM_CODE, REDEEMED_FLAG, REDEEMED_DATE) — rebate management attributes.
• SOURCE_SYSTEM_CODE, ORIG_SYS_DISCOUNT_REF — source system provenance for imported adjustments.

The CHANGE_REASON_CODE column is a lookup value that classifies the modification cause, complemented by CHANGE_REASON_TEXT for narrative detail.

Common Use Cases and Queries

Typical use cases include auditing price adjustment changes, reconciling order pricing to contracts, and extracting rebate or accrual adjustments for downstream systems. A representative query returning adjustments with their change reasons for a given order is:

• SELECT HEADER_ID, LINE_ID, PRICE_ADJUSTMENT_ID, DISCOUNT_ID, APPLIED_FLAG, CHANGE_REASON_CODE, CHANGE_REASON_TEXT FROM APPS.OKX_ORD_PRC_ADJMNTS_V WHERE HEADER_ID = :p_header_id AND CHANGE_REASON_CODE IS NOT NULL;

To summarize adjustments by reason code across a period:

• SELECT CHANGE_REASON_CODE, COUNT(*) FROM APPS.OKX_ORD_PRC_ADJMNTS_V GROUP BY CHANGE_REASON_CODE ORDER BY 2 DESC;

For rebate and accrual analysis, filters on ACCRUAL_FLAG or REBATE_TRANSACTION_TYPE_CODE isolate relevant rows. Because the view mirrors the base table exactly, all query tuning, index usage, and security policies applicable to OE_PRICE_ADJUSTMENTS apply unchanged.