Search Results mrp_wip_rep_schd_view




Overview
Explore in AI Chat

Overview

MRP_WIP_REP_SCHD_VIEW is an APPS-owned view within the Oracle E-Business Suite Master Scheduling/MRP product family. It exposes Work in Process (WIP) repetitive schedule supply records that have not yet been consumed by the planning engine, presenting them in a denormalized form suitable for planning, reporting, and integration. The view combines columns from Work in Process repetitive scheduling tables with descriptive item attributes from the MRP system items table, so that a single query can return repetitive schedule supply along with item lead time and planning characteristics.

Within the planning architecture, WIP repetitive schedules represent a distinct class of supply. Discrete jobs and purchase orders supply demand in their own ways, but repetitive schedules generate production at a daily rate across a date range on a specific production line. MRP_WIP_REP_SCHD_VIEW normalizes this data for consumption by planning and reporting logic, and it is the standard reference point when supply from repetitive schedules must be surfaced outside of the standard planning workbench. The firm_planned_flag column, in particular, indicates whether a schedule has been firmed by the planner, which is critical because firmed schedules are typically treated as fixed supply and are not rescheduled by the planning engine.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms in the APPS schema: MRP_SYSTEM_ITEMS (aliased MRP_ITEMS), WIP_REPETITIVE_SCHEDULES (aliased SCHED), and WIP_REPETITIVE_ITEMS (aliased ITEMS). The joins connect them on organization, item, line, and work entity identifiers: MRP_ITEMS.ORGANIZATION_ID equals SCHED.ORGANIZATION_ID; MRP_ITEMS.INVENTORY_ITEM_ID equals ITEMS.PRIMARY_ITEM_ID; ITEMS.ORGANIZATION_ID equals SCHED.ORGANIZATION_ID; ITEMS.LINE_ID equals SCHED.LINE_ID; and ITEMS.WIP_ENTITY_ID equals SCHED.WIP_ENTITY_ID. In effect, WIP_REPETITIVE_ITEMS links the repetitive schedule to the primary inventory item, while MRP_SYSTEM_ITEMS contributes planning attributes such as full lead time and compile designator.

The view applies two important filters. First, it restricts to schedule statuses 1, 3, and 6, which correspond to active repetitive schedule states (typically released/pending and in-process states). Second, it requires SCHED.LAST_UNIT_COMPLETION_DATE to be greater than or equal to TRUNC(SYSDATE), so only schedules whose last unit completion is today or in the future appear. Schedules entirely in the past are therefore excluded from this supply view.

Key Columns

  • PRIMARY_ITEM_ID — inventory item identifier from WIP_REPETITIVE_ITEMS; the planning item key.
  • COMPILE_DESIGNATOR — engineering compile designator for the item.
  • ORGANIZATION_ID — inventory organization in which the schedule resides.
  • WIP_ENTITY_ID — WIP entity identifier for the repetitive schedule.
  • REPETITIVE_SCHEDULE_ID — unique identifier of the repetitive schedule.
  • LINE_ID — production line on which the schedule is executed.
  • FIRST_UNIT_START_DATE / FIRST_UNIT_COMPLETION_DATE — start and completion of the first unit.
  • LAST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE — start and completion of the last unit; the completion date governs inclusion in the view.
  • PROCESSING_WORK_DAYS — number of working days over which production occurs.
  • DAILY_PRODUCTION_RATE — units produced per day, the core supply quantity driver.
  • BOM_REVISION — bill of material revision used by the schedule.
  • STATUS_TYPE — schedule status, filtered to values 1, 3, and 6.
  • FIRM_PLANNED_FLAG — indicates whether the schedule is firmed for planning purposes; firmed supply is held fixed by the planner.
  • QUANTITY_COMPLETED — quantity already completed against the schedule.
  • FULL_LEAD_TIME — cumulative lead time from MRP_SYSTEM_ITEMS.
  • DEMAND_CLASS — demand classification used for planning and prioritization.

Common Use Cases and Queries

Typical uses include identifying firmed repetitive supply, reconciling planned versus actual production, and feeding external reporting or integration extracts. A representative query returns firmed schedules for a given organization and item:

SELECT organization_id, repetitive_schedule_id, line_id,
       daily_production_rate, first_unit_start_date,
       last_unit_completion_date, quantity_completed
FROM   apps.mrp_wip_rep_schd_view
WHERE  organization_id = :org_id
AND    primary_item_id = :item_id
AND    firm_planned_flag = 'Y'
ORDER BY last_unit_completion_date;

Planners commonly filter on STATUS_TYPE to isolate active schedules, or aggregate daily production rate across a production line to estimate capacity loading. Because the view already restricts to future completions, it can be used directly to build open-supply reports without additional date predicates. When integrating with external planning systems, the view serves as the authoritative source of repetitive schedule supply, and the firm_planned_flag column determines whether that supply may be rescheduled downstream.