Integration with FDMEE and J.D. Edwards Enterprise...

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. Edwards Enterprise One Case Study on Compass Minerals and Grant Thornton EPM Implementation with Hyperion, FDMEE, and J.D. Edwards Enterprise One

Session ID#: 107440

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

About Compass Minerals and Grant Thornton


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 throughout North 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 Western Hemisphere

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

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

About Grant Thornton


•  Grant Thornton LLP is the U.S. member firm of Grant Thornton International Ltd, one of the world’s leading organizations of independent audit, tax and advisory 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 issues through implementing Oracle’s suite of technology applications.

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 data sourcing –  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

Planning / reporting challenges


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

Technology Solution


Joint implementation


•  Grant Thornton and Compass Minerals jointly implemented an integrated solution with Hyperion Planning, Essbase ASO, FDMEE, ODI, and J.D. Edwards EnterpriseOne to seamlessly provide data integration and Drill Back capabilities back to the source system. –  Implemented Oracle's Hyperion Planning for Budgeting and Forecasting with

driver-based modeling. –  Oracle Hyperion Financial Data Quality Management Enterprise Edition enables

business users to perform data integration tasks and Drill Back.

Grant Thornton selected to implement Oracle's Hyperion Planning for Budget and Forecast driver-based modeling, as well as provide integrated Financial Reporting capabilities to the ERP system

Solution: Hyperion Planning and FDMEE


•  Oracle products included in implementation –  Hyperion Planning - Standard data inputs and calculations for budgeting and

forecasting –  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

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

FDMEE (Data mappings, data loads, and drill through)


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

Introduction to FDMEE


•  Financial Data Quality Management Enterprise Edition, FDMEE 11.1.2.3 and Oracle Data Integrator (ODI) 11.1.1.7 is a data process flow tool to extract data 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 adapters

directly integrate the data from the source ERP systems and other data sources. –  ERPi, Enterprise Resource Planning Integrator, provides drill through from EPM

application 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 BSO and ASO, EBS, and EPMA –  Data loaded –  Drill Through at base-level based on the member intersections –  * Metadata source and Write-Back were not used

Introduction to drill through


•  'Drill Through' is defined as navigation from a value in one data source to corresponding data in another source, such as J.D. Edwards.

•  Drill Through can be setup with Hyperion Planning and/or HFM data forms. Essbase (BSO, ASO) can be setup with Smart View and Financial Reports.

•  The landing page is for drill through to J.D. Edwards and to review the data mappings which can be used for research and troubleshooting.

Term Definition Drill down Drilling down moves the user perspective

from aggregated data to detail data. Drill Through

Navigation from a value in an application to the corresponding data in a source system. FDMEE uses a landing page to navigate back to the source system.

Drill Region

Named region of data intersections in the EPM application which contains a name, a URL for the drill through, and intersection information.

Landing page

Displays the GL accounts to visually see the data mappings and drill through to the source system.

Source system

Transaction system in which the source data resides.

Target application

EPM Application to which you can load data with FDMEE.

FDMEE architecture


•  Financial Data Quality Management Enterprise Edition, FDMEE 11.1.2.3 and Oracle Data Integrator (ODI) 11.1.1.7 is the ETL tool to extract data from JDE sources and populate Essbase

•  CMP application utilizes FDMEE to: –  Manage data mappings –  Load data from JDE –  Drill through back to JDE

•  FDMEE mappings and data loads are managed by Finance

FDMEE data management


•  FDMEE is accessible on the EPM Workspace

•  FDMEE features: –  Register ERP Source System –  Source Adapter –  Register Target Application –  Import Format Mappings –  Define the Locations, Period

Mappings, Category Mappings –  Mapping Rules –  Data Load Rules –  * Also included but not used on

the project are Jython scripting, reporting, and batch processing.

FDMEE workflow


•  Setup –  Define the source –  Define the target application –  FDMEE uses the ODI

database connection for JD Edwards.

•  Data Mappings

•  Data Loads

•  Execute Data Load Rule

•  Review Process Details

FDMEE data mappings


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

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

Data mappings – Like


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

•  Key words. <BLANK> and IGNORE are used be FDMEE to Ignore values that are blank – data will not load.

Data mappings - Multi-dimension


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

Data mappings – Explicit


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

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

FDMEE data loads


•  Using the defined Data Load Mappings for the specific location, the data is loaded from the ERP system

Execute data load rule


•  Execute Data Load Rule

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

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 connection issues, etc.

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 for this 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 nothing mapped to a particular dimension value. You have to know your data and what to look for.

•  Nothing will load unless all data maps correctly.

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 drill through back to JD Edwards.

•  The custom Open Interface Adapter was also developed to pull Sales and COGS 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 the bottom level of all the dimensions.

•  When drilling from the target application to FDMEE, there is an FDMEE landing page 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.

FDMEE setup step 2 - J.D. Edwards


•  Install and configure using the J.D. Edwards Data Access Driver (DAD) via the JDE Server Manager –  Support for FDMEE 11.1.2.3 and Oracle JD Edwards EnterpriseOne 9.0 and 9.1

with 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 in

the 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 load rules. By modifying the filter, one data load rule was created. The filter was changed to pull all companies and only ledger types AA and AC. We also added a condition to ignore rows where the data equals zero. This reduced the rows by a 100,000 and greatly improved the data load time.

FDMEE setup step 3 – JDE adapter project


•  FDMEE uses ODI as a platform.

•  The JDE Adapter Project is the connection used for both Drill Through and Data Loads for segment expenses for each Business Unit.

•  ODI itself is a robust ETL tool. We utilized both the customization of the Open Interface Adapter and the JDE Adapter Project (included in the install).

•  The JDE Adapter Project is prebuilt from Oracle to perform the correct queries against J.D. Edwards Enterprise One. Normally, this Project would not need to be modified.

FDMEE setup step 4 – Open interface adapter project


•  The Open Interface Adapter was modified to pull data from the Sales and COGS custom 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 3rd normal form so it had to be unpivoted.

•  The results of this query are mapped to the table called AIF_OPEN_INTERFACE. Other packages could feed data here as well. The results get loaded to FDMEE from there and then the FDMEE functionality can take over.

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 Drill

Through URL for J.D. Edwards EnterpriseOne. –  Target Application - Setup the Drill Regions

FDMEE setup step 6 – Drill regions


•  Target Application - Setup the Drill Regions

•  Drill regions are defined by combination of dimension members. When we define a drill through URL in Essbase, it is stored in a Essbase database 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 target application if it belongs to the drill regions defined in the application.

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

•  Drill Through setup components have the J.D. Edwards EnterpriseOne Name and URL XML, and Drillable Regions based on the base level data loaded.

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.

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]

Login and connect


•  Drill Through to expense detail into JDE journal entry detail.

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

•  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

Drill through to the expense data


•  Drill Down to the bottom and then Drill Through to the expense data

•  From the bottom level of all the dimensions for Feb 2015, Drill Through to the source by selecting Drill-Through on the Smart View menu bar or double clicking on the number itself

FDMEE drill through landing page


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

FDMEE to J.D. Edward EnterpriseOne


•  Internet Explorer will launch a new window into the J.D. Edwards EnterpriseOne General Ledger

•  Login

•  URL gets created dynamically

•  h"p://ovp-‐v-‐wls1py:7777/jde/E1Client.mafService?jdema?asUID=1&jdema?asComponent=JDE_HTMLCLIENT&e1.namespace=&e1.service=E1Client&RENDER_MAFLET=E1Menu&jdema?asLauncher=HOSTED_E1_SERVLET&jdelogoutlink=true&e1.state=maximized&jdecloselink=%5BConfigure+Close+URL%5D&e1.mode=view&jdema?ascacheUID=477&TimeStamp=1409077887137

40

Data synchronization


Data synchronization


•  Data synch used to move data: –  Actuals from ASO to Planning –  Budgets/Forecasts from Planning to

ASO

42

Thank you


Date post:	07-Feb-2018
Category:	Documents
Upload:	vanhanh
View:	281 times
Download:	5 times

Integration with FDMEE and J.D. Edwards Enterprise...

Documents