Search Results benefit_uom_code




Overview
Explore in AI Chat

Overview

OE_AK_HEADER_PRCADJS_V is a reportable, multi-record view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Order Management (ONT) product family and exposes header-level price adjustment (modifier) information in a flattened, denormalized form suitable for Oracle Application Framework (OAF) regions, Oracle XML Publisher reports, Business Intelligence Publisher extracts, and custom integrations. The view is an "AK" (Application Kit) style construct, meaning it is designed to feed declarative UI pages and reporting layers rather than to serve as a transaction-entry object. Records are read-only from a business-logic perspective; all DML should target the underlying pricing entities. Because it surfaces attributes such as ESTIMATED_FLAG, APPLIED_FLAG, INVOICED_FLAG, and MODIFIED_FROM/MODIFIED_TO, it is frequently used to analyze how list price and modifier adjustments were estimated, applied, and subsequently invoiced across an order header.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over the base object OE_PRICE_ADJUSTMENTS_V (itself a view). The visible SELECT list references pricing-adjustment columns such as PRICE_ADJUSTMENT_ID, HEADER_ID, LINE_ID, DISCOUNT_ID, DISCOUNT_LINE_ID, LIST_HEADER_ID, LIST_LINE_ID, MODIFIER_MECHANISM_TYPE_CODE, OPERAND, ARITHMETIC_OPERATOR, PERCENT, and ADJUSTED_AMOUNT. These ultimately trace to the Advance Pricing (QP) adjustment and list-line tables (for example QP_LIST_HEADERS, QP_LIST_LINES, QP_PRICE_ADJUSTMENTS, and QP_PRICING_ATTRIBUTES) joined to OE_ORDER_HEADERS_ALL through HEADER_ID. Because the view inherits from OE_PRICE_ADJUSTMENTS_V, any change to the underlying pricing views propagates automatically; customers should never hard-code column ordering, as several columns are literal RPAD separators appended by the AK generator.

Key Columns

  • HEADER_ID – Surrogate key linking the adjustment to OE_ORDER_HEADERS_ALL; the primary join for header-level reporting.
  • PRICE_ADJUSTMENT_ID / DISCOUNT_LINE_ID – Identifiers for the applied modifier and its list line.
  • ESTIMATED_FLAG – Indicates whether the adjustment amount is an estimate (not yet finalized). This is the column most frequently searched when reconciling estimated versus actual pricing.
  • APPLIED_FLAG / UPDATED_FLAG / INVOICED_FLAG – Status indicators for whether the modifier has been applied, updated, or invoiced.
  • MODIFIER_MECHANISM_TYPE_CODE, OPERAND, ARITHMETIC_OPERATOR, PERCENT – Define the calculation mechanism of the adjustment.
  • MODIFIED_FROM / MODIFIED_TO / ADJUSTED_AMOUNT – The value range affected and the resulting adjusted amount.
  • AUTOMATIC_FLAG, UPDATE_ALLOWED, CHANGE_REASON_CODE – Control and audit attributes.
  • AC_ATTRIBUTE1..15 / ATTRIBUTE1..15 – Descriptive flexfield context and segments for extensibility.

Common Use Cases and Queries

Typical uses include reconciling estimated price adjustments against invoiced amounts, exporting modifier detail for downstream analytics, and exposing header price adjustments in custom OAF pages. A representative query filtering on the searched column is:

  • SELECT header_id, price_adjustment_id, modified_from, modified_to, adjusted_amount, estimated_flag, applied_flag FROM oe_ak_header_prcadj_v WHERE estimated_flag = 'Y';
  • Join to oe_order_headers_all on header_id to retrieve order_number and ordered_date.
  • Join to oe_price_adjustments_v on price_adjustment_id for line-level detail.

Because the view is read-only and denormalized, use it for reporting rather than transactional updates.