Search Results line_operation_sequence_id




Overview
Explore in AI Chat

Overview

The view APPS.WIP_PCB_FLOW_ASSEMBLY_EVENTS_V is an Oracle E-Business Suite internal database view owned by the APPS schema. It belongs to the Work in Process (WIP) application and is registered under the FND Design Data identifier WIP.WIP_PCB_FLOW_ASSEMBLY_EVENTS_V. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exposes routing and operation-level data that is used in the context of printed circuit board (PCB) flow assembly event processing, presenting a consolidated picture of an item's operational routing for a given organization and production line.

The view is documented as Oracle Internal Use Only. Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Consequently, its role is primarily that of an internal reporting and integration access point used by WIP and adjacent modules rather than a customer-facing interface. The view is read-only in nature (a view, not a table) and is not referenced by any other database object, confirming its position as a terminal reporting construct at the top of its dependency chain.

Underlying Base Objects

The view is defined over the following documented base objects:

  • BOM_OPERATIONAL_ROUTINGS (SYNONYM) — provides the routing header, including routing designator and routing revision context.
  • BOM_OPERATION_SEQUENCES (SYNONYM) — supplies the operation sequence lines, sequence identifiers, and operation associations.
  • BOM_STANDARD_OPERATIONS (SYNONYM) — provides standard operation definitions, including operation codes.
  • MTL_ROUTING_REV_HIGHDATE_V (VIEW) — supplies routing revision high-date information used to resolve valid routing revisions.
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — the key-flex view of the item master, providing inventory item identification and descriptive attributes.

The join across these objects allows the view to resolve an organization's item, its applicable routing, the operation sequences within that routing, and the corresponding standard operation codes into a single flattened result set. Because the routing revision is resolved through MTL_ROUTING_REV_HIGHDATE_V, the view observes point-in-time routing validity governed by effectivity and high-date logic.

Key Columns

The view exposes eleven columns that collectively identify the manufacturing context of each PCB flow assembly event:

  • ORGANIZATION_ID (NUMBER) — the inventory organization in which the routing and operation apply.
  • LINE_ID (NUMBER) — the production line associated with the assembly event.
  • INVENTORY_ITEM_ID (NUMBER) — the item being assembled.
  • ALTERNATE_ROUTING_DESIGNATOR (VARCHAR2, 10) — the alternate routing designator, if any.
  • EFFECTIVITY_DATE (DATE) — the effective date governing the routing revision.
  • PROCESS_REVISION (VARCHAR2) — the process revision identifier for the routing.
  • LINE_OPERATION_SEQUENCE_ID (NUMBER) — the primary key linking a line to a specific operation sequence; this is the identifier users most often search for when tracing operation sequence membership.
  • NODE_TYPE (NUMBER) — a numeric classification of the routing node.
  • OPERATION_SEQ_NUM (NUMBER) — the operation sequence number used to order operations within the routing.
  • NODE_LABEL (VARCHAR2, 45) — the descriptive label for the routing node.
  • OPERATION_CODE (VARCHAR2) — the standard operation code associated with the operation.

Common Use Cases and Queries

The view is typically queried to resolve which operations belong to a given item's routing for a specific organization and production line, and to retrieve the corresponding operation sequence identifiers and codes. A representative query retrieving all operation nodes for a given organization and item follows:

  • SELECT organization_id, line_id, inventory_item_id, operation_seq_num, operation_code, line_operation_sequence_id FROM apps.wip_pcb_flow_assembly_events_v WHERE organization_id = :org_id AND inventory_item_id = :item_id ORDER BY operation_seq_num;
  • SELECT line_operation_sequence_id, node_label, operation_code FROM apps.wip_pcb_flow_assembly_events_v WHERE line_operation_sequence_id = :seq_id;
  • SELECT DISTINCT alternate_routing_designator, process_revision FROM apps.wip_pcb_flow_assembly_events_v WHERE organization_id = :org_id AND effectivity_date <= SYSDATE;

Because direct access is unsupported by Oracle, any query should be treated as diagnostic or read-only investigative activity, and production integrations should rely on supported WIP and Bills of Material APIs where functionality is required.