Search Results so_headers_interface_all




Overview
Explore in AI Chat

Overview

The SO_HEADERS_INTERFACE_ALL table is a critical staging table within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary interface for importing sales order header information from external, non-Oracle systems, flat files, or other custom data sources into the core transactional tables of the Order Management suite. Its fundamental role is to act as a holding area where data is validated, enriched, and processed by the Order Import concurrent program (OE_ORDER_PUB.Process_Order) before being transferred to the base transactional tables, such as OE_ORDER_HEADERS_ALL. This staged import process ensures data integrity and allows for error correction before orders become active in the system.

Key Information Stored

The table stores a comprehensive set of attributes that define a sales order's header-level information. The primary key is a composite of the BATCH_ID and ORIGINAL_SYSTEM_REFERENCE, which uniquely identifies each imported record. Key columns, as indicated by the extensive foreign key relationships, include ORDER_TYPE_ID (linking to SO_ORDER_TYPES_115_ALL), CUSTOMER_ID and SHIP_TO_CUSTOMER_ID (linking to RA_CUSTOMERS), and ORDER_SOURCE_ID (linking to SO_ORDER_SOURCES_115). Other essential fields are PRICE_LIST_ID, CURRENCY_CODE, SHIP_ADDRESS_ID, SALESREP_ID, and various rule IDs for accounting and invoicing. Critical process control columns include PROCESS_FLAG, which indicates the record's status (e.g., 'PENDING', 'ERROR', 'PROCESSED'), and ERROR_MESSAGE, which stores validation errors for failed records.

Common Use Cases and Queries

The primary use case is the bulk import of sales orders via the Order Import concurrent program. Custom inbound interfaces or data conversion programs populate this table, after which the standard program validates and creates orders. Common SQL queries involve monitoring the interface for errors or pending records. A typical diagnostic query is:

SELECT batch_id, original_system_reference, process_flag, error_message FROM oe.so_headers_interface_all WHERE process_flag = 'ERROR' AND NVL(TRUNC(creation_date), TRUNC(SYSDATE)) = TRUNC(SYSDATE);

Another frequent pattern is joining with related interface tables, such as SO_LINES_INTERFACE_ALL, to obtain a complete view of a pending order: SELECT shi.*, sli.* FROM oe.so_headers_interface_all shi, oe.so_lines_interface_all sli WHERE shi.original_system_reference = sli.original_system_header_ref AND shi.process_flag = 'PENDING'.

Related Objects

  • SO_LINES_INTERFACE_ALL: The companion interface table for storing imported order line details, linked via ORIGINAL_SYSTEM_HEADER_REF.
  • OE_ORDER_HEADERS_ALL: The primary transactional table where successfully imported header records are ultimately stored.
  • Key Foreign Key Tables: As per the metadata, the table has numerous foreign key dependencies, including RA_CUSTOMERS (for customer data), SO_ORDER_TYPES_115_ALL (for order type), RA_ADDRESSES_ALL (for ship-to address), SO_PRICE_LISTS_B, and RA_TERMS_B. These relationships enforce referential integrity during the import validation process.
  • Concurrent Program: The Order Import program (typically seeded as "Import Orders") is the primary consumer of this table, executing the PL/SQL API OE_ORDER_PUB.Process_Order.