Results for “mrp_ap_calendar_dates_v”

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

Overview

MRP_AP_CALENDAR_DATES_V is a reporting view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It exposes the expanded, date-by-date definition of workday calendars used by the MRP planning engine, combined with the header-level attributes of each calendar. Its primary role is to provide planning, capacity, and shop-floor consumers with a flat, query-friendly representation of production calendars — including open and closed dates, sequence relationships between consecutive dates, and exception set associations.

The view is especially relevant to searches for calendar_start_date, since it surfaces CALENDAR_START_DATE from the calendar header together with the individual date rows. This allows a single query to retrieve both the boundary dates of a calendar and the daily records that fall within them. In Oracle EBS 12.1.1 and 12.2.2, such views are typically leveraged by reports, interfaces, and custom planning logic that need to know which days are workdays versus non-workdays.

Underlying Base Objects

The documented view text shows that MRP_AP_CALENDAR_DATES_V is defined over three base segments:

• MRP_AP_CLDRS_SN — the calendar header table, aliased BC. It supplies CALENDAR_START_DATE, CALENDAR_END_DATE, QUARTERLY_CALENDAR_TYPE, DAYS_ON, DAYS_OFF, DESCRIPTION, and the RN4 row identifier.
• MRP_AP_CLDR_DATES_SN — the calendar date detail table, aliased BCD. It supplies CALENDAR_DATE, SEQ_NUM, NEXT_SEQ_NUM, PRIOR_SEQ_NUM, NEXT_DATE, PRIOR_DATE, and RN3.
• An inline aggregate (Y) — built from MRP_AP_MTL_PARAS_SN and MRP_AP_MRP_PARAS_SN, grouped by CALENDAR_CODE and CALENDAR_EXCEPTION_SET_ID, yielding RN1 and RN2.

Joins connect BCD to BC on CALENDAR_CODE, and BCD to Y on both CALENDAR_CODE and EXCEPTION_SET_ID. The ETRM metadata for version 12.2.2 records no separately documented base objects and notes that the view is "Not implemented in this database" in the reference environment, meaning the object may not be deployed in every instance and its presence should be verified before use.

Key Columns

• CALENDAR_DATE — the individual date represented by each detail row, forming the granular axis of the calendar.
• CALENDAR_CODE / EXCEPTION_SET_ID — identifiers linking the date to a specific calendar and its exception set; these are the primary filtering keys.
• CALENDAR_START_DATE / CALENDAR_END_DATE — header-level effective boundaries of the calendar, sourced from BC.
• SEQ_NUM, NEXT_SEQ_NUM, PRIOR_SEQ_NUM, NEXT_DATE, PRIOR_DATE — sequence and adjacency metadata enabling traversal from one date to the next or prior date without window functions.
• DAYS_ON / DAYS_OFF — indicators of whether the calendar day is a working day (on) or non-working day (off).
• QUARTERLY_CALENDAR_TYPE, DESCRIPTION — descriptive attributes of the calendar header.
• RN1–RN4 — internal row identifiers used for deduplication or ordering in the view definition.

Common Use Cases and Queries

The view is commonly used to determine workday/non-workday status for capacity planning, to derive date ranges around a calendar start date, and to drive scheduling interfaces that need adjacent-date lookups.

• Listing calendar boundaries: select distinct CALENDAR_CODE, CALENDAR_START_DATE, CALENDAR_END_DATE from the view.
• Retrieving workdays within a range: filter on CALENDAR_DATE between two dates and on DAYS_ON.
• Adjacency traversal: use NEXT_DATE or PRIOR_DATE instead of analytic LAG/LEAD functions.

A representative query:

SELECT CALENDAR_CODE, CALENDAR_START_DATE, CALENDAR_DATE, DAYS_ON, NEXT_DATE
FROM MRP_AP_CALENDAR_DATES_V
WHERE CALENDAR_CODE = :code
AND CALENDAR_DATE BETWEEN :start_date AND :end_date
ORDER BY SEQ_NUM;

Because the view is not guaranteed to be implemented in all databases, availability should be confirmed against the target instance before it is referenced in production SQL.