GT C15 Integration With FDMEE and JD Edwards Enterprise One Jeff Price

8/17/2019 GT C15 Integration With FDMEE and JD Edwards Enterprise One Jeff Price

1/42

Presented on Thursday, April 16, 2015

© 2014 Grant Thornton LLP | All rights reserved | U.S. member firm of Grant Thornton International Ltd

Integration with FDMEE and J.D. EdwardsEnterprise OneCase Study on Compass Minerals and Grant Thornton EPM

Implementation with Hyperion, FDMEE, and J.D. EdwardsEnterprise One

Session ID#: 107440


2/42

2

Agenda

•

About Compass Minerals and Grant Thornton

• Planning/Reporting Challenges

• Technology Solution

• FDMEE (Data Mappings, Data Loads, and Drill Through)

•

Data Synchronization

• Summary



3/42

3

About Compass Minerals and Grant Thornton



4/42

About Compass Minerals (CMP)

4© 2015 Grant Thornton LLP | All rights reserved | U.S. member firm of Grant Thornton International Ltd

• Compass Minerals’ history dates back to the 1800s

– Publicly traded since 2003 (NYSE: CMP)

• The largest salt producer in North America and the U.K.

• A leading supplier of highway deicing products

– Keeping roadways safe in the U.S., Canada and the U.K.

• A key producer of high-quality salt for consumers and industry throughoutNorth America

– Food salt, water care products, packaged deicing, minerals for animal nutrition,and other salt and mineral products

•

The leading sulfate of potash specialty fertilizer producer in the WesternHemisphere

– Helps produce nutritious fruits, vegetables, tree nuts and other important crops

•

Provider of secure records management services in the U.K.


5/42

About Grant Thornton


• Grant Thornton LLP is the U.S. member firm of Grant Thornton InternationalLtd, one of the world’s leading organizations of independent audit, tax andadvisory firms.

• Grant Thornton Technology Solutions practice delivers a broad range of

process, technology and organizational needs across business functions,delivering Business Harmony for our clients.

•

We help our clients manage, grow and solve complex business issuesthrough implementing Oracle’s suite of technology applications.


6/42

Challenges


•

Planning and reporting performed in spreadsheets

– Large, complicated, and slow spreadsheets

– Limited reporting capabilities

– Lack of planning standardization

•

Functional and technical requirements for planning, reporting, and datasourcing

– Report on summarized data with ability to drill up/down

– Improve the budgeting and forecasting process

– Timely access to data for ad-hoc, financial analysis

– Drill through to the General Ledger transactions


7/42

7

Planning / reporting challenges



8/42

Technology Solution


•

Planning requirements

– P&L planning

– Allow for simple/standard user input

– Driver based calculations of margin

– Calculate FX impacts

• Loads / mappings maintained by functional lead

– Monthly loads from ERP, JD Edwards EnterpriseOne (JDE)

– Mappings from JDE to EPM (e.g., entity + GL attribute = segment)

•

Ability for user to drill through to general ledger– JDE “Account Ledger Inquiry” journal entry detail

• Historical data (2006 – present) for reporting purposes


9/42


10/42

Joint implementation


• Grant Thornton and Compass Minerals jointly implemented an integratedsolution with Hyperion Planning, Essbase ASO, FDMEE, ODI, and J.D.Edwards EnterpriseOne to seamlessly provide data integration and Drill Backcapabilities back to the source system.

– Implemented Oracle's Hyperion Planning for Budgeting and Forecasting withdriver-based modeling.

– Oracle Hyperion Financial Data Quality Management Enterprise Edition enablesbusiness users to perform data integration tasks and Drill Back.

Grant Thornton selected to implement Oracle's Hyperion Planning forBudget and Forecast driver-based modeling, as well as provide integrated

Financial Reporting capabilities to the ERP system


11/42

Solution: Hyperion Planning and FDMEE


•

Oracle products included in implementation

– Hyperion Planning - Standard data inputs and calculations for budgeting andforecasting

– Essbase ASO - Historical reporting and Drill Through capability

– EPMA – Hierarchy management

– FDMEE / ODI – Direct link to JDE: Drill Through, Data Loading, and Data Mapping

– Data Synchronization – Data flow between Planning and Reporting

– J.D. Edwards EnterpriseOne (JDE) – Link to financial transactions


12/42

EPM applications


•

Hyperion Planning

– Forms for user input (volume, ASP, COGS, expenses)

– Driver calculations (calculation of margin)

– FX impacts (e.g., Forecast @ Budget Rates)

•

Essbase ASO (Reporting)

– Historical data (actuals) as well as budgets/forecasts

– Data loads from FDMEE to ASO cube

– Drill through from ASO using Smart View


13/42

13

FDMEE (Data mappings, data loads, anddrill through)



14/42

FDMEE objectives


•

Introduction to FDMEE and Drill Through

– Architecture

– Data Management

– Workflow

•

FDMEE

– Data Mappings

– Data Loads

– Execute Data Load Rule

– Review Data Process

• Data Load and Drill Through Setup

– FDMEE, ODI, and JDE Setup Process

– Landing Page

– Drill Through to JDE


15/42

Introduction to FDMEE


•

Financial Data Quality Management Enterprise Edition, FDMEE 11.1.2.3 andOracle Data Integrator (ODI) 11.1.1.7 is a data process flow tool to extractdata from JDE sources and populate Hyperion Planning and Essbase.

• FDMEE is now combined into one platform with FDM, ERPi, and ODI.

– FDM, Financial Data Quality Management, has data mappings and adaptersdirectly integrate the data from the source ERP systems and other data sources.

– ERPi, Enterprise Resource Planning Integrator, provides drill through from EPMapplication via Smart View and Financial Reports to the transactional level detail.

– FDMEE uses ODI, Oracle Data Integrator, as its data integration platform.

•

FDMEE supports HFM, Hyperion Planning, Strategic Finance, Essbase BSOand ASO, EBS, and EPMA

– Data loaded

– Drill Through at base-level based on the member intersections

– * Metadata source and Write-Back were not used


16/42

Introduction to drill through


• 'Drill Through' is defined asnavigation from a value in onedata source to correspondingdata in another source, such asJ.D. Edwards.

•

Drill Through can be setup withHyperion Planning and/or HFMdata forms. Essbase (BSO, ASO) can be setup with SmartView and Financial Reports.

•

The landing page is for drillthrough to J.D. Edwards and toreview the data mappings whichcan be used for research andtroubleshooting.

Term Definition

Drill down Drilling down moves the user perspectivefrom aggregated data to detail data.

DrillThrough

Navigation from a value in an applicationto the corresponding data in a source

system. FDMEE uses a landing page tonavigate back to the source system.

DrillRegion

Named region of data intersections in theEPM application which contains a name,a URL for the drill through, andintersection information.

Landing

page

Displays the GL accounts to visually see

the data mappings and drill through tothe source system.

Sourcesystem

Transaction system in which the sourcedata resides.

Targetapplication

EPM Application to which you can loaddata with FDMEE.


17/42

FDMEE architecture


• Financial Data QualityManagement Enterprise Edition,FDMEE 11.1.2.3 and OracleData Integrator (ODI) 11.1.1.7 isthe ETL tool to extract data from

JDE sources and populateEssbase

• CMP application utilizes FDMEEto:

– Manage data mappings

– Load data from JDE

– Drill through back to JDE

• FDMEE mappings and dataloads are managed by Finance


18/42

FDMEE data management


• FDMEE is accessible on theEPM Workspace

• FDMEE features:

– Register ERP Source System

– Source Adapter

– Register Target Application

– Import Format Mappings

– Define the Locations, PeriodMappings, Category Mappings

– Mapping Rules

– Data Load Rules

– * Also included but not used onthe project are Jython scripting,reporting, and batch

processing.


19/42

FDMEE workflow


• Setup

– Define the source

– Define the target application

– FDMEE uses the ODIdatabase connection for JD

Edwards.

•

Data Mappings

•

Data Loads

• Execute Data Load Rule

• Review Process Details


20/42

FDMEE data mappings


• Types: Explicit, Between, In, Multi-Dimension, Like

•

Mappings are set by location - Rules for manipulating data could be differentfor data source.


21/42

Data mappings – Like


• Like: A pattern. For example, * in Source Value and * in Target Value bringsover the exact value. If we had * in Source and A* in Target, then all ofdestination account values would be prefixed with "A".

•

Key words. and IGNORE are used be FDMEE to Ignore values thatare blank – data will not load.


22/42

Data mappings - Multi-dimension


• Multi Dimension allows one to evaluate values in more than one dimension todetermine the target. You can even bring in members that are not used toload data. For example, to determine Region member, the source data mustbe like NPW* and Division (not even a dimension in this application) must belike 50*.


23/42

Data mappings – Explicit


•

An explicit mapping will override any of the other types of mappings.

Note the Change Sign option – this flipsthe data sign as it loads into Essbase.This option is only available on the

account dimension.


24/42

FDMEE data loads


•

Using the defined Data Load Mappings for the specific location, the data isloaded from the ERP system


25/42

Execute data load rule


•

Execute Data Load Rule

•

Check Import from Source and Export to Target. Can run it in steps to reviewdata before loading. Always choose Store Data. Override clears entiredatabase for Essbase Loads. Can run a range of periods too.


26/42

Review process details


•

Review completed steps• Review logs for troubleshooting.

• Issues could be related to mapping problems, Essbase load errors (maps fine,but members missing in outline), ODI problems, source data base connectionissues, etc.


27/42

Reviewing data – Data load workbench


• One can filter (Show) by Valid, Invalid, Ignored, or All.

•

Goldfish show the progress of the load for Location. A location is defined forthis application as the Scenario called "E1_Actual", year and period.

• If the data is invalid, it will not specifically state why, but it will show that nothingmapped to a particular dimension value. You have to know your data and whatto look for.

•

Nothing will load unless all data maps correctly.


28/42

Overview of FDMEE setup process step 1


• FDMEE uses the JDE Adapter Project in ODI. Business Unit expenses are

loaded from FDMEE and a drill region is created during the load to enable drillthrough back to JD Edwards.

• The custom Open Interface Adapter was also developed to pull Sales andCOGS custom summary table.

• End-user access to Drill Through in Smart View from the Essbase ASO

reporting cube and security is applied in EPM Shared Services.

•

Drill through has to be done at the level 0 of the Essbase cube. This is thebottom level of all the dimensions.

• When drilling from the target application to FDMEE, there is an FDMEE landingpage opened as separate window or tab in Workspace.

– The landing page will direct the user to Drill Through to Source System.

– With drill through functionality, the Landing Page can send the user to the J.D.

Edwards or to review the data mappings which can determine the root cause.These can uncover corrections to be made in the data mappings.


29/42

FDMEE setup step 2 - J.D. Edwards


• Install and configure using the J.D. Edwards Data Access Driver (DAD) via theJDE Server Manager

– Support for FDMEE 11.1.2.3 and Oracle JD Edwards EnterpriseOne 9.0 and 9.1with Tools 9.1 General Ledger

– JDE Data Access Driver installed on a New Managed Instance

– ODI is configured via server settings files (e.g. ini files and properties files) and inthe ODI client configuration (i.e. driver, URL, server name, port, and SID). The

FDMEE config files get updated through Server Manager in JD Edwards E1.

•

In ODI, filters are created to pull data by company and ledger type. Compass

has 52 companies and 2 ledger types. This would have required 104 data loadrules. By modifying the filter, one data load rule was created. The filter waschanged to pull all companies and only ledger types AA and AC. We alsoadded a condition to ignore rows where the data equals zero. This reduced therows by a 100,000 and greatly improved the data load time.


30/42

FDMEE setup step 3 – JDE adapter project


• FDMEE uses ODI as a platform.

•

The JDE Adapter Project is theconnection used for both Drill Throughand Data Loads for segment expenses foreach Business Unit.

• ODI itself is a robust ETL tool. We utilizedboth the customization of the OpenInterface Adapter and the JDE AdapterProject (included in the install).

•

The JDE Adapter Project is prebuilt fromOracle to perform the correct queries

against J.D. Edwards Enterprise One.Normally, this Project would not need tobe modified.


31/42

FDMEE setup step 4 – Open interfaceadapter project


• The Open Interface Adapter was modifiedto pull data from the Sales and COGScustom summary table in J.D. Edwards.It is called F56GSUM – aka Gross-to-Net.

•

The data is stored at a more detailed level

than the GL. The data is not stored in 3rdnormal form so it had to be unpivoted.

• The results of this query are mapped tothe table called AIF_OPEN_INTERFACE.Other packages could feed data here as

well. The results get loaded to FDMEEfrom there and then the FDMEEfunctionality can take over.


32/42

FDMEE setup step 5 – configure drill through


•

Drill Through allows direct access to J.D. Edwards by

configuring in FDMEE on EPM Workspace.– Application Settings store the URL in Setup > Configure

– Source System - Name, Type, ODI Context Code, and DrillThrough URL for J.D. Edwards EnterpriseOne.

– Target Application - Setup the Drill Regions


33/42

FDMEE setup step 6 – Drill regions


• Target Application - Setup the Drill Regions

•

Drill regions are defined by combination of dimension members. Whenwe define a drill through URL in Essbase, it is stored in a Essbasedatabase file.

• When drill regions are enabled, they are loaded into the target application

after data is loaded and consolidated. A cell is drillable in the targetapplication if it belongs to the drill regions defined in the application.

• Check to 'Create Drill Region' on thePeriod, Scenario, and Years dimensions.

• Drill Through setup components have theJ.D. Edwards EnterpriseOne Name andURL XML, and Drillable Regions based

on the base level data loaded.


34/42

FDMEE setup step 7 – Application details


• Target Application > Application Options

– Enable the Application for Drill Through by changing the Drill Region value to Yes.

– For Year, Period, and Scenario, FDMEE uses audit tables to create drill regions.

Drill through definitions (i.e. Drill Regions) for Essbase can be viewed in EAS in the

App/Db folder for each cube.


35/42

FDMEE setup step 8 – Drill through URL


•

The Drill URL in the Adapter

setup is dynamic:

– /jde/HostedE1Servlet?OID=P09200_W09200A_ZJDE0001&FormDSTmpl=|5|6|7|8|9|10|11|12|13|14|15|&FormDSData=||||$ATTR13$||

$ATTR11$|$ATTR12$|AA|AA||*|&jdelogoutlink=e1logout&jdecloselink=[Configure Close URL]


36/42

Login and connect


•

Drill Through to expense detail

into JDE journal entry detail.

• Drill Through has to be done atthe level 0 of the Essbase cube.This is the bottom level of all thedimensions.

•

Connect to the EPM Application

1. Connect to Smart View

2. Login to connect to Smart View

3.

Select the Essbase Provider

4. Select Ad-Hoc Analysis


37/42

Drill through to the expense data


•

Drill Down to the bottom and then DrillThrough to the expense data

• From the bottom level of all thedimensions for Feb 2015, Drill Through

to the source by selecting Drill-Throughon the Smart View menu bar or doubleclicking on the number itself


38/42

FDMEE drill through landing page


•

Landing Page will launch in Internet Explorer– Drill Through to Source

– View Mappings


39/42

FDMEE to J.D. Edward EnterpriseOne


•

Internet Explorer will launch a newwindow into the J.D. EdwardsEnterpriseOne General Ledger

• Login

• URL gets created dynamically

• !"#$%%&'#('()*+,#-$....%/01%2,3*4156789:;1


40/42

40

Data synchronization



41/42

Data synchronization


•

Data synch used to move data:– Actuals from ASO to Planning

– Budgets/Forecasts from Planning to

ASO


42/42

Date post:	06-Jul-2018
Category:	Documents
Upload:	parmitchoudhury
View:	217 times
Download:	0 times

GT C15 Integration With FDMEE and JD Edwards Enterprise One Jeff Price

Documents