Results for “so_headers_all”

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

Overview

SO_HEADERS_ALL is the master order header table in the Oracle Order Management (OE) module, owned by the OE schema. It stores one row per order (or order version) in Oracle E-Business Suite 12.1.1 and 12.2.2, serving as the central anchor for all downstream order processing activities — pricing, scheduling, shipping, invoicing, and holds. Because almost every subsidiary order object carries a HEADER_ID foreign key back to this table, it acts as the semantic and structural entry point for the entire order lifecycle.

From a data-modeling perspective, the documented foreign-key topology classifies SO_HEADERS_ALL as a hub (heuristically mined from its key structure). It introduces and preserves the durable HEADER_ID business identifier while referencing descriptive and transactional attributes through dependent objects. Note the metadata conflict: the DBA excerpt lists SO_HEADERS_PK as the primary key and SO_HEADERS_UK1 (ORDER_NUMBER, ORDER_TYPE_ID) as a unique key, whereas the ETRM physical schema reports SO_HEADERS_U1 (HEADER_ID) and SO_HEADERS_U2 (ORDER_NUMBER, ORDER_TYPE_ID) as unique indexes. Both sources agree that header identity is uniquely determined by HEADER_ID, with ORDER_NUMBER plus ORDER_TYPE_ID forming the natural business key.

Key Information Stored

The table carries 180 documented columns, of which the most significant are:

• HEADER_ID — surrogate primary key; the join spine for all dependent order objects.
• ORDER_NUMBER and ORDER_TYPE_ID — the unique business key combination (SO_HEADERS_U2); ORDER_TYPE_ID also foreign-keys to SO_ORDER_TYPES_115_ALL.
• ORDER_CATEGORY and ORIGINAL_SYSTEM_SOURCE_CODE — distinguish order flow (e.g., ORDER, RETURN) and origin.
• CUSTOMER_ID, SHIP_TO_SITE_USE_ID, INVOICE_TO_SITE_USE_ID, and their associated contact IDs — the customer and address snapshots that drive shipping and billing.
• DATE_ORDERED and DATE_REQUESTED_CURRENT — order and current requested dates used for scheduling and lead-time analysis.
• OPEN_FLAG and CANCELLED_FLAG — lifecycle status indicators (Open, Closed, Cancelled) frequently used in reporting filters.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_TYPE_CODE, PRICE_LIST_ID — pricing and localization context.
• TERMS_ID, INVOICING_RULE_ID, ACCOUNTING_RULE_ID, PAYMENT_TYPE_CODE — commercial terms and receivables integration.
• WAREHOUSE_ID, SHIP_METHOD_CODE, SHIPMENT_PRIORITY_CODE, FREIGHT_TERMS_CODE, FOB_CODE, SHIP_PARTIAL_FLAG — fulfillment and shipping attributes.
• AGREEMENT_ID, SALESREP_ID, SALES_CHANNEL_CODE — sales channel and agreement linkage.
• ORG_ID — multi-org operating unit discriminator, essential for any MOAC query pattern.
• ATTRIBUTE1–15 and CONTEXT — flexfield descriptors for extensions.

Common Use Cases and Queries

Typical reporting scenarios include open order backlogs, order status dashboards, fulfillment KPIs, and holds analysis. Because ICX_PANEL_SUMMARY.LAST_ORDER_HEADER_ID references SO_HEADERS_ALL.HEADER_ID, the table also underpins the iStore/self-service "last order" panel used in customer-facing portals.

A representative backlog query:

• SELECT h.ORDER_NUMBER, h.DATE_ORDERED, h.OPEN_FLAG, h.CURRENCY_CODE, h.ORDER_TYPE_ID FROM OE.SO_HEADERS_ALL h WHERE h.ORG_ID = :p_org_id AND h.OPEN_FLAG = 'Y' AND h.CANCELLED_FLAG = 'N';

Order with customer and line detail:

• SELECT h.ORDER_NUMBER, c.CUSTOMER_NAME, l.LINE_NUMBER FROM OE.SO_HEADERS_ALL h JOIN RA_CUSTOMERS c ON c.CUSTOMER_ID = h.CUSTOMER_ID JOIN OE.SO_LINES_ALL l ON l.HEADER_ID = h.HEADER_ID WHERE h.HEADER_ID = :p_header_id;

Joining to ICX_PANEL_SUMMARY for portal context uses ICX_PANEL_SUMMARY.LAST_ORDER_HEADER_ID = SO_HEADERS_ALL.HEADER_ID. Always filter on ORG_ID in multi-org environments.

Related Objects

• SO_LINES_ALL — join on SO_HEADERS_ALL.HEADER_ID = SO_LINES_ALL.HEADER_ID; the order line detail.
• RA_CUSTOMERS — join on SO_HEADERS_ALL.CUSTOMER_ID = RA_CUSTOMERS.CUSTOMER_ID; customer master.
• SO_ORDER_TYPES_115_ALL — join on ORDER_TYPE_ID; order classification.
• SO_ORDER_HOLDS_ALL and SO_HOLD_SOURCES_ALL — join on HEADER_ID / HOLD_ENTITY_ID; hold management.
• SO_PICKING_HEADERS_ALL (ORDER_HEADER_ID) and SO_PICKING_BATCHES_ALL (HEADER_ID) — picking and warehouse execution.
• SO_ORDER_APPROVALS, SO_LINE_APPROVALS, and SO_ORDER_CANCELLATIONS — join on HEADER_ID; workflow approvals and cancellations.
• ICX_PANEL_SUMMARY — join on LAST_ORDER_HEADER_ID = HEADER_ID; the object the user searched.
• RA_SALESREPS_ALL, RA_TERMS_B, RA_RULES, and SO_PRICE_LISTS_B — join on SALESREP_ID, TERMS_ID, ACCOUNTING_RULE_ID, and PRICE_LIST_ID respectively.