Results for “schedule_retrieve”

16 results




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

Overview

The APPS.MSC_ANALYSIS_BUDGET package body is a component of the Oracle Advanced Supply Chain Planning (ASCP) module within Oracle E-Business Suite. Its primary business function is to support budget-versus-service-level analysis within the planning engine. The package assembles planning buckets — arrays keyed by plan, organization, category, and time period — and computes measures such as achieved budget in USD, delivered and required quantities, and target service levels. These measures feed analytical dashboards and reports that allow planners to evaluate trade-offs between cost (budget) and customer service performance across a planning horizon. The package defines a rich record structure (Bucket) and collection types (Schedule, PlanList) that encapsulate the plan-instance context, bucket key dates, and computed budget/service-level metrics in a single structure, indicating it acts as a data-access and calculation layer rather than a user-facing API.

Key Procedures and Functions

ETRM documents two public program units for this package:

  • GET_CUSTOMER_TARGET_SL — Accepts a customer identifier and returns the target service level configured for that trading partner. Internally it queries MSC_TRADING_PARTNERS for records where the partner type indicates a customer, retrieving the stored service_level value. This function allows downstream analysis to compare planned or delivered service against each customer's contractual service target.
  • SCHEDULE_RETRIEVE — Retrieves a schedule of planning buckets (the Schedule collection of Bucket records) for a given plan and instance context, populating budget and service-level measures. It is the principal entry point for consuming code that requires the assembled analytical data set.

Numerous package-level constants (record types, calendar types, bucket types, budget-constrained flags, and an undefined customer code used in Java integration) and a debugging flag are declared but are not exposed as callable APIs.

Tables Accessed

The package reads from a defined set of ASCP and planning tables via APPS synonyms:

Usage Notes

This package is classified as OTHER in ETRM and is not listed as referenced by any other package, indicating it is consumed primarily by the Java-based planning analytics layer rather than by other PL/SQL units. The presence of the UNDEFINED_CUSTOMER_CODE constant with the comment "Used in Java" confirms that the package feeds the ASCP web-based analytical dashboards, where the Java middle tier invokes SCHEDULE_RETRIEVE to obtain bucket-level budget and service-level data. Typical invocation paths include ASCP planning dashboards, budget-versus-service-level reports, and concurrent planning processes that require aggregated budget attainment measures. Because it depends on the plan, instance, and organization context, it must be invoked after a plan run has populated the relevant MSC_BIS and demand tables. Customizations should avoid altering the documented function signatures, as the Java integration layer expects them to remain stable across EBS 12.1.1 and 12.2.2.