Results for “wip_pcb_flow_schedule_events_v”

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

Overview

WIP_PCB_FLOW_SCHEDULE_EVENTS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the Work in Process (WIP) product. It functions as a base view for the WIP Production Control Board, providing the schedule event data that drives the flow schedule display used by production supervisors and planners. The view supplies the sequence-based events associated with flow schedules for a given assembly and production line, enabling the Production Control Board to present routing operations as discrete events on a line-oriented schedule. Its definition includes the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes rather than for data manipulation. The view is present in both 12.1.1 and 12.2.2, with its documented metadata consistent across these releases.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through synonyms in the APPS schema:

• WIP_FLOW_SCHEDULES — the primary driver, supplying flow schedule attributes such as ORGANIZATION_ID, LINE_ID, WIP_ENTITY_ID, PRIMARY_ITEM_ID, ALTERNATE_ROUTING_DESIGNATOR, and ROUTING_REVISION_DATE.
• BOM_OPERATIONAL_ROUTINGS — provides the routing header, joined on ORGANIZATION_ID, ASSEMBLY_ITEM_ID, and LINE_ID, with the CFM_ROUTING_FLAG constrained to 1 and alternate routing designators matched via DECODE handling of nulls.
• BOM_OPERATION_SEQUENCES — supplies routing sequence detail, including the LINE_OP_SEQ_ID, operation type, effectivity and disable dates, and the linkage to standard operations. The view joins twice: once for the line operation (OPERATION_TYPE = 3) and once for the standard operation sequence.
• BOM_STANDARD_OPERATIONS — supplies the OPERATION_CODE and provides the STANDARD_OPERATION_ID linkage. The join to BSO is outer (+), allowing operations without a matching standard operation to remain visible.

Because the view relies on BOM routings and standard operations, it is the natural interface between BOM routing definitions and WIP flow scheduling, which is why users searching on bom_standard_operations will encounter it as a dependent object.

Key Columns

The view exposes the following columns:

• ORGANIZATION_ID — the inventory organization that owns the flow schedule and routing.
• LINE_ID — the production line on which the flow schedule executes.
• WIP_ENTITY_ID — the flow schedule work order entity identifier.
• LINE_OPERATION_SEQUENCE_ID — sourced from BOS.OPERATION_SEQUENCE_ID, identifying the line-level operation sequence as required by the Production Control Board.
• NODE_TYPE — a constant literal of 2, used internally by the Production Control Board to classify the record as a line operation node.
• OPERATION_SEQ_NUM — the operation sequence number from BOM_OPERATION_SEQUENCES.
• NODE_LABEL — a concatenation of OPERATION_SEQ_NUM and the operation code separated by a colon; this is the display label rendered on the control board.
• OPERATION_CODE — the standard operation code from BOM_STANDARD_OPERATIONS, describing the work performed at that step (for example, a routing operation name).

Common Use Cases and Queries

The view is typically queried to retrieve the ordered set of line operations for flow schedules on a given production line, supporting control board rendering, schedule event reporting, and integration extracts. A representative query follows:

• List all schedule events for an organization and line: SELECT wip_entity_id, line_operation_sequence_id, operation_seq_num, node_label, operation_code FROM apps.wip_pcb_flow_schedule_events_v WHERE organization_id = :org AND line_id = :line ORDER BY operation_seq_num;
• Retrieve events for a specific flow schedule: SELECT node_label, operation_code, node_type FROM apps.wip_pcb_flow_schedule_events_v WHERE wip_entity_id = :wip_entity_id ORDER BY operation_seq_num;
• Join to BOM_STANDARD_OPERATIONS to enrich reporting with additional standard operation attributes not exposed by the view.

Because the view is read-only and resolves current routing revision and effectivity logic at runtime, it should be queried directly rather than replicated.