Results for “document_sub_type”

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

Overview

INL_SHIP_HEADERS_INT is an Oracle E-Business Suite interface (staging) table that resides in the INL schema, the owner of the Oracle Landed Cost Management (LCM) module. Its documented purpose is to store Open Interface data for shipment headers. In practical terms, the table functions as the inbound gateway through which shipment header information from external or upstream sources — typically Oracle Purchasing, Receiving, or third-party logistics feeds — is collected, validated, and then processed into the permanent Landed Cost Management shipment tables.

Under the heuristic Data Vault classification derived from the mined foreign key structure, the table is modeled as standalone. This reflects the sparse relationship footprint: a single documented foreign key from LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES, with no other parent references. Because the interface table captures time-stamped, mutable load state (validation flags, processing status, request identifiers), it behaves functionally like a satellite rather than a true hub, but the classification should be treated as a modeling suggestion rather than a definitive design label.

Key Information Stored

The documented physical schema for 12.2.2 includes 49 columns. The critical columns fall into several logical groups:

• Primary surrogate key: SHIP_HEADER_INT_ID, which is also the sole documented unique index candidate (INL_SHIP_HEADERS_INT_U1). This is the interface's internal row identifier, not a business key derived from the source system.
• Interface identity and traceability: INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_TABLE, and INTERFACE_SOURCE_LINE_ID identify the originating system and row; GROUP_ID batches related records; TRANSACTION_TYPE distinguishes insert versus update processing.
• Processing control: PROCESSING_STATUS_CODE, VALIDATION_FLAG, LAST_TASK_CODE, and RCV_ENABLED_FLAG determine whether a row is ready, in error, or successfully transformed. REQUEST_ID and PROGRAM_ID tie each batch to its concurrent program run.
• Shipment business attributes: SHIP_NUM and SHIP_DATE describe the shipment; SHIP_TYPE_ID and SHIP_TYPE_CODE classify it; LEGAL_ENTITY_ID and LEGAL_ENTITY_NAME identify the incurring legal entity.
• Inventory and location context: ORGANIZATION_ID, ORGANIZATION_CODE, LOCATION_ID, LOCATION_CODE, and ORG_ID pinpoint the receiving organization and shipment location; TAXATION_COUNTRY and DOCUMENT_SUB_TYPE support landed cost tax determination.
• Audit columns: the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus the fifteen ATTRIBUTE1–15 flexfield slots for client extensions.

Common Use Cases and Queries

The primary operational use is monitoring the LCM open interface. A typical validation query lists unprocessed or failed rows:

• Reporting on outstanding interface records: SELECT ship_header_int_id, ship_num, organization_code, processing_status_code, validation_flag FROM inl_ship_headers_int WHERE processing_status_code IS NULL OR validation_flag = 'E';
• Batching by load run: SELECT group_id, request_id, COUNT(*) FROM inl_ship_headers_int GROUP BY group_id, request_id;
• Resolution of errors typically involves correcting source attributes, resetting VALIDATION_FLAG and PROCESSING_STATUS_CODE, and re-submitting the Landed Cost Management interface concurrent program.
• Reconciliation reporting joins INTERFACE_SOURCE_LINE_ID back to the originating PO or receipt for end-to-end landed cost traceability.

Related Objects

Only one foreign key is documented, but the interface participates in a broader processing chain:

• FV_LEGAL_ENTITIES — referenced via LEGAL_ENTITY_ID; supplies legal entity validation for each staged shipment header.
• INL_SHIP_LINES_INT — the companion line-level interface, joined on GROUP_ID or SHIP_HEADER_INT_ID, holding shipment line detail.
• INL_SHIP_HEADERS / INL_SHIP_LINES — the destination base tables populated by the LCM open interface processor.
• RCV_SHIPMENT_HEADERS — the Receiving source of shipment data, tracked through INTERFACE_SOURCE_TABLE and INTERFACE_SOURCE_LINE_ID when RCV_ENABLED_FLAG is set.
• PO_HEADERS_ALL / PO_LINES_ALL — Purchasing documents often referenced as the ultimate origin of inbound shipment data.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the interface program execution that loaded each batch.

Together these objects allow the LCM interface to ingest, validate, and post shipment headers into the landed cost costing engine.