Search Results applied_flag




Overview
Explore in AI Chat

Overview

ASO_I_ORDER_PRICE_ADJS_V is a public Oracle E-Business Suite view owned by the APPS schema and classified under the ASO - Order Capture product family. It is documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The view presents price adjustment information for orders by exposing a focused projection of the OE_PRICE_ADJUSTMENTS table. Its definition is a simple SELECT with no joins, filters, or aggregations, which makes it a lightweight, low-overhead access path for reporting and integration consumers who need order-level and line-level price adjustment attributes without querying the full pricing adjustments table.

The view is intended for inbound and outbound integration and inquiry scenarios where order capture, pricing, and fulfillment components need to read how a list or selling price was modified. Because it exposes only a fixed subset of columns, it acts as a stable, purpose-built interface for price adjustment data associated with orders.

Users searching for "applied_flag" typically arrive at this object because APPLIED_FLAG is one of the nine columns surfaced by the view. This column indicates whether the price adjustment has been applied to the order or line context in question, making it central to determining which adjustments are active versus merely defined.

Underlying Base Objects

The only documented referenced base object is OE_PRICE_ADJUSTMENTS, accessed through a SYNONYM in the APPS schema. The view text is:

Because there is a one-to-one column mapping with no joins or WHERE clause, every row returned corresponds directly to a row in OE_PRICE_ADJUSTMENTS, and all filtering, ordering, and aggregation logic must be supplied by the caller. This design keeps the view dependency-free and predictable across the 12.1.1 and 12.2.2 code lines.

Key Columns

  • PRICE_ADJUSTMENT_ID — Primary identifier of the price adjustment record; the natural join key back to OE_PRICE_ADJUSTMENTS and related pricing entities.
  • CREATION_DATE — Timestamp when the adjustment record was created.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification to the record; useful for incremental extraction and auditing.
  • HEADER_ID — Identifies the order header to which the adjustment belongs.
  • LINE_ID — Identifies the specific order line associated with the adjustment.
  • LIST_HEADER_ID — Header identifier of the price list from which the adjustment originates.
  • LIST_LINE_ID — Line identifier within the source price list.
  • LIST_LINE_TYPE_CODE — Code describing the type of price list line (for example, the pricing element category) that generated the adjustment.
  • APPLIED_FLAG — Flag indicating whether the price adjustment has been applied. This is the column most commonly referenced when users search on "applied_flag," since it distinguishes applied adjustments from those that were calculated but not applied.

Common Use Cases and Queries

Typical scenarios include reconciling order pricing, auditing which adjustments were actually applied, and extracting adjustments for downstream analytics or integration.

Retrieve all adjustments for a given order header:

  • SELECT price_adjustment_id, header_id, line_id, list_line_type_code, applied_flag FROM aso_i_order_price_adjs_v WHERE header_id = :p_header_id;

Isolate applied adjustments only, which is the common "applied_flag" use case:

  • SELECT price_adjustment_id, header_id, line_id, list_header_id, list_line_id FROM aso_i_order_price_adjs_v WHERE applied_flag = 'Y';

Support incremental extraction using the audit columns:

  • SELECT price_adjustment_id, header_id, line_id, applied_flag, last_update_date FROM aso_i_order_price_adjs_v WHERE last_update_date >= :p_since_date;

Because the view performs no filtering, callers should always constrain queries by HEADER_ID, LINE_ID, or an indexed adjustment identifier to avoid full scans of OE_PRICE_ADJUSTMENTS, particularly in high-volume order capture environments.