Results for “repetitive_daily_rate”

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

Overview

The APPS.MRP_SCHEDULE_DATES_V view is a reporting and integration layer within the Oracle E-Business Suite Master Scheduling/MRP module. Its function is to consolidate the schedule entries held in the base scheduling tables and present them with a set of decoded, business-friendly attributes that are not directly available on the underlying columns. The view joins schedule date records to item master flags, schedule consumption records, lookup translations, and organization parameters, producing a single denormalized result set suited to concurrent program logic, forms validation, and custom reporting.

The most significant behavior encoded in the view is its handling of repetitive versus discrete planning items. Using the REPETITIVE_PLANNING_FLAG from MTL_SYSTEM_ITEMS, the view conditionally suppresses or replaces quantity columns so that repetitive items expose a daily rate while discrete items expose an absolute quantity. This conditional logic makes the view the authoritative source for schedule quantity semantics across the module.

Underlying Base Objects

The view is defined over several documented objects. The primary driver is MRP_SCHEDULE_DATES (referenced through a synonym), which supplies the schedule entry rows including MPS_TRANSACTION_ID, SCHEDULE_LEVEL, SCHEDULE_DESIGNATOR, and SCHEDULE_DATE. MRP_SCHEDULE_CONSUMPTIONS is left-joined to determine whether relief transactions exist for a schedule entry, producing the RELIEF_FLAG through a DECODE over COUNT(TRANSACTION_ID). MTL_SYSTEM_ITEMS supplies the REPETITIVE_PLANNING_FLAG that governs the quantity DECODE expressions, and it also carries the inventory item context. MTL_PARAMETERS provides the ORGANIZATION_CODE for the source organization through the PARAM alias.

Two additional objects are documented as referenced: WIP_LINES, used in the relief-flag determination for work-in-process associated consumption, and MFG_LOOKUPS, which supplies the MEANING text for SCHEDULE_ORIGINATION_TYPE via the L alias, exposing it as SCHEDULE_ORIGINATION_TEXT. The MRP_GET_PROJECT package is also referenced, typically within the source designator or project derivation logic. Because the view reads from synonyms resolving to the MRP and INV schemas, it must be queried in the APPS context, and its result set respects the organization and item security of the invoking responsibility.

Key Columns

• ORIGINAL_QUANTITY — the column central to this object's documentation. It is derived as the repetitive daily rate for repetitive items, and otherwise as NVL(ORIGINAL_SCHEDULE_QUANTITY, SCHEDULE_QUANTITY). It therefore preserves the originally entered schedule quantity even after schedule quantity is subsequently revised.
• SCHEDULE_QUANTITY — returns NULL for repetitive items and the stored quantity for discrete items.
• REPETITIVE_DAILY_RATE — populated only for repetitive items; NULL otherwise.
• QUANTITY_OR_RATE — a unified measure that returns the daily rate for repetitive items and the schedule quantity for discrete items.
• RELIEF_FLAG — 'Y' or 'N', indicating whether schedule consumption records exist for the entry.
• SCHEDULE_DATE, SCHEDULE_WORKDATE, RATE_END_DATE — the effective dates governing the schedule entry.
• SCHEDULE_ORIGINATION_TEXT — decoded lookup meaning describing how the schedule was created.
• SOURCE_DESIGNATOR — resolved from forecast or source schedule designator depending on origination type.

Common Use Cases and Queries

The view is commonly used to report schedule entries with their correctly resolved quantities, to identify entries that have not been relieved, and to reconcile forecast and sales order sources against production schedules. A representative query retrieving original and current quantities for a schedule designator follows:

• SELECT inventory_item_id, organization_id, schedule_designator, schedule_date, original_quantity, schedule_quantity, quantity_or_rate, relief_flag FROM mrp_schedule_dates_v WHERE schedule_designator = :designator AND organization_id = :org_id ORDER BY schedule_date;
• To isolate unrelieved discrete entries: SELECT * FROM mrp_schedule_dates_v WHERE relief_flag = 'N' AND repetitive_daily_rate IS NULL;
• To compare original against revised planning quantities for repetitive items: SELECT inventory_item_id, original_quantity, repetitive_daily_rate FROM mrp_schedule_dates_v WHERE repetitive_daily_rate IS NOT NULL;

Because ORIGINAL_QUANTITY retains the pre-revision value, it is frequently used in variance reporting to measure schedule changes over time.