Search Results msd_translate_fact_data




Overview
Explore in AI Chat

Overview

MSD_TRANSLATE_FACT_DATA is an Oracle Applications (APPS) PL/SQL package body that forms part of the Oracle Demand Planning / Advanced Planning foundation layer within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to translate raw operational and transactional facts drawn from source EBS modules — shipments, bookings, opportunities, forecasts, pricing, manufacturing, and currency and unit-of-measure conversions — into the standardized fact format consumed by the demand planning and supply chain analytical data model. Operating under the APPS schema (documented status VALID, API classification OTHER), the package acts as an extract-transform layer that normalizes disparate source data structures so downstream planning engines can aggregate and model demand consistently across the enterprise.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, each handling a distinct translation domain:

Tables Accessed

All documented table references are made through APPS synonyms. The package reads and writes the fact header staging structures MSD_CS_DATA_HEADERS and MSD_CS_DATA_HEADERS_S (the latter being the language/translation-enabled variant), which are central to controlling and registering uploaded fact sets. It consults MSD_CS_DEFINITIONS for fact and column definitions, MSD_DP_PARAMETERS for demand planning runtime parameters, and MSC_APPS_INSTANCES to resolve instance context. Source data is drawn from MSD_MFG_FORECAST and MSD_PRICE_LIST, while MSD_ST_TIME, MSD_ST_UOM_CONVERSIONS, and MSD_UOM_CONVERSIONS supply the time-bucket and unit-of-measure conversion logic. Utility and runtime support come from MSD_COMMON_UTILITIES, FND_FILE, FND_GLOBAL, DUAL, and the PL/SQL table PLITBLM.

Usage Notes

MSD_TRANSLATE_FACT_DATA is not referenced by any other database object but is itself a consumer of several APPS packages, indicating it is invoked at the top of the call stack rather than nested within other logic. In practice it is executed as part of demand planning fact-load and refresh flows — typically triggered by a demand planning concurrent program or collection process that stages source records into MSD_CS_DATA_HEADERS and then calls the appropriate TRANSLATE_* routine to render them as planning facts. Because the search term msd_cs_data_headers_s resolves here, this package is relevant when investigating how language-specific fact header rows are created and maintained. Customizations should invoke the individual translation procedures in the supported sequence, honoring IS_POST_PROCESS_REQUIRED before running MFG_POST_PROCESS, and should not bypass CLEAN_FACT_DATA when reloading, to avoid stale fact remnants affecting planning results.