Search Results so_header_attributes_u1

Overview

OE.SO_HEADER_ATTRIBUTES is a child (sibling) table to OE.SO_HEADERS_ALL in the Oracle Order Entry/Shipping (OE) application. It stores globalization information about sales orders — the country-specific and localization attributes that extend the core sales order header beyond the standard English-language columns. For each row in SO_HEADERS_ALL there is, at most, one corresponding row in SO_HEADER_ATTRIBUTES, making this a strict one-to-zero-or-one extension of the order header entity. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is flagged VALID under the OE schema, with FND Design Data reference OE.SO_HEADER_ATTRIBUTES. Under a heuristic Data Vault classification derived from its foreign key structure, this object is modeled as standalone; as a modeling suggestion, it is best treated as a satellite attached to the SO_HEADERS_ALL hub, since it carries descriptive globalization context keyed to the same header identity. The object contains 31 documented columns in the 12.2.2 physical schema, and its documentation status is fully populated, making it a reliable reference point for both 12.1.1 and 12.2.2 environments.

Key Information Stored

The table is anchored by the surrogate primary key HEADER_ID (NUMBER), which is the system-generated identifier that ties each attributes row back to its parent sales order in SO_HEADERS_ALL. The unique index SO_HEADER_ATTRIBUTES_U1 (HEADER_ID) is documented as the business-key candidate enforcing the one-row-per-header cardinality. Consequently, HEADER_ID is both the primary key and the join key — no separate business identifier exists.

• HEADER_ID — Surrogate primary key; system-generated ID linking to SO_HEADERS_ALL.
• GLOBAL_ATTRIBUTE_CATEGORY (VARCHAR2 30) — Descriptive flexfield context that determines which globalization attributes are meaningful for a given order.
• GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20 (VARCHAR2 150) — The globalization information payload; each column holds country- or localization-specific data configured for the sales order header.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN provide audit trail and user accountability.
• Concurrent program columns — PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID record which concurrent program and request last touched the row, supporting diagnostic and reconciliation reporting.

The WHO and concurrent columns are populated automatically by Oracle Forms and the concurrent manager, so they are typically read rather than written directly.

Common Use Cases and Queries

Because the table is a one-to-one extension, the dominant query pattern is an outer join from the order header to retrieve globalization data without losing orders that have no attributes row. A representative pattern:

• SELECT h.ORDER_NUMBER, a.GLOBAL_ATTRIBUTE_CATEGORY, a.GLOBAL_ATTRIBUTE1, a.GLOBAL_ATTRIBUTE2 FROM OE.SO_HEADERS_ALL h, OE.SO_HEADER_ATTRIBUTES a WHERE h.HEADER_ID = a.HEADER_ID (+) AND h.ORG_ID = :org;
• Reporting on localizations — group by GLOBAL_ATTRIBUTE_CATEGORY to profile how many orders carry each globalization context.
• Audit and troubleshooting — query by REQUEST_ID or PROGRAM_ID to trace which concurrent process last updated a header's globalization attributes.
• Data migration and validation — confirm cardinality by checking for duplicate HEADER_ID values against SO_HEADER_ATTRIBUTES_U1.

These queries are commonly embedded in BI Publisher reports, custom concurrent programs, and Order Management extensions in both 12.1.1 and 12.2.2.

Related Objects

As a standalone-classified object with no outgoing foreign keys in the documented relationship data, all relationships are inbound. The following objects are most significant:

• OE.SO_HEADERS_ALL — Parent entity; joined on HEADER_ID (one-to-zero-or-one).
• OE.SO_HEADER_ATTRIBUTES_U1 — Unique index on HEADER_ID; the business-key candidate enforcing cardinality.
• OE.SO_HEADER_ATTRIBUTES_PK — Primary key constraint on HEADER_ID.
• OE.SO_LINES_ALL — Order lines, linked indirectly through the shared HEADER_ID.
• Order Management APIs (OE_ORDER_PUB / OE_Order_PUB) — Public programmatic interfaces that may populate globalization attributes during order creation and update.
• FND Descriptive Flexfield definitions — Drive the meaning of GLOBAL_ATTRIBUTE_CATEGORY and the GLOBAL_ATTRIBUTE1–20 columns.