Results for “mrp_items”

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

Overview

APPS.MRP_WIP_REP_SCHD_VIEW is a reporting view in Oracle E-Business Suite that consolidates repetitive manufacturing schedule information with the corresponding planning item attributes held in the MRP system items table. Its principal role is to expose open, future-dated repetitive schedules alongside the item master planning characteristics required by material requirements planning, capacity planning, and shop floor reporting processes. The view is owned by the APPS schema and is therefore accessible to any responsibility or concurrent program that operates against the application schema with the appropriate grants.

The view is deliberately filtered. Rather than presenting the full historical population of repetitive schedules, it returns only those schedules whose status indicates they are active or firmed — status types 1, 3, and 6 — and whose last unit completion date is on or after the current system date as evaluated by TRUNC(SYSDATE). This makes the view a forward-looking snapshot of repetitive production commitments. Because the user search term was "mrp_items," it is worth noting that the view joins the MRP system items table directly, making it a convenient bridge between repetitive schedule execution data and MRP planning attributes such as compile designator and full lead time.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over three referenced base objects, all exposed to the view owner through synonyms: MRP_SYSTEM_ITEMS, WIP_REPETITIVE_ITEMS, and WIP_REPETITIVE_SCHEDULES. The view text aliases these as MRP_ITEMS, ITEMS, and SCHED respectively.

• MRP_SYSTEM_ITEMS (MRP_ITEMS) — supplies the planning-level item attributes, joined to the schedule on ORGANIZATION_ID and, through the WIP_REPETITIVE_ITEMS alias, on INVENTORY_ITEM_ID matching ITEMS.PRIMARY_ITEM_ID.
• WIP_REPETITIVE_ITEMS (ITEMS) — provides the item-to-line and item-to-work-entity linkage, joining to SCHED on ORGANIZATION_ID, LINE_ID, and WIP_ENTITY_ID.
• WIP_REPETITIVE_SCHEDULES (SCHED) — the driving table, contributing schedule dates, rates, revisions, quantities, and status flags.

The join is fully correlated on organization, line, and work entity, ensuring that each row represents one item on one repetitive schedule within one inventory organization.

Key Columns

The projection includes identifiers and descriptive attributes from all three sources. Notable columns include:

• PRIMARY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR — item and organization identity plus the MRP compile designator.
• WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, LINE_ID — keys identifying the work entity, the repetitive schedule, and the production line.
• FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE — the span of the schedule.
• PROCESSING_WORK_DAYS, DAILY_PRODUCTION_RATE — capacity and throughput measures.
• BOM_REVISION, STATUS_TYPE, FIRM_PLANNED_FLAG, QUANTITY_COMPLETED — build context and progress information.
• FULL_LEAD_TIME — the cumulative lead time sourced from MRP_SYSTEM_ITEMS.
• DEMAND_CLASS — the demand classification carried on the schedule.

Common Use Cases and Queries

Typical usage includes repetitive schedule load reports, capacity versus rate analysis, and reconciling MRP-planned output with firm production commitments. A representative query is:

SELECT ORGANIZATION_ID, PRIMARY_ITEM_ID, REPETITIVE_SCHEDULE_ID, LINE_ID, DAILY_PRODUCTION_RATE, QUANTITY_COMPLETED, LAST_UNIT_COMPLETION_DATE FROM APPS.MRP_WIP_REP_SCHD_VIEW WHERE ORGANIZATION_ID = :org_id ORDER BY LAST_UNIT_COMPLETION_DATE;

To constrain by item, add a predicate on PRIMARY_ITEM_ID; to isolate firmed schedules, filter on FIRM_PLANNED_FLAG. Because the view already restricts to future-dated, active schedules, callers do not need to reapply the status or date conditions.