Search Results ship_confirm

Overview

The APPS.WSH_ITM_PKG package body is a shipping-execution integration component within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its business purpose is to bridge Oracle Shipping Execution (WSH) with the Integration and Transaction Management (ITM) framework used for export-compliance screening. When a shipment or pick-release is processed, Oracle Shipping can submit a compliance-screening request to an external partner application (for example, a restricted-party or denied-party list service). Once the partner returns a response, an inbound callback is required to reconcile that response against the original request and to advance the delivery or pick-release accordingly. WSH_ITM_PKG implements that callback logic, performing the post-processing operations that depend on the outcome of screening.

The package declares package-level constants that identify its scope unambiguously. The service type is fixed as WSH_EXPORT_COMPLIANCE, and the two business events it services are PICK_RELEASE and SHIP_CONFIRM, associated with the workflow event names oracle.apps.wsh.delivery.itm.responsereceivedatdelcreate and oracle.apps.wsh.delivery.itm.responsereceivedatship respectively. Because the user search term is ship_confirm, the G_SHIP_CONFIRM_EVENT and G_SUB_SHIP_CONFIRM_EXCEPTION constants are the most directly relevant declarations in the specification.

Key Procedures and Functions

ETRM documents a single callable entry point for this package body:

• WSH_ITM_WSH — The callback procedure invoked by the ITM application when a response is received from the partner application, informing Oracle of the status of an export-compliance request. It accepts a request-control identifier that uniquely identifies the request information held in the request control table, together with a request-set identifier retained for ITM standards compliance. The procedure executes the appropriate post-processing operations based on the returned screening status. Although only this procedure is catalogued in the ETRM metadata, the package body additionally defines private helper cursors, including an export-compliance query used to resolve request and rule data by request-control identifier and status.

The package raises named exceptions to signal completion and failure conditions to the calling workflow: WSH_PR_SUB_EXPORT_COMPL for completed pick-release export submissions, WSH_SC_SUB_EXPORT_COMPL for completed ship-confirm export submissions, and WSH_EXPORT_COMPL_FAILED when export compliance processing does not succeed.

Tables Accessed

The package operates against five documented application tables, all accessed through APPS synonyms:

• WSH_ITM_REQUEST_CONTROL — stores the outbound screening request and its control identifier; the input to the callback originates here.
• WSH_ITM_RESPONSE_HEADERS — holds the header-level response returned by the partner application.
• WSH_ITM_RESPONSE_LINES — holds line-level response detail, permitting disposition per delivery or item.
• WSH_ITM_RESPONSE_RULES — contains the screening rules associated with the response, used to determine the resulting compliance outcome.
• WSH_EXCEPTIONS — records exceptions raised during processing, supporting error handling and later diagnosis.

Usage Notes

WSH_ITM_PKG is not intended for direct invocation from Oracle Forms or standard concurrent programs. It is a workflow-driven integration API, called by the ITM application layer when the partner response arrives, and it is registered against the shipping workflow event names listed above so that the correct post-processing path is selected for PICK_RELEASE versus SHIP_CONFIRM. ETRM records zero other packages referencing it, which confirms its role as a terminal integration endpoint rather than a shared utility. Custom code should invoke it only through the ITM callback contract, passing a valid request-control identifier. Because the package persists results into the ITM response and exception tables, retry logic must be idempotent with respect to the request-control identifier to avoid duplicate post-processing.