Results for “adjustment_type_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_PRICE_ADJUSTMENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the ONT – Order Management product family. The view is a thin projection over the base table OE_PRICE_ADJUSTMENTS, exposing the price adjustment records that Oracle Order Management and Oracle Advanced Pricing generate when pricing, discounts, surcharges, coupons, rebates, and other modifiers are applied to order headers and order lines. Its primary value to implementers is that it surfaces the pricing adjustment structure without requiring consumers to join directly to the underlying transactional table or to translate internal lookup codes. Because the view is marked VALID and ships as a standard APPS object, it is commonly used as a stable interface for custom reports, Oracle Discoverer or OBIEE extracts, interface programs, and third-party order capture integrations that must display or reconcile the adjustments applied during pricing.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two referenced base objects: OE_PRICE_ADJUSTMENTS (exposed through a synonym) and QP_LIST_HEADERS_TL (also through a synonym). OE_PRICE_ADJUSTMENTS is the primary source of every column beginning with the ADJ prefix; it stores one row per adjustment instance attached to an order header or line, including the pricing attributes, modifier references, tax attributes, rebate attributes, and descriptive flexfield context and attribute columns. QP_LIST_HEADERS_TL is joined to supply the translatable modifier list name, aliased in the view text as QPLH.NAME and exposed as ADJUSTMENT_NAME. This join links each order-level adjustment back to the price list, agreement, promotion, or discount list that produced it. The view therefore presents a denormalized, read-friendly union of transactional adjustment data and the descriptive name of the originating pricing modifier.

Key Columns

The view exposes the full administrative column set of the base table, including ROW_ID, PRICE_ADJUSTMENT_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

• Hierarchical identifiers: HEADER_ID and LINE_ID place the adjustment at order header or line level; PARENT_ADJUSTMENT_ID supports adjustment hierarchies such as benefits applied on top of a base discount.
• Modifier linkage: DISCOUNT_ID, DISCOUNT_LINE_ID, LIST_HEADER_ID, LIST_LINE_ID, LIST_LINE_TYPE_CODE, and ORIG_SYS_DISCOUNT_REF tie the adjustment to its pricing modifier; QPLH.NAME supplies the human-readable ADJUSTMENT_NAME.
• Calculation attributes: PERCENT, OPERAND, ARITHMETIC_OPERATOR, ADJUSTED_AMOUNT, MODIFIER_MECHANISM_TYPE_CODE, MODIFIER_LEVEL_CODE, and RANGE_BREAK_QUANTITY describe how the adjustment was computed.
• Control flags: AUTOMATIC_FLAG, APPLIED_FLAG, UPDATED_FLAG, UPDATE_ALLOWED (aliased OVERRIDE_ALLOWED_FLAG), INVOICED_FLAG, ESTIMATED_FLAG, and SPLIT_ACTION_CODE.
• Tax attributes: TAX_CODE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, and TAX_EXEMPT_REASON_CODE.
• Rebate and accrual attributes: REBATE_TRANSACTION_TYPE_CODE, REBATE_TRANSACTION_REFERENCE, REBATE_PAYMENT_SYSTEM_CODE, ACCRUAL_FLAG, ACCRUAL_CONVERSION_RATE, REDEEMED_FLAG, and REDEEMED_DATE.
• Flexfield support: CONTEXT plus ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical scenarios include order-level discount auditing, rebate accrual reconciliations, invoice-to-order adjustment traceability, and custom pricing reports that need the modifier name alongside the adjustment amount. A representative query retrieving applied adjustments for a specific order is:

SELECT a.header_id, a.line_id, a.price_adjustment_id, a.adjustment_name, a.adjusted_amount, a.percent, a.applied_flag, a.automatic_flag, a.change_reason_code FROM oe_price_adjustments_v a WHERE a.header_id = :p_header_id AND a.applied_flag = 'Y' ORDER BY a.line_id, a.price_adjustment_id;

For auditing rebates and accruals, filtering on ACCRUAL_FLAG or REBATE_TRANSACTION_TYPE_CODE isolates rebate-related adjustments, while TAX_EXEMPT_FLAG supports tax-exemption reporting. Because the view is a simple projection with no computational logic, it can be safely joined to OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and QP_LIST_LINES on the exposed identifiers for detailed pricing analysis.