Search Results inventory_interfaced_status

Overview

WSHBV_PACKED_CONTAINER is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and documented under the Order Entry (OE) product family. The view exposes packed container information maintained by Oracle Shipping Execution, presenting one row per container record that has been packed against a delivery. In EBS 12.1.1 and 12.2.2 the object carries the annotation "Retrofitted," indicating that its definition was carried forward across releases to preserve backward compatibility for existing customizations, concurrent programs, and third-party integrations that reference the shipped packed container data.

The view is primarily used for reporting, data extraction, and interface auditing rather than for transactional maintenance. It provides a denormalized, read-friendly projection of the WSH_PACKED_CONTAINERS table enriched with container item descriptions from inventory, allowing shipping, warehouse, and order management users to inspect container hierarchies, weights, and interface statuses without joining multiple base tables.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through APPS synonyms:

• WSH_PACKED_CONTAINERS (alias PC) — the driving table. It supplies container identity, delivery association, item, quantities, sequencing, weight, and interface status columns.
• MTL_SYSTEM_ITEMS (alias MSI) — joined on PC.CONTAINER_INVENTORY_ITEM_ID = MSI.INVENTORY_ITEM_ID and PC.ORGANIZATION_ID = MSI.ORGANIZATION_ID to resolve the container item description.

The join is an inner join on both the item and organization keys, so only container rows with a matching item definition in the same inventory organization are returned. Because the parent_sequence_number is sourced directly from WSH_PACKED_CONTAINERS, the view preserves the parent-child relationship used to model nested (packed-into) containers on a delivery.

Key Columns

• CONTAINER_ID — primary identifier of the packed container record.
• DELIVERY_ID — the delivery to which the container belongs; the principal grouping key for shipping reports.
• CONTAINER_INVENTORY_ITEM_ID — the inventory item defining the container (for example, a carton or pallet item).
• PACKED_QUANTITY — quantity packed into the container, aliased from PC.QUANTITY.
• SEQUENCE_NUMBER — ordering sequence of the container within the delivery.
• PARENT_SEQUENCE_NUMBER — identifies the parent container by sequence, enabling reconstruction of the container hierarchy (the term for which this object was searched).
• GROSS_WEIGHT and WEIGHT_UOM_CODE — container weight and its unit of measure.
• CONTAINER_DESCRIPTION — item description sourced from MTL_SYSTEM_ITEMS.
• INVENTORY_LOCATION_ID, SUBINVENTORY, REVISION, LOT_NUMBER, SERIAL_NUMBER, MASTER_SERIAL_NUMBER — inventory attribution of the packed contents.
• INVENTORY_INTERFACED_STATUS and RECEIVABLE_INTERFACED_STATUS — aliases of PC.INVENTORY_STATUS and PC.RA_INTERFACE_STATUS, indicating whether the container has been interfaced to inventory or receivables.
• WHO columns and request 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 for audit and concurrent program traceability.

Common Use Cases and Queries

Typical usage includes container packing reports, weight verification, hierarchy reconstruction, and interface status audits. A representative query listing containers for a delivery follows:

• SELECT container_id, delivery_id, sequence_number, parent_sequence_number, container_description, packed_quantity, gross_weight, weight_uom_code FROM apps.wshbv_packed_container WHERE delivery_id = :p_delivery_id ORDER BY sequence_number;
• SELECT container_id, sequence_number, parent_sequence_number, container_description FROM apps.wshbv_packed_container WHERE parent_sequence_number IS NOT NULL ORDER BY delivery_id, parent_sequence_number, sequence_number; — reconstructs nested container structures.
• SELECT delivery_id, SUM(gross_weight) FROM apps.wshbv_packed_container GROUP BY delivery_id; — aggregates container weight per delivery.

Because the view joins to MTL_SYSTEM_ITEMS, results reflect the current item description in the same organization; reports requiring historical descriptions should query the base table directly.