Search Results get_plan_service_level




Overview
Explore in AI Chat

Overview

APPS.MSC_ANALYSIS_PKG is a PL/SQL package within the Oracle Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It provides the analytical engine behind the planning workbench's cost and service-level reporting features, enabling planners to generate cost savings analyses, cost breakdowns, service-level breakdowns, and service-level profitability summaries across one or more plans, organizations, categories, and items. The package translates user-entered analysis criteria into query results by reading from the MSC (Advanced Planning) staging and plan tables, and it also persists user analysis preferences. Because it is classified as an OTHER API, it is not intended as a public integration interface; rather, it is an internal package used by ASCP concurrent programs and Oracle Forms-based analysis windows. The header comment indicates a last significant revision in 2007 (version 120.2), confirming its long-standing role in the planning analytics stack across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • POPULATE_COST_SAVINGS — Populates cost savings analysis results based on period type, detail level, view-by dimension, and plan/organization/category/item/date filters, with an optional rounding factor.
  • POPULATE_SRVLVL_BREAKDOWN — Builds the service-level breakdown report, additionally filtering by demand class and a year-from/year-to range.
  • POPULATE_COST_BREAKDOWN — Produces the cost breakdown report across the same plan, organization, category, item, and date dimensions.
  • POPULATE_SRVLVL_PROFIT — Generates the service-level profitability analysis for a given plan list, view-by option, and rounding factor.
  • GET_TP_COST — Returns the trading partner cost for a specific period type, detail level, plan, instance, organization, item, and detail date.
  • STORE_USER_PREF — Persists user preferences for analysis parameters (such as plan type) so that subsequent analysis sessions retain the planner's selections.
  • GET_CAT_SET_ID — Retrieves the category set identifier used to drive category-level analysis.
  • GET_PLAN_SERVICE_LEVEL — Returns the service level defined for a given plan.
  • GET_PLAN_DFLT_VALUE — Fetches a default value associated with a plan for use in analysis forms.
  • GET_NUM_PERIODS — Determines the number of planning periods applicable to the analysis.
  • GET_DFLT_VALUE — Returns a general default value used by the analysis UI or callers.

Tables Accessed

The package reads from a range of ASCP plan and staging tables through APPS synonyms. MSC_BIS_INV_DETAIL and MSC_BIS_PERIODS supply the business intelligence summary inventory and period data underlying the cost and service-level metrics. MSC_PLANS, MSC_PLAN_ORGANIZATIONS, and MSC_SERVICE_LEVELS provide plan definitions, participating organizations, and service-level targets. MSC_SUPPLIES, MSC_SYSTEM_ITEMS, and MSC_ITEM_CATEGORIES support item and supply-level aggregation, while MSC_TRADING_PARTNERS and MSC_INTERORG_SHIP_METHODS supply trading partner costs and sourcing methods for cost computations. MSC_PERIOD_START_DATES defines period boundaries. MSC_FORM_QUERY and MSC_FORM_QUERY_S are used to store and manage saved analysis query definitions, and DUAL serves as a utility source for scalar lookups.

Usage Notes

MSC_ANALYSIS_PKG is invoked primarily from the Advanced Supply Chain Planning analysis windows and their supporting concurrent programs, which pass the planner's filter selections (plan list, org list, category list, item list, and dates) into the POPULATE_* procedures. The STORE_USER_PREF, GET_PLAN_DFLT_VALUE, and GET_DFLT_VALUE routines support the form layer by saving and retrieving user-specific analysis defaults, which is directly relevant to searches for "store_user_pref" — this procedure is the persistence hook that captures planner analysis preferences. Because the package is classified as OTHER, custom code should avoid direct calls to its procedures where a supported public API exists; the safest use in custom extensions is read-only invocation of the GET_* helper functions. The package is referenced by two other packages, indicating it participates in a broader dependency chain within ASCP, so changes to its signature or behavior should be regression-tested against those dependents.