Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Fdm migration guide ORACLE HYPERION FINANCIAL DATA QUALITY MANAGEMENT Release Migration Guide CONTENTS IN BRIEF About This Document Overview to the FDM Migration How Migration Works Supported FDM Versions for Migration Additional Migration Details FDM Art

ORACLE HYPERION FINANCIAL DATA QUALITY MANAGEMENT Release Migration Guide CONTENTS IN BRIEF About This Document Overview to the FDM Migration How Migration Works Supported FDM Versions for Migration Additional Migration Details FDM Artifacts and their Equivalents in FDMEE Installation Steps Pre- Migration Steps Executing the Migration Drill Region Post Migration Steps Check Rules Post Migration Steps Additional Post Migration Steps Testing and Troubleshooting Tips CAbout This Document This document shows how to migrate Oracle Hyperion Financial Data Quality Management to Oracle Hyperion Financial Data Quality Management Enterprise Edition Overview to the FDM Migration In EPM Release FDM is no longer available All customers who wish to continue using the key FDM functionality can migrate to FDMEE FDMEE is o ?ered as the full-featured successor to Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications ERP Integrator and Oracle Hyperion Financial Data Quality Management FDM FDMEE o ?ers combined features of both products It captures key functionality from FDM and preserves the ERP Integrator framework that enables users to load metadata and data and to drill-through and write-back Due to signi ?cant di ?erences between FDM and FDMEE no automated upgrade process is provided Notable aspects of this migration FDM supports multiple applications with separate schemas whereas FDMEE does not l support application concepts All data is stored in a single schema A large volume of data is stored in the staging table and all data may not have to be migrated l to the new environment You can selectively migrate required data and omit very old data FDM supports ?xed delimited script and adapter import format types FDMEE imports l only ?xed and delimited import format types Migration from FDM releases x and x to FDMEE is supported l The ERPI content is upgraded to FDMEE during an in place upgrade and the FDM content l can also be migrated After migration duplicate artifacts from both ERPI and FDM may occur It is recommended that you delete the duplicated artifacts from ERPI If you have an integration of ERPI and FDM in releases or then this combination is not supported for migration only x if you use both ERPI and FDM together FDM export uses dimension alias names when writing to the data ?le for Oracle Hyperion l Financial Management applications For this reason alias names should be the same as de ?ned in Financial Management How Migration Works The migration is implemented as a Extract Transform Load ETL process from one or more source FDM schema to a single target FDMEE schema The process is implemented using Oracle Database Integrator ODI The migration process can be executed using ODI installed as part of the FDMEE installation The process is executed and monitored using ODI Studio so make sure you have identi ?ed the server to install ODI Studio There are two ODI Scenarios one for the setup data and the other for the historical data CYou run the setup data process to migrate the setup information