Results for “so_price_adjustments_v”

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

Overview

SO_PRICE_ADJUSTMENTS_V is an APPS-owned, VALID database view in the Oracle E-Business Suite Order Entry (OE) module. It exposes price adjustment records — the individual discounts, surcharges, and pricing modifiers applied to order lines and headers — in a denormalized, human-readable form. The view joins the transactional adjustment table SO_PRICE_ADJUSTMENTS to its defining discount in SO_DISCOUNTS, and further resolves the discount type to a user-facing meaning via SO_LOOKUPS. This join-rich structure means report developers and integration specialists can retrieve adjustment details together with the descriptive name of the discount and the translatable lookup meaning of its type, without writing the three-way join themselves.

Within Oracle EBS 12.1.1 and 12.2.2 the view serves a reporting and integration role rather than a transactional one. Because it is a read-only projection defined with the ADJ.ROWID surfaced as ROW_ID and includes the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and so on) plus the concurrent program context columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID), it is well suited to BI Publisher reports, discoverer workbooks, and outbound interfaces that must expose order pricing in a consumable format.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: FND_GLOBAL (PACKAGE), SO_DISCOUNTS (SYNONYM), SO_LOOKUPS (SYNONYM), and SO_PRICE_ADJUSTMENTS (SYNONYM). The view text defines a three-way equi-join over SO_PRICE_ADJUSTMENTS (aliased ADJ), SO_DISCOUNTS (aliased DISCOUNT), and SO_LOOKUPS (aliased OELUP).

• SO_PRICE_ADJUSTMENTS (ADJ) — the driving transactional table supplying the adjustment row identity, header/line linkage, percent, automatic flag, and descriptive flexfield (CONTEXT and ATTRIBUTE1–15).
• SO_DISCOUNTS (DISCOUNT) — the pricing rule definition. Join condition ADJ.DISCOUNT_ID = DISCOUNT.DISCOUNT_ID. It contributes ADJUSTMENT_NAME (DISCOUNT.NAME), the base for ADJUSTMENT_TYPE_CODE (DISCOUNT.DISCOUNT_TYPE_CODE), and OVERRIDE_ALLOWED_FLAG.
• SO_LOOKUPS (OELUP) — the seeded lookup source. The view filters LOOKUP_TYPE = 'DISCOUNTS' and matches LOOKUP_CODE = DISCOUNT.DISCOUNT_TYPE_CODE to return ADJUSTMENT_TYPE_NAME (OELUP.MEANING).
• FND_GLOBAL — the standard EBS package referenced by APPS views for session context such as ORG_ID and USER_ID resolution.

Key Columns

The view exposes the full column set of SO_PRICE_ADJUSTMENTS plus three derived columns. PRICE_ADJUSTMENT_ID is the unique adjustment identifier and HEADER_ID, LINE_ID, DISCOUNT_ID, and DISCOUNT_LINE_ID provide the relational anchors to the order, its line, and the source discount definition. AUTOMATIC_FLAG indicates whether the adjustment was applied automatically by the pricing engine, and PERCENT carries the adjustment percentage.

The derived columns are the reporting value of the view. ADJUSTMENT_TYPE_CODE (from DISCOUNT.DISCOUNT_TYPE_CODE) is the raw code users search for — the underlying values are the seeded discount type lookup codes. ADJUSTMENT_NAME supplies the discount's descriptive name, and ADJUSTMENT_TYPE_NAME supplies the translated lookup meaning, so a single query returns both the code and its display text. OVERRIDE_ALLOWED_FLAG indicates whether the adjustment may be manually overridden during order entry. CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 carry any configured DFF segments. ROW_ID exposes the physical row identifier, and the WHO and concurrent-program columns support auditing.

Common Use Cases and Queries

A frequent scenario is retrieving all adjustments on an order together with human-readable type descriptions:

• List adjustments by header: SELECT price_adjustment_id, line_id, adjustment_name, adjustment_type_code, adjustment_type_name, percent, automatic_flag FROM so_price_adjustments_v WHERE header_id = :p_header_id;
• Filter by type code (the searched term): ... WHERE adjustment_type_code = :p_adjustment_type_code;
• Automatically applied adjustments only: ... WHERE automatic_flag = 'Y';
• Join to order lines: join LINE_ID to SO_LINES_ALL to correlate adjustments with ordered items for margin or discount reporting.
• Lookup-driven reporting: group by adjustment_type_name to summarize discount usage across headers.

Because the view performs inner joins across all three sources, adjustments whose discount lacks a matching 'DISCOUNTS' lookup row will not appear. When completeness is required, report developers should be aware of this filtering behavior and validate lookup coverage before relying on the view for reconciliation.