Results for “get_crossdock_criteria”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.WMS_XDOCK_CUSTOM_APIS_PUB is a public PL/SQL package in the Oracle Warehouse Management (WMS) module that exposes extension points for Oracle's crossdocking engine. Crossdocking moves inbound or in-transit material directly to outbound demand without intermediate putaway, and the WMS planned crossdocking process relies on a rules engine to determine a valid crossdock criteria for each Warehouse Distribution Demand (WDD) demand line. This package allows customers and integrators to replace or supplement that rules-based determination with custom logic. Its most significant documented component, GET_CROSSDOCK_CRITERIA, is invoked in lieu of the rules engine in the pegging logic during planned crossdocking. The package also declares a package-level constant, g_allow_partial_wip_xdock, set to 'N', which indicates whether a demand can be fulfilled through supplies of type WIP combined with other non-Inventory supply types; per the inline documentation this applies only to Order Entry demand lines, since WIP demand lines represent backordered component demand for which crossdock reservations are not created. The package header additionally carries a version stamp of 120.2 dated 2005, indicating it is a long-standing, stable public API surface in the EBS stack for releases including 12.1.1 and 12.2.2.

Key Procedures and Functions

• GET_CROSSDOCK_CRITERIA — Defines a custom method of determining a valid crossdock criteria to return for a given WDD demand line during Planned Crossdocking. It is called in lieu of the rules engine in the pegging logic. The output is expected to be a valid crossdock criteria ID of type 'Planned'. The input includes the WDD demand line record (p_wdd_release_record), which carries relevant attributes such as organization, item, customer ID, project, and task. The output parameter x_return_status follows standard FND_API conventions (g_ret_sts_success, g_ret_sts_error, g_ret_sts_unexp_error). The flag x_api_is_implemented controls behavior: when TRUE, the value in x_crossdock_criteria_id is used, and a NULL value means no crossdock criteria could be determined so the demand line is not crossdocked; when FALSE, the pegging logic falls back to the rules engine.
• GET_EXPECTED_TIME — Returns an expected time value used by the crossdocking logic, typically supporting timing or scheduling decisions during planned crossdock evaluation.
• GET_EXPECTED_DELIVERY_TIME — Returns the expected delivery time associated with a demand or supply consideration, supporting lead-time and feasibility assessment in crossdock pegging.
• SORT_SUPPLY_LINES — Provides custom ordering of supply lines so that the crossdocking engine evaluates candidate supplies in a caller-defined sequence.
• SORT_DEMAND_LINES — Provides custom ordering of demand lines, allowing prioritization of demand during crossdock matching.

Tables Accessed

The ETRM metadata for this package does not enumerate base tables referenced through APPS synonyms. Functionally, the package operates on Warehouse Distribution Demand (WDD) demand line records, which are passed into GET_CROSSDOCK_CRITERIA as a record structure rather than queried directly by the API signature. The custom logic a customer implements inside these extension points would typically read WMS and Inventory crossdock criteria and reservation data (for example, crossdock criteria definitions and supply/demand staging tables used by the planned crossdocking pegging process) to derive and return a valid 'Planned' crossdock criteria ID. Because these reads occur in customer-written bodies, no documented table list is provided by the package header itself.

Usage Notes

This package is an extension hook, not a program invoked directly by end users. It is called by the WMS planned crossdocking pegging logic when custom crossdock criteria determination is enabled, and its return flags determine whether the custom result is honored or the standard rules engine is used instead. The package is documented as referenced by one other package within the EBS schema, consistent with its role as a called API rather than a top-level entry point. Implementers extend the behavior by supplying a custom implementation of the documented procedures — most commonly GET_CROSSDOCK_CRITERIA — and by observing the x_api_is_implemented and x_crossdock_criteria_id contract so that returning NULL or setting the flag to FALSE cleanly falls back to the seeded rules engine without breaking pegging. The package is relevant across Oracle EBS 12.1.1 and 12.2.2, and any custom code should be validated against both releases because crossdocking pegging behavior and the surrounding WMS schema can differ between them.