Search Results inl_ship_holds_s

Overview

INL_SHIPMENT_PVT is the private application programming interface for shipment processing within Oracle E-Business Suite's Landed Cost Management (LCM) module. The package encapsulates the core business logic required to create, validate, adjust, complete, and reconcile landed cost shipments, which represent the movement of goods against which landed cost charges, taxes, and allocations are calculated. As a PVT-classified API, it is not intended for direct invocation by external consumers; instead it serves as the internal execution engine behind the public LCM APIs and the Landed Cost Management user interface. The package exhibits a status of VALID in the APPS schema and is not referenced by any other database object, confirming its role as a procedural endpoint whose behavior is exposed through forms and concurrent processes rather than through inbound dependency calls. It is referenced by four other packages, which orchestrate its procedures in support of higher-level landed cost workflows.

Key Procedures and Functions

The documented API surface comprises 25 procedures and functions organized around the shipment lifecycle:

• VALIDATE_SHIPMENT, VALIDATE_INVOPENPERIOD, SET_TOREVALIDATE — Perform shipment integrity checks, confirm that the inventory open period permits the associated transactions, and flag shipment records for revalidation when upstream data changes.
• ADJUST_SHIPLINES, ADJUST_CHARGELINES, ADJUST_TAXLINES, ADJUST_LINES — Apply quantity and amount adjustments across shipment lines, charge lines, and tax lines, with ADJUST_LINES acting as the consolidated driver across all three line categories.
• GET_1ARY2ARYQTY, GET_SRCAVAILABLEQTY, GET_1ARYQTY — Quantity retrieval utilities that derive primary and secondary unit-of-measure quantities and determine the quantity available at the source for allocation and adjustment purposes.
• PROCESSACTION, COMPLETE_SHIPMENT, COMPLETE_PENDINGSHIPMENT, UPDATE_PENDINGMATCHINGFLAG — Drive shipment completion, including processing of pending shipments and maintenance of the matching flag that gates downstream invoice matching.
• CHECK_POTOLERANCES, CHECK_POPRICETOLERANCE — Evaluate purchase order quantity and price tolerances to determine whether a shipment may proceed to completion or matching.
• GET_MATCHEDAMT, GET_LASTUPDATEDATEFORSHIP — Return matched amounts and the most recent update timestamp for a shipment, supporting reconciliation and audit reporting.
• DELETE_CHARGEASSOC, DISCARD_UPDATES — Remove charge associations and roll back uncommitted shipment updates.

Tables Accessed

The package operates primarily against the INL schema family. INL_SHIP_HEADERS and INL_SHIP_HEADERS_ALL hold shipment header records, while INL_SHIP_LINES, INL_SHIP_LINES_ALL, and INL_SHIP_LINES_ALL_S store line-level detail and its translation/audit shadow. INL_SHIP_HOLDS and INL_SHIP_HOLDS_S — the table named in the originating search term "inl_ship_holds_s" — record holds applied to shipments; INL_SHIPMENT_PVT reads and writes these to enforce hold release logic during validation and completion. INL_CHARGE_LINES and INL_CHARGE_LINES_S support charge adjustments; INL_TAX_LINES and INL_TAX_LINES_S support tax adjustments; and INL_ALLOCATIONS, INL_ASSOCIATIONS, and INL_ASSOCIATIONS_S underpin allocation and association processing. INL_MATCHES and INL_MATCH_AMOUNTS supply matched amount data for the GET_MATCHEDAMT routine, while INL_PARAMETERS provides system configuration values governing tolerance and validation behavior. The package also reaches into Oracle Purchasing (PO_LINE_LOCATIONS, PO_LINE_LOCATIONS_ALL, PO_DATES_S, PO_UOM_S), Receiving (RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, RCV_TRANSACTIONS_INTERFACE, RCV_QUANTITIES_S, RCV_PARAMETERS, RCV_INVOICE_MATCHING_SV), Inventory (MTL_SYSTEM_ITEMS_VL, MTL_UNITS_OF_MEASURE, ORG_ORGANIZATION_DEFINITIONS), and General Ledger (GL_SETS_OF_BOOKS, HR_LOCATIONS) to resolve item, organization, currency, and location context.

Usage Notes

Because INL_SHIPMENT_PVT is a private (PVT) package, it should not be called directly from custom code; Oracle does not guarantee backward compatibility for private APIs across patches or upgrades. Invocation occurs through the Landed Cost Management forms, which call the package when users create shipments, adjust charges, apply or release holds, or complete shipments, and through LCM concurrent programs that process pending shipments and refresh matching flags in batch. The dependency chain into INL_LANDEDCOST_PVT, INL_TAX_PVT, and INL_LOGGING_PVT indicates that shipment processing is nested within broader landed cost calculation and logging flows. Custom extensions requiring shipment behavior should be built on the public LCM APIs or on interface tables, with INL_SHIPMENT_PVT treated strictly as an internal implementation detail. The package is valid and active in both EBS 12.1.1 and 12.2.2; in 12.2.x it remains part of the APPS schema and continues to be referenced by the same four dependent packages.