Results for “completed_quantity”

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

Overview

WIPFV_FLOW_SCHED_COMPS is a reporting view owned by the APPS schema within the Work in Process (WIP) product of Oracle E-Business Suite. It exposes component-level supply and demand detail for flow manufacturing schedules. Specifically, the view flattens the bill of material (BOM) explosion for flow scheduled assemblies and presents, per manufacturing order and operation sequence, the total component quantity required by the schedule. Because it is defined as a view and not a table, it holds no persistent data; its contents are derived at query time by joining flow schedule headers to their associated BOM structures.

The view is intended primarily for reporting and lightweight integration scenarios where a denormalized, human-readable picture of flow schedule component requirements is needed. It is available in both 12.1.1 and 12.2.2, with the same definition in the APPS schema. The presence of ORGANIZATION_CODE, ORGANIZATION_NAME, and MFG_ORDER_NAME confirms its orientation toward end-user reporting rather than internal processing.

Underlying Base Objects

The ETRM metadata documents the following referenced objects: BOM_BILL_OF_MATERIALS (VIEW), BOM_EXPLOSIONS (SYNONYM), BOM_INVENTORY_COMPONENTS (VIEW), FND_GLOBAL (PACKAGE), HR_ALL_ORGANIZATION_UNITS (SYNONYM), MTL_MATERIAL_TRANSACTIONS (SYNONYM), MTL_PARAMETERS (SYNONYM), MTL_SYSTEM_ITEMS (SYNONYM), WIP_ENTITIES (SYNONYM), and WIP_FLOW_SCHEDULES (SYNONYM).

The view text joins MTL_PARAMETERS to HR_ALL_ORGANIZATION_UNITS for organization identification, WIP_FLOW_SCHEDULES to WIP_ENTITIES for the manufacturing order context, and MTL_SYSTEM_ITEMS to BOM_INVENTORY_COMPONENTS and BOM_EXPLOSIONS to derive the component explosion. BOM_BILL_OF_MATERIALS supplies the BOM header and alternate designator logic. The planning filter SYS.PLANNING_MAKE_BUY_CODE = 1 restricts the explosion to make items. Effectivity is applied by comparing EXPL.EFFECTIVITY_DATE and EXPL.DISABLE_DATE to TRUNC(FLOW.SCHEDULED_START_DATE), and the explosion is restricted to EXPL.EXPLOSION_TYPE = 'ALL'. FND_GLOBAL is referenced to supply the current organization context.

Key Columns

• ORGANIZATION_CODE / ORGANIZATION_NAME — The inventory organization in which the flow schedule resides, using the short code and full organization name.
• MFG_ORDER_NAME — The WIP entity name of the flow schedule, i.e., the manufacturing order identifier.
• OPERATION_SEQUENCE_NUMBER — The operation sequence at which the component is consumed.
• REQUIRED_QUANTITY — The component quantity required, computed as EXPL.COMPONENT_QUANTITY multiplied by FLOW.PLANNED_QUANTITY and aggregated with SUM across the outer query.
• COMPLETED_QUANTITY — Hard-coded as 0 in the inner query; the view does not derive issued or completed component quantity from MTL_MATERIAL_TRANSACTIONS.
• WIP_ENTITY_ID — The flow schedule's WIP entity identifier, usable to join back to WIP_ENTITIES.
• COMPONENT_SEQUENCE_ID — Identifier for the BOM component line.
• INVENTORY_ITEM_ID — The component item identifier.
• ORGANIZATION_ID — The inventory organization identifier for the schedule.

Common Use Cases and Queries

Typical uses include component requirement reporting for flow schedules, comparison of required versus on-hand or issued quantities, and ad hoc extraction to downstream planning or shop-floor systems. Because COMPLETED_QUANTITY is always zero, the view is best used for requirement-side reporting; issuance information must be sourced separately from the transaction tables.

A basic query lists all component requirements for an organization:

• SELECT MFG_ORDER_NAME, OPERATION_SEQUENCE_NUMBER, INVENTORY_ITEM_ID, REQUIRED_QUANTITY FROM APPS.WIPFV_FLOW_SCHED_COMPS WHERE ORGANIZATION_CODE = :org ORDER BY MFG_ORDER_NAME, OPERATION_SEQUENCE_NUMBER;

A second common pattern aggregates total requirements by component across open orders:

• SELECT INVENTORY_ITEM_ID, SUM(REQUIRED_QUANTITY) TOTAL_REQUIRED FROM APPS.WIPFV_FLOW_SCHED_COMPS WHERE ORGANIZATION_ID = :org_id GROUP BY INVENTORY_ITEM_ID ORDER BY TOTAL_REQUIRED DESC;

A third pattern joins the view to MTL_SYSTEM_ITEMS for descriptive component detail and to WIP_ENTITIES to obtain schedule status. As the view is read-only and aggregates BOM explosion output, queries should be filtered by organization and date to limit the volume of explosion rows returned, particularly in environments with many active flow schedules.