Results for “wms_packing_kitting_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WMS_PACKING_KITTING_V is a VALID database view owned by the APPS schema within the Warehouse Management (WMS) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve the Packing Workbench Kitting spreadtable, the interactive grid that Oracle's Packing Workbench uses to display kit and component line detail during outbound packing operations. The view is therefore a presentation-layer artifact: it does not store data of its own but projects the contents of an underlying global temporary table into the shape expected by the kitting spreadtable UI and by any concurrent program or custom report that reads the same structure.

Because the view text is defined simply as SELECT * FROM WMS_PACKING_KITTING_GTEMP, it acts as a thin, stable abstraction over the temporary staging table. The columns and their order are inherited directly from that table, which means the view remains consistent with the temporary table's definition as patched across releases. In ETRM terms the object is registered as a VIEW with a status of VALID, indicating that it compiles successfully against the current APPS schema and that no invalid dependency exists at the time of documentation.

Underlying Base Objects

The single documented referenced base object is WMS_PACKING_KITTING_GTEMP, held in the APPS schema as a synonym. The relationship is one-to-one and pass-through: every row and column visible in WMS_PACKING_KITTING_V originates from the global temporary table, with no joins, filters, aggregations, or computed expressions applied in the view layer. This design is characteristic of Oracle's Packing Workbench implementation, where temporary staging tables are populated by the workbench session and then exposed through a view for the spreadtable's query path and for any dependent logic that prefers a named view over a direct table reference. Because the underlying object is a GTT, its rows are scoped to the session or transaction that inserted them, so the view returns only the data staged by the calling session. This behavior makes the view unsuitable as a source for cross-session historical reporting on its own.

Key Columns

The columns exposed by WMS_PACKING_KITTING_V include:

• ITEM — the item identifier associated with the kit or component row, used for display and matching.
• KIT_ITEM_ID — the inventory item ID of the kit (parent) item being packed.
• COMPONENT_ITEM_ID — the inventory item ID of the component belonging to the kit.
• TOP_MODEL_LINE_ID — the identifier of the top-level model or configuration line that anchors the kit structure in the spreadtable.
• BOM_QTY — the bill of material quantity, i.e., the number of component units required per kit.
• ORDER_QTY — the ordered quantity of the kit or component for the line in context.
• PACKED_QTY — the quantity packed to date for the line.
• PACKED_QTY_DISP — the display-formatted packed quantity, typically rendered in the spreadtable.
• COMPLETED_FLAG — the flag indicating whether the kit or component line has been fully packed and is considered complete.

The COMPLETED_FLAG is the column most commonly targeted by users searching this view, as it drives completion status indicators in the kitting spreadtable and is frequently referenced in validation logic.

Common Use Cases and Queries

The view is used when the Packing Workbench populates the kitting spreadtable, when custom extensions need to read the staged kitting lines in the same session, and when diagnosing packing completion status. Typical access is session-bound, meaning a query must be executed from the same session (or application context) that populated the temporary table. A representative query is:

SELECT KIT_ITEM_ID, COMPONENT_ITEM_ID, BOM_QTY, ORDER_QTY, PACKED_QTY, COMPLETED_FLAG FROM APPS.WMS_PACKING_KITTING_V WHERE COMPLETED_FLAG = 'Y';

Additional filters are frequently applied on KIT_ITEM_ID or TOP_MODEL_LINE_ID to isolate a single kit within the spreadtable. Because the view performs no aggregation, any roll-up of packed quantities across components must be computed in the calling query. For persistent, cross-session reporting, the underlying WMS packing and shipping tables should be used instead, since the global temporary table's content is transient by design.