Search Results wip_pcb_flow_assemblies_v




Overview
Explore in AI Chat

Overview

WIP_PCB_FLOW_ASSEMBLIES_V is an APPS-owned, VALID database view within the Work in Process (WIP) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the base view for the WIP Production Control Board, a graphical shop-floor tool that presents assemblies flowing through a manufacturing line together with the pending line operations that still require execution. The view materializes the association between an assembly routed on a flow or continuous manufacturing line and its currently pending line operation, giving the Production Control Board a single, denormalized data source for rendering its node graph.

Because the view is defined WITH READ ONLY, it is intended strictly for query and reporting use. It exposes no DML path and is consumed by the PCB user interface layer as well as by custom reporting and integration logic that needs to determine, for a given organization and line, which assemblies have outstanding line work. Its output is filtered to flow routings only, since the defining query restricts BOM_OPERATIONAL_ROUTINGS to rows where CFM_ROUTING_FLAG = 1 (the continuous/flow manufacturing flag) and BOM_OPERATION_SEQUENCES to OPERATION_TYPE = 3, the line operation type.

Underlying Base Objects

The view is constructed from four documented base objects joined on organization and inventory item identity:

Joins link MTL_ROUTING_REV_HIGHDATE_V to MTL_SYSTEM_ITEMS_KFV on INVENTORY_ITEM_ID and ORGANIZATION_ID, and BOM_OPERATIONAL_ROUTINGS to MTL_ROUTING_REV_HIGHDATE_V on ASSEMBLY_ITEM_ID / INVENTORY_ITEM_ID and ORGANIZATION_ID.

Key Columns

  • ORGANIZATION_ID — the manufacturing organization (plant) context.
  • LINE_ID — the flow manufacturing line on which the assembly is routed.
  • INVENTORY_ITEM_ID — the assembly item identifier.
  • ALTERNATE_ROUTING_DESIGNATOR — distinguishes alternate routings for the same assembly.
  • EFFECTIVITY_DATE / PROCESS_REVISION — the effective routing revision date and revision identifier.
  • OPERATION_SEQUENCE_ID / STANDARD_OPERATION_ID — identifiers for the specific pending operation.
  • NODE_TYPE — hardcoded as 1, identifying the row as an assembly node in the PCB graph.
  • ASSEMBLY_NAME — the concatenated key flexfield segments for the item.
  • NODE_LABEL — a composite label formatted as ASSEMBLY_NAME:alternate designator:process revision:operation sequence number, used to label the node on the board.

Common Use Cases and Queries

Typical usages include populating Production Control Board node lists, driving custom pending-work dashboards, and validating line operation status during integration with MES or shop-floor systems. A representative query lists pending assemblies for a plant and line:

  • SELECT assembly_name, node_label, effectivity_date, process_revision FROM apps.wip_pcb_flow_assemblies_v WHERE organization_id = :org_id AND line_id = :line_id ORDER BY assembly_name;
  • SELECT inventory_item_id, alternate_routing_designator, operation_sequence_id FROM apps.wip_pcb_flow_assemblies_v WHERE organization_id = :org_id;

Because the view is read only and each row reflects a pending line operation, it should be queried at the reporting layer rather than updated directly; any refresh of pending status is performed internally through WIP_SFCB_UTILITIES.