Results for “csi_wip_components_v”

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

Overview

The APPS.CSI_WIP_COMPONENTS_V view is a reporting and integration construct within the Oracle E-Business Suite Install Base (CSI) module. It exposes component-level instance data associated with Work in Process (WIP) jobs, presenting a unified, flattened result set that joins transaction lines, transaction line details, and item-instance relationships. The view is defined as a UNION of at least two query branches, combining records sourced through transaction-relationship logic and records sourced directly from CSI_ITEM_INSTANCES. This design allows downstream reports, concurrent programs, and service integrations to retrieve WIP-linked component instances through a single object rather than assembling the same join logic repeatedly.

Because the view carries the WIP_JOB_ID column — derived from CTT.SOURCE_TRANSACTION_ID in the first branch and from CII.WIP_JOB_ID in the second — it is frequently discovered by users searching for that identifier. It provides a bridge between manufacturing execution records and the install base instance registry, which is central to traceability, genealogy, and post-manufacturing service reporting.

Underlying Base Objects

The documented referenced base objects are:

• CSI_ITEM_INSTANCES — the core install base instance table, supplying instance identity, serial and lot attributes, instance status, and the native WIP_JOB_ID in the second UNION branch.
• CSI_T_TRANSACTION_LINES — transaction header-level lines, joined by TRANSACTION_LINE_ID and filtered on SOURCE_TRANSACTION_TABLE = 'WIP_ENTITIES'.
• CSI_T_TXN_LINE_DETAILS — detailed line records carrying quantity, unit of measure, item, organization, and instance references.
• CSI_T_II_RELATIONSHIPS — instance-to-instance relationships linking subject and object detail records, joined on TRANSACTION_LINE_ID and subject detail ID.
• MTL_SYSTEM_ITEMS — the item master, referenced for item validation and descriptive lookups.

In the first branch, the join path is constrained by CTL.SOURCE_TRANSACTION_FLAG = 'N', isolating transaction detail rows that represent component consumption rather than the parent assembly event. The second branch draws directly from CSI_ITEM_INSTANCES using its persisted WIP_JOB_ID, which captures instances that may not have a corresponding transaction-line relationship record.

Key Columns

• INSTANCE_ID — identifier of the install base instance record.
• WIP_JOB_ID — the WIP entity (job or schedule) associated with the component; the primary join key to WIP tables such as WIP_ENTITIES.
• INVENTORY_ITEM_ID and INV_ORGANIZATION_ID — the component item and the inventory organization where it was last valid.
• SERIAL_NUMBER, LOT_NUMBER, and MFG_SERIAL_NUMBER_FLAG — instance serialization and lot attribution.
• QUANTITY and UNIT_OF_MEASURE — consumed or attributed quantity for the component instance.
• INSTANCE_STATUS_ID, LOCATION_TYPE_CODE, and LOCATION_ID — current instance status and physical location.
• TRANSACTION_LINE_ID, TXN_LINE_DETAIL_ID, PARENT_TXN_LINE_DETAIL_ID, and TXN_RELATIONSHIP_ID — transaction and relationship linkage supporting genealogy reconstruction.
• QUANTITY_CHECK_FLAG — a synthetic column returned as a constant 'N' in the first branch.

Common Use Cases and Queries

Typical uses include retrieving all serialized components consumed on a specific job, tracing installed instances back to their originating WIP entity, and building genealogy reports that join instance records to transaction relationships.

A representative query returns every component instance tied to a given job:

• SELECT instance_id, wip_job_id, inventory_item_id, serial_number, quantity
• FROM csi_wip_components_v
• WHERE wip_job_id = :p_wip_job_id;

The view is also joined to WIP_ENTITIES on WIP_JOB_ID to obtain job name, status, and assembly context, and to MTL_SYSTEM_ITEMS for item descriptions. Because the definition is a UNION across differently sourced branches, consumers should anticipate possible duplicate INSTANCE_ID values when a component is represented both through transaction relationships and directly within CSI_ITEM_INSTANCES; defensive DISTINCT or aggregate handling is advisable in downstream reporting.