Search Results inl_ship_headers_all_u2

Overview

The INL.INL_SHIP_HEADERS_ALL table is a core transactional table within the Oracle E-Business Suite Landed Cost Management (LCM) module, owned by the INL schema. It stores header-level information for shipments associated with landed cost calculations, holding one row per shipment. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while its associated indexes are held in APPS_TS_TX_IDX. The table is registered under FND Design Data as INL.INL_SHIP_HEADERS_ALL and is flagged VALID. Because shipments participate in the landed cost flow — from receipt through matching and cost absorption — this table acts as the anchor record against which shipment lines, adjustments, and matching results are organized.

From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning it does not exhibit the strongly connected foreign-key hub-and-link topology typical of a transactional hub or link. In practice, it behaves like a hub-like anchor keyed on SHIP_HEADER_ID, with descriptive shipment attributes forming satellite-like content. This classification is a mined suggestion rather than a documented Oracle design intent, and should be treated as guidance when constructing downstream warehouse or integration models.

Key Information Stored

The surrogate primary key of the table is SHIP_HEADER_ID, enforced by the unique index INL_SHIP_HEADERS_ALL_U1. Business-key candidates are captured by the unique indexes INL_SHIP_HEADERS_ALL_U1 (on SHIP_HEADER_ID) and INL_SHIP_HEADERS_ALL_U2 (composite on ORGANIZATION_ID and SHIP_NUM), the latter reflecting the natural business uniqueness of a shipment number within an inventory organization. Additional non-unique indexes (_N1 on SHIP_TYPE_ID, _N2 on LEGAL_ENTITY_ID, and _N3 on LOCATION_ID) support reporting and lookup access paths. The most significant columns include:

• SHIP_HEADER_ID — surrogate primary key and shipment identifier.
• SHIP_NUM — shipment number, unique per organization (up to 25 characters).
• SHIP_DATE — the shipment date used for period and timing analysis.
• SHIP_TYPE_ID — reference to the shipment type definition.
• SHIP_STATUS_CODE — shipment status, sourced from the lookup INL_SHIP_STATUSES.
• PENDING_MATCHING_FLAG — "Y"/"N" indicator that lines are matched but not yet absorbed by the landed cost calculation.
• LEGAL_ENTITY_ID — legal entity owning the shipment, with a documented foreign key to FV_LEGAL_ENTITIES.
• ORGANIZATION_ID — inventory organization identifier.
• LOCATION_ID — location identifier associated with the shipment.
• ORG_ID — multi-org operating unit identifier.
• TAXATION_COUNTRY — country used for tax calculation purposes.
• PENDING_UPDATE_FLAG and SIMULATION_ID — control flags and simulation linkage for landed cost processing.
• RCV_ENABLED_FLAG — indicates whether the shipment is linked to receiving activity.
• Interface traceability columns: SHIP_HEADER_INT_ID, INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_TABLE, and INTERFACE_SOURCE_LINE_ID.
• Standard WHO and audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus the ATTRIBUTE1–ATTRIBUTE15 flexfield descriptors.

Common Use Cases and Queries

Typical usage centers on landed cost reconciliation, shipment status monitoring, and interface troubleshooting. Common query patterns include:

• Locating a shipment by business key — SELECT * FROM INL.INL_SHIP_HEADERS_ALL WHERE ORGANIZATION_ID = :org_id AND SHIP_NUM = :ship_num; leveraging the INL_SHIP_HEADERS_ALL_U2 unique index.
• Identifying shipments pending cost absorption — SELECT SHIP_HEADER_ID, SHIP_NUM, SHIP_DATE FROM INL.INL_SHIP_HEADERS_ALL WHERE PENDING_MATCHING_FLAG = 'Y' AND SHIP_STATUS_CODE = '...';
• Reporting by legal entity or location — filtering on LEGAL_ENTITY_ID and LOCATION_ID, both indexed, for landed cost accruals and entity-level analysis.
• Tracing interface loads — joining on SHIP_HEADER_INT_ID and INTERFACE_SOURCE_TABLE to reconcile inbound integration rows against their originating source records.
• Simulation review — isolating rows by SIMULATION_ID to evaluate what-if landed cost scenarios before posting.

Status lookups should always resolve SHIP_STATUS_CODE against the INL_SHIP_STATUSES lookup to present meaningful values in reports.

Related Objects

The table participates in a small but meaningful dependency footprint. The documented foreign key LEGAL_ENTITY_ID → FV_LEGAL_ENTITIES ties shipments to their owning legal entity. Shipment line detail is typically held in a corresponding lines table keyed on SHIP_HEADER_ID, and landed cost adjustments reference the header through ADJUSTMENT_NUM and matching flags. The interface columns (SHIP_HEADER_INT_ID, INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_TABLE, INTERFACE_SOURCE_LINE_ID) connect the header to inbound interface and staging structures. Functional joins to purchasing and receiving tables using ORGANIZATION_ID, LOCATION_ID, and RCV_ENABLED_FLAG enable reconciliation between landed cost shipments and their goods receipt origins. Reports and concurrent programs that compute or rehearse landed costs rely on SHIP_HEADER_ID as the driving key across the module's line, adjustment, and matching objects.