Search Results wsh_container_load_pk

Overview

WSH_CONTAINER_LOAD is a container-load definition table owned by the OE (Order Entry) schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It defines the load (or mix) of items that may be placed into a container item, along with the maximum quantity permitted for each load item. In shipping and container-management flows, this table drives the rules that determine how order lines are packed into containers, pallets, or other handling units before shipment or manifesting.

The documented physical schema lists 29 columns, of which the first three form the primary key. The ETRM documentation assigns WSH_CONTAINER_LOAD a heuristic Data Vault classification of standalone. In Data Vault modeling terms this suggests the table behaves closest to a hub or reference construct rather than a dependent link or satellite: it is not joined horizontally through foreign-key-derived relationships to other vault entities, and its business identity rests entirely on the composite of MASTER_ORGANIZATION_ID, CONTAINER_ITEM_ID, and LOAD_ITEM_ID. This classification is a modeling suggestion derived from the FK structure, not an Oracle-declared attribute.

Key Information Stored

• MASTER_ORGANIZATION_ID — Part of the composite primary key. Identifies the master organization (inventory organization) under which the container-load rule is defined.
• CONTAINER_ITEM_ID — Part of the composite primary key. Identifies the container item (the outer pack, pallet, or shipping unit) that receives the load.
• LOAD_ITEM_ID — Part of the composite primary key; the column that most directly answers the user's search. Identifies the item that is loaded into the container.
• MAX_LOAD_QUANTITY — The maximum quantity of the load item that may be placed into the specified container item. This is the principal business quantity in the table and the basis for capacity validation during packing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive-flexfield columns, available for customer-specific extension without schema modification.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent change and session context.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent-program context columns identifying the process that last touched the row.

The surrogate primary key WSH_CONTAINER_LOAD_PK is defined over (MASTER_ORGANIZATION_ID, CONTAINER_ITEM_ID, LOAD_ITEM_ID). A unique index, WSH_CONTAINER_LOAD_U1, is documented over the same three columns, meaning the business key and the primary key coincide here and no separate surrogate identifier is exposed. Enforcing uniqueness on this triplet guarantees that one organization cannot define two competing maximum quantities for the same container/load item pairing.

Common Use Cases and Queries

Typical uses include validating whether a proposed packed quantity exceeds the allowed maximum for a given container, generating container-configuration reports, and troubleshooting packing or shipping errors where a load quantity was rejected.

To retrieve all load items permitted for a specific container in an organization:

• SELECT load_item_id, max_load_quantity FROM wsh_container_load WHERE master_organization_id = :org_id AND container_item_id = :container_item_id;

To look up a single rule using the full business key (the pattern most relevant to a search on load_item_id):

• SELECT * FROM wsh_container_load WHERE master_organization_id = :org_id AND container_item_id = :container_id AND load_item_id = :load_id;

To check whether any load quantity exceeds its configured maximum:

• SELECT * FROM wsh_container_load WHERE max_load_quantity < :requested_quantity;

Reporting queries frequently join to inventory item master tables to translate CONTAINER_ITEM_ID and LOAD_ITEM_ID into user-friendly item numbers and descriptions, since the table itself stores only numeric item identifiers.

Related Objects

WSH_CONTAINER_LOAD sits in the Oracle Shipping (WSH) and Order Entry (OE) family. The most significant related objects and join paths are:

• WSH_CONTAINERS — Actual container instances created during packing; joins on the container item and organization context.
• WSH_CONTAINER_ITEMS — Defines which items relate to a given container; complements the load-item rules held here.
• MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_TL — Inventory item master. Joins via CONTAINER_ITEM_ID and LOAD_ITEM_ID to resolve item numbers and descriptions; also supplies the MASTER_ORGANIZATION_ID context.
• MTL_PARAMETERS — Organization definition; joins on MASTER_ORGANIZATION_ID to confirm the operating organization.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — Order data that ultimately drives packing; related through inventory item references rather than direct foreign keys.
• WSH_DELIVERY_DETAILS — Shipment line detail populated as containers are packed and manifested.

No foreign keys are documented in the ETRM extract beyond the primary-key definition, consistent with the standalone Data Vault classification. Application logic in the packing and shipping modules enforces the referential integrity to the inventory item and organization tables at runtime.