Search Results operation_sequence_number




Overview
Explore in AI Chat

Overview

APPS.WIPBV_FLOW_SCHED_COMPS is a reporting and integration view in Oracle E-Business Suite that consolidates component-level supply and demand information for flow schedules (repetitive and mixed-model manufacturing) in Oracle Work in Process. The view derives its name from "WIP Bill of Materials View – Flow Schedule Components," and it presents an aggregated picture of required versus completed component quantities per operation sequence within a flow schedule.

The view is defined as a UNION ALL of two complementary subqueries. The first captures planned component requirements by exploding the applicable bill of materials for the flow schedule's primary assembly, multiplying each component quantity by the flow schedule's planned quantity. The second captures actual completed quantities from material transactions, expressed as a negative transaction quantity so that the union produces an internally consistent net perspective. Records are grouped and summed so that each row represents a distinct combination of operation_sequence_number, wip_entity_id, component_sequence_id, inventory_item_id, and organization_id. Because the underlying data spans discrete WIP entities, flow schedules, BOM structures, and inventory transactions, the view is a convenient single source for operational reporting, dashboard queries, and integrations that need flow schedule component position without writing the multi-table join logic manually.

Underlying Base Objects

The documented base objects referenced by the view are:

  • WIP_ENTITIES – Provides the work order / flow schedule header context, including wip_entity_id.
  • WIP_FLOW_SCHEDULES – Supplies planned quantity, scheduled start date, organization, primary item, and alternate BOM designator for the flow schedule.
  • BOM_BILL_OF_MATERIALS – Establishes the applicable bill of materials for the assembly, including alternate BOM designator validation and the common bill sequence.
  • BOM_EXPLOSIONS – The flattened BOM explosion supplying component quantity, operation sequence, component sequence, and effectivity/disable dates.
  • BOM_INVENTORY_COMPONENTS – Ties component items to the bill sequence and provides component sequence identifiers.
  • MTL_SYSTEM_ITEMS – Filters to items with planning_make_buy_code = 1, restricting the result set to make (manufactured) components.
  • MTL_MATERIAL_TRANSACTIONS – Contributes actual completed quantity from issued/consumed transactions in the second union branch.
  • FND_GLOBAL – Underpins the organization security predicate visible in the text (_SEC:flow.organization_id), enforcing multi-org access control.

Effectivity logic restricts the explosion to components effective as of the truncated scheduled start date, and alternate BOM designators are matched against the flow schedule's designator with a default-sentinel comparison.

Key Columns

  • operation_sequence_number – The routing operation sequence on which the component is consumed; sourced from expl.operation_seq_num and mtl.operation_seq_num. This is the column most frequently searched and used to align components to routing operations.
  • wip_entity_id – Identifies the flow schedule / WIP entity.
  • component_sequence_id – Identifies the component line on the BOM.
  • inventory_item_id – The component item identifier.
  • organization_id – The manufacturing organization; also the basis for the security predicate.
  • required_quantity – Sum of component_quantity × planned_quantity from the BOM explosion branch.
  • completed_quantity – Sum of negated material transaction quantities, representing consumed/completed component quantity.

Because the two branches are summed in the outer query, required_quantity and completed_quantity are released as aggregate values per grouped key.

Common Use Cases and Queries

Typical uses include flow schedule component shortage analysis, operation-level consumption reporting, and integration feeds into MES or planning systems. A representative query filtering by operation sequence:

  • SELECT wip_entity_id, operation_sequence_number, inventory_item_id, required_quantity, completed_quantity FROM apps.wipbv_flow_sched_comps WHERE organization_id = :org_id AND operation_sequence_number = :op_seq ORDER BY wip_entity_id, inventory_item_id;

To compute open requirements:

  • SELECT wip_entity_id, operation_sequence_number, inventory_item_id, SUM(required_quantity) - SUM(completed_quantity) open_qty FROM apps.wipbv_flow_sched_comps WHERE organization_id = :org_id GROUP BY wip_entity_id, operation_sequence_number, inventory_item_id;

Analysts join the view to WIP_ENTITIES or WIP_FLOW_SCHEDULES on wip_entity_id to enrich results with schedule status and dates, and to MTL_SYSTEM_ITEMS for item descriptions. Organization security is enforced automatically through FND_GLOBAL, so queries respect the session's accessible organizations.