Improved FDMEE

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1


New and Improved Financial Data Quality Management, Enterprise Edition (FDMEE) Session 11, 8:30-9:30 AM June 25, 2014

Mike Casey

Director, Product Management


Safe Harbor THE INFORMATION CONTAINED IN THIS DOCUMENT IS FOR INFORMATIONAL

SHARING PURPOSES ONLY. IT IS NOT A COMMITMENT TO DELIVER ANY

MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE RELIED UPON IN

MAKING PURCHASING DECISIONS. THE DEVELOPMENT, RELEASE, AND TIMING

OF ANY FEATURES OR FUNCTIONALITY DESCRIBED IN THIS DOCUMENT REMAINS

AT THE SOLE DISCRETION OF ORACLE.

THIS DOCUMENT IN ANY FORM, SOFTWARE OR PRINTED MATTER, CONTAINS

PROPRIETARY INFORMATION THAT IS THE EXCLUSIVE PROPERTY OF

ORACLE. YOUR ACCESS TO AND USE OF THIS CONFIDENTIAL MATERIAL IS

SUBJECT TO THE TERMS AND CONDITIONS OF YOUR ORACLE SOFTWARE

LICENSE AND SERVICE AGREEMENT, WHICH HAS BEEN EXECUTED AND WITH

WHICH YOU AGREE TO COMPLY. THIS DOCUMENT AND INFORMATION

CONTAINED HEREIN MAY NOT BE DISCLOSED, COPIED, REPRODUCED OR

DISTRIBUTED TO ANYONE OUTSIDE ORACLE WITHOUT PRIOR WRITTEN

CONSENT OF ORACLE. THIS DOCUMENT IS NOT PART OF YOUR LICENSE

AGREEMENT NOR CAN IT BE INCORPORATED INTO ANY CONTRACTUAL

AGREEMENT WITH ORACLE OR ITS SUBSIDIARIES OR AFFILIATES.


Agenda

Overview

Integration Strategy

Content and Features

Best Practices

Q & A


FDMEE Overview


Financial Data Quality Differentiated

Financial data collection and transformation

Repeatable financial processes

Internal controls

Audit trails with dynamic drill through

Write-back capability

Financial Data Quality Management (FDM) is a business

issue, and is defined as the practice by which companies can

effectively and consistently combine the following factors:

FDM helps finance users increase their confidence in the numbers and lowers their cost of compliance by eliminating data integrity

risks associated with collecting, mapping, validating, and moving critical financial data from across the enterprise.


Significant Business Challenges

Disparate Source Systems

Inconsistent account structure

Errors in financial data & metadata collection

Financial restatements

No audit trails back to the ERP/GL/Source data

Weak controls around data & meta data collection

Lack of visibility and transparent processes

Issues in synchronizing data between EPM and ERP


Audit Trails

• Integrate Controls questions

• Store current and historical mapping definitions, docs

• Allow dynamic drill through

to source ERP and files

Data Collection and Transformation

• Read and interpret GL trial balance files and ERP

• Mapping validation against Target dimensions

• Data & Metadata integrity checking against data validation rules

Internal Controls • Source financial document

archival

• Prepackaged audit and internal control reports

• Comprehensive role based security

Repeatable Processes

• Single standard and defined solution for any target application

• Standard upward data certification process

• Standardized database schema

FDM

Write-back Capability

• Write-back to Source System

• Synch ERP and EPM Systems

Oracle EPM System Delivers Confidence with FDM


Financial Data Quality Management Enabling Seamless Metadata and Data Integration

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


FDM Benefits

Confidence in the numbers – FDM provides robust audit trails from source systems to target and back, with robust validation capabilities, providing transparency into the numbers

Decrease cost of compliance – FDM with its internal control checks over the process ensure adherence to company policies and procedures, enhancing controls while lowering costs

Speed and agility – Improve the EPM cycle by days with a Finance owned and maintained application that is quick to implement and supports a simple, easy to follow, repeatable process


Integration Strategy

Develop direct “out of the box” integration

– Sources prioritized based on market demand

– Build using integration framework provided in FDM, Enterprise Edition (FDMEE)

– Table/View adapter to be available in 11.1.2.4

Provide open interface adapter

– Available when out of the box integration not available

– Licensing modified to allow updates to ODI packages delivered with FDMEE

Support file based integration

– Support data in any file format and majority of single and multi-byte encodings

Complete coverage via direct, open interface adapter or file


FDM Enterprise Edition 11.1.2.3

Financial Data Quality Management, Enterprise Edition

– FDM and ERP Integrator combined into a single product

– Built on Oracle Fusion Middleware platform

– Rebranded as FDM Enterprise Edition

– Windows based FDM still available for existing customers

– 11.1.2.3 is terminal release of FDM

– Migration to FDMEE required starting with 11.1.2.4

» Additional license fee NOT required

– New customers may only license FDMEE

FDM Adapters

– No change from today

– Must purchase FDMEE and at least one adapter

All commonly used features from FDM included FDMEE as of release 11.1.2.3.510 – Available now


EPMA ODI Native FDMEE

Metadata from ERP

Predefined Data Format

Any Data Format Requires Coding

Connect to ERP Requires Coding

Drill-through / Write-Back

Audit Trails

Process driven

Data Sync Requires Coding 11.1.2.4

Complex Mapping Requires Coding

Comparison of Integration Options


Why FDMEE is Preferred over FDM?

Combines the best features of both FDM and ERP Integrator

– One stop shop

– Easy to setup and configure

– Individual adapter configuration not required – targets natively supported

– Client components not required (FDM Workbench)

– Simplified menu structure

– Improved performance

Built on Fusion Middleware Technology

– Supports many more platforms and browsers than FDM

Integrated with Shared Services


Supported ERP Source Systems

EBS 11i and 12.x

PSFT Financial Management 9.0, 9.1, 9.2

PSFT HCM 9.0, 9.1, 9.2 to Public Sector Planning and Budgeting

Fusion Financials GL 11.1.2 and 11.1.3

JDE 9.0 and 9.1 with tools 9.1

SAP 4.6c, 4.7 and ECC 6.0 enh 3+

– Prior to 11.1.2.3, certified on Oracle DB only (ERPI)

SAP BW 7.0+

Open Interface Adapter – Extends integration to any source!


Installation and Configuration

FDM and FDMEE included in install list

– FDM available for existing customers

– FDMEE for existing and new customers

ODI Install and Configuration

– Performed automatically as part of FDMEE Install

– Automatically configured for file based loads

– Source ERP connection details entered manually

Install and configuration simplified from prior releases


FDMEE Content and Features


FDMEE Features

Parity with FDM

– Workflow process - Import, Validate,

Export and Check

– FDM mapping types, with the

addition of multi-dimension

– “Fish” icon retained – option to

replace with custom icon

– Logic accounts, check reports, and

check entity

– Condensed menu structure –

workflow and setup


FDMEE Features

HFM adapter parity

– All options available in

FDM available in FDMEE

– Adapter VB based in

11.1.2.3 and requires

FDMEE on windows

– For 11.1.2.4 adapter

converted to java for

platform independence


FDMEE Features

Reporting

– Implemented with BI

Publisher

– FDM Reports ported to

FDMEE

– Generate outputs in

PDF, Word, Excel, HTML


FDMEE Features

Batch Processing

– Scheduler built into

FDMEE

– Support for windows.bat

and Linux shell Scripts


FDMEE Features - Scripting

Replaced by Java based Jython

– VB supported in Event and Custom Scripts

– Custom Scripts available in PSU2

Import Scripting

– Jython only, specify in Import Format

Mapping Scripting

– Jython and SQL Script

– Supported for Between, In, Like mapping types

Event Scripting

– Jython and VB

– Before/After events for Import, Validate, Export, Check


Custom Scripts - Create

– Visual Basic or Jython

– Script files stored in

/data/scripts/custom folder

on FDMEE server

– Once created, the user

must register the custom

script


Custom Scripts - Register

– Define parameters

associated with script

– Parameter types include

» POV Location

» POV Period

» POV Category

» POV Rule

» Query

» Static

– Associate a script with a

target application


Custom Scripts - Run

– Available from the UI only

– Select script and then

execute

– System will present

parameters and then user

can verify or change

– Submit to process


Custom Calc Scripts for Essbase and Planning

– Prior release only supported default calc script

– Define script to execute as part of target application

details

– Multiple scripts may be run

– Script execution assigned a scope, event and

sequence


Open Batches

– Load in multiple files in a

single run

– POV determined from

the file name using the

file name separator

– Define open batches

from the batch definition

UI

– Run from the Batch

Execution UI


Custom Target Applications

– Used to extract data

from FDMEE to a flat file

– Select columns to

include

– Define Application

Options

– Set up artifacts like any

other workflow in the

system

– Run workflow to extract

data to file


HFM Journal Templates

– Excel based journals

– Same format as FDM

– Journal Status

– Download template from

Workbench

– Load journal by selecting

file, checking file, and then

posting

– Full parity with FDM


Load Data and Mappings using Excel Format

– Prior releases only

supported CSV format

– Data loaded using Trial

Balance Template

» Download from Workbench

– Mappings using mapping

template

» Download from Mapping UI

» Template is available in import

dropdown

– Achieves parity with FDM


HFM Intersection Check Reports

– Validate HFM data

intersections

– Generated as part of the

data validation step of the

workflow


File Append and Replace Mode

– Append new rows to

existing rows in

TDATASEG

– Replace data in

TDATASEG with data in

the selected file

– Provides additional

flexibility for file based data

loads


Data Load Options for Essbase/Planning

– Two methods to load data

to Essbase

» File – FDMEE will create a file

in loaded directly by Essbase.

» SQL – In-Memory loading of

data to Essbase

» Default is SQL

– For example – The current

Essbase SQL driver does

not support an encrypted

database, and the file

method is required


Prefix Duplicate Dimension Members

– Dimension name added to

member name during

export ([dim]@[member])

– Added for all dimensions

– Only use this option if

members are duplicated

across dimensions

– If duplicates within a

dimension, then this option

is not applicable and

should be set to No


File Based Multi-Period Load

– File based option, delimited

files only. Header not

required.

– The expression field in the

import format specifies the

amount fields in the file

– Select the starting and ending

periods when running the rule

– Specify the explicit periods in

the data load rule if not

contiguous.

– Not allowed from the

workbench

– Excel template also supports

multiple periods


FDM Enterprise Edition – 11.1.2.3.510

New Mapping Type –

Format Mask

– Supports ARM mapping

requirements

– Also available for non-

ARM implementations

– Enhanced replacement

and substitution

functionality for targets

Source

12345-6789-012-3456ABC-001

Target

#FORMAT(“???-*-GROUP-AA##?#*X-GROUP”,”-“)

Result: 123-6789-GROUP-AA5ABCX-GROUP

Explanation

Take the first three characters of the first segment, take the

entire second segment, replace the third segment with the

text “GROUP”, prefix the fourth segment with AA, drop the

third and fourth characters, keep the fifth character, drop

the sixth character, keep ABC and add suffix “X, replace

the fifth segment with the text “GROUP”.


Additional Considerations

Features from FDM not ported to FDMEE

– Tax Adapter

– Enterprise Adapter

– Time line

– Certification and Assessment

Additional smaller features/parity items to be included in release

11.1.2.4

Migration utilities for FDM to be provided with 11.1.2.4, or shortly

after the base release


FDM Enterprise Edition

Migration assistance for customers moving from FDM to FDMEE

– Migration of core artifacts from FDM to FDMEE in 11.1.2.4

Additional integrations

– Data Sync between EPM Applications

– Sub-ledger transactions for Account Reconciliation Manager

Provided via a generic table/view adapter

– Tax Provision and Explicit support for HPCM

– Fusion Commitment Control with PSBP

– Table/View Adapter: Import from any relational db source with simple UI mapping

– SAP BW Metadata Load

Roadmap Highlights


FDM Enterprise Edition - Continued

Additional Features

– Graphical Import Format Builder

– Integration with FCM

Web service that can be called from FCM

Open FDMEE from FCM

POV Locking

– Check Rule Test

– Fix explicit mapping rules from workbench

– Review mode for mapping UI

– Integration with Strategic Finance

Roadmap Highlights


FDM Enterprise Edition

Initial release of PBCS 11.1.2.3.400

– Includes FDMEE 11.1.2.3.000

– File based integration only

PBCS 11.1.2.3.412

– Includes FDMEE bug fixes from 11.1.2.3.510

– Load data and mapping rules via Excel

– Multi-period load from a file

– Changes to EPMCopy to kick off data rule after file upload

PBCS 11.1.2.3.600

– FDMEE 11.1.2.4 candidate for inclusion

– Investigating inclusion of scripting

Security concern for the cloud

– Better on premise and cloud to cloud integration considered

Features included in Planning and Budgeting Cloud Service (PBCS)


FDMEE Best Practices


Best Practices – All Application Types

Define efficient mapping rules

– Use fewest necessary

– Define with an eye towards maintenance

Use workbench to find mapping errors before loading

– Options for Valid, Invalid, Ignored and All data

– Ensure all rows are mapped

Use Incremental load when available

– EBS and Fusion sources only

Set log level to 5 to debug issues

– Process log available from FDMEE UI

– Also search for ERPIntegrator0.log on FDMEE server


Best Practices – Other Application Types

Financial Management

– Use intersection validation report as

needed

Identifies invalid cells on target

Resource intensive – be careful

with large data sets

Will stop partial loads if target

metadata missing

Planning

– Include currency dimension in import

format

– Invalid cells will show in FDMEE log

as Essbase errors


Best Practices – Other Application Types

Account Reconciliation Manager

– All data is loaded to ARM – mapped or

unmapped

– Limit the number of unmapped sources

Use IGNORE rule type as needed

Analyze data in workbench before

loading to ARM

– Concatenate source fields for easy mapping

to profile dimension

Use new #FORMAT Mask feature as

needed

– Mapping only required for Profile and Source

Type dimensions


Best Practices – Other Application Types Profitability and Cost

Management

– Load BSO cube within the model

Explicit support in 11.1.2.4

– Duplicate members used across

dimensions

Handle via mapping or with “Prefix

Dimension for Duplicate Members”

option

Use “@” to append dimension name

to member

Use “.” between members to define

full path


Q & A


Date post:	16-Jan-2016
Category:	Documents
Upload:	umapathi-baskar
View:	153 times
Download:	2 times

Improved FDMEE

Documents