Search Results call_custom_api

Overview

The APPS.WSH_ITM_POST_PROCESS_HANDLER package body is a component of the Oracle E-Business Suite Shipping Execution (WSH) module, specifically within the In-Transit Inventory Management (ITM) subsystem. Its principal business function is to coordinate post-processing activities that occur after a request has been submitted, either synchronously through Java-based ITM code or asynchronously through the XML Gateway (ECX) in the Advanced Supply Chain Planning and Order Management integration flows. The package determines whether outstanding requests remain to be processed within a given request set and, when appropriate, dispatches a custom API to complete the workflow. It is a critical orchestration layer that ensures all child requests in a request set reach a terminal processing state before downstream logic is triggered.

Key Procedures and Functions

• CHECK_PENDING_CALL_API — Performs the primary decision logic of the package. It accepts identifiers for the request control, request set, and application, along with a p_source flag indicating the invocation origin. The p_source parameter distinguishes between ECX (XML Gateway asynchronous mode) and ITM (ITM Java code synchronous mode). The procedure queries the WSH_ITM_REQUEST_CONTROL table to count records where the process flag indicates outstanding work. If no pending requests remain, it logs a diagnostic message through the WSH debug utilities and invokes CALL_CUSTOM_API to continue processing.
• CALL_CUSTOM_API — Invoked internally by CHECK_PENDING_CALL_API once all requests in a set have completed. It serves as the extension point where customer-specific or downstream business logic is executed for the completed request set. Its documented purpose is to carry forward the request set and application context to the custom API layer.

Both procedures are exposed with an OTHER API classification in the ETRM, indicating they are not classified as standard open interfaces but are called from within the WSH processing chain. The package relies on WSH_DEBUG_INTERFACE and WSH_DEBUG_SV for conditional diagnostic logging governed by the l_debug_on flag.

Tables Accessed

• WSH_ITM_REQUEST_CONTROL — The central operational table. CHECK_PENDING_CALL_API reads REQUEST_CONTROL_ID, REQUEST_SET_ID, and PROCESS_FLAG to determine whether any request in the set remains unprocessed. A count of zero pending rows signals readiness for the custom API call.
• FND_APPLICATION — Referenced to resolve application context, typically for validation or logging of the calling application.
• UTL_FILE — Used indirectly for file-based logging or output in the post-processing flow.

Usage Notes

This package is typically invoked from the WSH ITM concurrent program chain or directly by the ITM Java layer rather than from a standard Oracle Forms-based UI. In synchronous mode the caller passes p_source = 'ITM', while asynchronous XML Gateway submissions pass ECX. The ETRM records that this package is referenced by one other package, confirming it operates as an internal utility rather than a public entry point. Because the p_source parameter drives debug behavior and processing context, integrators customizing ITM post-processing should preserve its expected values and extend only the CALL_CUSTOM_API logic.