Results for “drop_snapshot_ei”

4 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.MRP_CL_REFRESH_SNAPSHOT is a VALID PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Advanced Supply Chain Planning (ASCP) / Material Requirements Planning (MRP) module, where it serves as the engine that creates, refreshes, drops, and purges snapshots used by the Collections and Planning Central infrastructure. In EBS planning architecture, collection snapshots are point-in-time materialized copies of source data drawn from multiple EBS modules — inventory, bills of material, purchasing, order management, and others — that are subsequently consumed by the planning data model. MRP_CL_REFRESH_SNAPSHOT orchestrates this materialized view lifecycle: it determines which snapshots correspond to the current planning entity, refreshes those that are stale or incomplete, drops obsolete structures, and cleans up residual data. The package therefore underpins the reliability of every planning run that depends on a complete and current collection snapshot.

Key Procedures and Functions

The ETRM metadata documents 18 procedures and functions. Their purposes are as follows:

Tables Accessed

The package reads and writes application metadata and planning control tables through APPS synonyms. FND_APPLICATION, FND_ID_FLEX_SEGMENTS, and FND_ID_FLEX_STRUCTURES supply application registration and key flexfield context. FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES, and FND_USER supply profile and user context. MRP_AP_APPS_INSTANCES_ALL and MRP_AP_REFRESH_S define the application instances participating in the refresh and the refresh status records. MRP_REGION_SITES supplies region-site scope. ALL_SNAPSHOT_LOGS, ALL_TABLES, DUAL, and the DBMS_LOCK, DBMS_MVIEW, and DBMS_UTILITY packages supply dictionary inspection, locking, and materialized view refresh services.

Usage Notes

MRP_CL_REFRESH_SNAPSHOT is not referenced by any other database object, indicating it is a top-level entry point rather than a library. It is referenced by four other packages and is typically invoked from the Collections Manager concurrent programs and related planning forms during the collection cycle. Developers extending collections or troubleshooting failed snapshot refreshes will find LOG_DEBUG and LOG_ERROR useful for diagnosis, while REFRESH_SNAPSHOT and DROP_SNAPSHOT are the primary runtime entry points.