Search Results inl_ship_headers_all




Overview
Explore in AI Chat

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:

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