Search Results validate_g_dmd_sch_id




Overview

MSC_WS_COMMON is a shared PL/SQL utility package in the APPS schema that underpins the Oracle Advanced Planning Command Center (APCC) and Advanced Supply Chain Planning (ASCP) web services layer. Its name follows the MSC_WS_* convention used by the planning family of web service packages, and it is classified as an "OTHER" API, meaning it is an internal support package rather than a public, documented interface. The package supplies the common validation, lookup, and plan-management routines that the individual Web Service entry points (MSC_WS_ASCP, MSC_WS_DRP, MSC_WS_ATP, MSC_WS_SNO, MSC_WS_SRP, MSC_WS_IO, and others) call before performing their specific business logic. In effect it centralizes responsibility for confirming that a caller is authenticated and authorized, that a referenced plan or simulation set is valid, and that organization and schedule records are consistent, so that the same checks are not re-implemented across every web service. It also provides a small set of schedule maintenance and plan-option routines used during plan administration.

Key Procedures and Functions

The metadata documents seventeen callable units. The access-control group includes VALIDATE_USER_RESP and VALIDATE_USER_RESP_FUNC, which verify that a user is associated with a responsibility (and, for the latter, that the responsibility is tied to a valid function), and GET_PERMISSION_IDS, which returns the permission identifiers granted to the caller. Lookup functions include GET_PLAN_NAME_BY_PLAN_ID, which resolves a plan identifier to its display name, GET_CAT_SET_ID for the applicable category set, and BOOL_TO_NUMBER, a convenience converter between Boolean and numeric representations used when passing values across the web service boundary.

The validation group covers GET_CAT_SET_ID's companion checks along with VALIDATE_PLAN_ID, PLAN_CONTAINS_THIS_ORG, VALIDATE_SIMULATION_SET_ID, VALIDATE_G_DMD_SCH_ID, VALIDATE_CONSUM_LVL, and VALIDATE_LOC_SUP_SCHS, which respectively confirm plan existence, that an organization participates in a plan, that a simulation set is usable, that global demand schedules and consumption levels are valid, and that location-supply schedules are correctly defined. The maintenance group comprises PURGE_ALL_SCHEDULES, INSERT_ALL_SCHEDULES, INSERT_OR_UPDATE_ALL_SCHS, UPDATE_PLAN_OPTIONS, and CONVERT_OVERWRITE, which together manage the population, refresh, and removal of schedule rows and the overwrite semantics applied to plan options.

Tables Accessed

The package reads Oracle EBS foundation data through FND_USER, FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL, FND_SECURITY_GROUPS, FND_APPLICATION, and FND_LANGUAGES, which supply the identity, responsibility, security group, application, and language context required for the security validations described above. Planning-specific data is drawn from MSC_PLANS, MSC_PLAN_ORGANIZATIONS, MSC_PLAN_SCHEDULES, MSC_DESIGNATORS, and MSC_ITEM_SIMULATION_SETS, supporting plan, organization, schedule, and simulation validations. MSD_DP_SCENARIO_OUTPUT_LEVELS holds Demand Planning scenario output-level settings used by the validation routines, and PLITBLM is an internal PL/SQL index-by table type used for in-memory collections rather than persistent storage. Direct logical references also include the MSC demand and supply schedule tables — MSCIGLBDMDSCHTBL, MSCILOCDMDSCHTBL, MSCILOCSUPSCHTBL, and MSCLOCSUPSCHTBL — consistent with the schedule-maintenance procedures.

Usage Notes

MSC_WS_COMMON is not intended for direct invocation by end users or custom applications; it is an internal dependency of the APCC/ASCP web service stack. The ETRM dependency listing shows it is referenced by thirteen packages, including MSC_SCN_ACTIVITY_WF, MSC_WS_APS_DATA_SERVICES, MSC_WS_ASCP, MSC_WS_ATP, MSC_WS_COLLECTIONS, MSC_WS_DRP, MSC_WS_IO, MSC_WS_NOTIFICATION_BPEL, MSC_WS_PLAN_MANAGEMENT, MSC_WS_SCENARIO_MANAGEMENT, MSC_WS_SNO, MSC_WS_SRP, and MSD_WS_DEM_RENAME_FORECAST, and it references itself for shared internal logic. In practice it is reached indirectly through planning web service calls, BPEL notification flows, and workflow activity processing, where its validation routines gate access and its schedule routines manage plan schedule records. Because the package is a shared dependency, changes to it carry broad impact across the planning web service layer, and it should only be modified through Oracle-supplied patches. It is present and valid in both EBS 12.1.1 and 12.2.2, where it resides in the APPS schema.