Search Results delete_ship




Overview
Explore in AI Chat

Overview

APPS.INL_INTERFACE_PVT is a private PL/SQL package within the Oracle E-Business Suite Logistics and Trade Management (formerly Landed Cost Management / International Trade) module. The "PVT" suffix designates it as a private API layer, meaning its procedures are not published for direct external consumption but are instead invoked by the public interface programs and concurrent processes that move trading and shipment data into the EBS transactional schema. The package serves as the inbound interface engine for landed cost and shipment information, handling the validation, transformation, and loading of records staged in the INL_SHIP_LINES_INT interface table.

The package operates against the APPS schema and is classified as VALID under ETRM 12.2.2. Its primary business purpose is to import shipment and match data from external sources—typically EDI feeds, third-party logistics systems, or legacy supply chain applications—and reconcile that data with the internal landed cost and allocation structures. By isolating the import logic in a private package, Oracle maintains a controlled boundary between interface staging tables and the core INL transactional tables.

Key Procedures and Functions

The ETRM metadata documents six entry points, four of which are named procedures:

  • IMPORT_LCMSHIPMENTS — Imports landed cost management shipment records from the INL_SHIP_LINES_INT staging table into the shipment and allocation structures. This procedure validates shipment line data, resolves parties and locations, and creates the corresponding internal shipment representations.
  • IMPORT_LCMMATCHES — Imports landed cost match records, reconciling shipment or receipt data against trade matches. It processes the matching relationships required for landed cost calculation and downstream cost allocation.
  • DELETE_SHIP — Removes shipment records, providing the interface layer with a controlled deletion path for shipments previously imported or staged, ensuring referential integrity with allocations and matches is maintained.
  • RESET_MATCHINT — Resets the match interface state, clearing or reinitializing match interface records so that a matching import cycle can be re-run. This supports reprocessing scenarios where the initial interface load must be reset without corrupting committed data.

The remaining two documented objects are functions or additional entry points within the same package that support the import flow. None of the parameter signatures are published in the metadata; only the procedure names and their business intent are documented.

Tables Accessed

The package references a broad set of APPS synonyms spanning trade, party, currency, and financials data:

The dependency metadata additionally confirms references to FND_API (the standard EBS API error-handling framework) and SYS.STANDARD.

Usage Notes

INL_INTERFACE_PVT is not intended for direct invocation by end users. It is typically called by concurrent programs and public interface packages that orchestrate the landed cost import cycle, such as the shipment and match import concurrent requests. The package is referenced by three other packages within APPS, which act as the public wrappers and scheduling entities.

Developers extending ETRM interfaces should invoke the public calling packages rather than INL_INTERFACE_PVT directly. Because it depends on FND_API, callers should expect standard EBS API error handling, including the FND_API.G_RET_STS_SUCCESS and error message stack conventions. In upgrade or migration projects between 12.1.1 and 12.2.2, the package remains a stable private interface, but its behavior is coupled to the INL interface tables; any changes to INL_SHIP_LINES_INT structure must be reviewed against this package before deployment.