Académique Documents
Professionnel Documents
Culture Documents
Activity Guide
D83546GC10
Edition 1.0
March 2014
D85653
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
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Table of Contents
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 1
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Review the business scenario.
Start services.
Navigate in FDMEE.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a.
b.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
6.
Chapter 1 - Page 8
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Register a target application.
Review system settings.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
3.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 3
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
Build the import format mappings for the Texas_GL.txt file with the following guidelines:
Source Column
Description
Account
Amount
Custom3
Custom4
Department
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
Prod/Sal
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
1.
b.
c.
d.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
7 minutes
Use WordPad to review the location and delimiter of the columns in the
D:\CF\FilesLoc\Indiana\Indiana_GL.csv file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
b. In the Import Format Summary area, click Add.
A blank row is added to the grid.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
Build the import format mappings for the Indiana_GL.csv file with the following
guidelines:
Source Column
Description
Account
Amount
Entity
ICP
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 Expression, enter Sign=,CR to add the Sign expression to define all amounts with a
trailing CR as a credit balance.
In the Source Column for the Entity row, enter Entity.
In Field Number, enter 1 and enter the Expression value, Center.
i.
j.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
Add an Account Description mapping to the import format. The account description is in
the second column of the data file.
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 Field Number, enter 2.
Click Save to save your changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
6 minutes
Use WordPad to review the location and length of the columns in the
D:\CF\FilesLoc\Ohio\Ohio_MultiEnt.txt file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
b. In the Import Format Summary area, click Add.
A blank row is added to the grid.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
Add an import format with the detail listed in the following table:
Detail
Value
Name
OhioMulti
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Build the import format mappings for the Ohio_MultiEnt.txt file with the following
guidelines:
a.
Source Column
Description
Account
Amount
Department
Entity
ICP
Prod/Sal
b.
c.
In the Import Format Summary area, verify that the OhioMulti import format is
selected.
In Source Column for the Account target dimension, enter Account.
In Start, enter 9, and in Length, enter 15.
d.
e.
f.
In Expression, enter Sign=,CR to add the Sign expression to define all amounts with a
trailing CR as a credit balance.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
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
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 26 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 26, and in Length, enter 24.
Click Save to save your changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
4 minutes
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
5 minutes
Use WordPad to review the location and length of the columns in the
D:\CF\FilesLoc\Nevada\Nevada.txt file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
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
Nevada
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Build the import format mappings for the Nevada.txt file with the following guidelines:
Source Column
Description
Account
Amount
Entity
Entity is not included in the data file. In Start and Length, enter
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.
In the Source Column for the Amount row, enter Amount.
c.
d.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
1.
Start
Length
Account
11
Amount
46
31
Expression
Target
Account
DRCRSplit=16
Amount
Custom3
Custom4
Department
Entity
Nevada
Entity
ICP
ProdSal
2.
3.
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 14 and is 32 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 14, and in Length, enter 32.
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.
A blank row is added to the mapping grid.
b. In Source Column, enter Skip.
c.
4.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
5 minutes
Use WordPad to review the location and length of the columns in the
D:\CF\FilesLoc\UK\UK_TrialBal.txt file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
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
UK
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Build the import format mappings for the UK_TrialBal.txt file with the following
guidelines:
Source Column
Description
Account
Amount
Entity
Entity is not included in the data file. In Start and Length, enter
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.
In Source Column for the Account target dimension, enter Account.
In Start, enter 3, and in Length, enter 10.
d.
Start
Length
Expression
Target
Account
10
Fill=0000000000 Account
Amount
112
15
Fill=EuroToUS
Amount
Custom3
Custom4
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
1.
Department
1
UK
Entity
ICP
ProdSal
2.
3.
4.
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 14 and is 38 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 14, and in Length, enter 38.
Add a mapping to the import format to skip any row that has Page: starting at character
107.
a. In the Mappings area, click Add, and then select Skip Row.
A blank row is added to the mapping grid.
b. In Source Column, enter Skip.
c. In Start, enter 107, and in Length, enter 5.
d. In Expression, enter Page:.
Click Save to save your changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
7 minutes
Use WordPad to review the location and length of the columns in the
D:\CF\FilesLoc\Illinois\Illinios.txt file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
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
Illinois
Source System
File
File Type
Fixed
Target Application
FLASH
Description
Build the import format mappings for the Illinois.txt file with the following guidelines:
a.
b.
c.
Source Column
Description
Account
Account
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
Entity
In the Import Format Summary area, verify that the Illinois import format is selected.
In Source Column for the Account target dimension, enter Account.
In Start, enter 7, and in Length, enter 4.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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 Start, enter 1, and in Length, enter 1.
In Expression, enter - (hyphen).
Note: The Account rows will display in the order that you entered them after you save
the import format.
Continue to define the mappings as listed in the following table:
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 an Account Description mapping to the import format. The account description is in
the Description column of the data file. It begins at character 20 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 20, and in Length, enter 24.
Add a mapping row to skip any row that has a : (colon) starting at character 42.
a. In the Mappings area, click Add, and then select Skip Row.
A blank row is added to the mapping grid.
b. In Source Column, enter Skip.
c. In Start, enter 42, and in Length, enter 1.
d. In Expression, enter :(a colon).
Click Save to save your changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
5 minutes
Use WordPad to review the location and delimiter of the columns in the
D:\CF\FilesLoc\California\California.dat file.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
b. In the Import Format Summary area, click Add.
A blank row is added to the grid.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
Add an import format with the detail listed in the following table:
Detail
Value
Name
California
Source System
File
File Type
Delimited
File Delimiter
Comma
Target Application
FLASH
Description
California - Factor
Build the import format mappings for the California.dat file with the following
guidelines:
Source Column
Description
Account
Amount
Entity
a.
b.
In the Import Format Summary area, select the California import format.
In Source Column for the Account target dimension, enter Account.
c.
d.
Field Number
Account
Amount
Expression
Target
Account
Factor=.001
Amount
Custom3
Custom4
Department
Entity
Entity
ICP
ProdSal
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
Chapter 4
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Add locations.
Set up category and period mappings.
Set the POV.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
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.
A blank row is added to the grid.
c. Under Details, in Name, enter Texas.
d.
2.
Import Format
Indiana
Indiana
Nevada
Nevada
Ohio
OhioMulti
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
5 minutes
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.
Click Save to save the changes.
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.
A blank row is added to the grid.
c. In Period Key, enter or select 2/28/2014.
d.
e.
f.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
5 minutes
Tasks
1.
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 5
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Define member mappings.
Export and import mappings.
Share mappings.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
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.
3.
d.
4.
5.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
6.
7.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
15 minutes
Exporting Mappings
1.
2.
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.
Export the Account member mappings to the IN_Acct_map.txt file.
a.
b.
c.
3.
4.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
3.
4.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
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.
The Select a file to upload dialog box is displayed.
d. Click Browse, navigate to the D:\CF\FilesLoc\Indiana folder, select the
IN_All_Maps.txt file, click Open, and then OK.
The file name is displayed in the File area.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
d.
e.
5.
6.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
5 minutes
Tasks
1.
2.
3.
4.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 6
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Add and execute data load rules.
Load data to a range of periods.
Schedule a data load rule.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
9 minutes
2.
On the Data Load Rule page, set the POV to the Indiana location, Jan - 2013 period, and
FDMEE_ACTUAL category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
The Data Load Rule page is displayed.
b. In the POV bar, click the location name.
The Select Point of View dialog box 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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
5.
On the Data Load Rule page, set the POV to the Nevada location, Jan - 2013 period, and
FDMEE_ACTUAL category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
The Data Load Rule page is displayed.
b. In the POV bar, click the location name.
The Select Point of View dialog box is displayed.
c. In Location, enter or select Nevada.
d.
Verify that the Jan - 2013 period and FDMEE_ACTUAL category are selected, and
click OK.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
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.
a. Under Data Rule Summary, click Add.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
5.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
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.
a. On the Workflow tab, under Data Load, select Data Load Rule.
The Data Load Rule page is displayed.
b. In the POV bar, click the location name.
The Select Point of View dialog box is displayed.
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.
a. Under Data Rule Summary, click Add.
b. In Name, enter IN_Range.
c. In Description, enter Load data to a range of periods.
d.
e.
f.
g.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
5.
6.
7.
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.
The Select Point of View dialog box is displayed.
b. In Period, enter or select Jan 2013.
c. In Rule, enter or select IN_Actual, and click OK.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
8 minutes
Tasks
1.
2.
3.
On the Data Load Rule page, set the POV to the Indiana location, Jan - 2013 period, and
FDMEE_ACTUAL category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
The Data Load Rule page is displayed.
b. In the POV bar, click the location name.
The Select Point of View dialog box is displayed.
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.
a. On the Workflow tab, under Monitor, select 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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
Chapter 7
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Load data and fix validation errors.
Load data into multiple entities.
Drill through to FDMEE from the target application.
Load data to multiple periods.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
10 minutes
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.
On the Data Load Rule page, set the POV to the Texas location, Jan - 2013 period, and
FDMEE_Actual category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
b. In the POV bar, click the location name.
The Select Point of View dialog box is displayed.
c. In Location, enter or select Texas.
d.
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
h.
i.
3.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
d.
e.
f.
g.
b.
c.
5.
6.
In Data Load Workbench, validate the data to check for any additional errors.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
b. At the top of the page, click Validate.
The Execution Mode Option dialog box is displayed.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
7.
8.
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.
The Execution Mode Option dialog box is displayed.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
e.
3.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
4 minutes
On the Data Load Rule page, set the POV to the Ohio location, Jan - 2013 period, and
FDMEE_Actual category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
b. In the POV bar, click the location name.
The Select Point of View dialog box is displayed.
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.
h.
i.
j.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
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.
The Execution Mode Option dialog box is displayed.
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.
The Execution Mode Option dialog box is displayed.
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. The
data is loaded to the four target application entities.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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]
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
6 minutes
Tasks
1.
2.
On the Data Load Rule page, set the POV to the Texas location and the FDMEE_BUDGET
category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
The Data Load Rule page is displayed.
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.
a. Under Data Rule Summary, click Add.
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.
The Select a file to upload dialog box is displayed.
h.
i.
j.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
5.
6.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 8
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Create, assign, and verify check rules.
Create, assign, and verify check entities.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
18 minutes
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
#SubTitle
#ModeList
Sequence: 30
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
GR_PROFIT
NET_INC
g.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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],,,,,,,,,,,,,,,,|.
Attribute
#SubTitle
#ModeRule
Sequence: 80
OUT_OF_BALANCE_ACCT
a.
b.
c.
d.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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],,,,,,,,,,,,,,,,|
2.
On the Location page, assign the Region1 check rule group to the Texas location.
a. On the Setup tab, under Integration Setup, select Location.
The Location page is displayed.
b. Select the Texas location.
c. In the Texas:Details area, in Check Rule Group, enter or select Region1.
d. Click Save to save the changes.
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.
2.
In Data Load Workbench, set the POV to Texas, Jan - 2013, FDMEE_ACTUAL, and
TX_Actual.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
b. In the POV bar, click the location name.
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.
The Execution Mode Option dialog box is displayed.
b. In Export Mode, select Replace.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
e.
f.
d.
e.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
7 minutes
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.
d. Click Save to save the changes.
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
On Report
Sequence
10
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
c.
d.
e.
f.
2.
On the Location page, assign the Region1 check entity group to the Texas location.
a. On the Setup tab, under Integration Setup, select Location.
The Location page is displayed.
b. Select the Texas location.
c. In the Texas:Details area, in Check Entity Group, enter or select Region1.
Click Save to save the changes.
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.
The Execution Mode Option dialog box is displayed.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
b.
Chapter 9
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Create, execute, and schedule a batch.
Create and execute an open batch.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
10 minutes
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.
d. In the Target Application list, select FLASH.
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.
h. Click Save to save the changes.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
d.
e.
Repeat steps 3a through 3c to add the rule name, IN_Actual, with a sequence of 20.
Click Save to save the changes.
2.
3.
4.
Scheduling a Batch
Schedule the WK_TX_IN batch to run every Saturday at a time of your choice.
a. On the Workflow tab, under Other, select Batch Execution.
b. Select the WK_TX_IN batch.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
10 minutes
2.
3.
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.
d. In the Target Application list, select FLASH.
e. In the Type list, select Open Batch.
f. Accept the default Execution Mode of Serial.
g. In the File Name Separator list, select @.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
3.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
d.
Chapter 10
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Run predefined reports.
Review a demonstration on defining a custom report.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
7 minutes
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.
A prompt to open or save the file is displayed at the bottom of the page.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
3.
In the Report Output Format list, select PDF, and click OK.
A prompt to open or save the file is displayed at the bottom of the page.
f. Click Open.
The report is displayed in Adobe Reader.
Review the check rules in the check report for Texas.
Close the report.
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.
The Generate Report dialog box is displayed.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 10 - Page 6
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 11
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Define role-level security.
Add groups for location security.
Assign users to groups in Shared Services.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
5 minutes
Tasks
1.
2.
c.
Batch Execution
Report Execution
Process Details
User Settings
Click Save to save the changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
d. Click Save to save the changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
5 minutes
Tasks
1.
2.
3.
4.
5.
6.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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
2.
3.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
5.
6.
2.
3.
4.
5.
6.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
f.
Chapter 11 - Page 8
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 12
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
8 minutes
2.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
2.
b.
Navigate to Data Load Workbench and set the POV to Indiana, Jan - 2013,
FDMEE_ACTUAL, and IN_Actual.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
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.
The Execution Mode Option dialog box is displayed.
d. In the Import Mode list, select Replace.
e. In the Execution Mode list, verify that Online is selected.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
f.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
13 minutes
2.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
The Create Script Options dialog box is displayed.
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.
a. In the script content area, enter the following script:
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.
a. In the script content area, enter the following script:
b.
Click Save.
Create a comma delimited import format named NewYork for a File source system and
the FLASH target application.
a. On the Setup tab, under Integration Setup, select Import Format.
b. Under Import Format Summary, click Add.
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.
d. Click Save to save the changes.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
Define the import format mappings for the NewYork.csv file with the following guidelines:
Source Column
Description
Account
Amount
Account
Description
Entity
a.
b.
c.
d.
In the NewYork:Mappings area, in Source Column for the Account target dimension,
enter Account.
In Field Number, enter 1.
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.
Create the NewYork location and use the NewYork import format.
a. On the Setup tab, under Integration Setup, select Location.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
2.
2.
Navigate to Data Load Workbench and add the Description-1 column to the grid.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
b. Select View, then Columns, and then Manage Columns.
The Manage Columns dialog box is displayed.
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.
The Execution Mode Option dialog box is displayed.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
7 minutes
2.
b.
Click Save.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
2.
3.
Navigate to Data Load Workbench and add the Description-1 column to the grid.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
b. Select View, then Columns, and then Manage Columns.
The Manage Columns dialog box is displayed.
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.
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.
a. At the top of the page, click Import.
The Execution Mode Option dialog box is displayed.
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 into the NewYork location. The validation fails because member
mappings are not yet defined for the location.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
1.
Verify that data rows with an entity that begins with 100 are not included in the import.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
12 minutes
2.
c. Exit WordPad.
In FDMEE, create an import script, Get_Entity, 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 Get_Entity, and click OK.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
4.
5.
Enter the script to store the entity value into a temporary variable.
a. In the script content area, enter the following script:
b. Click Save.
Create an import script, Put_Entity, for the FLASH application.
a. In the Script Editor page, click New.
The Create Script Options dialog box is displayed.
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.
a. In the script content area, enter the following script:
b.
Click Save.
2.
Create a fixed import format named Georgia for a File source system and the FLASH
target application.
a. On the Setup tab, under Integration Setup, select Import Format.
b. Under Import Format Summary, click Add.
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.
d. Click Save to save the changes.
Define the import format mappings for the Georgia.txt file with the following guidelines:
Source Column
Description
Account
Amount
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3.
Entity
a.
In the Georgia:Mappings area, in Source Column for the Account target dimension,
enter Account.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
2.
Create the Georgia location and use the Georgia import format.
a. On the Setup tab, under Integration Setup, select Location.
b. In the Location area, click Add.
c. Under Details, in Name, enter Georgia.
d. In the Import Format list, click Search
.
e. Select Georgia, and click OK.
f. Click Save to save the changes.
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.
a. On the Workflow tab, under Data Load, select Data Load Rule.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
In the Category list, select FDMEE_ACTUAL.
In File Name, click Select.
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.
2.
3.
Navigate to Data Load Workbench and add the Description-1 column to the grid.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
b. Select View, then Columns, and then Manage Columns.
The Manage Columns dialog box is displayed.
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 Georgia location.
a. At the top of the page, click Import.
The Execution Mode Option dialog box is displayed.
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 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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
b.
Chapter 12 - Page 18
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 13
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Set up a mapping script.
Create an event script.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
You should be logged on to FDMEE as user admin with the password hyperion.
Time
8 minutes
2.
In Data Load Workbench, set the POV to the Texas location, Jan - 2013 period,
FDMEE_ACTUAL category, and TX_Actual rule.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
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.
In the Data Load Mapping page, review the Between mapping for the source ICP members
1940-101 through 1940-105.
a. On the Workflow tab, under Data Load, select Data Load Mapping.
The Data Load Mapping page is displayed.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
2.
Ends in 102
Ends in 103
Ends in 104
a.
For the 1940-101,1940-105 source value, change the target value, [ICP None], to
#SCRIPT, and then press Tab.
b.
c.
d.
e.
Click OK.
Click Save to save the changes.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
b. At the top of the page, click Validate.
The Execution Mode Option dialog box is displayed.
c. In the Execution Mode list, verify that Online is selected, and click OK.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
12 minutes
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.
a. In the FDMEE folder on the Windows desktop, launch WordPad.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
b. Under Import Format Summary, click Add.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
d.
3.
Define the import format mappings for the IowaBal.txt file with the following guidelines:
Source Column
Description
Account
Amount
Account
Description
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.
Click Save to save the changes.
b.
In the Iowa:Mappings area, in Source Column for the Account target dimension, enter
Account.
In Start, enter 1, and in Length, enter 15.
c.
d.
e.
f.
g.
h.
i.
j.
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.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
c.
Source Column
Description
Account
Amount
Account
Description
Entity
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 Source Column for the Entity row, enter Entity.
In Field Number, enter 1, and in Expression, enter Inc.
In the Mappings area, click Add, and then select Description Row.
In Source Column of the Description 1 row, enter Account Description.
h.
i.
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.
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. In the Event folder, select the BefImport script name.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
5.
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.
Create the Iowa location and use Iowa_Bal as the default import format.
a. On the Setup tab, under Integration Setup, select Location.
b. In the Location area, click Add.
c. Under Details, in Name, enter Iowa.
d.
e.
f.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
e.
Create the IowaAct data load rule. Set up the data load rule to prompt for the data load file.
a. On the Workflow tab, under Data Load, select Data Load Rule.
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.
2.
Navigate to Data Load Workbench and, optionally, add the Description-1 column to the
grid.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
b. Select View, then Columns, and then Manage Columns.
The Manage Columns dialog box is displayed.
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 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.
a. At the top of the page, click Import.
The Execution Mode Option dialog box is displayed.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. At the top of the page, click Import.
The Execution Mode Option dialog box is displayed.
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.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
i.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Chapter 14
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 1
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices Overview
In these practices, you perform the following tasks:
Review a demonstration on integrating GL data in FDMEE.
Load source data from the open interface table.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
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.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 3
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
For FDMEE tasks, you should be logged on as user admin with the password hyperion.
Time
12 minutes
2.
3.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 4
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 5
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. On the Setup tab, under Integration Setup, select Import Format.
b. Under Import Format Summary, click Add.
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.
Click Save to save the changes.
2.
Create the OpenIntLoc location and assign the OpenInt import format to it.
a. On the Setup tab, under Integration Setup, select Location.
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.
f. Click Save to save the changes.
Navigate to the Data Load Rule page and set the POV to the OpenIntLoc location, Jan 2013 period, and FDMEE_ACTUAL category.
a. On the Workflow tab, under Data Load, select Data Load Rule.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 6
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
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.
a. Under Data Rule Summary, click Add.
b. In the Details area, enter OpenIntDR for the name.
c.
d.
e.
f.
g.
h.
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.
a. On the Workflow tab, under Data Load, select Data Load Workbench.
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.
a. At the top of the page, click Import.
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.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 7
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
b.
Practices for Lesson 14: FDMEE Integration with Other Source Systems
Chapter 14 - Page 8
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.