Search Results operation_sequence_number




Overview
Explore in AI Chat

Overview

WIPBV_FLOW_SCHED_COMPS is a reporting view owned by the APPS schema and defined within the Work in Process (WIP) product family. It consolidates component demand and consumption information for flow schedules, presenting a summarized picture of material requirements and completed quantities by operation. The view is most commonly accessed when reporting on component-level activity associated with flow manufacturing, where discrete job semantics are replaced by rate-based flow scheduling logic.

Because it joins bill of material explosion data with material transaction history through a UNION ALL, the view serves both as a planning reference (required quantities) and a consumption reference (completed quantities). This duality makes it suitable for shop floor dashboards, shortage analysis, and integration extracts that must reconcile planned component usage against actual transactions. The view carries a security predicate referencing FND_GLOBAL, ensuring that organization-level access controls are enforced at query time.

Underlying Base Objects

The view is defined over several documented base objects. BOM_EXPLOSIONS supplies the exploded component hierarchy for the flow schedule's assembly, including operation sequence, component quantity, effectivity, and disable dates. BOM_BILL_OF_MATERIALS provides the bill header, alternate BOM designator, and common bill sequence linkage. BOM_INVENTORY_COMPONENTS supplies the component-item relationship and sequence identifiers. MTL_SYSTEM_ITEMS enforces the planning make/buy flag, restricting results to internally manufactured components. WIP_ENTITIES and WIP_FLOW_SCHEDULES provide the flow schedule header, planned quantity, organization, and scheduled start date. MTL_MATERIAL_TRANSACTIONS contributes the transaction-side consumption rows that are unioned into the result set. FND_GLOBAL is referenced for the organization security predicate.

The first branch of the UNION ALL returns required quantities derived from the explosion, with a zero completed quantity placeholder. The second branch returns completed (consumed) quantities from material transactions, negating the transaction quantity and again carrying a zero placeholder for the required side. The outer query then aggregates by operation sequence number, WIP entity, component sequence, inventory item, and organization.

Key Columns

  • OPERATION_SEQUENCE_NUMBER — The routing operation sequence at which the component is required or consumed. This is the column most frequently referenced in ad hoc queries and is the term the user searched for.
  • REQUIRED_QUANTITY — Summed component demand, calculated as the exploded component quantity multiplied by the flow schedule planned quantity.
  • COMPLETED_QUANTITY — Summed consumed quantity, derived from material transactions and sign-adjusted.
  • WIP_ENTITY_ID — Identifier of the flow schedule entity.
  • COMPONENT_SEQUENCE_ID — Unique sequence identifier for the component within the bill.
  • INVENTORY_ITEM_ID — The component item identifier.
  • ORGANIZATION_ID — The inventory organization context, also used in the security predicate.

Common Use Cases and Queries

Typical scenarios include comparing required versus completed quantities per operation to detect shortages or over-issue, extracting component usage for a specific flow schedule, and aggregating demand by operation sequence for capacity and material planning reports.

Sample query to retrieve component demand and consumption for a flow schedule ordered by operation:

  • SELECT operation_sequence_number, inventory_item_id, SUM(required_quantity) req_qty, SUM(completed_quantity) comp_qty FROM wipbv_flow_sched_comps WHERE wip_entity_id = :wip_entity_id GROUP BY operation_sequence_number, inventory_item_id ORDER BY operation_sequence_number;

Sample query to list only operations with an outstanding shortage:

  • SELECT operation_sequence_number, inventory_item_id, SUM(required_quantity) - SUM(completed_quantity) open_qty FROM wipbv_flow_sched_comps WHERE organization_id = :org_id GROUP BY operation_sequence_number, inventory_item_id HAVING SUM(required_quantity) - SUM(completed_quantity) > 0;

Because the view aggregates at query time and reads from explosion and transaction sources, results should be filtered by organization and entity to limit execution cost. The FND_GLOBAL predicate ensures that callers only see data for organizations to which they are authorized.