Search Results inl_ship_headers_all_s

Overview

APPS.INL_SIMULATION_PVT is the private implementation package body behind the Oracle E-Business Suite Trade Management (formerly ETRM) simulation engine. Its purpose is to create, copy, and purge simulation scenarios against landed cost, shipment, association, tax, and charge data without disturbing the live transactional records that those simulations model. Simulations allow logistics and trade compliance users to evaluate "what-if" scenarios — alternative shipment structures, association assignments, tax treatments, and charge calculations — before committing the modeled changes to production data.

The package is classified as a PVT (private) API, meaning it is not intended as a public integration surface. It is invoked internally by INL_SIMULATION_PUB and other trade management components, and it carries the standard ETRM dependency footprint on FND_API, FND_MSG_PUB, FND_MESSAGE, and FND_GLOBAL for the Oracle Applications error-handling and message-stack conventions, plus DBMS_LOCK for concurrency control over simulation processing.

Key Procedures and Functions

• CREATE_SIMULATION — Establishes a new simulation record and populates the simulation tables with the appropriate snapshot of shipment, association, tax, and charge data. This is the entry point for generating a scenario from current or specified transactional input.
• COPY_SIMULATION — Duplicates an existing simulation into a new scenario, allowing users to iterate on a prior what-if analysis without rebuilding it from source data. It propagates the underlying simulation detail rows across the various _S shadow tables.
• PURGE_SIMULATIONS — Removes simulation records and their dependent detail rows when scenarios are obsolete. This maintains table volume in the simulation-side tables and prevents stale data from accumulating.

Tables Accessed

The package operates across a matched pair of live and simulation ("_S") tables. It reads and writes INL_SIMULATIONS and INL_SIMULATIONS_S for the scenario header, INL_ASSOCIATIONS and INL_ASSOCIATIONS_S for association (trade agreement/qualifier) data, INL_CHARGE_LINES and INL_CHARGE_LINES_S for calculated charge lines, and INL_TAX_LINES and INL_TAX_LINES_S for tax determinations. Shipment-related structures are handled through INL_SHIP_HEADERS, INL_SHIP_HEADERS_ALL, INL_SHIP_HEADERS_ALL_S, INL_SHIP_LINES_ALL, INL_SHIP_LINES_ALL_S, INL_SHIP_LINE_GROUPS, and INL_SHIP_LINE_GROUPS_S, which supply the logistics context being simulated. The package also references PO_HEADERS_ALL and PO_RELEASES_ALL to anchor simulated landed cost and receipt activity to the corresponding purchasing documents.

The constant reference to INL_ASSOCIATIONS_S — the object the user searched for — reflects that association simulation is a core function: the package clones association definitions into the shadow table so that alternate qualifier or association-combination scenarios can be evaluated in isolation.

Usage Notes

Because INL_SIMULATION_PVT is a private package, it is not called directly from concurrent program registration or from customer extensions. It is normally reached through the public simulation API or through the Trade Management simulation user interface. Custom code that requires simulation behavior should call the supported public wrapper rather than this body, since private signatures may change between 12.1.1 and 12.2.2 without notice. When troubleshooting simulation issues, DBAs typically inspect the _S tables listed above and check FND_MSG_PUB message stacks, since errors are raised through the standard EBS API error-handling pattern. The documented dependency list records that this package is referenced by three other packages and references INL_CUSTOM_PUB, INL_INTERFACE_PVT, and INL_LOGGING_PVT, indicating that simulation creation integrates with custom extension hooks and interface logging.