Search Results s10_date




Overview
Explore in AI Chat

Overview

SO_HEADERS is a VALID Oracle E-Business Suite view owned by the APPS schema and registered under the OE (Order Entry) product family. It exposes sales order header information for reporting, integration, and backward-compatibility purposes in Oracle EBS 12.1.1 and 12.2.2. The view presents a single logical record per sales order header, combining operational order attributes such as customer, contact, currency, price list, payment terms, freight, warehouse, and sales channel information with a wide set of descriptive and attribute flexfield columns.

Functionally, SO_HEADERS acts as a presentation-layer view over the core order header entity. It is typically used by custom reports, interfaces, and conversion programs that need to read order header data without directly touching the underlying _ALL table. Because the view includes SVRID (surrogate ID) columns alongside their lookup code and ID counterparts, it reflects an environment where descriptive flexfield structures and surrogate key mappings were both retained, which is characteristic of the transition between earlier 11i-era data models and R12 order management structures.

Underlying Base Objects

The documented ETRM metadata for the 12.2.2 release lists a single referenced base object: SO_HEADERS_ALL, accessed through a synonym. This is consistent with standard EBS order management design, where SO_HEADERS_ALL is the multi-organization base table (keyed by ORG_ID) and SO_HEADERS is the non-org-specific, backward-compatible view. The view text confirms that header-level attributes are drawn from the underlying order header record, with ORG_ID retained as a column so that operating unit can still be filtered explicitly. The presence of CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, and PROGRAM_APPLICATION_ID columns confirms that the view preserves standard EBS auditing and concurrent program context columns inherited from the base table.

Key Columns

Common Use Cases and Queries

SO_HEADERS is commonly queried for order header extracts, ETL/integration loads, audit reporting, and validation of order entry data by operating unit. Typical usage filters on ORG_ID and joins HEADER_ID to downstream entities such as order lines or holds.

  • Order header extract by operating unit:
    SELECT header_id, org_id, customer_svrid, currency_code, conversion_rate, terms_id, agreement_id
    FROM apps.so_headers
    WHERE org_id = :p_org_id;
  • Orders with agreement and price list context:
    SELECT header_id, agreement_id, salesrep_id, sales_channel_code, price_list_id
    FROM apps.so_headers
    WHERE agreement_id IS NOT NULL;
  • Payment and credit card detail review:
    SELECT header_id, payment_type_code, payment_amount, check_number, credit_card_code
    FROM apps.so_headers
    WHERE payment_amount > 0;
  • Flexfield-based reporting:
    SELECT header_id, context, attribute1, attribute13, attribute15
    FROM apps.so_headers
    WHERE context = :p_context;

Because the view exposes surrogate IDs and audit columns, it is suited to legacy-style reporting and integration routines. For new development on 12.1.1/12.2.2, Oracle recommends querying the current order management tables and public APIs where supported; however, SO_HEADERS remains a stable read-only interface for existing customizations.