Search Results wip_flow_schedules

Overview

The WIP_FLOW_SCHEDULES table is a core transactional entity within the Oracle E-Business Suite Work in Process (WIP) module, specifically supporting flow manufacturing environments. It serves as the master repository for work order-less flow schedules, a key construct in lean and repetitive manufacturing. Unlike discrete jobs, which are tracked by individual work orders, flow schedules represent a continuous, rate-based production plan for a specific item over a defined period. This table stores all defining, scheduling, and accounting attributes for each schedule, enabling the system to manage material consumption, resource charging, and cost collection without the administrative overhead of discrete job creation and closure.

Key Information Stored

The table's structure captures the complete lifecycle and definition of a flow schedule. Its primary keys are WIP_ENTITY_ID (a unique internal identifier linking to WIP_ENTITIES) and a composite unique key of SCHEDULE_NUMBER and ORGANIZATION_ID for business reference. Critical columns include PRIMARY_ITEM_ID, QUANTITY, and STATUS_TYPE to define what and how much is being built. Scheduling data is held in START_DATE, DUE_DATE, and DATE_RELEASED columns. The table is integral to cost management, containing numerous General Ledger account columns such as MATERIAL_VARIANCE_ACCOUNT, RESOURCE_ACCOUNT, and OVERHEAD_VARIANCE_ACCOUNT. It also links to engineering and production definitions via BOM_REVISION, ALTERNATE_BOM_DESIGNATOR, ROUTING_REVISION, and ALTERNATE_ROUTING_DESIGNATOR.

Common Use Cases and Queries

This table is central to operational and financial reporting in flow manufacturing. Common use cases include generating shop floor schedules, tracking schedule completion progress, performing cost analysis, and reconciling inventory transactions. A typical query retrieves active schedules with their item and quantity details:

• SELECT wfs.schedule_number, wfs.primary_item_id, msib.concatenated_segments item, wfs.quantity, wfs.status_type, wfs.date_released FROM wip_flow_schedules wfs, mtl_system_items_b_kfv msib WHERE wfs.organization_id = :org_id AND wfs.primary_item_id = msib.inventory_item_id AND wfs.organization_id = msib.organization_id AND wfs.status_type IN (3, 4); -- Released or Complete

Another critical pattern involves joining to transaction and cost tables to analyze material usage or variance against a specific schedule, using WIP_ENTITY_ID as the key correlator.

Related Objects

WIP_FLOW_SCHEDULES maintains extensive foreign key relationships, as documented, integrating it deeply with other EBS modules. Key related objects include:

• WIP_ENTITIES: Joined on WIP_ENTITY_ID. This is the fundamental parent entity for all WIP jobs and schedules.
• MTL_SYSTEM_ITEMS_B: Joined on PRIMARY_ITEM_ID and ORGANIZATION_ID. Defines the item being manufactured.
• BOM_STRUCTURES_B & BOM_OPERATIONAL_ROUTINGS: Joined on PRIMARY_ITEM_ID, ORGANIZATION_ID, and alternate designators. Provide the bill of material and routing definitions.
• GL_CODE_COMBINATIONS: Multiple joins for various accounting segments (RESOURCE_ACCOUNT, MATERIAL_VARIANCE_ACCOUNT, etc.).
• MTL_ITEM_REVISIONS_B & MTL_RTG_ITEM_REVISIONS: Joined for specific BOM and routing revisions.
• MTL_KANBAN_CARDS: Joined on KANBAN_CARD_ID, linking pull-based replenishment signals to production.
• PJM_UNIT_NUMBERS: Joined on END_ITEM_UNIT_NUMBER for project manufacturing tracking.
• MTL_ITEM_LOCATIONS: Joined on COMPLETION_LOCATOR_ID for finished goods receipt.