Remerciez-le!

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

ORACLE® HYPERION FINANCIAL DATA QUALITY MANAGEMENT Release 11.1.2.4 Migration G

ORACLE® HYPERION FINANCIAL DATA QUALITY MANAGEMENT Release 11.1.2.4 Migration Guide CONTENTS IN BRIEF About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Overview to the FDM Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 How Migration Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Supported FDM Versions for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Additional Migration Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 FDM Artifacts and their Equivalents in FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Pre-Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Executing the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Drill Region Post Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Check Rules Post Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Additional Post Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Testing and Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 About 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 11.1.2.4, FDM is no longer available. All customers who wish to continue using the key FDM functionality can migrate to FDMEE. FDMEE is offered 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 offers 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 significant differences between FDM and FDMEE, no automated upgrade process is provided. Notable aspects of this migration: l FDM supports multiple applications with separate schemas, whereas FDMEE does not support application concepts. All data is stored in a single schema. l A large volume of data is stored in the staging table and all data may not have to be migrated to the new environment. You can selectively migrate required data and omit very old data. l FDM supports fixed, delimited, script, and adapter import format types. FDMEE imports only fixed and delimited import format types. l Migration from FDM releases 11.1.1.x and 11.1.2.x to FDMEE 11.1.2.4 is supported. l The ERPI content is upgraded to FDMEE during an in place upgrade, and the FDM content 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 11.1.1.3 or 11.1.1.4, then this combination is not supported for migration, only 11.1.2.x if you use both ERPI and FDM together. l FDM export uses dimension alias names when writing to the data file for Oracle Hyperion Financial Management applications. For this reason, alias names should be the same as defined 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 11.1.2.4 FDMEE installation. The process is executed and monitored using ODI Studio so make sure you have identified the server to install ODI Studio. There are two ODI Scenarios: one for the setup data and the other for the historical data. 2 You run the setup data process to migrate the setup information like the application registration, import format, location, and so on to FDMEE. Since multiple FDM applications are consolidated into a single FDMEE schema to avoid duplication, you can prefix the data from each application with a prefix. If you follow a naming convention and data does not overlap, then a prefix may not be required. You run the data process to migrate historical data. You may have several years of historical data in your existing FDM applications. You may not need to migrate all the data to FDMEE environment. You can decide how much data should be migrated to the new system and run the migration process only for required range periods. Here is what you can expect when you migrate from FDM application to FDMEE. 1. The FDM migration does not delete or modify any objects within FDMEE. 2. The following FDM application objects are migrated: l Target Application l Global Categories l Application Categories l Global Periods l Application Periods l Logic groups l Check Entity Group l Check Rule Group l Import Format l Locations l Data Mappings l Data along with its workflow status, mappings, and drill regions If you use any other objects, they are not migrated automatically. You need to create or move them manually. If you use FDM along with ERPI, the application selected for migration may already exist in FDMEE. In this case, the FDMEE application is not created or modified. If a FDM location does not have an import format assigned (for example, you performed multi-loads only), the location and its data are not migrated. 3. Unlike FDM, FDMEE needs a data rule to store data. To meet this requirement, during the data migration, new data rules are created by a unique combination of location and category associated with the application. Dummy rules are only created for single period load irrespective of where the data in FDM was imported - from a single period or multi-period files. For any locations requiring multi- period loads, recreate import formats and data load rules as required in FDMEE. 4. FDM supports file-based, script-based, and ERPI adapter-based integrations. The following describes how these integrations are migrated: 3 l File-based—FDMEE creates a source system named “file” and assigns the source system type of “file” automatically. When file-based application objects are migrated, they are associated with this source system. l Script-based—During migration, FDMEE creates a new source system named "FDMC" and assigns the source system type “Others.” uploads/Management/ fdm-migration-guide.pdf