Search Results restore_plan

Overview

The APPS.MSD_ARCHIVE_PLAN package body is a component of the Oracle Demand Planning (MSD) schema within Oracle E-Business Suite. Its principal responsibility is to manage the lifecycle persistence of a demand plan by delegating archive and restore operations to the Oracle OLAP (Express) Analytic Workspace environment. Demand Planning stores plan data inside an OLAP workspace rather than in conventional relational tables, so archival and restoration of a plan requires interaction with the OLAP engine through the DBMS_AW interpreter interface. This package provides the thin PL/SQL wrapper that bridges standard EBS concurrent program execution and the OLAP archive/restore subsystem.

The package is registered in ETRM 12.2.2 under the APPS schema as an API classified as OTHER, and it exposes exactly two documented procedures. The header comment (msdarchb.pls 120.1, dated 2005) indicates a long-stable implementation that has remained essentially unchanged across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

• ARCHIVE_PLAN — Archives the demand plan identified by the supplied demand plan identifier. It builds a command string that attaches the OLAP workspace ODPCODE in read-only mode and invokes the OLAP pl.archive routine, passing the plan identifier as the target. Execution is performed through MSD_COMMON_UTILITIES.DBMS_AW_INTERP_SILENT. On success it returns a retcode of 0; on failure it captures the Oracle error text, writes diagnostic messages to the concurrent manager log via FND_FILE.PUT_LINE, and returns a retcode of -1.
• RESTORE_PLAN — Performs the inverse operation, restoring a previously archived demand plan. It issues an equivalent command that attaches ODPCODE read-only and calls the OLAP pl.restore routine with the plan identifier. Error handling mirrors ARCHIVE_PLAN, writing a bounded error string to the log and signaling failure through the retcode output parameter.

Both procedures use the standard EBS concurrent program signature, accepting errbuf and retcode as NOCOPY output parameters alongside the plan identifier. Both trap all exceptions through WHEN OTHERS, ensuring that failures are reported gracefully to the concurrent manager rather than raising unhandled exceptions.

Tables Accessed

The documented metadata does not list any relational tables accessed through APPS synonyms, and this is consistent with the implementation excerpt. All plan data manipulation occurs inside the OLAP workspace ODPCODE rather than in Oracle relational tables. The package therefore does not perform direct SQL against MSD base tables; the referenced analytic workspace is the effective data store, and the OLAP pl program is responsible for all read and write activity against plan objects.

Usage Notes

MSD_ARCHIVE_PLAN is designed to be invoked as a concurrent program from the Demand Planning responsibility, where users archive a plan to preserve a snapshot or restore a plan from a prior archive. The errbuf/retcode interface conforms to the Oracle Application Object Library standard for registered concurrent executables, so the procedures can also be called programmatically by custom code or workflow provided a valid demand plan identifier is supplied. Because both procedures depend on the OLAP interpreter and the ODPCODE workspace, the Demand Planning schema and OLAP options must be present and initialized, and the calling session must have access to MSD_COMMON_UTILITIES. Being a low-level wrapper, the package is not referenced by any other documented package, which confirms it sits at the boundary between EBS and the OLAP engine and is invoked directly rather than through higher-level APIs.