Ag - Fdmee Material

These eKit materials are to be used ONLY by you for the express purpose SELF STUDY.
SHARING THE FILE IS STRICTLY PROHIBITED.
Activity Guide
D83546GC10
Edition 1.0
March 2014
D85653
Oracle University and (Oracle Corporation) use only.
Hyperion Financial Data

Quality Management EE
Administration
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Author
Lea Jensen
Technical Contributors and Reviewers
Mike Casey, Khuteja Farheen, Murali Kuppala, Anu Nayyar, Sergiy Pecherskyy, Kumaresh
Sankarasubbaiyan
This book was published using:
Oracle Tutor
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Disclaimer
Practices for Lesson 1: Product Orientation ............................................................................................ 1-1

Practices for Lesson 1: Overview............................................................................................................. 1-2
Business Scenario .................................................................................................................................. 1-3
Practice 1-1: Starting Services................................................................................................................. 1-4
Practice 1-2: Navigating in FDMEE .......................................................................................................... 1-6
Practices for Lesson 2: Preparing FDMEE Integrations........................................................................... 2-1
Practice 2-1: Registering a Target Application .......................................................................................... 2-3
Practice 2-2: Reviewing System and Application Settings ......................................................................... 2-5
Practices for Lesson 3: Setting Up Import Formats for File Systems...................................................... 3-1
Practice 3-1: Creating Import Formats for Fixed Files ............................................................................... 3-3
Practice 3-2: Creating Import Formats for Delimited Files ......................................................................... 3-6
Practice 3-3: Creating Import Formats for Multiple Entities........................................................................ 3-9
Practice 3-4: Creating Import Formats for Multiple Periods ....................................................................... 3-12
Practice 3-5: Adding the SKIP Function and DRCRSplit Expression ......................................................... 3-14
Practice 3-6: Adding the FILL and SKIP Expressions (Optional)................................................................ 3-17
Practice 3-7: Adding the FillL Expression and Concatenating Fields (Optional).......................................... 3-20
Practice 3-8: Adding the FACTOR Expression (Optional) ......................................................................... 3-23
Practices for Lesson 4: Completing the Integration Setup ...................................................................... 4-1
Practice 4-1: Adding Locations ................................................................................................................ 4-3
Practice 4-2: Setting Up Category and Period Mappings........................................................................... 4-5
Practice 4-3: Setting the POV .................................................................................................................. 4-7
Practices for Lesson 5: Setting Up Data Load Mappings ........................................................................ 5-1
Practice 5-1: Defining Member Mappings................................................................................................. 5-3
Practice 5-2: Exporting and Importing Mappings ...................................................................................... 5-5
Practice 5-3: Sharing Mappings ............................................................................................................... 5-9
Practices for Lesson 6: Defining and Executing Data Load Rules .......................................................... 6-1
Practice 6-1: Adding and Executing Data Load Rules ............................................................................... 6-3
Practice 6-2: Loading Data into a Range of Periods.................................................................................. 6-7
Practice 6-3: Scheduling a Data Load Rule .............................................................................................. 6-9
Practices for Lesson 7: Processing Data in Data Load Workbench ........................................................ 7-1
Practice 7-1: Loading Data ...................................................................................................................... 7-3
Practice 7-2: Loading Data into Multiple Entities ....................................................................................... 7-8
Practice 7-3: Drilling Through to FDMEE from the Target Application ........................................................ 7-10
Practice 7-4: Loading Data into Multiple Periods ...................................................................................... 7-12
Practices for Lesson 8: Setting Up Check Rules and Check Entities ...................................................... 8-1
Practice 8-1: Creating, Assigning, and Verifying Check Rules ................................................................... 8-3
Practice 8-2: Creating, Assigning, and Verifying Check Entities ................................................................ 8-8
Practices for Lesson 9: Processing Batches ........................................................................................... 9-1
Hyperion Financial Data Quality Management EE Administration Table of Contents

i
Table of Contents
Practices for Lesson 10: Reporting in FDMEE ......................................................................................... 10-1

Practices for Lesson 10: Overview ........................................................................................................... 10-2
Practice 10-1: Running Predefined Reports ............................................................................................. 10-3
Practice 10-2: Defining Reports ............................................................................................................... 10-5
Practices for Lesson 11: Setting Up Security .......................................................................................... 11-1
Practice 11-1: Defining Role-Level Security ............................................................................................. 11-3
Practice 11-2: Adding Groups for Location Security.................................................................................. 11-5
Practice 11-3: Assigning Users to Groups in Shared Services .................................................................. 11-6
Practices for Lesson 12: Defining Import Scripts .................................................................................... 12-1
Practice 12-1: Extracting Beginning Characters........................................................................................ 12-3
Practice 12-2: Splitting Characters........................................................................................................... 12-6
Practice 12-3: Skipping Lines in a Load File ............................................................................................. 12-11
Practice 12-4: Creating a Script with Temporary Variables........................................................................ 12-14
Practices for Lesson 13: Defining Mapping and Event Scripts................................................................ 13-1
Practice 13-1: Setting Up a Mapping Script .............................................................................................. 13-3
Practice 13-2: Creating an Event Script.................................................................................................... 13-6
Practices for Lesson 14: FDMEE Integration with Other Source Systems .............................................. 14-1
Practice 14-1: Integrating GL Data in FDMEE .......................................................................................... 14-3
Practice 14-2: Loading Source Data from the Open Interface Table .......................................................... 14-4
Hyperion Financial Data Quality Management EE Administration Table of Contents

ii

Practice 9-1: Creating, Executing, and Scheduling a Batch....................................................................... 9-3
Practice 9-2: Creating and Executing an Open Batch ............................................................................... 9-6
Chapter 1
Practices for Lesson 1: Product Orientation

Chapter 1 - Page 1
Practices for Lesson 1:

Product Orientation
Practices Overview
In these practices, you perform the following tasks:
Review the business scenario.
Start services.
Navigate in FDMEE.
Practices for Lesson 1: Overview

Chapter 1 - Page 2
In the classroom practices, you are an FDMEE administrator and Financial Management user
for ABC Corporation. ABC Corporation is a distributor of auto parts headquartered in the United
States, with operations in both the US and Europe. They have purchased Financial
Management to provide a more efficient close and consolidation process and FDMEE to
develop standardized financial data management processes and validate data from their source
systems.
ABC Corporation exports actual data from their general ledger systems to text files each
accounting period, and loads the files to FDMEE where the data is mapped and validated for the
target application. The data is then exported to the target application, and after accounts are
checked for accuracy, the data is consolidated.
As the FDMEE administrator, you register the source and target systems and configure system
settings. You then set up the basic integration to enable users to load source data to the target
application. Integration setup includes defining the needed import formats, locations, and period
and category mappings. You perform data load tasks to map dimension members from the
source files to your target application, define the rules for loading data, and set up the workflow
process to import, validate, and export data to the target application.
After setting up the basic integration process, you extend FDMEE functionality by defining check
rules and check entities to validate data in the target application and perform consolidations.
You automate the workflow process for end users by creating and running batches at scheduled
intervals to import and validate data. During the integration process, you create and run reports
to check data, view variances, and monitor the integration process.
As you complete the integration setup, you define security to allow users to access FDMEE.
You limit the locations and tasks for users to control access to the data.
To enhance the power and flexibility of the integration process, you create scripts to modify
actions during the workflow process. For example, you create a script to map members and to
dynamically change the import format for a location.
In addition to loading data from a file source system, ABC Corporation also loads source data
from an open interface table. As the administrator, you set up the open interface table
integration and import the data into FDMEE.

Chapter 1 - Page 3
Business Scenario
Goal
In this practice, you start the required services to enable access to Oracle EPM System
products for the course practices.
Scenario
You must start the following Oracle services before working with FDMEE:
Oracle Hyperion EPM Server Java Web Application (epmsystem1)
Oracle Hyperion Financial Management DME Listener (epmsystem1)
Oracle Hyperion Financial Management Management Service (epmsystem1)
Oracle Hyperion Financial Management Web Service Manager (epmsystem1)
Oracle Hyperion Reporting and Analysis Framework (epmsystem1)
Oracle Hyperion RMI Service (epmsystem1)
Oracle Process Manager (epmsystem1)
Oracle Process Manager (ohsInstance1144678397)
OracleOraDb11g_home1TNSListener
OracleServiceORCL
Time
15 minutes
Tasks
1.
In the HYPERION desktop folder, use the Start All Oracle Hyperion Services shortcut to
start all services.
a. In the HYPERION desktop folder, double-click Start All Oracle Hyperion Services.
b. When you are prompted to confirm, click Yes.
Note: Do not close the command prompt window.
The process takes approximately 15 minutes to complete. The following message is
displayed when the process finishes: All Oracle/Hyperion Services started. Your
environment is now ready.
c. Click OK.
d. Close the HYPERION desktop folder.
2.
Verify that all services are started.
a.
b.
On the Windows desktop, double-click Services

.
Verify that the following services are started:
Oracle Hyperion EPM Server Java Web Application (epmsystem1)
Oracle Hyperion Financial Management DME Listener (epmsystem1)
Oracle Hyperion Financial Management Management Service (epmsystem1)
Oracle Hyperion Financial Management Web Service Manager (epmsystem1)

Chapter 1 - Page 4
Practice 1-1: Starting Services
Oracle Hyperion Reporting and Analysis Framework (epmsystem1)

Oracle Hyperion RMI Service (epmsystem1)
Oracle Process Manager (epmsystem1)

Oracle Process Manager (ohsInstance1144678397)
OracleOraDb11g_home1TNSListener
OracleServiceORCL
c.
Close the Services window.

Chapter 1 - Page 5
Goal
In this practice, you navigate in FDMEE to become familiar with the user interface.
Scenario
ABC Corporation uses FDMEE to integrate source data with their Financial Management target
application. In this practice, you access FDMEE and navigate through the user interface to
become familiar with FDMEE tasks.
Time
5 minutes
Accessing FDMEE
1.
2.
In the FDMEE desktop folder, use the Workspace URL shortcut to launch EPM Workspace
and log on as user admin with password hyperion.
a. In the FDMEE desktop folder, double-click the Workspace URL shortcut.
The Log On page is displayed.
b. In User Name, enter admin, and in Password, enter the case-sensitive password
hyperion, and click Log On.
The HomePage tab is displayed.
Select Navigate, then Administer, and then Data Management.
The Data Management tab displays the Tasks pane with the Workflow and Setup tabs.
Navigating in FDMEE
1.
2.
3.
4.
5.
Click on the Setup tab.

Review the System Settings task.
a. In the Tasks pane, select System Settings under Configure.
The File system settings are displayed.
b. In the Profile Type list, select Other.
Additional system settings options are displayed.
Review the registered target application.
a. Under Register, select Target Application.
The Target Application page is displayed.
b. Select the row for the TOTCONSOL application.
The details for the Financial Management application are displayed.
Navigate to the Location task and review locations.
a. Under Integration Setup, select Location.
The Location page is displayed.
b. Select the row for the zzIndiana location.
The location details are displayed.
Click on the Workflow tab.

Chapter 1 - Page 6
Practice 1-2: Navigating in FDMEE
7.
Navigate to the Data Load Workbench task and change the column display.
a. In the Tasks pane, select Data Load Workbench under Data Load.
The Load Data page displays the workflow tasks for a location.
b. On the Load Data tab, select View, then Columns, and then Memo Items.
The Memo Items column is removed from the grid.
c. Select View, then Columns, and then Manage Columns.
The Manage Columns dialog box is displayed.
d. In the Visible Columns area, select Source-Entity and Source-ICP, and click
Remove.
e. Click OK.
The columns are removed from the grid.
Detach the grid to a new window and then close the window.
a. In the Load Data menu bar, click Detach.
The grid is detached to a new window for better visibility.
b. Click the X in the top-right corner of the window to close it.

Chapter 1 - Page 7
6.
Chapter 1 - Page 8
Chapter 2
Practices for Lesson 2: Preparing FDMEE Integrations

Chapter 2 - Page 1

Preparing FDMEE
Integrations
Practices Overview
Register a target application.
Review system settings.

Chapter 2 - Page 2
Goal
In this practice, you register the Financial Management target application, FLASH.
Scenario
As the FDMEE administrator, you must register EPM target applications so that you can load
data to them from FDMEE, and optionally, consolidate the data. The ABC Corporation uses the
Financial Management target application, FLASH.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
6 minutes
Creating the Application Root Folder

1.
In System Settings, create the application folder in D:\CF\FDMEE.

Note: Be sure to instruct FDMEE to create the folder and subfolders on the server.
a. Under Configure on the Setup tab, select System Settings.
The System Settings page is displayed.
b. In the Profile Type list, verify that File is selected.
c. In the Value column for the Application Root Folder option, enter D:\CF\FDMEE.
d. Click Create Application Folders, and then click OK at the confirmation message.
The following folder and subfolders are created on the server:
2.
Click Save to save the changes.
Registering the Target Application

1.
Register the Financial Management target application, FLASH.

a. Under Register on the Setup tab, select Target Application.
The Target Application page is displayed.
b. In the Target Application Summary area, click Add.
The Select Application dialog box is displayed.

Chapter 2 - Page 3
Practice 2-1: Registering a Target Application
2.
3.
In the Type list, select Financial Management.

Note: The list with the available Financial Management application may take a minute
to display.
d. Select the target application, FLASH, and then click OK.
The Target Application Summary area displays a blank row because the changes are
not yet saved. However, in the Application Details area, the Dimension Details tab
displays the dimensions for the target application.
The target application name is displayed in the Target Application Summary area.
In the application options, enable the Check Intersection option, and review other
application options for the FLASH application.
a. In the Target Application Summary area, verify that FLASH is selected.
b. In the Application Details area, click on the Application Options tab.
c. In the Check Intersection option value, enter or select Yes, and click Save to save the
change.
d. Review some of the other application options and their values.
For example, data load and consolidation are enabled, the default load method is
Replace, and drill region is enabled.

Chapter 2 - Page 4
c.
Goal
In this practice, you review the default FDMEE system-level profiles and application settings.
Scenario
As the FDMEE administrator, you must define the default settings for the system-level and
application-level profiles. For example, you already set the default application root folder that
defines the default folder structure for FDMEE. During later class practices, you change system
or application settings as needed, such as defining the default POV settings for end users.
Time
4 minutes
Tasks
1.
2.
In System Settings, review the system settings for each profile type.
a. Under Configure on the Setup tab, select System Settings.
b. In the Profile Type list, verify that File is selected.
c. Review the File options and settings.
d. In the Profile Type list, select POV.
At this point, there are no values selected for the POV options. After you create
periods, categories, and locations, you will update these POV settings.
e. In the Profile Type list, select ODI.
The ODI options are populated for you. Do not change these options in the class
environment.
f. In the Profile Type list, select Other.
Review the default Other options. For example, the user-interface theme is BLAF+,
the default check report is named Check Report, and the default log level is 4.
In Application Settings, review the application settings for the TOTCONSOL and FLASH
target applications.
a. Under Configure, select Application Settings.
b. In the Target Application list, select TOTCONSOL.
c. Review the application settings for the TOTCONSOL application.
For example, the application root folder for the TOTCONSOL application is
D:\CF\TOTCONSOL and the default POV is set to the zzTexas location, Jan - 2013
period, and FDMEE_ACTUAL category. The remaining option values are blank and
default to the settings defined at the system level.
d. In the Target Application list, select FLASH.
e. Review the application settings for the FLASH application.
The application option values are blank and default to the settings defined at the
system level. For example, FDMEE uses the system setting for the application root
folder (D:\CF\FDMEE) for the FLASH application.

Chapter 2 - Page 5
Practice 2-2: Reviewing System and Application Settings

Chapter 2 - Page 6
Chapter 3
Practices for Lesson 3: Setting Up Import Formats for File Systems

Chapter 3 - Page 1

Setting Up Import Formats
for File Systems
Practices Overview
Build import formats for fixed files.
Build import formats for delimited files.
Create import formats for multiple entities.
Create import formats for multiple periods.
Add the SKIP function and DRCRSplit expression.
Optional: Add the FILL and SKIP expressions.
Optional: Add the FillL expression and concatenate fields.
Optional: Add the FACTOR expression.

Chapter 3 - Page 2
Goal
In this practice, you create a fixed import format and build the mappings that define the layout of
a fixed data file.
Scenario
ABC Corporation needs to load multiple data files to the Financial Management target
application. Each file has a different layout that you must define in FDMEE import formats. With
import formats, you define the mappings between the fields in the load file and the fields in the
FDMEE staging table.
In this practice, you define the import format for the fixed data load file for the Texas location. In
the import format, you also specify values for dimension members that are not included in the
load file. For example, you specify that Department dimension members have a 00 source
value. In later practices, you add the Texas location and specify that it uses this import format to
load data.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
8 minutes
Reviewing the Data Load File

1.
Use WordPad to review the location and length of the columns in the
D:\CF\FilesLoc\Texas\Texas_GL.txt file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
b. From the D:\CF\FilesLoc\Texas folder, open the Texas_GL.txt file.
The file displays Texas data for January, 2013.
c.
2.
Review the location and length of the Account, Description, and Ending Balance
columns.
Exit WordPad.

Chapter 3 - Page 3
Practice 3-1: Creating Import Formats for Fixed Files
Adding an Import Format
2.
In FDMEE, create the NorthAmerica fixed import format with the description North
America import format. Specify that the import format is for a File source system and the
FLASH target application.
a. On the Setup tab, under Integration Setup, select Import Format.
The Import Format page is displayed.
b. In the Import Format Summary area, click Add.
A blank row is added to the grid.
c. Add an import format with the detail listed in the following table:
Detail
Value
Name
NorthAmerica
Source System
File
File Type
Fixed
Target Application
FLASH
Description
North America import format
Adding Mappings to the Import Format

1.
Build the import format mappings for the Texas_GL.txt file with the following guidelines:
Source Column
Description
Account
Account is located in the Account column of the file. It consists

of characters 1 through 15.
Amount
Amount is located in the Ending Balance column of the file.

The amount begins at character 90 and is 19 characters long.
In the Expression column, add the Sign expression to define
all amounts with a trailing CR as a credit balance.
Custom3
Custom3 is not included in the data file. In Start and Length,

enter 1. Specify an expression value of 00 for Custom3
members.
Custom4
Custom4 is not included in the data file. In Start and Length,

enter 1. Specify an expression value of 00 for Custom4
members.
Department
Department is the third set of digits in the Account column of

the file. It consists of characters 10, 11, and 12.
Entity
Entity is not included in the data file. In Start and Length, enter
1. Specify an expression value of Center for Entity members.
ICP
ICP is located in the Account column of the file in characters 1

through 15.
Prod/Sal
Product is the fourth set of digits in the Account column of the

file. It consists of characters 14 and 15.

Chapter 3 - Page 4
1.
b.
c.
d.
In Start, enter 1, and in Length, enter 15.

In the Source Column for the Amount row, enter Amount.
e.
f.
In Expression, enter Sign=,CR to add the Sign expression to define all amounts with a
trailing CR as a credit balance.
Continue to define the mappings as listed in the following table:
g.
2.
3.
Verify that the NorthAmerica import format is selected in the Import Format Summary
area.
In the NorthAmerica:Mappings area, in Source Column for the Account target
dimension, enter Account.
Source Column
Start
Length
Expression
Target
Account
15
Amount
90
19
Sign=,CR
Amount
Custom3
00
Custom3
Custom4
00
Custom4
Department
10
Entity
ICP
15
ICP
Prod/Sal
14
ProdSal
Account
Department
Center
Entity
Add an Account Description mapping to the import format. The account description is in
the Description column of the data file. It begins at character 18 and is 24 characters long.
a. In the Mappings area, click Add, and then select Description Row.
A blank row is added to the mapping grid.
b. In Source Column, enter Account Description.
c. In Start, enter 18, and in Length, enter 24.
Click Save to save your changes.

Chapter 3 - Page 5
a.
Goal
In this practice, you create a delimited import format and build the mappings that define the
layout of a delimited data file.
Scenario
ABC Corporation needs to load multiple data files to the Financial Management target
application including delimited files.
In this practice, you define the import format for a delimited data load file for the Indiana
location. In the import format, you also define all amounts in the data file with a trailing CR as a
credit balance. In a later practice, you add the Indiana location and specify that it uses this
import format to load data.
Time
7 minutes

1.
Use WordPad to review the location and delimiter of the columns in the
D:\CF\FilesLoc\Indiana\Indiana_GL.csv file.
b. From the D:\CF\FilesLoc\Indiana folder, open the Indiana_GL.csv file.
The file contains three columns delimited by a comma. The file contains Indiana data
for January, 2013.
2.
Exit WordPad.

1.
In FDMEE, create the Indiana comma-delimited import format with the description Indiana
import format. Specify that the import format is for a File source system and the FLASH
target application.

Chapter 3 - Page 6
Practice 3-2: Creating Import Formats for Delimited Files
2.
Add an import format with the detail listed in the following table:
Detail
Value
Name
Indiana
Source System
File
File Type
Delimited
File Delimiter
Comma
Target Application
FLASH
Description
Indiana import format

1.
Build the import format mappings for the Indiana_GL.csv file with the following
guidelines:
Source Column
Description
Account
Account is located in the first field (column) of the data file.
Amount
Amount is located in the last field of the data file. In the

Expression column, add the Sign expression to define all
amounts with a trailing CR as a credit balance.
Entity
Entity is not included in the data file. In Field Number, enter 1.

Specify an expression value of Center for Entity members.
ICP
ICP is located in the first field of the data file.
a.
b.
c.
Select the Indiana import format in the Import Format Summary area.
In Source Column for the Account target dimension, enter Account.
In Field Number, enter 1.
d.
e.

f.
g.
h.
In the Source Column for the Entity row, enter Entity.
In Field Number, enter 1 and enter the Expression value, Center.
i.
In the Source Column for the ICP row, enter ICP.
j.

Chapter 3 - Page 7
c.
Compare the Indiana import format mappings to the rows listed in the following table:
Source Column
Field Number
Account
Amount
Expression
Target
Account
Sign=,CR
Amount
Custom3
Custom4
Department
Entity
ICP
Center
Entity
ICP
ProdSal
2.
3.
the second column of the data file.
c. In Field Number, enter 2.

Chapter 3 - Page 8
k.
Goal
In this practice, you create a fixed import format and build the mappings that define the layout of
a data file. The file contains data for multiple entities.
Scenario
Some of the data load files contain data for multiple entities in one file. In the import format, you
map the location of the Entity dimension values to correctly import them into the FDMEE staging
tables. In this practice, you define the import format for the fixed data load file for the Ohio
location. In later practices, you add the Ohio location, specify that it uses this import format to
load data, and map each source entity to its corresponding entity in the target application.
Time
6 minutes

1.
D:\CF\FilesLoc\Ohio\Ohio_MultiEnt.txt file.
b. From the D:\CF\FilesLoc\Ohio folder, open the Ohio_MultiEnt.txt file.
The file displays data for Ohio locations for January, 2013.
c.
d.
2.
Scroll through the file to see the different entities displayed in the Entity column.
Review the location and length of the Entity, Account, Description, and Ending Balance
columns.
Exit WordPad.

1.
In FDMEE, create the OhioMulti fixed import format with the description Ohio Multiple
Entity import format. Specify that the import format is for a File source system and the
FLASH target application.

Chapter 3 - Page 9
Practice 3-3: Creating Import Formats for Multiple Entities
2.
Detail
Value
Name
OhioMulti
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Ohio Multiple Entity import format

1.
Build the import format mappings for the Ohio_MultiEnt.txt file with the following
guidelines:
a.
Source Column
Description
Account
Account is located in the Account column of the file. It begins

in character 19 and is 15 characters long.
Amount

In the Expression column, add the Sign expression to define
all amounts with a trailing CR as a credit balance.
Department
Department is the third set of digits in the Account column of

the file. It consists of characters 18, 19, and 20.
Entity
Entity is located in the Entity column of the file. It begins in

character 1 and is 5 characters long.
ICP
ICP is located in the Account column of the file. It begins in

Prod/Sal
Product is the fourth set of digits in the Account column of the

file. It consists of characters 22 and 23.
b.
c.
In the Import Format Summary area, verify that the OhioMulti import format is
selected.
d.
e.

f.

Chapter 3 - Page 10
c.

Source Column
Start
Length
Account
15
Amount
55
19
Expression
Target
Account
Sign=,CR
Amount
Custom3
Custom4
2.
3.
Department
18
Department
Entity
Entity
ICP
15
ICP
Prod/Sal
22
ProdSal

Chapter 3 - Page 11
g.
Goal
In this practice, you review a multi-period Excel template and create an import format for loading
the file.
Scenario
ABC Corporation also has Excel data load files that load budget data to multiple time periods.
You must set up the Excel files in the correct format before you can load them into FDMEE. To
help with this task, FDMEE offers an Excel template that you can use as a guideline.
In this practice, you review an Excel template that includes budget data for multiple periods for
the Texas location. The template uses FDMEE metadata tags to define the dimensions and
periods that are included in the load file. After reviewing the load file, you set up the multi-period
import format for the load file. In later practices, you define a multi-period data load rule for the
Texas location and import the data.
Time
4 minutes
Reviewing the Excel Template

1.
Use Excel to review the layout of the D:\CF\FilesLoc\Texas\TX_TrialBalance.xls

file.
a. In the FDMEE folder on the Windows desktop, launch Microsoft Office Excel 2007.
b. From the D:\CF\FilesLoc\Texas folder, open the TX_TrialBalance.xls file.
The file was created for you from a download of the Excel template. Budget data rows
and metadata tags were added to the template for January through December. A
portion of the file is displayed in the following graphic.
c.
2.
Review row 6 of the file. The row contains metadata tags that define the dimensions
and periods for the data load. In the first three columns, the metadata tags (A, C, and
D) refer to the Account, Center (Entity), and Account Description values. Starting in
column D, the periods are defined. For example, V1:2013/1/31 refers to the Jan - 2013
period, and V2:2013/2/28 refers to the Feb - 2013 period.
Exit Excel.

Chapter 3 - Page 12
Practice 3-4: Creating Import Formats for Multiple Periods
Creating a Multi-Period Import Format

In FDMEE, create an import format, MultiPeriod, to load multi-period data from the Excel
file to the FLASH target application.
b. Under Import Format Summary, click Add.
c. In the Details area, in Name, enter MultiPeriod.
d.
e.
f.
2.
In the Source System list, select File.

In the File Type list, select Multi-Period.
In the File Delimiter list, accept the default, Comma. This field is ignored in MultiPeriod import formats.
g. In the Target Application list, select FLASH.
h. In Description, enter Import format for multi-period Excel template.
Note: You do not define mappings for this multi-period import format.

Chapter 3 - Page 13
1.
Goal
In this practice, you create a fixed import format and build the mappings that define the format of
a data file. You skip the summary rows in the data file, and you add the DRCRSplit expression
to handle the split debit and credit columns.
Scenario
FDMEE automatically skips rows in source data files that have spaces and non-numeric
characters in the amount field. However, some of the data load files for the ABC Corporation
also include other lines that you do not want to import into FDMEE. Usually, these lines are
report headers, totals, and subtotals that can lead to inaccurate data in target applications. They
can also be lines that include non-amount data, such as a date, in the same location as the
amount field.
In this practice, you define the import format for a fixed data load file for the Nevada location. In
the import format, you specify that certain lines must be skipped during the import process. You
also handle the split of debit and credit amount data. In later practices, you add the Nevada
location and specify that it uses this import format to load data.
Time
5 minutes

1.
D:\CF\FilesLoc\Nevada\Nevada.txt file.
b. From the D:\CF\FilesLoc\Nevada folder, open the Nevada.txt file.
The file displays Nevada data for January, 2013.
c.
2.
Review the location and length of the Account Number, Description, Debit, and Credit
columns.
Exit WordPad.

Chapter 3 - Page 14
Practice 3-5: Adding the SKIP Function and DRCRSplit Expression
2.
In FDMEE, create the Nevada fixed import format with the description Nevada import
format. Specify that the import format is for a File source system and the FLASH target
application.
Detail
Value
Name
Nevada
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Nevada import format

1.
Build the import format mappings for the Nevada.txt file with the following guidelines:
Source Column
Description
Account
Account is located in the Account Number column of the file. It

begins at character 1 and is 11 characters long.
Amount
Amount is located in the Debit and Credit columns of the file.

The columns begin at character 46 and are 31 characters
long. In the Expression column, add the DRCRSplit
expression to handle the split debit and credit columns.
Entity
1. Specify an expression value of Nevada for Entity members.
a.
b.
In the Import Format Summary area, verify that the Nevada import format is selected.
c.
d.

In Expression, enter DRCRSplit=16 to add the DRCRSplit expression to handle the
split debit and credit columns.

Chapter 3 - Page 15
1.

Source Column
Start
Length
Account
11
Amount
46
31
Expression
Target
Account
DRCRSplit=16
Amount
Custom3
Custom4
Department
Entity
Nevada
Entity
ICP
ProdSal
2.
3.
Add a mapping to the import format to skip any row that has a : (colon) at character 43.
a. In the Mappings area, click Add, and then select Skip Row.
b. In Source Column, enter Skip.
c.
4.
d. In Expression, enter a : (colon).


Chapter 3 - Page 16
e.
Goal
In this practice, you create a fixed import format and build the mappings that define the format of
a data file. You skip rows in the data file, add trailing fill characters, and convert Euro number
formats to the US number format.
Scenario
Some of your data load files contain source members of varying length. In cases where you
want to ensure that all imported members of a field are the same length, you can use the Fill
expression to pad the field with trailing characters. For example, the load file contains some
accounts that are 7 characters long and others that are 10 characters long. Using a Fill
expression, FDMEE evaluates the source field text value. If it is shorter than the Fill expression,
the text value is padded with the Fill characters.
In this practice, you define the import format for the fixed data load file for the UK location. In the
import format, you add a Fill expression for the Account dimension to ensure that all accounts
are the same length. You also add the Fill=EuroToUS expression to the Amount field to convert
amounts to a U.S. format, with the comma as the thousands separator and the period as the
decimal point. In later practices, you add the UK location and specify that it uses this import
format to load data.
Time
5 minutes

1.
D:\CF\FilesLoc\UK\UK_TrialBal.txt file.
b. From the D:\CF\FilesLoc\UK folder, open the UK_TrialBal.txt file.
The file displays UK data for January, 2013.
c.
2.
Review the location and length of the Account, Description, and Ending Balance
columns.
Exit WordPad.

Chapter 3 - Page 17
Practice 3-6: Adding the FILL and SKIP Expressions (Optional)
2.
In FDMEE, create the UK fixed import format with the description UK Fill and Skip.
Specify that the import format is for a File source system and the FLASH target application.
Detail
Value
Name
UK
Source System
File
File Type
Fixed
Target Application
FLASH
Description
UK Fill and Skip

1.
Build the import format mappings for the UK_TrialBal.txt file with the following
guidelines:
Source Column
Description
Account
Account is located in the Account column of the file. The

account begins at character 3 and is 10 characters long. In the
Expression value, add a Fill expression of ten zeroes.
Amount

The amount begins at character 112 and is 15 characters
long. In the Expression value, add the Fill=EuroToUS
expression to convert Euro number formats to the US number
format.
Entity
1. Specify an expression value of UK for Entity members.
a.
b.
c.
In the Import Format Summary area, verify that the UK import format is selected.
d.

Source Column
Start
Length
Expression
Target
Account
10
Fill=0000000000 Account
Amount
112
15
Fill=EuroToUS
Amount
Custom3
Custom4

Chapter 3 - Page 18
1.
Department
1
UK
Entity
ICP
ProdSal
2.
3.
4.
Add a mapping to the import format to skip any row that has Page: starting at character
107.
d. In Expression, enter Page:.

Chapter 3 - Page 19
Entity
Goal
In this practice, you create a fixed import format and build the mappings to define the format of a
data file. You concatenate three fields to define the account field and you also pad Entity
members with leading characters.
Scenario
Some of your data load files contain source members of varying length. In cases where you
want to ensure that all imported members of a field are the same length, you can use the FillL
expression to pad the field with leading characters. For example, the load file contains source
entities that are 1 or 2 characters long. Using a FillL expression, FDMEE evaluates the source
field text value; if it is shorter than the FillL expression, the text value is padded with leading
characters.
Data load files can also contain multiple fields that you want to concatenate into one field in the
FDMEE staging table. The concatenation order is based on the order of the lines in the import
format.
In this practice, you define the import format for the fixed data load file for the Illinois location. In
the import format, you concatenate two fields from the source file into the Account field in the
FDMEE staging table. You also add a FillL expression for the Entity dimension to ensure that all
entities are the same length. In later practices, you add the Illinois location and specify that it
uses this import format to load data.
Time
7 minutes

1.
D:\CF\FilesLoc\Illinois\Illinios.txt file.
b. From the D:\CF\FilesLoc\Illinois folder, open the Illinois.txt file.
The file displays Illinois data for January, 2013.
c.
2.
Review the location and length of the Account Number, Description, and Debits and
Credits columns.
Exit WordPad.

Chapter 3 - Page 20
Practice 3-7: Adding the FillL Expression and Concatenating Fields

(Optional)
2.
In FDMEE, create the Illinois fixed import format with the description Illinois FillL and
concatenate. Specify that the import format is for a File source system and the FLASH
target application.
Detail
Value
Name
Illinois
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Illinois FillL and concatenate

1.
Build the import format mappings for the Illinois.txt file with the following guidelines:
a.
b.
c.
Source Column
Description
Account
The account comprises multiple fields from the Account

Number column in the file. Define the first part of the account
as the last four digits of the account number in the file. The
first part of the account begins at character 7.
Account
The second part of the account is a hyphen. In Start and

Length, enter 1. Specify that the expression value is a (hyphen).
Account
The last part of the account is the middle two digits of the
account number in the file. The last part of the account begins
at character 4.
Amount
Amount is located in the Debit and Credit columns of the file.

In the Expression column, add the DRCRSplit=15 expression
to import debits and credits correctly.
Entity
Entity is located in the first two digits of the Account Number

column of the file. Some accounts are only one character
long. Add the leading fill expression to fill two missing
characters with zeroes.
In the Import Format Summary area, verify that the Illinois import format is selected.

Chapter 3 - Page 21
1.
e.
f.
g.
h.
Add another Account row to the import format. Click Add, select Dimension Row, and
then select Account.
In Source Column, enter Account.
In Expression, enter - (hyphen).
Note: The Account rows will display in the order that you entered them after you save
the import format.
Source Column
Start
Length
Account
Account
Account
Amount
44
29
Expression
Target
Account
DRCRSplit=15
Amount
Custom3
Custom4
Department
Entity
FillL=00
Entity
ICP
ProdSal
2.
3.
4.
Add a mapping row to skip any row that has a : (colon) starting at character 42.
d. In Expression, enter :(a colon).

Chapter 3 - Page 22
d.
Goal
In this practice, you create a delimited import format and build the mappings to define the format
of a data file. You divide the amounts by 1000 by using the Factor expression.
Scenario
In some cases, you want to multiply source amounts during the data-load process. For example,
amounts in a load file are scaled to thousands and you want to multiply the values by 1000 as
you import the data to the FDMEE staging table. In other cases, you want to increase or
decrease budget data as you load it into FDMEE.
In this practice, you define the import format for the delimited data load file for the California
location. In the import format, you add a Factor expression to multiply source amounts by a
decimal to correct the scaling of values. In later practices, you add the California location and
specify that it uses this import format to load data.
Time
5 minutes

1.
Use WordPad to review the location and delimiter of the columns in the
D:\CF\FilesLoc\California\California.dat file.
b. From the D:\CF\FilesLoc\California folder, open the California.dat file.
The file contains three columns delimited by a comma. The columns contain the entity,
account, and amount values for California for January, 2013.
2.
Exit WordPad.

1.
In FDMEE, create the California delimited import format with the description California Factor. Specify that the import format is for a File source system and the FLASH target
application.

Chapter 3 - Page 23
Practice 3-8: Adding the FACTOR Expression (Optional)
2.
Detail
Value
Name
California
Source System
File
File Type
Delimited
File Delimiter
Comma
Target Application
FLASH
Description
California - Factor

1.
Build the import format mappings for the California.dat file with the following
guidelines:
Source Column
Description
Account
Account is located in the second field (column) of the data file.
Amount
Amount is located in the third field of the data file.
Entity
Entity is located in the first field in the data file.
a.
b.
In the Import Format Summary area, select the California import format.
c.
d.

Source Column
Field Number
Account
Amount
Expression
Target
Account
Factor=.001
Amount
Custom3
Custom4
Department
Entity
Entity
ICP
ProdSal
2.

Chapter 3 - Page 24
c.
Chapter 4
Practices for Lesson 4: Completing the Integration Setup

Chapter 4 - Page 1

Completing the Integration
Setup
Practices Overview
Add locations.
Set up category and period mappings.
Set the POV.

Chapter 4 - Page 2
Goal
In this practice, you add FDMEE locations and specify their import formats.
Scenario
You set up locations to load your source data to your target application, FLASH. These
locations are associated with the File source system, and you import data from multiple data
files from that source system to the locations. The locations are also associated with target
entities, to which you load the data.
In this practice you set up the locations where you want to load the source data files with the
import formats that you created in the practices from the previous lesson. When you create a
location, you assign an import format to it. In later practices, you define data load mappings and
data load rules for the location before you import the source data. You will also define user
access to locations in later practices.
Time
10 minutes
Tasks
1.
Add the Texas location and specify the NorthAmerica import format.
a. On the Setup tab, select Location.
b. In the Location area, click Add.
c. Under Details, in Name, enter Texas.
d.
2.
In the Import Format list, click Search

.
The Search and Select: Import Format dialog box is displayed.
e. Select NorthAmerica, and click OK.
NorthAmerica is displayed as the selected import format, and the FLASH target
application is displayed as the target application for the location.
f. Click Save to save the changes.
Repeat step 1 to add the locations in the following table with their corresponding import
format:
Location Name
Import Format
Indiana
Indiana
Nevada
Nevada
Ohio
OhioMulti

Chapter 4 - Page 3
Practice 4-1: Adding Locations
Optional: If you completed any of the optional practices from the previous lesson, then
repeat step 1 to create the corresponding locations listed in the following table:
Location Name
Import Format
California
California
Illinois
Illinois
UK
UK
Note: The UK import format is from practice 3.6. The Illinois import format is from practice
3.7. The California import format is from practice 3.8.
3.

Chapter 4 - Page 4
Goal
In this practice, you add category and period mappings to FDMEE.
Scenario
You set up categories and periods in FDMEE to map them to their corresponding members in
the target application. These categories and periods define the members to which you can load
data for the target application.
In this practice you set up the global mappings for the categories and periods to which you want
to load source data. Many of the periods are already defined for you to save time. The global
mappings apply to all target applications. In later practices, you define your POV by selecting a
category and period that you defined in these mapping tables.
Time
5 minutes
Setting Up a Category Mapping

1.
2.
Add the FDMEE_PLAN category with a description of Plan data. Select a monthly
frequency and enter the target category, PlanLID.
a. On the Setup tab, under Integration Setup, select Category Mapping.
The Global Mapping tab of the Category Mapping page is displayed. The
FDMEE_ACTUAL and FDMEE_BUDGET categories are defined with a monthly
frequency. The categories are mapped to the Actual and Plan target categories.
b. On the Global Mapping tab, click Add.
A blank row is added to the grid. FDMEE assigns a category key to the row.
c. In Category, enter FDMEE_PLAN.
d. In Description, enter Plan data.
e. In the Frequency list, select Monthly.
f. In Target Category, enter PlanLID.
Setting Up Period Mappings

1.
Add the 2/28/2014 period key with a prior period key of 1/31/2014 and a period name of
Feb - 2014. Map the period to the target period month, February, for the year target, 2014.
a. On the Setup tab, select Period Mapping.
The Global Mapping tab of the Period Mapping page is displayed. The periods for 2012
and 2013 are defined for you. The first period of 2014 is also defined.
b. On the Global Mapping tab, click Add.
c. In Period Key, enter or select 2/28/2014.
d.
In Prior Period Key, enter or select 1/31/2014.
e.
f.
In Period Name, enter Feb - 2014.

In Target Period Month, enter February.

Chapter 4 - Page 5
Practice 4-2: Setting Up Category and Period Mappings
Period Key
Prior Period
Key
Period Name
Target Period
Month
Year Target
3/31/2014
2/28/2014
Mar - 2014
March
2014
4/30/2014
3/31/2014
Apr - 2014
April
2014
2.
g. In Year Target, enter 2014.

h. Click Save to save the changes.
Repeat step 1 to add the periods listed in the following table:

Chapter 4 - Page 6
Goal
In this practice, you define the default system POV for users.
Scenario
Administrators can control the period and category POV for all users by setting the POV in the
system-level options. The POV sets the location, period, and category on which you want to
focus. Most of the tasks that users perform on the Workflow tab affect data for the current
location set in the POV. Administrators can also lock the POV mode to ensure that end users
load data only to the proper period and category.
In this practice, you set the default POV for users in the system settings. In later practices, you
select your POV settings before loading source data, and you also define the default POV for a
specific user or application. The user options take precedence over application options, and
application options take precedence over system options.
Time
5 minutes
Tasks
1.
2.
Navigate to the POV profile type on the System Settings page.

a. On the Setup tab, under Configure, select System Settings.
The System Settings tab displays the File profile type.
b. In the Profile Type list, select POV.
The POV options are displayed.
Set the default POV to the Texas location, Jan - 2013 period, and the FDMEE_ACTUAL
category.
a.
b.
c.
d.
e.
For the Default POV Location option, click Select

.
The Search and Select: Default POV Location dialog box is displayed.
Select Texas, and click OK.
Repeat steps 2a and 2b for the Default POV Period option to select the Jan - 2013
period.
Repeat steps 2a and 2b for the Default POV Category option to select the
FDMEE_ACTUAL category.

Chapter 4 - Page 7
Practice 4-3: Setting the POV

Chapter 4 - Page 8
Chapter 5
Practices for Lesson 5: Setting Up Data Load Mappings

Chapter 5 - Page 1

Setting Up Data Load
Mappings
Practices Overview
Define member mappings.
Export and import mappings.
Share mappings.

Chapter 5 - Page 2
Goal
In this practice, you define Explicit, Between, and Like mappings for the Account dimension in
the Indiana location.
Scenario
You must create data load mappings in FDMEE to map your source dimension members to
their corresponding target application dimension members. For each location, you define a set
of mappings for each target application dimension, such as Financial Management and
Planning.
In this practice, you manually define mappings for the Indiana location. In later practices, you
import mappings for one and multiple dimensions to locations.
Time
5 minutes
Tasks
1.
On the Data Load Mapping page, set the POV to the Indiana location.
a. On the Workflow tab, under Data Load, select Data Load Mapping.
The Data Load Mapping page is displayed.
b. In the POV bar at the bottom of the page, click the location name.
The Select Point of View dialog box is displayed.
c. In Location, enter Indiana, and click OK.
2.
In the Dimensions list, select Account.

There are no mappings for the Account dimension.
Add an Explicit mapping to map source account 1100 to the target account 10000005 with
the description Cash Account 1.
a. Click on the Explicit tab.
b. Click Add.
c. In Source Value, enter 1100.
3.
d.
4.
5.
In Target Value, click Select

.
The Search and Select: Target Value dialog box is displayed.
e. Select 10000005, and click OK.
f. In Description, enter Cash Account 1.
g. Click Save to save the changes.
Repeat step 3 to map source account 1100-102 to the target account 10000010 with the
description Cash Account 2.
Add a Between mapping to map source accounts 2760 through 2767 to target account
29000010 with the rule name W2760B. Change the sign of the account.
a. Click on the Between tab.
b. Click Add.

Chapter 5 - Page 3
Practice 5-1: Defining Member Mappings
c.
In Source Value, enter 2760,2767.
6.
7.

.
e. Select 29000010, and click OK.
f. Select the Change Sign check box.
g. In Rule Name, enter W2760B.
Repeat step 5 to map source accounts 4320 through 4325 to target account 60000 with the
rule name W4320B. Do not change the sign of the account.
Add a Like mapping to map all source accounts that begin with 2422 to target account
24000055 with the rule name W2422L. Change the sign of the account.
a. Click on the Like tab.
b. Click Add.
c. In Source Value, enter 2422*.
d.
e.
f.
g.
h.

.
Select 24000055, and click OK.
Select the Change Sign check box.
In Rule Name, enter W2422L.

Chapter 5 - Page 4
d.
Goal
In this practice, you export Account mappings to a file to review the layout of the file. After
reviewing a mapping load file, you import Department dimension mappings into the Indiana
location and correct a mapping error. You then import mappings for all dimensions to the
Indiana location.
Scenario
You can build data load mappings externally and import them to FDMEE to more easily and
quickly load the dimension mappings for locations. As a starting point, you can manually enter a
few mappings and then export them to a file to review the layout of a mapping file. You can then
build the mapping load files and import them to multiple locations.
In this practice, you set up the member mappings for the Indiana location.
Time
15 minutes
Exporting Mappings
1.
2.
On the Data Load Mapping page, set the POV to the Indiana location.
b. In the POV bar at the bottom of the page, click the location name.
c. In Location, enter Indiana, and click OK.
Export the Account member mappings to the IN_Acct_map.txt file.
a.
b.
c.
3.
4.
In the Dimensions list, select Account.

Click on the All Mappings tab.
Select Export and then Current Dimension.
The Specify file location dialog box is displayed.
d. Expand FDMEE, then inbox, and then select the Indiana folder.
e. In File Name, enter IN_Acct_map.txt, and click OK.
f. At the information message, click OK.
g. Click Cancel to return to the Data Load Mapping page.
In the FDMEE folder on the Windows desktop, launch WordPad.
Open and review the D:\CF\FDMEE\inbox\Indiana\IN_Acct_map.txt file.
The file includes the account mappings that you created in the previous practice.
Note: Do not exit WordPad.

Chapter 5 - Page 5
Practice 5-2: Exporting and Importing Mappings
Importing Mappings for One Dimension

In WordPad, review the mappings load file,
D:\CF\FilesLoc\Indiana\IN_Dept_map.txt.
a.
2.
3.
4.
In WordPad, navigate to the D:\CF\FilesLoc\Indiana folder, and open the

IN_Dept_map.txt file.
b. Review the contents of the file. The file includes Like and Explicit mappings for the
Department dimension.
c. Exit WordPad.
In FDMEE, import the mappings for the Department dimension from the
D:\CF\FilesLoc\Indiana\IN_Dept_map.txt file. During the import, replace and
validate the mappings.
a. In Data Load Mapping, select the Department dimension in the Dimensions list.
b. Click on the All Mappings tab.
c. Click Import, and then select Current Dimension.
The Select a file to import dialog box is displayed.
d. Expand FDMEE and then inbox, and select the Indiana folder.
e. Click Upload.
The Select a file to upload dialog box is displayed.
f. Click Browse, navigate to the D:\CF\FilesLoc\Indiana folder, select the
IN_Dept_map.txt file, click Open, and then OK.
The file name is displayed in the File area.
g. Select the IN_Dept_map.txt file, and click OK to load the member mappings.
The Select import mode and validation dialog box is displayed.
h. Select Replace and Validate, and click OK.
The Mapping File Import Confirmation dialog box displays the following message:
Import failed for 1 rows. Please click the button to see the failed rows.
i. Click Show failed rows.
The Member mapping Import Validation Errors dialog box displays one failed row.
The target value, Marketig, is an invalid target member. You should correct the
mapping file and import it again.
j. Click OK.
In WordPad, open the D:\CF\FDMEE\inbox\Indiana\IN_Dept_map.txt file and
change the target value, Marketig, to Marketing, and save the changes.
b. Select File, then Open, then navigate to the D:\CF\FDMEE\inbox\Indiana folder,
and open the IN_Dept_map.txt file.
c. In the row for source member 112, change Marketig to Marketing.
d. Save the file and exit WordPad.
In FDMEE, import the mappings for the Department dimension from the updated
D:\CF\FDMEE\inbox\Indiana\IN_Dept_map.txt file. During the import, replace and
validate the mappings.
a. On the Data Load Mapping page for the Indiana location, select Department in the
Dimensions list.
b. Click Import, and then select Current Dimension.

Chapter 5 - Page 6
1.
f.
Expand FDMEE and then inbox, and select the Indiana folder.
Select the IN_Dept_map.txt file, and click OK to load the member mappings.
Select Replace and Validate, and click OK.
The Mapping File Import Confirmation dialog box displays the following message:
File imported successfully.
Click OK.
The imported Department mappings are displayed on the All Mappings tab.
Importing Mappings for All Dimensions

1.
Use WordPad to review the mappings load file,

D:\CF\FilesLoc\Indiana\IN_All_Maps.txt.
b. Navigate to the D:\CF\FilesLoc\Indiana folder, and open the
IN_All_Maps.txt file.
c.
2.
3.
Review the contents of the file. The file includes mappings for all of the dimensions,
such as Account, Entity, and Department. The file includes Explicit, Between, and Like
mappings.
d. Exit WordPad.
In FDMEE, import the mappings for all dimensions from the
D:\CF\FilesLoc\Indiana\IN_All_Maps.txt file to the Indiana location. During the
import, merge and do not validate the mappings.
a. On the All Mappings tab in Data Load Mapping, click Import, and then select All
Dimensions.
The Select a file to import dialog box is displayed.
b. Expand FDMEE and then inbox, and select the Indiana folder.
c. Click Upload.
d. Click Browse, navigate to the D:\CF\FilesLoc\Indiana folder, select the
IN_All_Maps.txt file, click Open, and then OK.
e. Select the IN_All_Maps.txt file, and click OK to load the member mappings.
The Select import mode and validation dialog box is displayed.
f. Select Merge and No Validate, and click OK.
g. At the confirmation message, click OK.
Review the mappings for some of the dimensions.
a. In the Dimensions list, select ProdSal and review the Like and Explicit mappings.
b. In the Dimensions list, select Account and review the Explicit, Between, and Like
mappings.
c. In the Dimensions list, select Department and review the Like and Explicit mappings.
d. In the Dimensions list, select Entity and review the Explicit mapping.
e. Continue reviewing the mappings by selecting the Custom3, Custom4, and ICP
dimensions in the Dimensions list.

Chapter 5 - Page 7
c.
d.
e.
5.
6.
Change the POV location to Texas.

a. In the POV bar, click Indiana.
b. In Location, enter or select Texas, and click OK.
Repeat step 2 to import the mappings for all dimensions to the Texas location from the
D:\CF\FilesLoc\Texas\All_Maps.txt file. Upload the file to the
D:\CF\FDMEE\inbox\Texas folder. Merge the mappings and do not validate them.
Repeat step 3 to review the mappings for all dimensions in the Texas location.
The Entity mappings include mappings for additional locations other than Texas. You will
share the Texas mappings with other locations that also require an Entity mapping.
4.

Chapter 5 - Page 8
Goal
In this practice, you specify that the Ohio location shares the same member mappings as the
Texas location.
Scenario
Locations often load data for the same accounts and other dimension members. The member
mappings that you set up for the Texas location might be the same mappings that you need for
other locations. Instead of importing the same mappings for multiple locations, you can specify
that locations share the same mappings as another location, which is considered the parent
location.
Time
5 minutes
Tasks
1.
2.
3.
4.
Navigate to the Ohio location on the Location page.

a. On the Setup tab, under Integration Setup, select Location.
b. In the Location area, select Ohio.
The Details area displays the Ohio location details.
Select the Texas parent location for Ohio.
a. Under Details, in Parent Location, enter or select Texas.
b. Click Save to save the changes.
On the Data Load Mapping page, review the data load mappings for the Ohio location.
b. In the POV bar, click the location name.
c. In Location, enter or select Ohio, and click OK.
Review the data load mappings for the Ohio location.
a. In the Dimensions list, select ProdSal and review the Like and Explicit mappings.
b. In the Dimensions list, select Account and review the Explicit, Between, and Like
mappings.
c. Optional: Continue reviewing the mappings by selecting the Entity, Custom3,
Custom4, and ICP dimensions.
Note: The data load mappings are the same as the mappings for the Texas location.

Chapter 5 - Page 9
Practice 5-3: Sharing Mappings

Chapter 5 - Page 10
Chapter 6
Practices for Lesson 6: Defining and Executing Data Load Rules

Chapter 6 - Page 1

Defining and Executing Data
Load Rules
Practices Overview
Add and execute data load rules.
Load data to a range of periods.
Schedule a data load rule.

Chapter 6 - Page 2
Goal
In this practice, you add a data load rule for the Indiana and Nevada locations and import data
into the locations.
Scenario
After setting up import formats, locations, and member mappings, you must define data load
rules. With data load rules, you define the source file(s) that you want to import into your
locations for a specific category. You can also indicate to which periods to process the data and
what Workflow tasks you want to execute.
In this practice, you create and run a data load rule to import source data into the Indiana and
Nevada locations. After importing the data, you check the status of the process and review the
imported data in Data Load Workbench. In later practices, you import data into multiple periods
and also schedule a data load rule to run at a later time.
Time
9 minutes
Importing Data into the Indiana Location

1.
2.
On the Data Load Rule page, set the POV to the Indiana location, Jan - 2013 period, and
a. On the Workflow tab, under Data Load, select Data Load Rule.
The Data Load Rule page is displayed.
c. In Location, enter or select Indiana.
d. In Period, enter or select Jan - 2013.
e. In Category, enter or select FDMEE_ACTUAL, and click OK.
Add a data load rule named IN_Actual to load the Indiana_GL.csv file. You can upload
the file from the D:\CF\FilesLoc\Indiana folder to the FDMEE\inbox\Indiana
folder.
a. Under Data Rule Summary, click Add.
b. In the Details area, enter IN_Actual in Name.
c.
d.
e.
f.
g.
h.
In Description, enter Indiana actual data load rule.

In the Category list, select FDMEE_ACTUAL.
In File Name, click Select.
Expand FDMEE, then inbox, and select Indiana.
Click Upload.
Click Browse, navigate to the D:\CF\FilesLoc\Indiana folder, select the
Indiana_GL.csv file, click Open, and then OK.

Chapter 6 - Page 3
Practice 6-1: Adding and Executing Data Load Rules
4.
5.
Importing Data into the Nevada Location

1.
On the Data Load Rule page, set the POV to the Nevada location, Jan - 2013 period, and
c. In Location, enter or select Nevada.
d.
Verify that the Jan - 2013 period and FDMEE_ACTUAL category are selected, and
click OK.

Chapter 6 - Page 4
3.
i. Select the Indiana_GL.csv file, and click OK.

j. Click Save to save the data load rule.
Run the IN_Actual data load rule to import data into January 2013 in Replace mode for
the Indiana location.
a. Under Data Rule Summary, verify that the IN_Actual data load rule is selected.
b. Click Execute.
The Execute Rule dialog box is displayed.
c. Select Import from Source.
d. In Start Period and End Period, select Jan - 2013.
e. In the Import Mode list, select Replace.
f. Click Run.
The following message is displayed: A process has been submitted for extraction.
followed by the process ID.
g. Click OK.
Review the process details and the log file for the data load import.
a. On the Workflow tab, under Monitor, select Process Details.
b. Click Refresh to update the status. Repeat this step until the rule runs and a success
status is displayed.
c. If needed, under Process Details, select the process ID.
d. In the Process Step area, review the status of each process step.
The status displays a green check mark to indicate a successful step.
e. Under Process Details, for your process ID, click Show in the Log column.
A prompt is displayed at the bottom of the page.
f. Click Open to display the log file in Notepad.
g. Review the log file and then close Notepad.
View the data in Data Load Workbench.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
The imported data for the Indiana location is displayed. The Import and Validate tasks
at the top of the page display a gold fish to indicate that the tasks were successful.
b. Scroll to the right to review all of the source and target dimension columns and the
amount imported in each row.
Add a data load rule named NV_Actual to load the Nevada.txt file. You can upload the
file from the D:\CF\FilesLoc\Nevada folder to the FDMEE\inbox\Nevada folder.
b. In the Details area, enter NV_Actual in Name.
c. In Description, enter Nevada actual data load rule.
d.
e.
f.
g.
h.
3.
4.

Expand FDMEE, then inbox, and select Nevada.
Click Upload.
Click Browse, navigate to the D:\CF\FilesLoc\Nevada folder, select the
Nevada.txt file, click Open, and then OK.

i. Select the Nevada.txt file, and click OK.
Run the NV_Actual data load rule to import data into January 2013 in Replace mode for
the Nevada location.
a. Under Data Rule Summary, verify that the NV_Actual data load rule is selected.
b. Click Execute.
d. In Start Period and End Period, select Jan - 2013.
f. Click Run.
g. Click OK.
Review the process details and the log file for the data load import.
b. Click Refresh to update the status. Repeat this step until the rule runs and the status is
updated.
c. If needed, under Process Details, select the process ID for the Nevada location.
The status symbol indicates that the process did not complete successfully.
d. For the process ID, click Show in the Log columns, and, at the bottom of the page,
click Open to open the log file.
e. Review the log file. For example, you can search for the word error to check for
errors.
The log file includes an error that indicates that data rows with unmapped dimensions
exist for the selected period.
f. Close Notepad.

Chapter 6 - Page 5
2.

The imported data for the Nevada location is displayed. The Import task displays a gold
fish to indicate success, however, the Validate task displays a grey fish to indicate that
the validation was not successful. The validation failed because there are no member
mappings defined for the Nevada location.
Note: In the practices for the next lesson, you perform tasks to correct validation
errors.
b. Scroll to the right to review all of the source dimension columns and the amount
imported in each row.
5.

Chapter 6 - Page 6
Goal
In this practice you load data into multiple periods in the Indiana location.
Scenario
You can define a data load rule to load source data into a range of periods. For example, you
can load the same source file to multiple periods for testing purposes or you can load data from
multiple files to a range of periods.
In this practice, you load data from multiple files to a range of periods in the Indiana location.
Time
8 minutes
Tasks
1.
2.
Review and copy the IN_GL02-28-2013.csv, IN_GL03-31-2013.csv, and IN_GL04-302013.csv files from the D:\CF\FilesLoc\Indiana folder to the D:\CF\FDMEE\inbox\Indiana
folder.
a. In Windows Explorer, navigate to the D:\CF\FilesLoc\Indiana folder.
b. Review the following files: IN_GL02-28-2013.csv, IN_GL03-31-2013.csv, and
IN_GL04-30-2013.csv.
The file names begin with IN_GL, include the period key in the file name, and have a
CSV file type.
c. Copy the three files to the D:\CF\FDMEE\inbox\Indiana folder.
In FDMEE, on the Data Load Rule page, set the POV to the Indiana location, Jan - 2013
period, and FDMEE_ACTUAL category.
c. In Location, enter or select Indiana.
d.
3.
Verify that the Jan - 2013 period and FDMEE_ACTUAL category are selected, and
click OK.
Create the IN_Range data load rule to import the three files. Select the period key for the
suffix of the files and enter the data format, MM-dd-yyyy.
b. In Name, enter IN_Range.
c. In Description, enter Load data to a range of periods.
d.
e.
f.
g.
In Category, select FDMEE_ACTUAL.

In File Name, enter IN_GL.csv.
In Directory, enter inbox\Indiana.
In the File Name Suffix Type list, select Period Key.

Chapter 6 - Page 7
Practice 6-2: Loading Data into a Range of Periods
4.
5.
6.
In Period Key Date Format, enter MM-dd-yyyy.

Note: The date format is case-sensitive.
i. Click Save to save the changes.
Run the IN_Range data load rule to import data into February through April of 2013 in
Replace mode for the Indiana location.
a. Under Data Rule Summary, select the IN_Range data load rule.
b. Click Execute.
d. In Start Period, select Feb - 2013.
e. In End Period, select Apr - 2013.
f. In the Import Mode list, select Replace.
g. Click Run.
h. Click OK.
Review the process details for the data load import.
b. Click Refresh to update the status. Repeat this step until the rule runs and the status is
updated.
c. If needed, select the process ID under Process Details.
The steps indicate that data was imported and transformed for February, March, and
April. The status displays a green check mark to indicate a successful step.
View the actual February, March, and April data for the Indiana location and the IN_Range
data load rule in Data Load Workbench.
c. In Period, enter or select Feb 2013.
d.
e.
7.
In Category, verify that FDMEE_ACTUAL is selected.

In Rule, enter or select IN_Range, and click OK.
The imported data for February is displayed. The Import and Validate tasks at the top
of the page display a gold fish to indicate that the tasks were successful.
f. Repeat steps 6b through 6d to view the data in Mar - 2013 and Apr - 2013.
Change the POV to the Jan - 2013 period and the IN_Actual data load rule.
a. In the POV bar, click the location name.
b. In Period, enter or select Jan 2013.
c. In Rule, enter or select IN_Actual, and click OK.

Chapter 6 - Page 8
h.
Goal
In this practice, you schedule a data load rule to import and export data into the Indiana location
for January 2013.
Scenario
The ABC Corporation needs source data loaded for the Indiana location on a weekly basis. To
accomplish this, you schedule the Indiana data load rule to run automatically every week on the
same day. This enables you to run the rule during off hours and to repeat the execution of the
rule on a regular basis.
Time
8 minutes
Tasks
1.
2.
3.
On the Data Load Rule page, set the POV to the Indiana location, Jan - 2013 period, and
c. In Location, enter Indiana.
d. In Period, enter or select Jan 2013.
e. In Category, enter or select FDMEE_ACTUAL, and click OK.
Schedule the IN_Actual data load rule to run on a weekly basis beginning today in a few
minutes. The rule should run for the current POV period.
a. Under Data Rule Summary, select the IN_Actual data load rule.
b. Click Schedule.
The Schedule dialog box is displayed.
c. Select Import from Source, Export to Target, and Use POV Period.
d. In the Import Mode list and the Export Mode list, select Replace.
e. Under Schedule Details, select Weekly, todays day, clear all other days, and set the
time so that the rule runs in a couple of minutes.
f. Click OK.
The following message is displayed: Scenario has been scheduled successfully.
g. Click OK.
Wait for the scheduled rule to run and review the process details.
b. Wait for the scheduled time, and then click Refresh to refresh the process status.
Repeat this step until the rule runs and the success status is displayed.
The Process Step area displays each step of the scheduled rule.

Chapter 6 - Page 9
Practice 6-3: Scheduling a Data Load Rule
View the data workflow in Data Load Workbench.

b. In the POV bar, verify that the Indiana location, Jan - 2013 period, and
FDMEE_ACTUAL category are selected.
The imported data is displayed. There is a gold fish under the Import, Validate, and
Export tasks at the top of the page.
4.

Chapter 6 - Page 10
Chapter 7
Practices for Lesson 7: Processing Data in Data Load Workbench

Chapter 7 - Page 1

Processing Data in Data Load
Workbench
Practices Overview
Load data and fix validation errors.
Load data into multiple entities.
Drill through to FDMEE from the target application.
Load data to multiple periods.

Chapter 7 - Page 2
Goal
In this practice, you execute the data workflow tasks to import, validate, and export data.
Scenario
After setting up your import formats, locations, and data load rules, you run the workflow tasks
to import and validate your source data for a specific POV. Your current POV defines the
location, period, and category to which you want to load the data. It also defines the data load
rules that you want to use for the import.
In Data Load Workbench, you import data to one period and verify that all source members are
mapped to valid target application members. When there are validation errors, you must correct
them and validate the data again before you can export the data to your target application.
In this practice, you import data into the Texas location and find some validation errors. After
correcting the member mappings, you validate the data again, and when it is successful, you
export the data to your target application. In a later practice, you verify that the data was loaded
to the target application.
Time
10 minutes
Reviewing Target Application Options

1.
2.
On the Target Application page, verify that the Check Intersection and Drill Region
options are enabled for the FLASH target application.
a. On the Setup tab, under Register, select Target Application.
b. In the Target Application Summary area, select the FLASH application.
c. In the Application Details area, click on the Application Options tab.
d. Verify that the Check Intersection and Drill Region options are set to Yes.
If Check Intersection and Drill Region are not enabled, enable them and click Save to save
the changes.
Importing Data and Fixing Validation Errors

1.
On the Data Load Rule page, set the POV to the Texas location, Jan - 2013 period, and
FDMEE_Actual category.
c. In Location, enter or select Texas.
d.
2.
In Period, enter or select Jan - 2013.
e. In Category, enter or select FDMEE_Actual, and click OK.

Add a data load rule named TX_Actual to load the Texas_GL.txt file. You can upload
the file from the D:\CF\FilesLoc\Texas folder to the FDMEE\inbox\Texas folder.
b. In the Details area, enter TX_Actual in Name.

Chapter 7 - Page 3
Practice 7-1: Loading Data
h.
i.
3.
In Description, enter Texas actual data load rule.

Expand FDMEE, then inbox, and select Texas.
Click Upload.
Click Browse, navigate to the D:\CF\FilesLoc\Texas folder, select the
Texas_GL.txt file, click Open, and then OK.
Select the Texas_GL.txt file, and click OK.

In Data Load Workbench, import actual data to the Texas location in Jan - 2013 with the
TX_Actual data load rule. Use the Replace mode for the import.
b. In the POV bar, click the location name, and verify that Texas, Jan - 2013, and
FDMEE_Actual are selected.
c. In Rule, enter or select TX_Actual, and click OK.
d. At the top of the page, click Import.
The Execution Mode Option dialog box is displayed.
f. In the Execution Mode list, verify that Online is selected.
g. Click OK.
The data is imported and validated for the Texas location. A gold fish under Import
indicates that the import task was successful. A grey fish under Validate indicates that
there are validation errors.

Chapter 7 - Page 4
c.
d.
e.
f.
g.
Review the validation errors.

a. Click on the Validation Errors tab.
Two validation errors are displayed. One entity, Center, and one account, 1100-104,
were not mapped to target members.
b.
c.
5.
In the top grid, select the Entity row.

Below the top grid, click Collapse Pane
to collapse the top grid and display the
bottom grid.
The Details area (bottom grid) displays the rows with the source entity (Center) that is
not mapped.
d. Above the grid, click Restore Pane
to restore the top grid.
e. In the top grid, select the Account row.
Account 1100-104 is not mapped.
Note: You must fix the mappings on the Data Load Mapping page and then validate
the data again.
Fix the validation errors on the Data Load Mapping page.
a. On the Workflow tab, select Data Load Mapping.
b. In the Dimensions list, select Entity.
c. Click on the Explicit tab.
d. In the row that maps the source value Central to the TX target member, change
Central to Center and then click Save.
e. In the Dimensions list, select Account.
f. On the Explicit tab, click Add.
g. In Source Value, enter 1100-104.
h.
6.
In Target Value, enter or select 10000015, and then click Save.
In Data Load Workbench, validate the data to check for any additional errors.
b. At the top of the page, click Validate.
c. Click OK.
A prompt to open or save the file is displayed at the bottom of the page.
d. Click Open.
The intersection check report is displayed with invalid member errors (in orange) in
the Department and ProdSal columns. The member, Marketig and Breaks, were
misspelled in the member mapping file that you loaded in an earlier practice.

Chapter 7 - Page 5
4.
7.
8.
Close the Intersection Check Report.

Note: You must fix the mappings on the Data Load Mapping page and then validate
the data again.
Fix the validation errors on the Data Load Mapping page.
b. In the Dimensions list, select ProdSal.
c. Click on the Explicit tab.
d. In the row that maps the source value 02, change the target value to Brakes and then
click Save.
e. In the Dimensions list, select Department.
f. On the Explicit tab, in the row that maps the source value 112, change the target value
to Marketing and then click Save.
In Data Load Workbench, validate the data to check for any additional errors.
c. Click OK.
An orange fish is displayed under the Validate task to indicate a successful validation.
Exporting Data
1.
In Data Load Workbench, export the Texas data to the target application.
a. At the top of the Data Load Workbench page, click Export.
b. In the Export Mode list, select Replace.
c. In the Execution Mode list, verify that Online is selected, and click OK.
An orange fish is displayed under the Export task to indicate a successful export.

Chapter 7 - Page 6
e.
3.
Review the process details.

b. Note the process ID number for the latest process and review the process steps. You
will need the process ID number for the next step.
The status of each step displays a green check mark which indicates a successful
process.
Verify that the Texas data load file is in the outbox folder.
a. In Windows Explorer, navigate to the D:\CF\FDMEE\outbox folder.
b.
Locate the data load file for your process ID. The data load file name includes the
target application name and the process ID; for example, Flash_51.dat.
c.
Close Windows Explorer and return to FDMEE.
2.

Chapter 7 - Page 7
Goal
In this practice, you load source data to multiple target entities.
Scenario
As the administrator, you must test the workflow process for loading your source data files. You
want to ensure that the import format defines the source data file layout correctly and that all of
the source members are correctly mapped to target application members.
In this practice, you import data into the Ohio location. The Ohio source data file contains data
for multiple target entities. After the import, you verify that each entity is mapped to the correct
target member, and then export the data to your target application. In a later practice, you verify
that the data was loaded to the target application.
Time
4 minutes
Importing Ohio Data

1.
On the Data Load Rule page, set the POV to the Ohio location, Jan - 2013 period, and
FDMEE_Actual category.
c. In Location, enter or select Ohio.
d. In Period, enter or select Jan - 2013.
e. In Category, enter or select FDMEE_Actual, and click OK.
2.
Add a data load rule named OH_Multi to load the Ohio_MultiEnt.txt file. You can
upload the file from the D:\CF\FilesLoc\Ohio folder to the FDMEE\inbox\Ohio folder.
a.
b.
c.
d.
e.
f.
g.
Under Data Rule Summary, click Add.

In the Details area, enter OH_Multi in Name.
In Description, enter Ohio rule for multiple entities.
Expand FDMEE, then inbox, and select Ohio.
Click Upload.
h.
Click Browse, navigate to the D:\CF\FilesLoc\Ohio folder, select the

Ohio_MultiEnt.txt file, click Open, and then OK.
i.
j.

Select the Ohio_MultiEnt.txt file, and click OK.
Click Save to save the data load rule.

Chapter 7 - Page 8
Practice 7-2: Loading Data into Multiple Entities
4.
In Data Load Workbench, import actual data to the Ohio location in Jan - 2013 with the
Ohio_Multi data load rule. Use the Replace mode for the import.
b. In the POV bar, verify that the Ohio location, Jan - 2013 period, FDMEE_ACTUAL
category, and Ohio_Multi rule are selected.
c. At the top of the page, click Import.
d. In the Import Mode list, select Replace.
e. In the Execution Mode list, verify that Online is selected, and click OK.
The data is imported and validated for the Ohio location. A gold fish under the Import
and Validate tasks indicates that the process was successful.
Review the source and target entity members.
a. Scroll down to review the four Ohio entity members in the Source-Entity and Entity
columns.
b. Notice the following entity mappings:
Source Entity
Entity
OH100
OH_100
OH110
OH_110
OH120
OH_120
OH130
OH_130
Exporting Data
In Data Load Workbench, export the Ohio data to the target application.
a. At the top of the Data Load Workbench page, click Export.
b. In the Export Mode list, select Replace.
An orange fish is displayed under the Export task to indicate a successful export. The
data is loaded to the four target application entities.

Chapter 7 - Page 9
3.
Goal
In this practice, you drill through to FDMEE from a grid in the FLASH target application.
Scenario
In a previous practice, you verified that the Drill Region application option is enabled for your
target application. For data that you loaded with FDMEE, this option enables you to drill through
from your target application to the source data in FDMEE.
After running the workflow tasks for the Texas and Ohio locations, you want to verify that the
data was loaded to your target application. In the target application, you view the data in a grid
and then verify the drill through from the target application to FDMEE to view the source data.
Time
5 minutes
Tasks
1.
2.
In EPM Workspace, open the Financial Management application, FLASH, and navigate to
the Documents page.
a. In Workspace, select Navigate, then Applications, then Consolidation, and then
FLASH.
b. In the Application Tasks pane, double-click Documents.
The Documents tab is displayed in the content area on the right.
Open the TX OH Assets document and set the POV to the Actual scenario, 2013 year,
January period, YTD view, <Entity Currency> value, [ICP None] member, and the
[None] member for the Department, ProdSal, Custom3, and Custom4 dimensions.
a. In the content area, double-click the TX OH Assets document to open it.
b. In the POV, select the members in the following table:
Dimension
Member
Scenario
Actual
Year
2013
Period
January
View
YTD
Value
<Entity Currency>
ICP
[ICP None]
Department
[None]
ProdSal
[None]
Custom3
[None]
Custom4
[None]

Chapter 7 - Page 10
Practice 7-3: Drilling Through to FDMEE from the Target Application

Chapter 7 - Page 11
3.
Some of the data that you loaded from FDMEE into the target application is displayed
in the document for the TX and Ohio entities. An indicator symbol in the upper-left
corner of input cells indicates that it contains drillable data. Data is displayed for cash
accounts, such as accounts 10000005 and 10000010.
Drill through from the Texas value for account 10000005 to the FDMEE landing page, and
then view the mappings for one of the source amounts.
a. Right-click the Region1.TX, 10000005 data-input cell to display the shortcut menu.
b. Select Drill and then Drill Through to Source.
The Drill Through tab displays two grids with the target and source data.
Note: It may take a minute for the two grids to display.
c. In the Drill Through Details grid, click a source amount and select View Mappings.
The Mapping Details dialog box displays the mappings for the source amount.
d. Click OK to close the dialog box and display the Drill Through tab.
e. Select File, then Close, and then Current to close the Drill Through tab and display
the FLASH application tab.
f. Select File, then Close, and then Current to close the FLASH application tab.
g. If prompted to continue closing the application, click OK.
The Data Management tab is displayed.
Goal
In this practice, you load budget data into the January through December time periods.
Scenario
In a previous practice, you reviewed an Excel template file that contains Texas trial balance
data for multiple time periods. You also created a multi-period import format to load this file.
As the administrator, you must test the workflow process for loading the Excel template. You
want to ensure that the Excel template includes the correct metadata tags for loading the source
data into multiple periods. You also want to verify that all source members are correctly mapped
to target application members.
In this practice, you first create the data load rule to load the multi-period Excel template, and
then you import the budget data into the Texas location. You import the data from the Data Load
Rule page since you are importing into more than one period. After the import, you verify that
the process was successful and view the data in Data Load Workbench.
Time
6 minutes
Tasks
1.
2.
On the Data Load Rule page, set the POV to the Texas location and the FDMEE_BUDGET
category.
b. In the POV bar, click the location name and change the POV to the Texas location and
the FDMEE_BUDGET category.
Add a data load rule named TX_MultiPeriod to load the TX_TrialBalance.xls file. You
can upload the file from the D:\CF\FilesLoc\Texas folder to the FDMEE\inbox\Texas
folder.
b. In the Details area, enter TX_MultiPeriod in Name.
c. In Description, enter Load multi-period budget data.
d. In the Category list, verify that FDMEE_BUDGET is selected.
e. In File Name, click Select.
f. Expand FDMEE, then inbox, and select Texas.
g. Click Upload.
h.
i.
j.
Click Browse, navigate to the D:\CF\FilesLoc\Texas folder, select the

TX_TrialBalance.xls file, then click Open, and then OK.
Select the TX_TrialBalance.xls file, and click OK.
In Import Format, enter or select MultiPeriod.

Chapter 7 - Page 12
Practice 7-4: Loading Data into Multiple Periods
4.
5.
6.

Chapter 7 - Page 13
3.
k. Click Save to save the data load rule.

Run the TX_MultiPeriod data load rule to import data into January through December of
2013 for the Texas location. Replace the data during the import.
a. Under Data Rule Summary, verify that the TX_MultiPeriod data load rule is selected.
b. Click Execute.
d. In Start period, select Jan - 2013, and in End Period, select Dec - 2013.
f. Click Run.
g. Click OK.
Review the process details.
b. Click Refresh to update the status. Repeat this step until the rule runs and the success
status is updated.
c. If needed, select the process ID.
The status for each step (import and transform) displays a green check mark to
indicate a successful step.
The Select Point of View dialog box displays a warning message that the data load rule
is not valid for the FDMEE_BUDGET category.
b. In Rule, enter or select TX_MultiPeriod, and click OK.
The imported budget data for January is displayed.
c. Change the POV to the Feb - 2013 period.
The imported budget data for February is displayed.
d. Change the POV to the Dec - 2013 period.
The imported budget data for December is displayed.
Change the POV back to the Texas location, Jan 2013 period, FDMEE_ACTUAL
category, and TX_Actual data load rule.

Chapter 7 - Page 14
Chapter 8
Practices for Lesson 8: Setting Up Check Rules and Check Entities

Chapter 8 - Page 1

Setting Up Check Rules and
Check Entities
Practices Overview
Create, assign, and verify check rules.
Create, assign, and verify check entities.

Chapter 8 - Page 2
Goal
In this practice, you create check rules, assign them to a location, and verify the rules.
Scenario
As the administrator, you want to enforce data integrity during the workflow process. With check
rules, you can retrieve and test values that you loaded to the target application and display them
in a report. FDMEE runs this check report as you load data to your target application. By default,
FDMEE runs the report for each entity that you load to the target application.
In this practice, you create check rules to review Net Sales, Gross Profit, and Net Income
account values that you loaded to your target application. You also test the out-of-balance
account to verify that it is zero.
Time
18 minutes
Creating Check Rules

1.
2.
On the Check Rule Group page, create the Region1 check rule group with the description
Region1 validation.
a. On the Workflow tab, under Data Load, select Check Rule Group.
The Check Rule Group page is displayed.
b. In the Check Rule Group Summary area, click Add.
A blank row is created in the Check Rule Group Summary area.
c. In the Check Rule Group Details area, enter the name Region1 and the description
Region1 validation.
d. Click Save to save the changes.
Add the check rule details listed in the following table. In the Category attribute value of
each rule, select All. Save the changes as you add each rule.
a.
b.
c.
d.
Display Value
Attribute
#Title
Description: Region1 Validation

Sequence: 10
#SubTitle
Description: Key Data

Sequence: 20
#ModeList
Sequence: 30
In the Rule Item Details area, click Add.

In Display Value, enter #Title.
In Description, enter Region1 Validation.
In Sequence, enter 10, and click Save.

Chapter 8 - Page 3
Practice 8-1: Creating, Assigning, and Verifying Check Rules
f.
3.
Repeat steps 2a through 2d to add the display value, #SubTitle, the description, Key
Data, and sequence 20.
Repeat steps 2a through 2d to add the display value, #ModeList with sequence 30.
Continue adding the check rule details listed in the following table. In the Category attribute
value of each rule, select All. Save the changes as you add each rule.
a.
b.
c.
d.
e.
f.
Display Value
Attribute
TOT_NET_SLS
Description: Net Sales

Sequence: 40
Rule Logic: |,,,,,,TOT_NET_SLS,[ICP Top], TotDepts,
TotProd,[None],[None],,,,,,,,,,,,,,,,|
GR_PROFIT
Description: Gross Profit

Sequence: 50
Rule Logic: |,,,,,,GR_PROFIT,[ICP Top],
TotDepts,TotProd,[None],[None],,,,,,,,,,,,,,,,|
NET_INC
Description: Net Income

Sequence: 60
Rule Logic: |,,,,,,NET_INC,[ICP Top], TotDepts,
TotProd,[None],[None],,,,,,,,,,,,,,,,|

In Display Value, enter or select TOT_NET_SLS.
In Description, enter Net Sales.
In Sequence, enter 40.
In Rule Logic, click Edit
.
The Rule Logic dialog box is displayed.
In the Rule Summary area, click Add.
g.
In the blank row, click Edit

A smaller Rule Logic dialog box is displayed.
h. In Intersection Type, select Target Intersection.
i. In the Dimension list, select Account.
j. Wait until the list of target accounts is displayed, and then search and select the
TOT_NET_SLS account.
k. Click Add to Intersection.
l. Repeat steps 3i through 3k to add the [ICP Top] member from the ICP dimension to
the intersection.
m. Repeat steps 3i through 3k to add the TotDepts member from the UD1 dimension, the
TotProd member from the UD2 dimension, and the [None] member from the UD3 and
UD4 dimensions.
n. Click OK.
The rule is displayed in the Rule Summary area.
o. Click OK.

Chapter 8 - Page 4
e.
Repeat steps 3a through 3o to add the display value, GR_PROFIT, the description,
Gross Profit, sequence 50, and rule logic
|,,,,,,GR_PROFIT,[ICP Top],
TotDepts,TotProd,[None],[None],,,,,,,,,,,,,,,,|.
q.
Repeat steps 3a through 3o to add the display value, NET_INC, the description, Net
Income, sequence 60, and rule logic
|,,,,,,NET_INC,[ICP Top], TotDepts,
TotProd,[None],[None],,,,,,,,,,,,,,,,|.

Continue adding the check rule details listed in the following table. In the Category attribute
value of each rule, select All. Save the changes as you add each rule.
Display Value
Attribute
#SubTitle
Description: Check Rules

Sequence: 70
#ModeRule
Sequence: 80
OUT_OF_BALANCE_ACCT
Rule Text: TB must be 0

Sequence: 90
Rule Logic: abs(|,,,,,,OUT_OF_BALANCE_ACCT,[ICP
Top],TotDepts,TotProd,[None],[None],,,,,,,,,,,,,,,,|)==0;
|,,,,,,OUT_OF_BALANCE_ACCT,[ICP Top],
TotDepts,TotProd,[None],[None],,,,,,,,,,,,,,,,|
a.
b.
c.

In Display Value, enter #SubTitle.
In Description, enter Check Rules.
d.
In Sequence, enter 70, and click Save.

Chapter 8 - Page 5
4.
5.
p.
6.
Repeat steps 2a through 2d to add the display value, #ModeRule with sequence 80.
Repeat steps 2a through 2d to add the display value, OUT_OF_BALANCE_ACCT, the
rule text, TB must be 0, and sequence 90. Add the following rule logic and display
value:
abs(|,,,,,,OUT_OF_BALANCE_ACCT,[ICPTop],TotDepts,TotProd,[None],
[None],,,,,,,,,,,,,,,,|)==0;
|,,,,,,OUT_OF_BALANCE_ACCT,[ICPTop],TotDepts,TotProd,[None],
[None],,,,,,,,,,,,,,,,|
Assigning Check Rules to Locations

1.
2.
On the Location page, assign the Region1 check rule group to the Texas location.
b. Select the Texas location.
c. In the Texas:Details area, in Check Rule Group, enter or select Region1.
Repeat step 1 to assign the Region1 check rule group to the Indiana location.
Note: You can assign a check rule group to multiple locations.
Verifying Check Rules

1.
2.
In Data Load Workbench, set the POV to Texas, Jan - 2013, FDMEE_ACTUAL, and
TX_Actual.
c. In the Select Point of View dialog box, select or enter the Texas location, Jan 2013 period, FDMEE_ACTUAL category, and the TX_Actual rule, and click OK.
Perform the Export task and view the resulting check report.
a. At the top of the page, click Export.
b. In Export Mode, select Replace.

Chapter 8 - Page 6
e.
f.
d.
e.
In Execution Mode, verify that Online is selected, and click OK.

When the task is finished processing, FDMEE automatically runs the Check task by
using the check rules that you assigned to Texas. A prompt to open or save the check
report is displayed at the bottom of the page.
Click Open to open the check report.
FDMEE displays the check report with the account and rule values as defined in the
check rule group for Texas. The following graphic is a portion of the report.
c.
Close the report.

Chapter 8 - Page 7
Goal
In this practice, you create a check entity group, assign it to a location, and consolidate the
entities in the target application.
Scenario
During the workflow process, you want to load the data into your target application and also
consolidate the data. In this practice, you create a check entity group and define the target
application entities that you want FDMEE to consolidate as part of the workflow process. After
you assign the check entity group to a location, FDMEE triggers a consolidation of the target
application entities after a data load. FDMEE then displays the entities and check rules in the
check report so that you can verify the data.
Time
7 minutes
Creating Check Entities

1.
2.
On the Check Entity Group page, create the Region1 check entity group with the
description Region1 consolidation.
a. On the Workflow tab, under Data Load, select Check Entity Group.
The Check Entity Group page is displayed.
b. In the Check Entity Group Summary area, click Add.
A blank row is created in the Check Entity Group Summary area.
c. In the Check Entity Group Details area, enter the name Region1 and the description
Region1 consolidation.
Add a check entity to the group with the details listed in the following table.
a.
b.
c.
d.
e.
f.
Attribute
Value
Parent
Region1
Entity
Region1
Consolidate
Select the check box
On Report
Sequence
10
Under Entity Details, click Add.

In Parent, enter or select the parent entity name, Region1.
In Entity, enter or select the entity name, Region1.
Select the check boxes for Consolidate and On Report.

Chapter 8 - Page 8
Practice 8-2: Creating, Assigning, and Verifying Check Entities
Add another check entity to the group with the details listed in the following table.
a.
Attribute
Value
Parent
Region1
Entity
TX
Consolidate
On Report
Sequence
20
b.
Under Entity Details, click Add.

In Parent, enter or select the parent entity name, Region1.
c.
d.
e.
In Entity, enter or select the entity name, TX.

Select the check boxes for Consolidate and On Report.
f.
Assigning the Check Entity Group to a Location

1.
2.
On the Location page, assign the Region1 check entity group to the Texas location.
b. Select the Texas location.
c. In the Texas:Details area, in Check Entity Group, enter or select Region1.
Verifying Check Entities

1.
In Data Load Workbench, set the POV to Texas, Jan - 2013, FDMEE_ACTUAL, and
TX_Actual.
a.
b.
c.
2.
On the Workflow tab, under Data Load, select Data Load Workbench.
In the POV bar, click the location name.
In the Select Point of View dialog box, select or enter the Texas location, Jan 2013 period, FDMEE_ACTUAL category, and the TX_Actual rule, and click OK.
Perform the Export task and view the resulting check report.
a. At the top of the page, click Export.

Chapter 8 - Page 9
3.
c.
d.
Accept the default load options and click OK to load the data to the target application.
When the task is finished processing, FDMEE automatically runs the Check task by
using the check rules and check entities that you assigned to Texas. A prompt to open
or save the check report is displayed at the bottom of the page.
Click Open to open the check report.
FDMEE displays the check report with the account and rule values as defined in the
check rule group for the entities in the check entity group.
b.
Close the report.

Chapter 8 - Page 10
Chapter 9
Practices for Lesson 9: Processing Batches

Chapter 9 - Page 1

Processing Batches
Practices Overview
Create, execute, and schedule a batch.
Create and execute an open batch.

Chapter 9 - Page 2
Goal
In this practice, you create and execute a batch to load actual data into two locations. You then
schedule the batch to run on a weekly basis.
Scenario
After verifying the importing and exporting of your source data files in FDMEE, you can now set
up batches to move the data files through the workflow tasks in a batch environment. This
process enables you to import data from source systems, validate the member mappings, and
then export the data to your target applications. In a batch environment, you can run multiple
data load rules at one time and schedule batches to run at a later time or on a recurring basis.
In this practice, you set up a batch to run two data load rules to import data into two locations.
After verifying that the batch runs successfully, you schedule the batch to run on a weekly basis.
Time
10 minutes
Creating a Batch Definition

1.
2.
Create a batch definition, WK_TX_IN, with the description Weekly batch for TX and IN.
Define the batch to load data to the FLASH target application with the default execution
mode of Serial.
a. On the Setup tab, under Batch, select Batch Definition.
The Batch Definition page is displayed.
b. In the Batch Definition Summary area, click Add.
A blank row is added to the area.
c. In the Batch area, in Name, enter WK_TX_IN.
e. In the Type list, select Data.
f. Accept the default Execution Mode of Serial.
g. In Description, enter Weekly batch for TX and IN.
Set up the batch to only import and replace data for February and March, 2013.
a. In the Batch Definition Summary area, verify that the WK_TX_IN batch is selected.
b. In the Batch area, click on the Parameters tab.
c. Verify that Import From Source is selected.
d. Deselect the Export To Target and POV Period options.
e. In Start Period, select Feb - 2013.
The period, 2/28/2013, is displayed.

Chapter 9 - Page 3
Practice 9-1: Creating, Executing, and Scheduling a Batch
3.
In End Period, select Mar - 2013.

The period, 3/31/2013, is displayed.
g. In the Import Mode list, select Replace.
Add the TX_Actual and IN_Actual rules to run in the WK_TX_IN batch definition. The
TX_Actual rule should be processed first.
a. In the Batch Jobs area, click Add.
A blank row is added to the Batch Jobs area.
b. In Rule Name, enter or select TX_Actual.
c.
In Job Sequence, enter 10.
d.
e.
Repeat steps 3a through 3c to add the rule name, IN_Actual, with a sequence of 20.
Executing and Verifying the Batch

1.
2.
3.
4.
Execute the WK_TX_IN batch.

a. On the Workflow tab, under Other, select Batch Execution.
The Batch Execution page is displayed.
b. Select the WK_TX_IN batch.
c. Click Execute.
The Information dialog box displays the message Batch has been submitted
successfully.
d. Click OK.
Check the status of the batch in Process Details.
The Process Details page is displayed.
b. Wait a minute and then click Refresh until you see a Batch process name and two
Data Load process names for Texas and Indiana.
c. Select one of the Data Load process IDs and review the process steps. Verify that
each step has a successful status (green check mark).
Review the data loaded into the Texas and Indiana locations for February and March, 2013.
b. Set the POV to the Texas location, Feb - 2013 period, FDMEE_ACTUAL category,
and TX_Actual data load rule, and verify that data was imported and validated
successfully.
c. Repeat step 3b for Texas and the Mar - 2013 period and then for Indiana for both
periods. For Indiana, select the IN_Actual data load rule.
Change the POV to the Texas location, Jan - 2013 period, FDMEE_ACTUAL category,
and TX_Actual data load rule.
Scheduling a Batch
Schedule the WK_TX_IN batch to run every Saturday at a time of your choice.
b. Select the WK_TX_IN batch.

Chapter 9 - Page 4
f.
d.
e.
f.
g.
Click Schedule.
The Schedule dialog box is displayed.
Select Weekly.
Select Saturday and deselect all other days.
Select the time of your choice, and click OK.
The Information dialog box displays the message Scenario has been scheduled
successfully.
Click OK.
c.

Chapter 9 - Page 5
Goal
In this practice, you create and execute an open batch to import data.
Scenario
The ABC Corporation requires that you load multiple file-based data load files for multiple
locations and periods. By setting up open batch files, you can process files automatically and
import them to the appropriate POV based on the open batch file names.
In this practice, you review source data files that have a specific file name format to load actual
data into Texas for April, 2013 and to load budget data into Illinois for January, 2014. The file
names define the batch load order, the POV, and the load method. You copy the files to the
openbatch folder, create and execute the open batch, and then verify the results.
Time
10 minutes
Reviewing and Copying the Open Batch Load Files

1.
Review the open batch load files in the D:\CF\FilesLoc\Batch folder.

a.
b.
2.
3.
In Windows Explorer, navigate to the D:\CF\FilesLoc\Batch folder.

Review the two open batch load files in the folder.
The folder contains the 01@Texas@FDMEE_ACTUAL@Apr - 2013@RR.txt file and
the 02@Illinois@FDMEE_BUDGET@Jan - 2014@RR.txt file. The number at the
beginning of the file name indicates the order in which FDMEE will process the files.
The file names specify the location name, category, and period for the workflow
process. The last two characters of the file names, RR, indicate the source and target
load method (Replace).
In Windows Explorer, copy the two files to the
D:\CF\FDMEE\inbox\batches\openbatch folder.
Exit Windows Explorer and return to FDMEE.
Creating the Open Batch Definition

1.
Create an open batch definition, Open_TX_IL, with the description Open batch for TX and
IL. Define the open batch to load data to the FLASH target application with the default
execution mode of Serial. Specify the file separator, @, and automatically create the data
rules.
a. On the Setup tab, under Batch, select Batch Definition.
The Batch Definition page is displayed.
b. In the Batch Definition Summary area, click Add.
A blank row is added to the area.
c. In the Batch area, in Name, enter Open_TX_IL.
e. In the Type list, select Open Batch.
f. Accept the default Execution Mode of Serial.
g. In the File Name Separator list, select @.

Chapter 9 - Page 6
Practice 9-2: Creating and Executing an Open Batch
Executing and Verifying the Open Batch Process

1.
2.
3.
Execute the Open_TX_IL open batch.

The Batch Execution page is displayed.
b. Select the Open_TX_IL batch.
c. Click Execute.
The Information dialog box displays the message Batch has been submitted
successfully.
d. Click OK.
Check the status of the batch.
The Process Details page is displayed.
b. If needed, click Refresh to update the process ID status. Repeat this step until three
process IDs are displayed (one Batch process and two Data Load processes) and the
process status is updated.
c. Select the process ID for the data load to the Texas location.
The process executed successfully for each process step (import, transform, and
validate). In the Process Details area, note the rule name for the Texas process.
FDMEE automatically created the rule name, Texas_FDMEE_ACTUAL, during the
open batch process.
d. Select the process ID for the data load to the Illinois location.
The Process Details area shows that the process did not complete successfully.
FDMEE automatically created the rule name, Illinois_FDMEE_BUDGET during the
open batch process. The Process Step area displays two process steps (import and
transform).
Note: The validation did not complete successfully because there are yet no member
mappings for the Illinois location.
Review the data loaded into the Texas and Illinois locations during the open batch
process.
b. Set the POV to the Texas location, Apr - 2013 period, FDMEE_ACTUAL category,
and Texas_FDMEE_ACTUAL data load rule.
c.
Note: Be sure to select the correct data load rule.

Verify that Texas data was imported and validated successfully.

Chapter 9 - Page 7
2.
h. Select the Auto Create Data Rule check box.

i. In Description, enter Open batch for TX and IL.
j. Click Save to save the changes.
Set up the open batch to only import data.
a. In the Batch area, click on the Parameters tab.
b. Verify that Import From Source is selected.
c. Deselect the Export To Target check box.
4.
5.
Set the POV to the Illinois location, Jan - 2014 period, FDMEE_BUDGET
category, and Illinois_FDMEE_BUDGET data load rule.
e. Verify that Illinois data was imported successfully. However, the data was not validated
successfully because there are no data load mappings set up for Illinois at this time.
Set the POV back to the Texas location, Jan - 2013 period, FDMEE_ACTUAL category,
and TX_Actual data load rule.
In Windows Explorer, navigate to the D:\CF\FDMEE\inbox\batches\openbatch
folder.
The two data load files are no longer in the openbatch folder. FDMEE moved the files to
the D:\CF\FDMEE\inbox\batches\openbatch\<unique-batch-ID> folder.
d.

Chapter 9 - Page 8
Chapter 10
Practices for Lesson 10: Reporting in FDMEE

Chapter 10 - Page 1

Reporting in FDMEE
Practices Overview
Run predefined reports.
Review a demonstration on defining a custom report.

Chapter 10 - Page 2
Goal
In this practice, you run predefined reports to monitor the FDMEE workflow process, view check
reports, and view trial balance data.
Scenario
ABC Corporation requires a reporting tool that can capture business-critical operations and
revenue-generating activities within the organization. FDMEE provides prebuilt reports that
enable you to view key information on the data integration in FDMEE.
Time
7 minutes
Running a Process Monitor Report

1.
2.
3.
Run the Process Status report for Texas for January through April, 2013.
a. On the Workflow tab, under Other, select Report Execution.
The Report Execution page is displayed.
b. In the Report Group list, select Process Monitor Reports.
The reports in the Process Monitor Reports group are displayed.
c. Select the Process Status Period Range (Cat, Start Per, End Per) report.
d. Click Execute.
The Generate Report dialog box is displayed.
e. Select the FDMEE_ACTUAL category, Jan - 2013 starting period, Apr - 2013 ending
period, and Texas location.
f. In the Report Output Format list, select PDF, and click OK.
g. Click Open.
The report is displayed in Adobe Reader. The report displays process information for
each data load rule for the selected location.
Review the status of the tasks for each period.
Close the report.
Running a Check Report

1.
Run Check Report for actual Texas data in January 2013.

a. In the Report Group list, select Check Reports.
The reports in the Check Reports group are displayed.
b. In the list of report names, select Check Report.
c. Click Execute.
d. Select the FDMEE_ACTUAL category, Jan 2013 period, and the Texas location.

Chapter 10 - Page 3
Practice 10-1: Running Predefined Reports
2.
3.
In the Report Output Format list, select PDF, and click OK.
f. Click Open.
The report is displayed in Adobe Reader.
Review the check rules in the check report for Texas.
Close the report.
Running a Trial Balance Report

1.
2.
3.
Run the Trial Balance report to display the source columns for actual Texas data in January
2013.
a. In the Report Group list, select Base Trial Balance Reports.
The reports in the Base Trial Balance Reports group are displayed.
b. Select the TB All Source Columns (Per,Cat,Loc) report.
c. Click Execute.
d. Select the Jan 2013 period, FDMEE_ACTUAL category, Texas location, and the
TX_Actual rule.
e. In the Report Output Format list, select PDF, and click OK.
f. At the bottom of the page, click Open.
The report is displayed in Adobe Reader.
Review the source columns and data for Texas.
Close the report.

Chapter 10 - Page 4
e.
Goal
In this practice, you review a demonstration on defining a custom report in FDMEE.
Scenario
In addition to the prebuilt reports in FDMEE, you may have a need to create custom reports.
You can use an existing query definition or create a new one, generate an XML file for the
query, and define a report template with BI Publisher. You can then define a new report by
specifying the query definition and report template.
Time
8 minutes
Tasks
1.
2.
In Windows Explorer, navigate to the D:\CF folder.

Double-click FDMEE_Report_demo.exe to view the demonstration.

Chapter 10 - Page 5
Practice 10-2: Defining Reports
Chapter 10 - Page 6
Chapter 11
Practices for Lesson 11: Setting Up Security

Chapter 11 - Page 1

Setting Up Security
Practices Overview
Define role-level security.
Add groups for location security.
Assign users to groups in Shared Services.

Chapter 11 - Page 2
Goal
In this practice, you define role-level security to control user access to FDMEE user-interface
artifacts, such as tasks and reports.
Scenario
As the administrator, you must secure the workflow process and locations in FDMEE. In your
organization, you have intermediate users that require varying access. Some intermediate users
define data load mappings, execute data load rules to import data and review the process
details, and define and execute reports and batches. Other users perform fewer tasks in
FDMEE such as importing data and then executing reports.
In this practice, you define role-level security. In a later practice, you define the groups and
users who have access to these roles.
Time
5 minutes
Tasks
1.
2.
Navigate to the Security Settings page to set up role security.

a. On the Setup tab, under Configure, select Security Settings.
b. On the Security Settings page, verify that the Role Security tab is selected.
Define the Intermediate 6 role with access to defining data load mappings, defining and
executing reports and batches, executing data load rules, importing data, viewing process
details, and defining user settings.
a. In the Role list, select Intermediate 6.
b. On the User Interface tab, select the check box for the following functions:
Batch Definition
Report Definition
Data Load Workbench
Data Load Rule Execution
Data Load Mapping
c.
Batch Execution
Report Execution
Process Details
User Settings

Chapter 11 - Page 3
Practice 11-1: Defining Role-Level Security
4.
Define the Intermediate 6 role with access to trial balance reports, check reports, and
process monitor reports.
a. Click on the Report tab.
b. Select the check box for the following report groups:
Base Trial Balance Reports
Check Reports
Process Monitor Reports
c. Click Save to save the changes.
Define the Intermediate 7 role with access to importing data, executing data load rules,
viewing process details, and defining user settings.
a. Click on the User Interface tab.
b. In the Role list, select Intermediate 7.
c. On the User Interface tab, select the check box for the following functions:
Data Load Workbench
Data Load Rule Execution
Process Details
User Settings

Chapter 11 - Page 4
3.
Goal
In this practice, you add groups to control user access to locations and to roles.
Scenario
In addition to defining the role-level security in FDMEE, you must define the locations and roles
to which users have access. With FDMEE security, you can secure the tasks, reports, batches,
custom scripts, and locations that users can access.
In this practice, you define location groups with access to the Intermediate 6 and Intermediate 7
roles that you set up in the previous practice. In the next practice, you use Shared Services to
define which users in your organization have access to the location groups.
Time
5 minutes
Tasks
1.
2.
3.
4.
Navigate to the Security Settings page to set up location security.

a. On the Setup tab, under Configure, select Security Settings.
b. On the Security Settings page, click on the Location Security tab.
c. If you are prompted to enable security by location, click OK.
Set up location security for the Intermediate 6 role. Define FDMEE as the location security
name prefix and Int6 as the suffix.
a. On the Location Security tab, click Add.
A blank row with the name _<LOCATION>_ is added to the grid.
b. In the Security Setting Details area, in Description, enter Intermediate-6 user.
c. In Prefix, enter FDMEE.
d. In Suffix, enter Int6.
e. Select the Intermediate 6 check box.
Set up location security for the Intermediate 7 role. Define FDMEE as the location security
name prefix and Int7 as the suffix.
a. On the Location Security tab, click Add.
A blank row with the name _<LOCATION>_ is added to the grid.
b. In the Security Setting Details area, in Description, enter Intermediate-7 user.
c.
5.
6.
In Prefix, enter FDMEE.
d. In Suffix, enter Int7.

e. Select the Intermediate 7 check box.
Click Maintain User Group to set up the location groups in Shared Services.
The following information message is displayed User groups and roles successfully
created for all locations.

Chapter 11 - Page 5
Practice 11-2: Adding Groups for Location Security
Goal
In this practice, you assign users to the FDMEE location groups in Shared Services.
Scenario
After defining role-level security and location groups in FDMEE, you use Shared Services to
assign users in your organization to the location groups. The location groups are provisioned
with FDMEE roles, such as Intermediate 6 and Intermediate 7. The groups that users have
access to determine the locations and artifacts that they can access in FDMEE.
After adding users to location groups, your organization also requires that some users have
additional access to FDMEE tasks. In this practice, after assigning a user to a location group,
you also provision the user with the Drill Through role to enable drill through from the target
application to FDMEE source data.
Time
10 minutes
Maintaining Users and Groups in Shared Services

1.
2.
3.
Navigate to the list of groups in Shared Services.

a. In EPM Workspace, select Navigate, then Administer, and then Shared Services
Console.
b. In the left pane, expand User Directories and then Native Directory.
c. Select Groups.
d. In the content area on the right, click Search.
Among the group names are the FDMEE group names for the Intermediate 6 and
Intermediate 7 roles. For example, FDMEE_Texas_Int6 and FDMEE_Texas_Int7.
Review the provisioning for the FDMEE_Texas_Int6 group.
a. In the content area, right-click FDMEE_Texas_Int6 and select Provision.
The Provisioning tab displays the available and selected roles for the
FDMEE_Texas_Int6 group.
b. In the Selected Roles area, expand FDM Enterprise Edition.
The Intermediate 6 role is displayed to indicate that the FDMEE_Texas_Int6 group is
provisioned with the Intermediate 6 role.
c. Click OK twice to close the Provisioning tab and return to the Browse tab.
Assign the Akelly, Mwoo, and Rjackson users to the FDMEE Intermediate 6 group for
Texas, Indiana, and Ohio.
a. Right-click the FDMEE_Texas_int6 group and select Properties.
The Group Properties dialog box is displayed.
b. Click on the User Members tab.
c. Above the Available Users area, click Search.
A list of users is displayed.
d. In the Available Users area, select Akelly, Mwoo, and Rjackson, and click the arrow
to add them to the Assigned Users area.
e. Click OK twice to save the changes and return to the Browse tab.

Chapter 11 - Page 6
Practice 11-3: Assigning Users to Groups in Shared Services
4.
5.
6.
Repeat steps 3a through 3e for the FDMEE_Indiana_Int6 and FDMEE_Ohio_Int6

groups.
Repeat steps 2 and 3 to review the provisioning for the FDMEE_Texas_Int7 group and to
assign Klee and Tredford to the group.
Provision the Rjackson user with the FDMEE Drill Through role.
a. In the Provisioning panel on the left, select Users, and then click Search in the content
area.
The list of users is displayed.
b. Right-click Rjackson and select Provision.
The Provisioning tab is displayed.
c. In the Available Roles area, expand FDM, then FDM Enterprise Edition, and then
Administrator to view the FDMEE roles.
d. Select Drill Through and click the arrow to add the role to the Assigned Roles area.
e. Click OK twice to save the changes and return to the Browse tab.
Select File, then Close, and then Current to exit out of Shared Services and return to
FDMEE.
Verifying Security Settings

1.
2.
3.
4.
5.
6.
Log out of FDMEE, but remain in EPM Workspace.

a. Select File and then Log Off.
b. In the Confirmation dialog box, click Yes.
The Log On page is displayed.
Log on to EPM Workspace and access FDMEE as user Rjackson with password
hyperion.
a. In User Name, enter Rjackson.
b. In Password, enter the case-sensitive password, hyperion, and click Log On.
c. Select Navigate, then Administer, and then Data Management.
Review Rjacksons access to FDMEE tasks and locations.
a. On the Workflow tab, Rjackson has access to Data Load Workbench, Data Load Rule,
and Data Load Mapping. Rjackson also has access to running reports and batches,
viewing process details, and defining user settings.
b. On the Setup tab, Rjackson has access only to defining reports and batches.
c. On the Workflow tab, select Data Load Workbench.
d. In the POV, click the location name.
e. Search for a location and notice that only Indiana, Ohio, and Texas are available.
f. Click Cancel twice to close the dialog box.
Select File, then Log Off, and Yes to log out.
Repeat steps 2 and 3 to log on as Tredford with password hyperion and review the
tasks and locations that Tredford can access. Tredford has no access to tasks on the Setup
tab.
Log out as Tredford, and log on to FDMEE as the admin user with password hyperion.

Chapter 11 - Page 7
f.
Chapter 11 - Page 8
Chapter 12
Practices for Lesson 12: Defining Import Scripts

Chapter 12 - Page 1

Defining Import Scripts
Practices Overview
Extract beginning characters in a load file.
Split characters in a load file.
Skip lines in a load file.
Create a script with temporary variables.

Chapter 12 - Page 2
Goal
In this practice, you create an import script that retrieves the first four characters of the account
number from the source data load file. You assign the script to the Account field in the import
format.
Scenario
The source data load file for the Indiana location includes account numbers that vary in length,
but you need only the first four characters of the account. You create an import script to import
only the first four characters of the source account into the FDMEE staging table.
Time
8 minutes
Creating the Import Script

1.
2.
Use WordPad to review the D:\CF\FDMEE\inbox\Indiana\Indiana_GL.csv file.

b. From the D:\CF\FDMEE\inbox\Indiana folder, open the Indiana_GL.csv file.
The account number is the first field in the file and varies in length.
c. Exit WordPad.
In FDMEE, create an import script, IN_Parse_Account, for the FLASH application.
a. On the Setup tab, under Scripts, select Script Editor.
The Script Editor page is displayed.
b. In the Target Application list, select FLASH.
c. In the Technology list, verify that Jython is selected.
d. Expand the Import folder.
e. Click New.
The Create Script Options dialog box is displayed.
f. In the Script Type list, select Import.
g. In File Name, enter IN_Parse_Account, and click OK.

Chapter 12 - Page 3
Practice 12-1: Extracting Beginning Characters
Enter the script to parse a string and retrieve the left four characters.
a. In the content area, enter the following script:
b.
Click Save.
Assigning the Script to the Import Format

1.
2.
Review the Indiana import format.

b. Select the Indiana import format.
The Mappings area displays the import format mappings. The source Account is the
first field in the data load file.
Assign the IN_Parse_Account script to the Account row of the import format.
a. In the Account row of the import format mapping, click in the Expression column and
enter Script=IN_Parse_Account.py.
The script name is displayed in the Expression field of the Account row.
b.
Importing the Data and Verifying the Script

1.
Navigate to Data Load Workbench and set the POV to Indiana, Jan - 2013,
FDMEE_ACTUAL, and IN_Actual.
b. In the POV bar, click the location name, set the POV to the Indiana location, Jan 2013 period, FDMEE_ACTUAL category, IN_Actual rule, and click OK.
c. At the top of the page, click Import.
d. In the Import Mode list, select Replace.
e. In the Execution Mode list, verify that Online is selected.

Chapter 12 - Page 4
3.
2.
Click OK.
The data is imported and validated for the Indiana location. The Import task was
successful. The Validate task was not successful because you do not have member
mappings for the shortened source account names.
Verify that the imported data displays only four digits for the source account.
The following graphic displays a portion of the imported rows.
f.

Chapter 12 - Page 5
Goal
In this practice, you create import scripts to parse a string from a source data file and import the
parsed fields into multiple columns in the FDMEE staging table.
Scenario
The source data load file for the New York location contains a string with three fields separated
by hyphens. The first field is the source cost center (entity), the second field is the source
account, and the third field is the source account description. You create three import scripts to
parse the string into three separate fields and import them to the source entity, account, and
account description columns in the FDMEE staging table.
Time
13 minutes
Creating the Import Scripts

1.
2.
Use Excel to review the D:\CF\FilesLoc\NewYork\NewYork.csv file.

a. In the FDMEE folder on the Windows desktop, launch Microsoft Office Excel 2007.
b. From the D:\CF\FilesLoc\NewYork folder, open the NewYork.csv file.
c. On the Home ribbon, select Format, and then click AutoFit Column Width to widen
the columns in the file.
The first column in the file contains a string with three fields separated by hyphens.
The first field is the cost center, the second field is the account, and the third field is
the account description.
d. Exit Excel and do not save any changes.

In FDMEE, create an import script, NY_Parse_Ent, for the FLASH application.
e. Click New.
g. In File Name, enter NY_Parse_Ent, and click OK.

Chapter 12 - Page 6
Practice 12-2: Splitting Characters
4.
5.
6.
Enter the script to parse a string and retrieve the first set of characters from the first field in
the load file.
a. In the script content area, enter the following script:
b. Click Save.
Create an import script, NY_Parse_Acc, for the FLASH application.
a. In the Script Editor page, click New.
b. In the Script Type list, select Import.
c. In File Name, enter NY_Parse_Acc, and click OK.
Enter the script to parse a string and retrieve the second set of characters from the first field
in the load file.
b. Click Save.
Repeat steps 4 and 5 to create an import script, NY_Parse_Desc, to parse a string and
retrieve the last set of characters located after the hyphen in the first field in the load file.
b.
Click Save.
Creating the Import Format

1.
Create a comma delimited import format named NewYork for a File source system and
the FLASH target application.
c. In Name, enter NewYork, in the Source System list, select File, in the File Type list,
select Delimited, in File Delimiter, select Comma, and in the Target Application list,
select FLASH.

Chapter 12 - Page 7
3.
Define the import format mappings for the NewYork.csv file with the following guidelines:
Source Column
Description
Account
Account is located in the first field of the file. In the

Expression column, add the NY_Parse_Acc.py script.
Amount
Amount is located in the fifth field of the file.
Account
Description
Add a description row to the import format. The description

is located in the first field of the file. In the Expression
column, add the NY_Parse_Desc.py script.
Entity
Entity is located in the first field of the file. In the Expression

column, add the NY_Parse_Ent.py script.
a.
b.
c.
d.
In the NewYork:Mappings area, in Source Column for the Account target dimension,
enter Account.
In Expression, enter Script=NY_Parse_Acc.py.
In Source Column for the Amount row, enter Amount.
e.
f.
g.
h.
i.
j.
k.
l.
m.

In Source Column for the Entity row, enter Entity.
In Expression, enter Script=NY_Parse_Ent.py.
In the Mappings area, click Add, and then select Description Row.
In Source Column of the Description 1 row, enter Account Description.
In Expression, enter Script=NY_Parse_Desc.py.
Creating the NewYork Location and Data Load Rule

1.
Create the NewYork location and use the NewYork import format.

Chapter 12 - Page 8
2.
2.
In the Location area, click Add.

Under Details, in Name, enter NewYork.
d. In the Import Format list, click Search

.
e. Select NewYork, and click OK.
Create the NewYork data load rule to load the NewYork.csv file. You can upload the file
from the D:\CF\FilesLoc\NewYork folder to the FDMEE\inbox\NewYork folder.
b. In the POV, click the location name, and change the POV to the NewYork location,
Jan - 2013 period, and FDMEE_ACTUAL category.
c. Under Data Rule Summary, click Add.
d. Under Details, in Name, enter NewYork.
e. In Description, enter New York actual data load rule.
f. In the Category list, select FDMEE_ACTUAL.
g. In File Name, click Select.
h. Expand FDMEE, then inbox, and select NewYork.
i. Click Upload.
j. Click Browse, navigate to the D:\CF\FilesLoc\NewYork folder, select the
NewYork.csv file, click Open, and then OK.
k. In the File area, select the NewYork.csv file, and click OK.
l. Click Save to save the data load rule.
Importing the Data and Verifying the Scripts

1.
2.
Navigate to Data Load Workbench and add the Description-1 column to the grid.
b. Select View, then Columns, and then Manage Columns.
c. In the Hidden Columns area, select Description-1, and click Move to add the column
to the Visible Columns area.
d. With the Description-1 column selected, use the up arrow to position the column after
the Account column, and then click OK.
Import the data in Replace mode into the NewYork location.
a. At the top of the page, click Import.
b. In the Import Mode list, select Replace.
c. In the Execution Mode list, verify that Online is selected.
d. Click OK.
The data is imported and validated for the NewYork location. The Import task was
successful, but the Validate task was not because there are no mappings for the
NewYork location at this time.

Chapter 12 - Page 9
b.
c.
Verify that data is displayed for the source entity, account, and description columns. The
string in the first field of the data load file was split into three separate fields and loaded to
the NewYork location. The following graphic displays a portion of the imported data.
3.

Chapter 12 - Page 10
Goal
In this practice, you parse a string and skip rows in the source data file with a cost center (entity)
that begins with 100.
Scenario
The source data load file for the New York location contains data for the 100 and 200 source
entities. You want to load the data rows only for the 200 source entity. You create a script and
assign it to the Entity row of the import format. When you import data into the NewYork location,
the script checks the source entity value. If the source entity begins with 100, FDMEE skips the
row and does not import it.
Time
7 minutes
Creating the Import Script

1.
2.
Create an import script, NY_Skip, for the FLASH application.

e. Click New.
g. In File Name, enter NY_Skip, and click OK.
Enter the script to parse the first string in the load file and skip lines with a cost center that
begins with 100.
b.
Click Save.

Practice 12-3: Skipping Lines in a Load File
Assigning the Script to the Import Format
2.
Review the NewYork import format.

b. Select the NewYork import format.
The Mappings area displays the import format mappings.
In the Entity row of the import format mapping, replace the NY_Parse_Ent.py script with the
NY_Skip.py script.
a.
b.
In the Entity mapping row, delete Script=NY_Parse_Ent.py in the Expression

column and replace the expression with Script=NY_Skip.py.

1.
2.
3.
Set the POV to the NewYork location, Jan 2013 period, FDMEE_ACTUAL category, and
NewYork rule.
a. In the POV bar, click the location name.
b. Set the POV to the NewYork location, Jan 2013 period, FDMEE_ACTUAL category,
and NewYork rule.
c. Click OK.
Import the data in Replace mode into the NewYork location.
d. Click OK.
The data is imported into the NewYork location. The validation fails because member
mappings are not yet defined for the location.

1.
Verify that data rows with an entity that begins with 100 are not included in the import.
4.

Goal
In this practice, you create import scripts to store the entity value in a temporary variable and
assign it to the Entity field.
Scenario
In the source data load file for the Georgia location, the entity is not repeated in every row, but it
is contained in the header of each section of the file. To import the correct entity for each data
row, you create two import scripts. You assign the first import script to the Amount row of the
import format. During the import, the script checks if the row is a header that contains the entity
value. If it is, the entity value is stored in a global variable. You assign the second script to the
Entity row of the import format. During the import, this script assigns the value in the global
variable to the Entity column in the FDMEE staging table.
Time
12 minutes
Creating the Import Scripts

1.
2.
Use WordPad to review the D:\CF\FilesLoc\Georgia\Georgia.txt file.

b. From the D:\CF\FilesLoc\Georgia folder, open the Georgia.txt file.
The entity is not repeated in every row, but it is contained in the header of each report
section. The entity, such as 0563, is displayed after the Bus Area / Dept: label.
c. Exit WordPad.
In FDMEE, create an import script, Get_Entity, for the FLASH application.
e. Click New.
g. In File Name, enter Get_Entity, and click OK.

Practice 12-4: Creating a Script with Temporary Variables
4.
5.
Enter the script to store the entity value into a temporary variable.
b. Click Save.
Create an import script, Put_Entity, for the FLASH application.
a. In the Script Editor page, click New.
b. In the Script Type list, select Import.
c. In File Name, enter Put_Entity, and click OK.
Enter the script to retrieve the Entity value from the GeorgiaEntity global variable.
b.
Click Save.

1.
2.
Create a fixed import format named Georgia for a File source system and the FLASH
target application.
c. In Name, enter Georgia, in the Source System list, select File, in the File Type list,
select Fixed, and in the Target Application list, select FLASH.
Define the import format mappings for the Georgia.txt file with the following guidelines:
Source Column
Description
Account
Account is located in the Acct column of the file. The

account begins at character 1 and is 4 characters long.
Amount

The amount begins at character 110 and is 21 characters
long. In the Expression column, add the script,
Get_Entity.py.

3.

is located in the Description column of the file. It begins at
Entity
Entity is in header areas in the file. It begins at character 33

and is 4 characters in length. In the Expression column,
add the script, Put_Entity.py.
a.
In the Georgia:Mappings area, in Source Column for the Account target dimension,
enter Account.
b.
c.

d.
e.
f.
g.
In Expression, enter Script=Get_Entity.py.

h.
i.
j.
In Expression, enter Script=Put_Entity.py.

k.
l.

Creating the Georgia Location and Data Load Rule

1.
2.
Create the Georgia location and use the Georgia import format.
c. Under Details, in Name, enter Georgia.
d. In the Import Format list, click Search
.
e. Select Georgia, and click OK.
Create the Georgia data load rule to load the Georgia.txt file. You can upload the file
from the D:\CF\FilesLoc\Georgia folder to the FDMEE\inbox\Georgia folder.

Account
Description
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
In the POV, click the location name, and change the POV to the Georgia location, the
Jan - 2013 period, and the FDMEE_ACTUAL category.
Under Data Rule Summary, click Add.
Under Details, in Name, enter Georgia.
In Description, enter Georgia actual data load rule.
Expand FDMEE, then inbox, and select Georgia.
Click Upload.
Click Browse, navigate to the D:\CF\FilesLoc\Georgia folder, select the
Georgia.txt file, click Open, and then OK.
In the File area, select the Georgia.txt file, and click OK.
Click Save to save the data load rule.

1.
2.
3.
Import the data in Replace mode into the Georgia location.
d. Click OK.
The data is imported and validated for the Georgia location. The Import task was
successful, but the Validate task was not because you did not create data load
mappings for the Georgia location.
Verify that the entity is displayed for each imported row.

b.
Chapter 13
Practices for Lesson 13: Defining Mapping and Event Scripts

Chapter 13 - Page 1

Defining Mapping and Event
Scripts
Practices Overview
Set up a mapping script.
Create an event script.

Chapter 13 - Page 2
Goal
In this practice, you add a mapping script to check source ICP values to determine target ICP
members.
Scenario
Now that you have verified the workflow process for your data load files, you want to build
additional mapping logic for mapping source members to target application members. With
FDMEE mapping scripts, you can build mapping logic to derive target application members
based on multiple source column and IF THEN logic. Mapping scripts enable you to map source
members by using a script expression rather than hard-coding a target application member. In
this scenario, you determine the ICP target application member based on a portion of the ICP
source member.
Time
8 minutes
Reviewing Imported Texas Data

1.
2.
In Data Load Workbench, set the POV to the Texas location, Jan - 2013 period,
FDMEE_ACTUAL category, and TX_Actual rule.
b. In the POV bar, click the location name and set the POV to the Texas location, Jan 2013 period, FDMEE_ACTUAL category, and TX_Actual rule, and then click OK.
The imported data for Texas is displayed.
Review the target mappings for source ICP members that begin with 1940-.
a. If the filter row is not displayed above the column names, select View, and then Query
by Example.
b. In the filter row above the Source-ICP column, enter 1940-, and press Enter.
The source ICP members that begin with 1940- are displayed. ICP members 1940-101
through 1940-105 map to the [ICP None] target member. Some of the ICP mappings
are displayed in the following graphic.
Modifying Data Load Mappings with a Script

1.
In the Data Load Mapping page, review the Between mapping for the source ICP members
1940-101 through 1940-105.

Chapter 13 - Page 3
Practice 13-1: Setting Up a Mapping Script
2.
In the Dimensions list, select ICP.

The All Mappings tab displays all of the source ICP mappings.
c. Click on the Between tab.
The 1940-101 through 1940-105 source values map to the [ICP None] target member.
Add a mapping script for the 1940-101,1940-105 source values. In the script, check the
source ICP value to determine the target ICP member.
Source ICP Value
Target ICP Member
Ends in 102
Map to the SP member.
Ends in 103
Map to the OH member.
Ends in 104
Map to the IN member.
All other members
Map to the [ICP None] member.
a.
For the 1940-101,1940-105 source value, change the target value, [ICP None], to
#SCRIPT, and then press Tab.
b.
In the Script column, click the script editor icon

.
The Edit Script dialog box is displayed.
Add the following script to check the mapped value of the source ICP member to
determine the target ICP member:
c.
d.
e.
Click OK.

Chapter 13 - Page 4
b.
4.
In Data Load Workbench, verify the mapping script by running the Validate task.
a. On the Workflow tab, under Data Load, select Data load Workbench.
Review the target mappings for the source ICP members that begin with 1940-.
a. If needed, in the filter row above the Source-ICP column, enter 1940-, and press
Enter to display the source ICP members that begin with 1940-.
b. Verify the member mappings. Source account 1940-102 maps to the target member
SP, 1940-104 maps to the target member IN, and 1940-101 and 1940-105 map to
the target member [ICP None]. No data was imported for the 1940-103 source
account.

Chapter 13 - Page 5
3.
Goal
In this practice, you create an event script that determines which import format to use
depending on the source data file that you want to import.
Scenario
You have two source data load files that you want to import into the Iowa location. One file
contains income statement data and the second file contains balance sheet data. The files have
different layouts and require a different import format for each file. When you create the Iowa
location, you specify that, by default, FDMEE should use the import format for the balance sheet
data. To also load income statement data into the Iowa location, you add script to the
BefImport event script. Whenever you import the income statement data file, the event script
overrides the default import format with the import format that you defined for the income
statement data file.
Time
12 minutes
Creating the Import Formats

1.
Use WordPad to review the IowaBal.txt and IowaInc.txt files from the
D:\CF\FilesLoc\Iowa folder before you create an import format for each file.
b. From the D:\CF\FilesLoc\Iowa folder, open the IowaBal.txt file, and review the
data rows in the file. A portion of the file is displayed in the following graphic.
c.
2.
Open the IowaInc.txt file from the same folder and review the data rows in the file.
A portion of the file is displayed in the following graphic.
d. Exit WordPad.
In FDMEE, create a fixed import format named Iowa_Bal for a File source system and the
FLASH target application. The import format defines the fields in the IowaBal.txt file.

Chapter 13 - Page 6
Practice 13-2: Creating an Event Script
d.
3.
Define the import format mappings for the IowaBal.txt file with the following guidelines:
Source Column
Description
Account
Account is located in the Account column of the file. The

account begins at character 1 and is 15 characters long.
Amount
Amount is located in the Ending Balance column of the file. The

amount begins at character 93 and is 15 characters long.
Account
Description
Add a description row to the import format. The description is

located in the Description column of the file. It begins at
Entity
Entity is not in the rows of the file. Define the entity by entering
1 in the Start and Length attributes, and in the Expression
column, enter Bal.
a.
4.
In Name, enter Iowa_Bal, in the Source System list, select File, in the File Type list,
select Fixed, and in the Target Application list, select FLASH.
b.
In the Iowa:Mappings area, in Source Column for the Account target dimension, enter
Account.
c.
d.
e.
f.
g.
h.
i.
j.

In Start, enter 1, in Length, enter 1, and in Expression, enter Bal.
Create a comma delimited import format named Iowa_Inc for a File source system and
the FLASH target application. The import format defines the fields in the IowaInc.txt file.
a. Under Import Format Summary, click Add.
b. In Name, enter Iowa_Inc, in the Source System list, select File, in the File Type list,
select Delimited, in the File Delimiter list, select Comma, and in the Target Application
list, select FLASH.

Chapter 13 - Page 7
c.
Source Column
Description
Account
Account is located in the first field of the file.
Amount
Amount is located in the third field of the file.
Account
Description

is located in the second field of the file.
Entity
Entity is not in the rows of the file. Define the entity by

entering 1 in the Field Number field, and in the Expression
column, enter Inc.
a.
In the Iowa:Mappings area, in Source Column for the Account target dimension, enter
Account.
b.
c.
d.
e.
f.
g.
In Source Column for the Amount row, enter Amount, and in Field Number,
enter 3.
In Field Number, enter 1, and in Expression, enter Inc.
h.
i.

Creating the Event Script

1.
Create the script for the BefImport event script for the FLASH application. Define the script
to change the default import format (Iowa_Bal) to Iowa_Inc when the data load file is
IowaInc.txt.
d. In the Event folder, select the BefImport script name.

Chapter 13 - Page 8
5.
c. Click Save to save the changes.

Define the import format mappings for the IowaInc.txt file with the following guidelines:
2.
In the content area on the right, add the following script to change the default import
format (Iowa_Bal) to Iowa_Inc when the data load file is IowaInc.txt.
Creating the Iowa Location and Data Load Rule

1.
Create the Iowa location and use Iowa_Bal as the default import format.
c. Under Details, in Name, enter Iowa.
d.
e.
f.
In the Import Format list, click Search

, and select Iowa_Bal.
In Parent Location, enter or select Texas, and click OK.

Chapter 13 - Page 9
e.
Create the IowaAct data load rule. Set up the data load rule to prompt for the data load file.
b. In the POV, click the location name, and enter or select the Iowa location, the
Jan - 2013 period, and the FDMEE_ACTUAL category.
c. Under Data Rule Summary, click Add.
d. Under Details, in Name, enter IowaAct.
e.
f.
g.
In Description, enter Iowa actual data load rule.

Note: When you run this data load rule, it will prompt you for the data load file name
because you did not select a file name in the data load rule definition.

1.
2.
Navigate to Data Load Workbench and, optionally, add the Description-1 column to the
grid.
Import the IowaBal.txt data file in Replace mode into the Iowa location. You must
upload the file from the D:\CF\FilesLoc\Iowa folder to the FDMEE\inbox\Iowa folder.
b. In File Name, click Select.
c. Expand FDMEE, then inbox, and select Iowa.
d. Click Upload.
e. Click Browse, navigate to the D:\CF\FilesLoc\Iowa folder, select the
IowaBal.txt file, click Open, and then OK.
f.
In the File area, select the IowaBal.txt file, and click OK.
g.
h.
In the Import Mode list, select Replace.

In the Execution Mode list, verify that Online is selected.

2.
3.
Click OK.
The balance sheet data is imported and validated for the Iowa location. The source
entity field displays the Bal value. The following graphic displays a portion of the
imported data rows.
Import and append the data from the IowaInc.txt file into the Iowa location. You must
upload the file from the D:\CF\FilesLoc\Iowa folder to the FDMEE\inbox\Iowa folder.
b. In File Name, click Select.
c. Expand FDMEE, then inbox, and select Iowa.
d. Click Upload.
e. Click Browse, navigate to the D:\CF\FilesLoc\Iowa folder, select the
IowaInc.txt file, click Open, and then OK.
f. In the File area, select the IowaInc.txt file, and click OK
g. In the Import Mode list, select Append.
h. In the Execution Mode list, verify that Online is selected.
i. Click OK.
The income statement data is imported and appended to the balance sheet data.
j. Scroll down to review the imported data.
The source entity column for the income statement data displays the Inc value. The
following graphic displays a portion of the imported data rows.

i.

Chapter 14
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 1

FDMEE Integration with Other
Source Systems
Practices Overview
Review a demonstration on integrating GL data in FDMEE.
Load source data from the open interface table.
Chapter 14 - Page 2
Goal
In this practice, you review a demonstration on integrating GL data in FDMEE.
Scenario
FDMEE supports loading data into EPM applications from general ledger source systems. In
this demonstration, you review the integration of data from an Oracle E-Business Suite (EBS)
source system.
Time
8 minutes
Tasks
1.
2.
In Windows Explorer, navigate to the D:\CF folder.

Double-click FDMEE_ERP_demo.exe to view the demonstration.
Chapter 14 - Page 3
Practice 14-1: Integrating GL Data in FDMEE
Goal
In this practice, you review the open interface source system and adapter. You create an open
interface adapter and define the columns that you want to load from the open interface table into
the FDMEE staging table. You then create the import format, location, and data rule to import
the data into FDMEE.
Scenario
In addition to loading data into FDMEE from source system data files, your organization also
needs to load data from other source systems. The data from these source systems has been
loaded to the FDMEE open interface table. As the administrator, you must set up the integration
in FDMEE to import the data from the open interface table into the FDMEE staging tables.
Time
12 minutes
Reviewing System Settings and the Open Interface Table

1.
2.
3.
Review the details of the OPENINT source system.

a. On the Setup tab, under Register, select Source System.
The Source System page is displayed.
b. Under Source System Summary, select OPENINT.
Under Details, the OPENINT source system attributes are displayed. The source
system type for OPENINT is Others.
Review the OPENINT source period mappings.
a. On the Setup tab, under Integration Setup, select Period Mapping.
The Global Mapping tab displays the global period mappings.
b. Click on the Source Mapping tab.
c. In the Source System list, select the source system name, OPENINT.
d. In the Mapping Type list, verify that Explicit is selected.
The January through June source period mappings for 2013 were created for you.
Notice that the calendar name is GLcal. You specify the calendar name when you
define the data load rule for the open interface table.
Review the open interface adapters.
a. On the Setup tab, under Register, select Source Adapter.
b. In the Source Adapter Summary area, select the OPENINT adapter key.
c. In the Source Adapter Details area, review the detail on the Source Column tab.
There are 30 columns defined with display names of Column 1 through Column 30.
d. In the Source Adapter Summary area, select the OPENINT2 adapter key.
The OPENINT2 adapter key was added for you. It is a copy of the original OPENINT
adapter key. The OPENINT2 adapter key includes seven columns to match the data
that was loaded to the open interface table. The other columns were removed.
In the Source Adapter Details area, review the seven columns. The Display Name for
each column was updated to identify the data in the open interface table. For example,
Chapter 14 - Page 4
Practice 14-2: Loading Source Data from the Open Interface Table
f.
g.
Scroll to the right and notice COL01 through COL07, which contain the data that you
want to import. For example, COL01 contains the source entity name and COL02
contains the source account name.
Note: Do not make any changes to the table.

Select File and then Exit to exit out of SQL Developer.
Chapter 14 - Page 5
4.
COL01 in the table contains the Entity value and COL02 in the table contains the
Account value. The display name is used in the Import Format and Data Load
Workbench pages.
In SQL Developer, review the data in the open interface table, AIF_OPEN_INTERFACE.
The table is located under hyperion\Other Users\EPM.
a. In the FDMEE folder on the Windows desktop, launch SQLDeveloper.
b. Expand hyperion, then Other Users, and then EPM.
c. Below EPM, expand Tables and select the AIF_OPEN_INTERFACE table.
d. Below the AIF_OPEN_INTERFACE tab in the content area on the right, click on the
Data tab.
e. Notice the first few columns of the table. For example, the columns display the batch
name (openint), year (2013), period (Jan), and an amount.
1.
2.
In FDMEE, create the import format, OpenInt, for the OPENINT source system, the
OPENINT2 source adapter, and the FLASH target application.
c. Under Details, in Name, enter OpenInt.
d. In the Source System list, select OPENINT.
e. In the Source Adapter list, select OPENINT2.
f. In the Target Application list, select FLASH.
g. Click Save to save the changes.
With the OpenInt import format selected in the summary area, the OpenInt:Mappings
area displays seven target dimension rows.
Select the source column mappings for the target dimensions.
a. In the OpenInt:Mappings area, in the Source Column 1 list for the Account target
dimension, select Account.
b. In the Source Column 1 list for the Custom3 target dimension, select C3.
c. Repeat step 2b to define the mappings in the following table:
d.
e.
f.
Source Column 1
Target Dimension
C4
Custom4
Dept
Department
Entity
Entity
ICP
ICP
ProdSal
ProdSal
In the Import Format Summary area, click Regenerate ODI Scenario to generate the
ODI Scenario based on the import format mappings.
At the success message, click OK.
Setting Up the Location and Data Load Rule

1.
2.
Create the OpenIntLoc location and assign the OpenInt import format to it.
b. Under Location, click Add.
c. Under the Details area, in Name, enter OpenIntLoc.
d. In Import Format, enter or select the OpenInt import format.
e. In Parent Location, enter or select Texas.
Navigate to the Data Load Rule page and set the POV to the OpenIntLoc location, Jan 2013 period, and FDMEE_ACTUAL category.
Chapter 14 - Page 6
3.
In the POV, click the location name and set the POV to the OpenIntLoc location, Jan
- 2013 period, and FDMEE_ACTUAL category.
Create the data load rule, OpenIntDR with the description Data load rule for open
interface table. Specify the GLcal calendar, the openint batch name, and do not delete
the data after the import.
b. In the Details area, enter OpenIntDR for the name.
c.
d.
e.
In Description, enter Data load rule for open interface table.

In Category, verify that FDMEE_ACTUAL is selected.
In Calendar, select GLcal.
f.
g.
h.
Under Source Filters, in Batch Name, enter openint.

In Delete Data After Import, enter N.
Importing Data from the Open Interface Table

1.
2.
Navigate to Data Load Workbench and verify that the POV is set to the OpenIntLoc
location, Jan - 2013 period, and the OpenIntDR data load rule.
b. Verify that the POV is set to the OpenIntLoc location, Jan - 2013 period,
FDMEE_ACTUAL category, and the OpenIntDR data load rule.
Import the data from the open interface table.
b. In the Execution Mode Option dialog box, verify that the Online execution mode is
selected, and click OK.
The data is imported from the open interface table to the OpenIntLoc location. The
following graphic displays some of the columns and data.
Chapter 14 - Page 7
b.
Chapter 14 - Page 8

Ag - Fdmee Material

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ag - Fdmee Material

Uploaded by

Copyright:

Available Formats

These eKit materials are to be used ONLY by you for the express purpose SELF STUDY.

SHARING THE FILE IS STRICTLY PROHIBITED.

Oracle University and (Oracle Corporation) use only.

Hyperion Financial Data

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 1: Product Orientation ............................................................................................ 1-1

Hyperion Financial Data Quality Management EE Administration Table of Contents

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 10: Reporting in FDMEE ......................................................................................... 10-1

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Hyperion Financial Data Quality Management EE Administration Table of Contents

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 9: Overview............................................................................................................. 9-2

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 1:

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 1: Overview

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Oracle University and (Oracle Corporation) use only.

Verify that all services are started.

On the Windows desktop, double-click Services

Practices for Lesson 1: Product Orientation

Oracle University and (Oracle Corporation) use only.

Practice 1-1: Starting Services

Oracle Hyperion Reporting and Analysis Framework (epmsystem1)

Oracle Process Manager (epmsystem1)

Oracle University and (Oracle Corporation) use only.

Close the Services window.

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Click on the Setup tab.

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Oracle University and (Oracle Corporation) use only.

Practice 1-2: Navigating in FDMEE

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Oracle University and (Oracle Corporation) use only.

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1: Product Orientation

Oracle University and (Oracle Corporation) use only.

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2: Preparing FDMEE Integrations

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 2:

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 2: Overview

Copyright 2014, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2: Preparing FDMEE Integrations

Creating the Application Root Folder

In System Settings, create the application folder in D:\CF\FDMEE.

Click Save to save the changes.

Registering the Target Application

Register the Financial Management target application, FLASH.

Practices for Lesson 2: Preparing FDMEE Integrations

Oracle University and (Oracle Corporation) use only.

Practice 2-1: Registering a Target Application