Search Results xnp_sync_registration_s

Overview

The APPS.XNP_WF_SYNC package body is a core synchronization component within the Oracle E-Business Suite supply chain execution stack, operating primarily in the context of Warehouse Management and the Logistics/Order Fulfillment modules. In Oracle EBS 12.1.1 and 12.2.2, the XNP prefix denotes objects belonging to the performance and synchronization infrastructure that coordinates outbound logistics activities—specifically the messaging layer that keeps the Workflow engine, the mobile/device layer, and the order-line processing engine in agreement. The package manages the lifecycle of synchronization registrations, tracks which records are candidates for the synchronization window, and controls the timer-driven polling that determines when a synchronization pass begins and ends. It also centralizes error handling for the synchronization subsystem, ensuring failures raised by device or workflow callbacks are captured consistently rather than propagated as unhandled exceptions.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions in this package body. SYNC_REGISTER is the entry point that creates or updates a synchronization registration, the record that marks an entity as participating in the sync cycle. RESET_SYNC_REGISTER clears that registration state so a fresh cycle can begin. PROCESS_SYNC performs the principal synchronization work against the registered records, while SYNCHRONIZE provides the higher-level orchestration wrapper around a sync pass. IS_LAST_SYNC is a predicate used to detect whether the current pass represents the final synchronization, a condition that governs cleanup and completion signalling. PROCESS_SYNC_TIMER drives the timer-based scheduling logic that invokes synchronization at defined intervals. RAISE_SYNC_ERROR and PROCESS_SYNC_ERR provide the paired error-raising and error-processing handlers for the subsystem. SET_RESULT_CODE records a completion or status code against the synchronization run. SYNCNOTIF raises or manages the workflow notification associated with synchronization outcomes.

Tables Accessed

The package reads and writes the APPS synonyms XNP_SYNC_REGISTRATION and XNP_SYNC_REGISTRATION_S, which hold the registration header and its synchronization state respectively; these are central to SYNC_REGISTER and RESET_SYNC_REGISTER. WF_NOTIFICATION_ATTRIBUTES is accessed so workflow notification attributes can be populated when SYNCNOTIF dispatches a message. XDP_ORDER_LINE_ITEMS supplies the order-line detail being synchronized, linking the workflow layer to the fulfillment engine. DUAL is used for singleton lookups and function-style evaluation.

Usage Notes

XNP_WF_SYNC is not referenced by any database object, confirming it is invoked at the application tier rather than through database triggers or views. It is typically called from Warehouse Management concurrent programs, from the OAF/Forms layer during outbound logistics transactions, and from Workflow background processes. Because the package depends on XNP_SYNC_REGISTRATION_S, the sequence searched by the user, callers should not manipulate registration state directly; SYNC_REGISTER and RESET_SYNC_REGISTER must be used to keep the sequence and registration table consistent. Custom code extending synchronization should route error handling through RAISE_SYNC_ERROR and PROCESS_SYNC_ERR to preserve the standard error and result-code semantics.