Results for “retrobill_request_id”

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

Overview

ONT.OE_PRICE_ADJUSTMENTS is a core Order Management table that stores every price adjustment applied to an order header or an order line. In Oracle EBS 12.1.1 and 12.2.2, it captures modifier and list-line discounts, freight and special charges, tax on order lines, and shipping costs recorded at ship confirmation. Each row represents a single adjustment instance — a discount, surcharge, tax, freight charge or rebate applied at a defined pricing phase — and is linked back to the originating pricing engine definition through the QP list header, list line and pricing phase columns.

The ETRM metadata lists 106 columns and classifies the object heuristically as satellite-leaning in Data Vault terms. This is a modeling suggestion: the table behaves primarily as a descriptive satellite hanging off the order header and order line hubs, keyed by its own surrogate PRICE_ADJUSTMENT_ID, and does not itself function as a business hub.

Key Information Stored

The surrogate primary key is PRICE_ADJUSTMENT_ID, enforced by OE_PRICE_ADJUSTMENTS_PK and by the unique index OE_PRICE_ADJUSTMENTS_U1. The business context is established by the foreign-key columns:

• HEADER_ID — the order header the adjustment belongs to (OE_ORDER_HEADERS_ALL).
• LINE_ID — the specific order line when the adjustment is line-level (OE_ORDER_LINES_ALL).
• LIST_HEADER_ID, LIST_LINE_ID, LIST_LINE_TYPE_CODE — the pricing list and line that generated the modifier.
• PRICING_PHASE_ID — the pricing phase (e.g. list, formulas, modifiers) that applied the adjustment.
• DISCOUNT_ID, DISCOUNT_LINE_ID — link to the discount definition and its line.
• COST_ID — reference to the freight cost record (WSH_FREIGHT_COSTS) when the row represents shipping or freight.
• ADJUSTED_AMOUNT, OPERAND, PERCENT, ARITHMETIC_OPERATOR — the applied value and how it was computed.
• APPLIED_FLAG, UPDATED_FLAG, AUTOMATIC_FLAG — indicate whether the adjustment was actually applied, has been modified, or was applied automatically by the pricing engine.
• TAX_CODE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_RATE_ID, INVOICED_FLAG, INVOICED_AMOUNT — tax and invoicing attributes.
• PARENT_ADJUSTMENT_ID — supports hierarchical or related adjustments.
• CHARGE_TYPE_CODE, CHARGE_SUBTYPE_CODE, CREDIT_OR_CHARGE_FLAG — classify freight, special charge and credit adjustments.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID) support audit and concurrent-program tracing.

Common Use Cases and Queries

Typical reporting scenarios include order-level discount and surcharge analysis, tax reconciliation, and freight cost verification against ship confirmation.

• List all adjustments for an order: SELECT price_adjustment_id, line_id, adjusted_amount, charge_type_code FROM oe_price_adjustments WHERE header_id = :p_header_id;
• Sum discounts by charge type: SELECT charge_type_code, SUM(adjusted_amount) FROM oe_price_adjustments WHERE header_id = :p_header_id GROUP BY charge_type_code;
• Identify tax rows: filter on tax_code IS NOT NULL or applied_flag = 'Y'.
• Freight/shipping reconciliation: join COST_ID to WSH_FREIGHT_COSTS.
• Trace a modifier back to pricing setup via LIST_HEADER_ID, LIST_LINE_ID and PRICING_PHASE_ID.

Related Objects

• OE_ORDER_HEADERS_ALL — join on HEADER_ID.
• OE_ORDER_LINES_ALL — join on LINE_ID.
• QP_LIST_HEADERS_B / QP_LIST_LINES — join on LIST_HEADER_ID / LIST_LINE_ID.
• QP_PRICING_PHASES — join on PRICING_PHASE_ID.
• SO_DISCOUNTS / SO_DISCOUNT_LINES_115 — join on DISCOUNT_ID / DISCOUNT_LINE_ID.
• WSH_FREIGHT_COSTS — join on COST_ID.
• OE_PRICE_ADJ_ASSOCS — child table linking adjustments via PRICE_ADJUSTMENT_ID and RLTD_PRICE_ADJ_ID.
• OE_PRICE_ADJ_ATTRIBS — child attribute table keyed on PRICE_ADJUSTMENT_ID.