Search Results wsh_container_load_u1

Overview

WSH_CONTAINER_LOAD is a transactional table owned by the OE schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the packing relationship between a container item and the individual items loaded into that container at the moment of ship confirmation. In shipping execution terms, the table captures the "what went inside what" association that underlies container packing, manifesting, and load verification activity within the Warehouse Management and Shipping Execution modules.

The table is registered under FND Design Data as OE.WSH_CONTAINER_LOAD with status VALID and resides in the APPS_TS_ARCHIVE tablespace with a PCTFREE of 10. Its structure comprises 29 documented columns, including a descriptive flexfield block (ATTRIBUTE_CATEGORY through ATTRIBUTE15) and the standard WHO and concurrent program audit columns. The heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting the object can be modeled as an independent hub rather than as a dependent satellite or link, since no inbound referential constraints are documented for it. Practitioners building analytics layers over shipping data may treat it as a hub keyed on the container/load item combination.

Key Information Stored

The most functionally important columns are the composite key members and the single quantitative measure. MASTER_ORGANIZATION_ID holds the master organization identifier, scoping each packing record to a specific inventory organization context. CONTAINER_ITEM_ID stores the inventory item identifier of the container itself, while LOAD_ITEM_ID stores the inventory item identifier of the item packed into that container. These three columns together form the documented primary key, WSH_CONTAINER_LOAD_PK, and are also the columns of the unique index WSH_CONTAINER_LOAD_U1, which makes them the business-key candidates for the table. MAX_LOAD_QUANTITY records the maximum quantity of the load item permitted in one container, expressed in the item's primary unit of measure.

The ATTRIBUTE_CATEGORY column holds the descriptive flexfield structure name, and ATTRIBUTE1 through ATTRIBUTE15 carry the individual flexfield segments, providing the standard extensibility mechanism for customer-specific packing attributes. The audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID — follow the standard EBS WHO and concurrent program conventions and are useful for lineage, data-fix auditing, and incremental extraction strategies. Note that the primary key here is a natural composite business key rather than a system-generated surrogate; no artificial single-column identifier is documented.

Common Use Cases and Queries

Typical usage centers on container capacity validation, packing confirmations, and load reporting. A common query retrieves all loaded items for a given container and organization:

• SELECT container_item_id, load_item_id, max_load_quantity FROM oe.wsh_container_load WHERE master_organization_id = :org_id AND container_item_id = :container_id;
• Reporting by loaded item across organizations to profile container usage: filter on LOAD_ITEM_ID and group by CONTAINER_ITEM_ID.
• Incremental extraction using LAST_UPDATE_DATE and LAST_UPDATED_BY to identify records touched by specific concurrent requests (REQUEST_ID, PROGRAM_ID).
• Descriptive flexfield reporting by joining ATTRIBUTE_CATEGORY to FND_DESCR_FLEX_CONTEXTS_VL for context validation.

Because the table is described as handling items packed during ship confirm, it is most valuable when correlated with the shipping confirmation window and delivery detail records rather than queried in isolation.

Related Objects

Although the documented metadata identifies WSH_CONTAINER_LOAD as standalone with no formal foreign-key dependencies, in practice it is queried alongside the shipping execution tables that share its item identifiers and organization scope. Significant related objects include WSH_CONTAINERS, which defines the container entities referenced through CONTAINER_ITEM_ID, and WSH_DELIVERY_DETAILS, which carries the delivery and item context for packed goods. MTL_SYSTEM_ITEMS_B supplies item descriptions for both CONTAINER_ITEM_ID and LOAD_ITEM_ID, and ORG_ORGANIZATION_DEFINITIONS resolves MASTER_ORGANIZATION_ID to an organization name. Supporting objects include the WSH_CONTAINER_LOAD indexes WSH_CONTAINER_LOAD_U1, WSH_CONTAINER_LOAD_N1 (CONTAINER_ITEM_ID), and WSH_CONTAINER_LOAD_N2 (LOAD_ITEM_ID), which drive query performance for container-centric and item-centric access paths respectively. Public APIs in the WSH shipping execution packages handle the insert and update operations that populate this table during ship confirm.