Search Results inl_ship_headers_int_u1

Overview

INL.INL_SHIP_HEADERS_INT is an Oracle E-Business Suite open interface (staging) table owned by the INL schema. It stores inbound shipment header data that has been loaded programmatically but not yet processed into the destination transaction tables by the Landed Cost Management (LCM) open interface processor. The table is registered in FND Design Data as INL.INL_SHIP_HEADERS_INT and resides in the APPS_TS_TX_DATA tablespace.

Its role is to serve as the transient holding area between external data sources (such as EDI feeds, third-party transportation systems, or custom staging routines) and the validated shipment records consumed by Oracle Landed Cost Management. Rows are inserted with a processing status, validated, and then pushed through the LCM open interface. From a data-modeling perspective, the mined relationship metadata classifies this object heuristically as a standalone structure rather than a strict hub, link, or satellite; it is best treated as a staging or integration entity whose unique key candidate, INL_SHIP_HEADERS_INT_U1, anchors each interface row.

Key Information Stored

The table contains 49 columns. The most operationally significant are:

• SHIP_HEADER_INT_ID — surrogate primary key and the single column of the unique index INL_SHIP_HEADERS_INT_U1, the business-key candidate that uniquely identifies each interface row.
• GROUP_ID — open interface group identifier used to process rows in batches.
• PROCESSING_STATUS_CODE — current state of the row within the open interface lifecycle.
• TRANSACTION_TYPE — open interface transaction type governing how the row is applied.
• INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_TABLE, INTERFACE_SOURCE_LINE_ID — provenance columns identifying the originating source system and record.
• VALIDATION_FLAG — "Y"/"N" indicator controlling whether the row participates in validation.
• SHIP_NUM, SHIP_DATE, SHIP_TYPE_ID, SHIP_TYPE_CODE — business shipment header attributes.
• LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME — legal entity context; LEGAL_ENTITY_ID is the documented foreign key to FV_LEGAL_ENTITIES.
• ORGANIZATION_ID, ORGANIZATION_CODE, LOCATION_ID, LOCATION_CODE, ORG_ID — inventory organization, location, and operating unit context.
• SHIP_HEADER_ID — link to the destination shipment record once processing completes.
• LAST_TASK_CODE — last task to be executed by the LCM Open Interface Processor.
• RCV_ENABLED_FLAG — controls integration with receiving.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) support audit and interface-run traceability, along with fifteen descriptive flexfield ATTRIBUTE columns.

Common Use Cases and Queries

Typical scenarios include monitoring open interface runs, isolating rows that failed validation, and tracking loaded data through to processed shipment headers.

• Locating a specific interface row by its surrogate key:

  SELECT * FROM INL.INL_SHIP_HEADERS_INT
   WHERE SHIP_HEADER_INT_ID = :p_id;

• Monitoring processing status by group:

  SELECT GROUP_ID, PROCESSING_STATUS_CODE, COUNT(*)
    FROM INL.INL_SHIP_HEADERS_INT
   GROUP BY GROUP_ID, PROCESSING_STATUS_CODE;

• Reporting unprocessed or invalid rows for error correction:

  SELECT SHIP_HEADER_INT_ID, SHIP_NUM, INTERFACE_SOURCE_CODE
    FROM INL.INL_SHIP_HEADERS_INT
   WHERE VALIDATION_FLAG = 'Y'
     AND PROCESSING_STATUS_CODE <> 'PROCESSED';

• Auditing an interface execution by its concurrent request:

  SELECT * FROM INL.INL_SHIP_HEADERS_INT
   WHERE REQUEST_ID = :request_id;

• Reconciling source records to success or failure via INTERFACE_SOURCE_TABLE, INTERFACE_SOURCE_LINE_ID, and SHIP_HEADER_ID.

Related Objects

The documented foreign key relationship is limited, but the following objects are significant in typical integration and processing flows:

• FV_LEGAL_ENTITIES — referenced through LEGAL_ENTITY_ID; the only documented foreign key dependency.
• INL_SHIP_LINES_INT — companion interface table holding the shipment line-level rows associated with each shipment header row.
• The LCM Open Interface Processor concurrent program — the process that consumes INL_SHIP_HEADERS_INT rows, honors LAST_TASK_CODE, and drives PROCESSING_STATUS_CODE.
• Destination LCM shipment header tables — linked through SHIP_HEADER_ID after successful processing.
• FND_USER — the standard reference for the WHO columns CREATED_BY and LAST_UPDATED_BY.
• FND_CONCURRENT_REQUESTS — used to resolve REQUEST_ID and correlate interface runs.
• Receiving-related interface logic governed by RCV_ENABLED_FLAG.

Because the row-level foreign keys are sparse, joins to the preceding objects are most reliably performed on the documented surrogate key SHIP_HEADER_INT_ID, the interface GROUP_ID, or the source identifiers embedded in the interface columns.