Search Results msd_dem_collect_level_types




Overview
Explore in AI Chat

Overview

MSD_DEM_COLLECT_LEVEL_TYPES is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM registry as OTHER. It forms part of the Oracle Demand Planning and Advanced Supply Chain Planning infrastructure, specifically the collection framework that gathers planning level definitions from the operational source instance into the planning server. The package is declared with AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking user rather than the definer, an important characteristic for a utility that must inspect data dictionary objects during execution.

The header comment block identifies the source file as msddemclts.pls, version 120.3, last modified on 2011/06/02, which is consistent with the EBS 12.1.1 and 12.2.2 code lines. The package exposes a single documented procedure, COLLECT_LEVELS, indicating that its sole business responsibility is to drive the collection of demand planning level type metadata for one or more instances registered in the planning schema. It is one of several MSD_DEM collection packages that the planning collection manager schedules during a data refresh.

Key Procedures and Functions

The package documents exactly one procedure, COLLECT_LEVELS. Because the ETRM metadata does not publish the parameter list in narrative form, the parameters are not restated here beyond what the specification shows: the procedure accepts an error buffer, a return code, an instance identifier, a collect level type indicator, and optional defaulted arguments for a plan identifier and an SPF flag. In functional terms, COLLECT_LEVELS reads the planning levels configured for the specified instance and level type, then materialises the corresponding combinations for use by downstream demand planning processes.

Tables Accessed

The documented APPS synonyms referenced by this package are:

  • MSC_APPS_INSTANCES — stores the registered source instances for planning collection; used to validate the instance and determine connection context.
  • MSC_PLANS — holds plan definitions; consulted when a specific plan identifier is supplied so that collection is scoped to the correct plan.
  • MSD_DEM_NEW_ITEMS — the demand planning table that receives or correlates newly identified items during level collection.
  • DBA_TABLES and DBA_TAB_COLUMNS — data dictionary views inspected dynamically, most likely to verify the existence and structure of source tables before collection proceeds.
  • DBMS_OUTPUT and DUAL — utility references used for diagnostics and simple scalar queries.

Usage Notes

COLLECT_LEVELS is not intended for direct interactive invocation. It is reached through the demand planning collection flow, where the collection manager invokes the MSD_DEM packages in sequence, typically from a concurrent program or a scheduled collection request. The errbuf and retcode conventions confirm that the procedure is designed to run as a concurrent program entry point or as a subprogram called by a parent concurrent request, with Oracle's standard error-reporting contract.

Because the package is declared AUTHID CURRENT_USER, callers invoking it under a schema other than APPS must hold the necessary object privileges and dictionary access; custom code should therefore grant the appropriate privileges to any non-APPS user that calls it. The referenced-by count of one other package indicates limited internal reuse, so the practical integration point is the planning collection scheduler rather than ad hoc application code. Administrators troubleshooting demand level collection should confirm that the target instance exists in MSC_APPS_INSTANCES and that any named plan exists in MSC_PLANS before rerunning the collection.