Intro To Fdmee: Presented by Justin D'Onofrio & Joe Stasi

INTRO TO FDMEE
PRESENTED BY JUSTIN DONOFRIO & JOE STASI
>> platformspecialists.com
ABOUT US
> Group of Hyperion & EPM specialists
(MBAs, CPAs, IT backgrounds)
> Focus on efficiency, delivery, and client
service
> 60+ systems implemented across
variety of industries
> Active Hyperion projects and support
contracts
platformspecialists.com
EPM MARKETPLACE
EPMMARKETPLACE.CO
M
u Hyperion services,
tools, and training
offerings
u App Store style with
straightforward
packages and pricing
u Open to partners and
developers
WHAT IS FDMEE?
Another acronym to remember
The new guy/gal in town future FDM replacement, improved version of ERPi
Software to get data to and from Hyperion applications (data integration)
Web-based and integrated with Hyperion Workspace
What will I mainly use it for?
Load data files to Hyperion applications
Load GL system data to Hyperion applications
Export data from Hyperion applications to GL systems
FEATURES & BENEFITS

Available as of Hyperion version 11.1.2.3
Integration with core Hyperion application suite (HFM, Planning, Essbase, etc)
Out-of-box integration with popular GL systems, including drill through
User friendly data mapping, loads, and exports
Audit trails and data validation
Reporting capabilities
Short learning curve from FDM Classic
HYPERION DATA INTEGRATION OPTIONS

FDMEE
Stand-alone ODI
Sweet spot
User friendly mapping and data

load process
Lights out automation and complex

systems integrations
Audience
Finance team / Hyperion Admin
IT team / Hyperion Admin
Easy to
Create loads for multiple users

(multiple users with different
load files)
Unwind information to/from
target systems
Schedule, log, and error check

automated processes
Connect to a wide array of
technologies
Weakness
Complex automation requires

heavy scripting
Learning curve / not as user

friendly
[in our opinion]

ITS MONDAY MORNING

Your boss sends you an email.
He/she wants you to load Actual
data from the new GL system
into your existing Hyperion
Planning application TODAY.
You have FDMEE, but have
never used it.
What do you do?
A) Create an elaborate call in sick scheme vis--vis Ferris

Buellers day off
B) Try your hand with taming FDMEE
C) Mumble non-pleasantries about your boss throughout
the day
FDMEE SETUP TAB

> Allows you to setup key configurations
> Source System:
> Place to register ERP source Systems
> 7 Out-of-Box
> 1 for File
> 1 Other (all else)
> Place to define Target Applications
> Connects to HFM, Planning, Essbase and ARM
> Setup Security Settings for individual users
IMPORT FORMAT
> An Import Format defines the content structure of the
source file/system
> You can navigate to the Import Format section of
FDMEE by selecting: Integration Setup > Import
Format.
> To create a new Import Format select > Add
IMPORT FORMAT
> Next, Name the Import Format, select a Target Application and define the
Source System.
> Anything setup as a File type import will need a File Type and File
Delimiter defined.
IMPORT FORMAT
> Define the mapping between the source and target system dimensions
> The expression field is used to make needed changes to the field being imported
> Out of the box items include changing the amount field delimiter (comma
versus period), removing zero suppression, or assigning a default value
> Scripting is also an option (expression field links to the Script Editor)
LOCATION / PERIOD / CATEGORY MAPPING

> Before loading data youll need to setup:
> A load location and assign an Import Format
> Period(s) that are being loaded (Month and Year) and
> Category (I.E. Actual or Budget).
CREATING A LOCATION
> Navigate to Integration Setup > Location > Add
> Next, Name the Location, Select an Import Format and the Target Application:
SETTING UP PERIODS
> Navigate to Integration Setup > Periods > Add
> Next, define the: Period Key, Prior Period Key, Period Name, Target Period
Month, Target Period Year and Year Target (See Example Below)
SETTING UP PERIODS
> Next, Select the Application Mapping tab > Add
> A box will appear with the new Period setup in the previous tab. Select Ok and
define the fields with the same information.
> Next, repeat the above steps for the Source Mapping Tab.
CREATING A CATEGORY
> Navigate to Integration Setup > Category Mapping > Add
> Youll need to define the Category, Frequency Data is loaded and Target
Category in the Application (See example below for data being loaded into the
Actual scenario).
CREATING SCRIPTS
> There are 3 types of Scripts: Event, Import and Custom.
> Event Scripts are triggered after an event has begun or completed during
the load process
> Import Scripts enable users to manipulate or Ignore imported source data
into useful strings that will later be mapped to the Target system.
> Custom Scripts can be written for a variety of reasons (I.E. Sending an
email when a batch load has completed)
> Scripts are typically written in Jython (See Example of Import Script Below)
DATA LOAD RULE

> Provides a framework for:
> Importing Data
> One or Multiple Files
> By pulling from a defined source system
> Batch Processing
> Scheduled Loads
> View and Verify
> Error/Log Files (Varying degree of data depending on setup)
DATA LOAD MAPPING

> Maps are defined within Workflow > Data Load > Data Load Mapping.
> Note that Maps are created Per Application Dimension which can be
changed via the drop down.
DATA LOAD MAPPING

> There are 5 types of mappings: Explicit, Between, In, Like, Multi-Dimension
> Explicit One for One Mappings
> Between Range of Source Values mapped to One Target Value.
> In Enables Non-Sequential Source Accounts mapped to One Target
Value.
> Like Source Value string is matched and replaced with One Target Value.
> Multi Dimension Specify a combination of multiple dimensions to create a
Unique Source Value to map to One Target Value.
> Special Characters are sometimes used to define Source Maps. I.E. 123*
returns all source members that begin with 123; 123? returns all source
members that begin with 123 and are 4 characters in length.
DATA LOAD MAPPING

> To define a mapping, select the type of map youd like to create from the tabs
and select add.
> As mentioned in the previous slide, some maps use special characters (See
example below of a Like type map).
DATA LOAD MAPPING

> If adding many maps, you can export to excel and input each map directly into
the excel file and load in once complete. Select the All Mappings Tab > Export >
Export to Excel.
> Please note that when mapping, each string must be unique to avoid data
being loaded to improper intersections.
> Once a map is satisfied it completes and continues to the next string. I.E. If
an explicit map is satisfied it will not continue through to Like.
> Note that Target System accounts need to be setup within the application
before they can be defined within the Data Load Maps.
DATA LOAD WORKBENCH

> Allows you to view data at its various stages:
> Import
> Validate
> Export
> Check
DATA LOAD WORKBENCH

> Select Workflow > Data Load Rule > Select a Load rule and Execute
> Select Import from Source box in the pop-up pane to load through Validate or
Export to Target to Load all the way through and select Run.
DATA LOAD WORKBENCH

> If the Load process executes successfully youll see a Green check next to
status.
> If the Load process executes unsuccessfully youll see an X within a Red circle
next to status. To view the error log, click on the Red circle and select show.
IMPORT
> Imports Data directly against a GL or uploads a Flat File.
> To view Imported Data select Data Load Workbench
> If everything has been setup properly youll receive a Orange fish.
> If something was setup incorrectly in a previous step, youll receive an import
error or Grey fish.
VALIDATION
> The Validate stage ensures that all members are mapped to a valid target
system account. If there are any unmapped dimension maps within the source
file it will be kicked out during this stage. Again, youll receive either an Orange
or Grey Fish to signify if the process completed successfully or not.
> If you receive a Grey Fish a second tab will appear, Validation Errors. Select this
tab to view errors at this stage.
VALIDATION
> Review kick-outs and add/update maps or import scripts to satisfy maps.
> Validation errors generally occur as accounts are added to the GL systems on a
month to month basis.
> After updating Maps and or scripts, re-run the validation process.
> If all is correct, continue to Export stage.
EXPORT
> Export stage exports data into the Target application.
> Note that data can be exported with a Replace, Merge, Accumulate or Replace
by Security.
Q&
Please visit epmmarketplace.com to download slides

and for information on our offerings, upcoming [free]
training sessions, and more.

Intro To Fdmee: Presented by Justin D'Onofrio & Joe Stasi

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Intro To Fdmee: Presented by Justin D'Onofrio & Joe Stasi

Uploaded by

Copyright:

Available Formats

INTRO TO FDMEE

PRESENTED BY JUSTIN DONOFRIO & JOE STASI

FEATURES & BENEFITS

HYPERION DATA INTEGRATION OPTIONS

User friendly mapping and data

Lights out automation and complex

Finance team / Hyperion Admin

IT team / Hyperion Admin

Create loads for multiple users

Schedule, log, and error check

Complex automation requires

Learning curve / not as user

[in our opinion]

ITS MONDAY MORNING

A) Create an elaborate call in sick scheme vis--vis Ferris

FDMEE SETUP TAB

LOCATION / PERIOD / CATEGORY MAPPING

DATA LOAD RULE

DATA LOAD MAPPING

DATA LOAD MAPPING

DATA LOAD MAPPING

DATA LOAD MAPPING

DATA LOAD WORKBENCH

DATA LOAD WORKBENCH

DATA LOAD WORKBENCH

Please visit epmmarketplace.com to download slides

You might also like