Search Results populate_summary

Overview

MSC_DEMANTRA_PKG is an Oracle Applications (APPS) PL/SQL package within the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. Its name derives from "Demantra," Oracle's demand management and supply chain planning analytics engine that integrates with ASCP. The package provides the database-side integration layer that moves forecast, demand, and measure data between the EBS planning tables and the Demantra analytics repository. In the 12.1.1 and 12.2.2 releases, this package is part of the "MSCHBDMS" source family, as indicated by the header identifier carried in the packaged specification.

The package is registered with an API classification of OTHER, meaning it is an internal, infrastructure-level utility rather than a formally published public API. It is not intended for direct customer invocation; instead it is called by planning engine jobs, concurrent programs, and other planning packages to populate, summarize, export, import, and archive Demantra-related planning data.

Key Procedures and Functions

The ETRM documentation lists eleven callable units. The specification in the documented source exposes three entry points with standard concurrent-program error signatures (ERRBUF and RETCODE output parameters plus plan identifiers):

• PURGE_DETAILS — Removes stale detail rows associated with a given plan and plan run, typically as a cleanup step after a planning cycle.
• POPULATE_DETAILS — Loads detailed demand and measure records for the specified plan and plan run.
• POPULATE_SUMMARY — Aggregates the populated detail data into the summary-level structures used for reporting and analysis.
• SUMMARIZE_DEMANTRA_F — Produces summarized values from the Demantra fact table.
• EXPORT_DEMANTRA_F — Exports Demantra fact data out of the EBS planning schema.
• EXPORT_DEMANTRA_ODS_F — Exports Demantra operational data store fact data.
• IMPORT_DEMANTRA_F — Imports Demantra fact data back into the EBS planning tables.
• IMPORT_DEMANTRA_ODS_F — Imports operational data store fact data.
• ARCHIVE — Moves or copies historical Demantra planning data to archive structures.
• REGISTER_CUSTOM_MEASURES — Registers user-defined custom measures so they participate in Demantra processing and mapping.
• CREATE_ITEM_HIERARCHY_VIEW and BUILD_CUSTOM_HIERARCHY — Construct item hierarchy views and custom hierarchy structures used for measure aggregation.
• SEEDED_MEASURE_MAPPING — Provides the seeded mapping between EBS measures and their Demantra equivalents.

Tables Accessed

The package operates across the Demantra integration tables. MSC_DEMANTRA_F and MSC_DEMANTRA_ODS_F hold Demantra fact and ODS fact data; MSC_ST_DEMANTRA_F and MSC_ST_DEMANTRA_ODS_F serve as staging tables for loads. Custom measure and hierarchy definitions reside in MSC_APCC_CUSTOM_MEASURES, MSC_APCC_CUSTOM_HIER, and MSC_HUB_QUERY_S. Instance configuration is read from MSC_APPS_INSTANCES, and localized or user-facing text is drawn from MSC_TRANSLATED_MESSAGE. Metadata operations use AD_DDL, DBA_TAB_COLUMNS, USER_SYNONYMS, and DUAL, while PLITBLM provides PL/SQL index-by table messaging support. These tables support the purge, populate, export, import, and archival flows described above.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, MSC_DEMANTRA_PKG is invoked indirectly through ASCP concurrent programs, planning manager jobs, and Demantra integration processes rather than from application forms. At least one other package references it, confirming its role as a shared integration utility. Because the API classification is OTHER and the package manipulates core planning fact and staging tables, any direct invocation in custom code should be treated as unsupported and performed only within a controlled maintenance window. The plan and plan run identifiers passed to the populate and purge routines dictate which planning cycle's data is affected, so callers must supply valid active plan context to avoid unintended data removal.