Search Results jai_po_osp_lines




Overview
Explore in AI Chat

Overview

The WIP_REPETITIVE_SCHEDULES table is a core transactional data store within the Oracle E-Business Suite Work in Process (WIP) module. It serves as the master record for all repetitive manufacturing schedules, a production method where discrete items are built continuously over a period of time on a dedicated production line, rather than as distinct jobs or lots. This table is central to the repetitive manufacturing flow, tracking the planned and actual production quantities, dates, and status for each schedule. Its integrity is critical for material consumption, cost collection, and production reporting in EBS releases 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list specific columns, the primary and foreign key relationships define its critical data elements. Each record is uniquely identified by the REPETITIVE_SCHEDULE_ID (primary key). The table links a schedule to its defining master data via foreign keys: WIP_ENTITY_ID and LINE_ID reference the assembly and production line defined in WIP_REPETITIVE_ITEMS. The COMMON_ROUTING_SEQUENCE_ID and COMMON_BOM_SEQUENCE_ID link to the approved routing (BOM_OPERATIONAL_ROUTINGS) and bill of material (BOM_STRUCTURES_B) used for the schedule. Typical data stored includes daily or periodic production rates, start and end dates, quantity scheduled, quantity completed, and status flags controlling transactions.

Common Use Cases and Queries

This table is queried extensively for production tracking, variance analysis, and period-end closing. Common operational reports include summarizing completed units versus planned schedules and identifying open schedules for a given line. A fundamental query retrieves schedule details for transaction processing:

  • SELECT wrs.repetitive_schedule_id, wrs.wip_entity_id, wrs.line_id, wrs.date_released, wrs.status_type, wrs.daily_production_rate FROM wip_repetitive_schedules wrs WHERE wrs.organization_id = :p_org_id AND wrs.line_id = :p_line_id AND wrs.status_type IN (3, 4); -- Released or Complete

For cost accounting, the table is joined to WIP_PERIOD_BALANCES to analyze variances. Integration points include material transactions (MTL_MATERIAL_TXN_ALLOCATIONS), move transactions (WIP_MOVE_TXN_ALLOCATIONS), and cost collection (CST_AE_LINES, WIP_TRANSACTION_ACCOUNTS), all of which reference the REPETITIVE_SCHEDULE_ID to tie transactions back to the specific production schedule.

Related Objects

As indicated by the foreign key constraints, WIP_REPETITIVE_SCHEDULES is a hub table with extensive integration. Key related objects include: