Search Results msc_ws_plan_management




Overview
Explore in AI Chat

Overview

MSC_WS_PLAN_MANAGEMENT is an APPS-owned PL/SQL package within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It exposes a small, focused set of plan lifecycle operations that are callable as web services through the MSC_WS_PLAN_MANAGEMENT interface layer. The package serves as the server-side implementation behind plan administration activities: copying an existing plan into a new plan, archiving a plan to preserve its contents, and purging a plan to reclaim storage and remove obsolete data. In the context of Oracle EBS 12.1.1 and 12.2.2, these operations correspond to the standard plan management functions that planners and administrators perform from the Oracle Advanced Supply Chain Planning responsibility or through scheduled concurrent requests.

The package is classified as OTHER in the ETRM API taxonomy rather than as a public or private API, reflecting that it is intended primarily as an internal service implementation consumed by the web service wrapper and by the planning application itself, rather than as a documented integration point for external callers.

Key Procedures and Functions

The ETRM metadata documents three procedures within this package:

  • COPY_PLAN — Creates a new plan by duplicating the definition and, where applicable, the planning data of an existing source plan. This supports the common planning practice of using a validated baseline plan as the starting point for a new simulation or scenario.
  • ARCHIVE_PLAN — Moves or retains plan data in an archived state so that historical plan results remain available for comparison and audit while the active planning tables are relieved of that data.
  • PURGE_PLAN — Removes a plan and its associated planning data from the active schema, freeing storage and eliminating plans that are no longer required.

Parameter lists are deliberately not reproduced here, as the ETRM excerpt does not document the formal signatures; consumers must not assume argument order or datatypes from this summary.

Tables Accessed

Two tables are documented as referenced by the package via APPS synonyms:

  • MSC_PLANS — The master definition table for plans in ASCP. This table stores the plan header information, including plan name, type, and configuration attributes. All three procedures necessarily read this table to identify the target plan; COPY_PLAN and PURGE_PLAN also write to it to create or remove the plan record.
  • MSC_DESIGNATORS — Stores plan designator information, which controls how plan entities such as organizations, items, and resources are named and organized. This table is referenced to keep designator mappings consistent when a plan is copied or removed.

Usage Notes

In a standard EBS deployment, MSC_WS_PLAN_MANAGEMENT is not invoked directly by end users. It is reached through the planning application user interface and through concurrent program submissions that perform plan copy, archive, and purge operations. The MSC_WS_PLAN_MANAGEMENT web service interface exposes these procedures for external or service-oriented invocation, which allows integration platforms and custom clients to trigger plan lifecycle operations without logging into the EBS forms.

Because the package is classified as OTHER and is referenced by no other packages, custom code should treat it as an internal implementation detail subject to change across patch levels and releases. Where plan management automation is required, the supported approach is to invoke the corresponding concurrent programs or the documented web service layer rather than calling this package directly. Administrators should also be aware that purge and archive operations are destructive with respect to planning data and should be scheduled during periods of low planning activity.