Search Results msc_hub_calendar




Overview
Explore in AI Chat

Overview

MSC_HUB_CALENDAR is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It forms part of the Oracle Advanced Supply Chain Planning (ASCP) and MSC (Manufacturing Supply Chain) schema, which underpins the planning engine and the planning data model in both EBS 12.1.1 and 12.2.2. The package is classified as OTHER and is not exposed as an open public API; it is an internal utility used by the planning server and related programs to resolve calendar-based date logic against the planning repository.

The central business function served by MSC_HUB_CALENDAR is the translation of planning calendars, workday definitions, and bucket boundaries into concrete dates. Planning activities such as scheduling, lead-time offsetting, safety stock placement, and plan bucketing require accurate answers to questions such as "what is the first workday in this period," "what is the last workday," and "into which bucket does this date fall." Rather than recompute these answers ad hoc, the planning code base funnels such requests through MSC_HUB_CALENDAR. The package therefore acts as a hub for calendar-derived date computation, consistent with its name.

Key Procedures and Functions

The documented package exposes seven procedures and functions. Their names, together with the objects they touch, indicate the following purposes:

  • FIRST_WORK_DATE — Returns the first eligible working date, typically within a given calendar or bucket, so that planning logic can anchor schedules to a valid workday.
  • LAST_WORK_DATE — Returns the last eligible working date for the corresponding interval, used to close out a bucket or schedule window.
  • SS_DATE — Resolves the effective date associated with safety stock processing, aligning safety stock placement with the calendar in force.
  • WORKING_DAY_BKT_START_DATE — Determines the start date of the bucket that contains a given working day, linking individual workdays to plan bucket boundaries.
  • GET_ITEM_ORG — Retrieves the item and organization context required by the date calculations, since calendars in MSC are held at the organization, item, and trading-partner level.

The remaining two documented procedures are additional calendar utility entry points that support the same date-resolution family. No parameter lists are documented in the available metadata, so signatures should be confirmed directly from the package specification before any custom invocation.

Tables Accessed

MSC_HUB_CALENDAR reads and writes through APPS synonyms to the following planning tables:

  • MSC_CALENDARS — the calendar header definitions, including workday patterns and the ranges within which calendars apply.
  • MSC_CALENDAR_DATES — the individual dated entries that designate working and non-working days.
  • MSC_CAL_WEEK_START_DATES — week start anchors used to align weekly buckets and calendar weeks.
  • MSC_PERIOD_START_DATES — period start dates that seed bucket boundaries for period-level planning.
  • MSC_PLANS — plan definitions, since bucket types and calendar assignments are plan-dependent.
  • MSC_PLAN_BUCKETS — bucket definitions used to map dates into planning periods.
  • MSC_SAFETY_STOCKS — safety stock records whose effective dates are resolved against the calendar.
  • MSC_SYSTEM_ITEMS — item-level attributes needed to select the correct item-organization calendar context.
  • MSC_TRADING_PARTNERS — partner-specific calendars used in supplier and customer scheduling.
  • FND_PROFILE — profile option lookups that influence planning behavior at runtime.

Usage Notes

MSC_HUB_CALENDAR is typically invoked internally by the planning engine and by companion MSC packages rather than directly from Oracle Forms or concurrent program parameters. The ETRM metadata records that it is referenced by six other database objects, indicating its role as a shared utility across the planning code base; it is not referenced by any non-package object. Standard dependencies include FND_PROFILE and the SYS STANDARD package.

Because the package is not an open interface, customizations should avoid calling it directly where a supported API exists. Where direct calls are unavoidable—for example, in custom planning extracts or reports that must reproduce bucket start and end dates—the safest approach is to wrap the calls and validate results against the plan bucket definitions in MSC_PLAN_BUCKETS. The package is marked VALID in the documented release, and no invalid or recompilation concerns are noted. Any upgrade from 12.1.1 to 12.2.2 should include a recompile check, since the underlying MSC tables are shared across both releases and the package depends on the same column semantics in each.