Search Results wsh_bulk_process_grp




Overview
Explore in AI Chat

Overview

WSH_BULK_PROCESS_GRP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports bulk processing operations within the Oracle Shipping Execution (WSH) module. Its role is to consolidate the creation and maintenance of delivery details when shipments are processed in bulk, rather than through the standard single-record Shipping Transactions form. The "GRP" suffix in the package name follows Oracle EBS naming conventions and indicates that this is a group or utility package exposing higher-level, composite operations that orchestrate calls into the lower-level WSH and Order Management (OE) application programming interfaces (APIs).

The package is part of the shipping execution stack and works closely with companion packages such as OE_WSH_BULK_GRP, WSH_BULK_TYPES_GRP, and OE_SHIPPING_INTEGRATION_PVT. Together these components allow batch shipments and delivery detail records to be assembled, validated, and persisted without repeated interactive form activity. The object is documented as VALID in the ETRM metadata for release 12.2.2, and the same package exists in 12.1.1.

Key Procedures and Functions

The ETRM metadata documents a single entry point in this package:

  • CREATE_UPDATE_DELIVERY_DETAILS — A procedure whose purpose is to create new delivery detail records and update existing ones as part of a bulk delivery processing operation. In a typical flow, it receives a collection or table of detail attributes representing shipped or staged quantities and then inserts or modifies the corresponding rows in the shipping delivery detail structures. Parameter lists are intentionally not enumerated here; the procedure is understood through its business intent rather than a fixed signature, since the metadata exposes only its name and role.

The package relies on the WSH_BULK_TYPES_GRP package to supply the underlying record and collection types used to pass detail data, and it delegates lower-level validation and persistence work to OE_WSH_BULK_GRP.

Tables Accessed

The ETRM metadata for this object does not enumerate specific base tables. Instead it lists the SYNONYM- and package-level dependencies that define the data context: APPS.OE_WSH_BULK_GRP, APPS.WSH_BULK_TYPES_GRP, and SYS.STANDARD. Through OE_WSH_BULK_GRP and its own logic, CREATE_UPDATE_DELIVERY_DETAILS operates on the core shipping delivery detail tables, principally WSH_DELIVERY_DETAILS, along with associated delivery assignment and line detail tables. Because no explicit table list is documented, the precise set of tables should be confirmed by viewing the package body, but the intent is clearly the persistence and refresh of delivery detail rows for existing and newly formed deliveries.

Usage Notes

WSH_BULK_PROCESS_GRP is not intended for direct end-user invocation. It is referenced by two other packages, OE_SHIPPING_INTEGRATION_PVT and PO_DELREC_PVT, both of which act as callers. OE_SHIPPING_INTEGRATION_PVT is the integration point used by Order Management to push order lines into shipping, while PO_DELREC_PVT relates to purchasing delivery record processing. This dependency pattern indicates the package is invoked programmatically during order-to-shipment integration and purchasing receiving flows, not from a dedicated Shipping Transactions form.

Typical invocation paths include concurrent programs and integration APIs that build bulk shipment requests, custom extensions that need to create or amend delivery details in volume, and internal WSH processing that turns staged order lines into delivery details. When using this package in custom code, callers should always work through the documented CREATE_UPDATE_DELIVERY_DETAILS entry point, supply data using the types defined in WSH_BULK_TYPES_GRP, and avoid direct DML against WSH_DELIVERY_DETAILS, since that bypasses the validation and synchronization logic the package provides. Because the ETRM metadata for this release is limited, developers should review the package specification and body in the target instance before deriving a signature or committing to a parameter contract.