Search Results wsh_container_items_u1

Overview

WSH.WSH_CONTAINER_ITEMS is a Shipping Execution (WSH) transactional table that defines the valid loading relationships between container items and the load items they may hold. In Oracle EBS 12.1.1 and 12.2.2 the table functions as an item-level container packing rule set: for a given inventory container item, it enumerates each load item that is permitted inside it and the maximum quantity of that load item the container can accommodate. This information drives container packing validation, load planning, and shipping documentation. The object resides in the APPS_TS_TX_DATA tablespace, is owned by the WSH schema, and is registered under FND Design Data as WSH.WSH_CONTAINER_ITEMS with status VALID.

Based on the mined foreign-key structure, the Data Vault classification heuristic returns standalone. No incoming or outgoing foreign keys are documented, so the table is best modeled as an independent reference/relationship entity rather than a hub, link, or satellite within a conventional Data Vault design. Its rows represent pair-wise compatibility rules, and the natural business key of each rule is captured by the composite unique index described below.

Key Information Stored

The table contains 31 documented columns. The most significant are:

• CONTAINER_ITEM_ID (NUMBER) – Inventory item identifier for the container; primary key column 1.
• LOAD_ITEM_ID (NUMBER) – Inventory item identifier for the item being loaded; primary key column 3.
• MASTER_ORGANIZATION_ID (NUMBER) – Organization context for the container item; primary key column 2.
• MAX_LOAD_QUANTITY (NUMBER) – Maximum quantity of the load item that fits into one container item.
• PREFERRED_FLAG – Indicates the preferred container/load combination.
• MASTER_LOCATION_ID (NUMBER) – Obsoleted by the location project; retained for backward compatibility only.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield context and segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard Who columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID – Concurrent program and request audit columns.

The surrogate primary key is WSH_CONTAINER_ITEMS_PK on (CONTAINER_ITEM_ID, LOAD_ITEM_ID, MASTER_ORGANIZATION_ID). The business-key candidate is enforced by the unique index WSH_CONTAINER_ITEMS_U1 on (CONTAINER_ITEM_ID, MASTER_ORGANIZATION_ID, LOAD_ITEM_ID), which prevents duplicate packing rules for the same container/load item pair within an organization. A non-unique index, WSH_CONTAINER_ITEMS_N2, supports retrieval by LOAD_ITEM_ID. Both indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical usage includes validating whether a load item may be packed into a container item, deriving the maximum fill quantity for packing calculations, and reporting container/item compatibility by organization. A representative lookup follows:

SELECT b.container_item_id, b.load_item_id, b.master_organization_id, b.max_load_quantity
FROM wsh_container_items b
WHERE b.master_organization_id = :org_id
AND b.container_item_id = :container_item_id;

To return all allowed load items for a container, filtering on the N2 index or the leading column of U1 is efficient; resolving load-item-centric questions benefits from WSH_CONTAINER_ITEMS_N2. Reporting queries frequently join to inventory item master and organization tables to translate the numeric item identifiers into descriptive flexfield or item-number values. Queries referencing MASTER_LOCATION_ID should treat the column as obsolete and avoid relying on it for new logic.

Related Objects

• WSH_LOAD_ITEMS – join via LOAD_ITEM_ID to obtain load-level packing attributes.
• WSH_CONTAINERS – join via CONTAINER_ITEM_ID to relate runtime containers to their defining items.
• MTL_SYSTEM_ITEMS_B – join via CONTAINER_ITEM_ID or LOAD_ITEM_ID to resolve item numbers and descriptions.
• ORG_ORGANIZATION_DEFINITIONS – join via MASTER_ORGANIZATION_ID to resolve organization names.
• WSH_CONTAINER_ITEM_ATTRS (or equivalent container item attribute table) – for extended container definition attributes.
• WSH_PACKING_RULES – for higher-level packing rule logic that may reference item compatibility.
• WSH_DELIVERY_DETAILS – indirectly related through load item and container references at ship-confirm time.

Because the object is classified as standalone, catalog joins must be supplied by the consuming application; no declarative foreign keys cascade from this table.