Search Results mst_launch_plan_pkg




Overview
Explore in AI Chat

Overview

MST_LAUNCH_PLAN_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Oracle Transportation Management (OTM) integration shipped with EBS Release 12.1.1 and 12.2.2. Its principal business function is the administrative orchestration of the snapshot-based data replication used to populate the MST (Transportation) staging layer from the EBS transactional applications. During the initial OTM integration setup and during incremental refresh cycles, the package coordinates three distinct activities: verifying that the required database objects (snapshots, snapshot logs, and refresh groups) exist in the source schema; creating or repairing those objects when they are absent; and submitting the concurrent request that performs the actual snapshot refresh. Because the source data volumes in a typical EBS install are large, the refresh is executed asynchronously as a concurrent program rather than in the calling session. The package therefore acts as a thin but essential control layer, bridging the Forms-based setup UI, the concurrent manager, and the underlying DBMS_SNAPSHOT / DBMS_LOCK database utilities. It is classified in ETRM as an OTHER API, meaning it is internal infrastructure rather than a public, supported extension point.

Key Procedures and Functions

  • MST_LAUNCH_PLAN — The main entry point. It determines whether the launching prerequisites are satisfied and then drives the snapshot launch sequence, ultimately requesting the refresh concurrent program through FND_REQUEST.
  • REFRESH_SNAPSHOT — Performs the refresh of the identified snapshots, relying on DBMS_SNAPSHOT and the standard snapshot dictionary views.
  • FOUND_EXIST_OBJECTS — A validation routine that inspects ALL_OBJECTS and ALL_SNAPSHOTS to confirm whether the expected source objects and snapshots are already present in the database.
  • SETUP_SOURCE_OBJECTS — Creates or registers the source objects and snapshot definitions required by the transportation plan when they are missing.
  • WAIT_FOR_REQUEST — Monitors a submitted concurrent request, typically polling FND_CONCURRENT, and returns control once the request completes or the wait condition is met.

Tables Accessed

  • MST_PLANS — The core transportation plan definition table; the package reads plan configuration to determine what must be launched or refreshed.
  • FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES — Supply site, application, and responsibility profile values that govern launch behavior.
  • ALL_OBJECTS, ALL_SNAPSHOTS — Used for existence checks on source objects and snapshot definitions.
  • DUAL — Standard single-row selection for scalar evaluations.
  • DBMS_LOCK — Serializes concurrent invocations to prevent overlapping refresh operations.
  • DBMS_SNAPSHOT — Executes the underlying snapshot refresh against the source schema.

Usage Notes

The package is invoked indirectly. It is called from the OTM / Transportation setup forms and from the concurrent programs that manage plan launching, and it depends on FND_CONCURRENT, FND_CONC_GLOBAL, FND_INSTALLATION, FND_MESSAGE, FND_PROFILE, and FND_REQUEST in addition to MSC_UTIL. Because the package is not referenced by any other database object and is classified as OTHER, it should be treated as internal Oracle code: customizations should call the supported transportation APIs rather than MST_LAUNCH_PLAN_PKG directly. When diagnosing refresh failures in Release 12.1.1 or 12.2.2, the dependency chain above identifies the practical starting points — profile option configuration, concurrent request status, and snapshot object validity.