Results for “repetitive_planning_flag”

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

Overview

MRP_SCHEDULE_ITEMS_V is an APPS-owned database view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It presents a denormalized, reporting-friendly projection of master schedule items, combining scheduling designator data from MRP_SCHEDULE_ITEMS with item master attributes from the system items tables. The view surfaces descriptive item attributes, time fence configurations, and schedule-specific assignments in a single queryable object, avoiding the need for repeated joins across the item master and scheduling tables.

The view is primarily consumed by concurrent programs, Oracle Discoverer worksheets, BI Publisher reports, and custom SQL used in master production scheduling and material requirements planning analysis. Because it joins MTL_SYSTEM_ITEMS_VL and MFG_LOOKUPS, output columns include translated item descriptions and lookup meanings, making it suitable for end-user-facing reports. The REPETITIVE_PLANNING_FLAG column, derived from MTL_SYSTEM_ITEMS and defaulted to 'N' via NVL, indicates whether the item is planned using repetitive manufacturing logic — a frequently searched attribute in planning diagnostics and item setup audits.

Underlying Base Objects

The view is defined over the following documented base objects:

• MRP_SCHEDULE_ITEMS — the primary source table supplying INVENTORY_ITEM_ID, ORGANIZATION_ID, SCHEDULE_DESIGNATOR, MPS_EXPLOSION_LEVEL, CAPACITY_MODEL_ID, and audit columns.
• MTL_SYSTEM_ITEMS_VL — supplies CONCATENATED_SEGMENTS (ITEM_NUMBER), DESCRIPTION, PRIMARY_UOM_CODE, BOM_ITEM_TYPE, MRP_PLANNING_CODE, and time fence attributes.
• MRP_SCHEDULE_DESIGNATORS — provides SCHEDULE_TYPE, which drives the DECODE logic that assigns either a demand or planning time fence date depending on schedule type.
• BOM_CALENDAR_DATES — the calendar reference (aliased CAL2) used to resolve actual time fence dates from lead-time and fence-day definitions.
• MFG_LOOKUPS — joined twice (L1 and L2) to translate BOM_ITEM_TYPE and MRP_PLANNING_CODE into their meanings.
• MRP_SYSTEM_ITEMS, MRP_ORGANIZATIONS_V, MTL_PARAMETERS — supporting organizational and planning context.

Key Columns

• ROW_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID — unique row and item/organization identifiers.
• ITEM_NUMBER, ITEM_DESCRIPTION, PRIMARY_UOM_CODE — item identification and unit of measure.
• REPETITIVE_PLANNING_FLAG — 'Y'/'N' indicator of repetitive planning applicability, NVL-defaulted to 'N'.
• DEMAND_TIME_FENCE_DAYS / PLANNING_TIME_FENCE_DAYS — fence durations, defaulted to 0.
• DEMAND_TIME_FENCE_DATE / PLANNING_TIME_FENCE_DATE — computed dates from calendar logic.
• SCHEDULE_DESIGNATOR, SCHEDULE_TYPE — the master schedule identifier and its type.
• BOM_ITEM_TYPE_TEXT, MRP_PLANNING_CODE_TEXT — lookup meanings for readability.
• MPS_EXPLOSION_LEVEL, CAPACITY_MODEL_ID — explosion and capacity settings.

Common Use Cases and Queries

Typical scenarios include identifying repetitive-planned items within a schedule, auditing time fence configuration, and validating planning codes ahead of a master schedule run.

SELECT item_number, item_description,
       repetitive_planning_flag,
       demand_time_fence_days, planning_time_fence_days
FROM   apps.mrp_schedule_items_v
WHERE  organization_id = :org_id
AND    schedule_designator = :designator
AND    repetitive_planning_flag = 'Y';

A time-fence audit query returns items whose fence dates fall within the current planning horizon:

SELECT item_number, schedule_designator,
       demand_time_fence_date, planning_time_fence_date
FROM   apps.mrp_schedule_items_v
WHERE  planning_time_fence_date >= SYSDATE
ORDER  BY planning_time_fence_date;

These queries make the view valuable for setup verification, exception reporting, and integration extracts destined for external planning systems.