fdmee hands-on lab - epmclarity.com · mappings types explicit –this is a map of one member in...
TRANSCRIPT
www.123olap.com
FDM / FDMEE’s strengths
▪ Data integration and mapping in a end-user friendly
interface.
▪ This allows for the management of data integration
and mapping to be decentralized.
www.123olap.com
FDM vs. FDMEE
▪ FDM sunset - 11.1.2.3 is the terminal release for FDM
Classic
▪ Workspace Integration
▪ ODI
▪ Multi-platform and multi-browser support
▪ LCM – makes migrations easier
▪ Multi-dimensional mappings (multi-dim only on
source)
▪ FDMEE Data Sync (EPM to EPM integrations)
▪ 64 bit
www.123olap.com
Menus - Workflow
www.123olap.com
Menus - Setup
www.123olap.com
Getting Started
▪ Source system▪ ERP-EBS, JDE, SAP,etc.
▪ File
▪ Setup Target system▪ EPM – HFM, Essbase –
•Map Dimensions to the fields in FDMEE
•Configure app specific options. Different options for Essbase vs.
HFM
www.123olap.com
Getting Started
▪ Import Format
▪ Location
▪ Period Mapping -When adding an application
period, a global period must first be selected.
▪ Category Mapping
▪ Metadata mapping
▪ Data Load Rule
▪ The fish
www.123olap.com
Location and Import Format
▪ Location requires an import format
www.123olap.com
Import Format - 1
▪ Maps the source to the target
www.123olap.com
Import Format - 2
▪ Maps the source columns to the target columns
www.123olap.com
Mappings - Notes- Executed in order : Explicit, Between, In, etc.
- Can be run for a specific rule
- Within a mapping type, maps are processed by the alphabetical order of the rule
name. To make sure something processes last, make the rule name zzz_____.
- Scripts can be added to Between, In, and Like mappings
- IIf a source member should not be loaded to the target application, map the source member to a target
member of IGNORE.
www.123olap.com
Mappings Types
▪ Explicit – this is a map of one member in the source to one member
in the target, like 12345 -> Cash
▪ Between – this specifies a range of members in the source to a single
member in the target, like 12300 to 12350 -> AcctsRec
▪ In – specifies many single members in the source to one member in
the target, like 12301, 12310, 12341 -> Inventory
▪ Multi Dimension – allows a member to be mapped based on another
dimension, like entity 110 account 12349 -> Cash and entity 120
account 12349 -> Inventory
▪ Like – uses wildcards to dynamically map members based on criteria,
such as 1234* (anything starting with 1234) -> Prepaids
www.123olap.com
Scripts - Import
▪ Import – setup in Import Format in “expression” field.
Syntax includes function definition that is same name
as python file - which is how script is referenced in
“Expression” field (see screenshot below)
www.123olap.com
Scripts - Mapping
▪ Mapping – consider writing this logic in SQL b/c
Jython mapping scripts are performed line by line.
▪ Does not require a function definition like Import
Scripts.
▪ Sample: account = fdmRow.getString("ACCOUNT") entity = fdmRow.getString("UD1") # Map based on account and dept column values fdmResultMap["ATTR1"] = account + "-" + entity if (account[0:2] == "71"): fdmResult = "7110"
www.123olap.com
Scripts - Event
▪ Event – triggers (events) at each step in the process
▪ Fxn definition not req’d-unlike Import Scripts.
www.123olap.com
*** Start Hands-On ***
www.123olap.com
Pick an Entity
▪ For the remainder of the class, each student should
label their work with one of these HFM entities. This
way everyone’s work will be unique. The instructor
will help coordinate assignment. In the screenshots to
follow, replace 540 with the assigned entity except
the one place noted.▪ 110 120 130 140 210 220 230 510 520 530
www.123olap.com
Working directory is here
www.123olap.com
Note on POV
▪ POV is crucial in FDMEE▪ Click on Location name which
is a “link” – there you can edit
POV details
www.123olap.com
Option A – Fastest and Easiest - 1
▪ Screenshots to follow this slide
▪ Create new Location : “YourName_YourEntity” (i.e. “Bernard_530”)▪ Leverage existing Import Format and existing Parent Location as you see in screenshot on following
slide
▪ Create new Data Load Rule “YourName_YourEntity” (i.e. “Bernard_530”)
▪ Heads up – make sure you pay attention to the POV.
▪ Notes:▪ Location will be set up to inherit mappings from a pre-defined Location. Ambitious students can try to
set those up manually using the slides in the Appendix of this deck but the instructor will NOT have time
to support this approach so you will be ON YOUR OWN if you choose this path.
www.123olap.com
New Location
- Name the Location “YourName_YourEntity” (i.e. “Bernard_530”)
- Leverage existing Import Format and existing Location. We inherit maps from the existing Location
www.123olap.com
Location Setup - Notes
▪ Import Format – provides detail on reading the incoming
data to the location
▪ Parent Location – locations can be linked together for
mapping purposes – if five ERPs use the same chart of
accounts then one mapping can be shared
▪ Accounting Entity – used for integration with specific ERPs
▪ Check Entity and Check Rule – related to the validation
process discussed in a later chapter
▪ Integration Options – additional fields that can be used for
scripting purposes
www.123olap.com
Data Load Rule
Note : when you want to set the file name,
hit “Select”, then you will see screenshot on the follow slide
Or you can type in what you see in the screenshot above
www.123olap.com
Data Load Rule – import file
www.123olap.com
Option A – Run Load – Screenshots after this slide
▪ Use Workbench and/or DLR:▪ Data Load Workbench (The fishes) – found in “Workflow” menu
• Hit import >> accept defaults and hit okay• Hit Export >> accept defaults and hit okay
• Check “Process Details” to see log from your import
– found in “Workflow” menu
– there will be an error on the “check” step
▪ Data Load Rule - found in “Workflow” menu
• Hit “Execute” >> check “Import from Source”
and “Export to Target” (see screenshot)
• Hit Run• Check “Process Details” to see log from your import
– found in “Workflow” menu
– there will be an error on the “check” step
www.123olap.com
Data Load Workbench
▪ Click Import▪ Accept defaults
▪ Click Export▪ Accept defaults
www.123olap.com
Execute Data Load Rule
www.123olap.com
Check Process Details
www.123olap.com
Option B – Longer and more hands-on.
▪ When you see a screenshot, this almost always
means you must replicate what you see in the
screenshot.
www.123olap.com
Location Setup - 1
▪ On the Setup panel click on Location.▪ The Location screen has two sections, a summary section at the top
and a detailed section at the bottom for the highlighted item at the
top.
▪ Add a new location by clicking the Add button
(green +) at the summary (top) section.
www.123olap.com
Location Setup
- Name the Location “YourName_YourEntity” (i.e. “Bernard_530”)
- Leverage existing Import Format and existing Location. We inherit maps from the existing Location
www.123olap.com
Location Setup - Notes
▪ Import Format – provides detail on reading the incoming
data to the location
▪ Parent Location – locations can be linked together for
mapping purposes – if five ERPs use the same chart of
accounts then one mapping can be shared
▪ Accounting Entity – used for integration with specific ERPs
▪ Check Entity and Check Rule – related to the validation
process discussed in a later chapter
▪ Integration Options – additional fields that can be used for
scripting purposes
www.123olap.com
Import Format Setup
Name – set the Import Format name to Fixed_ and then the assigned entity number
Source –can either be ERP (which includes flat files) or EPM applications
Target – Specify the desired Oracle EPM application
File Type – flat files can be delimited or fixed format or multiperiod – more on multiperiod in a
later chapter. Select Fixed.
www.123olap.com
Import Format Sample Files
– Fixed Format / Delimited
Note : We are using Fixed Format in this lab
www.123olap.com
Import Format – MappingsImport Script “AP_EntityName” (i.e. “AP_540”) for Account is for later – if you have time.
For now, leave that blank
www.123olap.com
Data Load Mapping - POV▪ Before working on the mappings, the location must be set properly at the bottom of the
screen. This area is called the point of view. There are five fields: location, period, category,
source, and target. Source and target are based on the location and displayed information
only.
www.123olap.com
Data Load Mapping – how to setup
There are four ways of building the mapping tables for a location.
▪ Build maps internally within FDMEE
▪ Import the maps from an Excel or text file
▪ Assigned a location as a parent location of another, which
applies the parent location’s maps to both
www.123olap.com
Data Load Mapping – Manual Setup
This lab typically not long enough to do this but the slides to follow are
Here if you are fast and ambitious
www.123olap.com
Data Load Mapping - explicit
www.123olap.com
Data Load Mapping - Between
www.123olap.com
Data Load Mapping - Like
www.123olap.com
Data Load Mapping – Multi-Dim AR
www.123olap.com
Data Load Mapping – Multi-dim ICAR
www.123olap.com
Create Data Load Rule 1
Note : when you want to set the file name,
hit “Select”, then you will see screenshot on the follow slide
Or you can type in what you see in the screenshot above
www.123olap.com
Create Data Load Rule 2 – import file
www.123olap.com
Run Load – Screenshots after this slide
▪ Use Workbench and/or DLR:▪ Data Load Workbench (The fishes) – found in “Workflow” menu
• Hit import >> accept defaults and hit okay• Hit Export >> accept defaults and hit okay
• Check “Process Details” to see log from your import
– found in “Workflow” menu
– there will be an error on the “check” step
▪ Data Load Rule - found in “Workflow” menu
• Hit “Execute” >> check “Import from Source”
and “Export to Target” (see screenshot)
• Hit Run• Check “Process Details” to see log from your import
– found in “Workflow” menu
– there will be an error on the “check” step
www.123olap.com
Data Load Workbench – don’t forget POV !
▪ Click Import▪ Accept defaults
▪ Click Export▪ Accept defaults
www.123olap.com
Execute Data Load Rule – don’t forget POV !
www.123olap.com
Check Process Details
www.123olap.com