Search Results wsh_container_items




Overview
Explore in AI Chat

Overview

WSH_CONTAINER_ITEMS is a Shipping Execution (WSH) table that stores container and item load relationships. In Oracle EBS 12.1.1 and 12.2.2, it acts as the association layer between a container (such as a pallet, carton, or LPN) and the items or load lines being packed into it. Each row binds a CONTAINER_ITEM_ID to a LOAD_ITEM_ID within a MASTER_ORGANIZATION_ID, making the table central to packing, container build, and load sequencing operations in the shipping process.

The ETRM metadata classifies this object heuristically (via FK structure analysis) as standalone in Data Vault terms. That classification is a modeling suggestion: the table behaves as its own hub-like structure rather than as a purely dependent satellite, though in practice it functions as a link between container and item load entities.

Key Information Stored

The table contains 31 documented columns. The most operationally significant include:

  • CONTAINER_ITEM_ID – Identifier for the container-item relationship; part of the composite primary key.
  • LOAD_ITEM_ID – References the load item being placed into the container; also part of the primary key.
  • MASTER_ORGANIZATION_ID – The master organization under which the relationship is valid; third component of the primary key.
  • MASTER_LOCATION_ID – Identifies the master inventory location associated with the container/load.
  • MAX_LOAD_QUANTITY – The maximum quantity that may be loaded for this container-item relationship.
  • PREFERRED_FLAG – Indicates whether this container-item arrangement is preferred.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Flexfield descriptor and reserved descriptive flexfield segments for customer-specific data.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID – Concurrent program and request tracking columns.

The surrogate primary key is WSH_CONTAINER_ITEMS_PK defined over (CONTAINER_ITEM_ID, LOAD_ITEM_ID, MASTER_ORGANIZATION_ID). A unique index, WSH_CONTAINER_ITEMS_U1, covers (CONTAINER_ITEM_ID, MASTER_ORGANIZATION_ID, LOAD_ITEM_ID), which serves as a business-key candidate enforcing uniqueness on the same logical combination.

Common Use Cases and Queries

Typical scenarios include identifying which items are packed into a given container, calculating total container loads, and reporting preferred container-item pairings. A representative query joins this table to load and container headers:

  • Select all items for a container: SELECT LOAD_ITEM_ID, MAX_LOAD_QUANTITY FROM WSH_CONTAINER_ITEMS WHERE CONTAINER_ITEM_ID = :container_id AND MASTER_ORGANIZATION_ID = :org_id;
  • Identify preferred relationships: SELECT * FROM WSH_CONTAINER_ITEMS WHERE PREFERRED_FLAG = 'Y';
  • Audit recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY to track packing maintenance activity.
  • Extract customer-specific packed configuration via ATTRIBUTE_CATEGORY and the ATTRIBUTE columns.
  • Feed container-level load reporting and weight/volume calculations in shipping dashboards.

Related Objects

The table participates in container and load management within Shipping Execution. Significant related objects include:

Because the ETRM relationship classification is standalone, no enforced foreign keys are documented; joins are established logically through the shared identifier columns rather than database constraints.