FDMEE: No Brainer or Risk?

Emtec, Inc. Proprietary & Confidential. All rights reserved 2014. Emtec, Inc. Proprietary & Confidential. All rights reserved 2014. Emtec, Inc. Proprietary & Confidential. All rights reserved 2014. Emtec, Inc. Proprietary & Confidential. All rights reserved 2014.

Webinar: An Understanding of FDMEE

Russ Rogers

Reid Kerr

December 2nd, 2014


Agenda

2

Introductions

What is FDMEE

Upgrade Considerations

Process Elements

Understanding Drill-back

Demonstration

Emtec is Your EPM Expert

Q/A


Introductions


Who’s Who on this Webcast

4

Reid Kerr

Senior Lead – Close & Consolidations, Emtec

• 21 Years of hands on consulting experience

• 8 Years at Hyperion (IMRS, Software, Solutions, etc.)

• 12 Years Partner and Independent Firms

• CPA, CMA, Certified (background in accounting, fx, m&a)

• 336-996-4242 office / 336-210-6934 mobile (Go TarHeels!)

• [email protected]

Russ Rogers

National Practice Lead – Close & Consolidations, Emtec

• 22 Years of hands on consulting experience

• 9 Years at Hyperion (IMRS, Software, Solutions, etc.)

• 12 Years Partner, Independent, Firms

• CPA, CMA, Certified (accounting, fx, IC, m&a)

• 312-561-3398 office / 816-721-1908 mobile (Go Jayhawks!)

• [email protected]


Our Team

5

Experience

• Over 400 Applications

• Practical Experience as well as technical expertise across all industries

Support

• In-house technical group – Luis Castillo

• Experience across the breadth of Oracle’s EPM suite

A Cohesive team supporting your Oracle Applications


What is FDMEE?


Financial Data Quality Management – Enterprise Edition

7

FDMEE is available beginning with EPM 11.1.2.3.x

Source: Oracle.com



Financial Data Quality Management, Enterprise Edition

• FDM and ERP Integrator combined into a single product.

FDM + ODI = FDMEE

• Based on ODI with the FDM process wrapper. Combines the platform

strength of ODI, with time tested process and methodology of FDM

• New Customers may only license FDMEE

• Built on Oracle Fusion Middleware platform

• Rebranded as FDM Enterprise Edition

8



Financial Data Quality Management, Enterprise Edition

• Windows Based FDM still available for existing customers

• 11.1.2.3 is terminal release of FDM

• Upgrade in place for the last time

• Migration to FDMEE required starting with 11.1.2.4

• New Customers may only license FDMEE.

• All new implementations are recommended to occur in FDMEE

Improvements

• Integrated security with Shared Services

• Different workflow simplifies maintenance and development

• Reduced need for custom scripting for most straight forward tasks

• Completely web based

9


Upgrade Considerations


Financial Data Quality Management – Why Upgrade

•Classic FDM has some limitations that are now covered by FDMEE.

–For example, when multi-dimensional mappings were needed, most of the people used mapping scripts.

• Difficult to maintain and understand

• Black Box

• Upgrade Considerations (Understatement of the year)

–In FDMEE, we have a new mapping type called Multi-Dimensional mapping.

• New mapping type will probably replace all your mapping scripts.

• In addition, you can use look-up dimensions in FDMEE to support your multi-dimensional mappings.

–Shared Artifacts

• Import formats

• Mapping Tables

–Direct connection to target application

11


Financial Data Quality Management – Why Upgrade

•Classic FDM required separately maintained locations to enforce even slightly different mapping schemas or sources

–The more locations you have, the more you will have to maintain

–Data load rules allow you to simplify your location structure. Two locations for two different file types may be replaced by one location and two data load rules having each one import format

–Can share related mapping further reducing maintenance

• Import process is almost always the bottle neck in Classic FDM

–Mapping process is performed during the import process and 90% of the customers having performance issues during import follow this rule: Wrong mapping logic design -> poor performance during import

–Better performance with large data sets

–Redesigning your artifacts will improve maintenance efforts and workflow

12


Financial Data Quality Management – Considerations

•You will have to re-write your scripts (import, mapping, event, and custom)

–Even if you keep VB for event and custom scripts, you will have to do some changes as VB Script is replaced by VB .NET.

–Event and custom scripts best written in Jython

• Import scripts (dump) support Jython only

• Integration scripts are not supported anymore as import scripts so they need to be implemented in BefImport event script (Jython or VB .NET)

• VB mapping scripts are not supported anymore so you will have to re-write them as Jython or SQL mapping scripts (or replace by multi-dimensional mappings)

–Great opportunity to review your code which sometimes is not as efficient as you think

–Commenting your code - do it now

13


Process Elements



15

File

Excel

XML

Other

Systems

Oracle EBS, PeopleSoft, JDE, Fusion

APPs, SAP R/3

Data Warehouse Data Mart

Data Strategy Management

Financial Close

Planning & Forecasting

Profitability Management

Financial Reports

Microsoft Office

Data & Metadata

Drill-Through & Write-Back

Web Interface

Meta-data


FDMEE Supported Target EPM Platforms

16

FDMEE supports the following EPM target applications (Oracle

Hyperion EPM Architect and Classic):

• Planning

• The Planning module, Oracle Hyperion Public Sector Planning and

Budgeting

• Financial Management

• Essbase ASO and Essbase BSO

• If Essbase has been deployed in standalone mode, it must be

registered with Shared Services since it does not work directly with

FDMEE

• Planning applications that rely on the standalone Essbase

application cannot work directly with FDMEE


FDMEE Is now directly linked to sources – regardless of type

17

FDMEE

• Focuses on workflow with artifacts used to support it

• Define the source

• Import Format – directly reads source fields

• Can combine source fields where necessary e.g. Entity

and Account to identify ICP

• Define the Target Application

• Associates Import format with Target

• No manual coding

• When connecting directly to supported ledgers Source

Accounting Entity is a representative sample

• Allows you to group entities

• Ignore entities if necessary


FDMEE Details You Should Know

18


FDMEE Is Now Directly Linked to Sources – Regardless of Type

19


FDMEE Is Now Directly Linked to Sources – Regardless of Type

20

• Period Mapping still exists but now more flexible and can be shared

• Category Mapping still exists but now reads directly from target application


FDMEE Details You Should Know

21

Ease of Setup – No cryptic

adaptors

Scripting Editor (LAST VB)


FDMEE Details You should know – The Fish Still Exists

22


Understanding Drill-back


FDMEE Supported Platforms

24

FDMEE allows drill thru data sourcing from the following ledgers

• File-based data loads that enable users to import balances from delimited

or fixed-width text files.

• Oracle E-Business Suites11i and 12

• Oracle Fusion Financials

• PeopleSoft Enterprise Financial Management 9.0 and 9.1

• PeopleSoft Enterprise Human Capital Management (HCM) 9.1

• PeopleSoft Commitment Control

• SAP ERP Financial and BW (Business Warehouse)

• JD Edwards General Ledger system

FDMEE supports Human Resource Data for

• PeopleSoft HCM 9.0 and 9.1


FDMEE Technical Setup for Drill Thru

25

Basic technical steps for setup:

• Every setup is different, planning your upgrade is critical. Collaboration with DBA and source system

administrator is critical as well…

• Have DBA setup proper permissions to tables and views for the source system as listed in the on the FDMEE

admin guide: https://docs.oracle.com/cd/E40248_01/epm.1112/erpi_admin_11123520.pdf

• Once table permissions have been set, FDMEE admin needs to log into ODI and enter the database details for

the source system

• Once ODI has been updated, the FDMEE admin needs to create a source system in FDMEE and they need to

add a URL for drill-through to work

• Once the source system has been created, it needs to be initialized

• The tricky part of the setup is the initialization which is where you will find out whether DB permissions for the

source system were set properly. Most errors during this step will be located in the ODI logs, not FDMEE since

ODI is the one performing the integration

• In most cases, synonyms in the database side will be required

• If the initialization is successful, you should see a green check mark for the step in the FDMEE process details

• Once initialization is complete, admin can start creating import formats, mapping tables, etc. to complete the

integration

https://docs.oracle.com/cd/E40248_01/epm.1112/erpi_admin_11123520.pdf


FDMEE Drill Back – How It Works

26

Drill Back is allowed from a base level data point to the source load and then

to the source system.

• Data is only loaded at base level – you can only drill from that level

• Drill Region is enabled on the load

• Drill Back is allowed from any enabled hyperlink: FRS Reports, SmartView, Grids,

Forms

The First Drill Back is from the target application to the load POV in FDM

• This allows the user to see the various loaded components

• Helps allow mapping and or formatting to answer the question

The second drill back launches a prepopulated query to your selected URL

• e.g. PeopleSoft 9.2 launches the Oracle login to the system and prepopulates the

detailed query screen

• Allows access to journal detail

Table assignments can be changed using synonyms


Demonstration


FDMEE Next Steps

28

Virtual Assessment – Free Offering

• 4 hour exercise completed by senior architects.

• Information collected and questionnaire completed prior to session.

• 2 hour collaboration virtually to understand your implementation and needs and deliver findings.

• Deliverables include documented upgrade considerations, broad cost and effort estimate, and

timeline.

FDMEE Roadmap – 4 day effort + Travel

• Detailed review of your FDMEE and HFM applications, processes and artifacts.

• Conducted by practice lead and senior architects.

• 2 day on-site engagement, with rest of work and delivery of findings completed virtually. Four

days of effort for two days of cost!

• Deliverables include documented upgrade roadmap, including detail design considerations,

budget-able cost and effort estimates, and detailed project plan and timeline.

• Cost will be reflected in reduced fees on your upgrade engagement.

To Schedule Now: please email Jennifer Sammons at: [email protected] or

call her at 312-216-4912. Or Feel free to contact us to engage directly:

Russ Rogers

312-561-3398 office / 816-721-1908 mobile

[email protected]

Reid Kerr

336-996-4242 office / 336-210-6934 mobile

[email protected]

mailto:[email protected]




Q & A


THANK YOU FOR YOUR TIME

Please visit us online at www.emtecinc.com

THANK YOU FOR YOUR TIME

Please visit us online at www.emtecinc.com

http://www.emtecinc.com/

Date post:	12-Jul-2015
Category:	Technology
Upload:	emtec-inc
View:	319 times
Download:	1 times

FDMEE: No Brainer or Risk?

Technology