Results for “type_weekly_bucket”

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

Overview

The APPS.MRP_CALENDAR package body is a core Oracle E-Business Suite utility that provides calendar arithmetic against the manufacturing and production calendars defined within Oracle Bills of Material. Its principal business function is to translate calendar-relative terms — work days, off days, period start dates, and week start dates — into concrete dates so that planning, scheduling, and shop floor processes operate against the same time basis. The package is classified as OTHER in the ETRM registry and is owned by the APPS schema with a status of VALID, indicating that it compiles cleanly in both Oracle EBS 12.1.1 and 12.2.2.

MRP_CALENDAR is heavily reused across the application: ETRM documents that it is referenced by 31 other packages. This makes it a foundational dependency for any module that must determine whether a given date is a working day or must advance a date by a defined number of working days. Although it is not referenced by any database object outside these dependent packages, its influence extends throughout planning and manufacturing logic.

Key Procedures and Functions

The package exposes five documented program units:

• NEXT_WORK_DAY — Returns the next valid working day on the applicable calendar, skipping designated non-working days. It is used to push a reference date forward to the nearest productive day.
• PREV_WORK_DAY — Returns the prior valid working day, mirroring NEXT_WORK_DAY in the backwards direction for scheduling and back-dating scenarios.
• DATE_OFFSET — Advances or retreats a supplied date by a specified number of working days, honoring the calendar's working-day definitions rather than simple calendar-day arithmetic.
• DAYS_BETWEEN — Computes the number of working days between two dates, providing the basis for duration and lead-time calculations.
• SELECT_CALENDAR_DEFAULTS — Resolves and returns the default calendar context, drawing on profile options and manufacturing parameters so that the other routines operate against the correct organizational calendar.

Parameter lists are not documented in the ETRM excerpt and are therefore not reproduced here.

Tables Accessed

The package reads from the following tables (through APPS synonyms):

• BOM_CALENDAR_DATES — The primary calendar date store, holding individual working and non-working day flags used by NEXT_WORK_DAY, PREV_WORK_DAY, DATE_OFFSET, and DAYS_BETWEEN.
• BOM_CAL_WEEK_START_DATES — Provides week start boundaries referenced when aligning planning buckets to calendar weeks.
• BOM_PERIOD_START_DATES — Supplies period start boundaries for period-based calendar logic.
• MTL_PARAMETERS — Supplies organizational defaults, including the default calendar identifier used by SELECT_CALENDAR_DEFAULTS.

Supporting dependencies include FND_MESSAGE, FND_PROFILE, and APP_EXCEPTION for error messaging and profile retrieval. No standalone database object references MRP_CALENDAR outside the 31 dependent packages.

Usage Notes

MRP_CALENDAR is typically invoked indirectly. Dependent packages in planning, manufacturing, and scheduling call its functions to normalize dates before performing their own computations, ensuring consistency across modules. It is not designed as an end-user interface; no forms or concurrent programs call it directly. Custom extensions should invoke it only through its documented procedures rather than reimplementing calendar logic, preserving consistency with the Oracle calendar model. Because the package is VALID and stable across 12.1.1 and 12.2.2, custom code that depends on it can generally be migrated between those releases without alteration.