Results for “wsh_packed_containers”

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

Overview

WSH_PACKED_CONTAINERS is the Oracle E-Business Suite table that stores the packing structure of a delivery: the physical containers (pallets, cartons, cases, or other handling units) into which shipped items are packed, along with the quantities, weights, volumes, and hierarchical parent/child relationships between those containers. It is owned by the OE schema and is used by the Oracle Shipping (WSH) and Order Entry modules to represent both the immediate packing of delivery contents and nested container topologies, such as a box placed on a pallet.

Within the Delivery/Shipping region of the ETRM, the table operates as a detail structure beneath WSH_DELIVERIES, keyed by CONTAINER_ID and carrying the packing attributes of each delivery. Its heuristic Data Vault classification is satellite-leaning: it holds descriptive, time-variant attributes about packing outcomes, referencing the delivery and inventory item hubs rather than capturing pure many-to-many intersections on its own. A Data Vault model would therefore treat WSH_PACKED_CONTAINERS as a satellite of the delivery hub, with container hierarchy handled as a recursive or self-referencing structure rather than a separate link.

Key Information Stored

The table contains 48 columns, with CONTAINER_ID as the surrogate primary key (WSH_PACKED_CONTAINERS_PK), also enforced by unique index WSH_PACKED_CONTAINERS_U1, making it the documented business-key candidate for the table. The most important columns are:

• CONTAINER_ID — surrogate primary key that uniquely identifies each packed container; referenced by downstream freight, picking, and interface tables.
• DELIVERY_ID — foreign key to WSH_DELIVERIES, tying each container to its parent delivery.
• CONTAINER_INVENTORY_ITEM_ID — foreign key to MTL_SYSTEM_ITEMS_B, identifying the inventory item used as the container (for example, the pallet or carton item); combined with ORGANIZATION_ID.
• QUANTITY — the quantity of the packed item or container contents.
• SEQUENCE_NUMBER and PARENT_SEQUENCE_NUMBER — define ordering and the hierarchical placement of containers within the packing structure.
• ORGANIZATION_ID, SUBINVENTORY, INVENTORY_LOCATION_ID — inventory context for the container.
• REVISION, LOT_NUMBER, SERIAL_NUMBER, MASTER_SERIAL_NUMBER, INVENTORY_STATUS — item control and traceability attributes.
• GROSS_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE, FILL_PERCENT — weight, volume, and capacity measurements used in shipping documentation and freight rating.
• PARENT_CONTAINER_ID and MASTER_CONTAINER_ID — self-referencing identifiers used to resolve nested and consolidated container relationships.
• RA_INTERFACE_STATUS and REQUEST_ID, PROGRAM_ID, ATTRIBUTE1–15 — integration status, concurrent program context, and descriptive flexfield attributes.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieval of all containers packed on a delivery, reconciliation of packed quantities against delivery lines, printing packing slips and container labels, and freight charge calculation. The following query pattern returns the packing structure for a delivery:

• SELECT CONTAINER_ID, DELIVERY_ID, CONTAINER_INVENTORY_ITEM_ID, QUANTITY, SEQUENCE_NUMBER, PARENT_SEQUENCE_NUMBER, GROSS_WEIGHT, WEIGHT_UOM_CODE FROM WSH_PACKED_CONTAINERS WHERE DELIVERY_ID = :delivery_id ORDER BY SEQUENCE_NUMBER;
• Joining to WSH_DELIVERIES on DELIVERY_ID to obtain delivery number, ship-to location, and carrier.
• Joining to MTL_SYSTEM_ITEMS_B on CONTAINER_INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve container item descriptions and units of measure.
• Self-joins on PARENT_CONTAINER_ID or PARENT_SEQUENCE_NUMBER to explode multi-level pallet/carton hierarchies.
• Aggregating GROSS_WEIGHT, NET_WEIGHT, and VOLUME by DELIVERY_ID for shipment manifest and freight rating reports.

Related Objects

• WSH_DELIVERIES — joined on WSH_PACKED_CONTAINERS.DELIVERY_ID; the parent delivery record.
• MTL_SYSTEM_ITEMS_B — joined on CONTAINER_INVENTORY_ITEM_ID and ORGANIZATION_ID; defines the container inventory item.
• SO_PICKING_LINE_DETAILS — references WSH_PACKED_CONTAINERS.CONTAINER_ID, linking picked lines to the container that received them.
• SO_FREIGHT_CHARGES — references CONTAINER_ID, associating freight charges with specific containers.
• WSH_FREIGHT_CHARGES_INTERFACE — references CONTAINER_ID for freight charge integration.
• WSH_PACKED_CONTAINER_INTERFACE — the interface table through which container data is staged and loaded.
• FTE_SHIPMENT_STATUS_HEADERS — references CONTAINER_ID for shipment status and tracking.
• BISM_OBJECTS and BISM_AGGREGATES — reference CONTAINER_ID for business intelligence and dimensional aggregation.

These relationships confirm that WSH_PACKED_CONTAINERS is a central operational detail for shipping execution, consumed by picking, freight, interface, and analytics components throughout Oracle EBS 12.1.1 and 12.2.2.