Results for “create_cont_instance_multi”

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

Overview

WSH_CONTAINER_ACTIONS is a core PL/SQL package in the Oracle E-Business Suite (EBS) Shipping Execution (WSH) module, residing in the APPS schema. It encapsulates the business logic that governs how containers, such as cartons, pallets, and license plates, are created, populated, packed, and associated with deliveries and delivery details. In the outbound shipping flow, containers represent the physical packing units used to consolidate items for shipment. This package provides the programmatic foundation for those operations, serving both as a callable API for form-based transactions and as an internal utility invoked by higher-level shipping packages. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and the ETRM classifies it under the OTHER API classification, indicating that it is primarily a supporting/internal package rather than a formally published public API, though its procedures may be invoked from custom code with appropriate caution.

Key Procedures and Functions

The ETRM metadata documents thirty-one procedures and functions, covering the full lifecycle of container management. Creation routines include CREATE_CONTAINER_INSTANCE, CREATE_CONT_INSTANCE_MULTI, CREATE_MULTIPLE_CONTAINERS, and CREATE_MULTIPLE_CONT_NAME, which instantiate one or more container records, optionally applying naming conventions. DEFAULT_CONTAINER_ATTR applies default attributes to newly created containers, while UPDATE_CONT_ATTRIBUTES and CHECK_CONT_ATTRIBUTES manage and validate container attributes respectively.

Assignment routines handle the relationships between containers, delivery details, and deliveries. ASSIGN_DETAIL, UNASSIGN_DETAIL, ASSIGN_TO_DELIVERY, CREATE_DELIVERY_ASSIGNMENT, UNASSIGN_DELIVERY, ASSIGN_TO_CONTAINER, and LAST_ASSIGNED_LINE manage the linkage of items to containers and containers to deliveries, including the creation of the underlying delivery assignment records.

Packing functions form the operational core: AUTO_PACK_LINES, AUTO_PACK_DELIVERY, AUTO_PACK_CONTS, and PACK_MULTI automate the process of placing delivery detail lines into containers based on packing rules. UPDATE_SHIPPED_QTY maintains the shipped quantities that result from packing operations, and UPDATE_CONT_HIERARCHY manages parent-child relationships for nested or hierarchical container structures.

Tables Accessed

The package reads and writes a substantial set of shipping and inventory tables through APPS synonyms. MTL_SYSTEM_ITEMS supplies item master attributes required to identify and validate packable items. WSH_CONTAINER_ITEMS and WSH_DELIVERY_DETAILS store the container contents and delivery lines being packed. WSH_DELIVERY_ASSIGNMENTS and its sequence WSH_DELIVERY_ASSIGNMENTS_S, along with WSH_DELIVERY_DETAILS_S, provide the assignment records linking details to containers and deliveries. WSH_NEW_DELIVERIES and WSH_DELIVERY_LEGS support delivery-level operations and routing, while WSH_TRIP_STOPS is used where container actions interact with trip and stop information. WMS_LICENSE_PLATE_NUMBERS and WMS_LPN_HISTORIES integrate with Warehouse Management license plate tracking. WSH_SHIPPING_PARAMETERS and MTL_PARAMETERS supply system-level configuration, and WSH_TMP serves as a temporary working table. WSH_UTIL_CORE and WSH_GLBL_VAR_STRCT_GRP are referenced as utilities and global variable structures.

Usage Notes

WSH_CONTAINER_ACTIONS is invoked indirectly by numerous shipping components rather than being called directly by end users. The metadata identifies sixteen referencing packages, including WSH_CONTAINER_GRP, WSH_DELIVERY_DETAILS_PKG, WSH_DELIVERY_DETAILS_ACTIONS, WSH_AUTO_MANIFEST, WSH_ASN_RECEIPT_PVT, WMS_DIRECT_SHIP_PVT, and WSH_INBOUND_UTIL_PKG. This dependency pattern confirms that the package acts as a shared service layer for container operations across outbound and inbound shipping, manifesting, and warehouse integration flows. Oracle Forms such as the Shipping Transactions form call the GRP-layer packages, which in turn delegate to this package. Customizations should avoid direct invocation where possible, since Oracle does not publish a formally supported interface for this object; where extension is required, developers should isolate calls and thoroughly test against the shipping data model, paying particular attention to shipped quantity and delivery assignment integrity.