Search Results find_exception

Overview

The APPS.WMS_XDOCK_EXCEPTION package is a PL/SQL API belonging to the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite. Its name reflects its business purpose: the identification and surfacing of cross-docking exceptions within warehouse operations. Cross-docking is the practice of moving inbound goods directly to outbound staging or shipping without long-term putaway into storage, and it depends on accurate, timely matching of inbound supply against outbound demand. Exceptions arise when that matching fails or is at risk — for example, when expected inbound stock that was intended for cross-docking cannot satisfy a pending outbound reservation within the planning horizon.

In the ETRM metadata classification, this package is registered as an OTHER API under the APPS schema, meaning it is a supporting utility rather than a public, fully versioned interface. It contains a single documented entry point, indicating a narrowly scoped, single-purpose routine. The package is available in both Oracle EBS 12.1.1 and 12.2.2, with the header comment indicating a source revision dated 2005, consistent with the long-standing WMS codebase lineage that predates the 12.2 online patching architecture.

Key Procedures and Functions

The package exposes one documented procedure:

• FIND_EXCEPTION — The sole documented entry point. Its purpose is to detect and report cross-docking exceptions for a given operating unit and planning window. Based on the documented parameter list, it accepts an organization identifier and a look-ahead time, which together bound the scope of the exception search: the organization defines the warehouse context, and the look-ahead time defines how far into the future the routine examines demand and supply. It returns standard concurrent-program style output parameters (error buffer and return code), which strongly indicates it is designed to run as a concurrent program or be invoked from a host environment where structured status feedback is required.

No other procedures or functions are documented in the ETRM metadata for this package. The single-procedure design reflects a focused responsibility: evaluating cross-dock eligibility and flagging deviations rather than performing transactional cross-dock execution.

Tables Accessed

The ETRM metadata documents two tables referenced through APPS synonyms:

• MTL_RESERVATIONS — The core inventory reservation table. FIND_EXCEPTION reads reservation records to determine which outbound demand is awaiting supply and whether cross-dock-eligible material is committed against it. Discrepancies between reserved demand and available inbound supply form the substance of the exceptions the routine reports.
• WMS_CROSSDOCK_CRITERIA — The configuration table that defines the rules under which items, orders, or order lines qualify for cross-docking. The procedure consults these criteria to distinguish genuine cross-dock exceptions from ordinary replenishment or putaway activity.

Both tables are read; the metadata does not indicate that the package performs writes. This read-only behavior is consistent with an exception-detection utility whose output is diagnostic rather than transactional.

Usage Notes

WMS_XDOCK_EXCEPTION is typically invoked as a concurrent program, given the error-buffer and return-code output signature, and appears in the WMS concurrent program landscape where warehouse supervisors schedule periodic exception review. It may also be called from custom PL/SQL or wrapper concurrent programs that require programmatic detection of cross-dock exceptions. The metadata records that the package is referenced by zero other packages, indicating it is not a dependency of standard Oracle code and is instead invoked directly by scheduled jobs or user-defined extensions.

Because the package is classified as OTHER rather than a public API, implementers should treat it as non-versioned and subject to change across releases. Any custom integration should validate behavior against the specific target release (12.1.1 or 12.2.2) and avoid assuming a stable signature beyond the documented FIND_EXCEPTION entry point.