Search Results bom_revision_date




Overview
Explore in AI Chat

Overview

WIP_REPETITIVE_SCHEDULES is the master table for repetitive manufacturing schedules in Oracle Work in Process (WIP). A repetitive schedule represents a production run for an assembly on a specific production line over a defined date range, as opposed to a discrete job, which is a single, bounded work order. Where discrete jobs track a fixed quantity of an assembly, a repetitive schedule defines a daily production rate that is spread across processing work days over the schedule's interval. This table is central to repetitive manufacturing environments such as electronics, automotive components, and consumer goods, where the same assembly is built continuously over a planning horizon.

Each row in WIP_REPETITIVE_SCHEDULES anchors a single repetitive schedule and stores its routing, bill of materials, status, scheduling dates, completion quantities, and the full set of accounting flexfield references used to charge and relieve WIP costs. The table is the parent of the schedule's operations, resource requirements, material requirements, move transactions, and cost transactions, and it is referenced extensively by costing, planning, purchasing, and shop-floor execution modules. From a Data Vault modeling perspective, ETRM classifies this object heuristically as a hub, since it carries a stable surrogate business key (REPETITIVE_SCHEDULE_ID) around which many dependent links and satellites cluster.

Key Information Stored

The surrogate primary key is REPETITIVE_SCHEDULE_ID, defined by the constraint WIP_REPETITIVE_SCHEDULES_PK. A unique index, WIP_REPETITIVE_SCHEDULES_U1, spans REPETITIVE_SCHEDULE_ID and ORGANIZATION_ID, confirming the schedule's identity is scoped to a single inventory organization and serving as a business-key candidate.

Common Use Cases and Queries

Repetitive schedules are queried most often for shop-floor dashboards, cost reporting, and planning reconciliation. A typical query retrieves active schedules for an organization by joining the item and line:

SELECT wrs.repetitive_schedule_id, wri.assembly_name,
       wrs.daily_production_rate, wrs.status_type,
       wrs.first_unit_start_date, wrs.last_unit_completion_date
FROM   wip.wip_repetitive_schedules wrs,
       wip.wip_repetitive_items wri
WHERE  wrs.wip_entity_id = wri.wip_entity_id
AND    wrs.organization_id = :org_id
AND    wrs.status_type IN ('RELEASED','UNRELEASED');

Cost analysts use WIP_PERIOD_BALANCES, WIP_TRANSACTION_ACCOUNTS, and CST_WIP_LAYERS filtered on REPETITIVE_SCHEDULE_ID to reconcile period WIP balances and variances. Supply chain planners interrogate MRP_AD_REPT_SCHDS and MSC_DEMANDS to verify that schedule demand has flowed into planning. Completion and scrap analysis joins QUANTITY_COMPLETED to WIP_MOVE_TXN_ALLOCATIONS and MTL_MATERIAL_TXN_ALLOCATIONS for material movement tracing. Purchasing teams look up PO_REQUISITION_LINES_ALL.WIP_REPETITIVE_SCHEDULE_ID when outside-processing requisitions originate from a repetitive schedule.

Related Objects

The most significant foreign-key relationships are:

  • WIP_REPETITIVE_ITEMS – joined on WIP_ENTITY_ID (and LINE_ID); holds the assembly and line identity for the schedule.
  • BOM_STRUCTURES_B and BOM_OPERATIONAL_ROUTINGS – joined via COMMON_BOM_SEQUENCE_ID and COMMON_ROUTING_SEQUENCE_ID to resolve the bill and routing.
  • WIP_OPERATIONS, WIP_REQUIREMENT_OPERATIONS, WIP_MOVE_TXN_ALLOCATIONS – the shop-floor operations and move transactions that execute the schedule.
  • WIP_PERIOD_BALANCES, WIP_TRANSACTION_ACCOUNTS, CST_WIP_LAYERS, CST_AE_LINES – WIP and cost accounting records keyed by REPETITIVE_SCHEDULE_ID.
  • MTL_MATERIAL_TXN_ALLOCATIONS and MTL_TRANSACTION_ACCOUNTS – material issue and accounting distribution linkage.
  • PO_REQUISITION_LINES_ALL – outside-processing requisitions generated from the schedule.
  • WIP_JOB_SCHEDULE_INTERFACE and WIP_MOVE_TXN_INTERFACE – open interfaces for importing and transacting schedule data.
  • MRP_AD_REPT_SCHDS, MSC_DEMANDS, and MRP_AD_REPT_ITEM_DEMANDS – planning demand records that reference the schedule.

Together these relationships establish WIP_REPETITIVE_SCHEDULES as the operational and accounting hub for repetitive manufacturing in Oracle E-Business Suite 12.1.1 and 12.2.2.