Basics of fdmee

2015
BISP Solution Inc
Ashima Rajput
[FDMEE GETTING STARTED]
This document contains basics of FMDEE, comparison with FDM and FDMEE GUI walk through. Someone
who is new to FDMEE can refer this document as getting started guide.

www.bisptrainings.com Page 1
Table on Contents
Product Guideline
 FDMEE Introduction
 FDMEE Overview
 Architecture of FDMEE
 FDM VS FDMEE
 Value added Features in FDMEE
 FDMEE GUI Components
User Interface of FDMEE
 Navigate
 Workspace
 Help
 Task Pane Options
 Workflow
 Setup
 System settings
 Application Settings
 Integration Setup
 Import Format
 Location
 Period Mapping
 Category Mapping
 Excel Interface
 Data Load
 Data Load Mapping
 Data Load Rule
 Batch
 Batch Definition

FDMEE Introduction: Oracle FDMEE is designed to integrate Enterprise Resource Planning
(ERP) systems with Oracle's Hyperion EPM applications. The beauty of FDMEE is lies in ease of
access with other Oracle EPM tools using common workspace. FDMEE intuitive interface with
underlying engine as Oracle Data Integrator makes it first choice among users. FDMEE sits on
top of Oracle Data Integrator and orchestrates the movement of metadata and data into EPM
applications.
After releasing of 11.1.2.3 FDM and FDMEE united in one single product .FDMEE integrates
FDM and ERPi with enhanced performance. FDMEE (Financial Data Quality Management,
Enterprise Edition) is an enhanced version of FDM (Financial Data Quality Management)
Overview
FDMEE can integrate Data and Metadata across EPM and ERP applications or across EPM
applications. FDMEE can also write back modified budget data to ERP.
FDMEE Architecture
The underlying FDMEE architecture is similar to ETL fundamental process. Basically, FDMEE
accommodate with three parts, first is ERP system from where we Extract data or metadata
called source system it could be flat file, Text files, PeopleSoft, Oracle, SAP, JD Edwards etc.
Second is ODI Agent (Oracle data integrator), it is an integrator tool which follows the concept
of ELT (Extraction, Load, Transformed), first data will be extracted from source system and then
it loads data into target and the target system can be used as intermediate transformation. ODI
and ERP’I both tools together perform integration. FDMEE takes place of FDM + ERP’i. However,
staging tables are used during intermediate transformation

FDM VS FDMEE
 FDMEE is the upgraded version of FDM with advanced features.
 FDM was a standalone product therefore It doesn’t include workspace, whereas FDMEE
is fully integrated with workspace.
 FDMEE has underlying engine as ODI (Oracle data integrator) and it supports LCM (EPM
Lifecycle Management) which is missing in FDM.
 FDMEE supports multiple platforms and browsers.
 FDM supports only VB Script whereas FDMEE supports both Jython and VB script.
 Multicolumn filters FDMEE, missing in FDM.
 Mapping into FDM was a complicated or cumbersome process where we have to
browse for target value to find them out whereas in FDMEE it is much easier because
source and target on same screen.
FDMEE Value Added Features
 FDMEE contains all the features which we used in classic FDM.
 FDMEE support HPCM (Hyperion Profitability and cost Management) for target
application.
 FDMEE supports HFM (Oracle Hyperion Financial Management) custom application (Tax
provision).
 Using FDMEE data synchronization, one can easily move data different EPM applications
without creating intermediate data file. for example, synchronizing data enables you to
move data from Financial Management to Oracle Essbase for reporting

FDMEE GUI Components
User Interface of FDMEE
 The interface of FDMEE remodel in a way that is exciting and impressive.
 FDMEE make us easy to work on it because we can obtain directly EPM workspace.
 We have common workspace for HFM and planning.
 Accessed through the same Workspace HFM and Planning are accessed.
 The Fish still alive for determining our work progress.
 Work bench and workflow are more customizable so many options are present for
different view of data like we can see invalid records, ignored records etc.
 We also have offline mode for execution in FDMEE.
 Rule execution make easy to operate like One click for Import

 POV Locking present in FDMEE, by using POV lock we can apply lock for an individual
location so that it helps to stop modifying data. We can only load data when POV is
unlocked unlike older version as it was presented on application level which was difficult
to manage.
 Import format builder helps to provide graphical representation mapping of source and
target dimension members.
 In import format, the restriction of using max 5 segments while concatenating source
dimensions for ERP segment, has been eliminated.
 Duration of validating step in Data load Workbench with Fix maps option one can view
the error by fixing them.
Getting started with FDMEE
Login to workspace and open data management

Now select Navigate - Administer - Data Management
From there you will find Navigate Tab

After click on Navigate, select Administer and  Data Management
After click on Data Management, you enter into FDMEE environment.
This is the User interface OF FDMEE here we perform our task.

Navigate
Navigate tab is the entrance of FDMEE it helps us to navigating FDMEE from oracle Hyperion
Workspace from there we enter into Oracle Hyperion Financial Data Quality Management,
Enterprise Edition.
Workspace: Workspace is used to access oracle Hyperion content like reporting and Analysis it
is an Web User interface
Help: With this menu people can take online help from oracle technical support Knowledge
about FDMEE and, we can view current version on which we are working.
Task Pane Options: once you clicked on Data management then you see task Pane option
which resides to the left of FDMEE if you want you can change its size. This provide choices to
handle FDMEE and its features this contains two option one is Workflow and other is Setup
tabs.

Workflow: In Task Pane you can see workflow tab from here we perform our main objective
which is integrate data and metadata from ERP system (Source system) to EPM system (Target
system) and also check data validation means verifying that all members should be mapped
with valid Account you can also import and export data into source and target from here.
Import represents load data from source system and in export we load the mapped members
into target system.
When we are done all the work from workflow, we find fish icon over there which indicates our
status of each process which we have done so far. If Fish color is orange that means happy
moment we success on that step else if fish color Gray, then it indicates failed process.
In above diagram you can see it how it looks.
Setup: With the help of setup tab user can setup all the things related to data like set source
and Target system for data loading, System settings we can create application folder define
import format, all mapping, data load rule we discuss all these in detail so that we will find how
these things works in FDMEE.

System settings This option you will find under Configure here we choose path where we want
to create application root folder in my case path is after giving path click on create Application
folders button once you clicked on that go to specified path where you can see three folders
are created automatically named as data, inbox, outbox after seeing this return on FDMEE and
click on save. Under these folders our Application artifacts going to be store.
These folders will be created on given path(c:FDMEE)

Basically, here we are going to choose our source system from here we pull our source data and
put into Target system in my case my source system is File you can view in dropdown Profile
type  File, means we import data from File system. System settings required to be done only
once.
Setup -- Configure -- System Settings
If you are not able to view source system under dropdown than register it by going under
Register -- Source System

If Your source is different from file than click on add button below you find option for adding
source
Here you can give all the details and select your source system type.
Application Settings:
In system setting we gave definition of source Application but in Application settings we give
definition of Target Application. select our Target application where we want to load data here
my Target system is Sample-Basic (Essbase cube) you can view in dropdown Target Application
 Sample-Basic, means we import data from File system to Sample-Basic cube.
Under Application settings my application should be register.in order to register our application
should view in Target Application drop down if you can view your application than select it or
otherwise you need to add target application form register  Target Application.
Setup -- Configure -- Application Settings

If your Target is not present under dropdown than register it by going under
Register -- Target System
You will view this window

If Your Target is different from Sample-Basic than click on add button below you find option for
adding Target system.
Here you can give all the details and select your Target system type. And from Name select your
cube name. Than provide name In Target Application Summary. In application details you can
see all the details comes automatically related to dimension mapping this refers to staging
table.
Integration Setup: integration setup is all about integration means how our data/metadata
integration accomplished via FDMEE to source system into Target system here we have options
in integration setup like Import Format, Location, Period Mapping, Category Mapping, Excel
Interface.
Setup - Integration Setup

Import Format: In import format we define how data will pull from source system and put into
staging table Now if you see your Import format in already in list like in my case my source is
File and Target is Sample-Basic already present in list then select it.
Setup - Integration Setup Import Format
If Import format not present in list than add it by click on add button you will have option below
to add new import format fill all the details like Name of import format than source Type,
Source File etc. File Type Delimited means your source file contains which type of delimiter in
my case it is semi-colon. Click on save than need to define Mapping Type.

Here define Mapping based in your source File provide Source column name than Field Number
of source
Location: Once we define Import Format define Location Here if location not available in list
than click on add button and fill related details.
Setup - Integration Setup Location
To Specify new Location, give any name to Location provide Import Format Name which you
gave in last step once you provide Import format system automatically fetch all other details
related to source and Target. Then click on save. The location combines related mapping and
data load rules into a logical grouping.

Period Mapping: suppose we want to load data for Jan 2016 so we can specify this into Period
mapping. Period mapping is used to map source data(File) to Target dimension which is period
dimension(Sample-Basic) we can define mapping at different levels like Global, Application,
source system.
Setup - Integration Setup Period Mapping
Category Mapping: If category exist under category list which you want to load into target
dimension than select it or otherwise create them.
Setup - Integration Setup Period Mapping

For creating New click on add provide source system data to Target Scenario dimension
member Define category mappings to map source system data to target Scenario dimension
members
Excel Interface: Excel interface is a new feature in 11.1.2.4 version. This allows users to export
and import data to Excel and vice versa. FDMEE provides different artifacts to be exporting to
excel. Using the Excel Interface, you can easily download FDMEE metadata items to Excel for
review. There’s a preset list of metadata items you can download, e.g. location detail and
import format detail. You can also specify a table name from the FDMEE database repository.
The Excel Interface component also lets you upload metadata elements to FDMEE The Excel
Interface Upload feature can greatly reduce an application rebuild.
Key points of excel interface we need to Know.
 Data modification is not possible we can only insert data.
 We are not able to verify data.
 FDMEE automatically skip those rows which are duplicate
Setup - Integration Setup Excel Interfac

Steps to Upload data
Excel Interface -- File -Upload
Enter name of excel file which you want to upload than click on upload. We can also select
file from list
We can also download file.
Excel Interface -- download
In order to download select Entity type - file -click on select -Download

Data Load: In this Part of FDMEE We will see process of Data Load and validation of data and
finally how we export data from ERP to EPM system
Data Loa
Data Load Mapping: We use Data Load Mapping for map source dimension member to their
target Application Dimension member. We have Location, Period, Category set of Mappings for
Data Load Mapping. For that we need to select for which member we want to load data like in
my case I choose Product as a dimension than we have types of Mapping choose one of them
then click on add then fill all details. We need to specify mapping for each dimension.
Setup - Data Load -- Data Load Mapping

Data Load Rule: We need to create data Load rule for location and category to describe what
we are going to import from ERP system.
Workflow -- Data Load - Data Load Rule
Basically, data load rule represents our file which we want to import with other details once
we complete data load rule we need to save it so execute button enabled than click on it here
Execute rule window will appear here we need to specify one or more periods. Run it than
you will see one process id has created than verify it by click on save

Batch: FDMEE providing batch scheduling from the web interface using batch processing we
can use it to automate our data load as per our requirement like we can schedule batch to
run hourly, weekly or month end close as per our business requirement.
Setup -Batch -Batch Definition
 We can make one batch which contains more than one load rule in a time.
 FDMEE provide two types of mode to run batch it could be serial or parallel.
 We need to give parameters of batch
 We can also create one master batch which has more than one batches. For example,
you can have one batch for metadata rules run in serial mode, and a second batch for
the data rule run in parallel mode.
 we can connect a batch into a batch group for security and flexibility.
Batch Definition: Batch definition contained batch jobs, parameters, type of rules in a batch,
one batch has one rule only and rule could be metadata, data, batch or open batch. Batch
created by administrator.
To add New Batch Definition.
Setup - Batch - Batch Definition - under Batch Definition Summary -- click on add

Provide Name then select Target Application, Data Type(rule Type) , Execution Mode from
dropdown list fill all other details

Basics of fdmee

More Related Content

What's hot (20)

Similar to Basics of fdmee (20)

More from Amit Sharma (20)

Recently uploaded (20)

Basics of fdmee