Search Results all_tab_partitions




Overview
Explore in AI Chat

Overview

APPS.MSC_ANALYSIS_SAFETY_STOCK_PERF is a performance-oriented PL/SQL package body belonging to the Advanced Supply Chain Planning (ASCP) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented role is to populate and maintain the safety-stock analysis tables used by the Planner Workbench and related supply chain analysis reports. Safety stock represents buffer inventory held to absorb demand and supply variability, and this package supports the aggregated reporting layer by computing performance metrics across plan, organization, item, and period dimensions.

The package is classified as OTHER in the ETRM repository; it is not a public open interface or a standard FND-style API. It functions as an internal engine invoked by the planning analysis infrastructure rather than by end users directly. The dependency list confirms integration with the FND application framework (FND_API, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, FND_INSTALLATION) and with the MSC analysis and planning tables, including MSC_ANALYSIS_AGGREGATE, which suggests this package persists its results into the aggregate analysis structures consumed by ASCP dashboards.

Key Procedures and Functions

The documented package exposes five procedures and functions:

  • SCHEDULE_DETAILS_SL — Produces safety-stock detail rows in the schedule (detail-level) format, typically keyed at the item/organization/period grain for the selected plan.
  • SCHEDULE_DETAILS_SS — Computes and stages safety-stock detail output in a summary-oriented form, supporting comparisons of target versus achieved safety-stock levels.
  • SCHEDULE_DETAILS_IV — Derives inventory-related detail for the analysis, reconciling on-hand and projected inventory positions against safety-stock targets.
  • SCHEDULE_AGGREGATE — Rolls the detail results up into the aggregate analysis structures, driving the summary views presented to planners.
  • GET_CAT_SET_ID — Resolves the category set identifier used to group items consistently across the analysis output.

No parameter signatures are documented in the ETRM metadata; the package is intended for internal invocation only.

Tables Accessed

The package reads and writes a defined set of MSC planning tables. Plan and calendar context come from MSC_PLANS, MSC_PLAN_ORGANIZATIONS, MSC_PLAN_BUCKETS, MSC_PERIOD_START_DATES, and MSC_BIS_PERIODS. Item and category metadata come from MSC_SYSTEM_ITEMS, MSC_ITEM_CATEGORIES, and MSC_TRADING_PARTNERS. Demand and supply quantities are drawn from MSC_DEMANDS; safety-stock targets originate in MSC_SAFETY_STOCKS; and extended inventory/cost figures come from MSC_BIS_INV_DETAIL and MSC_COST_BREAKDOWN_NOTPCOST_V. Query definitions are read from MSC_FORM_QUERY and MSC_FORM_QUERY_S. Results are written to MSC_ANALYSIS_AGGREGATE.

Notably, the dependency list includes ALL_TAB_PARTITIONS, which is the data dictionary view matching the user's search term "all_tab_partitions." The package references ALL_TAB_PARTITIONS dynamically to discover which partitions exist on the underlying analysis tables, allowing it to target the correct partition when inserting or purging period-scoped data. This is a common pattern for interval-partitioned ASCP analysis tables, where partition names shift over time.

Usage Notes

Because this is an internal ASCP component, it is normally invoked by the planning analysis concurrent programs and by the Planner Workbench forms framework, not called directly by users or custom code. It is referenced by one other database object in the repository and is not referenced by any external consumer, reinforcing its role as a supporting module within the MSC analysis layer. Custom developers should avoid direct calls; instead, use the supported ASCP analysis concurrent programs and report definitions. Any direct dependency on ALL_TAB_PARTITIONS should be treated as an implementation detail subject to change between 12.1.1 and 12.2.2, and should not be relied upon in custom extensions.