Search Results line_operation_sequence_id




Overview
Explore in AI Chat

Overview

WIP_PCB_FLOW_ASSEMBLY_EVENTS_V is an APPS-owned read-only view in the Oracle E-Business Suite Work in Process (WIP) module, documented as the "WIP Production Control Board base view." It is part of the data layer that supplies the Production Control Board (PCB), the graphical shop-floor display that presents the flow of assemblies through their routings, along with the assembly events (operations) associated with each routing node. The view was verified against ETRM metadata for Oracle EBS 12.1.1 and 12.2.2, where it holds VALID status. Because it is declared WITH READ ONLY, it is intended strictly for querying and reporting; no DML should be attempted against it. Its principal role is to flatten the relationship between an assembly item, its routing, and the line operations that make up that routing into a single rowdenormalized result set that a form or reporting front end can render as the flow diagram of the PCB.

Underlying Base Objects

The view text joins five documented base objects. The driving chain begins with MTL_ROUTING_REV_HIGHDATE_V (a view that returns the high-date routing revision for an item and organization) and MTL_SYSTEM_ITEMS_KFV (a synonym for the key flexfield item view, supplying ORGANIZATION_ID and INVENTORY_ITEM_ID). These are joined to BOM_OPERATIONAL_ROUTINGS (synonym), filtered on CFM_ROUTING_FLAG = 1, which restricts the result to flow routings rather than standard routings. Two aliased instances of BOM_OPERATION_SEQUENCES (BOS and BOS2) are used: BOS carries the line operation (OPERATION_TYPE = 3) linked via ROUTING_SEQUENCE_ID to COMMON_ROUTING_SEQUENCE_ID, while BOS2 joins on LINE_OP_SEQ_ID = BOS.OPERATION_SEQUENCE_ID to obtain the operation sequence number and effectivity. Finally, BOM_STANDARD_OPERATIONS (BSO) is outer-joined to BOS2 to resolve the human-readable OPERATION_CODE. Effectivity is enforced by comparing TRUNC(BOS2.EFFECTIVITY_DATE) to TRUNC(MRIR.HIGH_DATE), with disabled sequences excluded when DISABLE_DATE is null or greater than the high date.

Key Columns

  • ORGANIZATION_ID / INVENTORY_ITEM_ID — the inventory organization and assembly item identifying the flow subject.
  • LINE_ID — the production line associated with the routing.
  • ALTERNATE_ROUTING_DESIGNATOR — the alternate routing the assembly flows through.
  • EFFECTIVITY_DATE — TRUNC of the routing revision effectivity date.
  • PROCESS_REVISION — the process (routing) revision carried from the high-date revision view.
  • LINE_OPERATION_SEQUENCE_ID — aliased OPERATION_SEQUENCE_ID from BOS, the line operation identifier.
  • NODE_TYPE — constant literal 2 in the view text, a PCB node classification value.
  • OPERATION_SEQ_NUM — the operation sequence number of the line operation.
  • NODE_LABEL — concatenation of OPERATION_SEQ_NUM, a colon, and OPERATION_CODE, used as the display label for the node.
  • OPERATION_CODE — the standard operation code from BOM_STANDARD_OPERATIONS.

Common Use Cases and Queries

The view is typically consumed to populate or troubleshoot the PCB flow display, to audit which line operations exist for a given assembly routing, and to reconcile routing effectivity against the high-date revision. A representative query follows:

  • Retrieve the flow nodes for an item: SELECT organization_id, inventory_item_id, alternate_routing_designator, operation_seq_num, node_label, operation_code FROM apps.wip_pcb_flow_assembly_events_v WHERE inventory_item_id = :item_id AND organization_id = :org_id ORDER BY operation_seq_num;
  • List all flow routings on a line: SELECT DISTINCT line_id, inventory_item_id, process_revision FROM apps.wip_pcb_flow_assembly_events_v WHERE line_id = :line_id;
  • Join to WIP entities for current job context using LINE_OPERATION_SEQUENCE_ID as the correlation key.

Because the view predigests the routing, item, and operation joins, it is preferable to re-deriving those joins for PCB-related reporting and integration. All access should remain read-only.