Results for “wsh_delivery_autocreate”

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

Overview

WSH_DELIVERY_AUTOCREATE is a PL/SQL package in the APPS schema that drives the automatic creation of Oracle Shipping execution deliveries from eligible order, trip, and inventory data. Its central purpose is to consolidate delivery details into new or existing deliveries according to grouping rules, matching attributes, and scheduling constraints, thereby removing the need for manual delivery assembly in high-volume fulfillment operations. The package is classified as an OTHER API in the ETRM documentation for 12.1.1 and 12.2.2 and holds a VALID status, confirming it is a supported and active component of the shipping module.

Functionally, WSH_DELIVERY_AUTOCREATE sits at the intersection of order management, inventory, and transportation. It evaluates candidate delivery details, determines whether their requested and scheduled dates align, computes grouping hashes, and either assigns them to matching deliveries or creates new deliveries as required. It also performs housekeeping by deleting empty deliveries and unassigning obsolete containers. The package is referenced by twenty-three other packages, underscoring its role as a foundational utility within the WSH product family.

Key Procedures and Functions

The documented interface exposes twelve procedures and functions, each supporting a distinct phase of the auto-create lifecycle:

• CHECK_SCH_DATE_MATCH and CHECK_REQ_DATE_MATCH — validate whether scheduled dates and requested dates, respectively, match across candidate records so that only compliant details are grouped together.
• AUTOCREATE_DELIVERIES — the primary driver that creates deliveries from qualifying delivery details.
• AUTOCREATE_DEL_ACROSS_ORGS — extends auto-create processing across multiple inventory organizations, enabling cross-org consolidation.
• AUTOCREATE_CONSOL_DELIVERY — handles consolidated delivery creation, grouping details that share consolidation criteria.
• DELETE_EMPTY_DELIVERIES — removes deliveries that contain no remaining details, preventing orphaned records.
• UNASSIGN_EMPTY_CONTAINERS — detaches containers that no longer hold assigned content.
• GET_GROUP_BY_ATTR — retrieves the grouping attributes used to determine which details belong together.
• CREATE_HASH and CREATE_UPDATE_HASH — generate and refresh hash values that support efficient match-group identification.
• FIND_MATCHING_GROUPS — locates existing match groups for candidate details.
• RESET_WSH_TMP — clears the temporary working table used during processing.

Tables Accessed

The package reads and writes several core shipping tables through APPS synonyms. WSH_DELIVERY_DETAILS provides the source lines evaluated for grouping and assignment, while WSH_NEW_DELIVERIES and WSH_DELIVERY_ASSIGNMENTS hold the deliveries and detail-to-delivery relationships created or updated during processing. WSH_DELIVERY_LEGS and WSH_TRIPS, together with WSH_TRIP_STOPS, support trip and stop-level scheduling context. WSH_MATCH_GROUP_S persists matching-group definitions, and WSH_TMP serves as the transient work area reset by RESET_WSH_TMP. MTL_CLIENT_PARAMETERS supplies client-level configuration. Utility dependencies include DBMS_LOCK and DBMS_UTILITY for concurrency control and diagnostics, DUAL for scalar queries, and PLITBLM for PL/SQL table handling.

Usage Notes

WSH_DELIVERY_AUTOCREATE is typically invoked indirectly rather than called directly by end users. The AutoCreate Deliveries concurrent program, the Shipping Transactions form, and the Pick Release process all rely on this package to assemble deliveries. It is also called by integration flows such as WSH_INTEGRATION and by trip and container actions through WSH_TRIPS_ACTIONS, WSH_CONTAINER_ACTIONS, and WSH_NEW_DELIVERY_ACTIONS — the latter being the object many users locate when searching for wsh_new_delivery_actions. Custom extensions may call the documented procedures directly, but doing so requires careful attention to commit points and locking, since the package uses DBMS_LOCK to serialize concurrent auto-create runs. Because it is referenced by FTE_MLS_WRAPPER, FTE_SOURCE_LINE_CONSOLIDATION, and WMS_CROSS_DOCK_PVT, changes to its behavior can propagate into fulfillment, warehouse management, and cross-dock processes.