Search Results msc_analysis_safety_stock




Overview
Explore in AI Chat

Overview

MSC_ANALYSIS_SAFETY_STOCK is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, residing in the Advanced Supply Chain Planning (ASCP) module of the Oracle Value Chain Planning suite. It is an internal analysis utility rather than a public application programming interface, and the ETRM metadata classifies it as an API classification of OTHER, indicating that it is not published or supported for direct customer invocation. Its name reflects its purpose: it supports the analysis of safety stock data within the planning schema, aggregating and presenting safety stock and customer target service level information across planning organizations, plans, and buckets so that planners can evaluate buffer inventory levels and service-level targets. The package includes both a specification and a package body, and its status is recorded as VALID in both EBS 12.1.1 and 12.2.2 environments. It depends on the SYS STANDARD package and is reported as being referenced by no other packages, confirming its role as a leaf-level or display-support utility rather than a reusable library component.

Key Procedures and Functions

The ETRM documentation records three callable program units within the package specification:

  • SCHEDULE_RETRIEVE — Drives the retrieval of safety stock analysis data for the current form query context. The name suggests it manages or schedules the data fetch that populates the analysis results, likely coordinating the read of safety stock and plan data against the active query definition.
  • GET_CAT_SET_ID — Returns the category set identifier relevant to the current query or display context. This value is required to resolve item category information correctly when safety stock analysis spans multiple category hierarchies.
  • GET_CUSTOMER_TARGET_SL — Returns the customer target service level used in safety stock and service-level analysis. This function supplies the target service level value that planners compare against actual or projected performance for trading partners.

The metadata does not document parameter lists for these units; consumers should not assume a public callable signature.

Tables Accessed

The package reads from a defined set of ASCP planning tables via APPS synonyms. The core planning context is established through MSC_PLANS, MSC_PLAN_ORGANIZATIONS, MSC_PLAN_BUCKETS, and MSC_PERIOD_START_DATES, which supply plan definition, organization scope, bucket granularity, and calendar alignment. Safety stock and item data are drawn from MSC_SAFETY_STOCKS, MSC_SYSTEM_ITEMS, and MSC_ITEM_CATEGORIES, while MSC_TRADING_PARTNERS provides the customer or supplier context required by service-level analysis. Demand information comes from MSC_DEMANDS. The form integration layer is represented by MSC_FORM_QUERY and MSC_FORM_QUERY_S, which store the query definitions and the associated query identifiers that drive the on-screen analysis. DBMS_OUTPUT, DUAL, and PLITBLM are referenced for diagnostic output, single-value selection, and index-by-table PL/SQL operations respectively. No writes to application tables are documented.

Usage Notes

MSC_ANALYSIS_SAFETY_STOCK is intended for internal consumption by the ASCP planning workbench and related Oracle Forms user interfaces, most likely the safety stock and service-level analysis screens. It is not a supported integration point, and the ETRM record shows no other packages referencing it, so custom code should not depend on it. Planners trigger its logic indirectly through form interactions that build an MSC_FORM_QUERY record and then invoke the retrieve path. Because the package accesses data through APPS synonyms and relies on session-level query state, any diagnostic or troubleshooting exercise should be performed in a controlled environment, and direct invocation should be avoided in favor of supported ASCP concurrent programs and planner workbench functionality.