Search Results wsh_packed_containers




Overview
Explore in AI Chat

Overview

The WSH_PACKED_CONTAINERS table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary transactional repository for recording and managing container-level information within the shipping execution process. This table is fundamental to the Warehouse Management System (WMS) and Shipping Execution functionalities, enabling the physical grouping of picked items into discrete containers, cartons, or pallets for a delivery. Its role is to establish the link between the logical delivery, the physical container used, and the specific inventory items packed within it, forming a critical layer in the fulfillment data model.

Key Information Stored

The table's primary key is CONTAINER_ID, which uniquely identifies each packed container record. As indicated by the foreign key relationships, other crucial columns include DELIVERY_ID, which associates the container with a specific delivery in the WSH_DELIVERIES table. The combination of CONTAINER_INVENTORY_ITEM_ID and ORGANIZATION_ID links the physical container type (e.g., a specific box or pallet item) to its master definition in the MTL_SYSTEM_ITEMS_B table. While the provided metadata does not list all columns, typical data stored includes container identifiers (like a license plate number), tare weight, gross weight, packing instructions, and status flags that track the container's progress through the shipping lifecycle.

Common Use Cases and Queries

A primary use case is generating packing lists and shipping manifests, where details of all containers for a delivery are required. This is also essential for freight rating and cost allocation, as freight charges (SO_FREIGHT_CHARGES) can be associated at the container level. Common reporting needs involve analyzing container utilization or tracing the history of a specific physical container. A sample query to list all containers for a delivery would be:

  • SELECT pc.container_id, pc.seal_code, d.delivery_id
  • FROM oe.wsh_packed_containers pc,
  •      oe.wsh_deliveries d
  • WHERE pc.delivery_id = d.delivery_id
  • AND d.name = '<Delivery_Name>';

Another critical operational query involves joining to picking line details (SO_PICKING_LINE_DETAILS) to validate that all picked items have been successfully assigned to a container.

Related Objects

The WSH_PACKED_CONTAINERS table is centrally connected to several key EBS tables via documented foreign key relationships. The primary foreign keys are:

  • WSH_DELIVERIES: Linked via WSH_PACKED_CONTAINERS.DELIVERY_ID. This is the master-delivery relationship.
  • MTL_SYSTEM_ITEMS_B: Linked via the composite foreign key (CONTAINER_INVENTORY_ITEM_ID, ORGANIZATION_ID). This defines the container item.

Furthermore, this table is referenced as a parent key in the following tables:

  • SO_FREIGHT_CHARGES: Linked via SO_FREIGHT_CHARGES.CONTAINER_ID, enabling freight cost assignment per container.
  • SO_PICKING_LINE_DETAILS: Linked via SO_PICKING_LINE_DETAILS.CONTAINER_ID, tying specific picked inventory to its packed container.