Search Results oe_price_adjs_iface_all




Overview
Explore in AI Chat

Overview

The OE_PRICE_ADJS_IFACE_ALL table is a critical multi-organization open interface table within the Oracle E-Business Suite (EBS) Order Management (ONT) module. Its primary role is to serve as a staging area for importing sales order and sales order line-level price adjustments into the application. As an interface table, it facilitates the bulk loading of pricing data from external systems, legacy applications, or custom programs. The table's multi-org structure, indicated by the "_ALL" suffix and the presence of an ORG_ID column, allows it to store data for multiple operating units, adhering to Oracle's security model. Data populated into this table is subsequently processed by concurrent programs or API logic to create valid price adjustments within the core transactional tables of Order Management and Advanced Pricing.

Key Information Stored

The table stores metadata and transactional data necessary to define a price adjustment for an order or order line. While the full column list is not detailed in the provided metadata, the foreign key relationships indicate several critical fields. The ORDER_SOURCE_ID links to the source of the sales order. The LIST_HEADER_ID and LIST_LINE_ID are foreign keys to the QP_LIST_HEADERS_B and QP_LIST_LINES tables in the Advanced Pricing (QP) module, identifying the specific price list and line being applied. Other essential columns typically found in this interface include a unique INTERFACE_LINE_ID for identification, the ORG_ID for multi-org context, and columns for the associated HEADER_ID or LINE_ID of the sales order. It also includes adjustment attributes such as applied value, adjustment type, and operational flags like PROCESS_FLAG and ERROR_MESSAGE to manage the interface processing lifecycle.

Common Use Cases and Queries

The predominant use case is the programmatic import of promotional pricing, discounts, or manual overrides into Oracle Order Management. A common operational query is to check for pending or errored records awaiting processing. For example:

  • SELECT interface_line_id, order_source_id, list_header_id, process_flag, error_message FROM oe_price_adjs_iface_all WHERE process_flag = 'P' AND org_id = 123;

Another typical pattern involves joining with pricing tables to validate incoming data before submission to the interface:

  • SELECT iface.interface_line_id, qll.list_line_code FROM oe_price_adjs_iface_all iface, qp_list_lines qll WHERE iface.list_line_id = qll.list_line_id AND iface.process_flag IS NULL;

Reporting often focuses on summarizing the volume and type of adjustments loaded through the interface over a specific period, which requires grouping by list_header_id and order_source_id.

Related Objects

Based on the documented foreign key relationships, OE_PRICE_ADJS_IFACE_ALL has direct dependencies on several key tables:

  • OE_ORDER_SOURCES: Joined via OE_PRICE_ADJS_IFACE_ALL.ORDER_SOURCE_ID. This table defines valid order origination sources (e.g., 'Manual', 'EDI', 'iStore').
  • QP_LIST_HEADERS_B: Joined via OE_PRICE_ADJS_IFACE_ALL.LIST_HEADER_ID. This is the master table for price lists in Advanced Pricing.
  • QP_LIST_LINES: Joined via OE_PRICE_ADJS_IFACE_ALL.LIST_LINE_ID. This table stores the individual pricing rules and modifiers within a price list.

Furthermore, this interface table is the primary source for the Order Management Open Interface program, which validates and transfers data into core transactional tables such as OE_PRICE_ADJUSTMENTS.