Results for “inl_ship_headers_all”

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

Overview

The INL.INL_SHIP_HEADERS_ALL table is a core transactional object within Oracle Landed Cost Management (INL), a module of Oracle E-Business Suite available in releases 12.1.1 and 12.2.2. It stores header-level information for shipments that are subject to landed cost processing. Each row in this table represents a single shipment header — the parent record that groups the shipment lines, charges, adjustments, and cost allocations used to compute the true landed cost of received or in-transit goods.

Landed Cost Management consumes shipment data originating from receiving, inventory, and purchasing activities so that freight, duty, insurance, and other charges can be apportioned to items and ultimately reflected in inventory valuation. The shipment header is the anchor for that computation, and INL_SHIP_HEADERS_ALL is therefore central to the module's integration with Oracle Receiving (RCV), Oracle Inventory (INV), and Oracle Purchasing (PO).

The heuristic Data Vault classification mined from the foreign-key structure labels this object as standalone. As a modeling suggestion, this reflects that the table sits at the center of its own reference structure rather than functioning purely as a hub, link, or satellite in a strict Data Vault sense. Its single documented outbound relationship, via LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES, supports the multi-organization, legal-entity-aware design typical of EBS tables.

Key Information Stored

The table contains 45 documented columns. The most significant are:

• SHIP_HEADER_ID — The surrogate primary key, enforced by the unique index INL_SHIP_HEADERS_ALL_U1. It uniquely identifies each shipment header record.
• SHIP_NUM and ORGANIZATION_ID — Together they form the business-key candidate enforced by unique index INL_SHIP_HEADERS_ALL_U2. SHIP_NUM is the user-visible shipment number, and ORGANIZATION_ID scopes it to an inventory organization.
• SHIP_DATE — The date associated with the shipment, used for period and cost-accounting determinations.
• SHIP_TYPE_ID — Identifies the shipment type, driving processing behavior.
• SHIP_STATUS_CODE — Tracks the lifecycle state of the shipment header (for example, new, matched, or closed).
• LEGAL_ENTITY_ID — The owning legal entity, referenced by a foreign key to FV_LEGAL_ENTITIES. It governs tax and accounting treatment.
• LOCATION_ID and ORG_ID — Supply the physical location and the operating unit context for the shipment.
• PENDING_MATCHING_FLAG and PENDING_UPDATE_FLAG — Indicators that the header still requires matching or update processing, frequently used by concurrent programs to select eligible records.
• RCV_ENABLED_FLAG — Flags whether the shipment is enabled for receiving integration.
• INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_TABLE, and INTERFACE_SOURCE_LINE_ID — Trace the origin of imported shipment data back to its source.
• SIMULATION_ID — Associates a shipment with a what-if landed cost simulation rather than a committed run.
• TAXATION_COUNTRY and DOCUMENT_SUB_TYPE — Support tax determination and document classification.
• ADJUSTMENT_NUM — Tracks adjustment processing against the header.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent program context columns (PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID) record who created and last changed each row and through which process, while the fifteen ATTRIBUTE columns provide configurable descriptive flexibility.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying shipments awaiting cost matching, reconciling shipment data against received purchase orders, and auditing landed cost runs by legal entity or organization. A representative query to find open headers is:

• SELECT ship_num, ship_date, ship_status_code FROM inl_ship_headers_all WHERE pending_matching_flag = 'Y' AND organization_id = :org_id;
• SELECT h.ship_num, h.ship_date, l.legal_entity_name FROM inl_ship_headers_all h, fv_legal_entities l WHERE h.legal_entity_id = l.legal_entity_id;
• SELECT ship_header_id, ship_num FROM inl_ship_headers_all WHERE organization_id = :org AND ship_num = :num; — resolving a header through the U2 business key.

These patterns support landed cost reconciliation reports, period-close validation, and integration troubleshooting.

Related Objects

• FV_LEGAL_ENTITIES — Referenced through LEGAL_ENTITY_ID; the principal documented foreign-key relationship for the header.
• INL_SHIP_LINES_ALL — Child table holding shipment line detail, joined on SHIP_HEADER_ID.
• INL_SHIP_CHARGES_ALL — Stores charge lines associated with the header.
• INL_SHIP_COST_ALLOCS — Holds the allocated landed cost results driven by the header.
• INL_SHIP_HEADERS_INT (interface/staging) — Populates this table through the INTERFACE_SOURCE_* columns and SHIP_HEADER_INT_ID.
• RCV_SHIPMENT_HEADERS / RCV_TRANSACTIONS — Oracle Receiving sources linked through the RCV_ENABLED_FLAG and source reference columns.
• MTL_SYSTEM_ITEMS_B and MTL_PARAMETERS — Provide organizational and item context for downstream cost computation.