Search Results msc_ds_schedule




Overview
Explore in AI Chat

Overview

MSC_DS_SCHEDULE is a PL/SQL package owned by the APPS schema that forms part of the Oracle Advanced Supply Chain Planning (ASCP) data collection and reporting infrastructure. In Oracle EBS 12.1.1 and 12.2.2, the MSC prefix denotes objects belonging to the MSC (Manufacturing and Supply Chain) product family, and this package is closely associated with the MSC_DS_* family of "Decision Support" or dashboard-style reporting utilities that surface planning results to planners and supply chain analysts. Its documented procedures return aggregated and detailed views of planning data, specifically schedule summaries, late supply positions, and resource utilization, which are the operational metrics planners monitor when reviewing a plan. The package exposes its output through a small, well-defined API rather than through direct table access, allowing the planning dashboards and concurrent programs that depend on it to retrieve consistent, pre-calculated results. The ETRM record classifies the package as API classification OTHER, indicating it is not a public open-interface API in the sense of an integration or extension entry point, but rather an internal package whose procedures are called by Oracle's own planning UI and concurrent processes. It references SYS.STANDARD and is self-referencing in the dependency chain, confirming it is a standalone package with no upstream APPS package dependencies of note.

Key Procedures and Functions

The documented API surface consists of five procedures and functions, all of which return planning performance data in either summary or detail form:

  • GETSCHEDULESUMMARY — Returns a consolidated summary of the plan schedule, providing planners with high-level status information across the planning horizon.
  • GETLATESUPPLYDETAILS — Returns detail-level records identifying supply orders or receipts that are late relative to demand requirements, supporting exception management and expediting decisions.
  • GETLATESUPPLYSUMMARY — Returns an aggregated view of the same late supply information, suitable for dashboard display and trend analysis.
  • GETRESUTILSUMMARY — Returns a summary of resource utilization, showing how capacity is consumed against available resource time at an aggregate level.
  • GETRESUTILDETAILS — Returns detail-level resource utilization records, typically per resource, department, and time bucket, enabling drill-down from the summary view.

The deliberate pairing of summary and detail procedures across both late supply and resource utilization indicates the package is designed to support progressive drill-down reporting. No parameter lists are documented in the ETRM metadata, and none are asserted here.

Tables Accessed

The package reads from several ASCP and Bills of Material/planning tables through APPS synonyms:

  • MSC_BIS_PLAN_SUMMARY_KPI — Stores plan-level key performance indicator summaries, the primary source for GETSCHEDULESUMMARY and related summary procedures.
  • MSC_BIS_RES_SUMMARY — Holds pre-aggregated resource summary data used by the resource utilization procedures.
  • MSC_DEPARTMENT_RESOURCES — Defines the resources associated with departments, providing the resource dimension used to resolve utilization detail.
  • MSC_PLANS — The plan definition table, used to identify the active or selected plan whose schedule and metrics are being reported.
  • PLITBLM — A numeric table (the standard "PLITBLM" number table) typically used within PL/SQL for array-based processing or IN-list expansion rather than as a data source.

Consistent with a reporting-oriented package, the access pattern is predominantly read-only against the BIS summary tables, with PLITBLM used as a utility construct.

Usage Notes

MSC_DS_SCHEDULE is invoked internally by Oracle's planning dashboards and by concurrent programs that populate or refresh planning reporting regions, rather than being called directly by end users. Because the ETRM record shows it is referenced by no other APPS packages, it is a leaf dependency within PL/SQL and does not serve as a building block for other packages. Customizations that require schedule, late supply, or resource utilization data should treat these procedures as read-only reporting entry points and should not attempt to modify their logic. When extending planning reports, developers typically call the summary procedures for headline figures and the corresponding detail procedures to populate drill-down blocks. Given the "OTHER" API classification, the procedures carry no Oracle-supported interface guarantee, and any custom code depending on them should be regression-tested during EBS upgrades between 12.1.1 and 12.2.2.