2. 2
Safe Harbour
• The following is intended for information purposes only on
behalf of Infratects, and may not be incorporated into any
contract. It is not a commitment to deliver any services or
functionality, and should not be relied upon in making
purchasing decisions. This provides no warranties with
respect to the offerings described within. The development,
release, and timing of any features or functionality described
for Oracle’s products remains at the sole discretion of
Oracle. Any third-party names, trademarks and copyrights
contained in this document are the property of their
respective owners
6. 6
About 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
7. 7
About me
• Data Integration Lead @Infratects
• +9 years Hyperion Experience
focused on Data Integration
• Link between functional and
technical people
• FDMEE Blogger and Trainer
– fishing with FDMEE
• Oracle ACE
• Trail running lover
UTMB CCC (102KM 6500m+)
8. 8
Current landscape
• FDMEE 11.1.2.3.700
– FDM Classic and/or FDMEE (IE 11 support)
• FDMEE 11.1.2.4.100 (Dec-2015)
– No FDM Classic available anymore
– FDM > FDMEE migration is a must (95% parity)
• Migration utility released on Aug-2015
– Built using ODI (standalone)
– Migrate 1 target application at a time
– FDM Classic 11.1.1.x/11.1.2.x > FDMEE 11.1.2.4
– FDM Metadata (locations, mappings, control tables, etc.)
– FDM Data (historical data, archived maps, process info)
– Not included (audit information, memo items, Security, Scripts, Custom Reports)
– Post-migration manual steps needed
Upstream
FDM
ERPI
FDMEE
9.3.x-11.1.2.3
11.1.1.3-11.1.2.2
11.1.2.3-∞
10. 10
Looking back at the past
• Crystal Reports
– SQL Query + RPX file
• Standard + Custom Reports
• FDM Workbench Client
– Report Designer
• Scripting capabilities
• Parameters
• API to publish reports from scripts
• Output as PDF, Excel, Word, RTF, or HTML
15. 15
New product, new life
• Oracle BI Publisher templates (RTF)
– No need of BIP license
– Templates located in FDMEE Server
• Not all standard reports migrated
– Audit mapping monitor available from 11.1.2.4.100
• Custom Reports
– BI Publisher
– BIP Desktop (plugin for MS Word)
• Output as PDF, Excel, HTM, or XSLX
• LCM (+ copy templates)
17. 17
BIP Desktop for MS Word
• Used to create new RTF templates
• Does not require BIP installed
• Free download
• Install on client machine
– Version depends on MS Office 32-bit or 64-bit version
• Can import sample XML data generated from FDMEE
– Preview reports offline
18. 18
RTF Templates
• Consume XML data
– Template content and layout must correspond to the content and
hierarchy of the input XML file
• Generates the output report dynamically
• Can be downloaded from FDMEE UI
19. 19
RTF Templates
• Some basics
– Placeholders are used to map data fields (show data)
– Groups are used to designate repeating elements
• BIP supports two methods for creating RTF templates
• Basic RTF Method
– Use placeholders
– At runtime the placeholder is replaced by the value of XML element
– Syntax: <?XML element tag name?>
• MS Word’s Form Field Method
– Place the syntax in hidden form fields, rather than directly into the
design of your template.
23. 23
Why would we need them?
• Enhanced our data load workflow
– Custom Check Report
– HP/Essbase validations
– Check Exchange Rates loaded
– Etc.
• Enrich TB standard reports
– Include target member properties (Ex: account type or descriptions)
– Include additional FDMEE data
– Etc.
• Align with other business reports
– Add company logo
– Change header/footer
– Change colors/format
– Etc.
24. 24
Creating a Custom Report
1. Define the Query definition
– Test in SQL tool (replace parameters with values)
– Export results to XML from FDMEE and import into RTF template
– May require some SQL work for complex queries (views, functions …)
2. Create the RTF template
– Copy existing template
– Import XML file with sample data (BIP Desktop)
– Configure the template as needed
– Run unit tests for each report item (header, footer, groups, etc.)
3. Define the Report definition
– Copy existing or create new one
– Assign Query definition
– Assign RTF Template
– Assign Report Group (+ security)
– Define parameters
4. Test report with parameters
30. 30
Requirement for custom report
• TB Report with both HFM and JDE descriptions
• Add company logo
• A similar report already existed in legacy FDM
• It needs enhancements
– Add JDE Account Descriptions
– Add company logo
31. 31
Solution design
• HFM Account Description is stored in the HFM Database
• The SQL Queries are executed in the FDMEE Database
– Create SQL View in HFM database (Account properties)
– Create Synonym in FDMEE database
• Query Definition
– Join FDMEE tables and Synonym for the SQL View
– 2 parameters (Period and Data Load Rule)
– Generate XML
• RTF Template
– Copy existing template for TB Report
– Create new format
– User XML for unit tests
45. 45
Generate Translation File (11.1.2.4)
• FDMEE supports reports in multiple languages
• We have to create the XLIFF translation file from BIP Desktop
– Save file as reportname_en.xlf
• XLIFF is a standard file format that is understood by many
translation software packages
46. 46
Place RTF template in Server
• Copy the file in the server or upload through Web UI
• Copy XLF file in its language folder (ex: en)
