Search Results demand_time_fence_date




Overview
Explore in AI Chat

Overview

APPS.MRPFV_MDS_ITEMS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, registered under FND Design Data as MRP.MRPFV_MDS_ITEMS and reported with a status of VALID. It presents the items that are members of a master demand schedule (MDS), exposing planning-relevant attributes in a denormalized, reporting-friendly form that joins schedule definitions, item master data, organization context, and calendar information into a single queryable object.

The view is read-only by design; the ETRM documentation notes that it is not referenced by any other database object, which confirms its role as a terminal reporting artifact rather than a dependency for other logic. It is therefore appropriate for ad hoc queries, custom concurrent programs, Oracle Discoverer workbooks, and downstream data extraction rather than for transactional processing. The view is available in both 12.1.1 and 12.2.2, with the documented APPS.BIS view metadata remaining consistent across those releases.

Underlying Base Objects

The view resolves against six base objects, each accessed through a SYNONYM in the APPS schema:

  • MRP_SCHEDULE_DESIGNATORS — supplies the schedule definition and name that identifies the master demand schedule.
  • MRP_SCHEDULE_ITEMS — the primary fact source, containing the item-to-schedule membership records.
  • MTL_SYSTEM_ITEMS — provides item attributes such as description, primary unit of measure, planning method, bill type, and repetitive flag.
  • MTL_PARAMETERS — supplies organization-level inventory parameters and the organization code used in the output.
  • HR_ALL_ORGANIZATION_UNITS — resolves the organization name associated with the operating unit or inventory organization.
  • BOM_CALENDAR_DATES — supports calendar and date derivations, including the demand time fence date exposed by the view.

Because these are all synonymous references, the view presents a consolidated planning picture without requiring the caller to reproduce the underlying join logic.

Key Columns

The view exposes descriptive, organizational, and planning-control columns:

  • ORGANIZATION_CODE / ORGANIZATION_NAME / ORGANIZATION_ID — identify the inventory organization and provide both a short code and a descriptive name.
  • SCHEDULE_NAME — the master demand schedule to which the item belongs.
  • _KF:ITEM_NUMBER — the flexfield-qualified item number key, the primary human-readable item identifier.
  • DESCRIPTION — the item description from the item master.
  • PRIMARY_UOM — the item's primary unit of measure.
  • DEMAND_TIME_FENCE_DATE — the date that marks the demand time fence boundary for the item within the schedule; demand inside this fence is typically firm and changes are restricted by planning rules. This column is the direct answer to the searched term.
  • _LA:BILL_TYPE, _LA:PLANNING_METHOD, _LA:REPETITIVE_FLAG — lookup-attribute columns that resolve the item's bill type, planning method (for example, MRP, MPS, or not planned), and whether the item is planned repetitively.
  • _DF — a descriptive flexfield attribute column.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

Typical uses include auditing MDS membership, verifying planning attributes for items on a schedule, and reporting demand time fence boundaries for supply chain planning reviews.

  • List items on a given master demand schedule with their demand time fence dates:
SELECT organization_code,
       organization_name,
       schedule_name,
       _KF:ITEM_NUMBER   AS item_number,
       description,
       primary_uom,
       demand_time_fence_date
FROM   apps.mrpfv_mds_items
WHERE  schedule_name = :p_schedule_name
ORDER  BY item_number;
  • Identify items whose demand time fence date falls within a horizon of interest:
SELECT organization_code,
       schedule_name,
       _KF:ITEM_NUMBER       AS item_number,
       _LA:PLANNING_METHOD   AS planning_method,
       demand_time_fence_date
FROM   apps.mrpfv_mds_items
WHERE  demand_time_fence_date BETWEEN :p_start_date AND :p_end_date;
  • Audit planning method and repetitive flag distribution across schedules:
SELECT schedule_name,
       _LA:PLANNING_METHOD   AS planning_method,
       _LA:REPETITIVE_FLAG   AS repetitive_flag,
       COUNT(*)              AS item_count
FROM   apps.mrpfv_mds_items
GROUP  BY schedule_name,
          _LA:PLANNING_METHOD,
          _LA:REPETITIVE_FLAG;

Because the view is not referenced by any database object, it can be queried freely without risk of impacting planning logic, making it suitable for both production reporting and diagnostic analysis.