Search Results check_detail




Overview
Explore in AI Chat

Overview

WSH_CONTAINER_GRP is a PL/SQL package body owned by the APPS schema and classified in the ETRM documentation as a Group (GRP) type API within the Oracle E-Business Suite Shipping Execution (WSH) module. It encapsulates the core container-management logic used during the outbound logistics cycle: creating, updating, packing, and manipulating container instances (LPNs and delivery details) associated with deliveries. The package exposes a set of procedural entry points that allow both Oracle's own Shipping forms and external/custom code to drive container operations programmatically rather than through the user interface.

The documented package header carries the revision marker WSHCOGPB.pls 120.7.12020000.2, consistent with the 12.1.1 and 12.2.2 code lines. Standard global constants such as G_PKG_NAME and p_message_type are declared at the top of the body, and all public procedures follow the Oracle Application Object Library (AOL) API conventions: p_api_version, p_init_msg_list, p_commit, p_validation_level, and the standard x_return_status, x_msg_count, and x_msg_data out parameters. This makes the package compatible with the FND_API error-handling and message-stack model used throughout EBS.

Key Procedures and Functions

  • CREATE_CONTAINERS — Creates one or more container instances from a container item definition. The procedure accepts a container item id (key flex identifier) or a concatenated container item name, along with organization and naming parameters such as prefix, suffix, base number, and number of digits, and returns a table of generated container ids (delivery detail ids). The ETRM source comments explicitly state that this procedure is retained only for backward compatibility and should no longer be used by new development.
  • UPDATE_CONTAINER — Modifies attributes of an existing container instance, such as its name or content associations, after creation.
  • AUTO_PACK — Performs automatic packing of delivery details into containers, applying the packing rules and content-item logic defined for the shipping transaction.
  • CONTAINER_ACTIONS — Dispatches container-related actions (for example, pack, unpack, or status transitions) against a container instance, serving as a general action handler for the container workflow.

These four procedures represent the documented public surface of the package. Parameter lists are intentionally omitted where not published in the metadata.

Tables Accessed

  • WSH_DELIVERY_DETAILS — Stores the delivery detail rows that represent container instances and packed items; the package inserts and updates here when creating or modifying containers.
  • WSH_DELIVERY_ASSIGNMENTS — Links delivery details to deliveries; container creation and packing update this table to associate the new container with the correct delivery.
  • WSH_NEW_DELIVERIES — Holds the delivery header that a container ultimately belongs to; read and referenced during container assignment.
  • PLITBLM — A generic PL/SQL index-by table type used internally to pass collections between procedures and to return out tables of container ids.

Usage Notes

WSH_CONTAINER_GRP is invoked primarily from the Oracle Shipping Execution container and packing forms, and from concurrent programs that perform bulk packing or container generation. The ETRM metadata records that the package is referenced by six other packages inside the EBS codebase, indicating it is reused as a building block by higher-level shipping APIs rather than being called directly by end users.

Custom development referencing the check_detail search term should note that, per the source comments, CREATE_CONTAINERS is deprecated and retained only for backward compatibility; new integrations should prefer the more current container APIs surfaced through the Shipping public interfaces. All calls should honour the standard API contract by supplying a valid p_api_version and inspecting x_return_status before assuming success. Because the package writes to delivery and assignment tables, callers should manage transaction boundaries with p_commit and be aware of the locking behaviour inherent in concurrent container operations.