Search Results so_headers_all

Overview

The SO_HEADERS_ALL table is the central repository for order header information within the Oracle E-Business Suite Order Entry (OE) module. It serves as the master record for every sales order, capturing the overarching transactional metadata that defines the business agreement between the customer and the organization. This table is fundamental to the order management lifecycle, from entry through fulfillment and invoicing. As a multi-organization table, denoted by the "_ALL" suffix, it contains data for all operating units, with access typically governed by the MOAC (Multi-Org Access Control) security profile. Its integrity is maintained through a complex network of foreign key relationships with core trading community, pricing, and sales force entities.

Key Information Stored

The table's primary key is the system-generated HEADER_ID, which uniquely identifies each order header. A significant alternate unique key combines ORDER_NUMBER and ORDER_TYPE_ID, enforcing business-level uniqueness for an order type. Critical foreign key columns define the order's context: CUSTOMER_ID links to RA_CUSTOMERS, ORDER_TYPE_ID to SO_ORDER_TYPES, and SALESREP_ID to RA_SALESREPS_ALL. Financial and pricing attributes are stored in columns such as CURRENCY_CODE, PRICE_LIST_ID, and TERMS_ID. The table also holds key site-use identifiers (INVOICE_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID) for customer locations and contact IDs for various roles. Operational status, dates (ordered, booked), and sourcing information (SOURCE_HEADER_ID for copied orders) are also core data elements within this structure.

Common Use Cases and Queries

This table is essential for operational reporting, data validation, and integration tasks. Common queries involve joining with the SO_LINES_ALL table to create a complete order snapshot. A fundamental pattern is retrieving order headers with their associated lines: SELECT h.header_id, h.order_number, h.ordered_date, l.line_id, l.ordered_item FROM oe.so_headers_all h JOIN oe.so_lines_all l ON h.header_id = l.header_id WHERE h.org_id = :p_org_id;. Another critical use case is analyzing order sources or copying relationships via the SOURCE_HEADER_ID. The table is also central to customer order history reports, often joined to customer and site tables. As indicated by the user's search term "icx_panel_summary", the HEADER_ID is referenced by the ICX_PANEL_SUMMARY table (LAST_ORDER_HEADER_ID), linking order data to iProcurement requisition summary information.

Related Objects

SO_HEADERS_ALL has extensive relationships across the EBS suite. Its most direct child is the SO_LINES_ALL table, which stores the detailed line items for each header. It is referenced by numerous transactional and control tables, including SO_ORDER_HOLDS_ALL, SO_ORDER_CANCELLATIONS, SO_PICKING_BATCHES_ALL, and SO_NOTE_REFERENCES. Key parent tables, as per the provided metadata, include RA_CUSTOMERS, SO_ORDER_TYPES_115_ALL, RA_SITE_USES_ALL (for ship-to and invoice-to addresses), SO_PRICE_LISTS_B, and FND_CURRENCIES. Beyond the OE module, it is referenced by objects in other products, such as CST_MARGIN_BUILD in Cost Management and, notably, ICX_PANEL_SUMMARY in iProcurement, demonstrating its integration into broader supply chain and procurement processes.