Results for “demand_time_fence_date”

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

Overview

MRPFV_MDS_ITEMS is an APPS-owned Oracle E-Business Suite view within the MRP (Master Scheduling/MRP) product family. It is identified in the ETRM metadata as a retrofitted database object, meaning it was originally introduced under an earlier EBS release and subsequently re-implemented or preserved to retain backward compatibility within the 12.1.1 and 12.2.2 code lines. The view presents item-level detail scoped to Master Demand Schedules (MDS), exposing the combination of organization, schedule designator, item attributes, and the calculated demand time fence date at which each scheduled item becomes relevant to the planning horizon.

The embedded leading underscore tokens in the view text (for example _KF:INV:MSTK:SY, _LA:SY.BOM_ITEM_TYPE:MFG_LOOKUPS:BOM_ITEM_TYPE:MEANING, and _DF:MRP:MRP_SCHEDULE_ITEMS:SCIT) indicate that the view is a Flexfield/Descriptive Flexfield-aware construct used by Oracle's generic reporting and integration layers. These markers instruct the reporting engine to resolve key flexfield segments, lookup meanings, and descriptive flexfield contexts at runtime, so the view functions as a metadata-driven data source rather than a plain relational projection. In practical terms, MRPFV_MDS_ITEMS serves as a reporting and integration access point for MDS item content consumed by planning reports, custom concurrent programs, and downstream planning extracts.

Underlying Base Objects

The ETRM documentation confirms that the view is defined over six referenced base objects, all resolved through APPS synonyms:

• MRP_SCHEDULE_ITEMS (alias SCIT) — the driving table; supplies ORGANIZATION_ID, INVENTORY_ITEM_ID, SCHEDULE_DESIGNATOR, and audit columns.
• MRP_SCHEDULE_DESIGNATORS (alias SC) — provides SCHEDULE_TYPE and joins to the schedule item rows on organization and designator.
• MTL_SYSTEM_ITEMS (alias SY) — supplies item description, PRIMARY_UOM_CODE, planning attributes, and time fence definitions.
• MTL_PARAMETERS (alias PA) — supplies the calendar code and calendar exception set used for date derivation.
• HR_ALL_ORGANIZATION_UNITS (alias AL) — supplies the organization NAME for reporting presentation.
• BOM_CALENDAR_DATES (aliases CAL1 and CAL2) — used twice to anchor the current date and to compute the demand time fence date by advancing the calendar sequence.

The join conditions restrict output to schedule designators where SCHEDULE_TYPE = 1, ensuring only MDS-type schedules are returned. The CAL1 instance is pinned to TRUNC(SYSDATE), and CAL2 is offset by the calendar sequence equal to the prior sequence number plus the applicable time fence value derived from the item's DEMAND_TIME_FENCE_CODE.

Key Columns

• ORGANIZATION_CODE — operating unit/organization identifier from MTL_PARAMETERS.
• NAME — organization name from HR_ALL_ORGANIZATION_UNITS.
• SCHEDULE_DESIGNATOR — the MDS designator to which the item belongs.
• SY.DESCRIPTION — item description from MTL_SYSTEM_ITEMS.
• SY.PRIMARY_UOM_CODE — primary unit of measure for the item.
• Demand time fence date — a computed column derived via DECODE on SCHEDULE_TYPE and DEMAND_TIME_FENCE_CODE, using CAL2.CALENDAR_DATE.
• BOM_ITEM_TYPE, MRP_PLANNING_CODE, REPETITIVE_PLANNING_FLAG meanings — lookup-resolved columns delivered through the underscore token mechanism.
• ORGANIZATION_ID, INVENTORY_ITEM_ID — composite key columns supporting downstream joins.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns from MRP_SCHEDULE_ITEMS.

Common Use Cases and Queries

Typical uses include MDS item verification, calendar-based demand time fence reporting, and integration extracts feeding planning or external scheduling systems. Because the demand time fence date is computed against the current date, queries are inherently time-sensitive.

A representative query listing MDS items for a specific organization and designator:

SELECT organization_code, name, schedule_designator, description,
  primary_uom_code, organization_id, inventory_item_id
FROM apps.mrpfv_mds_items
WHERE organization_code = :p_org
  AND schedule_designator = :p_designator
ORDER BY inventory_item_id;

A second scenario retrieves item-level planning attributes for audit or exception review:

SELECT inventory_item_id, description, primary_uom_code,
  last_update_date, last_updated_by
FROM apps.mrpfv_mds_items
WHERE organization_id = :p_org_id
  AND last_update_date >= :p_since_date;

Because the view depends on BOM_CALENDAR_DATES for the current workday and the time fence offset, results should be interpreted alongside the organization calendar definition. Reports that must be reproducible across dates should persist the extracted rows rather than re-querying the view at a later time.