Search Results change_output_period

Overview

MSD_APPLY_TEMPLATE_DEMAND_PLAN is an Oracle E-Business Suite PL/SQL package in the APPS schema that supports template-driven maintenance of demand plans within the Demand Planning module of Oracle Advanced Supply Chain Planning (ASCP) and the Enterprise Territory/Supply Chain Management (ETRM) family of applications. The package is declared with AUTHID CURRENT_USER and exposes a public API through which callers can instantiate a new demand plan from an existing template or source plan, or selectively modify the components of an existing demand plan. Its methods fall into two broad categories: plan creation routines (APPLY_TEMPLATE and CREATE_PLAN_USING_TEMPLATE) and component-level maintenance routines that add or remove dimensions, parameters, scenarios, events, price lists, calendars, hierarchies, and scenario output levels. Because the package manipulates rows directly in the underlying MSD_DP_* demand planning tables rather than relying solely on the Demand Planning user interface, it is classified as an OTHER API and is generally intended for controlled, programmatic use rather than ad-hoc execution.

Key Procedures and Functions

The documented public interface contains thirty-seven procedures and functions. Two are constructor-style entry points:

• APPLY_TEMPLATE — a function that creates a new demand plan by applying the definition of a source plan (p_source_dp_id) to a target plan identified by name and description, returning the new plan identifier through the p_new_dp_id out parameter.
• CREATE_PLAN_USING_TEMPLATE — a function that builds a demand plan from template attributes including plan type, start and end dates, and an optional associated supply plan, returning a boolean outcome and the new plan id.

The remaining routines are component-level maintenance procedures grouped by the entity they affect:

• Dimensions: ADD_DIMENSION and REMOVE_DIMENSION manage entries in the plan's dimension configuration.
• Parameters: ADD_PARAMETER and REMOVE_PARAMETER control plan-level parameters, including the parameter identified by p_parameter_id — the metadata most often located via searches for get_parameter_id.
• Scenarios and events: ADD_SCENARIO, REMOVE_SCENARIO, ADD_SCENARIO_EVENT, REMOVE_SCENARIO_EVENT, ADD_SCENARIO_OUTPUT_LVL, REMOVE_SCENARIO_OUTPUT_LVL, ADD_EVENT, and REMOVE_EVENT.
• Price lists, calendars, hierarchies: ADD_PRICE_LIST, REMOVE_PRICE_LIST, REMOVE_CALENDAR, ADD_HIERARCHY, and REMOVE_HIERARCHY.
• Period control: CHANGE_OUTPUT_PERIOD adjusts the output period used by the plan.

Tables Accessed

The package reads and writes through APPS synonyms to the following base tables:

• MSD_DEMAND_PLANS — the master demand plan record created or modified by the constructor functions.
• MSD_DP_DIMENSIONS and MSD_DP_DOC_DIM_SELECTIONS — dimension definitions and document-level dimension selections.
• MSD_DP_PARAMETERS and MSD_DP_PARAMETERS_S — plan parameter values and their set/translation rows; these store the parameter_id values manipulated by ADD_PARAMETER and REMOVE_PARAMETER.
• MSD_DP_FORMULAS and MSD_DP_FORMULA_PARAMETERS — formulas associated with a plan and their parameters.
• MSD_DP_SCENARIOS, MSD_DP_SCENARIOS_S, MSD_DP_SCENARIOS_TL, and MSD_DP_SCENARIO_EVENTS — scenario definitions, their set and translated rows, and scenario event linkages.
• MSD_DP_HIERARCHIES, MSD_DP_PRICE_LISTS, and MSD_DP_CALENDARS — hierarchy, price list, and calendar assignments.
• MSC_PLANS — the shared plans table, referenced when linking the demand plan to a supply plan or template plan.

Usage Notes

MSD_APPLY_TEMPLATE_DEMAND_PLAN is referenced by three other packages in the APPS schema and is therefore typically invoked indirectly rather than directly. The most common path is through Demand Planning setup or plan-creation flows launched from the Oracle EBS forms or from concurrent programs that provision new plans from a template. Custom code that needs to create, clone, or prune demand plans should call the exposed functions rather than inserting into the MSD_DP_* tables directly, since the package encapsulates the associated set and translation rows. When calling the maintenance procedures, callers must supply the correct parameter_id, scenario_id, or dimension_code; these identifiers are normally obtained by querying the corresponding MSD_DP_* tables (for example, MSD_DP_PARAMETERS) using the demand plan id and the parameter or scenario name. The error code out parameter should be inspected on every call to determine whether the requested change was applied successfully.