FDM Study Material

Oracle Hyperion Financial Data
Quality Management 11.1.2

Administration
Volume II Student Guide
D69377GC10
Edition 1.0
May 2011
D73203
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Copyright 2011, Oracle. All rights reserved.
Disclaimer
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 Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.
Author
Lea Jensen
Technical Contributors
and Reviewers
Philip Attea
Mike Casey
Jeffrey Jones
Todd Newman
Sergiy Pecherskyy
Shawn Stalker
Martin Toma
Michael Van Der Merwe
Stuart Weiner
Editor
Susan Moxley
Graphic Designer
Lea Jensen
Publisher
Lea Jensen
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D

Preface 0
Welcome to Financial Data Quality Management 11.1.2 Administration.
Before you begin, please take a moment to review this section. The
preface presents an overview of the following information:
Course objectives
Structure of the course
Course materials used in the class
Conventions used in the book
Additional resources to enhance your learning
Relevant follow-up courses that you might want to attend
Course Objectives
After completing this course, you should be able to:
Create FDM applications
Integrate FDM applications with target applications from disparate
systems
Import mappings
Create import formats for source applications
Create validation rules and entities
Load data to target systems
Apply financial controls to comply with Sarbanes-Oxley legislation
Set up user and object security
Create scripts
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Preface
iv Financial Data Quality Management 11.1.2 Administration
Course Structure
Financial Data Quality Management 11.1.2 Administration is a 3-day, instructor-led
training course consisting of lectures, demonstrations, and hands-on exercises. In this
course, the instructor presents a topic and guides you through the exercises.
Demonstrations and hands-on exercises reinforce the concepts and skills introduced
during lectures.
Course Materials
You use two books in classthe student guide and the activity guide. The instructor may
also give you handouts.
Student Guide
The student guide contains lessons. Each lesson begins with a list of objectives followed
by the presentation of slides and accompanying text. The lesson ends with a summary of
the topics covered in the lesson.
The student guide contains appendices of material related to the course.
Activity Guide
The activity guide has two sectionsexercises and exercise solutions.
ExercisesA critical part of the learning process is the challenge of completing real
tasks associated with each lesson. Each exercise is an opportunity to apply your
knowledge.
Exercise SolutionsThe exercise solutions present the detailed steps to complete
the exercises.
Conventions
The following text conventions are used in this course book:
Text to be entered, options to be selected, names of files and modules, and menu
selections are displayed in bold type. Examples:
- Select Clear Profile.
- Click YES to clear the profile.
When available, figures are used to identify an object or task. Example:
Click Edit .
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Preface
Financial Data Quality Management 11.1.2 Administration v
Keyboard shortcuts are displayed as follows: Click OK or press Alt+O.
Alerts are used to direct your attention to different types of information.
NOTE: A note provides related information, common mistakes, or cautions
about the current topic.
TIP: A tip provides information that helps you work more efficiently.
Additional Resources
Use the following resources to enhance your learning:
Oracle Hyperion Financial Data Quality Management, Fusion Edition Release
11.1.2.1 Readme (fdm_11121_readme.pdf)
11.1.2.1 Configuration Guide (fdm_config.pdf)
11.1.2.1 Administrators Guide (fdm_admin.pdf)
11.1.2.1 DBA Guide (fdm_dba.pdf)
11.1.2.1 API Object Guide (fdm_api.pdf)
Oracle provides the following user assistance with Enterprise Performance Management
products:
Context-sensitive helpClick Help for context-sensitive help.
Help menuFrom the Help menu in the software, access screen-level help, general
product help, technical support, EPM documentation, oracle.com, and optionally
Oracle User Productivity Kit.
My Oracle SupportAccess release-specific Readme files.
E-DeliveryAccess release-specific installation documentation before downloading
software.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Preface
vi Financial Data Quality Management 11.1.2 Administration
Oracle Technology NetworkExplore product documentation, get started with
Java, PHP, Linux, and other industry-standard technologies, download free software,
and read technical articles and notes authored by OTN members. You can also join
discussion forums to request advice from Oracle engineers and other OTN
members; listen to podcast interviews with Oracle engineers, customers, and
partners; bookmark Technology and Developer Centers devoted to your area of
interest; and subscribe to Developer e-mail newsletters.
OTN Documentation LibraryDownload documentation for all Enterprise
Performance Management products, including reference information and PDF and
HTML versions of each deliverable.
Related Courses
The following courses are available:
Financial Data Quality Management ERP Integrator Module Overview (online
tutorial)
NOTE: Course names and learner paths may change. Visit
www.oracle.com/education for the latest information.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D

Table of Contents 0
Preface
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Activity Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Courses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Lesson 1: Product Orientation
Oracles Enterprise Performance Management System . . . . . . . . . . . . . . . . . . . . . . . 1-2
Information Delivery Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
EPM and BI Applications Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
BI Foundation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
FDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Benefits of FDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Features of FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Processing Data Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Source Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Validation of Dimension Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Mapping Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Target System Data Loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Lesson 2: Navigating FDM
Accessing FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Accessing Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Workbench Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Accessing the FDM Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
FDM Web Client Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Working with the POV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
viii Financial Data Quality Management 11.1.2 Administration
Rules That Determine the Default POV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Changing the POV Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Changing the POV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Searching for POV Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Locking Out Users for Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Running Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Process Monitor Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Changing Report and Group Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Viewing Graphical Timelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Viewing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Changing the Timeline Viewer Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Lesson 3: Creating FDM Applications
About FDM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Application-Building Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Creating Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Directory Structure of Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Managing Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Modifying Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Removing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Adding Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Lesson 4: Integrating Applications
Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Importing Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Adapter Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Source System Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Target System Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Modifying Dimension Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Registering Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Configuring Financial Management Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Adding Machine Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Configuring Integration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Application Name Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Logon Method Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
Financial Data Quality Management 11.1.2 Administration ix
Global Logon Information Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Integrating Hyperion Enterprise Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Associating Dimensions Between Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Testing Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Setting Up Standard Reports and Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Setting Up Standard Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Setting Up Standard Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Lesson 5: Setting Up Control Tables and Locations
Viewing Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Managing Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Managing Control Tables with Excel Worksheets . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Viewing Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Managing Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Setting Location Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Setting General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Setting Workflow Behaviors Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Setting Financial Controls Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Setting Integration Options Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Searching Control Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Lesson 6: Setting Up Mapping Tables
Mapping Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Activating Map Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Assigning Dimension Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Opening Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Building Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Map Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Explicit Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Rules-Based Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Wildcard Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Processing Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Processing Order in Multiple Mapping Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Processing Order in the Same Mapping Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Building Maps Externally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Building Maps with MapLoader Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
x Financial Data Quality Management 11.1.2 Administration
Importing Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Importing Maps from Hyperion LedgerLink Files . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Importing Maps from Hyperion Enterprise Files. . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Copying Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Sharing Dimension Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
Setting Up Conditional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33
VarValues Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
Conditional Mapping Script Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
Conditional Mapping Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . 6-36
Lesson 7: Building Import Formats
About Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Creating Import Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Creating Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Creating Import Formats with Import Format Builder. . . . . . . . . . . . . . . . . . . . . . . 7-7
Fixed Import Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Delimited Import Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Building Import Formats for ERP Integrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Skipping Lines in Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Concatenating Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Assigning Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Adding Import Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Sign Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
DRCRSplit Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Fill and Fill=EuroToUS Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Fill and Fill=EuroToUS Expressions: Example. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
FillL Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Factor Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
NZP Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Expression Stacking and Processing Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Lesson 8: Loading Data
About Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Importing Source Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Working with Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Sorting Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Finding Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Filtering Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
Financial Data Quality Management 11.1.2 Administration xi
Deleting Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Validating Dimension Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Validation Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Fixing Validation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Intersection Validation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Loading Data to Target Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Drilling Up on Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Displaying Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Displaying Conversion Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Displaying Archive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
Displaying Source Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Displaying Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Displaying Processing Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Restoring Source Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28
Drilling Down on Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Drilling Up on a Drilldown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
Drilling Through to FDM from Target Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Drilling Through from Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
Drilling Through from Essbase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Drilling Through from Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Drilling Through from Strategic Finance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
Lesson 9: Building Validation Rules
About Validation Rules and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Creating Validation Rule Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Creating Validation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Selecting Display Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Defining Rule Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Adding Rule Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Creating Validation Rules in Validation Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Adding Rules and Display Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Looking Up Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Testing Rules and Display Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Assigning Validation Rules to Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Checking Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Lesson 10: Setting Up Validation Entities
About Validation Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
xii Financial Data Quality Management 11.1.2 Administration
Creating Validation Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Creating Validation Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Assigning Validation Entity Groups to Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Verifying Consolidations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Lesson 11: Processing Batch Files
About Batch Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
Enabling Batch Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
Setting Up Batch-Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5
Processing Batch-Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
Batch Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
Batch Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-9
Creating Batch Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10
Scheduling Batch Scripts in Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-12
Lesson 12: Creating Logic Accounts
About Logic Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Creating Logic Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Creating Simple Logic Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Selecting Source Accounts for Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Grouping Accounts by Source Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-11
Selecting Operators and Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Retrieving Source Account Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
Assigning Function Return Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Simple Logic Function Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Creating Logic Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Creating Complex Logic Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Applying Criteria Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Complex Logic Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
Complex Logic Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
Assigning Logic Groups to Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
Lesson 13: Loading FDM Journals
About FDM Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Creating Journal Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Adding Metadata Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Load Method Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
Financial Data Quality Management 11.1.2 Administration xiii
Dimension Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Loading Journal Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Checking In Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Posting Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Lesson 14: Loading Data with Multiload Files
About Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Creating Multiload Excel Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Adding Metadata Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Adding Load Control Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Adding Dimension Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Creating Multiload Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Loading Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Checking In Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19
Executing Workflow Tasks for Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Viewing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Lesson 15: Setting Up Security
About FDM Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
About Object Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Setting Up Object Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
About User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Setting Up User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Adding Authentication Providers for FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Provisioning Users in Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Adding Users to FDM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Modifying User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17
Locking and Unlocking the Local POV Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
Setting Up Report Group Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19
Lesson 16: Working with Financial Controls
About Financial Controls in FDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Creating Controls Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Adding Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Adding Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
xiv Financial Data Quality Management 11.1.2 Administration
Setting an Effective Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Creating Question Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Importing Questions from Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Deleting Controls Groups, Sections, or Questions . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
Restoring Controls Groups, Sections, or Questions . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Assigning Reviewer, Submitter, and Proxy Rights. . . . . . . . . . . . . . . . . . . . . . . . . . 16-16
Assigning Reviewers and Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-17
Assigning Submitters and Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
Assigning Risk Levels to Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20
Accessing Financial Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-22
Adding Memos and Attaching Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . 16-23
Reviewing and Submitting Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-28
Selecting Application Settings for Financial Controls. . . . . . . . . . . . . . . . . . . . . . . . 16-30
Lesson 17: Working with Import Scripts
About Scripting in FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
Working with Scripting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Accessing Script Editor in the FDM Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Accessing Script Editor in Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Accessing Accelerators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Creating Import Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Import Script Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Creating Import Scripts in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Creating Import Scripts: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-11
Assigning Import Scripts to Import Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Applying Scripting Functions to Import Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Applying the Left Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Applying the Right Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Applying the Mid Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Applying the fParseString Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Applying the RES.PblnSkip Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Applying the RES.PblnSkip Function: Example. . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Working with Temporary Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Assigning Temporary Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Importing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
Manually Executing Custom Web Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
Financial Data Quality Management 11.1.2 Administration xv
Lesson 18: Working with Import Integration Scripts
About Import Integration Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Import Integration Script Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Population of FDM Table Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Creating Import Integration Scripts in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Creating Import Integration Scripts: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Creating Import Integration Scripts: Example (cont.) . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Assigning Import Integration Scripts to Import Formats. . . . . . . . . . . . . . . . . . . . . . 18-10
Lesson 19: Working with Event Scripts
About Event Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Types of Event Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
ImportAction Subevents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Event Script Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Creating Event Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Changing Import Formats Dynamically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Changing Import Formats Dynamically: Example . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Changing Other Location Attributes Dynamically . . . . . . . . . . . . . . . . . . . . . . . 19-10
Appendix A: Setting Up Multilanguage Support
About Multilanguage Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Changing Language Settings in FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Changing Browser Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Setting Decimal Formatting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Creating Reports for Multiple Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Translating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Selecting Validation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Appendix B: ERP Integrator
About ERP Integrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
ERP Integrator Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
ERP Integrator Architecture: Loading Metadata and Data. . . . . . . . . . . . . . . . . . . B-6
ERP Integrator Architecture: Drilling Through and Writing Back Budget Data . . . B-8
Security in ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
ERP Integrator User Interface Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Table of Contents
xvi Financial Data Quality Management 11.1.2 Administration
Accessing ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Extracting GL Metadata and Data: Configuring ERP Integrator . . . . . . . . . . . . . . . . B-16
Registering ERP Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Enabling FDM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21
Registering EPM Target Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
Selecting Source Accounting Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24
Extracting GL Metadata and Data: Setting Up ERP Integrator . . . . . . . . . . . . . . . . . B-26
Creating Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
Defining Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Defining Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-31
Defining Period Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35
Defining Category Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37
Defining Data Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39
Drilling Through to View Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44
Drilling Through from Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . B-46
Drilling Through from Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47
Drilling Through from Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-48
Drilling Through from Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-49
Drilling Through from the ERP Integrator Landing Page . . . . . . . . . . . . . . . . . . . B-50
Drilling Through from the E-Business Suite Landing Page . . . . . . . . . . . . . . . . . B-51
Drilling Through from the PeopleSoft Landing Page . . . . . . . . . . . . . . . . . . . . . . B-52
Writing Back Budget Data from EPM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . B-53
Configuring and Setting Up ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54
Creating Write-Back Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54
Creating Data Write-Back Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-55
Executing Data Write-Back Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-56
Loading Data into the ERP Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-57
Managing Data Write-Back Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-58
Extracting HR Metadata and Data from PeopleSoft HCM. . . . . . . . . . . . . . . . . . . . . B-59
Configuring and Setting Up ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-60
Creating HR Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-60
Executing HR Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-63
Managing HR Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-65
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 2

Creating Logic Accounts 12
Objectives
At the end of this lesson, you should be able to:
Describe logic accounts
Create logic groups
Create simple logic accounts
Create complex logic accounts
Assign logic groups to locations
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 12 Creating Logic Accounts
12-2 Financial Data Quality Management 11.1.2 Administration
About Logic Accounts
You create logic accounts to calculate data values that are not provided in the source
data files. When you associate logic accounts with data locations, FDM generates the
logic accounts and their values when you import the source data to the locations. Just
like source accounts, you can map and load logic accounts to target systems.
You typically use logic accounts for the following tasks:
Statistical loadingMap a source account to multiple target accounts
Conditional mappingMap source accounts based on their values
Arithmetic mappingPerform arithmetic operations on source values
Because you create logic accounts in FDM, detailed audit trails for the logic account
values are not available.
Copyri ght 2011, Oracl e and/or its affi liates. All rights reserved.
About Logic Accounts
Account Entity ICP Amount
1150 TX 07 50,500
1176 TX 04 10,000
1222 TX 04 9,500
Set up logic account L1100 for the
Texas location to summarize source
accounts that begin with 11.
Import source data records
for the Texas location.
FDM creates logic account
L1100 with a total amount
of 60,500, and displays the
account in the Import
window.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Financial Data Quality Management 11.1.2 Administration 12-3
You perform the following tasks to set up logic accounts for locations:
1. Create logic groups.
2. Define the logic accounts for each group.
3. Assign the logic groups to data-load locations.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Logic Groups
You create logic groups to hold logic accounts that you want to calculate for data-load
locations. You define logic groups as simple or complex.
Simple logic groups contain logic accounts that derive their values only from source
accounts. For example, you can total the values of multiple source accounts into one
logic account. FDM calculates the simple logic accounts for all dimensions.
Complex logic groups contain logic accounts that derive their values from any
combination of dimensions. For example, you can calculate logic accounts for specific
centers, time periods, and categories.
The Logic Groups window contains two tables. The top table displays the list of logic
groups, and the bottom table displays the logic accounts for the selected logic group.
The attributes for the logic accounts in the bottom table vary depending on the type of
logic group, simple or complex.
Creating Logic Groups
Add a logic group.
Types of logic groups
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
FDM administrators can view and modify all logic groups and logic accounts. FDM end
users can view and modify only the logic groups and accounts that they created, and
only if the administrator changes object security to allow end users to open the Logic
Groups window.
To create logic groups:
1. In the FDM Web client, select MetaData, and then Logic Groups.
The Logic Groups window displays a logic group table at the top
of the window.
2. In the logic group table, click Add.
A row is added to the logic group table.
3. In the Logic Group column, enter the logic group name.
4. Optional: In the Description column, enter a description for the logic group.
5. In the Logic Type column, select Simple Logic or Complex Logic.
6. Click Update Grid to save the changes.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Simple Logic Accounts
After creating a simple logic group, you define the logic accounts for the logic group in
the bottom table of the Logic Groups window. Each row in this table represents logic
accounts that you want to calculate based only on source accounts.
When you import source data, FDM generates the logic accounts and displays their
names in the Account column of the Import window. You should precede logic account
names with a character, such as an L, to distinguish the logic accounts from the source
accounts. If you intend to load the logic account values to target systems, you must map
the logic account names to valid target accounts.
Creating Simple Logic Accounts
Simple
logic
group
Enter the logic account name, or select Zoom
to enter the account name in Zoom Editor.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For simple logic accounts, you can define the attributes described in the following table:
NOTE: Later topics in this lesson contain more information about the Type, Criteria
Value, Operator, and Value/Exp attributes.
To create simple logic accounts:
The Logic Groups window is displayed.
2. Select a simple logic group from the logic group table.
The table for the logic accounts of the selected logic group is
displayed at the bottom of the window.
3. In the bottom table, click Add.
A row is added to the bottom table.
4. In the Item column, enter the logic account name.
Attribute Description
Item Logic account name. FDM displays the name in the Account column of
the Import window.
Description Logic account description. FDM displays the description in the Account
Description column of the Import window.
Type Operator (Between, In, or Like) that works with the Criteria Value attribute
to determine the source accounts for the logic account calculation.
Criteria Value Criteria that work with the Type attribute to determine the source accounts
for the logic account calculation.
Operator Operator (NA, +, -, x, /, Exp, or Function) that works with the Value/Exp
attribute to perform calculations and derive the logic account values.
Value/Exp Value or logic expression that works with the Operator attribute to perform
calculations and derive the logic account values.
Seq Sequence in which FDM processes the logic account calculations. The
order allows FDM to use one logic account to calculate other logic
accounts, as long as FDM first calculates the dependent account.
Exp On-off switch that determines whether you must map the logic account to
a target account so that FDM can export the logic account to the target
system.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
5. In the Description, Type, Criteria Value, Operator, Value/Exp, Seq, and Exp columns,
enter or select the logic account attributes.
6. In the bottom table, click Update Grid to save the changes.
7. Repeat steps 3 through 6 for each logic account that you want to create in the simple
logic group.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Selecting Source Accounts for Calculations
You can derive a logic account value from multiple source accounts. The logic account
Type and Criteria Value attributes work in tandem to select the source accounts that
FDM processes to derive the logic account value.
For the Type attribute, you select the operatorBetween, In, or Like. In the Criteria Value
attribute, you specify the source account names.
Type Description
Between Specifies a range of source accounts. In the Criteria Value attribute, separate
the two source accounts with a comma.
In Includes a single source account or a list of nonsequential source accounts.
In the Criteria Value attribute, separate the list of source accounts with
commas.
Like Specifies multiple source accounts with wildcards. Use the question mark (?)
wildcard as a placeholder for one character and the asterisk (*) wildcard as a
placeholder for any number of characters.
Selecting Source Accounts for Calculations
Type Criteria Value Selected Source Accounts
Between 1000, 1999
Range of accounts between account 1000 and
account 1999
In 1031 Single account 1031
In 1017, 1028, 1215 Accounts 1017, 1028, and 1215
Like 25??
Accounts that begin with 25 followed by two
characters
Like 10*
Accounts that begin with 10 followed by any
number of characters
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Sample selections of source accounts are described in the following table:
Type Criteria Value Selected Source Accounts
Between 1000, 1999 Range of accounts between account 1000 and
account 1999
In 1031 Single account 1031
In 1017, 1028, 1215 Accounts 1017, 1028, and 1215
Like 25?? Accounts that begin with 25 followed by two
characters
Like 10* Accounts that begin with 10 followed by any
number of characters
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Grouping Accounts by Source Locations
By default, when the source data file includes multiple source locations, FDM creates
separate logic accounts for each location. For the first example in the slide (12300), FDM
creates logic account 12300 for each source location in the source data file.
You can create a logic account that summarizes multiple source locations by placing a
semicolon after the account and entering a number that corresponds to the number of
characters in the location that you want to group by. For the second example in the slide
(12300;3), FDM creates a summarized logic account that includes all source locations
that have the same first three characters. FDM assigns these characters to the location
of this logic account. If you have locations 32520 and 32540 in the source data file, FDM
assigns 325 to the location of the logic account.
Grouping Accounts by Source Locations
Criteria Value Result
12300
FDM creates a logic account for each source location that FDM
finds in the source data file.
12300;3
FDM creates a summarized logic account that includes all
source locations that have the same first three characters.
12300;3,4
source locations that have the same three characters in the
source location, starting at position 4.
12300;Dept100
source locations. FDM assigns the Dept100 location to this
summarized logic account.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You can group multiple source locations that have the same characters starting at a
specified position in the location name. For the third example in the slide (12300;3,4),
FDM creates a summarized logic account that includes all source locations that have the
same three characters in the source location, starting at position 4. If you have locations
10-325-17 and 10-325-22, FDM assigns location 325 to the logic account.
You can create a logic account that summarizes all source locations from the source
data file. When you place a semicolon after the source account and enter a text value,
FDM assigns this value to the location of the summarized logic account. For the last
example in the slide (12300;Dept100), FDM creates a summarized logic account that
includes all source locations, and assigns the Dept100 location to the summarized logic
account.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Selecting Operators and Values
The operator that you select in the Operator column works in tandem with the value in
the Value/Exp column to perform calculations and derive values for the logic accounts.
For example, you can multiply source account values by a decimal value.
You can select the following operators for logic account calculations:
Operator Description
NA Operator that performs no calculation
+ Numeric operator to perform addition
- Numeric operator to perform subtraction
x Numeric operator to perform multiplication
/ Numeric operator to perform division
Selecting Operators and Values
Select the
operator.
Enter the value,
logic expression,
or logic function.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
When you select a numeric operator, you must enter a numeric value in the Value/Exp
column for the operator to calculate on. With the NA operator, you do not specify a value
in the Value/Exp column, and FDM totals the values of the source accounts that are
listed in the Criteria Value column.
NOTE: Later topics in this lesson contain information about the Function and Exp
operators.
Exp Operator that executes a logic expression which you
define in the Value/Exp column
Function Operator that executes a logic function that you define
in the Value/Exp column
Operator Description
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Retrieving Source Account Values
The Lookup function retrieves source account values from FDM. You can use the Lookup
function in logic functions and logic expressions.
You place the parameters of the Lookup function within pipes ( | | ). The syntax for the
Lookup function is the following:
|source location, FDM category key, FDM period, source account|
Examples for retrieving source account values are described in the following table:
Syntax Result
|810| Retrieves the value of source account 810 for the current
source location, FDM category, and period.
Retrieving Source Account Values
To retrieve the source account value for source location 325,
FDM category key 13, FDM period 12/31/2010, and source
account 1028, enter the syntax
|325,13,12/31/10,1028|.
To retrieve the source account value for the current source
location, the FDM category key 14, the current FDM period,
and the source account 1215, enter the syntax
|,14,,1215|.
FDM
category
keys
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
|325,13,12/31/10,1028| Retrieves the value of source account 1028 for source location
325, FDM category key 13, and FDM period 12/31/2010.
|,14,,1215| Retrieves the value of source account 1215 for the current
source location, the FDM category key 14, and the current FDM
period.
Syntax Result
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Function Return Values
The Function operator executes a logic function that you define in the Value/Exp column.
You typically use logic functions for conditional mapping and complex operations that
involve multiple source accounts. Logic functions enable you to use If statements for
conditional mapping and also enable the use of variables. You can use Lookup functions
within logic functions to retrieve the value of source accounts.
You can use the parameters described in the following table in logic functions:
Parameter Description
CurVal Value assigned from the source accounts to the logic account
strLocation Current FDM location in the POV
strCenter Current source location from the source data file
strCatKey Category key of the current FDM category in the POV
strPerKey Current FDM period in the POV
Assigning Function Return Values
Select the
Function operator.
Define a logic
function.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You must assign the result of a logic function to the keyword Result. For example, you
can look up the value of account 810, multiply the value by .5, and add it to the current
value of the source account by entering the following syntax:
Result = CurVal + (|810| * .5)
If the logic account calculation results in no return value, FDM assigns a 0 value to the
Result keyword. In this case, FDM skips the calculation and does not create a logic
account for the source location.
Review the logic function examples in the following table:
For the first example in the table, FDM retrieves the value of account 1100-104 from the
data file and assigns it to the CurVal parameter. If the value is greater than 0, FDM
assigns the value to logic account L1100-104A. If the value is less than 0, FDM skips the
record and does not create the logic account.
For the second example in the table, FDM retrieves the value of account 1100-104 from
the data file and assigns it to the CurVal parameter. If the value is less than 0, FDM
assigns the value to logic account L1100-104L. If the value is greater than 0, FDM skips
the record and does not create the logic account.
Item Description Type Criteria Value Operator Value/Exp
L1100-104A Cash_FNB In 1100-104 Function If CurVal > 0 Then
Result = CurVal Else
Result = Skip End If
L1100-104L STLiab_FIB In 1100-104 Function If CurVal < 0 Then
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Simple Logic Function Examples
Review the logic function examples described in the following table:
Operator Value/Exp Result
Function If strCatKey=14 Then
When 14 is the category key of the FDM
category POV, FDM assigns the current
values of the source accounts to the logic
account.
Function If strCenter=325 Then
Result = CurVal * 100 Else
When 325 is the current location in the
data file, FDM assigns the result of the
calculation (CurVal*100) to the logic
account.
Simple Logic Function Examples
Operator Value/Exp
Function
If strCatKey=14 Then Result = CurVal Else
Function
If strCenter=325 Then Result = CurVal * 100 Else
Function
If strPerKey=12/31/2010 Then Result = CurVal + |4000-100|
Else Result = Skip End If
Function
If strLocation=Texas Then
Result = CurVal + |325, 14, 09/30/2010, 1540|
Logic functions containing the strCatKey,
strCenter, strPerKey, and strLocation parameters
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Function If strPerKey=12/31/2010 Then
Result = CurVal+|4000-100| Else
When December 2010 is the current FDM
period POV, FDM assigns the result of the
calculation (CurVal+|4000-100|) to the
logic account.
Function If strLocation=Texas Then Result =
CurVal+|325, 14, 09/30/2010, 1540|
When Texas is the current FDM location
POV, FDM adds a source account from a
different source location, FDM category,
and FDM period to the current values of
the logic account.
Operator Value/Exp Result
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Logic Expressions
The Exp operator executes a logic expression that you define in the Value/Exp column.
Logic expressions are simpler than logic functions and are executed faster than logic
functions. You cannot include If statements or variables in logic expressions.
Logic expressions contain one parameter, CurVal, which you must enclose in pipes. You
do not need to assign the value of the expressions to the Result keyword, as you do in
logic functions.
Review the logic expression examples described in the following table:
Operator Value/Exp Lookup Function Result
Exp |CurVal| + |810| + |238| Retrieves the values of accounts 810 and 238, and
adds the values to the current logic account value.
Exp (|CurVal| + |325, 14,
12/31/10, 1630|) * 100
Adds a source account (1630) from a different
location, FDM category, and FDM period to the
current logic account value, and multiplies the result
by 100.
Creating Logic Expressions
Example Operator Value/Exp
1 Exp |Curval| + |810| + |238|
2 Exp (|Curval| + |325, 14, 12/31/2010, 1630|) * 100
Select the
Exp operator.
Type the custom
logic expression.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Complex Logic Accounts
After creating a complex logic group, you define the logic accounts for the group in the
bottom table of the Logic Groups window. Each row in this table represents logic
accounts that you want to calculate based on values from any combination of
dimensions.
The attributes for complex logic accounts are the same as those for simple logic
accounts, except for the Criteria Value attribute and the Include Calc attribute.
FDM processes logic account calculations by the sequence order. With the Include Calc
attribute, you can include previously calculated FDM values in the logic account
calculation, provided that the previously calculated values meet the logic account criteria.
Creating Complex Logic Accounts
Complex
logic
group
Enter the logic account name, or click Zoom
to enter the account name in Zoom Editor.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
To create complex logic accounts:
The Logic Groups window is displayed.
2. In the logic group table, select a complex logic group.
The table for the logic accounts of the selected complex logic
group is displayed at the bottom of the window.
A row is added to the bottom table.
4. In the Item column, enter the logic account name.
5. In the Description column, enter the description for the logic account.
7. In the Criteria Value column, click the arrow.
The Complex Logic Criteria Account dialog box is displayed.
8. Perform the following actions:
a. Click Add.
A row is added to the criteria table.
b. Double-click in the Dimension column, and select a dimension name.
c. In the Criteria Type, Criteria Value, Group By, and Group Level columns, enter or
select the logic criteria attributes.
d. Click Update Grid to save the changes.
e. Select File, and then Close to return to the Logic Group window.
9. In the Criteria Value, Operator, Value/Exp, Include Calc, Seq, and Exp columns,
enter or select the logic account attributes.
11. Repeat steps 3 through 10 for each logic account that you want to create in the
complex logic group.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying Criteria Values
You define criteria values for complex logic accounts to define the selection criteria for
dimensions. The logic accounts are derived only from the source data records that meet
the criteria specified for the dimensions. For example, you can select values for accounts
that begin with 15, only for the Texas entity, and for all ICP members.
You create dimension criteria with the following criteria attributes:
Dimension Source dimension that is enabled for loading; you can select each
dimension only once
Criteria Type Operator (Between, In, or Like) that works with the Dimension and Criteria
Value attributes to determine the dimension members for the logic account
calculation
Criteria Value Criteria that work with the Dimension and Criteria Type attribute to
determine the dimension members for the logic account calculation
Applying Criteria Values
Dimension
names
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You use the Group By and Group Level attributes together to group logic accounts by the
preferred level and to override the display of the dimension member names in the Import
window. When you enter a text value for the Group By attribute of a dimension, FDM
displays the text value in place of the dimension member in the Import window. This
option enables FDM to group the dimension members based on the value that you enter
for the Group By attribute. You can hard code the member name, or you can append
hard-coded text values to the original member name. To append hard-coded values, you
enter the value with an asterisk (*) in the Group By column.
With the Group Level attribute, you can further group the dimension members. When you
enter 3 for the Group Level attribute of a dimension, FDM returns the first three
characters of the Group By value. If you do not enter a Group By value, FDM returns the
first three characters of the original source dimension member.
For example, when you enter the word Cash for the Group By attribute of the Account
dimension, FDM displays Cash in the Account column of the Import window for the
calculated logic account. If you enter the text value L-* for the Group By attribute, FDM
displays L-1100 in the Import window, where 1100 is the source account that matches
the logic criteria. If you also enter a Group Level of 2 for the same row, FDM displays
L-11 in the Import window.
If you do not enter a Group By text value for a dimension, FDM does not group the
dimension members and creates a separate logic account for each unique dimension
member.
Group By Name that overrides the dimension member name in the Import window
Group Level Number that works with the Group By attribute to override the dimension
member name in the Import window
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Complex Logic Example 1
Review the complex logic criteria example in the following table:
Dimension Criteria Type Criteria Value Group By Group Level
Account Like 151* PREPAID 0
Entity Like * TEXAS 0
ICP Between 1515-107,1518-112 ICP 0
UD1 Like * 0
UD2 Like * 0
Import
window
Complex
logic
criteria
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
In this example, the Account dimension criteria retrieve source accounts that begin with
151. The Entity, UD1, and UD2 dimension criteria specify that source data records for all
entity, UD1, and UD2 members are included in the calculation. The ICP dimension
criteria reduces the results to those source data records that have an ICP value between
1515-107 and 1518-112. Imported source data records that do not meet all of the criteria
are excluded from the calculated results.
When you import the source data records, FDM calculates one logic account from
multiple source data records. The Group By attribute for the Account, Entity, and ICP
dimensions includes the hard-coded values, TEXAS, PREPAID, and ICP. For every
source data record that passes the criteria, FDM replaces the original imported member
with the member that is listed in the Group By attribute. For the example in the slide, the
four data records that match the criteria are summarized into one logic account.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The criteria values in this example are the same as in the previous example except for
the Group By and Group Level attributes of the ICP dimension. The Group By value
contains ICP-*, which means that for every source data record that passes the specified
criteria, FDM returns ICP-, followed by the source member. The Group Level value is 7,
which causes FDM to return the first seven characters of the Group By member values.
In this example, FDM generates the following three logic accounts from the source data
records.
Source ICP members 1515-107 and 1515-108 are grouped into a logic account with
the ICP member name ICP-1515-10.
Source ICP member 1515-112 is placed into a logic account with the ICP member
name ICP-1515-11.
Source ICP member 1518-112 is placed into a logic account with the ICP member
name ICP-1518-11.
Complex
logic
criteria
Import
window
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Logic Groups to Locations
After you assign logic groups to data-load locations, FDM generates the logic accounts
when you import data files to the locations. You can assign the same logic group to
multiple locations.
To assign logic groups to locations:
1. In the FDM Web client, select Metadata, and then Locations.
2. In the Controls tree, select a data-load location.
3. Select the Workflow Behaviors tab.
4. In the Logic Group list, select a logic group, and click Save.
Assigning Logic Groups to Locations
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
In this lesson, you should have learned to:
Describe logic accounts
Create logic groups
Create simple logic accounts
Create complex logic accounts
Assign logic groups to locations
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 3

Loading FDM Journals 13
Objectives
Create journal templates
Add metadata tags
Check in and post journals
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 13 Loading FDM Journals
About FDM Journals
You can make adjustments to imported source data by loading FDM journal templates
into FDM. The journal templates add or replace data records that you want to load to
target systems. After posting the FDM journals, you can verify the adjustments by
displaying the Import window for the current location, period, and category. When you
have all the imported source data and adjustments, you can validate the data and export
it to target systems.
You typically use FDM journal templates for the following types of adjustments:
GAAP adjustments to GL files
Account breakdown into roll-forward accounts (Beginning Balance, Additions,
Disposals)
Supplemental data entry (Head Count, Ratios)
About FDM Journals
Headcount data imported f rom data file
Headcount data loaded from journal template
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
These changes are usually adjustments that you could not make in the GL of the original
source system because of statutory requirements or GL limitations.
NOTE: You should make as many entries as possible in the original source system
to enhance the data-load process and reduce the amount of manual work in
FDM.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Journal Templates
Journal templates are Excel spreadsheets that you format as journal entry input screens
with metadata tags and journal entries. You use the metadata tags to specify where to
load the journal entries. You add journal entries to specify the dimension members and
adjustment amounts that you want to load. For the example on the slide, you want to
load adjustments to four headcount accounts for the Indiana location, the FDM_Actual
category, and the 1/31/2011 period.
FDM provides a starting journal template (Journal.xls). The template has a range name
that includes all metadata tags rows and journal entries. The metadata tags are the first
five rows of the range, and are hidden between rows 15 and 23 of the spreadsheet
example. You must enter all journal entries between the two red lines in the range. There
is no limit to the number of journal entry rows that you import into FDM, as long as the
rows are between the two red lines.
Any user with access to Excel can create journal templates.
Creating Journal Templates
Hidden
metadata
rows
Data to
load
Where
t o load
the data
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Consider the following guidelines for journal templates:
You can insert and delete rows between the red lines.
You should not cut and paste rows in the template.
You can use formulas.
You can have more than one journal template in a Journal.xls file, as long as each
template has a unique range name.
To create journal templates:
1. Perform one of the following actions:
In the FDM Web client, select Tools, and then Templates, click Journal.xls, and then
click Open.
In Excel, open the Journal.xls file located in the FDM applications
Outbox\Templates directory.
The journal template file is opened in Excel.
2. Select rows 15 and 23, right-click, and select Unhide.
The metadata tags are displayed in rows 16 through 20.
3. Perform the following actions to define the metadata tags:
In cell C5, enter a journal ID of up to 10 characters.
In cell C7, enter the FDM location where you want to load the data.
In cell C9, enter the FDM category where you want to load the data.
In cell C11, enter the FDM period where you want to load the data.
In cell C13, enter the load method, A for append or R for replace.
The values that you enter are also displayed in the first four
metadata rows.
4. In the 5th metadata row, enter dimension tags to define the dimensions that you want
to load in the journal entries. By default, the Account, Center, Amount, and
Description dimensions are displayed.
5. Between the two red lines, add the journal entries that you want to load.
6. Save the journal template.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Metadata Tags
The journal template must have a range name that contains the metadata tags and
journal entries. This range name must begin with the prefix ups. For the example on the
slide, the range name, upsJournal, includes the metadata tags in rows 16 through 20 and
the journal entries in rows 23 through 26.
You must keep the metadata tags in a specific tabular format. The metadata tags row
order is important, but the column order is not. When you prepare journal templates, the
first five rows of the range must contain the metadata tags for the data rows.
Metadata tags
are in the first
five rows of
the range.
The upsJournal range is rows 16 through 26.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The metadata tags and their required positions in the journal template are described in
the following table:
Load Method Tags
You can append or replace data when loading the journal entries.
AppendAppends data to an existing journal with the same journal ID. If journal
entries exist with the same journal ID within the same POV, FDM appends the journal
entries in the Import window.
ReplaceReplaces data in an existing journal with the same journal ID. If journal
entries exist with the same journal ID within the same POV, FDM replaces the old
journal entries with the new journal entries.
There are four load method tags, as described in the following table. The AZ and RZ load
methods work the same as the append and replace load methods, except that FDM
suppresses all zero value amounts.
Row Tag Description
1 Journal ID Journal name. Place this tag in the Account column.
1 Location Location where you want to load the journal. Place this tag in the
Amount column.
2 Category Valid FDM category where you want to load the journal. Place this
tag in the Amount column.
3 Period Valid FDM period where you want to load the journal. Place this
tag in the Amount column.
4 Load Method Journal load method where you specify whether to append or
replace the journal data. Place this tag in the Amount column
5 Dimension Dimensions that specify where you want to load the journal. Place
these tags in separate columns.
Load Method Valid Tag
Append Journal A, Append
Replace Journal (default) R, Replace
Append Journal - Zero Suppress AZ
Replace Journal - Zero Suppress RZ
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Dimension Tags
You place dimension tags in separate columns in the fifth row of the range. The tags
define the dimensions that you want to load in the journal entries. For the example on the
slide, you load the Account, Center (location), Amount, and Description dimensions. The
Account and Center dimensions are the names of the accounts and centers from the
source system or the target system.
Journal templates can include the dimension tags described in the following table:
Dimension Valid Tags
Account (required) A, Account, SrcAcctKey
Center (required) C, Center, SrcCenterKey
Description (optional) D, Description, SrcAcctDesc
IC Counter Party (optional, except for Financial
Management target systems)
I, IC, ICCoParty
User Defined 1 through User Defined 20 (required
only if they are used by the target systems)
1, UD1, UserDefined1 through
20, UD20, UserDefined20
Amount (required) V, Amount, SrcAmount
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Loading Journal Templates
You load journal templates into FDM to post the journal entries to the data that you
imported from data files.
To load journal templates:
1. In the FDM Web client, select the location, category, and period POV for which you
want to load the journal template.
2. Select Activities, and then Journal.
The Journal window is displayed.
On the Upload File tab, browse to select the journal template, click Open, and then
click Check-In.
Loading Journal Templates
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
On the Select File From Inbox tab, click Select File, select the journal template from
the appropriate Inbox directory or subdirectory, and then click OK.
FDM compares the templates location, period, and category with
the corresponding dimensions in the POV. If the check is
successful, FDM displays a Post button in the Journal window.
4. Click Post.
FDM loads the journal entries to the data that you imported from
data files.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Checking In Journals
When you check in a journal template, FDM processes the metadata tags that are
located in the range names that start with the prefix ups. FDM compares the location,
category, and period in the template with the current dimension members in the POV. If
the members are the same, FDM displays the journal template name, the journal ID, and
the metadata tags in the File Contents area of the Journal window. If the members are
different, FDM displays an error. You must fix the errors and successfully check in the
template before you can post the journal.
For the check-in error on the slide, the category in the template, FDM_Actual, does not
match the category in the POV, FDM_Budget. If you want to load the journal template to
the FDM_Actual category, change the POV category to FDM_Actual and repeat the
check-in process.
Checking In Journals
FDM displays the
Post button after a
successful check-in.
Error during check-in.
Successful check-in.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Posting Journals
When you post journals, FDM either appends or replaces the data in the Import window
based on the load method that you specified in the journal template. You must
successfully check in a journal template before you can post it.
NOTE: Administrators and end users can post journal templates only to the Global
POV, unless they turn off the POV Lock option.
Posting Journals
Headcount data loaded from journal template.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Create journal templates
Add metadata tags
Check in and post journals
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 4

Loading Data with Multiload Files 14
Objectives
Create multiload Excel templates
Create multiload text files
Load multiload files into FDM
Execute Workflow tasks for multiload files
View errors
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 14 Loading Data with Multiload Files
About Multiload Files
Multiload files are text files or Excel templates that you use to load data into multiple
periods, categories, and locations. The files require metadata tags that FDM uses to
interpret the data that you want to load. The files also contain data rows that you want to
import into FDM.
The data columns in multiload files must contain a value. The data columns must have a
zero in every field that does not contain a value to load. If you include blank values in
data columns, FDM cannot successfully complete the multiload process.
You typically use multiload files for the following tasks:
Plan data collection (budget, forecast)
Historical data loading
Administrator data maintenance
About Multiload Files
Data for multiple time periods
Metadata
tags
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
During the multiload process, FDM users import data into FDM and load the data to
target systems. FDM users can load multiload files to all periods and categories, but only
to locations to which they have access. As the administrator, you can load multiload files
to all periods, categories, and locations.
NOTE: You can load a maximum of 12 periods with multiload text files, and you can
load an unlimited number of periods with multiload Excel templates.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Multiload Excel Templates
To create multiload Excel templates, you must define the metadata tags that FDM uses
to interpret the data in the template. The metadata tags define the columns that you
import into FDM and load to target systems.
FDM provides starting multiload Excel templates, Budget-12-Period.xls and Budget-12-
Period_All_Dims.xls. Both sample templates have a range name that includes the
metadata tag rows and data rows. The metadata tags are the first five rows of the range,
and are hidden between rows 9 and 16 in the templates. You must enter data rows
between the two red lines in the range. There is no limit to the number of data rows that
you can import into FDM, as long as the rows are between the two red lines.
Any user with access to Excel can create multiload templates.
Consider the following guidelines for multiload Excel templates:
You can insert and delete rows between the red lines.
Creating Multiload Excel Templates
Hidden
metadata
rows
Budget-12-Period.xls
sample template
Budget-12-Period_All_Dims.xls
sample template
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You should not cut and paste rows in the template.
You can use formulas.
To create multiload Excel templates:
In the FDM Web client, select Tools, and then Templates, click Budget-12-Period.xls or
Budget-12-Period_All_dims.xls, and then click Open.
In Excel, open the Budget-12-Period.xls or Budget-12-Period_All_dims.xls file located in
the FDM applications Outbox\Templates directory.
The multiload template file is opened in Excel.
2. Select rows 9 and 16, right-click, and select Unhide.
The metadata tags are displayed in rows 10 through 14.
3. Perform the following actions to define where and how to load the data:
In cell B5, enter the FDM location name.
In cell B6, enter the FDM category name.
In cell B7, enter the load method.
In row 12, for each data load column, enter the FDM period.
4. In the 5th metadata row, enter dimension tags to define the dimensions where you
want to load the data.
5. Between the two red lines, add the dimension members and data that you want to
load.
6. Save the Excel template.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Multiload templates must have a range name that contains the metadata tags,
dimensions, and amounts that you want to import. Range names must begin with the
prefix ups. For the example on the slide, the range name, upsBudget, includes the
metadata tags in rows 10 through 14 and the data in rows 16 through 24.
You must keep the metadata tags in a specific tabular format. The metadata row order is
important, but the column order is not. When you prepare multiload templates, the first
five rows of the range must contain the metadata tags for the data rows.
Metadata tags
are in the first
five rows of
the range.
The upsBudget range is rows 10 through 26.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The metadata tags and their required positions in multiload Excel templates are
described in the following table:
Adding Load Control Tags
You control the load methods for both FDM and the target system with the load control
tags in row 4. The tags that you specify depend on the target system. Target systems do
not require all of the tags. The 10 load control tags that FDM supports are described in
the following table:
Row Tags Description
1 Location FDM locations where you want to load the data. Place these tags
in Amount columns.
2 Category FDM categories where you want to load the data. Place these
tags in Amount columns.
3 Period FDM periods where you want to load the data. Place these tags in
Amount columns.
4 Load Method Data-load methods for FDM and the target system; control tags
vary by target system. Place these tags in Amount columns.
5 Dimension Dimensions that specify where you want to load the data. Place
these tags in separate columns.
Load Tag
Number Load Control Tag Name Description
1 FDM Load Method FDM data-load method
2 Target System Load Method Target system data-load method
3, 4, and 5 List Box 1, List Box 2, and List Box 3 Varies by integration block
6 Check Box Calc Data calculation (Y/N)
7, 8, and 9 Check Box 1, Check Box 2, and
Check Box 3
Varies by integration block
10 Data View YTD, Periodic, or Qtr Year-to-Date
data view
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Load Control Tags for Financial Management
The tags that you use to control the data-load method for Financial Management target
systems are described in the following table:
Load Tag Number and Name Option Valid Tags
1FDM Load Method Append A
Replace (default) R
Append - Zero Suppress AZ
Replace - Zero Suppress RZ
2Financial Management Load
Method
Merge M, Merge
Replace R, Replace
Accumulate A, Accumulate
for Financial Management
Place the load control tags in row 4 of the range.
Separate the load control tags with commas.
Type commas as placeholders for default tag values and
for unused tags.
Load control tags
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
If you do not enter values for tags 2, 3, 7, and 8, the values default to the data-load
options that you define in the FDM applications integration settings.
NOTE: You do not use load tags 4, 5, 6, and 9 with Financial Management target
systems. You must insert a comma as a placeholder to accommodate these
unused tags.
When you include the Data View tag in the header, FDM loads each data row with the
same data view. As an alternative method, you can create a Data View column in row 5
and specify a Data View tag for each row. If you do not define a Data View tag in the
header, and no Data View column exists, FDM sets the default data view to YTD.
Examples of Financial Management Load Control Tags
In the following example, you specify a valid tag for each load control tag item. You must
use commas as placeholders for the load tags that Financial Management does not
usetags 4, 5, 6, and 9. With this syntax you define the replace load method for FDM,
the merge load method for Financial Management, and the Load process. You also
specify that data is accumulated in the file, that the load file does not contain share data,
and that the data view is YTD.
R,M,0,,,,Y,N,,YTD
3Financial Management Load
Process
Load 0, Load
Scan 1, Scan
7Accumulate in File Yes Y, Yes, True, T
No N, No, False, F
8File has Share Data Yes Y, Yes, True, T
No N, No, False, F
10Data View Year-to-Date (default) Y, YTD, Year-To-Date
Periodic P, Per, Periodic
Qtr Year-To-Date Q, QYTD, Qtr
Half-Year H, HYTD, Half-Year
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
In the following example, you define only the FDM load method tag (A-append) and the
Financial Management load method tag (M-merge). The Data View tag defaults to YTD.
All other tags default to the load settings that you define in the applications integration
settings. You do not need trailing commas after the last supplied argument.
A,M
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Load Control Tags for Hyperion Enterprise
The tags that you use to control the data-load method for Hyperion Enterprise target
systems are described in the following table:
1FDM Load Method Append A
Replace (default) R
Append - Zero Suppress AZ
Replace - Zero Suppress RZ
2Hyperion Enterprise Load Method Merge M, Merge
Replace R, Replace
Accumulate A, Accumulate
3Data View Category C, Cat, Category
for Hyperion Enterprise
Place the load control tags in row 4 of the range.
Separate the load control tags with commas.
Type commas as placeholders for default tag values and
for unused tags.
Load control tags
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For a complete list of the Scale tag options, see the Oracle Hyperion Financial Data
Quality Management, Fusion Edition Release 11.1.2 Administrators Guide.
If you do not enter values for tags 2, 3, 4, and 7, the values default to the data-load
options that you define in the FDM applications integration settings.
NOTE: You do not use load tags 5, 6, 8, 9, and 10 with Hyperion Enterprise systems.
You must insert a comma as a placeholder to accommodate these unused
tags.
Examples of Hyperion Enterprise Load Control Tags (Multiload Excel File)
In the following example, you specify a valid tag for each load control tag item. You must
use commas as placeholders for the load tags that Hyperion Enterprise does not use
tags 5 and 6. With this syntax, you define the replace load method for FDM, the merge
load method for Hyperion Enterprise, and the Category data view. You also specify the
scale as None and the Zero No Data option.
R,M,C,N,,,Y
In the following example, you define only the FDM load method tag (A-append) and the
Hyperion Enterprise load method tag (M-merge). All other tags default to the load
settings that you define in the applications integration settings. You do not need trailing
commas after the last supplied argument.
A,M
Periodic P, Per, Periodic
Year-To-Date Y, YTD, Year-To-Date
4Scale None N, -1, None
Thousands TH, 3, Thousands
Millions ML, 6, Millions
Billions B, 9, Billions
7Zero No Data Yes Y, Yes, T, True
No N, No, F, False
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Dimension Tags
You place dimension tags in separate columns in the fifth row of the range. The tags
define the dimensions for the data that you want to load. For the first example on the
slide, you specify tags for the Account, Center (location), and Description dimensions, as
well as for two Value columns. For the second example on the slide, you specify tags for
the Account, Center (location), Description, View, Intercompany, and custom
dimensions, as well as two Value columns.
Accounts in multiload files can be existing accounts in the location mapping, or they can
be accounts that you must map during the Validate process.
When you load memos in multiload files, FDM enters the same memo specified in the
row for every period.
Adding Dimension Tags
Place the dimension tags in row 5 of the range.
Place the dimension tags in separate columns.
Dimension tags
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Multiload files can include the dimension tags described in the following table:
Dimension Valid Tags
Account (required) A, Account, SrcAcctKey
Center (required) C, Center, SrcCenterKey
Description (optional) D, Description, SrcAcctDesc
Data View (optional) W, DV, DataView
Accepted values:
Y, YTD, Year-To-Date
P, Per, Periodic
Q, QYTD, Qtr
H, HYTD, Half-Year
IC Counter Party (optional) I, IC, ICCoParty
User Defined 1 through User Defined 8
(optional)
1, UD1, UserDefined1
2, UD2, UserDefined2, and so on
Memo ID (optional except when using
Memo Detail)
M1
Memo Detail (optional) M2
Amount (required) V, Amount, VZ (zero suppress),
AmountZ (zero suppress)
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Multiload Text Files
You can also load data into multiple periods by using multiload text files. These files must
include the metadata tags in the first six rows, followed by the data rows. You must keep
the metadata tags in a specific tabular format. The metadata row order is important, but
the dimension tag order is not.
You can use the same load control tags and dimension tags for multiload text files as for
multiload Excel templates. You separate the load control tags and dimension tags with
delimiters. Valid delimiters include commas, semicolons, pipes, tabs, and exclamation
points. You must use the same delimiter in row 6 (to separate dimension tags) and in the
data rows (to separate dimension members and data values).
Creating Multiload Text Files
Metadata
tags
Data for
multiple time
periods
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For the multiload text file on the slide, the first six lines contain the metadata tags, and
the last seven lines contain the account name, account description, and data values. The
file defines the data that you want to load for the Texas location, the FDM_Budget
category, and the January through April time periods. With the load control tags for
Financial Management (R,M,0), you specify that you want to replace the data in FDM,
merge the data in the Financial Management target system, and load rather than scan
the data.
Depending on the amount of data, FDM processes multiload text files at a much faster
rate than multiload Excel templates. FDM creates a single load file and consolidates a
range of periods when processing a multiload text file. However, when processing a
multiload Excel template, FDM creates separate load files for each period and
consolidates one period at a time.
To create multiload text files:
1. In a text editor, open a text file that contains data that you want to load or create a
new text file.
2. Perform the following actions to define the metadata tags:
In row 1, enter the FDM location where you want to load the data.
In row 2, enter the FDM category where you want to load the data.
In row 3, enter the FDM period where you want to start loading the data.
In row 4, enter the number of periods that you want to load.
FDM uses this tag in combination with the starting period to derive
the periods of data to load.
In row 5, enter the data-load methods for FDM and the target system. Control tags
vary by system.
In row 6, enter the dimension tags that specify where you want to load the data. A
valid delimiter must separate the dimension tags.
3. Below row 6, include the dimension members and data that you want to load.
4. Save the text file.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Loading Multiload Files
You load multiload files into FDM to load data to multiple periods, categories, and
locations. FDM does not require the POV on the FDM desktop to match the POV in the
multiload file.
To load multiload files:
1. In the FDM Web client, select Activities, and then Multi-Load.
The Multi-Load window is displayed.
On the Upload File tab, browse to select the file, click Open, and then Check-In.
Loading Multiload Files
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
On the Select File From Inbox tab, click Select File, select the file from the
appropriate Inbox directory or subdirectory, and click OK.
FDM displays the POV for the locations, categories, and periods
that you want to load. FDM also displays the Status, Import,
Validate, Export, Consolidate, and Check buttons.
3. Click Status.
FDM expands the POV rows and displays the status of the Import,
Validate, Export, Load, and Check tasks.
4. Click Import.
When the task is completed successfully, FDM imports the data
and displays a check mark next to the Import task.
5. Click Validate.
When the task is completed successfully, FDM validates the data
and displays a check mark next to the Validate task.
6. Click Export.
When the task is completed successfully, FDM exports the data to
the target system and displays a check mark next to the Export
and Load tasks.
7. Optional: Click Consolidate to consolidate the data in the target system.
8. Click Check.
FDM checks the data and, when the task is completed
successfully, displays a check mark next to the Check task.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Checking In Multiload Files
When you check in multiload files, FDM processes the metadata tags in the multiload
file, and checks that the POV for each period in the file matches a valid POV in FDM. If
the POV is valid, FDM displays the POV for each period in the File Contents area of the
Multi-Load window. If the POV is invalid, FDM displays errors.
You must check in files that you select on the Upload File tab. FDM automatically checks
in files that you select on the Select File From Inbox tab.
For the check-in error on the slide, the FDM_BUD category in the multiload file does not
match a valid FDM category. You must change the category in the file to a valid FDM
category and repeat the check-in process.
Checking In Multiload Files
Successful check-in
Errors during check-in
FDM displays these buttons
after a successful check-in.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Executing Workflow Tasks for Multiload Files
After checking in multiload files, you follow the load process by clicking the Import,
Validate, Export, Consolidate, and Check buttons in the Multi-Load window. FDM
processes all periods in the multiload file during each task. For example, when you select
the Import task, FDM imports data from all periods in the multiload file into FDM.
As you successfully complete each Workflow task, FDM displays a red check mark to the
left of the task for each period. If FDM cannot complete a task, an error is displayed in
the File Contents area of the Multi-Load window. You can view the error details in the
Processing Details area of the window. For example, if mapping validation errors occur
during the Validate task, FDM displays the unmapped members in the Processing
Details area.
Executing Workflow Tasks for Multiload Files
Successful tasks
Workflow tasks
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Viewing Errors
For the example on the slide, FDM encounters an error when validating the data for the
Jan-2011 time period.
To view errors:
1. In the FDM Web client, select Activities, and then Multi-Load.
The Multi-Load window is displayed.
2. Check in a file that you want to load.
3. Perform the workflow tasks, such as import, validate, and export.
When a task end unsuccessfully, a link to an error is displayed for
the task.
Viewing Errors
Click the error.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. In the File Contents area, click the link to the error.
The error or a link to an error log file is displayed in the Processing
Details area.
Review the error in the Processing Details area.
In the Processing Details area, click the link to open and review the error log file.
NOTE: You must fix the errors before you can continue with the load process.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Create multiload Excel templates
Create multiload text files
Load multiload files into FDM
Execute Workflow tasks for multiload files
View errors
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 5

Setting Up Security 15
Objectives
Describe FDM security and security levels
Set up object security
Add authentication providers
Create users and assign user rights
Lock and unlock the Local POV mode
Set up report group security
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 15 Setting Up Security
About FDM Security
FDM security enables you to secure nearly every menu item, button, window, and report.
FDM supports two levels of security:
Object securityControls access to application objects (forms, menus, or menu
items) and controls (buttons, images, labels, drop-down lists, or links).
User securityControls user access to locations and objects.
You apply security levels to users and objects. FDM compares these security levels
when users access objects. If you assign a security level to a user that equals or
exceeds the security level of an object, the user can access that object.
You must have administrator rights to modify FDM security.
About FDM Security
FDM supports two levels of security:
User security Object security
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Security Levels
You assign security levels to objects and users. FDM compares the security level that is
assigned to a user with the security level that is assigned to the object to determine what
objects the user can access.
For the example on the slide, Rjackson and Lturner are intermediate-level users with
access to the File, Workflow, Activities, Tools, and Help menus. They cannot access the
objects that are assigned the Administrator security level (Analysis, MetaData, or
Administration menus).
The lower the security level, the more access the user has to objects. For example, an
Intermediate-4 security level has less-restrictive security than an Intermediate-9 security
level.
Security Levels
User Security Level
Cwest Administrator
Lturner Intermediate-5
Psmith Basic Reviewer
Rjackson Intermediate-7
Security levels
assigned to users
Security levels
assigned to controls in the
NavigationMenus object
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You assign the security levels described in the following table:
Consider the following examples:
Object assigned Intermediate-4 security levelOnly users who are assigned the
Administrator or Intermediate-2 through Intermediate-4 security levels can access
the object.
Users assigned Intermediate-7 security levelUsers have access to objects that
are assigned the All, All Intermediate, and Intermediate-7 through Intermediate-9
security levels. Users do not have access to objects that are assigned the
Intermediate-2 through Intermediate-6, or Administrator security levels.
Security Level Default Access
Administrator All locations, forms, and controls. You assign this role to
administrators.
Intermediate 2-9 Map, Import, Export, Validate, and MenuMaker forms and controls.
All Intermediate Map, Import, Export, Validate, and MenuMaker forms and controls.
Administrator users and Intermediate users 2 through 9 can access
objects that are assigned the All Intermediate level.
Basic Reviewer &
Submitter
Review and submit questions in Process Explorer. Users who are
assigned this level are automatically directed to the Process Explorer
window when they log on.
Basic Reviewer Review questions in Process Explorer. Users who are assigned this
level are automatically directed to the Process Explorer window when
they log on.
All File and Help forms and controls. All users can access objects that are
assigned the All level.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
About Object Security
You set up object security to assign minimum security levels for FDM objects.
The security levels for FDM objects control access to the objects. For example, on the
Maps form, you assign users access to the Add and Copy buttons, but restrict them from
the Delete All button.
FDM assigns a default security level to objects. As the administrator, you can modify the
default security levels and determine object security levels. Be sure to take into
consideration the different types of users that access FDM.
About Object Security
Object security defines access to objects such as
navigation menus and forms in FDM applications.
Objects contain controls, such as buttons and images, to
which you assign security levels.
Delete All Add Copy
Buttons on the
Maps Form object
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Setting Up Object Security
The Object Maintenance window lists all application objects and their respective controls.
You can modify the minimum security level for each control.
FDM compares the security level that is assigned to the object with the security level that
is assigned to the user to determine whether the user can access the object.
To set up object security:
1. In the FDM Web client, select Administration, and then Object Maintenance.
The Object Maintenance window is displayed.
2. In the top grid, select an application object.
Controls for the selected object are displayed in the bottom grid.
3. In the bottom grid, select a control.
Setting Up Object Security
Controls for
the Import
Form object
Minimum
security
level
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. Double-click in the Security Level column, and select a security level.
5. In the bottom grid, click Update Grid to save the changes.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
About User Security
FDM user security gives users access to objects and locations.
Object security levels control user access to components of the user interface, such
as forms, menu commands, and buttons.
Location security levels control user access to locations. You can grant users access
to all locations, or you can grant users access to limited locations with an assigned
security level.
New York
About User Security
User security gives users access to objects and locations.
Location security
levels control
access to locations.
Object security levels
control access to forms
and form controls.
Texas
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Setting Up User Security
You set up user security to define application users, assign user security levels, and
assign user access to locations.
Setting up user security in FDM consists of the following tasks:
Adding authentication providers for FDM
Provisioning users in Shared Services
Adding users and assigning user rights
Modifying user rights
Deleting users
Setting Up User Security
Setting up user security in FDM consists of the following tasks:
Adding authentication providers for FDM
Provisioning users in Shared Services
Adding users and assigning user rights
Modifying user rights
Deleting users
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Authentication Providers for FDM
You must add authentication providers for FDM before you can set up FDM user security.
The users that you add to FDM applications must exist in the authentication providers
that you define for FDM.
In Load Balance Configuration, you can add the following authentication providers:
CSS (Common Security Services)For integrating with products that use Shared
Services. CSS is the only supported authentication provider when the user
credentials contain extended ASCII or multibyte characters.
Visual Basic Script AuthenticationFor integrating with products that do not use
Shared Services.
Visual Basic Script SSO (Single Sign-On) AuthenticationFor integrating with
products that do not use Shared Services. Visual Basic Script SSO enables you to
authenticate a token that was passed via a URL. This authentication provider does
not apply to Workbench, so there must be at least one other enabled authentication
provider.
Adding Authentication Providers for FDM
Shared Services
authentication
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
FDM attempts to authenticate users against the authentication providers in the order in
which they are listed in Load Balance Configuration, from top to bottom.
FDM requires that you enable at least one authentication provider.
To add authentication providers for FDM:
1. Select Start, then Programs, then Oracle EPM System, then Financial Data Quality
Management, then Load Balance Manager, and then Load Balance Configuration.
The General tab of the Hyperion FDM Load Balance
Configuration dialog box is displayed.
2. Enter the Windows account user name and password that runs Load Balance
Manager.
3. For Password and Confirm Password, enter the password.
4. Select the Authentication Providers tab.
5. Click Add.
The Add Authentication Provider dialog box is displayed.
6. In the Authentication Provider list, select CSS, Visual Basic Script Authentication, or
Visual Basic Script SSO Authentication, and click OK.
The Authentication Provider dialog box is displayed.
7. Select or enter the properties for the selected authentication provider.
NOTE: For information about the authentication provider properties, see the
Oracle Hyperion Financial Data Quality Management, Fusion
Edition Release 11.1.2 Configuration Guide.
8. Select Enabled to force FDM to authenticate users with this authentication provider,
and click OK.
The Authentication Providers tab of the Hyperion FDM Load
Balance Configuration dialog box is displayed.
9. Optional: Select an authentication provider, and click Move Up or Move Down to
change the order of the authentication providers.
10. Click OK.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Provisioning Users in Shared Services
When you set up CSS as the FDM authentication provider, you must provision users for
FDM applications in Shared Services before adding the users to the applications in FDM.
Provisioning FDM users in Shared Services defines only the users security levels. You
define the users access to locations and the security levels for objects in FDM.
To provision users for FDM applications in Shared Services:
1. Select Start, then Programs, then Oracle EPM System, then Foundation Services, and then
Shared Services URL.
The Log On window is displayed.
2. Enter the user name and password, and click Log On.
The Oracle Hyperion Shared Services Console is displayed.
3. Expand User Directories, and then Native Directory.
Provisioning Users in Shared Services
In Shared Services, right-click a user, and select Provision.
Role assigned to
JodyG for the FDM
Flash application
Available roles for
the FDM Flash
application
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. Select Users, and click Search.
The native-directory users are displayed.
5. Right-click a user name, and select Provision.
The Provisioning tab displays the list of available and selected
roles.
6. Expand the application group, then the FDM application, then Administrator, and then
Basic Reviewer and Submitter.
The FDM application roles are displayed.
7. From the Available Roles area, select Administrator, Basic Reviewer And Submitter, Basic
Reviewer, or an intermediate (Intermediate 2 through Intermediate 9) role, and click the
add icon.
The FDM application name with the selected role is displayed in
the Selected Roles area.
NOTE: The Create Integration, Drill Through, Run Integration, and
Provisioning Manager roles are reserved for ERP Integrator.
8. Click Save.
The Provision Summary window is displayed.
9. Click OK.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Users to FDM Applications
After provisioning users for FDM applications in Shared Services, you can add the users
in FDM to the corresponding applications.
When you add users from Shared Services, you assign user access to locations in FDM,
but FDM obtains the user security levels from Shared Services.
User security associates each user with a security level that FDM evaluates against each
objects assigned security level. This process controls the user-interface components
that users can access. The Administrator security level provides access to every
location, form, and control. You assign the Administrator security level to grant users
administrator rights.
You can grant users access to all locations or you can assign users to specific locations,
one of which must be a default location.
Adding Users to FDM Applications
Select a user from the
list of provisioned
Shared Services users.
In User Maintenance, click New User.
Assign FDM
user rights.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
By default, the users security level determines their security level for each location. You
can assign security levels to locations to override the default security. For locations, the
security level that you specify in the Security Level field, rather than the level that you
specify for the user, determines access to the location.
For example, you assign the Intermediate-7 security level and three locations to a user. If
you assign a security level of Intermediate-5 to one of the locations, the users rights are
set to Intermediate-5, rather than Intermediate-7, when the user accesses that location.
To add users to FDM applications:
1. In the FDM Web client, log on to an FDM application for which you provisioned users
in Shared Services.
2. Select Administration, and then User Maintenance.
The User Maintenance window is displayed.
3. Click New User.
The New User dialog box is displayed.
4. In the Username list, select a user name from the list of provisioned Shared Services
users, and click OK.
The New User dialog box is displayed with user and location
options.
5. Optional: In the Email Address box, enter the users email address.
6. Select the Auditor check box to grant the user administrator rights for financial
controls.
7. In the Locations section, click Add to add a row to the grid.
8. In the row, double-click in the Location column, and select a location.
9. Select the Default check box to set the location as the users default, and clear the
Default check box for the CONTROLSREVIEW location.
10. Double-click in the Security Level column, and select a security level to set up
alternate rights by location.
12. Select the Grant Access to All Locations check box to enable non-administrator users
access to all locations.
13. Click OK.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Modifying User Rights
After adding Shared Services users to FDM applications, you can modify the users
rights to add access to locations and to select the users default location. However, you
change the users default security level in Shared Services, not in FDM.
To modify user rights:
1. In the FDM Web client, select Administration, and then User Maintenance.
2. Double-click the user name.
The User Rights dialog box is displayed.
3. In the Locations grid, add or change access to locations, and click Update Grid to save
the changes.
4. Change other user rights as needed, and click OK to save the changes.
Modifying User Rights
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Deleting Users
You can delete users from FDM applications. The users are not deleted from the
authentication providers.
To delete users:
1. In the FDM Web client, select Administration, and then User Maintenance.
2. Select a user, and click Delete.
Deleting Users
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Locking and Unlocking the Local POV Mode
You use this option to control the availability of the Local POV mode.
To lock or unlock the Local POV mode:
1. In the FDM Web client, select Administration, and then Point-of-View Mode Lock.
2. In the POV Mode Lock dialog box, perform one of the following actions:
Select the On/Off check box to lock the POV so that end users cannot change to
the Local POV mode.
Clear the On/Off check box to unlock the POV so that the Local POV is available to
all users on the system.
3. Optional: In the POV Mode Lock Message box, enter a message that is displayed
when the user tries to change the POV mode.
4. Click OK.
Locking and Unlocking the Local POV Mode
Select Administration, and then Point-of-View Mode Lock.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Setting Up Report Group Security
You can set up different security levels for each report group so that a report group can
be accessed only by users who are assigned the same or a less-restrictive security level.
To set up report group security:
1. In Workbench, select View, and then Reports.
2. Expand a language folder (for example, the English folder).
3. Right-click a report group, and select Properties.
The Report Group Properties dialog box is displayed.
4. In the Security Level list, select a security level.
5. Click OK.
Setting Up Report Group Security
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Describe FDM security and security levels
Set up object security
Add authentication providers
Create users and assign user rights
Lock and unlock the Local POV mode
Set up report group security
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 6

Working with Financial Controls 16
Objectives
Describe financial controls in FDM
Create controls groups
Delete and restore groups, sections, and questions
Assign reviewer, submitter, and proxy rights
Access financial controls
Add memos and attach documentation to questions
Review and submit questions in Process Explorer
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 16 Working with Financial Controls
About Financial Controls in FDM
To comply with Sarbanes-Oxley requirements, FDM includes a standardized, reviewable,
enterprise-wide process that enables you to certify financial data and assess your
internal controls. You use the process to configure financial controls for your locations.
Financial controls are defined in the following groups:
Certification GroupStores user-defined questions for use in the certification that
is required by Section 302 of the Sarbanes-Oxley legislation.
Assessment GroupActs as a repository for the documentation of internal controls
that are required by Section 404 of the Sarbanes-Oxley legislation.
You organize certification and assessment information by as many user-defined controls
groups as needed. Each controls group can consist of sections that organize controls
group information. Each section comprises questions. You answer, review, and submit
questions in Process Explorer to certify your financial data.
About Financial Controls in FDM
FDM financial controls are defined in two groups:
Certification Group (Section 302 of the Sarbanes-Oxley
legislation)
Assessment Group (Section 404 of the Sarbanes-Oxley
legislation)
Certification Group
Section 302
Controls Group Controls Group Controls Group
Section Section
Question Question
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Controls Groups
You create controls groups to maintain and organize certification and assessment
information.
To create controls groups:
1. In the FDM Web client, select MetaData, and then Controls Groups.
The Controls Groups window is displayed.
2. Right-click the Certification or Assessment group, and select Add Controls Group.
The Controls Group Properties dialog box is displayed.
3. In the Controls Group Name box, enter the group name.
4. In the Description box, enter the description.
5. In the Type list, select Certification (302) or Assessment (404), and click OK.
Creating Controls Groups
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Sections
You organize controls group information into sections. You can add as many sections as
you need. For example, a Financial Reporting controls group can consist of Review and
Completeness sections.
To add sections to controls groups:
2. Expand the Certification or Assessment group to display the controls groups.
3. Right-click a controls group, and select Add Controls Section.
The Controls Section Properties dialog box is displayed.
4. In the Controls Section Name box, enter a unique section name.
5. In the Description box, enter a description, and click OK.
Adding Sections
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Questions
Sections can consist of as many questions as needed. You must answer, review, and
submit these questions to certify your financial data and internal controls. For example,
you add the following question in the Verify Data section of the Final Review controls
group: Do you certify that these results are accurate?
You can create either a unique group of questions for each location, or a standard set of
questions that you assign to all locations of the organization. You can also assign
additional question groups to locations that require unique questions.
To add questions to sections:
2. Expand the Certification or Assessment group, then a controls group, and select a
section.
The Controls Items For Section grid is displayed.
Adding Questions
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
3. Click Add.
4. Enter the information described in the following table:
Column Description
ID Unique ID for the controls item. Do not include periods in the name.
Objectives Expected result of the question.
Type Type of question: Operations, Financial, Compliance, Ops/Fin,
Ops/Com, Fin/Com, or Ops/Fin/Com.
Risks Risks that can prevent the objective from being achieved.
Level Level of risk associated with an unexpected response to the question.
The risk range is L (low) to H (high).
Question Question that you want answered.
Frq.(Frequency) Frequency that you want the question answered: M (monthly),
Q (quarterly), Y (yearly).
Seq.(Sequence) Numerical order in which you want the question presented.
Resp. Req.
(Response
Required)
If selected, a response is required before you can complete the
section review.
Resp. Exp. Expected response to a question: Yes or No.
Inactive Question is not displayed and answered if you select the check box.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Setting an Effective Date
You can specify the period (month, quarter) when FDM presents the question. If you do
not specify an effective date, FDM presents the question in all periods.
To set an effective date for questions:
2. Expand the Certification or Assessment group, and then a controls group, and select
a section.
3. Click the ID for a question in the section.
The Explorer User Prompt dialog box is displayed.
4. In the Enter Effective Date box, enter the effective date, and click OK.
Setting an Effective Date
The effective date determines the period when the question is
first presented.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Question Profiles
You can combine one or more controls groups to create profiles. With profiles, you can
assign a different set of questions to each location.
For example, you include more than one controls group (consisting of various questions)
for a specific location and create a profile. You can similarly create another profile for
another location.
You can also edit a profile, by adding or deleting controls groups from the profile.
To create question profiles:
1. In the FDM Web client, select MetaData, and then Locations.
The Locations window is displayed.
2. In the Controls tree structure, select a location.
Creating Question Profiles
You create question profiles to assign a different set of
questions to each location.
Set 2
New York
Set 1
Texas
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
3. On the Financial Controls tab, click the Edit link under Certification (302) or
Assessment (404).
The Certification Profile or Assessment Profile dialog box is
displayed.
4. Click Add.
5. In the Enter profile name box, enter the name of the profile, and click OK.
6. Under the Available Groups section, select the controls group, and click the
right-arrow button.
The controls group moves to the Group Profile section.
7. Click OK.
8. Click Save.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Importing Questions from Excel
You can develop questions in Excel and import them into FDM. You can import the
general framework of the questions, and then update the questions in FDM as needed.
You must format all date fields as text or string in Excel before you can import them into
FDM. The example on the slide shows the format for a sample question import template;
it shows only a sample of the available fields for the tControlsItem table. The import
range name begins with ups.
The tControlsItem table includes the fields described in the following table:
Fields Description
ControlsItemKey Question Key (required)
ControlsGroupKey Group (required)
ControlsItemTag Question ID (required)
Importing Questions from Excel
Import range name
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
To import questions from Excel to the FDM Web client:
1. In the FDM Web client, select Tools, and then Import XLS.
2. On the Upload File tab, click Browse, select a file, and click Open.
3. Click Import.
ControlsSectionKey Section number (required)
ControlsItemCommentRequired True or False
ControlsItemObjective Objectives
ControlsItemType F (Financial), O (Operations), C (Compliance)
ControlsItemRisks Risk associated with question or objective
ControlsItemRiskLikelihood 1 thru 5
ControlsItemFocus Questions
ControlsItemSequence Order in which question is presented
ControlsItemExpectedRespones Yes or No
Fields Description
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Deleting Controls Groups, Sections, or Questions
When you delete controls groups, sections, or questions, the deleted objects are placed
in the respective Certification or Assessment recycle bin.
NOTE: Items in the recycle bin can be restored, but items that are deleted from the
recycle bin are deleted permanently.
To delete controls groups or sections:
2. Expand the Certification or Assessment group, and then a controls group.
Deleting Controls Groups, Sections, or Questions
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
3. Right-click a controls group or section, and select Delete Controls Group or Delete
Controls Section.
4. Click OK at the confirmation prompt.
To delete questions:
2. Expand the Certification or Assessment group, and then a controls group.
3. Select the section that contains the question that you want to delete.
4. Select a question, and click Delete.
5. Click Update Grid to save the change.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Restoring Controls Groups, Sections, or Questions
You can restore controls groups, sections, or questions from the recycle bin.
To restore controls groups:
2. Expand Recycle Bin for the certification or assessment group.
3. Right-click a controls group, and select Restore Controls Group.
To restore sections:
Restoring Controls Groups, Sections, or Questions
Restore
questions
Restore icon
Restore
controls
groups
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
3. Expand DELETED SECTIONS.
4. Right-click a section, and select Restore Controls Section.
6. In the Select Controls Group dialog box, select the group where you want to restore
the section, and click OK.
To restore questions:
3. Expand DELETED SECTIONS, and select DELETED QUESTIONS.
The Controls Items For Section area displays the deleted
questions.
4. For the question that you want to restore, click the restore icon.
6. In the Select Controls Section dialog box, select the section where you want to
restore the question, and click OK.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Reviewer, Submitter, and Proxy Rights
You set up certification and assessment reviewers to answer questions in assigned
sections. You can assign one reviewer to each section or one reviewer to multiple
sections.
You assign certification submitters and assessment submitters to a location. Submitters
submit certifications or assessments after reviewing all sections.
NOTE: If the certification is contingent on data loading, the submitter cannot submit
until data is loaded and all sections are reviewed.
You also assign proxies as alternate reviewers and submitters.
Assigning Reviewer, Submitter, and Proxy Rights
Reviewer Submitter
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Reviewers and Proxies
To assign reviewers and proxies to sections:
2. In the Controls tree structure, select the location whose section you want to assign to
the reviewer and proxy.
3. Select the Financial Controls tab.
4. In the Certification or Assessment list, select a question profile.
5. Click Save.
The Certification Reviewers or Assessment Reviewers table is
populated with the sections in the question profile.
6. For each section, select a user in the Reviewer and Proxy lists.
Assigning Reviewers and Proxies
Select a user name.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
7. Click Update Grid.
NOTE: If you set up users with the Basic Reviewer or Basic Reviewer &
Submitter role, they will be routed directly to the Process Explorer
window when they log on.
8. Click Save.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Submitters and Proxies
To assign submitters and proxies to locations:
2. From the Controls tree structure, select the location to which you want to assign the
submitter and proxy.
4. In the Submitter and Proxy lists, select the users.
5. Click Save.
Assigning Submitters and Proxies
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Risk Levels to Locations
As with questions, you assign risk levels (low to high) to locations. FDM compares the
risk level that you assign to a location with the risk level that you assign to a question. If
the locations risk level is lower that the questions risk level, FDM displays a red flag for
an unexpected response to the question. For example, if the expected response to a
question is Yes, but the response is No, a red flag is displayed.
Locations whose risk level is Medium (M) generate red flags for questions whose risk
level is medium or higher and that are answered with an unexpected response.
Questions whose risk level is low (L) to low-medium (L-M) do not generate red flags for
unexpected responses associated with locations whose risk level is medium.
Assigning Risk Levels to Locations
Location Risk Level = M
Question Risk Level = L
Location Risk Level = L
Question Risk Level = M
New York
Texas
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
To assign risk levels to locations:
2. From the Controls tree structure, select the location to which you want to assign a
risk level.
4. In the Risk Flag Level list, select a risk level: L, L-M, M, M-H, or H.
5. Click Save.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Accessing Financial Controls
In the FDM Web client, you access financial controls in the Process Explorer window.
As a reviewer, you can perform the following tasks in Process Explorer:
Attach documentation to memos
Review and submit questions
To access financial controls:
In the FDM Web client, perform one of the following actions:
Select Analysis, and then Process Explorer.
After data is successfully loaded to a location, click the notepad icon.
Accessing Financial Controls
You access financial controls on the Process Explorer desktop.
Click here t o view
Process Explorer.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Adding Memos and Attaching Documentation
You organize documentation in the following groups:
General DocumentationUsers with the appropriate security can attach
documents in this group.
Audit DocumentationOnly users who are granted Auditor status can attach
documents in this group.
NOTE: Auditor status is set up in the FDM User Maintenance window.
Adding Memos and Attaching Documentation
You attach supporting documentation to memos in the Process
Explorer window.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Attaching General Documentation
You can attach general documents to certifications or assessments.
To attach general documentation:
1. In the FDM Web client, select Analysis, and then Process Explorer.
The Process Explorer window is displayed.
3. In the Section list, select a section name.
The controls items for the section are displayed.
4. In a controls item row, click in the second column to display the Memo Item dialog
box.
Attaching General Documentation
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
5. Click Add.
6. Enter the memo item ID, and click OK.
7. In the Memo box, enter a description for the memo item.
8. Next to Line 1, click Add.
The File Browser dialog box is displayed.
Documents in the application Inbox directory: Select a document, and click OK.
Documents on the network: Click Browse, select and open the document, and click
Upload to upload it to the Inbox directory. Select the document, and click OK.
10. Repeat steps 8 and 9 to attach other general documents.
You can attach up to 10 supporting documents to each memo.
11. Click Close.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Attaching Audit Documentation
FDM divides the Audit Documentation group into the following sections: Evaluation, Gap
Analysis, and Action Plans.
The Audit Documentation group has an additional responsibility area for tracking and
reporting on audit memo items. You can designate assigned users and a target date for
completion.You can also check when the item is completed.
To attach audit documentation:
3. In the Section list, select a section name.
Attaching Audit Documentation
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. In a controls item row, click in the third column to display the Audit Evaluation dialog
box.
5. Select the item type: Evaluation, Gap Analysis, or Action Plans.
6. Click Add.
7. Enter the memo item ID, and click OK.
8. In the Memo box, enter a description for the memo item.
9. Next to Line 1, click Add.
Documents in the application Inbox directory: Select a document, and click OK.
Documents on the network: Click Browse, select and open the document, and click
Upload to upload it to the Inbox directory. Select the document, and click OK.
11. Repeat steps 9 and 10 to attach other audit documents.
12. Optional: Select the Responsibility tab, and perform the following actions:
a. In the Assigned To list, select a user name.
b. In the Assigned By list, select a user name.
c. In the Target Date box, enter a target completion date.
d. Select the Completed check box when the item is completed.
e. In the Evaluation ID list, select an Evaluation memo item to link to Gap Analysis or
Action Plans memo items.
f. In the Gap Analysis Value list, select L, L-M, M, M-H, or H to rank the significance of
the identified gap for Gap Analysis memo items.
13. Click Close.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Reviewing and Submitting Questions
You certify data for the certification and assessment processes by reviewing and
submitting questions at each level of the organization.
You can assign a unique group of questions to each location.
You can develop a standard group of questions that you assign to all locations.
You can assign question groups to locations that require additional questions.
To review and submit questions:
Reviewing and Submitting Questions
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
3. In the Section list, select the section name that contains the question.
4. Review the objectives and risks of the question.
5. Answer the question by performing one of the following actions:
If the Resp. Req. field is selected, in the Y/N column, select Yes or No. If you select
No, proceed to step 6; otherwise, skip to step 7.
If the Resp. Req. field is not selected, select Yes, No, NR, or NA. If you select No,
proceed to step 6, otherwise skip to step 7.
6. In the Response column, enter a comment.
7. Optional: Attach General or Audit documentation.
9. Click Review.
The Review Status changes to Yes. You can unsubmit or
unreview a question.
10. Click Submit to validate the completeness and accuracy of the data.
Successful completion of the data promotes the data within FDM.
The Submit Status changes to Yes. The point of view is locked,
and the Process Explorer icon displays a check mark.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Selecting Application Settings for Financial Controls
You can set several FDM application settings for financial controls. The application
settings provide additional flexibility for the use of financial controls.
To select application settings for financial controls:
1. In the FDM Web client, select Administration, and then Application Settings.
2. In the Options list, select the application settings related to financial controls as
described in the following table:
Application
Settings Description
Controls Lock Locks the POV after users submit the certification. After
certification is submitted, data cannot be loaded to a location with a
locked POV.
Selecting Application Settings
for Financial Controls
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For the Controls Lock, Controls W/O Data, or Controls Unsubmit options, select
the On/Off check box.
For the Fiscal Start Period option, select a start period from 1 to 12.
For the Memo Item Filter With Category and Period option, select 0-None to display
the memos and attachments in all categories or periods, or 1-Category_Period to
display them only in the category and period POV in which they were added.
4. Click Save.
Controls W/O Data Enables users to submit data in the certification process without
loading data from data-loading locations.
Controls Unsubmit Enables non-administrators to unsubmit data. If this option is
cleared, only administrators can unsubmit data.
Fiscal Start Period Defines the first period of the fiscal year (Jan. = 1, Feb. = 2,
Mar = 3, and so on) to enable correct processing of information in
the Monthly, Quarterly, and Yearly frequencies.
Memo Item Filter
With Category and
Period
Displays memos and audit attachments in all categories and
periods (default), or only in the category and period POV in which
they were added.
Application
Settings Description
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Describe financial controls in FDM
Create controls groups
Delete and restore groups, sections, and questions
Assign reviewer, submitter, and proxy rights
Access financial controls
Add memos and attach documentation to questions
Review and submit questions in Process Explorer
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 7

Working with Import Scripts 17
Objectives
Describe the scripting components in FDM
Create import scripts
Assign import scripts to import formats
Apply scripting functions to import scripts
Store and retrieve temporary variables
Manually execute custom Web scripts
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 17 Working with Import Scripts
About Scripting in FDM
You can use Visual Basic scripting in FDM to enhance the flexibility and power of the
product. You can also reference the FDM internal object model (FDM-specific functions)
in FDM scripts.
FDM supports following three types of scripts:
Import scripts are executed during the import process. For example, you can create
an import script to parse the left two characters of accounts before importing them
into FDM.
Custom scripts are created for a specific purpose, such as executing multiple reports
or starting batchloading processes.
Event scripts are executed in response to events. For example, you can use the
BefFileImport event script to dynamically change the import format for a location.
About Scripting in FDM
Enhances basic product
Supports three kinds of scripts
Import scripts
Custom scripts
Event scripts
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Working with Scripting Components
FDM scripting has the following three main components:
Script EditorYou create all scripts in Script Editor within the FDM Web client or
Workbench, and save the script files in the FDM applications Data\Scripts directory
with a USS file type. You can edit FDM scripts with a text editor and copy scripts to
other FDM applications by copying the script file itself.
AcceleratorsAccelerators are prebuilt code modules that simplify the process of
creating scripts.
Menu MakerMenu Maker adds a link on the FDM Web client interface to enable
users to run custom Web scripts manually.
Working with Scripting Components
Menu Maker
Accelerators
Script Editor
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Accessing Script Editor in the FDM Web Client
To access Script Editor in the FDM Web client:
1. Select Tools, and then Script Editor.
2. Expand the Events, Custom, or Import folder to access a stored script.
The list of scripts in the selected folder is displayed.
3. Select a script.
The selected script is displayed for editing.
Accessing Script Editor in the FDM Web Client
Select Tools, and then Script Editor.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Accessing Script Editor in Workbench
Currently, Workbench offers more powerful script-editing capabilities than the FDM Web
client. For this reason, Workbench is the preferred method for building and maintaining
scripts, and it is the method that you will use in this class.
To access script editor in Workbench:
1. From the bottom of the navigation pane, select the Scripts tab.
The Script Editor and Object Browser panes are displayed.
2. Expand the Event, Custom, or Import folder to access a stored script.
The list of scripts in the selected folder is displayed.
3. Double-click a script.
The selected script is displayed for editing.
Accessing Script Editor in Workbench
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The Script Editor pane displays folders for the three types of scripts. The Object Browser
pane displays the accessible FDM objects. Each FDM object corresponds to a public
class module within an FDM.dll file. Each object contains subobjects, methods,
functions, and properties that you can access in scripts.
You can reference all FDM objects in any script type, with the exception of the API
object. You cannot reference an API object in an import script.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Accessing Accelerators
Accelerators are prebuilt code modules that simplify the process of creating scripts. They
are available only in Workbench. You can find accelerators in the Object Browser pane of
the Script Editor window.
To access accelerators:
1. In Workbench, position the cursor in an open script.
2. In the Accelerators folder, double-click the accelerator name that you want to insert in
your script.
The accelerator code is added at the cursor position in the script.
Accessing Accelerators
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Scripts
You create import scripts to manipulate source data as it is being imported into FDM. The
script can be assigned to any import field within an import format, and it is executed
when a source data line is read by FDM.
Import Script Parameters
The following parameters are passed into the import script:
strFieldContains the value from the data file for the field to which the import script
is assigned. For example, if the import script is assigned to the Amount field, this
parameter contains the value from the Amount field in the data file. If the import script
is assigned to the Account field, this parameter contains the value from the Account
field in the data file.
strRecordContains an entire record from the data file being scanned.
Creating Import Scripts
The following parameters are passed into import scripts:
strField
strRecord
Example record: 190-102, Accounting, 500.00 (Comma-delimited)
190-102, Accounting, 500.00 190-102, Accounting, 500.00
strField parameters strRecord parameters
Account Account Desc Amount
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For the example on the slide, the import file includes the record 190-102, Accounting,
500.00. When the import script is attached to an Account field, the values passed to the
script for this record are as follows:
strField: 190-102
strRecord: 190-102, Accounting, 500.00
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Scripts in Workbench
To create import scripts in Workbench:
1. Select the Scripts tab.
2. Select File, and then New Script.
The New Script dialog box is displayed.
3. In the Script Type list, select Import (DataPump).
4. In the Script Name box, enter a script name, and click OK.
The script window is displayed, and the two parameters, strField
and strRecord, are passed into the import script.
5. Enter the appropriate documentation, such as author, date, and purpose of the script.
6. Enter the script lines.
7. Select File, and then Save Script.
Creating Import Scripts in Workbench
Script lines Documentation
Script name Parameters
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Scripts: Example
The following example shows an import script (Parse_Account) for parsing the left four
characters of the field.
Function Parse_Account(strField, strRecord)
Parse_account = Left (strField, 4)
End Function
Creating Import Scripts: Example
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Import Scripts to Import Formats
After creating and saving the import script, you assign it to a field in an import format.
To assign import scripts to fields in import formats:
1. In the FDM Web client, select MetaData, and then Import Formats.
The Import Formats window is displayed.
2. Select the import format.
3. In the Field Name column, select the field to which you want to assign the script.
4. Double-click in the corresponding Expression column, point the cursor to the arrow,
and select Add Expression.
The Add Expression dialog box is displayed.
Assigning Import Scripts to Import Formats
Script assigned to
the Account field
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
a. In the Expression Type list, select Script.
b. Click Browse to search for the created script.
c. Select the script, and click OK.
The Add Expression dialog box displays the script name in the
Expression Value field.
d. Click OK to return to the Import Formats window.
6. In the bottom grid, click Update Grid to save the changes.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying Scripting Functions to Import Scripts
You can use the functions described in the following table in import scripts to retrieve
specific parts of records and to skip selected records:
Function Description
Left Returns the first n characters of a string
Right Returns the last n characters of a string
Mid Returns characters located in the middle of a string
fParseString Parses strings that contain a delimiter into separate fields
RES.PblnSkip Skips records in data files
Applying Scripting Functions to Import Scripts
Left function
Right function
Mid function
fParseString function
RES.PblnSkip function
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying the Left Function
You use the Left function to return the first n characters of a string.
For the example on the slide, the mapping for the location uses only the first four digits of
the account number. You can change the mapping by adding wildcards or by importing
only the first four characters in an import script.
You use the Visual Basic Left function to return the first four characters of the field. This
code assigns the first four digits of the account number to the script.
After creating the script, you assign it to the Account field of the import format.
Syntax:
Left (String, Length)
Parameters:
String String expression from which to return the first n characters of a
string
Length Numeric expression indicating how many characters to return
Example:
Left (1100 - Cash in Bank - 48,200,580, 4)
Returns the value 1100
Applying the Left Function
String
Length
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying the Right Function
You use the Right function to return the last n characters of a string.
For the example on the slide, the fields in the record include account description, cost
center, and account number. The account number consists of the last four characters of
the field.
You use the Visual Basic Right function to return the last four characters of the field. This
script assigns the last four digits of the account number to the script.
Applying the Right Function
Syntax:
Right (String, Length)
Parameters:
String String expression from which to return the last n characters of a string
Example:
Right (Sales Discount 100 - 8250, 4)
String
Length
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying the Mid Function
You use the Mid function to return characters located in the middle of a string.
For the example on the slide, the fields in the record include account description, cost
center, and account number as a continuous string in the record. You can separate the
string into separate fields by writing a script to parse out the fields. The account starts at
column 7 and contains four characters. You use the Mid function to return the characters
in columns 7 through 10.
Applying the Mid Function
Syntax:
Mid (String, Start, Length)
Parameters:
String String expression from which to return characters located in the
middle of a string
Start Character position in string at which to start the substring
for the substring
Example:
Mid (100 0012 Sales Discount, 7, 4)
Returns the value 0012 String
Length
Start
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying the fParseString Function
You can use the fParseString function to parse a string that contains a delimiter into
separate field strings.
For the example on the slide, the fields in the record, Cost Center, Account, and Account
Description, are separated by a dash (-). The fParseString function breaks the string into
three distinct fields and returns a value for Account.
NOTE: The fParseString function is not a Visual Basic function. It is an FDM function
that enables you to parse a string that contains a delimiter.
Similarly, you could use the fParseString function to return values for the cost center and
account description.
Applying the fParseString Function
Syntax:
DW.Utilities.fParseString (String, #Fields, Desired, Delimiter)
Parameters:
String String expression to be parsed
#Fields Total number of substrings created by separating the string by
using the delimiter
Desired Number of the substring that is returned
Delimiter Character splitting the items in the record
Example:
myString = 100 0012 Sales Discount
DW.Utilities.fParseString (100 0012 Sales Discount, 3, 2, -)
String Desired #Fields
Delimiter
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying the RES.PblnSkip Function
You can selectively skip data file records with the RES.PblnSkip function. The skipped
records are, therefore, not imported into FDM.
The RES.PblnSkip function is typically placed within an IF function and may use other
functions, as shown in the example on the next page.
Applying the RES.PblnSkip Function
Syntax:
Res.PbLnSkip = TRUE
Parameters: (none)
Usage:
Embedded in IFTHEN expressions
Often used with the fParseString function
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Applying the RES.PblnSkip Function: Example
For the example on the slide, the script skips all entities that begin with 06. Notice that
the script uses the FDM fParseString function to separate the entity field, which is stored
in the temporary variable, strEntity. The temporary variable is locally defined and is lost
when the script is completed.
Applying the RES.PblnSkip Function: Example
If strField = 063 0790 - Other Costs, the script skips the line.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Working with Temporary Variables
Some data files contain fields that are not repeated on every line, but must be included
on every row in the target application. For example, entity or description might be located
in header lines that appear repeatedly in the data file (but not on every line).
When FDM reads a data file, it automatically skips lines that do not contain a valid
amount, but scripts in the Amount field are still executed. Thus, you have the flexibility to
write scripts for lines that FDM would otherwise skip.
For example, suppose you need to capture the Entity field from header lines in the data
file. First, assign to the Amount field a script that gets the required field from the header
line and stores the field in a temporary variable.
Next, assign to the Entity field a script that puts the entity value from the temporary
stored variable into the Entity field. This process is illustrated in the next three topics.
Working with Temporary Variables
You can store variables to share between import scripts.
Syntax:
RES.PvarTemp1
RES.PvarTemp2
RES.PvarTemp3
RES.PvarTemp4
RES.PvarTemp5
Example:
RES.PvarTemp1 = 75
Sets the value of temporary variable RES.PvarTemp1 to 75.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Temporary Variables
The example on the slide shows a balance sheet data file layout. The entity is not
repeated in every row, but it is contained in the header for each section of the report.
(The entity appears as a four-character string after the Dept label.)
You can write two scripts (a get script and a put script) and use a temporary variable to
capture the entity from the header lines in the file. This process is shown in the following
two topics.
Assigning Temporary Variables
Entities
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Storing Temporary Variables
For the script example on the slide, GetEntity is assigned to the Amount field in the
import format. GetEntity uses an If...Then statement and the Mid function to determine if
the data line contains the required entity. If it does, the script stores the entity in a
temporary variable.
Storing Temporary Variables
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Retrieving Temporary Variables
For the script example on the slide, PutEntity is assigned to the Entity field in the import
format. The PutEntity script assigns the value stored in the temporary variable,
RES.PvarTemp1, to the entity.
Retrieving Temporary Variables
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Importing Files
After assigning the scripts to the Amount and Entity fields, you import the balance sheet
data in FDM. When you import the data file, the entity value is assigned to each record.
For the example on the slide, you assign the GetEntity script to the Amount field and the
PutEntity script to the Entity field of the import format.
Importing Files
Assign scripts
to fields in the
import f ormat.
Import the data
file to FDM.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Manually Executing Custom Web Scripts
You can set up custom Web scripts so that you can manually execute them from links in
the Task Flows window. The Menu Maker feature in the Tools menu makes this a simple
process. To make a custom script link available to your users, first create the script as a
Custom (Web) script type in Script Editor, and then create the link and assign it to the
Web script by using the FDM Web client.
To manually execute custom Web scripts:
1. In the FDM Web client, select Tools, and then Menu Maker.
The Menu Maker window is displayed.
2. Click Add to create a menu item.
3. In the Menu Caption column, enter a caption for the menu.
4. In the Associated Script list, select the custom Web script.
Manually Executing Custom Web Scripts
Click to execute the script.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
5. Under Sequence, enter a number to control the order in which the custom Web
scripts appear on the Task Flows window.
6. Select the Active check box to display the script on the Task Flows window.
8. Select Tools, and then Task Flows to view the links in your custom menu.
9. Click a link to execute the script.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Describe the scripting components in FDM
Create import scripts
Assign import scripts to import formats
Apply scripting functions to import scripts
Store and retrieve temporary variables
Manually execute custom Web scripts
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 8

Working with Import Integration Scripts 18
Objectives
Describe import integration scripts
Create import integration scripts
Assign import integration scripts to import formats
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 18 Working with Import Integration Scripts
About Import Integration Scripts
You can import source data directly from ODBC/OLEDB-compliant source systems by
using an import integration script. The import integration script enables you to connect to
source systems and import data directly from the source systems to FDM applications.
The import integration script performs the following tasks:
1. Accesses and queries the database tables in the source system.
2. Moves the data from the query results to a temporary working table, from which the
data is imported to the FDM application.
NOTE: With the exception of the FDM API object, all FDM objects are supported in
import integration scripts.
About Import Integration Scripts
ODBC/OLEDB
data source
Financial
Management
Hyperion
Enterprise
Planning
Essbase
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Import Integration Script Parameters
The following parameters are passed into import integration scripts:
strLocContains the active FDM location key.
lngCatKeyContains the active FDM category key.
dblPerKeyContains the date serial key of the active FDM period.
strWorkTableNameContains the name of the working table into which the source
data is imported for the FDM location.
Import Integration Script Parameters
The following parameters are passed into import integration
scripts:
strLoc
IngCatKey
dblPerKey
strWorkTableName
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Population of FDM Table Fields
The FDM table fields are described in the following table:
Field Name Field Information Note
PartitionKey [Type=Long, Size=0,
Required=Yes]
FDM location name; use strLoc parameter
CatKey [Type=Long, Size=0,
Required=Yes]
FDM category key; use lngCatKey parameter
PeriodKey [Type=TimeStamp, Size=0,
Required=Yes]
FDM period key; use dblPerKey parameter
DataView [Type=VarWChar, Size=5,
Required=Yes]
Load Frequency; defaults to YTD
Amount [Type=Double, Size=0,
Required=Yes]
Source amount
Population of FDM Table Fields
When creating import integration scripts, you must populate the
FDM table fields with source data that is retrieved from the
source system.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Desc1 [Type=VarWChar, Size=75,
Required=No]
Source account description
Account [Type=VarWChar, Size=75,
Required=Yes]
Source account
Entity [Type=VarWChar, Size=75,
Required=Yes]
Source entity
ICP [Type=VarWChar, Size=75,
Required=No]
Source ICP
UD1UD20 [Type=VarWChar, Size=75,
Required=No]
Source UserDefined dimensions 1 through 20
Attr1Attr14 [Type=VarWChar, Size=20,
Required=No]
Source Attribute dimensions 1 through 14
ArchiveID [Type=Bigint, Size=8,
Required=No]
Archive ID from the data directory
Field Name Field Information Note
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Integration Scripts in Workbench
To create import integration scripts in Workbench:
2. Select File, and then New Script.
The New Script dialog box is displayed.
a. In the Script Type list, select Import (Integration).
b. In the Script Name box, enter a script name.
TIP: Name the script similar to the import format name or the location name.
Creating Import Integration Scripts in Workbench
Documentat ion
area
Parameters
Script lines
area
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
c. Click OK.
The script window is displayed, and the four parameters are
passed into the import integration script.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Integration Scripts: Example
The example on the slide shows an import integration script that opens an Oracle
database and imports the data directly into an FDM application. This example is one of
many ways that you can integrate with a database via a script.
The Set statements open the ADO database connection, point rs to Recordset, and point
rsAppend to the temporary working table.
Creating Import Integration Scripts: Example
Function name
and parameters.
Declare
variables.
Define the OLE
database connection.
Populate the rs dataset with all
records from the dat abase.
Check for data and display
message if no records are f ound.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Integration Scripts: Example (cont.)
The script loops to populate the rsAppend dataset with all records from the rs dataset.
FDM assigns a value of True to the function if the import is successful. A value of False is
assigned to the function if errors are raised in the script.
Creating Import Integration Scripts: Example (cont.)
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Assigning Import Integration Scripts to Import Formats
After creating and saving the import integration script, you assign it to the import format
in the FDM Web client.
To assign import integration scripts to import formats:
1. In the FDM Web client, select MetaData, and then Import Formats.
The Import Formats window is displayed.
2. Perform the following actions to create an import group for the import integration
script:
a. In the import group table, click Add.
b. In the Import Group column, enter the import group name.
c. Optional: In the Description column, enter a description for the import group.
Assigning Import Integration Scripts
to Import Formats
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
d. In the File Type column, select Script.
e. In the Delimiter column, select the NA delimiter.
f. Click Update Grid to save the changes.
The Fields for Selected Import Format table is displayed at the
bottom of the window.
A row is displayed below the Expression column.
4. Double-click in the Expression column, place your cursor over the arrow, and select
Add Expression.
The Add Expression dialog box is displayed.
a. In the Expression Type list, select Script.
b. Click Browse, select the import integration script, and click OK.
The import integration script is displayed in the Expression Value
field.
c. Click OK to close the Add Expression dialog box.
The import integration script is displayed in the Expression
column.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Describe import integration scripts
Create import integration scripts
Assign import integration scripts to import formats
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
L E S S O N 1 9

Working with Event Scripts 19
Objectives
Describe event scripts
Create event scripts
Change import formats dynamically
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Lesson 19 Working with Event Scripts
About Event Scripts
Event scripts are executed in response to FDM events.
The Script Editor Event folder contains a list of events that FDM can respond to.
NOTE: All FDM objects are supported in event scripts.
About Event Scripts
Event scripts are triggered at various times
during FDM processes.
For example, for an import process, FDM
can recognize events before and after the
import.
Import process
Before File
Import
After File
Import
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Types of Event Scripts
Event scripts can be single events or multiaction events:
Single events consist of a single event and contain no subevents.
Multiaction events consist of subevents, and each subevent can consist of other
events and actions. On completion of the subevents, the event is completed. For
example, the ImportAction event consists of several subevents that must be
processed before the event is completed, as described in the ImportAction
Subevents topic on the next page.
Single events
Multiaction events
Types of Event Scripts
Multiaction events
Single event s
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
ImportAction Subevents
When you perform ImportAction, the following subevents are processed in this order:
1. StartProcessStarts the import process.
2. StartDeleteProcessDeletes existing files and, when you select the Replace import
type, it deletes the previously imported data.
3. StartImportProcessCopies or moves the original file to the archive. It consists of
the following events and actions:
- Event: BefFileImport
- ArchiveItemAction: AftAddItem
- Event: AftFileImport
- ArchiveItemAction: AftCopyFiles
1. StartProcess
2. StartDeleteProcess
3. StartImportProcess
4. StartLogicProcess
5. StartMapProcess
6. PostWorkToMainProcess
7. EndProcess
ImportAction Subevents
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. StartLogicProcessCreates additional calculated amounts and adds records to the
temporary table. It consists of the following events:
- Event: BefProcLogicGrp
- Event: AftProcLogicGrp
5. StartMapProcessRuns the mapping process by dimension calculation order. It
consists of the following events:
- Event: BefProcMap (by number and order of dimensions)
- Event: AftProcMap (by number of order of dimensions)
6. PostWorkToMainProcessPosts the temporary table to the Main Data Segment
Table.
7. EndProcessEnds the process.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Event Script Parameters
Each FDM event script has a set of parameters. You can use these parameters within
the script instead of calling the FDM function, method, or property that returns the same
value.
For example, the parameter strLoc contains the name of the active FDM location, and is
more efficient than using the API.POVMgr.PPOVLocation property to return the FDM
location.
Examples of event script parameters:
BefImportMap(strLoc, strType, strFile)
BefCopyMap(strLoc, strTargLoc, strType)
BefValidate(strLoc, strCat, strPer)
AftValidate(strLoc, strCat, strPer, lngProcState)
AftLoad(strLoc, strCat, strPer, strTCat, strTPer, strFile)
Event Script Parameters
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Event Scripts
To create event scripts in Workbench:
2. In Script Editor, expand the Event folder.
3. Double-click the event for which you want to develop a script.
The script window is displayed.
Creating Event Scripts
Script name
Documentation
Parameters
Script lines
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Changing Import Formats Dynamically
You can use the BefFileImport event to dynamically change the import format for a
location. Each location is assigned one default import format. For the example on the
slide, the default import format for Iowa is IowaIS. If a location has two import formats
for example, one for the balance sheet and one for the income statementyou can use
the event script to change the import group based on the file that you import.
NOTE: Since the import script checks the file name before the import process,
Before File Import (BefFileImport) is the appropriate event for this task.
Changing Import Formats Dynamically
Default import format
for Iowa location
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Changing Import Formats Dynamically: Example
For the example on the slide, the script changes the import format group based on the
data file name. To implement this script, create two import formats. Assign one import
format (Income Statement) as the default import format group for the location, and leave
the other format unassigned.
When you import the file BS.txt (balance sheet file), the event script checks the file
name, detects that it contains the characters BS, and overrides the default import format
group with the balance sheet import format group.
Changing Import Formats Dynamically: Example
Data file name parameter for the import.
The PblnImportGroupOverride and
PstrImportGroup lines override the
assigned import format group.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Changing Other Location Attributes Dynamically
The following table lists events and properties for changing location attributes:
Event Name FDM Properties Purpose
BefFileImport RES.PblnImportGroupOverride=True
RES.PstrImportGroup=NewImportFormat
Change the import format
group before import.
BefProcLogicGrp RES.PblnLogicGroupOverride =True
RES.PstrLogicGroup =NewLogicGroup
Change the logic group
before processing logic.
BefConsolidate RES.PblnValEntGroupOverride =True
RES.PstrValEntGroup=NewEntityGroup
Change the validation
entity group before
consolidating.
BefCheck RES.PblnValRuleGroupOverride=True
RES.PstrValRuleGroup=NewRuleGroup
Change the validation rule
group before running the
Validation report.
Changing Other Location Attributes Dynamically
In addition to using event scripts to change import formats, use
event scripts to dynamically change other location attributes,
such as the following:
Validation groups
Validation rules
Logic groups
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Describe event scripts
Create event scripts
Change import formats dynamically
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
A P P E N D I X A

Setting Up Multilanguage Support A
Objectives
Describe multilanguage support in FDM
Select the default language in application and user settings
Set decimal formatting options
Create reports for multiple languages
The information in this appendix applies only to localized releases of FDM.
The list of supported languages for all EPM System products is included in
the Oracle Hyperion Enterprise Performance Management System
Certification Matrix.
FDM Release 11.1.2 supports the following languages: French, Italian,
German, Brazilian Portuguese, Japanese, Korean, Simplified Chinese,
Traditional Chinese, Russian, Turkish, Dutch, Danish, Finnish, and
Swedish.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Appendix A Setting Up Multilanguage Support
A-2 Financial Data Quality Management 11.1.2 Administration
About Multilanguage Support
When you log on to FDM, the language that is displayed for the user-interface (UI)
elements depends on settings in the FDM application, FDM user setting, operating
system, and Internet Explorer.
FDM translates most of the Web page based on the FDM language settings. For the
example shown on the slide, you select the German language setting, and the Web page
displays most of the UI elements (menu commands, Workflow commands, tabs) in the
selected language. Some UI elements, like the Browse button, are components of the
operating system, and are displayed in the language of the operating system. Other UI
elements are never translated, such as adapter names and dimension names.
Copyright 2011, Oracle and/or its affili ates. All ri ghts reserved.
About Multilanguage Support
Browse button: Defined
by the operating system
Adapter name:
Does not translate
Web page: Defined by the
user language setting in FDM
Example of FDM Web page in German
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Financial Data Quality Management 11.1.2 Administration A-3
The Multi-Language Support chapter in the Oracle Hyperion Financial Data Quality
Management, Fusion Edition, Configuration Guide Release 11.1.2 includes a list of the
UI elements and the language setting that control the translation. Some UI elements and
the language setting that controls the translation in the FDM Web client and in
Workbench are listed in the following table:
The user-defined elements (dimension aliases, reports, and templates) are globally
defined by the FDM administrator. For example, if the administrator defines the
dimension aliases for the application in German, all users see the dimension aliases in
German.
FDM always formats dates in error logs in the ISO format (yyyy-mm-dd). This format
ensures that dates do not change when you change your language setting.
UI Element FDM Web Client Workbench
Logon page Internet Explorer Operating system
All other Web pages FDM user setting Not applicable
Dimension aliases User-defined User-defined
Reports User-defined User-defined
Templates User-defined Not applicable
Dimension names Do not translate Do not translate
Adapter names Do not translate Do not translate
Browse button Operating system Operating system
OK and Cancel buttons in
message dialog boxes
Operating system Operating system
Dates in error logs International Standard
Format (ISO)
ISO
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Changing Language Settings in FDM
Administrators set the default language for the FDM application, and users can override
the default setting. For example, after the administrator selects English for the
applications language setting, users can change their language setting to German or
French to override the default language and display the UI elements in their selected
language.
To change the default language setting for FDM applications:
1. In the FDM Web client, select Administration, and then Web Settings.
The General tab of the Web Settings window is displayed.
2. In the Select your default Language list, select a language.
3. Click Save.
Changing Language Settings in FDM
The users language setting overrides the applications
language setting.
Application setting User setting
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
To change the language setting for users:
1. In the FDM Web client, select Tools, and then User Settings.
The General tab of the User Settings window is displayed.
2. In the Language list, select a language.
3. Click Save.
The users language setting overrides the applications language
setting.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Changing Browser Language Settings
The FDM Web Logon window is displayed in the language that is defined by your
Internet Explorer language settings.
To change the browser language settings:
1. Launch Internet Explorer, and select Tools, and then Internet Options.
The General tab of the Internet Options dialog box is displayed.
2. Click Languages.
The Language Preference dialog box is displayed.
3. Click Add.
The Add Language dialog box is displayed.
4. In the Language list, select a language, and click OK.
Changing Browser Language Settings
You can change the language that is displayed in the FDM Web
Logon window.
FDM Web
Logon window
in German
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
5. In the Language Preference dialog box, select the language, and click Move Up until
the language is first in the list.
6. Click OK twice to close the dialog boxes.
7. Exit Internet Explorer.
When you launch the FDM Web client, the Logon window is
displayed in the selected language setting.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Setting Decimal Formatting Options
Because FDM supports language localization and regional data, time, and number
formats, you must ensure that decimal formatted-related options are set.
Two precepts govern decimal handling in FDM:
1. The relational database that serves as the FDM repository requires that decimal data
be formatted without a thousands separator and with period decimal separators.
This precept implies that, when the FDM application server decimal format specifies
a character other than a period as the decimal separator, you must set the Decimal
Replacement configuration option in FDM. The option ensures that the decimal-
separator character is converted to a period before the data load.
Setting Decimal Formatting Options
Select Start, then Control Panel, and then Regional and
Language Options to specify regional settings.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
2. The selected region for standards and formats on the FDM application servers
determines which characters are designated as the thousands and decimal
separators. This region impacts decimal-formatted data in imported data files, as well
as the default decimal format that is used to create export files and load target
systems.
This precept implies that you must take additional steps when the decimal format for
the application server differs from the decimal format for the import data file or from
the format expected by the target system.
For example, if you import a data file with English-formatted decimals into FDM
running on a French-locale application server, you must use an import script or the
Fill=UStoEuro expression to convert the decimals to the French format (decimal
separator is a comma). Also, to export from the French-locale application server and
load a target system that expects English-formatted decimals, either the target
system must implement its own conversion mechanism, or you must use an FDM
script to perform the output conversion before loading the data to the target system.
To set decimal formatting options:
1. Select Start, then Control Panel, and then Regional and Language Options.
The Regional and Language Options dialog box is displayed.
2. On the Regional Options tab, select a language.
The number, currency, time, short date, and long date formatting
options for the selected language are displayed.
3. Click Customize.
The Numbers tab of the Customize Regional Options dialog box is
displayed.
4. In the Decimal symbol list, select the decimal format, and click OK twice to close the
dialog boxes.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Reports for Multiple Languages
FDM includes many predefined audit, log, system, and process management reports.
The reports are distributed only in English, but you can copy and translate the reports
into multiple languages.
Overview of tasks to create reports for multiple languages:
1. In Workbench, replicate the English folder structure below a language folder.
2. Copy the English version of the report to the new folder structure.
3. Translate the report text.
Creating Reports for Multiple Languages
You can make reports available in multiple languages.
Two Check reports
translated into German
Reports window in a
German language setting
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You must first replicate the English folder structure below a language folder. You can
replicate any number of folders and reports. For the example on the slide, you replicate
the Process Explorer and Check Reports folders below the Deutsch (German) folder.
You copy the English version of two Check reports to the German version of the Check
Reports folder, and then translate the reports into German. When users with a German
language setting open the Reports window in the FDM Web client, they can view the
English reports and the reports that you translated into German.
To replicate folders for reports:
1. In Workbench, select the Reports tab.
2. Right-click the language folder, and select Add Report Group.
The Add Report Group dialog box is displayed.
3. In the Description box, enter the report group name.
You can enter the report group name in any language.
4. In the Sequence box, enter a sequence number.
The sequence number determines the order in which the folders
are displayed.
5. In the Security Level list, select the security level for the report group.
6. Click OK.
To copy English reports to a language folder structure:
1. In Workbench, select the Reports tab, and expand the English folder.
The subfolders with the English reports are displayed.
2. Expand a subfolder of reports.
The reports in the folder are displayed.
3. Right-click a report name, and select Copy Report.
4. Expand a different language folder.
The subfolders for the reports are displayed.
5. Right-click a subfolder name, and select Paste Report.
The English version of the report is copied to the subfolder.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Translating Reports
You can replace any field that is hard coded in reports with translated text. Report fields
that are pulled from the database cannot be translated.
To translate reports:
1. In Workbench, select the Reports tab, and expand the language folder and subfolder.
The reports in the subfolder are displayed.
2. Right-click a report name, and select Design Report.
The report opens in the FDM Reporting window.
3. Translate any of the fields in the report that are hard coded.
Translating Reports
You can replace text in reports with translated text.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
NOTE: FDM reports are designed with ActiveReports, a third-party software
tool. Refer to the http://www.datadynamics.com Web site for product
details and to download the ActiveReports product documentation.
4. Click Save, and close the report.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Selecting Validation Reports
You can select a translated report and set it as the default validation report for the
selected language. For the example on the slide, the translated Check report is set as
the validation report for users with the German language setting. When these users run
the Check task, FDM opens the translated Check report from the German folder. If the
German version of the report is not set as the default validation report, FDM opens the
English version of the report.
To select validation reports:
1. In Workbench, select the Reports tab, and expand the language folder and subfolder.
The reports in the subfolder are displayed.
2. Right-click a report name, select Set as Validation Report, and click Yes for the
confirmation prompt.
The report is displayed in the folder structure with a bold font.
Selecting Validation Reports
Each language setting can have a default validation report.
Set the report as the default
validation report f or users with
a German language setting.
Check task in a German language setting
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
Describe multilanguage support in FDM
Select the default language in application and user settings
Set decimal formatting options
Create reports for multiple languages
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
A p p e n d i x B

ERP Integrator B
Objectives
At the end of this appendix, you should be able to:
Describe ERP Integrator
Extract GL metadata and data from ERP source systems
Drill through to the ERP source system with ERP Integrator
Write back budget data from EPM target applications
Extract HR metadata and data from the PeopleSoft Human Capital
Management source system
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Appendix B ERP Integrator
B-2 Financial Data Quality Management 11.1.2 Administration
About ERP Integrator
ERP Integrator is a module of FDM that enables you to perform the following tasks:
Integrate metadata and data (including HR data) from an ERP source system into an
EPM target application.
Drill through from the EPM target application and view data in the ERP source
system.
Write back budget data to the source system from any Planning, Essbase ASO, or
Essbase BSO application.
About ERP Integrator
ERP Integrator is an add-on module of FDM that enables you
to integrate an ERP source system into an EPM target
application.
EPM Target
Application
ERP Integrator
ERP Source
System
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Financial Data Quality Management 11.1.2 Administration B-3
Supported Systems
ERP Integrator supports the following source systems and target applications:
Source Systems
For GL data:
- PeopleSoft Enterprise Financial Management 9.0
- PeopleSoft Enterprise Financial Management 9.1
- Oracle E-Business Suite 11
- Oracle E-Business Suite 12
For HR data:
- PeopleSoft Human Capital Management (HCM) 9.0
Supported Systems
Source Systems
General Ledger: PeopleSoft Enterprise Financial Management
9.0 and 9.1, Oracle E-Business Suite 11 and 12
Human Resource Data: PeopleSoft Human Capital
Management 9.0
Target Applications
Planning
Planning enabled for Public Sector Planning and Budgeting
Financial Management
Essbase ASO and Essbase BSO
FDM
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For information on supported technologies for each source system, see the Oracle
Hyperion Enterprise Performance Management System Certification Matrix.
Target Applications
Planning
Planning enabled for Public Sector Planning and Budgeting
Essbase ASO and Essbase BSO
FDM
For detailed information on upgrading EPM System products, including ERP Integrator,
see the Oracle Hyperion Enterprise Performance Management System Installation and
Configuration Guide.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
ERP Integrator Process
Here is a high-level overview of the ERP Integrator process:
1. Extract GL metadata and data from the ERP source system into the EPM target
application.
2. Drill through from the EPM target application to view data in the ERP source system.
3. Write back budget data from the EPM target application to the GL source system.
4. Extract HR data from the ERP source system to the EPM target application.
ERP Integrator Process
.
ERP
Source
System
EPM
Target
Application
ERP Integrator
1
2
3
4
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
ERP Integrator Architecture: Loading Metadata and Data
The following is the ERP Integrator architecture for loading metadata and data:
1. As a module of FDM, ERP Integrator is the key application for integrating ERP
systems with EPM applications. ERP Integrator fits within the EPM System
architecture and is accessed through Oracle Enterprise Performance Management
Workspace, Fusion Edition (Workspace) which uses Shared Services to authenticate
users. The key to its integration lies within its underlying engine, which is Oracle Data
Integrator.
2. ERP Integrator sits on top of Oracle Data Integrator and enables the movement of
data and metadata into Oracle Hyperion EPM applications.
3. If you use FDM and ERP Integrator together:
Metadata is loaded through Oracle Hyperion Enterprise Performance
Management Architect, Fusion Edition (Performance Management Architect) for
the classic application.
ERP Integrator Architecture:
Loading Metadata and Data
.
E-Business
Suite
Planning
Financial
Management
E-Business
Suite
E- Business
Suite General
Ledger
PeopleSoft
Enterprise
Financial
Management
PeopleSoft
Human
Capital
Management
Essbase
EPM Applications
Metadata and Data Load
Data Load
.
FDM
ERP Integrator
Data Load
Oracle Data
Integrator
Smart
View
Financial
Reporting
Metadata and
Data Load
1
3
Metadata Load
3
EPMA for Classic application
2
3
3
2
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Data is loaded in FDM through ERP Integrator, and then the flat files in FDM push
the data to the EPM target application.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
ERP Integrator Architecture: Drilling Through and Writing Back
Budget Data
The following is the ERP Integrator architecture for drilling through and writing back
budget data:
1. You can drill through from Planning, Financial Management, Smart View, Oracle
Hyperion Financial Reporting, Fusion Edition (Financial Reporting), and Hyperion
Enterprise (Release 6.5.1 or later) to view source data.
NOTE: For Smart View and Financial Reporting, you can drill through only if
the data source is Financial Management, Planning, or Essbase.
2. You can write back budget data from the EPM target system to the ERP source
system.
ERP Integrator Architecture:
Drilling Through and Writing Back Budget Data
E-Business
Suite
E-Business
Suite
E- Business
Suite General
Ledger
PeopleSoft
Enterprise
Financial
Management
PeopleSoft
Human
Capital
Management
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For detailed information on prerequisites for configuring ERP Integrator, see the Oracle
Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle
Applications Administrator's Guide, Release 11.1.2.1.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Security in ERP Integrator
ERP Integrator roles and tasks per role are listed in the following table:
ERP Integrator Role Tasks per Role
Administrator Manages applications and performs any action.
Drill Through Controls the ability to drill through to the source system.
Create Integration Controls the ability to create metadata and data rules. Users with
this role can perform the following tasks:
Create, delete, and edit dimension rules and data rules
View process details
Perform calendar mapping
Security in ERP Integrator
You can assign ERP Integrator roles to one of the following
security roles:
Administrator
Drill Through
Create Integration
Run Integration
GL Write Back
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Run Integration Controls the ability to run existing metadata and data rules. Users
with this role can perform the following tasks:
Run dimension rules or data rules
View process details
GL Write-Back Controls the ability to create and run write-back data rules to ERP
source system.
ERP Integrator Role Tasks per Role
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
ERP Integrator User Interface Elements
The common user interface elements on the ERP Integrator pages are described in the
following table:
Button Description
Customize your views.
Detach the column grid to display the columns in their own
windows.
Refresh the data.
ERP Integrator User Interface Elements
ERP Integrator pages have the following common elements:
View
Detach
Refresh
Filter
Explore
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Filter the row, enter text, and filter rows for a specific column.
All text you enter is case-sensitive.
Search for artifacts on a page, such as a target application,
member, or GL responsibility.
Button Description
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Accessing ERP Integrator
You access ERP Integrator from Workspace.
To access ERP Integrator:
1. Ensure that Shared Services and EPM Workspace Server are running.
2. Start the Hyperion ERPI-Web Application process by performing one of the following
actions:
In the Services panel, start Hyperion ERPI - Web Application.
Select Start, then Programs, then Oracle EPM System, then Performance Management
Integrator, and then Start aif (application integration framework).
3. Ensure that Performance Management Architect is running.
4. Optional: Depending on your integration with ERP Integrator, start the following
services:
Accessing ERP Integrator
In Workspace, select Navigate, then Administer, and then
ERP Integrator.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Planning
FDM
Essbase (required for Planning)
5. Open Internet Explorer, and enter the Workspace URL to launch Workspace. By
default the URL is http://<servername>:19000/workspace.
6. Enter your user name and password, and click Log On.
7. In Workspace, select Navigate, then Administer, and then ERP Integrator.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Extracting GL Metadata and Data: Configuring ERP Integrator
You configure ERP Integrator to extract GL metadata and data from the ERP source
systems.
The following are guidelines for extracting GL metadata and data:
Assigning dimension and member properties: For each required dimension in
Planning and Financial Management, you must assign specific member properties.
For detailed information on required dimensions in Planning and Financial
Management, assigning specific member properties, and how dimensions are
processed, see the Oracle Hyperion Financial Data Quality Management ERP
Integration Adapter for Oracle Applications Administrator's Guide, Release 11.1.2.1.
Managing hierarchies: When managing hierarchies for the GL integration process,
keep the following points in mind:
- You create or replace hierarchies in the target application.
Extracting GL Metadata and Data:
Configuring ERP Integrator
You configure ERP Integrator by performing the following tasks:
1. Register an ERP source system.
2. Enable FDM applications.
3. Register target applications.
4. Select source accounting entities.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
- Selecting hierarchies is optional. However, if you do not select a hierarchy, you
must determine how to handle members. For example, decide whether you want
to create children of a selected node as orphans (for Performance Management
Architect only) or whether you want to leave them out.
- You can define two types of hierarchies: one-to-one, many-to-one.
For more information on loading source system hierarchies into EPM dimensions,
see the Oracle Hyperion Financial Data Quality Management ERP Integration
Adapter for Oracle Applications Administrator's Guide, Release 11.1.2.1.
You configure ERP integrator, by performing the following tasks:
1. Register an ERP source system.
2. Enable FDM applications.
3. Register target applications.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Registering ERP Source Systems
Before using ERP Integrator, you must register your source systems.
To register source systems:
1. In the Tasks pane, under Setup, select Source System.
The Source System page is displayed.
2. Click Add.
3. Enter the following source system details:
In the Name box, enter the name of the ERP source system that you want to
register.
Optional: In the Description box, enter a description.
In the Type box, enter the ERP source system type: E-Business Suite, PeopleSoft, or
Fusion.
Registering ERP Source Systems
In the Tasks pane, under Setup, select Source System.
Source System
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. In the EPMA Data Source Name box, enter the EPMA data source name defined
when configuring the Performance Management Architect data source in the
configuration utility.
The import profile uses the data source name to import tables.
5. In the Drill-Through URL box, enter the URL used to launch E-Business Suite or
PeopleSoft and drill through. For example, http://qapache.us.oracle.com:6362.
The URL identifies the URL to use for drilling through. Users can
drill through to Oracle General Ledger or PeopleSoft General
Ledger from an EPM System application that displays data
loaded from the source system.
6. In the ODI Details region, enter the following details:
In the Context Code box, enter the name of the context defined in Oracle Data
Integrator. A context groups the source and target connection information.
In the Repository Code box, enter the Oracle repository name.
In the Agent Host box, enter the name of the machine where Oracle Data
Integrator is installed.
In the Agent Port box, enter the port number of the machine where Oracle Data
Integrator is installed.
In the User box, enter the database schema user name used to access the Oracle
Data Integrator master repository.
In the Password box, enter the database schema password used to access the
Oracle Data Integrator master repository.
In the JDBC Driver box, enter the name of the driver that connects to an Oracle
database. For example, oracle.jdbc.driver.OracleDriver.
In the JDBC URL box, enter the name of the URL that connects to an Oracle
database. For example,
jdbc:oracle:thin:@ServerName.oracle.com:PortNumber:sp3.
In the Repository User box, enter the Oracle Data Integrator master repository
user name.
In the Repository Password box, enter the Oracle Data Integrator master
repository password.
In the Log Level box, enter the level of detail that you want to display in logs.
Oracle Data Integrator supports log levels 0 through 5, where 5 is the most
detailed. If you want to save space, use a lower log level.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
In the Metadata Navigator URL box, enter the URL for Oracle Data Integrator
Metadata Navigator tool. You can use Metadata Navigator to view process details
and detailed information about Oracle Data Integrator jobs.
7. Click Save.
8. Click Initialize to bring all metadata from the ERP source system into the ERP
Integrator.
Retrieving metadata enables you to define dimension mappings
between the ERP source system and EPM target application.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Enabling FDM Applications
Applications registered in FDM but not in Shared Services must be registered as target
applications in ERP Integrator. You do that by enabling FDM applications.
After enabling the applications, you can define import formats, locations, and data rules
in ERP Integrator.
To enable FDM applications:
1. In the Tasks pane, under Setup, select FDM Application.
The FDM Application page is displayed.
2. Click Add and enter the name, user name, and password for the FDM application
schema.
3. Select Remote Database if FDM accesses a different database than ERP Integrator.
4. Optional: Enter a SQL server database name.
5. Click Test Connection and then, on successful connection, click Save.
Enabling FDM Applications
In the Tasks pane, under Setup, select FDM Application.
FDM Application
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Registering EPM Target Applications
Before you can extract data from the ERP source systems into target applications, you
must register the target applications with ERP Integrator.
When you register target applications, you must select metadata and dataload methods,
a default language, and a drill region.
To register a target application:
1. In the Tasks pane, under Setup, select Target Application.
The Target Application page is displayed.
2. Click Add.
The Select Application page is displayed.
3. In the Application Type list, select an application type and an application, and click
OK.
Registering EPM Target Applications
In the Tasks pane, under Setup, select Target Application.
Target Application
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. In the Default Language list, select a language.
NOTE: For Planning applications, the language you select is mapped to the
Default member in the Alias dimension. All other languages are
mapped to the Alias dimension as long as the languages in the
target and source match exactly. For Financial Management
applications, the language you select as the default language is
loaded. All other languages are ignored.
5. In the Metadata Load Method list, select one of the following metadata-load methods:
Select EPMA to load metadata into the Performance Management Architect
interface tables through the import profile.
Select Classic to load metadata directly to the Classic application.
Select Not Applicable for applications registered in FDM and where no metadata is
required to be extracted from the source.
6. In the Data Load Method list, select one of the following data-load methods:
Select EPMA to load data through the interface tables and automatic data
synchronization.
Select Classic to load data directly into the EPM application.
Select FDM to load data into a data file, which is pulled into FDM.
7. In the Create Drill Region list, select Yes to create a drill region; otherwise, select No.
A drill region includes the following:
Account/Scenario/Year/Period for Financial Management
Entity/Account/Scenario/Year/Period for Planning
A URL to get back to either FDM or ERP Integrator
Name of the region
8. Define application dimension details for Essbase and Public Sector Planning and
Budgeting applications.
9. Click Save.
10. Confirm that the application registered successfully.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Selecting Source Accounting Entities
Source accounting entities are used to specify the E-Business Suite ledgers or
PeopleSoft business units to be included in the integration. Source accounting entities
include the following:
Oracle E-Business Suite General Ledger
PeopleSoft General Ledger
When selecting source accounting entities in E-Business Suite General Ledger, you can
also assign users GL responsibility. GL responsibility provides the authentication
required for ERP Integrator to drill through to the E-Business Suite journal summary
page.
Selecting Source Accounting Entities
In the Tasks pane, under Setup, select Source Accounting
Entities.
Source Accounting
Entities
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
To select source accounting entities for E-Business Suite source
systems:
1. In the Tasks pane, under Setup, select Select Source Accounting Entities.
The Source Accounting Entities page is displayed.
2. In the Source System type list, select the source system type.
3. In the Source System list, select a source system.
The source accounting entities for the source system are
displayed.
4. In the Select column, click the check box to select the appropriate accounting entity
and its associated chart of accounts, currency, and calendar.
5. Optional: Assign a GL responsibility.
In the GL Drill Through Responsibility box, enter a name for the GL responsibility,
or click Browse to display the GL Responsibilities page.
In the GL Responsibility Name box, enter the GL Responsibility name or click Go to
display all GL responsibility names.
Select a GL Responsibility, and click OK to display it for the ledger.
6. Click Save.
To select source accounting entities for PeopleSoft source systems:
1. Select a source accounting entity, a source system type, and a source system. For
details, see To select source accounting entities for E-Business Suite source
systems in this topic.
2. In the Select column, click the check box to select the appropriate business unit and
its currency.
3. Click Save. O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Extracting GL Metadata and Data: Setting Up ERP Integrator
After configuring the ERP Integrator, you set up ERP Integrator by performing the
following tasks:
1. Create import formats.
2. Define locations.
3. Define metadata rules.
4. Create period mappings.
5. Create category mappings.
6. Define data rules.
Extracting GL Metadata and Data:
Setting Up ERP Integrator
You set up ERP Integrator by performing the following tasks:
1. Create import formats.
3. Define metadata rules.
4. Create period mappings.
6. Define data rules.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Creating Import Formats
You create import formats to define a relationship between the source system and target
application. You do that by mapping source segments or chartfields to target dimensions.
To create import formats, you define import format mappings for the metadata.
Import format mappings can be one of the following:
One-to-one mapping, also known as single-segment mapping, defines simple one-
to-one mappings between source and target dimension members. Each member in
the source is created as a single member in the target. The graphic on the slide
shows a one-to-one mapping where the company, account, department, and product
in the source system are mapped to entity, account, department, and product
respectively in the target application.
Many-to-one mapping defines multiple segments or chartfields from the source to a
single EPM dimension. Up to five segments or chartfields may be concatenated into
the target dimension.
Creating Import Formats
ERP Source System
Company
Account
Department
Product
EPM Target Application
Entity
Account
Department
Product
Import
Format
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
NOTE: For budget write-back purposes, you can reverse and reuse mappings
defined for data loading.
To create import formats:
1. In the Tasks pane, under Setup, select Import Format.
The Import Format page is displayed.
2. Click Add.
3. Enter a name and description for the import format.
4. In the Source System list, select the source system.
5. In the Target Application list, select a target application.
6. On the Data Load Mapping tab, perform one of the following actions:
For E-Business Suite source systems: Select one or more GL source segments.
The drop-down list displays all source system segments for the accounting entity
that you selected when you defined the import format details.
For PeopleSoft source systems: Select one or more chartfields, as necessary.
7. Enter the target EPM dimension name.
NOTE: For target applications with the FDM data-load type, enter the
concatenation character.
8. Optional: Repeat steps 6 and 7 if necessary.
9. Click Save.
NOTE: When you define an import format, you can also define import
format mappings from the EPM application for the data write-back
rule.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Defining Locations
A location is a combination of source system, target application, and import format. You
define locations to specify the following:
Where data is extracted from
Where data is loaded to
How data is loaded
Locations enable you to use the same import format for more than one target application
with the same dimensionality. You can create multiple locations with the same import
format.
Locations reduce setup time and ensure consistency of mappings across ERP systems
and EPM applications for different integration tasks.
Defining Locations
A location is a combination of source system, target application,
and import format.
Source system: E-Business Suite
Target application: Financial Management
Import format: CorpLedger
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
To define locations:
1. In the Tasks pane, under Setup, select Location.
The Location page is displayed.
2. Click Add.
3. Enter the name for the location.
4. Click Browse to select an import format.
The source system is automatically populated based on the
import format.
5. Click Browse to select the accounting entity.
NOTE: The functional currency is automatically determined by the source
accounting entity.
6. Click Browse to select the target application.
7. Click Save.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Defining Metadata Rules
After mapping dimensions in the import format, you create metadata rules to select the
dimensions for which you want to extract metadata.
You create metadata rules once and rerun the rules as necessary.
NOTE: You cannot create more than one metadata rule for the same ledger or
business unit for each target application.
To define metadata rules:
1. In the Tasks pane, under Setup, select Metadata.
The Metadata page is displayed.
Defining Metadata Rules
You define metadata rules to extract metadata from the ERP
source system to the EPM target application.
Company
Account
Cost Center
Product
Entity
Account
Department
Product
ERP Source System EPM Target Application
Metadata
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
2. Click Browse to select a location.
The Location page is displayed.
3. Select the location, and click OK.
4. Click Add.
5. Under Dimension Mappings, select a dimension.
NOTE: The dimensions are listed based on the import format defined.
6. Under Mapping Details, perform the following actions:
Optional: Enter a member prefix.
For Planning and Essbase applications, select the time balance property for
Balance Sheet Accounts and for Income Statement Accounts.
NOTE: The time balance property specifies how the value of summary time
periods is calculated. If it is set to Flow, it is an aggregate of all
values for a summary time period as a period total. If it is set to
Balance, it is an ending value in a summary time period as the
period total.
7. Under Hierarchy Region, perform the following actions:
a. Click Add to define the hierarchy region starting parent.
b. Select the Base Hierarchy check box.
c. Select a prefix or suffix for the hierarchy, and enter a prefix/suffix value.
d. Perform one of the following actions:
For Planning applications, select the plan type for Account and Entity
dimensions.
For Financial Management applications, enter the intercompany segment value
details for the Entity dimension.
8. Select one of the following options to process orphan members:
Select Ignore so that no orphan members from the source are extracted.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Select Create as Root Members so that only root members are created. All members
are created at the top level of the hierarchy.
Select Create as children of so that all orphans are placed as children of the selected
member.
9. For Account segments, select one of the following options to handle statistical
account orphans:
Select Ignore so that no orphan members from the source are extracted.
Select Create as Root Members so that only root members are created. All members
are created at the top level of the hierarchy.
Select Create as children of so that all orphans are placed as children of the selected
member.
10. Repeat steps 5 through 9 for each dimension.
11. Click Save.
Executing Metadata Rules
After creating a metadata rule, you execute the rule to push data into the target
application.
To execute metadata rules:
On the Metadata page, click Execute.
The rule is updated and pushes the metadata into the target
application. All submitted rules are processed by Oracle Data
Integrator.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Managing Metadata Rules
You manage metadata rules on the Metadata page.
To manage metadata rules:
On the Metadata page, perform the following actions:
- Click Add to modify metadata rules if the metadata rule is not running.
- Click the Status icon to navigate to the Process Details page.
- Click Delete to delete dimension mappings or hierarchies.
Managing Metadata Rules
Click Delete to delete
a metadata rule.
Click Add to edit
a metadata rule.
Click Status to check the
status of the metadata rule.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Defining Period Mappings
You use period mapping to define mappings between ERP calendars and Period and
Year dimensions of EPM applications.
Mappings can be the following types:
Global mappings are available for all data rules, and eliminate the need to map
individual calendars from ERP systems.
Application-level mappings are available for a particular EPM application.
Adjustment period mappings map the source system adjustment periods to the
EPM target periods.
To define period mappings:
1. In the Tasks pane, under Setup, select Period Mapping.
The Period Mapping page is displayed.
Defining Period Mappings
Before you can define data rules, you must define period
mappings.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
2. Perform one or all of the following actions:
On the Global Mapping tab, perform the following actions:
Click Add.
Select a period key and a prior period key.
Enter a period name, target period month, target period quarter, target period
year, target period day, and year target.
On the Application Mapping tab, perform the following actions:
In the Target Application list, select a target application.
Click Add.
Select the period key.
Enter a target period month, target period quarter, target period year, target
period day, and year target.
On the Adjustment Period Mapping tab, perform the following actions:
In the Source System list, select a source system.
Click Add.
Click Browse to select the source system period key, source system calendar,
and source system adjustment period.
For PeopleSoft source systems, in the GL Period Year box, enter the GL period
year.
Optional: Enter a description.
3. Click Save.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Defining Category Mappings
A category mapping defines categories of data from a source system and maps them to
the Scenario dimension of EPM applications (Financial Management, Planning,
Essbase, and FDM registered).
Mappings can be the following types:
Global mappings map various scenario dimensions to individual mappings.
Application-level mappings map a dimension to a particular EPM application.
To define category mappings:
1. In the Tasks pane, under Setup, select Category Mapping.
The Category Mapping page is displayed.
Defining Category Mappings
Category mappings map source system data to a specific
target EPM Scenario dimension member.
ERP Source System
EPM Target Application
Actual Scenario
Current Scenario
Financial
Management
Planning
FDM
Essbase
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
2. Perform one or both of the following actions:
On the Global Mapping tab, click Add, enter a category name and description,
select the category frequency, and enter the target category.
NOTE: The target category is the Scenario dimension in the application.
Select the Application Mappings tab. In the Target Application list, select a target
application, click Add, select a category, and click Browse to select a target
category.
3. Click Save.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Defining Data Rules
A data rule is specific to a ledger (E-Business Suite) or a business unit (PeopleSoft). You
define data rules to extract data from the ERP source system.
You can create multiple data rules for a target application to enable you to import data
from multiple sources into a target application.
You perform the following tasks to define data rules:
1. Create member mappings.
2. Create data rules by defining source filter options and selecting target application
options.
3. Execute the data rules.
Creating Member Mappings
Member mappings define the relationship between source dimension members and
target dimension members within a single dimension.
Defining Data Rules
You define data rules to extract data from the ERP source
system.
EPM Target
Applications
ERP Source
Systems
Data
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
You must create a member mapping for each target dimension.
The following three types of member mappings are available:
ExplicitThe source value is matched exactly and replaced with a target value.
BetweenThe range of source values is replaced with one target value.
LikeThe string in the source value is matched and replaced with the target value.
To create member mappings:
1. In the Tasks pane, under Data Load, select Member Mapping.
The Member Mapping page is displayed.
3. In the Dimensions list, select a dimension.
4. In the Type list, perform one of the following actions:
Select Explicit, click Add, and select a source and target value.
Select Between or Like, click Add, and enter a source value, target value, rule name,
and rule description.
5. Repeat steps 3 and 4 to create member mappings for other dimensions.
6. Click Save.
Creating Data Rules
After creating member mappings, you define data rules to filter the data that you want to
extract from the E-Business Suite or PeopleSoft source system, and to define the target
application options.
To create data rules:
1. In the Tasks pane, under Data Load, select Data Load.
The Data Load page is displayed.
2. Click Add.
3. Under Details, perform the following actions:
a. Enter a name for the data rule.
b. In the Category list, select a category.
c. Optional: Enter a description.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
4. Under Source Filters, perform one of the following actions:
For Oracle E-Business Suite, select the following source data:
Amount Type: Monetary amounts, statistical amounts, or both monetary and
statistical amounts.
Include Zero Balance: Yes or No.
Include Adjustment Periods: Yes or No.
Amount for Balance Sheet Accounts: YTD or Periodic.
Amount for Income Statement Accounts: YTD or Periodic.
Balance Method: Standard or Average.
Balance Type: Actual, Budget, or Encumbrance.
Segment Values: All or Selected.
For the PeopleSoft source system, select the following source data:
Amount Type: Monetary amounts, statistical amounts, or both monetary and
statistical amounts
Include Adjustment Periods: Yes or No.
Amount for Balance Sheet Accounts: YTD or Periodic.
Amount for Income Statement Accounts: YTD or Periodic.
Ledger Group: Select a ledger group.
Ledger: Select a ledger.
Book Code Values: Select book code values.
Budget Values: Select budget values.
5. Under Target Options, perform one of the following actions:
For EPM Planning applications, select the plan type, data synchronization
method, and exchange rate options.
For EPM Financial Management applications, select the data synchronization
method and exchange rate options.
For Classic Planning applications, select the plan type and exchange rate
options.
For Classic Financial Management applications, select the exchange rate
options.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
6. Click Save.
For more information on data rules, see the Oracle Hyperion Financial Data Quality
Management ERP Integration Adapter for Oracle Applications Administrator's Guide,
Release 11.1.2.1.
Executing Data Rules
After creating a data rule, you execute it to load updates and push data to the target
application. All submitted rules are processed by Oracle Data Integrator.
To execute data rules:
1. On the Data Load page, click Execute.
The Execute Rule page is displayed.
2. Select the following options to execute data rules:
Import from Source: Select this check box if you want to load the source data into
the ERP Integrator interface tables.
Export to Target: Select this check box if you want to load data into the target
application.
Start and End Periods: Specify a range of dates for year, quarter, month, and so
on.
Include Exchange Rates: Select this check box if you want to include exchange
rates.
Execution Mode: Select Snapshot to extract everything for the selected source set
for an entire period, or select Incremental to extract only those records that were
added after the prior data extract.
3. Click Run.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Managing Data Rules
You manage data rules on the Data Load page.
To manage data rules:
On the Data Load page, perform one or more of the following actions:
Click Add to add data rules. You can modify rule details if the data rule is not running.
Click the Status icon to navigate to the Process Details page to check the status of
data rules.
Click Delete to delete data rules. You can delete data rules created in ERP Integrator.
Only the data rule is removed; no metadata rules are removed. You cannot delete
data rules if they are running. After deleting data rules, you can delete a source
system.
Managing Data Rules
Click Add to
edit a data rule.
Click Status to check the
data rule status.
Click Delete to
delete a data rule.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through to View Source Data
ERP Integrator enables you to drill through from EPM target applications to view data in
the source system. You can drill through to the source system by using ERP Integrator or
FDM from Financial Management, Planning, Smart View, and Financial Reporting.
NOTE: For Smart View and Financial Reporting, you can drill through only if the data
source is Financial Management or Planning.
If you loaded data through ERP Integrator or FDM, you can click the drillable cell in the
EPM target application to display an ERP Integrator landing page.
A drillable region is automatically created and loaded to either Financial Management or
Essbase (for Planning) when data is loaded from ERP Integrator or FDM.
Drilling Through to View Source Data
Data
Staging
Table
Structure
Similar to
OGL Table
Oracle GL Account
Dimension Mapping
Table
URL with
Parameters
EPM Target
Applications
ERP Integrator or
FDM Landing Page
General Ledgers
Journal Entry Lines
(EBS/PSFT)
Drill Through
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The drillable region enables Financial Management, Planning, Smart View, and Financial
Reporting to drill through to the source data from the ERP Integrator or FDM landing
page.
The drillable region includes the following:
For Financial Management, it includes the Account, Scenario, Year, and Period
dimensions.
For Planning, it includes the Entity, Account, Scenario, Year, and Period dimensions.
It includes a URL to return to the ERP Integrator or FDM landing page.
It includes a region name.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from Financial Management
In Financial Management, drillable cells are identified by a blue tick mark in the upper-left
corner.
To drill though from Financial Management:
1. In the Financial Management data form or data grid, right-click the drillable cell.
2. Select Drill Through to ERP Integrator to display the ERP Integrator landing page.
Drilling Through from Financial Management
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from Planning
In Planning, drillable cells are identified by a blue tick mark in the upper-right corner.
To drill through from Planning:
1. In the Planning Web form, place the cursor on the drillable cell and confirm that the
following message is displayed: This cell is drillable.
2. Click once in the cell.
3. Click one more time to display a spreadsheet-like icon.
4. Click the spreadsheet icon to drill through to the ERP Integrator landing page.
Drilling Through from Planning
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from Smart View
In Smart View, you use custom formatting to identify drillable cells.
To drill through from Smart View:
1. Place the cursor on the drillable cell, and confirm that following message is
displayed: Drill Through: Drill to ERPI.
2. Click the cell to drill through to the ERP Integrator landing page.
Drilling Through from Smart View
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from Financial Reporting
In Financial Reporting, drillable cells are identified by a hyperlink.
To drill through from Financial Reporting:
Click the hyperlink amount to drill through to the ERP Integrator landing page.
Drilling Through from Financial Reporting
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from the ERP Integrator Landing Page
The ERP Integrator landing page acts as a gateway to the data in the source system.
You use the page to drill through from Financial Management, Planning, Financial
Reporting, or Smart View to the Oracle or PeopleSoft general ledger.
The ERP Integrator landing page displays GL accounts and the hyperlinked balances
that were used to populate the cells in the EPM target application. You can drill through
from an ERP Integrator page to the E-Business Suite or PeopleSoft landing page.
To drill through from the ERP Integrator landing page:
Click the hyperlinked GL balances to drill through to the E-Business Suite or
PeopleSoft landing page.
Drilling Through from the
ERP Integrator Landing Page
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from the E-Business Suite Landing Page
The E-Business Suite landing page displays the account balances for an account after
logon validation.
To drill through from the E-Business Suite landing page:
1. Click the Summary Accounts icon to drill through to the Summary Balances page.
2. Click the hyperlink account on the Summary Balances page to drill through to the
Detail Balances page.
3. Click the Period to Date (PTD) hyperlink on the Detail balances page to drill through
to the Journal Lines page.
E-Business Suite Landing Page
3
2
1
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Drilling Through from the PeopleSoft Landing Page
You can drill through to a PeopleSoft landing page from the ERP Integrator landing page.
When you navigate to the PeopleSoft landing page, the Ledger Inquiry page is displayed
after logon validation. You can drill through from the PeopleSoft landing page to the
Journal Inquiry page.
To drill through from the PeopleSoft landing page:
Click the Detail link.
PeopleSoft Landing Page
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Writing Back Budget Data from EPM Applications
You can extract budget data from EPM source applications and write it back to the ERP
target systems.
The following are guidelines for writing back budget data:
You can extract budget data from the Planning, Essbase ASO, or Essbase BSO
11.1.2.x applications. Applications created in earlier releases are not supported.
You can write back data to Oracle E-Business Suite or PeopleSoft Enterprise
Financial Management.
You can write back only monetary amounts to the general ledger.
You have the option to export data to the ERP system or to extract data only from the
EPM application.
You cannot allocate amounts from one source to multiple targets.
You must have the GL Write-back security role to create data write-back rules.
Writing Back Budget Data from EPM Applications
You can write back budget data from Planning, Essbase ASO,
or Essbase BSO applications to the ERP systems.
EPM Target Applications ERP Source Systems
PeopleSoft
Enterprise
Financial
Management
Oracle E-
Business
Suite
Essbase ASO
Planning
Essbase BSO
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The process for writing back budget data consists of the following tasks:
1. Configure and set up ERP Integrator.
2. Create write-back mappings.
3. Create data write-back rules.
4. Execute data write-back rules.
5. Load data into ERP systems.
6. Manage data write-back rules.
Configuring and Setting Up ERP Integrator
You configure and set up the ERP Integrator by performing the following tasks:
1. Register the ERP source system.
2. Register the target application.
4. Define import formats.
5. Create locations.
6. Define period mappings.
For details about the tasks, see the following topics in this appendix:
Extracting General Ledger Metadata and Data from an ERP Source System:
Configuring ERP Integrator.
Extracting General Ledger Metadata and Data from an ERP Source System: Setting
up ERP Integrator.
Creating Write-Back Mappings
Before creating data write-back rules, you must create write-back mappings. Write-back
mappings map EPM application dimensions to the ERP system segment or chartfield
values.
NOTE: You can use member mappings defined for data loads as long as the
mapping is one-to-one.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
The following types of mappings are available:
Explicit: The source value is matched exactly and replaced with a target value.
Between: The range of source values is replaced with one target value.
Like: The string in the source value is matched and replaced with the target value.
To create write-back mappings:
1. In the Tasks pane, under Data Write-Back, select Write-Back Mapping.
The Write-Back Mapping page is displayed.
3. In the Segments list, select a segment.
4. In the Type list, perform one of the following actions:
Select Explicit, click Add, and select a source and target value.
Select Between or Like, click Add, and enter a source value, target value, rule name,
and rule description.
5. Repeat steps 3 and 4 to create write-back mappings for other segments.
6. Click Save.
Creating Data Write-Back Rules
After creating write-back mappings, you create data write-back rules to filter the data that
you want to extract from the Planning, Essbase ASO, or Essbase BSO applications, and
to define the target application options to load budget data.
You can create data write-back rules for locations whether or not they were already used
for data loading.
To create data write-back rules:
1. In the Tasks pane, under Data Write-Back, select Data Write-Back.
The Data Write-Back page is displayed.
2. Enter the location name or click Browse to select the location.
3. Click Add.
4. Under Details, perform the following actions:
Enter a name.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For Planning applications, select a plan type.
Optional: Enter a description.
5. Under Source Filters, perform the following actions:
Click Add.
In the Dimension Name list, select a dimension.
Click Select to select a filter for the dimension.
The Edit Member page is displayed.
6. Click Browse.
The Member Selector page is displayed.
7. Select a member, and click OK twice.
8. Repeat steps 5 through 7 to select filters for other dimensions.
9. Under Target Option, perform one of the following actions:
For E-Business Suite, select whether you want to a create budget journal. If you
select Yes, select parameters for budget, journal source, and journal category. If
you select No, select parameters for budget and budget organization.
For PeopleSoft Enterprise Financial Management, select a budget scenario,
ledger group, and ledger.
10. Click Save.
Executing Data Write-Back Rules
After creating data write-back rules, you must run them to write back the data from the
EPM applications to the GL system.
To execute data write-back rules:
1. On the Data Write-Back page, click Execute.
The Execute Rule Options page is displayed.
2. Select one or both of the following Execute Rule options:
Select Import from Source to review the information in the staging tables before
exporting the data to the general ledger.
Select Export to Target to transfer the data to the GL.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Loading Data into the ERP Systems
After running the data write-back rules, you must load the data into the ERP system.
To load data into Oracle E-Business Suite:
1. Launch Oracle General Ledger.
2. Run the Journal Import process.
3. Review the journal and budget balances.
For detailed information, see the Oracle General Ledger Users Guide, Release 12.1.
To load data into PeopleSoft Enterprise Financial Management:
1. Launch PeopleSoft General Ledger.
2. Run the Generate Journals process.
3. Define the following options:
Accounting Definition Name: Select HYPDEFN.
Template: Select HYP_STDBUD.
4. Run the process.
5. Review the journal, create balancing entries, and post the journals.
For detailed information, see the PeopleSoft Enterprise General Ledger 9.1 Peoplebook.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Managing Data Write-Back Rules
You manage data write-back rules on the Data Write-Back page.
To manage data write-back rules:
On the Data Write-Back page, perform the following actions:
Click Add to edit the data write-back rule. You can edit the data write-back rule by
modifying the source filters or target options. You cannot edit the plan type or location
after the rule is run.
Click Delete to delete a data write-back rule.
Click the Status icon to navigate to the Process Details page to check the status of a
data write-back rule.
Managing Data Write-Back Rules
Click Status to check
the rule status.
Click Delete to
delete a rule.
Click Add to
edit a rule.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Extracting HR Metadata and Data from PeopleSoft HCM
ERP Integrator extracts HR metadata and data from PeopleSoft HCM to the following
Public Sector Planning and Budgeting models:
Employee
Position
Employee and Position
Before you can extract HR metadata and data, you must perform the following actions:
Run the following processes in PeopleSoft HCM to load future-dated salaries: Copy
Job Data and Load Step Increment.
Define data-load settings in Planning to select data-load members based on driver
dimensions.
Extracting HR Metadata and Data
from PeopleSoft HCM
ERP Integrator enables you to extract HR metadata and data
from PeopleSoft HCM to the Public Sector Planning and
Budgeting applications.
PeopleSoft
Human Capital
Management
(HCM)
ERP Integrator
Public Sector
Planning and
Budgeting
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For more information on the prerequisites, see the Oracle Hyperion Financial Data
Quality Management ERP Integration Adapter for Oracle Applications Administrator's
Guide, Release 11.1.2.1.
The process of extracting HR metadata and data consists of the following tasks:
1. Configure and set up ERP Integrator.
2. Create HR data rules.
3. Execute HR data rules.
4. Manage HR data rules.
Configuring and Setting Up ERP Integrator
You configure and set up ERP Integrator, by performing the following tasks:
1. Register the HR source system.
2. Register the target Public Sector Planning and Budgeting application.
3. Select the source HR business unit.
4. Define import formats.
For details about the tasks, see the following topics in this appendix:
Extracting General Ledger Metadata and Data from an ERP Source System:
Configuring ERP Integrator.
Extracting General Ledger Metadata and Data from an ERP Source System: Setting
up ERP Integrator.
Creating HR Data Rules
Before you can extract HR metadata and data, you must create HR data rules. HR data
rules enable you to load employee and position information from PeopleSoft HCM into a
target Public Sector Planning and Budgeting application.
You perform the following tasks to create HR data rules:
1. Define HR rule details.
2. Create rule line definitions.
3. Create mapping definitions.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Defining HR Rule Details
You define HR rule details on the HR Data Load page.
To define HR rule details:
1. In the Tasks pane, under HR Data Load, select HR Data Load.
The HR Data Load page is displayed.
2. Enter a location or click Browse to select a location.
3. Click Add.
4. Under Rule Definition, perform the following actions:
Enter a name for the rule.
Select a salary assignment option to be loaded by the database table. The options
are Standard, Auto Increment, and Standard-Include Future Dated.
Select the scenario that you identified when you registered the application.
Select a version dimension.
Optional: Enter a description
5. Click Save.
Creating HR Rule Line Definitions
You create rule line definitions to map dimension members to a Planning account. You
can create rule line definitions manually, from a template, or copied from other rules.
To create HR rule line definitions manually:
1. Under Rule Line, click Add.
2. In POV Name, enter a name for the point of view.
3. In POV Type, select the following set of dimensions:
Position PropertyPosition dimension member properties
Employee PropertyEmployee dimension member properties
Position and/or Employee AssignmentProperty and salary data associated with
positions and employees
Compensation AllocationAllocation of salary costs to GL accounts for positions
and employees
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Jobcode PropertyPosition and employee member properties (available if you
created an Employee Only application in Planning)
Salary GradeRates for Element dimension members that correspond to salary
grades
Salary StepRates for Element dimension members that correspond to salary
steps
4. For each POV mapping, click the Add/Edit Mappings icon to define the mappings for
the POV. See Creating Mapping Definitions in this appendix.
5. Repeat steps 1 through 4 for each POV that you want to define.
To create HR rule line definitions from a template or by copying them
from another rule:
1. Under Rule Definition, in the Create Mapping list, perform one of the following
actions:
Select Copy Rule, select a rule, and click OK.
Select Create a template mapping, select a language, and click OK.
The POV rules and their mapping details from a rule or template
are displayed under Rule Line.
2. Optional: Under Rule Line, click Delete or Add to edit or add new rule line definitions.
3. For each POV mapping, click the Add/Edit Mappings icon to define the mappings for
the POV. See Creating Mapping Definitions in this appendix.
Creating Mapping Definitions
You create mapping definitions to specify the Public Sector Planning and Budgeting
accounts into which to load the extracted HR data.
For each dimension in the point of view, you must select a member and then map the
column in the source system to a Planning account.
To create mapping definitions:
1. Under Rule Line, click the Add/Edit Mappings icon.
The Rule Line Mapping page is displayed.
2. Under Rule Line Point of View, enter, or click Browse to search for, a member and
map the members for dimensions in the POV.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
NOTE: You must enter a member for Budget Item, Year, and Period.
3. Under Rule Line Mapping, click Add to map the source column to the account.
4. Under Source Column, enter or click Browse to select the source column in the
PeopleSoft Human Capital Management table that contains the human resource data
to load.
5. In the Account column, enter or click Browse to select the account in the Public Sector
Planning and Budgeting account into which to load the extracted HR data.
6. Repeat steps 3 through 5 to map additional source columns to the accounts.
7. Click Save.
8. Click Back to return to the HR Data Load page.
Executing HR Data Rules
After creating an HR data rule, you must run the rule to extract and load data from
PeopleSoft HCM.
To execute HR data rules:
1. On the HR Data Load page, click Execute to run the rule.
The Execute Rule window is displayed.
2. Select one or more of the following Execute Rule Options:
As Of DateEnter or select a date from which to load data from the human
resource source system.
Import From SourceSelect this option if you want to review the information in the
staging tables before exporting the data to the Public Sector Planning and
Budgeting application
Export to TargetSelect this option if you want to transfer the data to the Public
Sector Planning and Budgeting application.
Load TypeIf you selected Export to Target, perform one of the following actions:
For Classic Public Sector Planning and Budgeting applications: Select the Data,
Metadata, or Both load type.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
For Performance Management Architect Public Sector Planning and Budgeting
applications: Select Metadata and run the data rule. After the rule runs
successfully in Performance Management Architect, deploy the application.
Return to ERP Integrator, and on the HR Data Load page, run the rule and select
Data.
Department Load OptionSelect whether to load all or specific departments.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Managing HR Data Rules
You can manage HR data rules on the HR Data Load page.
To manage HR data rules:
On the Data Load page, perform any of the following actions:
Click Add to edit the HR rule details, rule line definitions, and mapping settings.
Click Delete to delete a HR data rule. Only the rule is removed. The extracted data
and dimensions are not removed. You cannot delete a HR data rule if it is running.
Click the Status icon to check the data-load process details on the Process Details
page.
Managing HR Data Rules
Click Delete to
delete a data rule.
Click Add to
edit a data rule.
Click Status to check
the rule status.
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D
Summary
In this appendix, you should have learned to:
Describe ERP Integrator
Extract GL metadata and data from ERP source systems
Drill through to the ERP source system with ERP Integrator
Write back budget data from EPM target applications
Extract HR metadata and data from the PeopleSoft Human Capital
Management source system
O
r
a
c
l
e

U
n
i
v
e
r
s
i
t
y

a
n
d

O
R
A
C
L
E

C
O
R
P
O
R
A
T
I
O
N

u
s
e

o
n
l
y
T
H
E
S
E

e
K
I
T

M
A
T
E
R
I
A
L
S

A
R
E

F
O
R

Y
O
U
R

U
S
E

I
N

T
H
I
S

C
L
A
S
S
R
O
O
M

O
N
L
Y
.

C
O
P
Y
I
N
G

e
K
I
T

M
A
T
E
R
I
A
L
S

F
R
O
M

T
H
I
S

C
O
M
P
U
T
E
R

I
S

S
T
R
I
C
T
L
Y

P
R
O
H
I
B
I
T
E
D

FDM Study Material

Uploaded by

Copyright:

Available Formats

FDM Study Material

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FDM Study Material

Uploaded by

Copyright:

Available Formats

Oracle Hyperion Financial Data

Quality Management 11.1.2

You might also like