Results for “validate_hold_code”

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

Overview

WSH_CONTAINER_UTILITIES is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its API classification is OTHER, indicating that it is an internal utility package rather than a documented public business API, but one that is heavily reused across the Oracle Shipping Execution (WSH) module. The package encapsulates the container and LPN (license plate number) logic used throughout the outbound logistics flow: master container identification, container naming, serial number validation, container counting and estimation, fill percentage calculation, and validation of hold codes and hazard classes.

In Oracle EBS 12.1.1 and 12.2.2 the package remains valid and is central to the containerization feature of Shipping Execution. Physical handling units — pallets, cartons, totes and nested (child) containers — are modeled in the WSH container tables, and WSH_CONTAINER_UTILITIES provides the reusable routines the shipping forms, actions packages and concurrent processes call to manipulate and validate those records. Because it is referenced by ten other packages and one view, changes to it carry broad impact across the shipping module.

Key Procedures and Functions

The ETRM metadata documents 16 procedures and functions, of which the following are recorded:

• GET_MASTER_CONT_ID — returns the identifier of the master (top-level) container associated with a given container or detail context.
• GET_CONT_NAME — retrieves the descriptive name of a container.
• ESTIMATE_DETAIL_CONTAINERS — estimates the number of containers required for delivery detail lines.
• ESTIMATE_MASTER_CONTAINERS — estimates the number of master containers required for a shipment or delivery.
• GET_MASTER_CONT_SERIAL — obtains the serial number of the master container.
• UPDATE_CHILD_CONTAINERS — maintains the parent/child relationship between nested containers, recalculating or reassigning child records.
• VALIDATE_MASTER_SERIAL_NUMBER — validates a supplied master container serial number.
• GET_MASTER_SERIAL_NUMBER — returns the master container serial number.
• IS_EMPTY — determines whether a container is empty, supporting fill and packing logic.
• GET_FILL_PERCENT — calculates the percentage fill of a container based on its contents.
• GET_DELIVERY_STATUS — returns the status of the delivery associated with a container.
• VALIDATE_HOLD_CODE — validates a container hold code against the defined values.
• VALIDATE_HAZARD_CLASS — validates a hazardous material class for container contents.
• VALIDATE_CONTAINER — performs overall container validation.

These routines are predominantly getter, validation and estimation helpers. They do not own the container transaction; instead they supply consistent rules to the calling shipping logic.

Tables Accessed

Through APPS synonyms the package touches the core shipping and inventory tables:

• WSH_CONTAINER_ITEMS — the contents (items and quantities) packed inside containers; drives fill percentage and emptiness checks.
• WSH_DELIVERY_DETAILS — delivery detail lines used in container estimation and detail-level processing.
• WSH_DELIVERY_ASSIGNMENTS — the link between delivery details and deliveries, used to resolve delivery context.
• WSH_NEW_DELIVERIES — header information for deliveries, used by GET_DELIVERY_STATUS.
• MTL_SYSTEM_ITEMS — item master attributes for the container item and its contents.
• WSH_SHIPPING_PARAMETERS — shipping profile/setup values that govern container behavior.

Usage Notes

WSH_CONTAINER_UTILITIES is invoked indirectly rather than as a standalone API. Its documented dependents — WSH_CONTAINER_ACTIONS, WSH_CONTAINER_GRP, WSH_DELIVERY_AUTOCREATE, WSH_DELIVERY_DETAILS_ACTIONS, WSH_DLVB_COMMON_ACTIONS, WSH_NEW_DELIVERY_ACTIONS, WSH_TPA_CONTAINER_PKG, WSH_TP_RELEASE_INT and WSH_USA_CATEGORIES_PVT, plus the QA_ERES_WSH_DELIVERABLES_V view — call it during packing, container build, delivery auto-creation, release integration and warehouse execution. Users encounter it through the Shipping Transactions and Container/LPN forms and through concurrent programs such as delivery auto-creation. Custom code should call the higher-level WSH action APIs rather than this internal utility package directly, since its interface is not a published business API and may change between releases.