Edgewater Ranzal presented at ODTUG Kaleidoscope 2015 (KSCOPE15) on the importance of assessing Oracle Hyperion Financial Data Quality Management (FDM) mappings in your Oracle Enterprise Performance Management (EPM) system.

2. Mapping in FDMEE
It's Time to Reassess Your FDM Mappings
Tony Scalese & Francisco Amores Torres
Edgewater Ranzal & Infratects

3. About Us- Infratects
DEEP EXPERTISE
HOSTING
CLOUD
DESIGN
CONFIGURATION
INSTALLATION
STRESS TESTING
UPGRADES
MIGRATIONS
PATCHING
INTEGRATION
SUPPORT
TRAINING
INFRASTRUCTURE
FOLLOW THE SUN
SUPPORT
40+
CONSULTANTS
15+ YEARS
EXPERIENCE
5 DATA
CENTERS
NA EMEA APAC
DEDICATED
MANAGED SERVICES
& SUPPPORT
TEAM
FOCUSED
15
IN BUSINESS
YEARS INFRATECTS FI
INFRATECTS UK
INFRATECTS NL2000
INFRATECTS AUS2008
2009
2012
INFRATECTS US2014
INFRATECTS SP2012
WWW.INFRATECTS.COM

4. About Us – Edgewater Ranzal

5. Our Services – Edgewater Ranzal
Financial Close &
Consolidations
Business
Intelligence
Enterprise
Planning &
Analytics
Data Integration
Services
Training &
Support Services
Advisory ServicesInfrastructure
Costing &
Profitability
Mgmt
Data Integration Services
• FDMEE, ERPi & FDM
Classic
• ERP Integration including
EBS, PeopleSoft & SAP
• Master Data Management
(DRM)
• Automation

6.  Mapping Overview
 FDMEE New Capabilities Overview
 Mapping Design Discussion
 Classic to FDMEE Discussion & Case Study
 Tuning Discussion
 Roadmap Discussion
 Questions
Agenda

7. Mapping Process
Source
TDATASEG_T TDATASEG
Target
AIF_OPEN_INTERFACE
Logic Accts
Mappings

8. Type Description Example
Explicit One to One Mapping GL account 10000 maps
to EPM account Cash
Between A continuous range of source
system members mapping to 1
target member
GL Accounts 10000-10099
map to EPM account
Cash
In A non-continuous range of
source system members
mapping to 1 target member
GL Account 10100,10135,
& 10143 map to EPM
account ST_Investments
Multi Dimension 2 or more source system
members used to map to 1
target member
Account 50799 and cost
centers like ???75 map to
EPM account Severance
Like Wildcard mapping supporting
single or multi character
wildcards
Accounts beginning with
12* maps to EPM Account
Fixed_Assets
Mapping Types

9. Wildcard Usage Example Limitations
? Single
character
wildcard
CC 100?? = Finance
* Multi
character
wildcard
CC 100* = Finance
<x> Use x field of
a
concatenated
source field
<2> for source C1
CompanyCode_Cost
Center = CostCenter
1000_10065 = 10065
Concatenation character
must be underscore
<BLANK> Source field is
blank
<BLANK> = [None] Field must contain a
blank space, cannot be
null
More About Like Maps
See Examples of Expressions Using Special Characters in Admin Guide

10.  New to FDMEE 11.1.2.3.510
 Originally developed for ARM targets but
applicable to any target
 Very powerful for when needing to combine
source system chart fields to derive EPM target
 Enter #FORMAT in the target
● #FORMAT(Source Value,Delimiter)
Advanced Mapping – Format Mask

11. Operator Usage
? Single character wildcard
# Skip/Ignore character at a given position
String/Character Hard coded text to append to the target
* Include all characters for a segment
Format Mask Operators

12.  Source: 12345-6789-012-3456ABC-001
 Format Mask: #FORMAT(“???-*-GROUP-AA##?#*X-
GROUP”,”-“)
● Take characters 1-3 of 1st segment (12345)
● Take the entire 2nd segment (6789)
● Replace the 3rd segment (012) with the word “GROUP”
● Append text “AA” to the 4th segment
● Ignore characters 1 & 2 (34) of the 4th segment
● Take the 3rd character (5) of the 4th segment
● Ignore the 5th character (6) of the 4th segment
● Take the remaining characters of the 4th segment (ABC)
● Append the text “X” to the 4th segment
● Replace the 5th segment (001) with the text “GROUP”
 Target: 123-6789-GROUP-AA5ABCX-GROUP
Format Mask Example

13.  Within a dimension, maps processing in the
following order:
● Explicit, Between, In, Multi Dimension, Like
 Dimensions process in the following order:
● Account, Entity, ICP, Custom1-20
Map Processing Order

14.  Replaces varValues concept
 Supported for Between, In & Like
 Supports Jython or SQL
 Only required when needing to map based on
TARGET dimensions
● Use Multi dimension maps for source values
● Use DLR specific mapping for location and category
based mapping
Advanced Mapping - Scripting

15.  Map based on a debit/credit balance for the
record
Mapping Script Example

16.  Using custom SQL functions
● Map based on logic account value
● Map based on HFM “is icp” metadata property
Mapping Script Example

17.  Limited audit
● Premapping in script
 Limited version control
 “Administrator” owned/maintained
 Unnecessary with new mapping capabilities
 Performance impact pre-11.1.2.3.530
Why Import Scripts May No Longer Be Needed

18.  Parse a chart field
● 100.210.50010.1468.000
 Get & Put functions
 Dynamically assign source entity as Location
Name
Import Script Use Cases

19. Importing Maps
Method Interface Number of
Dimensions
Number
of
Locations
Validation Load Method
Flat File GUI – Data
Load
Mapping
1+ 1 Yes Merge/Replace
Excel GUI – Data
Load
Mapping
1 1 Yes Merge/Replace
Excel GUI –
Excel
Interface
1+ 1+ No Append
Flat File Command
Line
1 1 Yes Merge/Replace

20. Importing Text Maps

21.  Download template from Import  Download
Excel Template
Excel Upload – Data Load Mapping

22.  Uses Excel Named Range
● First cell: Table name (tdatamap)
● Row 2: Field names for table
● Row 3-x: Maps to be imported
Excel Upload – Excel Interface

23.  Applicable to text files only
 Arguments:
● User Name
● Password
● Location Name: FDM location Name
● Dimension Name: ACCOUNT, ENTITY, ICP, UDx
● File Path: Path to text file
● Import Method: MERGE/REPLACE
● Validate: Y/N
● Sync Mode: SYNC/ASYNC
Command Line
OracleMiddlewareEPMSystem11R1productsFinancialDataQualitybin>importmapping.bat admin
PASSWORD TestHFM ACCOUNT E:OracleFDMEE_ShareMap_TestHFM.txt MERGE Y SYNC

24.  Essbase DRs
● Defined as data slice
● Created from mappings regardless data loaded
● Only mappings with explicit target value (A* A1)
 Current approach
● Limits #Drill Regions
● Restricts mapping definition
 Planned approach
● Define DR in Data Load Rules using member
functions
Mapping impact on HP/Essbase Drill Regions

25. Researching Data

26.  View Mappings
 Show Invalid
Researching Maps

27. The Art & Science of Designing Maps
 Science: Understanding what source system
chart fields are required to determine the target
system member and the transformation
(mapping) required
 Art: Designing mapping that is:
1. Accurate
2. Balances
a) Maintenance
b) Performance

28.  High Level (BRs) > Lowest Level (MRs)
 Good start: Dimension Mapping Matrix
The Art & Science of Designing Maps
FDMEE
Source Entity Account ICP C1
Department x
Profit Center x
Account x x
Sub-Account x
Partner Code x
Functional Area x

29.  GL has 1 chart field containing natural account
& cost center (not always populated)
 Cost Center is only applicable for mapping
HFM Cost of Goods & Operating Expenses
Mapping Case Study

30.  Combination of Explicit & Like Maps
FDM Classic Maps

31.  Import script to split the GL chart field to Natural
Account & Cost Center
 Natural Account used as source HFM Account
 Cost Center used as source Custom3
● All mapped to [None]
 Transitioned to mainly explicit maps (116)
 Leveraged Between maps for COGS & OPEX
(7)
 Reduced mapping records (and complexity)
from 171 to 124 – 27% reduction
FDMEE Mapping

32. FDMEE Mapping Result

33.  Explicit maps perform “best”
 Performance penalty for “extra” wildcard maps
Tuning - Map Design

34.  Good mapping design still with lower
performance
 Additional indexes may be needed on
TDATASEG_T
 Analyze your mappings in
TDATAMAP
Tuning: Database

35.  Monitor load process with the DBA
● Use DB Tuning Advisory tools
Tuning: Database
CREATE NONCLUSTERED INDEX [CUST_TDATASEG_T_ENT] ON [dbo].[TDATASEG_T]
(
[CATKEY] ASC,
[LOADID] ASC,
[PARTITIONKEY] ASC,
[PERIODKEY] ASC,
[ENTITY] ASC,
[ENTITYX] ASC
)

36.  Don’t just “lift & shift”
 Recreate varValues mapping as multi
dimension or #SQL
 Remove mapping records that are not
applicable, especially non explicit maps
 Identify opportunities for parent maps
 Test, Test, Test!
● Ported maps
● Redesigned maps
Classic to FDMEE Considerations

37.  DRM Integration
 Mapping Review Mode
 Mapping Audit Report
Roadmap

38.  Fix “Fix Maps”
 Use NOT in multi dimension maps
 Limit entity to active entities only (HFM)
 Include target dimensions in Multi Dimension maps
 Include amount criteria in Account mappings
 Grid for searching mappings across locations and
dimensions
 Define mappings at DLR level for Parent Locations
 Copy maps
Pending Enhancement Requests

39.  All the search fields accept wildcards (? or *)
 E.g.: want to search anything that maps to a
certain account, across all locations
Custom Web for Mapping Searching

40. Tony Scalese
Edgewater Ranzal
ascalese@ranzal.com
Francisco Amores Torres
Infratects
francisco.amores@infrat
ects.com
Questions

41. Edgewater Ranzal
108 Corporate Park Drive, Suite 105
White Plains, NY 10604
Tel (914) 253-6600
Email: info@ranzal.com
Co-Presenter
Tony Scalese, Integration Practice Director
45 Beech Street, Suite
109
London EC2Y 8AD
United Kingdom
Tel +44 (0) 2033 717 174
150 North Michigan
Ave.
Suite 2800
Chicago, IL 60601
Tel (312) 624-7738
200 Harvard Mill
Square
Suite 210
Wakefield, MA 01880
Tel (781) 246-3343
Contact Information

42. Infratects
2401 Internet Blvd., Suite 101
Frisco, Texas 75034
Tel (214) 436-8987
Email: info@infratects.com
Co-Presenter
Francisco Amores Torres, Integration Specialist
Contact Information
Herculesplein 32-34
Utrecht 3584 AA
The Netherlands
Tel +31 (0)88 238 08 00
Horton House
Exchange Flags
Liverpool L2 3PF
Tel +44 (0) 7833 444717
Tekniikantie 14
Espoo 02150
Finland
Tel +358 (0)40 559 2630