Search Results msc_activity_parameters

Overview

MSC_SCN_UTILS is a utility package in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, owned by the APPS schema and classified as OTHER in the ETRM metadata. It provides the supporting programmatic infrastructure for the Scenario Planning feature set, particularly the management and display of planning scenarios, scenario sets, plan runs, and the collection of planning process activities. The package body encapsulates reusable helper logic that drives the scenario management user interfaces and concurrent processing routines, bridging the MSC_SCENARIOS, MSC_PLANS, and MSC_PLAN_RUNS data model with the forms and LOV components that expose this data to planners.

A notable element of the package body is the insert_seed_data procedure, which seeds the MSC_ACTIVITY_PARAMETERS table. The procedure opens a cursor that counts rows in msc_activity_parameters where param_version >= p_version (with p_version set to 7 in the shipped source). If fewer than one row exists, it deletes existing rows from msc_activity_parameters, commits, and re-inserts the activity parameter definitions. This version-guarded seeding pattern is central to how the package maintains the parameter metadata consumed by the activity parameter LOV and parameter population routines.

Key Procedures and Functions

• GET_PLAN_NAME, GET_SCENARIO_NAME, GET_SCENARIO_SET_NAME, GET_OWNER_NAME, GET_PROC_ACT_NAME — Resolve descriptive display names for plans, scenarios, scenario sets, owners, and process activities, typically for LOVs and form fields.
• GET_SCN_VERSION, GET_PLAN_VERSION — Return version identifiers for scenarios and plans, supporting version-aware copy and comparison logic.
• GET_SCN_USERS — Retrieves the set of users associated with a scenario, drawing on MSC_SCENARIO_USERS.
• SCENARIO_STATUS, PLAN_STATUS, GET_PROCESS_STATUS — Derive status values for scenarios, plans, and underlying concurrent processes.
• PLAN_SCNS_COUNT — Returns counts of plans or scenarios associated with a given context.
• ARCHIVE_SCN_CONC, PURGE_SCN_CONC, PURGE_PLAN_CONC — Manage concurrent request artifacts for scenario archiving and purging, invoking concurrent processing against FND_CONCURRENT_REQUESTS.
• POPULATE_ACT_PARAMS_FOR_LOV — Populates activity parameter values for list-of-values display, directly related to MSC_ACTIVITY_PARAMETERS.
• POPULATE_DEFAULT_PARAMS — Applies default parameter values when no explicit values are supplied.
• GET_ACTIVITY_SUMMARY — Returns a summarized view of activity status for planning processes.
• GET_PLAN_RUN_DATE — Returns the date a plan was executed, sourced from MSC_PLAN_RUNS.
• COPY_SCN_PLANS — Copies scenarios and their associated plans, using the version and name helpers.

Tables Accessed

The package reads and writes MSC_ACTIVITY_PARAMETERS for parameter seeding and LOV population. Scenario metadata is drawn from MSC_SCENARIOS, MSC_SCENARIO_PLANS, MSC_SCENARIO_SETS, MSC_SCENARIO_SET_DETAILS, MSC_SCENARIO_USERS, and MSC_SCN_SCENARIOS_S. Plan execution data comes from MSC_PLANS, MSC_PLAN_RUNS, and MSC_PLANNING_PROC_ACTIVITIES. Concurrent request state is read from FND_CONCURRENT_REQUESTS, and user names from FND_USER. MSC_FORM_QUERY supports form-level query resolution, MSD_DP_SCENARIO_REVISIONS supports Demand Planning revision data, and DUAL is used for scalar evaluations.

Usage Notes

MSC_SCN_UTILS is invoked indirectly during Scenario Planning form interactions and concurrent program execution, rather than being called by other packages (the metadata records zero referencing packages). Customizations should call these helpers through the APPS synonym, respecting session context, since the package relies on FND_USER and FND_CONCURRENT_REQUESTS to resolve user and request identity. Because insert_seed_data performs commits and deletes, it should not be invoked within a larger uncommitted transaction. The package behaves identically under EBS 12.1.1 and 12.2.2, though file system and online patching differences affect profiling rather than logic.