PTS FM11.1.2 SG

Oracle® Hyperion
Financial Management
Fusion Edition 11.1.2:
Administration
Hands-on Workshop
Student Guide
D63786GC10-PARTNER
Edition 1.2
October 2011
Partner Technology Solutions
®
Author Copyright © 2011, Oracle. All rights reserved.
Mark Mitsock Disclaimer
GS Gill 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
Technical Contributors any way. Except where your use constitutes "fair use" under copyright law, you may
and Reviewers 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
Margaret Reed express authorization of Oracle.
Ron Reiley
The information contained in this document is subject to change without notice. If you
Phil Attea find any problems in the document, please report them in writing to: Oracle Platform
Techology Solutions, 500 Oracle Parkway, Redwood Shores, California 94065 USA.
This document is not warranted to be error-free.
Editor Restricted Rights Notice
Susan Moxley If this documentation is delivered to the United States Government or anyone using
Shirley lum the documentation on behalf of the United States Government, the following notice is
applicable:
Graphic Designer U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
Priya Saxena disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
Publisher Trademark Notice
G.S. Gill Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names
may be trademarksof their respective owners.
Table of Contents
Table of Contents i
Preface
se
ur
co
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i
ng
Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
i
Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
in
tra
Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
er
Activity Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
rtn
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
pa
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
e®
cl
Lesson 1: Financial Management Overview
ra
O
an
About Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Financial Consolidation, Reporting, and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
in
e
Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

us
Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

al
Management of the Extended Close Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

on
rs
Related Oracle Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

pe
Financial Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

to
Financial Management Business Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

ed
Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
ct
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
tri
es
Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

R
Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

-
Financial Management Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

ry
ta
Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

ie
Logging On to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

pr
Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

o
Pr
Navigating in Financial Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

e®
View Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

cl
Advanced and Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

ra
O
Setting the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Managing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Custom Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Financial Management 11.1.2 Administration i

Table of Contents
Related Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33

Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Lesson 2: Creating Financial Management Applications
se
Methods for Creating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
ur
Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
co
Classic Application Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
ng
Performance Management Architect Application Creation Process . . . . . . . . . . . . . . 2-4
i
in
Classic Financial Management Administration Application Creation Process . . . . . . . 2-5
tra
Oracle Hyperion Data Integration Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
er
Integration Solutions in the Oracle EPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
rtn
Integration Feature Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
pa
Tools for Metadata Loading into Financial Management Applications . . . . . . . . . . . . 2-10
e®
Tools for Data Loading into Financial Management Applications . . . . . . . . . . . . . . . .2-11
cl
ra
O
Lesson 3: Creating Classic Applications
an
in
Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
e
Creating Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

us
Accessing the Process Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

al
on
Entering Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

rs
Defining the Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

pe
Editing Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

to
Editing Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

ed
Saving Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

ct
Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

tri
es
Creating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

R
-
Lesson 4: Setting Up Dimensions

ry
ta
ie
Accessing Metadata Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

pr
Editing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

o
Pr
Adding and Deleting Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

e®
Editing Groups of Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

cl
Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

ra
Creating Alternate Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

O
Assigning Members to Multiple Parents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

Common Member Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Property Value Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
ii Financial Management 11.1.2 Administration

Table of Contents
Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Setting Up Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Requirements for Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Entities and Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Entities and Intercompany Partners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
se
Entities and the ICP Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
ur
Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
co
Setting Up Accounts and Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
ng
Account Types and Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
i
in
Time Balance and Account Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
tra
Dynamic Account Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
er
Group Label Account Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
rtn
Accounts and Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
pa
Assigning Custom Members to Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
e®
Balance Sheet Accounts and Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
cl
Custom Dimensions and Account Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
ra
O
Setting Up Custom Members for Balance Sheet Movement . . . . . . . . . . . . . . . . 4-37
an
Auditing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
in
Account Properties for Intercompany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
e
Other Account Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

us
Setting Up Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

al
on
Frequency and View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46

rs
View and Missing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47

pe
Scenarios and Process Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48

to
ed
Lesson 5: Configuring Application Settings

ct
tri
es
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

R
Exchange Rate Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

-
PVA Translation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

ry
Consolidation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

ta
ie
Org by Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

pr
Intercompany Aggregations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

o
Pr
Consolidation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

e®
Phased Submission Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11

cl
Validation Account Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

ra
Dimension Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

O
Metadata Security Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Node Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Document Attachment Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Financial Management 11.1.2 Administration iii

Table of Contents
FDM Application Name Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Lesson 6: Loading Metadata

Metadata Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
se
Format for Metadata Load Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
ur
Format for Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
co
Members Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
ng
Hierarchy Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
i
in
Application Settings Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
tra
Currencies Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
er
Loading and Extracting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
rtn
Load Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
pa
Merge Versus Replace—Some Rules of Thumb . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
e®
Extracting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
cl
Managing User Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
ra
O
Disabling Users Log-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
an
in
Lesson 7: Loading and Extracting Data
e
us
Data Load and Extract Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

al
Data Load Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

on
Group Dimension Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

rs
pe
Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

to
Line-Item Detail Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

ed
Submission Phase Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

ct
Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

tri
Financial Management Data Storage and Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

es
Subcube Dimensions and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

R
Guidelines for Managing Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

-
y
Loading Data from Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

r
ta
Merge Option: Overwriting Application Data with Load File Data . . . . . . . . . . . . 7-18
ie
pr
Replace Option: Replacing Data with Load File Data . . . . . . . . . . . . . . . . . . . . . 7-19

o
Pr
Replace by Security Option: Loading Members. . . . . . . . . . . . . . . . . . . . . . . . . . 7-19

e®
Accumulate Option: Accumulating Application Data with Load File Data . . . . . . 7-20
Accumulate Within File Option: Loading Totals into Applications . . . . . . . . . . . . 7-21
cl
ra
Extracting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

O
Exporting Data with Extended Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Removing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
iv Financial Management 11.1.2 Administration

Table of Contents
Lesson 8: Entering Data by Using Data Grids

Data Grids Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Accessing Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Creating Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
se
Changing Grid Layout and Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
ur
Selecting Members for Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
co
Selecting Members for Rows and Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
ng
Selecting Members Through Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
i
in
Saving Data Grid Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
tra
Entering and Saving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
er
Cell Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
rtn
Saving Data and Parent Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
pa
Clearing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
e®
Filling Multiple Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
cl
Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
ra
O
Calculating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
an
Adding Cell Text and Custom Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
in
Cell Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
e
Custom Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

us
Adding Line-Item Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

al
Retrieving Data from FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

on
rs
pe
Lesson 9: Creating, Loading, and Extracting Member Lists

to
ed
Member Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

ct
System-Defined Member Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

tri
User-Defined Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

es
Creating Member Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

R
Identifying Member Lists in a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

-
y
Creating Static Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

r
ta
Creating Dynamic Member Lists for the Entity Dimension. . . . . . . . . . . . . . . . . . 9-12

ie
pr
Creating Dynamic Member Lists for Other Dimensions. . . . . . . . . . . . . . . . . . . . 9-13

o
Pr
Loading Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14

e®
Extracting Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

cl
ra
Lesson 10: Managing Rules with Calculation Manager

O
Financial Management Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Calculation Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Financial Management 11.1.2 Administration v

Table of Contents
Calculation Manager for Classic Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Rule Types and Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Creating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11
Creating Rule Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
se
Validating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
ur
Deploying Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
co
Importing and Exporting Calculation Manager Objects . . . . . . . . . . . . . . . . . . . . . . 10-18
ng
Importing Script-Based Rules Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
i
in
Importing Using the Import Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
tra
Importing with the Rules Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
er
rtn
pa
Lesson 11: Provisioning Users and Groups
e®
Levels of Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
cl
ra
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
O
Task Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
an
Document Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5
in
Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6
e
User Roles Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7

us
User Role Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8

al
on
Assigning User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-9

rs
pe
Lesson 12: Assigning Access to Data and Documents

to
ed
Application Settings and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

ct
Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

tri
Document Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

es
R
Security Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Assigning Access to Security Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
-
ry
Deleting Security Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

ta
ie
Running Security Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-11

pr
Configuring Security Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

o
Pr
Running Auditing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

e®
Loading Security Information from Text Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

cl
Security Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17

ra
Loading Security Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19

O
Extracting Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21

Migrating Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
vi Financial Management 11.1.2 Administration

Table of Contents
Lesson 13: Creating Data Forms

Data Forms Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Data Form Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Data Forms-Context Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
se
Creating Data Forms with Form Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
ur
Defining the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
co
Defining Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
ng
Setting Column and Row Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
i
in
Formatting Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
tra
Setting Up Text Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
er
Setting Column and Row Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
rtn
Setting Heading Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
pa
Viewing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
e®
Exporting to and Importing from Spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
cl
ra
Lesson 14: Creating and Managing Task Lists
O
an
Task Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
in
Creating Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
e
us
Adding Items to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

al
Organizing Task List Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

on
Creating Folders in Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

rs
pe
Nesting Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7

to
Adding Related Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8

ed
Adding Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10

ct
Managing Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12

tri
es
Lesson 15: Entering Intercompany Data

R
-
y
Intercompany Transactions Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

r
ta
Intercompany Account Balances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

ie
pr
Elimination Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

o
Pr
Plug Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

e®
Intercompany Eliminations and the Value Dimension . . . . . . . . . . . . . . . . . . . . . 15-6

Setting Up Entities for Intercompany Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
cl
ra
Setting Up Accounts for Intercompany Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9

O
Creating Intercompany Matching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10

Running Intercompany Matching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Formatting Intercompany Reports with Oracle BI Publisher . . . . . . . . . . . . . . . . . . 15-15
Financial Management 11.1.2 Administration vii

Table of Contents
Lesson 16: Adjusting Data with Journals

Journals Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Viewing Automated Consolidation Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Journals and the Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
se
Multiple Journal Postings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
ur
Creating Parent and Contribution Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
co
Opening Periods for Journal Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
ng
Journal Creation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-11
i
in
Creating Journal Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
tra
Setting the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15
er
Creating Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16
rtn
Entering Journal Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18
pa
Submitting, Reviewing, Approving, and Posting Journals . . . . . . . . . . . . . . . . . . . . 16-20
e®
Viewing Journal Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-22
cl
ra
Viewing Adjusted Data in Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-23
O
Viewing Adjustments in the Entity Details Report . . . . . . . . . . . . . . . . . . . . . . . 16-24
an
Creating and Formatting Journal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-25
in
Setting Journal Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-27
e
Selecting Columns and Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-28

us
Previewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-30

al
on
Saving Journal Reports Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31

rs
Saving Journal Reports Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-32

pe
Printing Journal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-33

to
ed
Lesson 17: Translating Data

ct
tri
Data Translation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

es
R
Default Translation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

-
Entering Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

ry
Checking Translation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

ta
ie
Translating Financial Data in Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9

o pr
Pr
Lesson 18: Running Consolidations

e®
cl
Financial Management Business Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

ra
Consolidation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3

O
Consolidation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4

Consolidation and the Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Checking Calculation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
viii Financial Management 11.1.2 Administration

Table of Contents
Consolidation of Children by Percentages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-9

Ownership Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
About Manage Equity Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-11
Assigning Ownership by Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Consolidating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
se
ur
Lesson 19: Managing the Review Cycle Using Process Management
co
ng
Process Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
i
in
Process Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
tra
Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
er
Process Management Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
rtn
Process Management Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
pa
About Phased Submission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
e®
Submission Group Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
cl
Submission Phase Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
ra
O
Process for Setting Up Phased Submissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
an
Setting Application and Metadata Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-11
in
Assigning Validation Accounts to Submission Phases . . . . . . . . . . . . . . . . . . . 19-12
e
Setting Up Submission Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13

us
Assigning Submission Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15

al
Security Access for Process Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17

on
rs
Viewing Process Unit Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18

pe
Setting Process Control Panel Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21

to
Viewing Status for Multiple Submission Phases . . . . . . . . . . . . . . . . . . . . . . . . 19-23

ed
Viewing Status for All Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24

ct
Validating Process Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25

tri
es
Validation Accounts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27

R
Viewing Validation Account Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29

-
Calculating and Consolidating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30

ry
Moving Process Units Through the Review Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32

ta
ie
Submission Phases and Review Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33

pr
Selecting Review Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34

o
Pr
E-mail Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-35

e®
Viewing Review History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37

cl
Viewing Process Level in Data Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-38

ra
Managing Process Unit States in Data Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-39

O
Locking and Unlocking Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-40
Financial Management 11.1.2 Administration ix

Table of Contents
Lesson 20: Analyzing Data with Smart View

Navigating Smart View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Smart View Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Business Process for Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
se
Components of Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
ur
Connecting to Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
co
Viewing and Analyzing Data with the Ad Hoc Analysis Tool . . . . . . . . . . . . . . . . . . . 20-8
ng
Changing the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
i
in
Changing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-11
tra
Drilling Down and Up Dimension Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12
er
Pivoting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
rtn
Displaying Cell Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-14
pa
Adding Formulas and Preserving Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
e®
Creating Free-Form Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
cl
Drilling Through to ERP Integrator and FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
ra
Creating Smart Slices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-20
O
an
Designing Reports in Report Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22
Creating Cascading Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
in
e
Viewing Calculation and Process Management Status in Smart View. . . . . . . . . . . 20-26

us
Submitting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27

al
Working with Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-28

on
rs
pe
Lesson 21: Managing Intercompany Transactions

to
ed
Intercompany Transactions Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

ct
Business Process for the Intercompany Transactions Module . . . . . . . . . . . . . . 21-3

tri
Setup Considerations for Intercompany Transactions . . . . . . . . . . . . . . . . . . . . . 21-4

es
Opening Intercompany Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

R
Creating Intercompany Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7

-
ry
Loading Intercompany Transactions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8

ta
ie
About Process IC Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9

pr
Creating IC Transactions from Process IC Transactions . . . . . . . . . . . . . . . . . . 21-10

o
Pr
Matching Intercompany Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-12

e®
Intercompany Transaction Matching Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13

cl
Posting Intercompany Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-15

ra
Generating Matching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-17

O
Drill-Through Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19

Locking Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-20
Closing Intercompany Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-22
x Financial Management 11.1.2 Administration

Table of Contents
Monitoring Intercompany Entity Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-23
Lesson 22: Enterprise Performance Management Architect

Performance Management Architect Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
se
Creation and Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
ur
Calculating Business Rules for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
co
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
ng
Performance Management Architect Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
i
in
Dimension Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5
tra
Application Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
er
Calculation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-9
rtn
Data Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
pa
Transform Classic to EPM Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-12
e®
Library Job Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-13
cl
Performance Management Architect Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 22-15
ra
O
Workspace Navigate Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-17
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
ry
ta
ie
o pr
Pr
e®
cl
ra
O
Financial Management 11.1.2 Administration xi

O
xii
ra
cl
e®
Pr
opr
ie
Table of Contents
ta
ry
-
R
es
tri
ct
ed
to
pe
rs
on
al
us
e
in
an
O
ra
cl
e®
pa
rtn
er
tra
in
ing
co
Financial Management 11.1.2 Administration

ur
se
Preface 0
se
ur
co
Welcome to Oracle® Hyperion Financial Management, Fusion Edition
ng
i
11.1.2 Administration!
in
tra
Before you begin, please take a moment to review this section. The
er
preface presents an overview of the following information:
rtn
pa
• Course objectives
e®
• Structure of the course
cl
ra
• Course materials used in the class
O
• Conventions used in the book an
in
• Additional resources to enhance your learning
e
us
al
on
Course Objectives
rs
After completing this course, you should be able to:

pe
to
• Describe Financial Management concepts, product features, and

ed
architecture
ct
tri
• Manage data and metadata

es
R
• Create and deploy applications

-
• View and enter data by creating data forms and grids

yr
ta
• Define simple business calculations using Calculation Manager

ie
opr
• Enter intercompany transactions and perform data consolidation

Pr
• Manage the financial review cycle using process management

e®
cl
• Set up security including users, groups, security classes, and access

ra
rights
O
Preface
Course Structure
Oracle® Hyperion Financial Management, Fusion Edition 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.
se
ur
co
Course Materials
ng
You use two books in class—the student guide and the activity guide. The instructor may
i
in
tra
also give you handouts.
er
rtn
Student Guide
pa
The student guide contains lessons. Each lesson begins with a list of objectives followed
e®
by the presentation of slides and accompanying text. The lesson ends with a summary of
cl
the topics covered in the lesson.
ra
O
The student guide contains appendices of material related to the course.
an
in
e
Activity Guide
us
The activity guide has two sections—exercises and exercise solutions.

al
on
• Exercises—A critical part of the learning process is the challenge of completing real
rs
tasks associated with each lesson. Each exercise is an opportunity to apply your
pe
knowledge.
to
ed
• Exercise Solutions—The exercise solutions present the detailed steps to complete

ct
the exercises.
tri
es
R
Conventions
-
r y
The following text conventions are used in this course book:

ta
ie
• Text to be entered, options to be selected, names of files and modules, and menu
opr
selections are displayed in bold type. Examples:

Pr
e®
- Select Clear Profile.

cl
ra
- Click YES to clear the profile.

O
• When available, figures are used to identify an object or task. Example:

Click Edit .
ii Financial Management 11.1.2 Administration

Preface
• 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.
se
ur
co
ngi
TIP: A tip provides information that helps you work more efficiently.
in
tra
er
rtn
pa
Additional Resources
e®
Use the following resources to enhance your learning:
cl
ra
• Oracle® Hyperion Financial Management, Fusion Edition, Administrator’s Guide
O
(PDF)
an
• Oracle® Hyperion Financial Management, Fusion Edition, User’s Guide (PDF)
in
e
us
• Oracle® Hyperion Calculation Manager, Designer’s Guide (PDF)

al
• Oracle® Hyperion Smart View for Office, Fusion Edition, User’s Guide (PDF)
on
rs
• Oracle® Hyperion Enterprise Performance Management Architect, Fusion Edition,

pe
Administrator’s Guide (PDF)

to
ed
• Oracle® Hyperion Enterprise Performance Management System, Fusion Edition,

ct
Installation and Configuration Guide (PDF)

tri
es
Oracle provides the following user assistance with Enterprise Performance Management
R
products:
-
y
r
• Context-sensitive help—Click Help for context-sensitive help.

ta
ie
• Help menu—From the Help menu in the software, access screen-level help, general
opr
product help, technical support, EPM documentation, oracle.com, and optionally

Pr
Oracle User Productivity Kit.

e®
cl
• My Oracle Support—Access release-specific Readme files.

ra
O
• E-Delivery—Access release-specific installation documentation before downloading

software.
Financial Management 11.1.2 Administration iii

Preface
• Oracle Technology Network—Explore 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
se
interest; and subscribe to Developer e-mail newsletters.
ur
co
• OTN Documentation Library—Download documentation for all Enterprise
Performance Management products, including reference information and PDF and
ng
HTML versions of each deliverable.
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
iv Financial Management 11.1.2 Administration

L E S S O N 1
Financial Management Overview 1
se
ur
co
ngi
Objectives
in
tra
At the end of this lesson, you should be able to:
er
rtn
• Describe the features of Financial Management
pa
• Discuss the product architecture of Financial Management
e®
cl
• Identify related products
ra
O
• Describe the user interface components
an
• Describe the business process (tasks) in a typical monthly reporting
in
financial cycle
e
us
• Describe metadata in Financial Management

al
on
• Describe dimensions and dimension hierarchies

rs
pe
• Navigate in Financial Management

to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 1 Financial Management Overview
About Financial Management
• Consolidation
se
• Performance and operational metrics
ur
co
• Reports
ng
• Profitability and cash flow
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
Co pyri ght © 2 011, Ora cle an d/or its a ffil ia te s. Al l righ ts rese rved.
rs
pe
to
About Financial Management

ed
ct
Financial Management delivers global data collection, financial consolidation, reporting

tri
and analysis in one highly scalable solution. It enables you to:

es
R
• Conduct in-depth analysis of key performance and operational metrics.

-
y
• Deliver accurate and timely reports to both internal management and external
r
ta
regulatory bodies.
ie
pr
• Discover sources of profitability and cash flow at the company, product, brand, and
o
Pr
customer levels.
e®
• Reduce consolidation and reporting cycles by days or weeks.

cl
ra
• Consolidate data with multiple consolidation paths.

O
1-2 Financial Management 11.1.2 Administration

Financial Consolidation, Reporting, and

Analysis
se
Local Regional Central
ur
co
Input or load Submit Publish reports
Finance Dept. Group finance
Monthly Submit
ng
and quarterly Validate
 Review  Review
i
in
actual results
Approve  Approve Approve  Approve  SEC
tra
 Adjust  Adjust  Tax
er
SAP Oracl e JDE  Consolidate Reject  Consolidate  Legal
 Treasury
rtn
 IC match
ERP/GL  Management
 Translate
pa
Monthly Input or load Approve
e®
forecast Submit
Validate
cl
Reject
ra
O
Approve
an
Input or load
Annual budget
Submit
in
Validate Reject
e
us
al
on
rs
pe
to
Financial Consolidation, Reporting, and Analysis

ed
ct
Financial Management enables highly efficient collection and consolidation of data from
tri
diverse sources. It includes these features:

es
R
• Process management for tight control of the review and approval process
-
y
• Data validation
r
ta
ie
• Currency translation to support multiple local currencies

opr
Pr
• Automatic eliminations for intercompany transactions

e®
Financial Management is designed for large-scale, centralized Web deployment. You

cl
can use it to consolidate data from diverse general ledger systems and locations around
ra
the globe.
O
Financial Management 11.1.2 Administration 1-3

Product Components
• Financial Reporting
se
• Smart View
ur
co
• Foundation Services
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Product Components
ed
ct
Financial Management comes bundled with the following products and module that
tri
extend its capabilities:

es
R
• Oracle® Hyperion Financial Reporting, Fusion Edition is a reporting and charting tool
-
for Web or print distribution of financial reports.

y
r
ta
• Oracle® Hyperion Smart View for Office, Fusion Edition is a spreadsheet add-in
ie
pr
based on Excel for reporting and analysis.

o
Pr
• Hyperion® Foundation Services enables user provisioning and sharing of metadata

e®
among Financial Management applications or between Financial Management and

cl
other products.
ra
O

Product Architecture
Client Windows client Browser client
se
ur
co
Microsoft Excel
ngi
in
tra
Application
er
rtn
pa
Performance
e®
Web server
Management Architect Financial Management
cl
dimension server application server
ra
O
Database
an
in
e
us
Architect Financial Management

RDBMS RDBMS
al
on
rs
pe
to
Product Architecture
ed
ct
Financial Management uses a multitier architecture that includes a client tier, an

tri
application tier, and a database tier.

es
R
The client tier contains the user interface. It communicates with the application tier. The
-
primary function of the client tier is to display, enter, and maintain data and to maintain
yr
metadata.
ta
ie
pr
The application tier contains the application, the report, and Web servers. The Web
o
server enables you to access the Web-based portions of Financial Management. The
Pr
application server contains the financial intelligence and connections to the relational
e®
database and OLAP engine. It also contains Oracle® Hyperion Enterprise Performance
cl
ra
Management Architect, Fusion Edition for managing metadata.

O
The data tier contains the relational databases for Financial Management metadata and
source data.

Management of the Extended Close Process
se
ur
co
CFO Dashboard
i ng
in
Governance, Risk & Compliance
tra
Fin ancial Clo se Management
er
rtn
Tax Tax
pa
ERP: Calculations Filing
Data Financial
e®
Oracle, SAP,
Assurance Consolidation Disclosure
Legacy, Other Financial and
cl
Mgmt. Reporting Management
ra
O
Transactions Reporting
an
in
e
us
al
on
rs
pe
to
Management of the Extended Close Process

ed
ct
Oracle® Hyperion Financial Close Management and Oracle® Hyperion Disclosure

tri
Management are complementary products that, together with Financial Management,

es
enable you to manage the extended close process.

R
-
• Financial Close Management provides process monitoring, a financial close

y
r
calendar, and close task management with e-mail and alerts.

ta
ie
pr
• Disclosure Management covers the entire process of transforming a company’s

o
consolidated results into specifically stylized statutory filings. It has built-in Extensible
Pr
Business Reporting Language (XBRL) reporting capabilities, including full instance

e®
document creation and validation.

cl
ra
O

Related Oracle Hyperion Products
• Essbase
se
• Web Analysis
ur
co
• Financial Data Quality Management
ng
• ERPI
i
in
tra
• Oracle Data Integrator
er
• Oracle Hyperion Essbase Analytics Link for FM
rtn
(HyperRoll)
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Related Oracle Hyperion Products

ed
ct
Oracle provides other complementary products that integrate with Financial

tri
Management.
es
R
• Essbase is a multidimensional database that extends the analytical capabilities of

-
Financial Management by providing more detail, more dimensions, and sophisticated

y
r
allocation routines.
ta
ie
pr
• Hyperion® Web Analysis is an intuitive, Web-based, interactive data analysis tool

o
that you can use to retrieve and analyze Financial Management data.
Pr
e®
• Oracle® Hyperion Financial Data Quality Management (FDM) is a packaged solution

cl
for finance users. It helps simplify the collection, mapping, verification, and loading of
ra
financial data from external systems into Financial Management.

O

• Oracle® Hyperion Financial Data Quality Management ERP Integration Adapter for
Oracle Applications, Fusion Edition (ERP Integrator), a module of FDM, enables
seamless loading of metadata and data from ERP to EPM applications. It allows
drillback to the ERP source data from the data entry forms and reports in EPM
applications.
• Oracle Data Integrator is a comprehensive data integration platform that covers all
se
data transformation and integration requirements.
ur
co
• Oracle® Hyperion Essbase Analytics Link for Financial Management (HyperRoll)
ng
enables accelerated financial reporting for a financial close. It delivers preintegrated
i
in
reporting to Financial Management from Essbase and Oracle BI.
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Financial Management Components
Enterprise Performance
se
Workspace Financial
Management
ur
Management
Architect
co
ng
i
in
tra
er
rtn
pa
Manage enterprise financial
e®
information
cl
ra
O
an
in
Manage Financial Managem ent applications Manage financial data
e
us
al
on
rs
pe
to
Financial Management Components

ed
ct
Financial Management integrates application creation and management in a centralized

tri
administration environment.
es
R
• Single sign-on—Users log on once to Workspace to access Performance

-
Management Architect, Financial Management, and the reporting tools.

y
r
ta
• Single console for application management and creation—Users create, manage,

ie
pr
and deploy applications from Performance Management Architect. These

o
applications are opened in Financial Management for data retrieval and data output.
Pr
e®
• Centralized repository of key dimensional elements for different products.

cl
ra
• Centralized console for controlling data flow between applications.

O

Financial Management Business Tasks
se
ur
co
Calculate data Adjust data
ng
Translate, eliminate
Load and
i
interco, and consolidate
in
add data
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
Run and publish Lock data Appr ove data

us
financial reports
al
on
rs
pe
to
Financial Management Business Tasks

ed
ct
Financial Management is a powerful application that enables you to manage enterprise

tri
financial information quickly and cost effectively. You follow a typical task flow for a
es
monthly financial cycle. The following table describes the typical task flow:
R
-
y
Task Description
r
ta
ie
Load and add data You can add data to your application by loading it from a file and by
pr
using data forms.

o
Pr
Calculate After you enter data, you can run calculation rules to populate
e®
calculated accounts.
cl
Adjust data After you calculate data, you can adjust the data by using journals that
ra
provide an audit trail of your adjustments.

O
Translate and After entering and adjusting data for individual business units, you can
consolidate data translate and consolidate the data.

Task Description
Approve data After consolidating data, you can submit the data for review and
approval.
Lock data After receiving the approval for the submitted data, you can lock the
data to prevent further modifications.
Run and publish You can run reports against the approved data.
se
financial reports
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Metadata
se
ur
3689.00 Data
co
ngi
in
tra
Metadata
er
rtn
pa
e®
January actual sales for Cola in Manhattan are 3689.00.
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Metadata
ed
ct
Metadata is defined as the structural elements of an application that describe and hold
tri
data. Examples of metadata are dimension names, member names, properties,

es
exchange rates, and security.

R
-
In the illustration in the slide, the circled dimension member labels are the metadata. The
yr
metadata describes the data value. The value 3689.00 is the value for Actual, Sales for
ta
ie
Cola in Manhattan in January.

pr
o
Pr
e®
cl
ra
O

Dimensions
Account Entity Period
se
Income Before
ur
Taxes Geographical
Quarter1
co
Gross Margin
ng
United States
January
i
in
Total Revenues
tra
California
February
er
Sales
rtn
Connecticut
pa
Sales Interco March
e®
Total Costs Massachusetts
cl
ra
Salaries
O
Interest Charges an
in
e
Admin Expense
us
al
on
rs
pe
to
Dimensions
ed
ct
You create metadata for applications by defining dimensions. Dimensions describe your
tri
organization’s data. Examples of dimensions are Account, Entity, and Period.

es
R
The elements that comprise a dimension are called members. For example,
-
GrossMargin and TotalRevenues are members of the Account dimension.

y
r
ta
ie
opr
Pr
e®
cl
ra
O

Dimension Hierarchies
Child of Gross
Parents Margin
Income Before
se
Taxes
ur
co
Gross Margin 500
ng
Descendants of
Gross Margin
i
in
tra
Total Revenues 900
er
rtn
700
Sales
pa
e®
200
Other Revenues
cl
ra
O
an
Total C osts
in 400
400
e
us
Salaries
al
on
rs
pe
to
Dimension Hierarchies
ed
Members of a dimension are arranged in hierarchies. Upper-level members are called

ct
tri
parent members, and a member immediately below a parent member is referred to as its
es
child. All members below a parent are referred to as descendants. The bottom-level
R
members of the hierarchy are called base-level members.

-
r y
The illustration in the slide shows a part of the dimension hierarchy of the Account
ta
ie
dimension. In this hierarchy, the Total Revenues member is a child of Gross Margin.
pr
Sales, Other Revenues, Salaries, Total Revenues, and Total Costs are descendants of
o
Pr
Gross Margin. Sales, Other Revenues, and Salaries are base-level members.
e®
cl
ra
O

Dimensions and Data

Data
aggr egates
se
Income Before to the parents.
ur
Taxes
co
ng
Gross Margin 500
i
in
tra
Total Revenues 900
er
rtn
Sales 700
pa
Data is input to
base-level
e®
m embers. Other Revenues 200
cl
ra
O
Total Costs 400
an
in
Salaries 400
e
us
al
on
rs
pe
to
Dimensions and Data

ed
Data is always entered into base level members with the exception of the Entity
ct
tri
dimension. For the Entity dimension, data is entered to <Entity Currency> of base
es
members only, and may also be entered through journals to the adjustments Value
R
dimension members for both base and parent entity members. If "Input" rules are used,
-
then data may be entered to the <Entity Currency> member of specified parent entity
y
r
ta
members.
ie
pr
In the illustration in the slide, the data values from the base-level members are rolled up
o
Pr
to the parent-level members—Total Revenues and Total Costs. Data values from Total
e®
Revenues and Total Costs are then rolled up to their parent, Gross Margin.
cl
ra
O

Financial Management Dimensions
se
Scenario
ur
co
Intercompany Partner Year
ngi
in
tra
er
rtn
Account/Custom Period
pa
e®
cl
ra
O
Value View
an
in
Entity
e
us
al
on
rs
pe
to
Financial Management Dimensions

ed
Financial Management supplies eight system-defined dimensions and four custom

ct
tri
dimensions. You customize the members of each dimension to meet the needs of your
es
organization. The Financial Management dimensions are described in the following

R
table:
-
yr
ta
Dimension Description
ie
pr
Scenario Set of related data, such as Budget, Actual, or Forecast. For example, the
o
Budget scenario can contain data that reflects the targeted business
Pr
operations. The Actual scenario can contain data from a general ledger,
e®
reflecting past and current business operations. The Forecast scenario

typically contains data that corresponds to predictions for upcoming periods.
cl
ra
In Financial Management, multiple scenarios can be defined for an

O
application.
Year Fiscal or calendar year for the data. An application can contain data for more
than one year.

Period Time periods, such as quarters and months.
View Various modes of calendar intelligence, such as periodic, year-to-date, and
quarter-to-date frequencies. If you set the view to Periodic, the values for
each month are displayed. If you set the view to year-to-date or quarter-to-
date, the cumulative values for the year or quarter are displayed.
se
Entity Management and legal reporting structures in your organization, such as
ur
regions and divisions. Entities can be categorized as base entities (bottom
co
of the organization structure; data is loaded to base entities) or parent
ng
entities (contain one or more entities as children).
i
in
Value Types of values stored in an application. For example, the Entity Currency
tra
member stores the value for an entity in the local currency of the entity. The
er
Parent Currency member stores the value for an entity translated to the
rtn
currency of the parent entity.
pa
Account Hierarchy of natural accounts. Natural accounts store financial data for
e®
entities and scenarios in an application. Each account has a type, such as
cl
Revenue or Expense, that defines its accounting behavior.
ra
O
Intercompany Intercompany account balances. Financial Management can track and
Partner eliminate intercompany transaction details across entities and accounts.
an
in
Custom Dimensions associated with accounts. These dimensions enable you to
specify additional details, such as products, markets, channels, or balance
e
us
sheet movement. For example, a custom dimension for products associated

with Sales and COGS accounts enables you to track sales and cost detail by
al
on
product.
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
o pr
Pr
e®
cl
ra
O

Value Dimension
se
Contribution Total represents the value that
ur
aggregates to the par ent.
co
ngi
in
tra
er
These mem bers represent the intermediary values
rtn
used to derive Contribution Total.
pa
e®
cl
ra
O
an
Entity Currency represents the original input or
in
loaded value.
e
us
al
on
rs
pe
to
Value Dimension
ed
The Value dimension is a system-defined dimension that provides an audit trail of the
ct
tri
transformations applied to Financial Management data.

es
R
You load data for each entity to the Entity Currency member of the Value dimension for
-
the entity. During the process of journal entry, currency translation, and consolidation, the
yr
values that are input to the Entity Currency member typically go through transformations
ta
ie
before being aggregated to the parent. The Value dimension members, either stored or
pr
derived, represent the data for the intermediate steps in the transformation. For example,
o
Pr
the Parent Currency member stores the value for an entity translated to the currency of
e®
its parent entity.

cl
You can display Value dimension members on data grids and reports. The display
ra
O
provides an audit trail that enables you to determine how the value that each entity
contributed to its parent is derived.

Logging On to Workspace
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Logging On to Workspace
ed
ct
Shared Services uses user names and passwords from the external authentication
tri
provider, such as Active Directory or Lightweight Directory Access Protocol (LDAP). On

es
the Workspace logon page, you enter the user name and password that you use to
R
access your network. When you select a Financial Management application, Financial
-
y
Management verifies that your user name and password are valid for the application.
r
ta
ie
pr
To log on to workspace:
o
Pr
1. From your Windows desktop, launch Workspace.

e®
cl
2. Enter user name and password.

ra
O
3. Click Log on.

Workspace is displayed.

Opening Applications
Financial Management applications are
se
in the Consolidation gr oup.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Opening Applications
ed
In Financial Management, all data is processed within applications. You access Financial
ct
tri
Management applications from server clusters. Server clusters improve performance by

es
sharing the workload among a group of servers.

R
-
You can make the application that is currently open the default application. When you log
y
r
on, the default application is opened automatically.

ta
ie
pr
To open applications:
o
Pr
• Select Navigate, then Applications, and then Consolidation and select an application.
e®
cl
ra
O

Navigating in Financial Management
se
ur
Menus
Toolbar
co
Application
ng
Maximize
i
in
content
tra
pane
er
rtn
pa
e®
cl
ra
O
View
pane an
in
e
us
al
on
rs
pe
to
Navigating in Financial Management

ed
After you access Financial Management from the Navigate menu, the application is
ct
tri
displayed in a window with a tab at the top left. Financial Management provides several
es
tools for selecting tasks and documents:

R
-
• Financial Management menus

y r
ta
• Financial Management toolbar

ie
pr
• View pane
o
Pr
e®
cl
ra
O

Financial Management Menus

Financial Management menus provide quick access to frequently performed tasks. The
Financial Management Menus are described in the following table:
Option Description
se
File menu • New
ur
• Document
co
• Data Grid
ng
• Data Form
i
in
tra
• Link
er
• Related Content
rtn
• Task Lists
pa
• System Reports
e®
• Open
cl
ra
• Document
O
• Applications
• Close an
in
• Preferences
e
• Log off
us
• Exit
al
on
View menu • View Pane

rs
• Advanced Mode and Basic Mode

pe
to
Favorites • Manage Favorites

ed
• My Personal Page
ct
Tools • Personalize
tri
es
• Show Subscribed Items

R
• Manage Personal Pages

-
• Links
yr
• Web Analysis Studio

ta
ie
• Install
pr
• Interactive Reporting Web Client

o
Pr
• Smart View
e®
cl
ra
O

Option Description
Administration menu • Manage Documents
• Manage Favorites
• System Messages
• Users on System
• Manage Servers and Applications
se
• Task Audit
ur
co
• Data Audit
• Running Tasks
ngi
• Extended Analytics
in
tra
• Copy Document Link
• Manage Taskflows
er
rtn
• View Taskflow Status
pa
• Register
e®
• Unregister
• Manage Smart View Providers
cl
ra
Help menu Access help for the currently selected task or document
O
Browser View icon • Select tasks
an
in
• View documents, task lists, and favorites
e
• Open documents, task lists, and favorites

us
Project View icon List task lists

al
on
Toolbar New Document, Open Document, Home, Explore, Manage

rs
Documents, Task Lists, and Favorites, Log Off, Help

pe
to
Financial Management Toolbar

ed
The toolbar buttons open dialog boxes that you can use to manage documents, task
ct
tri
lists, and favorites. The Financial Management toolbar options are described in the
es
following table:
R
-
y
r
ta
ie
o pr
Pr
e®
cl
ra
O

Button Purpose Description

Home Workspace startup page
New Document • Create Workspace document
se
• Collect reports in a book
ur
• Batch reports for scheduling
co
ng
Open Document Open Workspace documents
i
in
tra
er
Explore Display Workspace folders in the view pane
rtn
pa
e®
Manage Documents Manage the following types of documents:
cl
ra
• Task lists
O
• Data grids
• Data forms an
in
• System reports
e
• Links
us
• Related content
al
on
• Custom documents
rs
Manage Task Lists • Add items to a task list

pe
• Remove items from a task list

to
• Reorder items on a task list

ed
• Select a task list as your default task list

ct
tri
Manage Favorites • View items stored as favorites

es
• Remove items stored as favorites

R
-
Logoff Log off the application

ry
ta
ie
o pr
Help Access help for the currently selected task or document

Pr
e®
cl
ra
Maximize Content Maximize or restore the content pane

O
Pane (on far right of

navigation path)

View Pane
Project View button
Browser View button
se
ur
co
ngi
in
Pr oject View Browser View
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
View Pane
ed
The view pane is displayed on the left side of the Financial Management Web page. The
ct
tri
view can be a Browser View or Project View, depending on the toolbar button selected at
es
the top of the pane. Browser View lists all accessible documents and tasks in the
R
application. It is a split pane. The bottom pane reflects the contents of the item selected
-
in the top pane. You can double-click an item in the bottom pane to view it in the content
y
r
ta
area on the right.

ie
pr
Project View lists the available task lists. A task list is a predefined list of related tasks or
o
Pr
documents that you access frequently. You can expand a task list to show its content.
e®
When you select a task list item, it is displayed in the content area on the right.
cl
ra
O

To navigate the view pane:

1. To Minimize or Maximize the View Pane size, drag the horizontal or scroll bars on the
right of the View Pane.
2. To show or hide the View Pane, select View, then View Pane.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Advanced and Basic Modes
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Advanced and Basic Modes

ed
ct
Depending on the tasks that users perform in Financial Management, you can set up
tri
users with Advanced or Basic security roles. Users with the Advanced security role can
es
work in either Advanced mode or Basic mode. Users without the Advanced security role
R
can work only in Basic mode.

-
y
Advanced mode provides access to both Browser View and Project View. Browser View
r
ta
provides access to all tasks and documents in Financial Management for which the user
ie
pr
has security privileges.

o
Pr
When users work in Basic mode, the view pane displays predefined task lists. Users
e®
select tasks and documents from the Project View pane to the right of the task list.
cl
ra
O

Setting the Point of View
se
Click a dimension to select a member. Scroll to view more dimensions.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to

ed
ct
The members selected for the dimensions assigned to the point of view (POV) determine
tri
the context for the data in the rows and columns of data grids and data forms. For
es
example, if the Scenario dimension is set to Budget in the POV of a data grid, then all
R
rows and columns on the data grid display data for the Budget scenario. The POV is
-
y
always set to a single member for each POV dimension.

r
ta
ie
pr
To change members:
o
Pr
You can change the member that is currently selected for a POV dimension.
e®
1. Click the dimension in the POV bar to display the Member Selector.
cl
ra
O
2. Select the member and click OK.

To display member in the point of view:

You can display a POV dimension not currently visible on the toolbar.
• Click the arrows at the right end of the POV bar to scroll until the dimension is
displayed.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Selecting Members
se
ur
co
ng
i
in
tra
er
Member Top
rtn
list parent
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Selecting Members
ed
ct
The Member Selector displays a member list, a subset of related members that belong to
tri
a dimension. The member that is currently selected is displayed in the Selected Value
es
text box. Parent members are displayed as folders. You can click the plus sign next to a
R
parent member to view its children.

-
y r
Member lists can reduce the time spent browsing the hierarchy of members. For
ta
ie
example, if Italy, France, and UK are used frequently in the point of view for the Entity
pr
dimension, you can create a member list named European Region that includes the
o
Pr
frequently used members. You can then select a European member from this list instead
e®
of browsing through the entire hierarchy of the Entity dimension.

cl
ra
O

Financial Management provides system-defined member lists, whose names are

enclosed in brackets; for example, [Descendants] and [Children]. You can filter system-
defined member lists by entering a parent in the text box to the right of the member list
drop-down list. For example, if you select the [Descendants] member list and type
California as the parent, the member list is filtered to show only descendants of
California.
se
ur
To select members:
co
ng
• Select a Member from the Member List, or enter a member label in the Selected
i
in
Entity Value field and click the Validate button.
tra
er
To search for members
rtn
pa
• Enter all or part of the member label in the Selected Value text box and click the Find
e®
Next or Find Previous button.
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Managing Documents
Manage Documents
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Managing Documents
ed
ct
The Manage Documents task provides a central location from which you can manage
tri
documents in applications.
es
R
• You can work with task lists, data grids, data forms, system reports, links, related
-
content, and custom documents.

y
r
ta
• You can create, edit, load, extract, and delete documents, add them to your
ie
pr
Favorites section, and create document folders. (By selecting the All tab, you can
o
delete or extract documents, create folders for them, or add them to Favorites all at
Pr
once instead of working with each document tab in turn.)

e®
cl
• You can create public documents to share with other users, or private documents.
ra
O
• You can integrate external documents (custom documents, related content, and
links) into Financial Management applications.

To access Manage Documents:

• Select Administration, then Manage Documents, or click the Manage Documents icon on
the toolbar.
Custom Documents
se
You can attach one or more documents to cells in data grids, data forms, and Process
ur
Control cells. You must first upload the documents to the Financial Management
co
database. The documents are stored in the database, and you can apply security
ng
classes to them.
i
in
tra
Related Content
er
rtn
You can include Financial Reporting and Web Analysis reports in Financial Management
pa
applications. These reports are referred to as related content.
e®
You create related content documents from the Related Content tab of the Manage
cl
Documents task. A related content document serves as a link to a resource in another
ra
O
product. For example, you can view a report from Financial Reporting in HTML format or
an
as a PDF file. You can add the item to a task list or launch it separately from the Related
Content menu in the view pane. You must be assigned the appropriate security rights to
in
view the content.
e
us
al
on
Links
rs
• You can create links to files or Web pages. You can add links to task lists and to the
pe
Favorites section. You can also launch them from the view pane. If you have a link to
to
a Web page that is time-consuming to open, you can have the system prompt you
ed
before opening the page.

ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
In this lesson, you should have learned to:
i
in
tra
• Describe the features of Financial Management
er
• Discuss the product architecture of Financial Management
rtn
pa
• Identify related products
e®
• Describe the user interface components
cl
ra
• Describe the business process (tasks) in a typical monthly reporting
O
financial cycle
an
in
• Describe metadata in Financial Management
e
us
• Describe dimensions and dimension hierarchies

al
on
• Navigate in Financial Management

rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 2
Creating Financial Management

Applications 2
se
ur
co
ng
i
in
tra
• List two methods for creating Financial Management applications
er
rtn
• Explain various methods to load information into applications
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 2 Creating Financial Management Applications
Methods for Creating Applications
Performance Management Architect:
se
• Create applications by using a wizard
ur
• Modify applications by dragging and dropping
co
ng
• Design applications graphically in a central library that
i
includes tools for auditing, tracking and comparing information
in
tra
• Validate applications
er
rtn
• Deploy applications to Financial Management server
pa
Classic Application Administration:
e®
• Create application profiles
cl
ra
• Create Financial Management applications
O
• Register Financial Management server or cluster (if needed)
an
in
• Manage metadata files, including adding, changing, and
e
deleting members
us
al
on
Co pyri ght © 20 11 , Orac le a nd/or i ts affili ates. Al l ri gh ts rese rved .

rs
pe
to
Methods for Creating Applications

ed
You create applications with Performance Management Architect or Classic Application

ct
tri
Administration. Different menus and options are available for each method.
es
R
-
Performance Management Architect

yr
ta
Performance Management Architect enables you to manage, create, and deploy

ie
Hyperion applications within one interface. You create applications by using Application
pr
Creation Wizard to ensure that all required dimensions are included. Then you work in a
o
Pr
central (shared) library to modify dimensions and metadata and to audit, track, and
e®
compare information.
cl
ra
O

In Performance Management Architect, you create applications to describe the

dimensionality and other information required for a Financial Management application.
You validate and deploy the application to a Financial Management application server.
The deployment process automatically creates an application on the application server.
You validate and deploy applications from the Performance Management Architect
se
Application Library. You can also deploy applications from the Application Creation
ur
Wizard.
co
ng
Classic Application Administration
i
in
tra
Classic Administration enables you to administer Financial Management on an
er
application-by-application basis. Each application has its own metadata file, which
rtn
defines the dimensions for the application, as well as an application profile that defines
pa
the calendar and languages.
e®
You cannot edit dimensions in Performance Management Architect if the applications
cl
were created with Classic Administration. However, you can upgrade the applications to
ra
O
Performance Management Architect. They are added to Dimension Library and
an
Application Library, and you can no longer edit them with Classic Administration.
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Performance Management Architect

Application Creation Process
Use Application Creation Wizard to create applications:
se
• Select application type:
ur
co
– Set up name, type of applic ation (Consolidation)
ng
– Auto create local dimensions required in application
i
in
tra
• Select dimensions (add dimensions from Shared Library or
create new dimensions)
er
rtn
• Modify application settings
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Performance Management Architect Application Creation

ed
Process
ct
tri
With Application Creation Wizard, you create applications with all required components
es
R
to ensure successful deployment. The wizard contains applicable property and

dimension information by application type.
-
ry
ta
For Financial Management applications, you can optionally create a blank application. A
ie
blank application does not contain any dimensions. You must add the dimensions to the
o pr
application manually in the Dimension Library.

Pr
e®
You use the Configure Application Settings window to validate the application and to
cl
modify application properties, associations, and other application settings as required to

ra
pass validation.
O

Classic Financial Management Administration

Application Creation Process
se
ur
co
ng
i
in
Create profile.
tra
er
rtn
Create application.
pa
e®
Manage Metadata file.
cl
ra
O
an Load the metadata
in
file into the application.
e
us
al
on

rs
pe
to
Classic Financial Management Administration Application

ed
Creation Process
ct
tri
es
To manage Financial Management applications using Classic Administration, you must

R
perform the following tasks:

-
y
• Create an application profile that defines the time periods, number of years, and
r
ta
languages for the application.

ie
pr
• Create the application, referencing the application profile.

o
Pr
• Create or edit a metadata file that defines the account, entity, scenario, and custom
e®
dimensions, as well as the application settings.

cl
ra
• Load the metadata file into the application.

O

Oracle Hyperion Data Integration Strategy

There are various tools available to load metadata and data for Oracle Hyperion
Enterprise Performance Management applications.
• Financial Data Quality Management (FDM)
- Hyperion Financial Data Quality Management - A packaged application with a
se
highly intuitive graphical user interface that enables non-technical end users to
ur
co
handle GL trial balance data loading/mapping process with ease. Built-in
functionality includes key Sarbanes-Oxley controls such as audit trail
ng
documentation, document management, full auditing of entire data flow process,
i
in
tra
80 pre-built reports, and preventative controls. Preferred tool for HFM and
Hyperion Enterprise. Now includes ERP Integrator (ERPI).
er
rtn
• Oracle Data Integrator (ODI)
pa
e®
- Formerly Sunopsis - Oracle’s data integration platform that covers key data
integration requirements — from high-volume, high-performance batches, to
cl
ra
event-driven, trickle-feed integration processes. Recommended for IT owned and
O
managed environments with direct ERP connectivity needs. No Charge/Restricted
Use for Planning, ERPI and HFM. an
in
e
• Data Relationship Management (DRM)

us
al
- Industry leading enterprise master data change management solution that

on
facilitates rationalization of chart of accounts as well as BI/EPM dimensions and

rs
hierarchies within the most complex, heterogeneous enterprise IT environments.

pe
to
• EPM Architect (EPMA)

ed
- A feature-set within Hyperion Shared Services built for the Hyperion application
ct
tri
construction and deployment provides centralized administration for financial and

es
custom analytical applications including metadata and data administration, basic

R
data load and sync features.

-
yr
• Data Integration Management (DIM)

ta
ie
- Powered by Informatica’s PowerCenter - DIM is an integration platform similar to

opr
ODI, and as of June 2010 is on controlled availability. Premier support will be

Pr
provided until July of 2013, and commercial migration to either ODI or FDM is
e®
allowed. See doc 1267051.1 on the support portal for full details related to the
cl
status of DIM.
ra
O

Oracle EPM System

Where Do Our Integration Solutions Fit?
EPM Workspace
se
ur
co
Performance Management
ng
Applications BIBIApplications
Applications
FDM
i
in
tra
er
DRM Business Intelligence Foundation EPMA
rtn
pa
e®
ODI Fusion Middlew are
cl
ra
O
DIM
an
in
e
O LTP & O DS Data Wareho use O LAP S AP , O racle, Si ebel, Excel Business
us
S ystem s Data Mart P eopl eSo ft, Custom XM L P rocess

al
on

rs
pe
to
Integration Solutions in the Oracle EPM System

ed
ct
tri
es
R
-
ry
ta
ie
o pr
Pr
e®
cl
ra
O

Integration Feature Matrix

Functionality EPMA DRM ODI FDM DIM
Business User F riendly X X X
se
ur
Mapping Designer UI X X X X X
co
ng
Workflow Designer UI X X L im ited X
i
in
Administration and Monitoring UI X X X X X
tra
er
Debugging Environment X
rtn
Metadata Repository X X X X X
pa
e®
Scheduler X X X
cl
ra
Execution From External Process X X X
O
External Process Execution from
X X X
Workflow
an
in
EBS,
Direct ERP C onnectivity X X PSFT, X
e
SAP
us
al
on
8
rs
pe
to
Integration Feature Matrix

ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Integration Feature Matrix Cont’d

Functionality EPMA DRM ODI FDM DIM
Logging functionality X X X X X
se
Loading Unstructured content X X X
ur
co
Slowly changing dimensions X X X X X
ng
Data quality
i
in
(cleansing, integrity, X X X X
tra
accuracy, completeness, etc…)
er
Integration with real-time
X X
rtn
message queue provider
pa
Oracle’s Hyperion Planning Load Load
X X
e®
Metadata / Data Load and Extract Only Only
cl
Oracle Essbase Load Load
X X
ra
O
Oracle HFM Load Load
an
X X
in
Sophisticated Transf ormations Limited X X X X
e
us
al
on

rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Tools for Loading into Financial Management

Applications
Classic
Metadata Load Tool FM
EPMA Comments
Accepts following file extensions: APP
se
or XML (def ault), TXT or CSV. Oracle
Metadata Load F iles X
recommends using the APP or XML
ur
f ile extension.
co
Oracle D ata Integrator (ODI) See the Hyperion Data Integration
ng
Adapter for Financial X Management Adapter for Financial
i
Management Management User's Guide.
in
tra
Data Integration Management See the Oracle Data Integrator
(DIM) Adapter for Financial X Adapter for Financial Management
er
Management Online Help.
rtn
Loads from supported ERP Integrator
pa
Oracle H yperion Financial Data
source systems. See the Oracle
Quality Management ERP X
e®
X F inancial Data Quality Management
Integration Adapter for Oracle
ERP Integration Adapter for Oracle
Applications
cl
Applications Administrator's Guide.
ra
See the Oracle Hyperion Enterprise
O
Performance Management X
Performance Managem entArchitect
Architect flat files
an Administrator’s Guide.
See the Oracle Hyperion Enterprise
in
Performance Management X
Performance Managem entArchitect
e
Architect interface tables

Administrator’s Guide.
us
al
on

rs
pe
to
Tools for Metadata Loading into Financial Management

ed
Applications
ct
tri
es
R
-
ry
ta
ie
pr
o
Pr
e®
cl
ra
O

Tools for Loading into Financial Management

Applications
Classic
Data Load Tool Planning
EPMA Comments
ASCII format supporting multibyte
se
character sets (MBCS) or a file
ur
Data Load Files X encoded with the Unicode format. By
default, data files use the DAT file
co
extension.
ng
Loads data for Financial Management.
i
Performance Management X See the Oracle Hyperion Enterprise
in
tra
Architect data synchronization Performance Management Architect
Adm inistrator’s Guide.
er
Loads f rom supported ERP Integrator
rtn
source systems. See the
pa
X Oracle F inancial D ata Quality
ERP Integrator X
Managem ent ERP Integration Adapter
e®
for Oracle Applications Administrator's
cl
Guide.
ra
Oracle H yperion Financial Data Loads numeric data for Financial
O
Management. See the Hyperion
Quality Management Adapter for X X
an
Financial Data
Financial Management, Fusion Quality Management Adm inistrator's
in
Edition (FDM) Guide.
e
us
al
on

rs
pe
to
Tools for Data Loading into Financial Management

ed
Applications
ct
tri
es
R
-
y
r
ta
ie
o pr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• List two methods for creating Financial Management applications
er
• Explain various methods to load information into applications
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 3
Creating Classic Applications 3
se
ur
co
ngi
in
tra
• Describe classic administration
er
rtn
pa
• Create applications
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 3 Creating Classic Applications
Classic Administration Overview
se
ur
co
ng
i
in
Create profile.
tra
er
rtn
Create application.
pa
e®
Manage Metadata file.
cl
ra
O
an Load the metadata
in
file into the applicati on.
e
us
al
on
rs
pe
to
Classic Administration Overview

ed
ct
Classic Administration enables you to administer Financial Management on an

tri
application-by-application basis. Each application has its own metadata file, which
es
defines the dimensions for the application, as well as an application profile that defines
R
the calendar and languages. To manage applications using Classic Administration, you
-
y
must perform the following tasks:

r
ta
ie
• Create an application profile that defines the time periods, number of years, and
opr
languages for the application.

Pr
• Create the application, referencing the application profile.

e®
cl
• Create or edit a metadata file that defines the account, entity, scenario, and custom
ra
O
dimensions, as well as the application settings.

• Load the metadata file into the application.

You cannot edit dimensions in Performance Management Architect if the applications

were created with Classic Administration. However, you can upgrade the applications to
Performance Management Architect. They are added to Dimension Library and
Application Library, and you can no longer edit them with Classic Administration.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Application Profiles
You use application profiles for the following purposes:
se
• To define the languages available for entering descriptions
ur
co
• To define the application calendar
ng
• To define the application frequencies
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Application Profiles

ed
ct
You create application profiles before you create applications. An application profile
tri
defines the languages, the application calendar, and application frequencies. Each
es
application can contain only one application profile. However, you can use one
R
application profile to create many applications.

-
y
r
To create an application profile, you perform the following tasks from the Windows
ta
ie
desktop client:
opr
• Access the Select Profile process pad

Pr
e®
• Enter languages
cl
• Define the calendar

ra
O
• Edit frequencies
• Edit periods
• Save the profile

Accessing the Process Pad
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Accessing the Process Pad

ed
The Select Profile process pad guides you through the steps for defining an application
ct
tri
profile. You can edit or create a profile.

es
R
To access the process pad:

-
y
r
ta
1. Select Programs, then Oracle EPM System, then Financial Management, and then Financial
ie
Management.
opr
Pr
The Logon window is displayed.

e®
2. Enter the domain, user name, and password, and click Logon.
cl
ra
3. On the left side of the screen, select Define Application Profile.

O
The Select Profile page is displayed.

Entering Languages
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Entering Languages
ed
You can enter up to 10 languages so that you can create descriptions in multiple
ct
tri
languages for each item in your application.

es
R
To enter languages:
-
y
r
ta
1. On the Select Profile page, select Create a New Application Profile, and click Next.
ie
pr
The Enter Languages page is displayed.

o
Pr
2. Enter the languages that you want to use in the application, and click Next.
e®
The Define Calendar page is displayed.

cl
ra
O

Defining the Calendar
se
ur
co
ngi
in
tra
er
Summary Period
rtn
pa
e®
Quarter 1
cl
ra
O
an
in
e
us
Base Periods
al
on
rs
pe
to
Defining the Calendar

ed
After creating applications, you cannot change the total number of years. Therefore, be
ct
tri
sure to allow enough years in your calendars to accommodate historical and forecast
es
data.
R
-
Financial Management provides a flexible calendar. You can completely customize the
yr
base periods, summary periods, start year, and number of years; and you can use the
ta
ie
standard, custom, or manual method to define the calendar.

opr
• Standard Calendar— You can select half-years, quarters, trimesters, or months as

Pr
base periods. Base periods are created based on your selections. When you use a
e®
standard calendar, the available summary periods are determined by the selected
cl
base periods.
ra
O
Example 1: If you select months as base periods, you can select trimesters or
quarters and half-years as summary periods.
Example 2: If you select quarters as base periods, you can select half-years, but not
trimesters, as summary periods.

• Custom Calendar—You must specify a prefix for the period label and the number of
base periods. Base periods are created automatically. You must create the summary
periods manually.
• Manual Calendar—You must create both base periods and summary periods
manually.
se
ur
To define calendars:
co
1. Under Time Periods, perform one of the following actions:
ng
i
in
• Select Standard Calendar and select half-years, quarters, trimesters, or months as
tra
base periods. If you select months as base periods, select a starting month.
er
rtn
• Select Custom Calendar and enter the number of base periods and period label
pa
prefix.
e®
• Select Manually Defined Calendar and define a calendar manually.
cl
ra
2. Under Years, enter the start year and the number of years in the calendar.
O
3. Click Next.
an
in
The Edit Frequencies page is displayed.
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Editing Frequencies
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Editing Frequencies
ed
Frequencies define the running totals for the time periods available in your application;
ct
tri
for example, quarter-to-date or year-to-date. You can define up to six frequencies.

es
R
To edit frequencies:
-
r y
ta
1. In the Language list, select a language.

ie
pr
2. Perform one or both of the following actions:

o
Pr
• Edit the frequency labels and descriptions.

e®
• Add frequencies.
cl
ra
O
3. Click Next.
The Edit Periods page is displayed.

Editing Periods
se
ur
co
Add multiple Add Add
ng
periods child sibling Delete period
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Editing Periods
ed
You can edit period labels and add descriptions, add or delete base and summary
ct
tri
periods, drag periods to new locations in the hierarchy. Each level in the hierarchy
es
corresponds to a frequency. You can add levels to the hierarchy corresponding to the
R
added frequencies.
-
r y
ta
To edit periods:
ie
opr
1. Under Periods, select a base or summary period, and add multiple periods, a child,
Pr
or a sibling.
e®
2. In the Description text box, enter a description.

cl
ra
O
3. In the Language list, select a language.

4. In the Label text box, enter or change a label.
5. Click Next.
The Save Profile page is displayed.

Saving Application Profiles
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Saving Application Profiles

ct
tri
You can save the application profile locally or on the application server, using the PER
es
file extension.
R
You reference the PER file when you create an application. You can also modify an
-
yr
application profile by opening the PER file on the Financial Management Desktop. If you
ta
ie
modify an application profile, the changes do not affect existing applications that were
pr
created using the profile. However, the changes affect new applications that you create
o
Pr
using the profile.

e®
cl
To save application profiles:

ra
O
1. Click Browse to select a location where you want to save the profile.
The Save As page is displayed.
2. In the File Name text box, enter a name for the profile.

3. Click Save.
The Save Profile page is displayed with the name of the profile in
the File Name text box.
4. Click Finish.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Application Requirements
Keep this information on hand before you create an application:
se
• The name of the application server cluster
ur
co
• The name and description of the application
ng
• The file name and path of the application profile (.per file)
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Application Requirements
ed
An application consists of a set of entities, accounts, scenarios, and other dimensions

ct
tri
that you use together. You can create as many applications as you need. For example,
es
you may want to set up one application to report on tax data for several organizations
R
and another application to report on Security and Exchange Commission data for other
-
organizations.
y
r
ta
ie
Before creating an application, keep the following information on hand:

opr
• Name of the application server cluster

Pr
e®
• Name and description of the application

cl
ra
• File name and path of the application profile (PER file)

O
Here are application name guidelines:

• It can contain a maximum of 10 alphanumeric characters.

• It cannot start with a number or include spaces or special characters.

• It is not case-sensitive. For example, App1 and APP1 are considered the same
application.
• It cannot begin with HFM, HSV, and HSX, which are reserved names.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Applications
You create a classic application from the Create Application
se
menu.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Applications
ed
ct
You create a Classic Application from the Create Application page.

tri
es
R
To create applications:
-
1. In Workspace, select Navigate, then Administer, then Classic Application Administration,

y
r
ta
then Consolidation Administration, and then Create Application.

ie
pr
The Create Application page is displayed.

o
Pr
2. In the Server list, select a server.

e®
cl
3. Enter a name and description for the application.

ra
O
4. In the Application Profile text box, enter the path and name of the profile (PER) for
the application, or click Browse to locate the profile.

5. In the User Management Project list, select the Shared Services project for the
application.
6. Click Create.
• Confirm that the application is created successfully.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe classic administration
er
rtn
pa
• Create applications
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 4
Setting Up Dimensions 4
se
ur
co
ing
Objectives
in
tra
After completing this lesson, you should be able to:
er
rtn
• Access a metadata file
pa
• Edit members
e®
cl
• Edit groups of members
ra
O
• Build member hierarchies
an
• Describe the common member properties
in
e
• Set up entities
us
al
• Set up accounts and custom dimensions

on
rs
• Set up scenarios
pe
• Audit metadata
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 4 Setting Up Dimensions
Accessing Metadata Files
se
ur
co
ngi
in
tra
er
rtn
pa
Create and edit metadata files
e®
cl
ra
Load metadata file into the application
O
an
in
e
us
al
on
rs
pe
to
ed
Accessing Metadata Files

ct
tri
You use the Manage Metadata task on the Windows desktop client to work with
es
metadata files. You can:

R
-
• Create or edit metadata files without opening an application

y
r
ta
• Store metadata files locally or on the server

ie
pr
Before loading metadata files into the application, you can use the Manage Metadata
o
Pr
task to perform the following tasks:

e®
• Edit members
cl
ra
• Add and delete members

O
• Assign member hierarchies to multiple parents

• Edit group of members

• Configure application settings

Load metadata files into applications after editing the files (You must reload the files into
the applications each time that you edit the files.)
NOTE
se
You also can create and edit metadata files by using a text editor.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Editing Members
Select the
metadata type
se
ur
Search for a
co
member
ngi
in
tra
Select a
er
rtn
member to edit
from the list
pa
e®
cl
ra
O
an
in
e
Create a
us
new file
al
Open a file Save changes

on
rs
pe
Co pyri ght © 2 011, Oracle an d/or its affil ia te s. Al l righ ts rese rved.
to
ed
Editing Members
ct
tri
You use the Manage Metadata page to edit dimension members. You also use it to
es
configure application settings and to add currencies and consolidation methods. You
R
save your edits for all metadata types in a single file. For example, if you name your
-
y
metadata file AppElements, metadata for accounts, entities, scenarios, and all other
r
ta
application elements are saved in the AppElements file.

ie
opr
Pr
To edit members:
e®
1. Select Programs, then Oracle EPM System, then Financial Management, and then Financial
cl
Management.
ra
O
2. On the left side of the screen, select Manage Metadata.

The Manage Metadata page is displayed.

3. Optional: Select New File to create a new metadata file.

4. Click Open File, select the metadata file you want to edit, and click Open.
5. Select the Tree View tab.
6. In the Metadata Item list, select a dimension.
se
ur
The members of the dimension are displayed.
co
7. Perform one of the following actions:
ing
in
• In the Find text box, enter the name of the member that you want to edit, and click
tra
the right-arrow button.
er
rtn
• In the Members area, select the member that you want to edit.
pa
8. On the Member Attributes tab, modify the attributes for the member.
e®
cl
9. Repeat steps 7 and 8 for other members you want to edit.
ra
O
10. Click Save File to save the changes.
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Adding and Deleting Members
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Adding and Deleting Members

ct
tri
You use the Tree View tab on the Manage Metadata page to add and delete members
es
and set up member hierarchies. You manage the hierarchies with the buttons above the
R
Members area, as well as with shortcut menus.

-
y
r
ta
To add members:
ie
pr
1. On the Manage Metadata page, select the Tree View tab.

o
Pr

e®
cl

ra
O

• In the Find text box, enter the name of the member to which you want to add a
member, and click the right-arrow button.

• In the Members area, select a member.

4. Right-click the selected member and perform one of the following actions:
• Select Add child to add a child.
• Select Add sibling to add a sibling.
se
ur
5. Enter the name of the member and, on the Member Attributes tab, enter and/or
co
select the member attributes.
ng
i
6. Click Save File to save the changes.
in
tra
er
To delete members:.
rtn
pa
1. On the Manage Metadata page, select the Tree View tab.
e®
cl
ra
O
an
3. Perform one of the following actions: in
• In the Find text box, enter the name of the member you want to delete, and click
e
us
the right-arrow button.

al
• In the Members area, select a member.

on
rs
4. Right-click the selected member and perform one of the following actions:
pe
to
• Select Remove from parent to remove the member from the parent.
ed
• Select Remove from dimension to remove the member from the dimension.
ct
tri
Click Save File to save the changes.

es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Editing Groups of Members

Add member Delete member
se
ur
co
Cut, copy
ng
or paste
i
in
tra
Validate
er
member s
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Editing Groups of Members

ct
tri
You can manipulate groups of members in a flat-list format on the List View tab. The
es
spreadsheet-like interface displays a row for each metadata item and a column for each
R
attribute. You can:

-
y
r
• Copy cells, columns, or rows

ta
ie
• Disable combo boxes (Member information that you add or edit in list view is not
opr
validated until you change views.)

Pr
e®
• Force a validation by clicking Validate or by selecting another dimension

cl
You cannot assign parents to members or work with hierarchies in list view. All members
ra
O
that you add in list view are orphan members. After adding members in list view, you can
use the Member list tab on the Tree View tab to assign parents to the members.

Building Member Hierarchies
se
Create the member hierarchy.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
Edit member hierarc hies.

on
rs
pe
to
ed
Building Member Hierarchies

ct
tri
You setup member hierarchies on the tree view tab of the Manage Metadata pane to set
es
up member hierarchies, and you manage the hierarchies with the buttons above the
R
Members area as well as with the shortcut menus.

-
yr
You use the short-cut menu to delete members.To delete a member, right-click the
ta
ie
member, and select Remove from Parent to remove the member from its current parent
pr
or select Delete from Dimension to remove the member from the dimension.
o
Pr
e®
cl
ra
O

Creating Alternate Hierarchies
se
EastSales and WestSales occur in alternate hierarchies.
ur
co
Entity Entity
ng
[N on e] [N on e]
i
in
tra
Ge og raph ical Ge og raph ical
er
U ni te d States Acti vity
rtn
Sale sServi ces
pa
Ca li fo rnia
e®
We stSa les
Plan t1
cl
Ea stSa le s
ra
We stSa le s
O
Eme aSal es
Co nne cticut
EastSale s an Eme aServi ces

in
e
Manu fa ctu rin g

Acti vity
us
Deve lo pment
al
on
rs
pe
to
ed
Creating Alternate Hierarchies

ct
tri
You can create multiple rollup paths for data by placing a child member under multiple
es
parents. In the slide, EastSales and WestSales are members of a geographical

R
hierarchy, with Geographical as the top member. They are also members of a functional
-
y
hierarchy, with Activity as the top member.

r
ta
ie
A member has the same property settings under all its parents. When you edit a
pr
member’s properties for one parent, the properties are updated for all parents.
o
Pr
e®
cl
ra
O

Assigning Members to Multiple Parents
se
You can add a member to more than one parent.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Assigning Members to Multiple Parents

ct
tri
You use the member list tab to assign members to more than one parent. The Member
es
List tab displays a flat list of all members in the current dimension. You can drag
R
members from the Member List tab to the hierarchy in the tree view tab.
-
y
r
Any member not a part of the hierarchy defined on the tree view tab is an orphaned
ta
ie
member because it has no parent. Orphaned members are not allowed in Hyperion
pr
Financial Management. If you load a metadata file that has orphaned members, an error
o
Pr
results.
e®
By selecting the Only Show Orphaned Members check box, you can filter the member
cl
list to show orphaned members. You can then assign the orphaned members to parents
ra
O
or delete them from the dimension.

Common Member Properties
se
These properties are common to members in most dimensions:
ur
co
• Member
ng
• Description
i
in
• Security Class
tra
er
• Default Parent
rtn
• UserDefined1
pa
• UserDefined2
e®
cl
• UserDefined3
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Common Member Properties

ct
tri
The following table describes the common member properties:

es
R
Property Description Valid For

-
y
r
Member A member name of up to 50 characters, All dimensions

ta
including spaces. For Oracle databases,

ie
pr
spaces are not allowed.

o
Pr
Description A description of up to 80 characters, which All dimensions

can include spaces but not ampersands
e®
( & ).
cl
ra
Security Class The name of the security class that defines Entity, Account, Scenario,
O
the users who can access data for the ICP, Custom1, Custom2,
member. Custom3, Custom4

Property Description Valid For

Default Parent The parent to use when drilling up in a Web Entity, Account, Scenario,
Analysis report. Custom1, Custom2,
Custom3, Custom4
UserDefined1, 2, 3 Custom text to filter members in member Entity, Account, Scenario,
se
lists, rules, and reports. You can enter a ICP, Custom1, Custom2,
ur
maximum of 20 characters. Custom3, Custom4
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Property Value Inheritance
se
For properties with inheritance:
ur
co
• Updating the value of a property for an ancestor
ng
automatically updates the value for its descendants.
i
in
• Directly modifying a property of a descendant prevents it
tra
from inheriting from an ancestor.
er
rtn
Account type revenue
pa
Revenue inherited for
e®
acc ount type
cl
Acc ount type manually set
ra
to Expense, over-riding
O
inherited value
an Expense inherited for
account type
in
e
us
Note: For Metadata Manager, properties are not inherited from the parent.
al
on
rs
pe
to
ed
Property Value Inheritance

ct
tri
For some properties, descendant members inherit property values from ancestors. The
es
inheritance feature allows high-level members to share their property values with lower
R
points in the hierarchy, eliminating the need to store and maintain redundant information.
-
y
It allows newly entered members to automatically obtain their property values from the
r
ta
appropriate ancestors. Proper use of inheritance enhances the referential integrity of an

ie
pr
application and reduces maintenance requirements.

o
Pr
e®
cl
ra
O

Performance Management Architect uses the following process for determining property
values:
1. It checks whether a value was entered for the member. If a value exists, it uses it.
2. If a value does not exist, it searches the member’s ancestors for a value, and uses
se
the first entered value that it finds by moving up the ancestral tree. (A change to the
ur
properties of an ancestor member can affect descendant members that inherit its
co
value).
ng
i
3. If no ancestor has an entered value, it uses the system default property value.
in
tra
The following properties support inheritance from ancestors:
er
rtn
• Calc Attribute
pa
• Consolidation Account Type
e®
cl
• Is Calculated
ra
O
• Is Consolidated
• Number Of Decimal Places an
in
e
• Enable Custom1 Aggregation

us
al

on
rs

pe

to
ed
• Switch Sign For Flow

ct
tri
• Switch Type For Flow

es
R
Note that for Metadata Manager, properties are not inherited from the parent. All new
-
members are initially created with a standard default set of attributes regardless of the
y
r
attributes of the parents.

ta
ie
opr
Pr
e®
cl
ra
O

Guidelines for Member Names
se
Member names cannot contain these characters:
ur
co
• Period ( . ) • Braces ( {} )
ng
• Plus sign ( + ) • Comma ( , )
i
in
• Minus sign ( - ) • Semicolon ( ; )
tra
• At sign ( @ )
er
• Asterisk ( * )
rtn
• Double quotation
• Slash mark ( / )
pa
mark s ( " )
• Number sign ( # )
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Guidelines for Member Names

ct
tri
Member names can be up to 50 character in length, including spaces. Certain characters

es
cannot be used in member names for Financial Management applications.

R
-
A member name must be unique within a dimension, but not between dimensions. For
y r
system-generated members, you can edit only descriptions; you cannot edit member
ta
ie
names. Member names cannot contain spaces if you are using an Oracle database.
pr
o
Pr
e®
cl
ra
O

Setting Up Entities
se
Entities define the consolidation path for your data.
ur
co
Ent it y E ntit y
ng
[N one ]
i
[N one]
in
tra
Geogr a phic al
Ge ogra phica l
er
rtn
A ctiv ity
U nite dSta tes
pa
S ale sS er vic es
C alifor nia
e®
EastSales and We stS ale s
cl
Plant 1 WestSales occur
ra
in alternate rollups. Ea st Sale s
O
We st Sa le s
an
Em e aS ale s
Conne ct ic ut
in
E me a Ser vic es
e
Ea s tSa les
us
Ma nufac tur ing

al
Ac tivity De v elopm ent

on
rs
pe
to
ed
Setting Up Entities
ct
tri
When you run a consolidation for the Entity dimension, data rolls up from children to
es
parents as defined in the dimension hierarchy. You can create multiple consolidation
R
paths by placing an entity child member under more than one parent. In the slide
-
y
illustration, EastSales and WestSales are members of a geographical rollup, with

r
ta
Geographical as the top member, and a functional rollup, with Activity as the top
ie
pr
member.
o
Pr
e®
cl
ra
O

Requirements for Entities
se
Before adding an entity, you should have this information:
ur
co
• The parent to which the entity’s data rolls up
ng
• The currency in which data is input for the entity
i
in
• Whether adjustments through journal should be allowed for
tra
the entity
er
rtn
• The security class for the entity
pa
• Whether the entity can be a partner in intercompany
e®
transactions
cl
ra
• For statutory applications, the holding company for the entity
O
• If the entity has more than one parent, the default parent an
in
e
us
al
on
rs
pe
to
ed
Requirements for Entities

ct
tri
Holding companies are used in statutory consolidations. In a statutory consolidation, the

es
ownership structure may or may not match the dimension hierarchy. The Holding
R
Company property identifies the owner of a member; the owner is not necessarily the
-
parent of the member in the hierarchy.

y r
ta
ie
The Default Parent property is used by Hyperion Web Analysis reports to determine
pr
which parent to drill up to if a member has more than one parent.

o
Pr
e®
cl
ra
O

Entities and Journals
se
• The AllowAdj property enables posting of journal
ur
adjustments to the <Ent Curr Adjs> member for an entity.
co
ng
• The AllowAdjFromChildren property enables posting of
i
in
journal adjustments to the Parent Adjustment and
tra
Contribution Adjustment nodes of the Value dimension.
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Entities and Journals

ct
tri
Journals enable you to make adjustments to accounts after the account data is loaded or
es
entered. Unadjusted values are input to the Entity Currency member. Adjustments from
R
journals are posted to the Entity Curr Adjs member. The adjusted value in Entity Curr
-
Total is aggregated to the parent during consolidation. You use the AllowAdj property to
y
r
ta
enable or disable journal adjustments for each entity.

ie
pr
For entities that roll up to more than one parent, you can enable the
o
Pr
AllowAdjFromChildren property for the parent entities. This property enables you to
e®
apply an adjustment to the Parent Adjustment and Contribution Adjustment nodes of the
Value dimension.
cl
ra
O

Entities and Intercompany Partners
se
ur
co
ngi
in
tra
Spec ifies whether the entity
er
dis plays as a member in the
rtn
ICP dimens ion
pa
e®
cl
Spec ifies a security
ra
class for the entity for
O
intercompany transactions
an
in
e
us
al
on
rs
pe
to
ed
Entities and Intercompany Partners

ct
tri
You can specify which entities can act as intercompany partners.

es
R
IsICP
-
y
The IsICP property for entities specifies whether entities can be partners in intercompany
r
ta
transactions. A member for which the IsICP property is selected is automatically

ie
pr
displayed as a member in the ICP dimension. The ICP dimension is used to specify the
o
intercompany partner in a transaction.

Pr
e®
cl
Security as Partner
ra
You can specify more than one security class for an entity when the entity acts as an
O
intercompany partner. For example, you can give users in the United States write access
to entities in Canada for entering intercompany transactions but read access otherwise.

Entities and the ICP Dimension
se
The ICP dimension includes all members of the Entity
ur
dimension for which the IsICP property is selected.
co
ng
Members of t he Entity dimension Members of the ICP dimens ion
i
in
tra
California Plant1
er
rtn
pa
Plant1 IsICP member
attribute West Sales
e®
selected
cl
ra
West Sales
O
1000
an
in
e
us
al
on
rs
pe
Co pyri ght © 2011, Ora cle an d/or its a ffil ia te s. Al l righ ts reserved.
to
ed
Entities and the ICP Dimension

ct
tri
The ICP dimension contains a system-generated list of the members from the Entity
es
dimension for which IsICP is selected. You use the ICP dimension to specify the partner
R
for an entity when entering intercompany transactions.

-
y
r
The only properties that you can edit for members in the ICP dimension are Description
ta
ie
and Security Class.

opr
Pr
e®
cl
ra
O

Adding Currencies
se
You must add a currency to the application for each default
ur
currency assigned to an entity in the Entity dimension.
co
ngi
in
Add or edit
tra
currencies.
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Adding Currencies
ct
tri
The currencies that you define for your application store translated values for entities.
es
Each currency that you add is displayed as a system-generated member in the Value
R
dimension. You can select a currency from the Value dimension to view data values
-
translated to the currency. Currencies are also displayed as system-generated members

y r
ta
in the Custom1 and Custom2 dimensions. You use currency members in the Custom1
ie
and Custom2 dimensions for entering currency exchange rates.

pr
o
Pr
If you are using the Intercompany Transactions module, you can specify whether the
e®
currency is used for intercompany transactions and whether to multiply or divide the local
currency by the exchange rate.
cl
ra
O

The scale for a currency specifies the unit in which amounts are displayed and stored; it
identifies where the decimal point is placed. The scale also determines how the
exchange rate must be entered. For example, if data is scaled to thousands, a value of 1
entered on a data entry form is stored as 1000 in the database. Specify one of the
following values for scale:
se
ur
Value Scale
co
Blank Units
ng
i
0 Units
in
tra
1 Tens
er
rtn
2 Hundreds
pa
3 Thousands
e®
4 Ten thousands
cl
ra
5 Hundred thousands
O
6 Millions
7 Ten millions an
in
e
8 Hundred millions
us
al
9 Billions
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Setting Up Accounts
and Custom Dimensions
se
• The Account dimension defines the chart of accounts for an
ur
application.
co
ng
• Custom dimensions provide additional detail for accounts.
i
in
• Ten predefined account types provide built-in financial
tra
intelligence.
er
rtn
Account Types
pa
• Asset • Balance
e®
• Liabilities • Balance Recurring
cl
ra
• Revenue • Currency
O
• Expense • Dynamic
an
in
• Flow • Group Label
e
us
al
on
rs
pe
to
ed
Setting Up Accounts and Custom Dimensions

ct
tri
The Account dimension defines the chart of accounts for an application. Each account
es
has an account type. Account types determine how child accounts aggregate to their
R
parents and how account balances accumulate over time.

-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

Account Types and Hierarchies
se
Account types determine whether child values are added to or
ur
subtracted from their parent value.
co
ng
i
in
GrossMarg in Revenue Tan gi ble AssetsNet Asset
tra
er
rtn
To ta lR even ues Tan gi ble Assets
pa
e®
cl
Tota lCo sts Expense Ta ngi bl eAssetsDe prec Liability
ra
O
TotalRevenues are added to GrossMargin and TotalCosts are an
in
subtracted.
e
us
al
on
rs
pe
to
ed
Account Types and Hierarchies

ct
tri
When data is input to base-level accounts, results are automatically rolled up through the
es
hierarchy. Account types determine whether child values are added to or subtracted from
R
their parent value. This determination enables you to build financial calculations directly
-
into your chart of accounts.

ry
ta
ie
pr
NOTE
o
When you load data, Hyperion Financial Management assumes that the natural
Pr
sign for the data is positive.

e®
cl
ra
O

The following table describes account type behavior. For example, the Asset account
type does not total across periods. If you debit an Asset account, the value is added. If
you credit it, the value is subtracted. The default translation is the value in the
DefaultRateForBalanceAccounts field.
se
Type YTD Total Debit Credit Default Translation
ur
co
Asset No Add Sub DefaultRateForBalance Accounts
ng
Liability No Sub Add DefaultRateForBalance Accounts
i
in
tra
Revenue Yes Sub Add DefaultRateForFlow Accounts
er
Expense Yes Add Sub DefaultRateForFlow Accounts
rtn
pa
Flow Yes Add Sub None
e®
Balance No Add Sub None
cl
ra
BalanceRecurring No Add Sub None
O
CurrencyRate No N/A N/A
an N/A
in
GroupLabel N/A N/A N/A N/A
e
us
Dynamic N/A N/A N/A N/A

al
on
rs
Note: In the table, N/A represents Not Applicable.

pe
The following table shows account type behavior when it is totaled into a specific type of
to
parent account. For example, aggregated asset account values are added into parent
ed
asset and expense accounts and subtracted from parent liability and income accounts..
ct
tri
es
Parent Account
R
-
Account Type A L R E F B BR C G
ry
ta
Asset Add Sub Sub Add Add Add Add No No

ie
pr
Liability Sub Add Add Sub Add Add Add No No

o
Pr
Income Sub Add Add Sub Add Add Add No No

e®
cl
Expense Add Sub Sub Add Add Add Add No No

ra
O
Flow Add Add Add Add Add Add Add No No
Balance Add Add Add Add Add Add Add No No

Parent Account
Account Type A L R E F B BR C G
Balance Add Add Add Add Add Add Add No No

Recurring
se
ur
CurrencyRate No No No No No No No No No
co
Group No No No No No No No No No
ng
Label
i
in
tra
Dynamic No No No No No No No No No
er
rtn
The abbreviations represent the first one or two letters of the account types. “No” indicates that
pa
the account type is not aggregated into the parent account.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
o pr
Pr
e®
cl
ra
O

Time Balance and Account Types
Account type determines how balances accumulate over time:
se
ur
• Revenue, Expense, and Flow account types total across
co
periods.
ng
• Asset, Liability, Balance, Balance Recurring, and Currency
i
in
tra
Rate account types do not total across periods.
er
Qu arter 1
rtn
pa
e®
cl
Jan Feb Mar
ra
O
Total Revenues Revenue 50 75 50 175
an
in
e
us
Cash on Hand Ass et 100 150 75 75

al
on
rs
pe
to
ed
Time Balance and Account Types

ct
tri
Time balance behavior does not apply to the Dynamic and Group Label account types.
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

Dynamic Account Type
se
Accounts that use the Dynamic account type have this behavior:
ur
co
• Results are calculated on the fly; data is not stored.
ng
• Parent totals for accounts, custom dimensions, and time
i
in
periods are calculated dynamically, not aggregated from
tra
children.
er
rtn
• Period-to-date views calculate correctly
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Dynamic Account Type

ct
tri
The Dynamic account type is needed to correctly calculate parent values for custom
es
dimensions and time periods, as well as for period-to date views, for accounts that use
R
percentages and ratios.

-
y
r
For the example on the slide, note the value for Hardware for the GM_Pct_Non_Dynamic
ta
ie
account is aggregated from the percentages of its children, which yields an incorrect
pr
result. For the GrossMarginPct account, which is flagged as dynamic, the value for
o
Pr
Hardware is recalculated at the parent level, rather than aggregated from the children,
e®
which yields the correct result.

cl
ra
O

Group Label Account Type
• Used with parent accounts whose children do not need to be
se
aggregated
ur
co
• Does not create parent data value
ng
• Helps reduce database size
i
in
tra
Group Label Statistical
er
rtn
TaxRate
pa
e®
cl
SquareFootage
ra
These accounts are
O
not aggregated to a
an
UnitPr ice
in meaningful value.
e
us
UnitsSold
al
on
rs
pe
to
ed
Group Label Account Type

ct
tri
You can use the Group Label account type to group related accounts that do not need to
es
be aggregated to a total. For example, you can create a top-level account named
R
Balance Sheet Accounts that groups your balance sheet accounts. No data value is
-
stored for members with the Group Label account type; thus database size and
yr
ta
calculation time are reduced.

ie
pr
o
Pr
e®
cl
ra
O

Accounts and Custom Dimensions
se
• Custom dimensions work in conjunction with the Account
ur
dimension, providing additional detail for accounts.
co
ng
• Four custom dimensions are provided.
i
in
tra
The Sales account uses the The Cash account uses the
er
Custom1 dimens ion to capture Custom4 dimension to capture
rtn
sales detail by product. cash flow detail.
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Accounts and Custom Dimensions

ct
tri
The custom dimension names are Custom1, Custom2, Custom3, and Custom4.
es
Although you cannot change custom names, you can create an alias. The alias displays
R
in place of the predefined dimension name in data grids, data forms, journals, and
-
reporting applications such as Hyperion Financial Reporting. For example, if you give the
y r
ta
Custom1 dimension the alias Line of Business, Hyperion Financial Reporting can display
ie
Line of Business as the dimension name in reports.

opr
Pr
The following table describes the properties for custom members:

e®
cl
Property Description
ra
O
IsCalculated Use this property for custom members that are calculated by business
rules. Members with this property selected do not permit data entry.
SwitchSignForFlow Use this property to track balance sheet movement. This property
reverses the sign.

SwithTypeForFlow Use this property to track balance sheet movement. This property
reverses the default flow behavior.
Aggregation Use this property to specify the percentage of the custom member to be
Weight aggregated to the parent, with 1 representing 100%. For example, if
se
you set the aggregation weight to .5, only 50 percent of the value for the
ur
co
member is aggregated to the parent. This property is located on the
Node Attributes tab.
ng
i
Alias Use this property to assign a description to the custom dimension. This
in
tra
property is located on the Metadata Item Properties tab.
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

Assigning Custom Members to Accounts
se
ur
co
ng
i
in
tra
Cus tom1 members except for
[None] are
er
not valid for Cash.
rtn
pa
e®
ClosingBalance and its
cl
ra
descendants in Cus tom4
O
are valid for Cas h.
an
in
e
us
al
on
rs
pe
to
ed
Assigning Custom Members to Accounts

ct
tri
You can restrict an account by assigning only specific custom dimension members to the
es
account. Limiting the assignment of custom members for an account prevents errors in
R
data entry and reduces the database size. For example, if you are using a custom
-
dimension to store product detail, you can restrict the Cash On Hand account so that
yr
ta
data entry or data load into the custom dimension members for products is not allowed,
ie
since cash on hand is not tracked by product.

opr
Pr
You specify the custom dimension members and the parent members in the TopMember
e®
text boxes. Those parents and their descendants are the only members valid for data
load and data entry for the account. You have the following choices:
cl
ra
O
• Enter the keyword All to make all members of a custom dimension valid for the
account
• Specify custom dimension members

If you do not assign a top member, then only the default [None] member of that
dimension is valid for the account.
For the example on the slide, Cash has no Custom1 top member, so only Custom1
[None] member is valid for data entry and data load for Cash; the cells at the intersection
of Cash and all other Custom1 members are invalid. The Custom4 top member is
se
ClosingBalance, so ClosingBalance and its descendants are valid for data entry and data
ur
co
load for Cash.
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Balance Sheet Accounts

and Custom Dimensions
se
You can use custom dimension members to track movement
ur
detail for balance sheet accounts.
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
ClosingBalance = OpeningBalance + Increases - Decreases
an
in
e
us
al
on
rs
pe
to
ed
Balance Sheet Accounts and Custom Dimensions

ct
tri
Typical balance sheet accounts are asset or liability accounts that show a running
es
balance. You can use custom dimension members to track periodic movement for these
R
accounts. For example, you can create the custom members OpeningBalance,
-
y
Increases, Decreases, and ClosingBalance and make them valid for your balance sheet
r
ta
accounts. You can use these members to track monthly increases and decreases as well
ie
pr
to maintain a running balance for the account.

o
Pr
e®
cl
ra
O

Custom Dimensions and Account Types

• Members in custom dimensions inherit the account type
se
behavior of the account with which they are used.
ur
co
• When tracking balance sheet movement, you may need to
ng
override the account type for some custom members.
i
in
These members
tra
use the default
er
account behavior.
rtn
pa
ClosingBalance
e®
cl
OpeningBalance
ra
O
These members need to Increases an
in
show monthly values, This member needs
e
us
not YTD balances. Decreases to be subtracted from

al
closing balance.
on
rs
pe
to
ed
Custom Dimensions and Account Types

ct
tri
Members in custom dimensions inherit the account type behavior of the account with
es
which they are used. For example, if you are entering product detail in the Custom1
R
dimension for the Sales account, the custom members inherit the Income account type.
-
You must modify this default behavior when tracking balance sheet movements. To track
yr
ta
balance sheet movement, you typically store detail for increases and decreases in
ie
children that are aggregated to a parent member such as ClosingBalance. Some child
pr
o
members may need account behavior other than the account behavior of the account
Pr
with which they are associated.

e®
For the example on the slide, ClosingBalance and OpeningBalance need to use balance
cl
ra
behavior to store the opening and closing year-to-date balance for their associated
O
accounts. Increases and Decreases need to use flow behavior to store monthly debits
and credits. In addition, Decreases needs to be subtracted from, rather than aggregated
to, the total for ClosingBalance, so the sign for Decreases needs to be reversed.

Setting Up Custom Members for Balance Sheet

Movement
se
• Use SwitchTypeForFlow to change the flow behavior for custo m members:
ur
– If the associated account uses balan ce be havior (for example ,
co
asset or liabil ity accounts), the custom member switches to fl ow
ng
behavio r.
i
in
– If the associated account uses flow behavio r (fo r example, reven ue
tra
accounts), the custo m membe r switches to balance behavior.
er
• Use SwitchSignForFlow to reverse the sign for custo m membe rs.
rtn
pa
ClosingBalance
e®
cl
ra
OpeningBalance
O
Increases an
in
These members need
e
SwitchTypeForFlow. This member needs

us
Decreases SwitchSignForFlow
al
to reverse the sign.

on
rs
pe
to
ed
Setting Up Custom Members for Balance Sheet Movement

ct
tri
Custom members have special properties that you can set to facilitate the tracking of
es
balance sheet movement. The following table shows what happens to the sign behavior
R
of an account type when SwitchSignForFlow is applied:

-
yr
ta
Switches These Account Types To These Account Types

ie
pr
Asset Liability
o
Pr
Liability Asset
e®
Expense Revenue
cl
ra
Revenue Expense
O
Balance Flow
Flow Balance

The following table shows what happens to the flow behavior of an account type when
SwitchTypeForFlow is applied.
Switches These Account Types To These Account Types

Asset Expense
se
Expense Asset
ur
co
Liability Revenue
ng
Revenue Liability
i
in
tra
Balance Flow
er
Flow Balance
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
ry
ta
ie
o pr
Pr
e®
cl
ra
O

Auditing Data
Enable the EnableDataAudit property to keep an audit trail of
se
changes made to an account.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Auditing Data
ct
tri
You can select the EnableDataAudit property for those accounts and scenarios for which
es
you want to audit changes to data. The following user activities are logged in the data
R
audit:
-
r y
• Data entry
ta
ie
pr
• Data clear
o
Pr
• Data audit
e®
• Data copy
cl
ra
• Data load
O
The data audit log includes the following information:

• Username

• Activity performed
• Time modified
• Server name
• Point of view
se
ur
• Value entered for the point of view
co
ng
The data audit log information is stored in a table (APPNAME_DATA_AUDIT). You can
i
back up or extract the information in the table. You should monitor the size of the log and
in
tra
clear it on a regular basis.
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Account Properties for Intercompany
se
These are the properties for intercompany accounts:
ur
co
• IsICP
ng
• PlugAcct
i
in
• ICPTopMember
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
Copyri ght © 2 011, Ora cle an d/or its affil ia te s. Al l rights rese rved.
to
ed
Account Properties for Intercompany

ct
tri
You can enter intercompany transactions only in designated intercompany accounts.

es
R
The following table below describes the intercompany account properties.

-
yr
ta
IsICP Specifies whether the account is used in transactions. If the account is an

ie
intercompany account, you must specify a plug account. You must specify
pr
one of the following values:

o
Pr
• Y if ICP transactions, including self-ICP transactions, are allowed for

e®
the account
• N if ICP transactions are not allowed for the account
cl
ra
• R if ICP transactions are allowed for the account, but the account is
O
restricted from having ICP transactions with itself

PlugAcct Specifies the account used for identifying discrepancies in intercompany
transactions. Must be blank or the name of a valid account. Used when
IsICP is Y. If blank, no plug account is used.

ICPTopMember Specifies which top member in the hierarchy of the Entity dimension is
valid for the account. The specified member and all descendants of the
specified member are valid for the account. All other members of the
Entity dimension are not valid for the account.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

Other Account Properties
se
Additional account properties enable you to specify:
ur
• Whether account data is calculated or input
co
ng
• Whether account data is aggregated to the parent
i
in
• Whether data for custom dimensions is aggregated for the
tra
account
er
rtn
• The number of decimal places
pa
• Whether line-item detail is allowed
e®
• Rules calculation information for the account
cl
ra
O
an
in
e
us
al
on
rs
pe
Co pyri ght © 2011, Ora cle an d/or its affil iates. Al l righ ts rese rved.
to
ed
Other Account Properties

ct
tri
The following table describes the additional account properties.

es
R
-
yr
IsCalculated Specifies whether base-level accounts are calculated

ta
by a rule.
ie
pr
IsConsolidated Specifies whether values for the account are

o
Pr
consolidated to parent entities. If selected, the

account is consolidated when consolidation is
e®
performed.
cl
ra
EnableCustom1Aggr Specifies whether custom dimension data is

O
EnableCustom2Aggr aggregated for the current account.

EnableCustom3Aggr
EnableCustom4Aggr

NumDecimalPlaces Specifies the number of digits to the right of the
decimal point to be displayed for values. Must be a
value between 0 and 9.
UsesLineItems Specifies whether an account can have line items. If
se
selected, the account uses line items in scenarios for
ur
which line items are enabled.
co
CalcAttribute Text that describes the calculations in the rules file
ng
that are done for this account. This information is
i
in
displayed as part of cell information in data forms and
tra
data grids. It can contain up to 80 characters
er
including spaces.
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
ry
ta
ie
opr
Pr
e®
cl
ra
O

Setting Up Scenarios
se
• The Scenario dimension represents a set of related data, such as
ur
budget, actual, or forecast
co
• Before you add a Scenario dimension member, you should have
ng
this information ready:
i
in
tra
– The frequency for the scenario data
er
– The frequency for intercompany transa ction data
rtn
– The default data view, periodi c or year-to-date
pa
– The default data view for periods with missing d ata
e®
– Whether consol idation should be based on pe riodic or year-to-date
cl
values
ra
O
– Whether the scenari o will suppo rt process management a nd, if so,
the number of review levels an
in
– Whether accoun ts can use line-item detail in thi s scenario
e
us
– Whether changes to data for the scenario should b e tra cked in the
data audit log
al
on
rs
pe
to
ed
Setting Up Scenarios
ct
tri
The Scenario dimension represents a set of related data, such as budget, actual, or
es
forecast. Although you can define hierarchies in the Scenario dimension for grouping
R
purposes, data for child members is not aggregated to parent members.

-
ry
You can enable line-item detail for a scenario. If line-item is enabled for a scenario, you
ta
ie
can enter line-item detail in accounts that permit line-item detail.

opr
Pr
e®
cl
ra
O

Frequency and View
se
• The frequency of a scenario specifies the time period level at
ur
which data can be input, for example, months or quarters.
co
ng
• The default data view for a scenario can be either periodic
i
in
values or year-to-date values.
tra
er
Year to Date gives a
rtn
running total.
pa
January February March Quart er 1
e®
Periodic 10 10 15 35
cl
ra
Year to Date 10 20 35 35
O
an
in
e
us
al
on
rs
pe
to
ed
Frequency and View

ct
tri
Hyperion Financial Management gives you the flexibility to input and view either periodic
es
or year-to-date data values. For example, if you input your data as year-to-date values,
R
when you select Periodic as the data view, Hyperion Financial Management
-
automatically derives the periodic values from the year-to-date values.

y
r
ta
ie
Example 1: You load actual data on a monthly basis, so the frequency for the Actual
pr
scenario is set to Monthly.

o
Pr
Example 2:You forecast earnings on a quarterly basis, so you set the frequency of the
e®
Forecast scenario to Quarterly. Data input is not permitted in months.

cl
ra
O

View and Missing Data
se
• Missing data can be interpreted as either zero for the current
ur
period (Periodic) or as zero for year to date (YTD).
co
ng
• You can specify separate settings for nonadjusted data and
i
in
for adjusted data.
tra
er
rtn
pa
e®
cl
Budget scenario uses Data for February is missing.
ra
ZeroView=Periodic.
O
an
Forecast scenario uses
ZeroView=YTD.
in
e
us
al
on
rs
pe
to
ed
View and Missing Data

ct
tri
Hyperion Financial Management interprets missing data as zero for display on reports
es
and for calculating summary periods. For each scenario, you can specify whether a zero
R
for missing data is interpreted as zero for the current period (Periodic) or as zero for year
-
to date (YTD). The example in the slide shows a periodic view of data, with data missing
y
r
ta
for February. The Budget scenario interprets missing data as zero for the current period,
ie
so the value for February is displayed as zero. The Forecast scenario interprets missing
opr
data as zero for the year-to-date value. Because January has a value of 75, the current
Pr
period value for Feburary is interpreted as -75, to result in a year-to-date value of 0 for
e®
February.
cl
ra
O

Scenarios and Process Control
se
Process Control is enabled by scenario.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Scenarios and Process Control

ct
tri
Process Management is the management of the review and approval process. Data is
es
grouped into process units for review. A process unit is the combination of data for a
R
specific scenario, year, period, and entity. Each process unit can have up to 10 levels of
-
review.
y
r
ta
ie
Process Management is enabled or disabled by scenario. Select Y for the

pr
EnableProcessManagement option to enable Process Control for the scenario. Select A

o
Pr
for the EnableProcessManagement option if you want to enable Process Control with e-
e®
mail alerts.
cl
Use the MaximumReviewLevel option to specify the maximum level of reviews for
ra
O
process units for the scenario. You can enter a number from 1 to 10.

Summary
se
ur
co
• Access a metadata file
ng
i
• Edit members
in
tra
• Edit groups of members
er
rtn
• Build member hierarchies
pa
• Describe the common member properties
e®
cl
• Set up entities
ra
O
• Set up accounts and custom dimensions
• Set up scenarios an
in
e
• Audit metadata
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 5
Configuring Application Settings 5
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Configure exchange rate and translation settings
pa
• Configure consolidation settings
e®
cl
• Configure phased submission settings
ra
O
• Configure validation account settings
• Configure security settings an
in
e
• Configure document attachment settings

us
al
• Configure FDM application settings

on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 5 Configuring Application Settings
Configuring Application Settings
• Exchange rate and • Security settings
se
translation settings • Audit settings
ur
co
• Consolidation settings • Document attachment limits
ng
• Validation account settings
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
Co pyrig ht © 2 011, Oracl e and /o r i ts affil iates. All ri gh ts reserve d.

rs
pe
to
Configuring Application Settings

ed
With Classic Administration, you use the Application Setting options in Metadata
ct
tri
Manager to configure application settings. The settings are saved when you save the
es
metadata file.
R
-
You can configure the following application settings:

y
r
ta
• Exchange rate and translation settings

ie
pr
• Consolidation settings
o
Pr
• Validation account settings

e®
cl
• Security settings
ra
O
• Audit settings
• Document attachment limits

To configure application settings:

1. On the Manage Metadata page, select the List View tab.
2. In the Metadata Item list, select AppSettings.
The application settings are displayed.
se
3. Configure or change the application settings.
ur
• Click Save File to save the changes.
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Exchange Rate Settings
• Default Currency
se
• Default Rate for Flow Accounts
ur
co
• Default Rate for Balance Accounts
ing
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Exchange Rate Settings

ed
The DefaultCurrency property specifies the default application currency. Translations to

ct
tri
other currencies can be triangulated through the default currency. For example, you
es
enter rates for translating U.S. dollars to European euros and Japanese yen to European
R
euros. You can then translate U.S. dollars to yen by triangulation.

-
ry
You store exchange rates in accounts that you create in the Account dimension. The
ta
ie
DefaultRateforFlowAccounts property identifies the account that stores exchange rates

pr
to translate values for all accounts with a flow behavior.

o
Pr
The DefaultRateforBalanceAccounts property specifies the account that stores

e®
exchange rates to translate values for all accounts with a balance behavior. For example,
cl
you can use the AverageRates account to store exchange rates for flow accounts and
ra
O
the EndRates account to store exchange rates for balance accounts.

PVA Translation Method
The periodic value add (PVA) method:
se
1. Translates just the YTD change from the previous period
ur
co
at the current period’s exchange rate
ng
2. Adds this to the previous month’s translated balance
i
in
tra
Default Method PVA Method 75 – 50 = 25
er
rtn
Jan Feb Jan Feb X 2
pa
Exchange Rate 1:3 1:2 1:3 1:2
50
e®
Local Currency YTD 50 75 50 75
cl
+ 150
ra
Translated YTD 150 150 150 200
O
200
Cur rent period increase/decrease at an
in
current period rate plus prior period
e
balance
us
al
on

rs
pe
to
PVA Translation Method

ed
The default translation method is the value at the exchange rate method. This method
ct
tri
translates the entire current period balance at the current period exchange rate.
es
R
With the periodic value add (PVA) method, only the current month change in the YTD
-
value is translated at the current period exchange rate. The translation result is added to
ry
the balance from the previous period, translated at the exchange rate of the previous
ta
ie
period.
opr
For example, the January YTD balance in local currency is 50 and the exchange rate is
Pr
1:3. The YTD local currency balance for February is 75 and the exchange rate is 1:2.
e®
Here are the two ways that you can determine the February translated value:
cl
ra
O
• The value at exchange rate method translates the entire February local currency
balance (75) at the February exchange rate (1:2), for a translated balance of 150.

• The PVA method calculates the change between the January and February local
currency balance (25) and translates the change at the February rate (1:2), for a
translated value of 50. It adds this result to the translated January balance (150), for
a February translated balance of 200.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Consolidation Settings
• Org by Period
se
• Aggregation for intercompany accounts
ur
co
• Consolidation rules
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Consolidation Settings
ed
Consolidation settings enable you to specify consolidation options for your applications.
ct
tri
es
R
-
ry
ta
ie
o pr
Pr
e®
cl
ra
O

Org by Period
• Enable Org by Period if you need entity structures that
se
vary from period to period.
ur
co
• Mark entities as active or inactive for each period.
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
Co pyrig ht © 2 011, Oracl e and/o r i ts affil iates. All ri gh ts reserve d.

rs
pe
to
Org by Period
ed
You use Org by Period if entity structures vary from period to period. Using Org by Period
ct
tri
enables you to capture change of ownership between entities.

es
R
Inactive entities are not consolidated to their parent. The DefaultForActive property
-
specifies whether entities are inactive by default or active by default (0=Inactive,

ry
1=Active).
ta
ie
o pr
Pr
e®
cl
ra
O

Intercompany Aggregations
The Intercompany Aggregation Weight setting lets you specify
se
a consolidation percentage for intercompany entities to their
ur
co
parent ICP Top.
ng
i
in
tra
er
ICP Top
rtn
pa
Plant1
e®
West Sales
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Intercompany Aggregations
ed
Use the ICPEntitiesAggregationWeight property if you want to roll up only a percentage

ct
tri
of the value for intercompany transactions. A value of 1 represents 100%; for example,
es
you specify .5 for 50%.

R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Consolidation Rules
• Enable Consolidation Rules if you need to write custom
se
rules to override the default consolidation and elimination
ur
co
process.
ng
• If you select this option, you can define consolidation
i
in
methods.
tra
er
rtn
pa
'* *** *** ** *** ** *** *** ** *** *** ** *** *** ** *** ** *** ***
'* C ONS OL IDA TE RO UTI NE *
'* *** *** ** *** ** *** *** ** *** *** ** *** *** ** *** ** *** ***
e®
Su b C ons ol ida te ()
'= === === == === == === === == === === == === === == === == === ===
cl
' = Do no t Con sol id ate if E qui ty Me tho d =
ra
' === == === == === === == === === == === === == === == === === === =
' If Me tho d <> "EQ UI TY" th en
O
' C al l W ri teT oFi le ("E nti ty =" & E nt ity & " POW N=" & PO WN & " P MIN =" & PM IN & " Ac cou nt =
" & A cco un t)
an
' --- -- --- --- -- --- --- -- --- --- -- --- -- --- --- --- -- --- -
' De fa ult co ns oli dat io n
' --- -- --- --- -- --- --- -- --- --- -- --- -- --- --- --- -- --- -
in
' C all H S.C on( "" ,PC on, "" )
' --- -- --- --- -- --- --- -- --- --- -- --- -- --- --- --- -- --- -
e
us
al
on

rs
pe
to
Consolidation Rules
ed
Consolidation rules enable you to override the default consolidation process.

ct
tri
es
• Select Y to enable consolidation rules.

R
• Select R to use the default consolidation process with a reduced Value dimension.
-
y
Data for the Proportion member is only calculated; it is not stored in the database.
r
ta
ie
o pr
Pr
e®
cl
ra
O

Phased Submission Settings
Set phased submissions in the application properties.
se
ur
co
ng
Application pr operties
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Phased Submission Settings

ed
Financial Management provides flexible process management by enabling users to

ct
tri
submit data in phases. Process management by submission phases enables you to

es
subdivide a process unit into different submission groups.

R
-
You select the dimensions for submission phases. The Account, ICP, and custom
yr
dimensions support submission phases.

ta
ie
opr
Pr
e®
cl
ra
O

Validation Account Settings
Use the validation account in Process Control and for data
se
locking.
ur
co
The validation account balance m ust be zero
ng
before data can be promoted, approved, or
i
in
locked.
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Validation Account Settings

ed
You use the Validation Account field to specify a validation account for an application.
ct
tri
The balance in the validation account must be zero before data can be promoted,
es
approved, or locked. Leave the Validation Account field blank if you do not want to use
R
validation in Process Control or for data locking.

-
y r
If you are using phased submissions, you can specify a separate validation account for
ta
ie
each submission phase. An application can have up to nine submission phases. For
pr
applications that use phased submissions, the Validation Account field identifies the
o
Pr
validation account for phase 1. Validation accounts 2 through 9 identify the remaining
e®
phases.
cl
ra
O

Dimension Security Settings
Securable dimensions
se
ur
co
ng
i
in
Custom1
tra
Custom2
Account Entity Scenario ICP Custom3
er
rtn
Custom4
pa
e®
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Dimension Security Settings

ed
You can assign data security to members of the Account, Entity, Scenario, ICP, and
ct
tri
custom dimensions.
es
R
• If you enable security for a dimension, users must have read or write access to the
-
security class assigned to a member in order to view data for the member.
y
r
ta
• If you do not enable security for a dimension, all users have read and write access to
ie
the members of the dimension.

opr
Pr
• You can enable or disable metadata filtering for the application.

e®
cl
ra
O

Metadata Security Filtering
Enti ty
se
ur
co
Geo graphi cal
ng
i
in
Uni te dStates
tra
er
Cal ifornia
rtn
pa
1 00 0
e®
If users have access only to the
children of California, the
cl
Pl an t1
ra
ancestors are displayed but are
O
not selectable.
an
We stSale s
in
e
us
al
on

rs
pe
to
Metadata Security Filtering

ed
You use the EnableMetadataSecurityFiltering property to enable or disable filtering of

ct
tri
metadata based on user security access. Filtering the display of metadata facilitates
es
navigation in large applications and enables you to keep certain metadata information
R
confidential.
-
r y
When you filter metadata based on security, users see only those members of the
ta
ie
Scenario, Entity, ICP, Account, and custom dimensions to which they are granted
pr
access. Metadata filtering applies to member selection lists and to rows and columns in
o
Pr
data grids and data entry forms.

e®
In member hierarchies, users have implied access to the parents and ancestors of any
cl
member to which they are granted access. This means that users see those ancestors
ra
O
and parents in a hierarchical tree structure, but they cannot access them.

Node Security
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
Parent option limits data access
O
to these members.
an
in
e
us
al
on

rs
pe
to
Node Security
ed
The NodeSecurity property enables you to specify whether users can access Value
ct
tri
dimension members that contain parent data. In the Value dimension, the Entity
es
Currency member stores the total for a member. The Parent Curr Total member shows
R
the total for the entity after adjustments and translation to the parent currency. The Value
-
dimension members above Parent Curr Total store transformations to the data that take
y
r
ta
place before it is consolidated with the parent, such as intercompany eliminations. The
ie
Node Security property specifies whether users have access to the members above the
opr
Parent Curr Total member.

Pr
e®
• If you select Entity, users can view all Value dimension members for an entity,
cl
regardless of their access rights to the parent of the entity.

ra
O
• If you select Parent, users cannot view data for Value dimensions members above
the Parent Curr Total member unless they have read or write access to the parent of
the current entity.

For example, assume that East is a child member of North America. If a user has read
access to East, no access to North America, and Parent is selected for node security, the
user cannot view data for the Parent Adjs member for East. If Entity is selected for Node
security, the user can view data for all Value dimension members for East.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

Document Attachment Settings
• Document attachment size
se
• Number of attachments per user
ur
co
• Number of characters for cell text
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on

rs
pe
to
Document Attachment Settings

ed
The following table describes the document attachment limits:

ct
tri
es
Attribute Description
R
MaxDocAttachmentSize Maximum number of bytes for the size of document attachments.

-
y
Enter -1 for no limit or a number up to 2,147,483,647.

r
ta
Default is -1.
ie
pr
MaxNumDocAttachments Maximum number of document attachments per user. Enter -1

o
Pr
for no limit, or a number up to 2,147,483,647.

e®
Default is -1.
cl
MaxCellTextSize Maximum number of characters allowable for cell text. Enter -1

ra
for no limit, or a number up to 2,147,483,647.

O
Default is 1900 characters.

FDM Application Name Settings
You can drill through from data grid and data form cells in
se
Financial Management to an FDM application or to a
ur
co
transactional data source.
ngi
in
tra
er
rtn
pa
e®
Drill through
cl
ra
O
FDM
an
in
e
us
al
on
Copyrig ht © 2 011, Oracle and/o r its affiliates. All ri ghts reserve d.

rs
pe
to
FDM Application Name Settings

ed
If you use FDM to load data into an application, the drill-through feature enables you to
ct
tri
follow the audit trail from Financial Management to the original source document.
es
R
To configure FDM application name settings:

-
y
r
ta
• In the FDM Application Name field in the Application Settings window, specify the
ie
FDM application name.

opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Configure exchange rate and translation settings
er
• Configure consolidation settings
rtn
pa
• Configure phased submission settings
e®
• Configure validation account settings
cl
ra
• Configure security settings
O
an
• Configure document attachment settings
in
• Configure FDM application settings
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 6
Loading Metadata 6
se
ur
co
ing
Objectives
in
tra
After completing this lesson, you should be able to:
er
rtn
• Format metadata files
pa
• Load metadata from files
e®
cl
• Extract metadata to files
ra
O
• Manage user logins
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 6 Loading Metadata
Metadata Load Files
se
• Metadata load files can be in APP or XML format.
ur
co
• They can contain metadata for:
ng
– Account, Entity, Sc enario, Custom, and ICP dimensions
i
in
– Currencies
tra
– Application settings
er
rtn
– Consolidation methods
pa
• They cannot contain metadata for:
e®
– Periods
cl
ra
– Years
O
– View
an
in
e
us
al
on
rs
pe
to
ed
Metadata Load Files

ct
tri
You can include any combination of dimensions in a load file, and you can have multiple
es
load files. For example, you could have one load file for the Account and custom
R
dimensions and a separate load file for entities. For system-generated members, you
-
y
can modify some member properties, but you cannot remove members. For example,
r
ta
you can modify the description and security class for members of the Intercompany
ie
pr
Partner (ICP) dimension, but you cannot remove ICP members.

o
Pr
e®
cl
ra
O

Format for Metadata Load Files
se
• APP load files are divided into sections with an
ur
exclamation point as the section delimiter.
co
ng
• Sections can be in any order in the file.
i
in
• Fields for the items within a section are delimited with any
tra
of these characters:
er
rtn
– ,~ @#$^ &_ |:; ?\
pa
e®
cl
ra
!CURRENCIES
O
EUR;0;English=Euro;;French=Euro
USD;0;English=US Dollar;;French=Dollar Americaine an
in
GBP;0;English=British Pound;;French=Livre Anglaise
e
us
al
on
rs
pe
Copyri ght © 2 011, Ora cle and/or its affil iates. Al l rights reserved.
to
ed
Format for Metadata Load Files

ct
tri
The section for each type of metadata can be displayed only once in a metadata file. Do
es
not use a character included in the actual metadata as the delimiter.

R
-
ry
ta
ie
o pr
Pr
e®
cl
ra
O

Format for Dimensions
se
For each dimension:
ur
co
• You add a !MEMBERS= section to specify members and
ng
their properties
i
in
• You add a !HIERARCHIES= section to specify the parent-
tra
child relationship
er
rtn
For custom dimensions only, you can add a !DIMENSION
pa
section to specify an alias.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Format for Dimensions

ct
tri
You define the member properties and the member hierarchy for a dimension in
es
separate sections. If you want to specify aliases for a custom dimension, you must add a
R
!DIMENSION section for the dimension.

-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Members Sections
se
Use a separate members section for each dimension.
ur
co
Specify member properties in the correct order.
ng
Include all member properties. If you do not provide a value,
i
in
leave the field blank; do not omit it.
tra
Use Y for true and N for false.
er
rtn
pa
e®
!MEMBERS=Scenario
Actual;MTD;Periodic;Periodic;Periodic;N;Reporting;;;N;US;10;Y;Y;MTD;DefaultParent=#root;
cl
Budget;MTD;Periodic;Periodic;Periodic;N;Budgeting;;;N;US;10;Y;Y;MTD;DefaultParent=#root;
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Members Sections
ct
tri
You define the metadata dimension members in a members section. To begin a

es
members section, enter the following line, replacing the angle brackets (< >) with the
R
dimension name:
-
y
r
!MEMBERS=< >
ta
ie
pr
You must include entries for all dimension properties in the proper order. You can
o
Pr
represent missing values as empty, using delimiters. Language descriptions are optional.
If you use them, enter them after all other properties; the descriptions can be in any
e®
order. To specify a language description, use this syntax:

cl
ra
O
<language>=<description>

Accounts
List properties for Account dimension members in the following order:
Label, AccountType, IsCalculated, IsConsolidated, IsICP,
PlugAcct, Custom1TopMember, Custom2TopMember, Custom3TopMember,
Custom4TopMember, NumDecimalPlaces, UsesLineItems,
se
EnableCustom1Aggr, EnableCustom2Aggr, EnableCustom3Aggr,
ur
EnableCustom4Aggr, UserDefined1, UserDefined2, UserDefined3,
co
XBRLTags, SecurityClass, ICPTopMember, EnableDataAudit,
ng
DefaultParent, Language=description
i
in
tra
Entities
er
List properties for Entity dimension members in the following order:
rtn
pa
Label, DefCurrency, AllowAdjs, IsICP, AllowAdjFromChildren,
SecurityClass, UserDefined1, UserDefined2, UserDefined3,
e®
HoldingCompany, SecurityAsPartner, DefaultParent,
cl
ra
Language=description
O
an
Scenarios
List properties for Scenario dimension members in the following order:
in
e
us
Label, DefaultFreq, DefaultView, ZeroViewForNonadj,

ZeroViewForAdj, ConsolidateYTD, UserDefined1, UserDefined2,
al
on
UserDefined3, SupportsProcessManagement, SecurityClass,

rs
MaximumReviewLevel, UsesLineItems, EnableDataAudit,

pe
EnableJournalsAutoLabel, DefFreqForPostingFlowTrans,
to
ed
ct
Custom 1, 2, 3, and 4
tri
List properties for custom dimension members in the following order:

es
R
Label, IsCalculated, SwitchSignForFlow, SwitchTypeForFlow,

-
UserDefined1, UserDefined2, UserDefined3, SecurityClass,

yr
ta
ie
pr
ICP
o
List properties for ICP dimension members in the following order:

Pr
e®
Label,SecurityClass,Language=description
cl
ra
O
Values
List properties for Value dimension members in the following order:
Label, Language=description

Hierarchy Sections
se
!HIERARCHY sections define the Entity
ur
parent-child relationships within
co
dimensions Geographical
ng
i
Use this format:
in
UnitedStates
tra
<parent member>;<child member>
er
Represent top-level members as Calif ornia
rtn
children of an empty parent:
pa
1000
;<top-level member>
e®
Plant 1
cl
ra
!HIERARCHIES=Entity
WestSales
O
;Geographical
an
Geographical;UnitedStates
Geographical;Europe Connecticut
in
UnitedStates;California
e
Massachusetts
us
California;1000
California;Plant1
al
California;WestSales Europe
on
rs
pe
to
ed
Hierarchy Sections
ct
tri
To begin a hierarchy section, enter the following line, replacing angle brackets(<>) with
es
the dimension name:

R
-
!HIERARCHIES=<>
y
r
ta
Do not include spaces when starting sections for dimensions. For example, begin the
ie
pr
hierarchy section for the Account dimension with the following line:
o
Pr
!HIERARCHIES=Account
e®
cl
ra
O

For custom dimensions, you specify an aggregation weight for each parent-child pair.
Aggregation weight defines the percentage of amounts that are aggregated from the
child to the parent. Percentages for this attribute are scaled to hundreds, with 1.0
equalling 100 percent. Use the following syntax for Custom1 through Custom4
hierarchies:
se
<parent member>;<child member >;<Aggregation Weight>
ur
co
The following example shows a hierarchy section for a custom dimension:
ng
i
in
!HIERARCHIES=Custom1
tra
;[None];1
er
;AllProducts;0
rtn
AllProducts;Golf;.75
pa
Golf;GolfBalls;1
e®
Golf;GolfShoes;1
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Application Settings Section
se
The !APPLICATION_SETTINGS section defines settings that
ur
apply to the entire application.
co
ng
Use this format:
i
in
<Property>=<Value>
tra
er
!APPLICATION_SETTINGS
rtn
Currency=USD
pa
DefaultRateForBalanceAccounts=RATE1
DefaultRateForFlowAccounts=RATE2
e®
UsePVAForBalanceAccounts=Y
cl
UsePVAForFlowAccounts=Y
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Application Settings Section

ct
tri
The !APPLICATION_SETTINGS section defines settings that apply to the entire

es
Hyperion Financial Management application. These are the properties that you can set:
R
-
Currency UseSecurityForAccounts
y r
ta
DefaultRateForBalanceAccounts UseSecurityForEntities
ie
pr
DefaultRateForFlowAccounts UseSecurityForScenarios
o
Pr
UsePVAForBalanceAccounts UseSecurityForCustom1
e®
UsePVAForFlowAccounts UseSecurityForCustom2
cl
ra
ICPEntitiesAggregationWeight UseSecurityForCustom3
O
DefaultValueForActiveStatus UseSecurityForCustom4
ConsolidationRules UseSecurityForICP
OrgByPeriodApplication EnableMetadataSecurityFiltering
NodeSecurity

Currencies Section
se
The !CURRENCIES section defines the application’s
ur
currencies.
co
ng
You specify a currency label, scale, and descriptions for one or
i
in
more languages.
tra
Use this format:
er
rtn
<currency label >;<scale>;<operator>; <ICT>;<language>=<description>
pa
e®
!CURRENCIES
EUR;0;M;Y;English=Euro;French=Euro
cl
ra
USD;0;M;Y;English=US Dollar;French=Dollar Americaine
O
GBP;0;M;Y;English=British Pound;French=Livre Anglaise
an
in
e
us
al
on
rs
pe
to
ed
Currencies Section
ct
tri
The currencies that you define for your application store translated values for entities.
es
The scale for a currency specifies the unit in which amounts are displayed and stored for
R
the currency by identifying where the decimal point is placed. Specify one of the following
-
values for scale:

y
r
ta
ie
pr
Value Scale Value Scale

o
Pr
Blank Units 5 Hundred thousands

e®
0 Units 6 Millions
cl
1 Tens 7 Ten millions

ra
O
2 Hundreds 8 Hundred millions

3 Thousands 9 Billions
4 Ten thousands

Loading and Extracting Metadata

You access the Load Metadata and Extract Metadata tasks
se
from the view pane.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Loading and Extracting Metadata

ct
tri
You can load the following types of metadata into your applications:
es
R
• Application settings
-
y
• Currencies
r
ta
ie
• Scenarios
opr
• Entities
Pr
• Accounts
e®
cl
• Custom1, Custom2, Custom3, and Custom4

ra
O
• Consolidation methods
• System-generated accounts
• System-generated ICP and Value dimension members

Load Options
se
You can merge the metadata in the file with the existing
ur
application metadata or you can replace the existing metadata.
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Load Options
ct
tri
You can merge or replace metadata:

es
R
• The Merge option updates members that exist in the application with the information
in the file. If the file contains members that do not exist in the application, they are
-
y
r
added.
ta
ie
• The Replace option replaces the existing metadata with the metadata in the file. If a
opr
dimension member that currently exists in the application is not present in the
Pr
metadata file that you are loading, the Replace option removes the member from the
e®
application.
cl
ra
O

If you use the Replace option, existing data is not cleared. If you remove an account
containing data from the metadata file, the data exists but you cannot access it. If you
add the account later, you still cannot access the data. If you select the “Clear all
metadata before loading” option, existing members are removed from the specified
dimensions. That option then clears all data from the Hyperion Financial Management
se
application for the current dimension. You cannot use the “Clear all metadata before
ur
loading” option and the Replace option at the same time.
co
Before clearing or loading metadata, you can scan the load file to make sure that it is in
ng
the correct format.
i
in
tra
NOTE
er
The Check Integrity attribute validates that there are no conflicts with any posted
rtn
journals in the system.
pa
e®
cl
ra
Merge Versus Replace—Some Rules of Thumb
O
• Use Merge if you are adding members or updating member properties.
an
in
• Use Replace if you are moving members or deleting members.
e
us
• Use Merge with Clear all metadata before loading if you are promoting members.
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Extracting Metadata Files
se
ur
co
ngi
in
tra
er
rtn
pa
Select to save extract
e®
files in Financial
cl
Management APP
ra
format; otherwise, XML
O
format is used
an
in
e
us
al
on
rs
pe
to
ed
Extracting Metadata
ct
tri
You can extract metadata from an application and save it in XML format or in Financial
es
Management application format. Use Financial Management application format if you

R
want to edit the file manually in a text editor. Financial Management application format is
-
an easier-to-read format for manual editing.

yr
ta
ie
After making any modifications to the file with either Metadata Manager or a text editor,
pr
you need to reload it into the application for the changes to take effect.
o
Pr
e®
cl
ra
O

Managing User Logins
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Managing User Logins

ct
tri
You can use the Users on System option on the Administration menu to view logged-in
es
users for all applications and all servers, logged-in users of a specific application on a
R
specific server, logged-on users of a specific application on all servers, and logged-in
-
y
users of all applications running on a specific server.

r
ta
ie
• To view all logged-in users for all application and all servers, leave both the Server
pr
Selection and Application Selection text boxes blank.

o
Pr
• To view all logged-in users of all application on a server, enter the name of the server
e®
in the Server Selection text box and leave the Application Selection text box blank.
cl
ra
• To view all logged-in users of an application, enter the name of the application in the
O
Application Selection text box and leave the Server Selection text box blank.
• To view all logged-in users of an application on a server, enter the name of the server
in the Server Selection text box and the name of the application in the Application
Selection text box.

To log out all user of an application, enter the server and the application name and click
Log Out Users. To logout individual users, click View Logged-In Users, then click the
icon in the Logout column next to the user that you want to log out.
When you log out a user, any process that the user is executing finishes before the user
is logged out.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Disabling User Logins
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
Disabling Users Log-ins

ct
tri
If users are logged in to the system when you make load changes to metadata, their
es
session becomes invalid and they cannot save their changes. You can select Manage
R
Servers and Applications from the Administration menu to logoff currently logged on
-
y
users and disable new log-ins before performing metadata loads or other application
r
ta
maintenance.
ie
pr
• Click the Log Out users button to log all users out of the system specified in the
o
Pr
Server and Application text boxes.

e®
• Click the Disable Connections button to prevent users log-ins for the system
cl
ra
specified in the Server and Application text boxes.

O
• Click the Enable Connections button to enable users logins for the system specifed
in the Server and Application text boxes.

• Click the Enable Connections button to enable users logons for the system specifed
in the Server and Application text boxes.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Summary
se
ur
co
• Format metadata files
ng
i
• Load metadata from files
in
tra
• Extract metadata to files
er
rtn
• Manage user logins
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

O
ra
6-20
cl
e®
Pr
opr
ie
ta
ry
-
R
es
tri
ct
ed
to
pe
rs
on
al
us
e
in
an
O
ra
cl
e®
pa
rtn
er
tra
in
ing
co
Financial Management 11.1.2 Administration

ur
se
L E S S O N 7
Loading and Extracting Data 7
se
ur
co
ing
Objectives
in
tra
er
rtn
• Discuss methods of loading data in Financial Management
pa
• Describe the format of a data load file
e®
cl
• Identify guidelines for managing performance
ra
O
• Load data from a file
• Extract data an
in
e
• Export data with Extended Analytics

us
al
• Copy data within a database from one location to another

on
rs
• Remove data from a database

pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 7 Loading and Extracting Data
Data Load and Extract Methods
• Text files
se
• FDM
ur
co
• ERP Integrator
ngi
in
tra
er
Data
rtn
Text
pa
files
e®
ERP
cl
System s FDM
ra
Data Financial
O
Management
ERP Data
an
in
Integrator
e
Drill through
us
al
on
rs
pe
to
Data Load and Extract Methods

ed
ct
You can load and extract data in Financial Management using a text file, FDM, or ERP
tri
Integrator.
es
R
• A text file contain sections that map the file data to Financial Management
-
dimensions. For more information about data load text files, see “Data Load Text
y
r
Files” in this lesson.

ta
ie
pr
• FDM is an out-of-the-box data transformation tool that loads source-level financial

o
data to Financial Management applications. FDM provides an audit trail to the source
Pr
financial data, helping to ensure data integrity and mapping consistency that allows
e®
easy reconciliation of financial data. The audit trail also saves end users,
cl
ra
administrators, and auditors the time associated with data error investigation,
O
identification, and correction.

• ERP Integrator is a module of FDM that enables you to:

- Load data and metadata from an ERP source system (Oracle E-Business Suite or
Peoplesoft) into a Financial Management target application.
- Drill through from the Financial Management application and view data in the ERP
source system.
When you load data, you can also load drillable region definitions. Drillable region
se
definitions are used to define data that is loaded from a general ledger ERP source
ur
system and specifies drillable data to ERP Integrator and FDM.
co
In data grids and data forms, cells that are drillable are indicated by a light blue icon at
ng
i
the top left corner of the cell.
in
tra
For more information about FDM and ERP Integrator, see Oracle® Hyperion Financial
er
Data Quality Management, Fusion Edition 11.1.2 Administrator’s Guide.
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

Data Load Text Files
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Data Load Text Files

ed
ct
You can populate Financial Management applications by loading as many data files as
tri
needed. For example, you can load multiple data files to consolidate data from multiple
es
ledger systems, such as Oracle, SAP, and Peoplesoft.

R
-
Here are data load file guidelines:

y
r
ta
• Load files are divided into sections, with an exclamation point as the section delimiter.
ie
pr
• Sections can be in any order in the file.

o
Pr
• The default column order is Scenario, Year, Period, View, Entity, Value, Account, ICP,
e®
Custom1, Custom2, Custom3, Custom4.

cl
ra
• Fields for the items within a section are delimited with any of the following characters: , ~
O
@#$^&_|:;?\

Group Dimension Section
Sets the point of view for the data records.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Group Dimension Section

ed
The group dimension section sets the point of view for the load data that is contained in
ct
tri
the data section. For the example on the slide, the group dimension section specifies that
es
the lines of data within the data section represent data for the WestSales entity and the
R
Actual scenario for January 2010.

-
yr
Only the Period dimension can have a specified range. You need to define a single
ta
ie
member for all other dimensions that are specified in the group dimension section.
opr
The following example shows how you specify a range of periods from January to March:
Pr
e®
!Period = January...March
cl
ra
O

Data Section
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
Represents data values an
in
for one or more periods.
e
us
al
on
rs
pe
to
Data Section
ed
The data section contains lines that represent data values for one or more periods. You
ct
tri
typically specify accounts in the data section. For the example on the slide, the line of
es
business and the market for each value are also specified in the data section.
R
-
If you specify a range of periods in the group dimension section, you can include multiple
yr
values on each line, as in the following example:

ta
ie
pr
!Period = Jan...Mar
o
!Data
Pr
Actual,2010,Periodic,WestSales,USD,Purchases,[ICP_
e®
None],Chips,Customer2,[None],Increases,50000,60000,70000
cl
ra
O

Line-Item Detail Section

Line-item descriptions are
enclosed in quotation marks.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Line-Item Detail Section

ed
Data load files can also contain sections for line-item detail. Data records for line-item
ct
tri
detail include a field for the description before the data value. You must enclose the
es
description in quotation marks. Data records for line-item detail cannot include values for
R
more than one period.

-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Submission Phase Section
You can load assignments of submission groups to phases.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Submission Phase Section

ed
The Process Management feature of Financial Management enables you to assign

ct
tri
account and custom members to submission groups. The submission groups in turn are
es
assigned to submission phases for phased review. You can load the submission phase
R
assignments from a file. The load format is as follows:

-
y
r
ta
!SUBMISSION PHASE
ie
Scenario;Period;Phase#;”Group Assignment”
opr
Pr
NOTE: A load file cannot contain both submission phase records and data records.
e®
cl
ra
O

Column Order
Specifies the order of the
se
dimensions in the data section.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Column Order
ed
You can change the order of dimension members in data records. The following syntax
ct
tri
specifies the default column order:

es
R
!Column_Order = Scenario, Year, Period, View, Entity, Value, Account,

-
ICP, Custom1, Custom2, Custom3, Custom4

yr
ta
The default dimension sequence is optional. You can change the sequence to meet your
ie
needs, and you can specify multiple column-order sections in a data file. Each
opr
subsequent column-order section overrides the previously defined section.

Pr
e®
cl
NOTE: Column order impacts load performance. To maintain optimal performance,

ra
first list the Scenario, Year, Entity, and Period dimensions.

O

Financial Management Data Storage and

Retrieval
se
ur
co
California, Actual, 2010
ngi
in
tra
er
rtn
pa
Entity Currency Parent Currency Proportion
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Financial Management Data Storage and Retrieval

ed
ct
An understanding of Financial Management data storage and retrieval can help you
tri
design an efficient application. Financial Management manages data from the Financial
es
Management database in blocks called subcubes, rather than in records or rows. You
R
can think of a subcube as a grid or spreadsheet with the dimension members on the
-
y
rows and columns.

r
ta
ie
Within subcubes, data is stored at the cells formed by the intersections of the members
pr
of the subcube dimensions. All aggregations and calculations are performed on subcube
o
Pr
data that is retrieved into RAM on the application server.

e®
The number of subcubes in a Financial Management database is determined by the

cl
ra
number of members in the Entity, Scenario, and Year dimensions. Each unique
O
combination of dimension members has three subcubes: one for local or entity currency
Value dimension members, one for parent currency or translated Value dimension
members, and one for the contribution Value dimension members. The Entity, Scenario,
Year, and Value dimensions are referred to as page dimensions.

For the example on the slide, the combination of members represented by California
(entity), Actual (scenario), 2010 (year), has three subcubes, as follows:
California,2010, Actual, Local currency members
California,2010, Actual, Parent currency members
California,2010, Actual, Contribution members
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Subcube Dimensions and Performance
• Aggregations and calculations are most efficient when all
se
members needed are preloaded in RAM.
ur
co
• The subcube structure is designed to preload the members
ng
most likely to be needed for calculations and aggregations.
i
in
• Each subcube contains all members of the Account, ICP,
tra
View, and custom dimensions.
er
rtn
pa
California, Actual, 2010, Entity Currency
e®
cl
ra
Account ICP C1 C2 C3 C4 View Period
O
NetSales [ICP None] [None] Wood Retail [None] Periodic April 300
GrossSales [ICP None] [None] Wood Retail an[None] Periodic April 350
in
Discount [ICP None] [None] Wood Retail [None] Periodic April 25
e
us
Returns [ICP None] [None] Wood Retail [None] Periodic April 25

al
on
rs
pe
to
Subcube Dimensions and Performance

ed
Each subcube contains all members of the Account, ICP, View, and custom dimensions.
ct
tri
These dimensions are referred to as the subcube dimensions.

es
R
Each subcube cell represents an intersection of a unique set of page dimension

-
members (members of the Entity, Scenario, Year, and Value dimensions) with a unique
ry
set of subcube dimension members. Subcube data is retrieved in an all-or-nothing

ta
ie
manner. If a data grid, data form, or rule requests data from a subcube cell, Financial
pr
Management retrieves the entire subcube into memory.

o
Pr
For example, a data grid or rule requests the value in the cell for California, Budget,
e®
2010, Entity Currency, Cash, OpeningBalance, ICP None, Periodic, Feb. Financial
cl
Management loads the entire California, Budget, 2010, Entity Currency subcube into
ra
O
memory. It then retrieves, from the subcube, the value from the Cash, OpeningBalance,
ICP None, Periodic, Feb cell.

The Financial Management subcube structure is designed to anticipate the data needed
for calculations and aggregations and preload it into RAM. Processing data in RAM is
much more efficient than retrieving it from disk; therefore, performance is improved by
reducing the number of times data needs to be read from the database. Because,
typically, many dependencies exist between data for Account members and custom
se
dimension members, a change to data in one Account–custom combination is likely to
ur
require recalculation of data in other Account–custom combinations. Therefore, if you
co
include all Account and custom members in the subcube data loaded in RAM, you
ng
increase the likelihood that the data needed for aggregations and calculations is
i
in
available in RAM.
tra
Similar considerations apply to Period dimension data. Period values frequently depend
er
rtn
on prior period values. If you include data for all periods, you reduce the number of times
pa
that the data must be read from disk to calculate data for periods.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Guidelines for Managing Performance
se
ur
co
ngi
in
tra
This data grid opens 14
er
subcubes in memory,
rtn
one for each entity.
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Guidelines for Managing Performance

ed
You can use your understanding of subcube structure to helps you design more efficient
ct
tri
data load files, data grids, data forms, and rules. The example on the slide shows a data
es
grid with 14 entities in the rows. The data grid opens 14 subcubes in memory, one for
R
each entity.
-
y
r
If the Account and custom dimensions have a large number of members, opening
ta
ie
multiple subcubes can affect rule performance. When defining your application, you
pr
need to consider the impact of subcube size.

o
Pr
e®
cl
ra
O

Data Load Performance

Data load is more efficient if the data records are loaded by subcube. You can
accomplish this by placing the Entity, Scenario, and Year members in the Group Member
section, since these members define a subcube. For example, the following data section
is inefficient because it repeatedly switches back and forth between the subcubes for
EastSales, WestSales, and WestAdmin, rather than loading the data for each subcube
se
separately. !COLUMN_ORDER=Entity,Custom1,Custom2:
ur
co
!DATA
ng
EastSales; Chips;Fortune100;1200
i
WestSales; Chips;Fortune100;1200
in
tra
WestAdmin; Chips;Fortune100;1200
EastSales; Network;Fortune100;1200
er
rtn
WestSales; Network;Fortune100;1200
WestAdmin; Network;Fortune100;1200
pa
e®
Data Grid and Data Form Performance
cl
ra
You should also take the subcube structure into consideration when you create data
O
grids and data forms to enter data and run rules. For example, a data grid contains
an
20 entities in its rows and 3 scenarios in its columns. If you want to calculate all rows and
in
columns in the grid, you must open and calculate 60 subcubes. Performance for data
e
grids and data forms is best when the subcube dimensions are on the rows, and columns
us
and page dimensions are on the point of view.

al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Loading Data from Files
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Loading Data from Files

ed
ct
In Financial Management, you can load data from a file into an application. You select
tri
the following options for specifying the data load file:

es
R
• Merge
-
y
• Replace by Security
r
ta
ie
• Replace
opr
Pr
• Accumulate
e®
• Accumulate within File

cl
ra
O

To load data from files:

1. In the view pane, select Tasks, then Load Tasks, and then Load Data to display the Load
Data page.
2. Under Default Load Options, specify the Delimiter character and Load mode.
3. Optional: Perform one or all of the following actions:
se
ur
• Select Accumulate within File with the Merge and Replace load mode options.
co
• Select File Contains Ownership Data if the load file contains ownership data, such as
ng
shares owned. If you do not select this check box, an error occurs when you load
i
in
tra
the file.
er
• Select File Contains Process Management Data if the load file contains data for
rtn
assignment of process management submission groups to submission phases.
pa
e®
4. In the File box, enter the file name or click Browse to locate the data load file.
cl
You can load multiple data files, which are loaded in sequential
ra
O
order.
5. Click Load. an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Merge Option: Overwriting Application Data

with Load File Data
se
Application
ur
Data Load File
co
Account Value Account Value
ng
Sales 100 Sales 50
i
in
tra
Returns 20 Purchases 30
er
Purchases No Data
rtn
pa
e®
Results of Load
cl
Account Value
ra
O
Sales 50
Returns an 20
in
Purchases 30
e
us
al
on
rs
pe
to
Merge Option: Overwriting Application Data with Load File Data

ed
Select the Merge option to overwrite the application data with the load file data:
ct
tri
es
• If the data load file includes multiple values for the same point of view, the value for
R
the last entry is loaded.

-
y
• Application data that is not changed by the data load file remains in the application.
r
ta
ie
The Merge option relates to the Scenario, Entity, and Period dimensions and to valid
pr
intersections of the Account dimension.

o
Pr
The example on the slide shows data in the application before and after data is loaded
e®
using the merge option.

cl
ra
O

Replace Option: Replacing Data

with Load File Data
se
Application
ur
Data Load File
co
ng
Sales 100 Sales 50
i
in
tra
er
Purchases No Data
rtn
pa
e®
Results of Load
cl
Account Value
ra
O
Sales 50
Returns an No data
in
Purchases 30
e
us
al
on
rs
pe
to
Replace Option: Replacing Data with Load File Data

ed
Select the Replace option to replace the application data with the load file data. For each
ct
tri
unique combination of Scenario, Year, Period, Entity, and Value, the Replace option
es
clears all account values from the application. After the account values (including the
R
values in all valid intersections of custom dimensions) are cleared, the load file values
-
are loaded.
y
r
ta
ie
pr
Replace by Security Option: Loading Members

o
Pr
Select the Replace by Security option to perform a data load (in Replace mode) in which
e®
only the members to which you have access are loaded.

cl
ra
O
using the replace option.

Accumulate Option: Accumulating Application

Data with Load File Data
se
Application
ur
Data Load File
co
ng
Sales 100 Sales 50
i
in
tra
er
Purchases No Data
rtn
pa
e®
Results of Load
cl
Account Value
ra
O
Sales 150
Returns an 20
in
Purchases 30
e
us
al
on
rs
pe
to
Accumulate Option: Accumulating Application Data with Load File

ed
Data
ct
tri
Select the Accumulate option to accumulate the application data with the load file data.
es
For each unique point of view in the data file, load file values are added to the application
R
values.
-
yr
ta
ie
using the accumulate option.

pr
o
Pr
e®
cl
ra
O

Accumulate Within File Option: Loading Totals

into Applications
• Merge with Accumulate within File
se
• Replace with Accumulate within File
ur
co
ng
Application Data Load File
i
in
tra
Sales 100 Sales 50
er
rtn
Returns 20 Sales 60
pa
Purchases No Data
e®
Results of Load
cl
ra
Account Value
O
Sales 110 Merge with
an
Returns 20 Accumulate
in
within File
Purchases No data
e
us
al
on
rs
pe
to
Accumulate Within File Option: Loading Totals into Applications

ed
Use the Accumulate within File option with the Merge and Replace options. When a data
ct
tri
load file contains multiple lines of data for the same point of view and the Accumulate
es
within File option is selected, the lines are totaled, and the total is loaded into the
R
application.
-
y
r
ta
ie
using the accumulate within file option.

o pr
Pr
e®
cl
ra
O

The following table describes the load option combinations for Accumulate within File:
Load Option
Combination Description
Merge with All values for the same point of view in the data file are added, and
Accumulate within File the data in the application is overwritten with the total.
se
Replace with The values from the application are cleared, all values for the same
ur
Accumulate within File point of view in the data file are added, and the total is loaded into the
co
application.
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Extracting Data
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
Numbers in parentheses
an
indicate that multiple
mem bers are selected.
in
e
us
al
on
rs
pe
to
Extracting Data
ed
ct
From Financial Management applications, you can extract base-level input data and the
tri
following types of calculated data:

es
R
• Consolidated data for parent entities

-
y
• Base accounts and custom dimension members that are calculated by rules
r
ta
ie
• Parent accounts that intersect with their respective custom top member and [ICP
pr
Top] member (If the CustomTop metadata attribute is blank or ALL, the [None]
o
Pr
member is used.)
e®
cl
ra
TIP: The Extract Data functionality is useful as a means to verify application data.
O

To extract data:
1. In the view pane, select Extract Tasks, and then Extract Data.
2. Select the POV members.
You must specify a member for the Scenario dimension and the
Year dimension. You can specify multiple members for the
se
Period, Entity, and Account dimensions. The example on the slide
ur
shows three members of the account dimension selected.
co
ng
3. Select one of the following data views to extract:
i
in
• Year to Date
tra
er
• Periodic
rtn
• Scenario Default
pa
e®
4. Optional: Perform one or both of the following actions:
cl
ra
• Select Extract Calculated Data to extract calculated data.
O
an
• Select Extract Process Management Data to extract process management data.
in
5. Click Extract.
e
us
• Only valid data intersections are extracted. For each unique point of view, data is
al
presented in a single data line in the file. Group headings are not created.
on
rs
• Extracted data is saved as an ASCII file, and you can view and modify it in a text
pe
file editor.
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Exporting Data with Extended Analytics
An Extended Analytics star schema enables you to use
se
Essbase to analyze data and produce reports.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Exporting Data with Extended Analytics

ed
ct
You use Extended Analytics to export data from the Financial Management database to
tri
a star schema or a flat file. You can export data to a file with or without headers.
es
Exporting without headers can facilitate importing into external systems. You then use
R
Integration Services to import the data to an Essbase database.

-
y
r
ta
ie
NOTE: To access Extended Analytics, you must be assigned the security role of
opr
Extended Analytics or Administrator.

Pr
e®
cl
ra
To export data with Extended Analytics:

O
1. Open the application.

2. Select Consolidation Administration, and then Extended Analytics.


• In the Template drop-down list, select a saved POV template.
• Create a template and include the POV dimension members that you want to
export.
se
4. From the Destination Database (DSN) drop-down list, select the database to which
ur
co
you are exporting the star schema.
ng
Do not use the same Financial Management database as the destination database.
i
in
tra
er
NOTE: You cannot use Templates and DSN for extracting data with Flat
rtn
Files.
pa
e®
cl
5. In the Relational Table Prefix text box, enter a prefix to identify the tables for the star
ra
schema.
O
an
in
NOTE: The prefix can contain up to 10 alphanumeric characters and must
e
us
start with a letter. The default prefix is the name of the application.
al
on
rs
6. From the Extract Format drop-down list, select one of the following schema formats:
pe
to
• Standard (Use this schema for the Standard, Metadata Only, and Selected
ed
Metadata Only aggregation types.)

ct
tri
• Selected Metadata Only (Use this schema to extract only the metadata for the
es
selected dimension members.)

R
• Essbase
-
y
r
ta
• Data Warehouse
ie
pr
7. Optional: Clear the Exclude Dynamic Accounts option to include dynamic accounts in
o
Pr
the star schema.

e®

cl
ra
• Select Create Star Schema.

O
• Select Update Star Schema.

Copying Data
The number of source and destination
periods m ust be the same.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
You can increase or an
in
decrease the copied
e
us
values by a factor.
al
on
rs
pe
to
Copying Data
ed
You can copy data from a specific scenario, year, period, or list of periods to a specific
ct
tri
destination. The frequency of the source periods must equal the frequency of the
es
destination periods. If you copy a list of periods, the number of source periods must
R
equal the number of destination periods. For example, on the slide the source and
-
y
periods are both twelve.

r
ta
ie
For the Value dimension, you can copy values only from the Entity Currency member, or
pr
you can include system and exchange rate accounts.

o
Pr
You can use the Mode option to specify how data is copied into an application; that is,
e®
you can merge, replace, or accumulate the data. For all Mode options, copy and load
cl
ra
data options are the same.

O

You can define a factor by which copied data values are multiplied. Source amounts are
multiplied by the factor before data is copied to the destination. For example, you can
increase all Actual 2010 data values by 15% when you copy them to Forecast 2011. The
multiplication factor that you define is not applied to system accounts. For example, on
the slide a value of 1.15 in entered in the Factor box.
se
To copy data:
ur
co
1. In the View pane, select Tasks, then Data Tasks, and then Database Management.
ng
2. Select the Copy Data tab.
i
in
tra
3. Under Source, select a scenario and year, and a period or a range of periods from
er
which to copy data.
rtn
pa
4. Under Destination, select a scenario, year, and the same number of periods to which
to copy data.
e®
cl
5. Under Copy Members, select the entity and account data to copy.
ra
O
6. Under Options, select the Mode and View options.
an
7. Under Value, select Entity Currency, or Rates And System, or both.
in
e
us
8. In the Factor box, enter a factor to multiply the copied data.

al
9. Optional: Select one or all of the following check boxes:

on
rs
• Copy Cell Text

pe
to
• Copy Derived Data

ed
• Enable Detailed Logging

ct
tri
10. Click Copy Data.

es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Removing Data
You can remove (clear) data from a specified range in the
se
database.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Removing Data
ed
ct
You can remove (clear) data for selected entities and accounts for a specific scenario,
tri
year, period, or list of periods. When you clear data, both base and parent entities are
es
cleared. However, only base-level accounts are cleared.

R
-
y
To remove data:
r
ta
ie
1. In the View pane, select Tasks, then Data Tasks, and then Database Management.
opr
Pr
2. Select the Clear Data tab.

e®
3. Select the scenario, year, period, entity, and account.

cl
ra
4. Under Value, select Entity Currency, or Rates And System, or both.

O
5. Optional: Select Enable Detailed Logging.

6. Click Clear Data.

se
ur
Summary
co
ng
i
in
tra
• Discuss methods for loading data in Financial Management
er
• Describe the format of a data load file
rtn
pa
• Identify guidelines for managing performance
e®
• Load data from a file
cl
ra
• Extract data
O
• Export data with Extended Analytics an
in
• Copy data within a database from one location to another
e
us
• Remove data from a database

al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 8
Entering Data by Using Data Grids 8
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Access data grids
pa
• Create data grids
e®
cl
• Enter, save, spread, and calculate data in data grids
ra
O
• Enter cell text and line-item detail
an
• Retrieve data from Financial Data Quality Management
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 8 Entering Data by Using Data Grids
Data Grids Overview
Use data grids to enter, view, or edit data manually in Financial
se
Management.
ur
co
ng
Enter manually View Edit
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Data Grids Overview

ed
Use data grids to enter, view, or edit data manually. Dimensions are displayed in rows
ct
tri
and columns.
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Accessing Data Grids
se
ur
Manage Documents button
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
Select a grid
us
al
on
rs
pe
to
Accessing Data Grids

ed
ct
You access data grids on the data grids tab of the Manage Documents task.
tri
es
R
To access data grids:

-
1. Click the Manage Documents button to open the document manager.

y
r
ta
ie
2. Select the Data Grids tab to display a list of available data grids.
opr
3. In the Document column, select a grid.

Pr
e®
Alternatively
cl
ra
1. In View pane, select Documents, then Data Grids.

O
A list of data grids is displayed in the View pane.

2. Click a grid.

Creating Data Grids
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
New Data Grid button

al
on
rs
pe
to
Creating Data Grids

ed
ct
You create data grids on the data grids tab.

tri
es
R
To create data grids:

-
1. Click the Manage Documents button to open the document manager.

y
r
ta
ie
2. Click New Data Grid to display a data grid.

opr
Pr
e®
cl
ra
O

Changing Grid Layout and Display
se
ur
co
Click the Grid Settings
ng
button.
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Changing Grid Layout and Display

ed
On the data grid, click the grid settings button on the toolbar to access the Grid Settings
ct
tri
dialog box. There, you can change the grid layout and display.
es
R
Grid Layout
-
y
You use the Layout tab to move dimensions between three areas: Page Dimensions,
r
ta
Row Dimensions, and Column Dimensions. For example, you can move the Period
ie
pr
dimension from the Page Dimensions area to the Column Dimensions area to view
o
periods in columns. The dimensions that you select for the page area are displayed on
Pr
the grid POV.

e®
cl
ra
Grid Display
O
You use the Display Options tab to select cell, label, row suppression, page size, and
scale options.

You can select whether to view data, calculation status, or process review level. The
calculation status indicates, for example, whether data needs to be calculated,
translated, or consolidated. The review levels indicate the process management level for
combinations of data called process units. You can easily toggle between the data and
the calculation status and review level. The data grid automatically refreshes to reflect
changes.
se
When you enable descriptions, they are displayed in the language that you specified in
ur
co
the User Preferences dialog box. If you select to view both labels and descriptions, the
dimension member is displayed as “Label - Description.” For entities, the member is
ng
displayed as “Parent.Entity - Description,” where Description is the description of the
i
in
tra
entity, not of the parent entity.
er
In addition, you can select a scale value to determine how data is displayed. For
rtn
example, if the currency U.S. dollars (USD) is defined with a scale of 3, the value
pa
300,000 USD is displayed as 300.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Selecting Members for Dimensions
se
Click to select members for POV dimensions.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
Click to select m embers for rows and columns.
an
in
e
us
al
on
rs
pe
to
Selecting Members for Dimensions

ed
You select the members for the row, column, and POV dimensions:
ct
tri
es
• Select the members for the POV dimensions by clicking the links displayed on the
R
POV bar.
-
y
• Select members for the row or column dimension by clicking a dimension name in
r
ta
the row or column heading area.

ie
opr
Pr
e®
cl
ra
O

Selecting Members for Rows and Columns
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
A row or column is
ra
displayed on the grid
O
for each member that
an you select.
in
e
us
al
on
rs
pe
to
Selecting Members for Rows and Columns

ed
You use the POV selector to select the members that you want to be displayed in the
ct
tri
rows and columns. For each member that you select, a row or column is displayed on the
es
grid.
R
-
y
r
ta
NOTE: For POV dimensions, you can select only one member.
ie
opr
Pr
e®
cl
ra
O

Selecting Members Through Member Lists
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
The member list displays the an
in
children of Gross Margin.
e
us
al
on
rs
pe
to
Selecting Members Through Member Lists

ed
Member lists display subsets of related members that belong to a dimension. They can
ct
tri
reduce the time that you spend browsing the hierarchy of members. For example, if Italy,
es
France, and UK are used frequently in the POV for the Entity dimension, create a
R
member list named European Region, and then select from the list instead of browsing
-
through the hierarchy of the Entity dimension.

y
r
ta
ie
Financial Management provides various system-defined member lists, such as

pr
[Descendants] and [Children]. System-defined member list names are enclosed in

o
Pr
brackets ( [ ] ).
e®
When you select members for rows or columns, use member lists as follows:
cl
ra
• Select a member list and then, in the Selector area, select the members that you
O
want to place in the selected values list.

• Select a list, and do not select a member. Rows or columns are created for all
members of the selected member list.

You can filter member lists by using a top member (parent). Enter a parent member
name in the top member text box, and then press Enter. The example on the slide shows
the Account dimension. If you select the [Children] member list and enter GrossMargin
as the top member, the selector area lists descendants of the GrossMargin member.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

Saving Data Grid Settings
Click the Save
se
Settings button.
ur
co
ng
i
in
tra
er
Private data grids are displayed in
rtn
the Documents list of the users who
pa
created them.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Saving Data Grid Settings

ed
By saving your data grid settings, you can reduce the time that you spend selecting
ct
tri
dimensions for rows and columns.

es
R
When you click the Save Settings button, the Save Document page is displayed, and you
-
specify the name and description for the grid settings.

y
r
ta
You can select the Private option to save the data grid settings as private data grids.
ie
Private data grids are displayed in your Documents list.

opr
Pr
e®
cl
ra
O

Entering and Saving Data
se
ur
co
ng
Saves data
i
in
tra
Refreshes data, and
discards unsaved changes
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Entering and Saving Data

ed
ct
Data grids provide a spreadsheet-like user interface for entering data. After entering
tri
data, you use the Submit Data button to save changes to the database. You use the
es
Reset Data button to refresh the form with the most recent data from the database,
R
discarding any unsaved changes.

-
yr
ta
Cell Color
ie
pr
Cell color is a visual guide to cell content:

o
Pr
• Green—Green cells contain calculated data. Calculated cells are read-only and thus
e®
do not accept user input.

cl
ra
• Light Yellow—Light yellow cells accept data entry.

O
• Orange—Orange cells contain invalid intersections of dimension members. You

cannot enter data in invalid cells.
• Dark Yellow—Dark yellow cells contain data that is modified but not saved.

• Beige—Beige cells contain locked data. Locked data cannot be edited.
Saving Data and Parent Totals

When you save data, Financial Management automatically calculates totals for the
parent members of the dimension hierarchy. For example, if you enter and save data for
the Hotel and Meals members, a total is calculated for their parent Total Expenses.
se
ur
For the Entity dimension, the focus is consolidation. Consolidation sums data from
co
children and aggregates data to parents. Data does not aggregate to parent members
ng
until consolidation occurs.
i
in
tra
er
Clearing Data
rtn
You can enter “NODATA” in a cell to clear data from the database. For example, you
pa
might enter or load data into an incorrect intersection and want to clear the data without
e®
entering zeros in the database. In Financial Management, NODATA is the only text that
cl
can be entered in a cell.
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

Filling Multiple Cells
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Filling Multiple Cells

ed
At times, you may need to enter the same data in multiple cells of a row.
ct
tri
es
To enter data in multiple cells:

R
-
1. Enter the data in an input cell of the row.

y
r
ta
2. Press the Shift key, and select the cell from which you want to replicate the data.
ie
opr
3. Select the destination cells, right-click, and select Fill.

Pr
e®
cl
ra
O

Spreading Data
You can spread data from summary periods to base periods.
se
ur
co
Enter the amount
in the sum mary
ng
time period.
i
in
tra
er
rtn
pa
Click the Submit
Data button.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Spreading Data
ed
In data grids, you can enter data in parent-level members of the Period dimension and
ct
then spread the data among the base periods. For the example on the slide, you enter
tri
es
an amount of 75,000 in the Quarter 1 member that contains the months of January,
R
February, and March. Then you distribute 75,000 among the three months.
-
y
After entering data in parent-level members, you must submit the data to spread it
r
ta
among the base periods and to save it to the database.

ie
pr
For blank base periods, spread data is distributed evenly across the periods. For base
o
Pr
periods that contain data, spread data is distributed proportionally. For example, if the
e®
months of January, February, and March list 3, 3, and 4 as the existing data, entering 100
cl
in the Quarter1 member distributes 30, 30, and 40 to January, February, and March,
ra
respectively.
O

Calculating Data
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
Right-click a cell to access
an
Price = Sales/UnitsSold
in the Calculate option.
e
us
al
on
rs
pe
to
Calculating Data
ed
Your application can include calculation rules that are not based on parent-child
ct
relationships. For the example on the slide, the rule calculates the value for the Price
tri
es
account by dividing the Sales account by the UnitsSold account.

R
Values for accounts that are calculated by rules are not calculated automatically when
-
y
data is saved. You must use the Calculate option to calculate values for these accounts.
r
ta
ie
When you calculate data, calculation rules run for the selected scenario, year, period,
pr
entity, and value. In addition, all prior time periods that are within the year and that were
o
Pr
not previously calculated are calculated. For example, if you calculate data for June, data
that was not previously calculated for January to May is calculated.
e®
cl
The Calculate option is available only for cells for which data has changed since the cells
ra
were last calculated. You can use the Force Calculate option to calculate cells for which
O
data has not changed. For example, a cell uses a formula that calculates the current
period value based on the previous period value. If the value for the previous period
changes, you can use Force Calculate to recalculate the current period value.

Adding Cell Text and Custom Documents
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
Attaches a custom
O
document.
an
in
e
us
al
on
rs
pe
to
Adding Cell Text and Custom Documents

ed
ct
In a data grid, you can add text notes and document attachments to cells by using the
tri
Cell Text option.

es
R
-
NOTE: You can identify cells with text notes by their blue border.
yr
ta
ie
pr
o
Pr
Cell Text
e®
Text notes provide information about the cell data. For example, use text notes to
cl
communicate with reviewers or to explain the assumptions behind your data. You set the
ra
O
maximum length for cell text in the Application Settings section of the application. The
default limit is 8,000 characters.

Custom Documents
You can attach one or more documents to cells in data grids, data forms, and Process
Control cells. You must first upload the documents to the Financial Management
database. The documents are stored in the database, and you can apply security
classes to them.
You can load different types of documents into the Financial Management database; for
se
ur
example, Excel documents (XLS), Word documents (DOC), text files (TXT), and
co
PowerPoint files (PPT). Uploaded documents are called custom documents. When you
ng
click the Attach button in a Web data entry form or a data grid, you select from the list of
i
in
custom documents.
tra
You load, extract, organize, view, and delete custom documents on the Custom
er
Documents tab in the same way that you work with Financial Management documents.
rtn
To attach or extract custom documents to or from the server, you must be assigned the
pa
Manage Custom Documents security role or you must be an administrator.
e®
cl
You can limit the number of attachments allowed per user and the size (in bytes) of each
ra
attachment.
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Adding Line-Item Detail
se
ur
co
ngi
in
tra
er
Adds a
rtn
new row
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Adding Line-Item Detail

ed
ct
In a data grid, you can add line-item detail to base-level accounts and scenarios for
tri
which line-item detail is enabled and the member attribute UsesLineItems is selected.
es
R
To add line-item detail:

-
y
r
ta
1. Right-click a cell.
ie
pr
2. Select Cell Line Item Detail to display the Cell Line Item Detail dialog box.
o
Pr
3. Enter one or more rows of detail, and click Add.

e®
cl
ra
O
NOTE: A cell with line-item detail displays the total of the rows of line-item
detail. Cells with line-item detail have a red border. Also, line-item
details does not consolidate.

Retrieving Data from FDM
• You can drill back from data grid cells in Financial
se
Management to FDM.
ur
co
• Source documents for data are archived in FDM.
ngi
in
tra
er
rtn
pa
e®
Drill back
cl
ra
O
FDM
an
in
e
us
al
on
rs
pe
to
Retrieving Data from FDM

ed
ct
If you use FDM to load data, you can drill from data grids to FDM to view the source data.
tri
You can view additional information about the data load, including POV information, load
es
date and time, the user who performed the load; and you can drill through to
R
intercompany transactions.
-
y
r
ta
ie
To retrieve data from FDM:

o pr
1. From a data grid, select an input cell that was configured for FDM.
Pr
e®
2. Right-click and select Drill through to FDM to launch FDM with the point of view for the
cl
selected cell.
ra
O

se
ur
Summary
co
ng
i
in
tra
• Access data grids
er
• Create data grids
rtn
pa
• Enter, save, spread, and calculate data in data grids
e®
• Enter cell text and line-item detail
cl
ra
• Retrieve data from Financial Data Quality Management
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 9
Creating, Loading, and Extracting

Member Lists 9
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe system-defined and user-defined member lists
pa
• Create static and dynamic member lists
e®
cl
• Load and extract member lists
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 9 Creating, Loading, and Extracting Member Lists
Member Lists Overview

A member list is a subset of related members that belong to a
single dimension.
se
Account Dim ension
ur
Member List
co
Inco me
Be fo re Ta xe s
i ng
in
Gross Ma rgi n
tra
To ta l R even ue
Total Re ven ue
er
rtn
Sal es
pa
e®
Sa les In te rco
Total Co sts
cl
To ta l C osts
ra
O
Sala rie s
an
in
Intere st Expen se
e
Ad min Expe nse

us
Ad min Expen se
al
on
rs
pe
to
Member Lists Overview

ed
ct
Member lists can reduce the time that you spend browsing member hierarchies in data
tri
grids and data forms. For the example on the slide, if Total Revenue, Total Costs, and
es
Administration Expenses are used frequently in the point of view for the Account
R
dimension, your administrator can create a member list named Profit. You can then
-
y
select members from the list, instead of browsing through the hierarchy of the Account
r
ta
dimension.
ie
pr
You can also use member lists in rules and in Financial Reporting and Web Analysis. For
o
Pr
example, you can write a rule that calculates all members of a member list, or run a
e®
report for all members of a member list.

cl
ra
Two types of member lists are used in Financial Management:

O
• System-defined member lists

• User-defined member lists

System-Defined Member Lists
se
ur
Income
co
Be fo re Ta xes Children of Base
Gro ss Ma rgin
parent member list
ng
member list
i
in
To ta l Reve nue
tra
Sal es
Sa le s Sal es
er
Sal es In te rco
rtn
Sa le s Interco Sal es In te rco
Sa la ries
pa
To ta l C osts
e®
In te rest C hgs
Sal ari es
cl
ra
Admin Expe nse
O
Interes t Exp en se
Ad min Expe nse

an
in
e
us
al
on
rs
pe
to
System-Defined Member Lists

ed
After an application is created and metadata is loaded, the system generates system-
ct
tri
defined member lists.

es
R
System-defined member lists group members according to common properties, such as

-
all children of a specified parent or all base members of a specified dimension.

r y
ta
For the example on the slide, Sales and Sales Interco are shown as children of Total
ie
Revenue, and Sales, Sales Interco, Salaries, Interest Charges, and Administration
o pr
Expense are shown as base members in a hierarchy.

Pr
e®
cl
ra
O

User-Defined Member Lists
Create user-defined member lists to customize your
se
application.
ur
co
Income
ng
Before Taxe s
Static Dynamic
i
in
member list member list
tra
Gross Marg in
Sal es
er
Total Reve nu e
rtn
Total Co sts
Sal es Interco To ta l Reve nue
pa
Sala rie s
e®
Total Co sts Total Co sts
In terest C hgs
cl
Admin Exp ense
ra
Sa lari es
Admin Expe nse
O
In te rest Expe nse
an
in
Admin Expe nse
e
us
al
on
rs
pe
to
User-Defined Member Lists

ed
User-defined members lists are static or dynamic.

ct
tri
es
Static member lists contain user-specified dimension members. To add members to static
R
lists (for example, to add accounts to a static Account member list, such as
-
ProfitandLoss), you must add the members manually.

r y
ta
Dynamic member lists contain members that, at runtime, meet specified criteria.
ie
Because the lists are built dynamically, they are updated when they are retrieved.
opr
Pr
For the example on the slide, Total Revenue, Total Costs, and Administration Expense
e®
are shown as members of the static list and Total Costs, Salaries, Interest Expense, and
cl
Administration Expense are shown as members of the dynamic list.

ra
O
TIP: Static lists are helpful when you need a standard list, such as a list of tax
accounts.

Creating Member Lists
• Create member lists in a text file that you load into your
se
application.
ur
co
• Include definitions for all user-defined member lists in a
ng
single file.
i
in
tra
Sub EnumMemberLists()
er
Dim aEntityLists(2)
rtn
Dim aAccountLists(1)
If HS.Dimension = "Entity" Then
pa
aEntityLists(1) = "UnitedStates"
e®
aEntityLists(2) = "Europe"
HS.SetMemberLists aEntityLists
cl
ra
ElseIf HS.Dimension = "Account" Then
O
aAccountLists(1) = "ProfitAndLoss"
an
HS.SetMemberLists aAccountLists
End If
in
End Sub
e
us
al
on
rs
pe
to
Creating Member Lists

ed
ct
You can use a text editor, such as Microsoft Notepad, to create member list files.
tri
es
Member list creation process:

R
1. Identify the number of lists for the dimension and the name and number ID for each
-
y
list.
r
ta
ie
2. Following Microsoft Visual Basic script syntax, add members to each static and
pr
dynamic list.
o
Pr
The example on the slide shows the following syntax for creating two Entity member lists
e®
and one Account member list:

cl
ra
O
Sub EnumMemberLists ()
Dim aEntityLists(2)
If H.S Dimension = “Entity” Then

aEntityLists(1) = “UnitedStates”
aEntityLists(2) = “Europe”
HS. SetMemberLists aEntityLists
ElseIf HS.Dimension = “Account” Then
aAccountLists(1) = “ProfitAndLoss”
se
HS. SetMemberLists aAccountLists
ur
co
End If
ng
End Sub
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Identifying Member Lists in a File
Use the EnumMemberLists subroutine to specify the number
se
of member lists and the names of the member lists.
ur
co
ngi
in
Dim aEntityLists(2)
tra
er
rtn
pa
e®
cl
ra
O
End If
an
End Sub in
e
us
al
on
rs
pe
to
Identifying Member Lists in a File

ed
Each member list file must include an EnumMemberLists subroutine to specify which
ct
tri
dimensions have member lists, the number of lists for each dimension, and the name of
es
each member list.

R
-
The following table describes the syntax shown in the slide:

y
r
ta
ie
Syntax Description
o pr
Dim aElementLists(n) Specifies the number of lists for each statement.

Pr
Element = dimension name

e®
n = total number of member lists for this element

cl
ra
For example, if the file contains four member lists for the
O
Entity dimension the syntax is Dim aEntityLists(4).

Syntax Description
aElementLists(n) = “ListName” Specifies the name and numeric ID for each list.
n = ID number of the list
“ListName”= name of the list
se
For example, to set the name for the first Entity member list
ur
as UnitedStates, use aEntityLists(1) =
co
“UnitedStates”.
ng
HS.SetMemberLists Sets the specified names and numeric IDs.
i
in
aElementLists
tra
er
For example, to set the name and ID number of the lists for
rtn
the Entity dimension use HS.SetMemberLists
pa
aEntityLists.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
o pr
Pr
e®
cl
ra
O

Creating Static Member Lists
Use the EnumMembersInList subroutine to create static and
se
dynamic member lists.
ur
co
ngi
in
Sub EnumMembersInList()
tra
If HS.Dimension = "Account" Then
If Hs.MemberListID=1 Then
er
rtn
HS.AddMemberToList "Sales"
HS.AddMemberToList "SalesInterco"
pa
HS.AddMemberToList "Purchases"
e®
HS.AddMemberToList "PurchasesInterco"
End If
cl
ra
End If
O
End Sub
an
in
e
us
al
on
rs
pe
to
Creating Static Member Lists

ed
You use the EnumMembersInList subroutine to add members to a list. For a static
ct
tri
member list, you list all members of the list in the script.
es
R
For all dimensions except Entity, you use the HS.AddMemberToList statement, in which
you must specify a member. For the Entity dimension, you use the Hs.AddEntityToList
-
y
r
statement, in which you must specify a member and its parent.

ta
ie
opr
Pr
e®
cl
ra
O

The following table describes the functions you use within the EnumMembersInList
subroutine to add members to lists:
Syntax Description
HS.MemberListID=n Specifies the member list by its numeric ID.
n = numeric ID assigned to the member list in the
se
EnumMemberLists subroutine
ur
co
HS.AddMemberToList "Member" Adds members to a list for dimensions other than
ng
Entity.
i
in
Member = member name
tra
The following example adds the Sales member to
er
the member list:
rtn
HS.AddMemberToList "Sales"- Specifies the
pa
members to include in the list.
e®
HS.AddEntityToList “Parent”, “Member” Adds members to a list for the Entity dimension.
cl
ra
Parent = parent of the member that you are adding
O
Member = a member of the Entity dimension
an
The following example adds the California
in
member to the member list:
e
us
HS.AddEntityToList “UnitedStates”, “California”

al
on
Sample Script
rs
pe
The following member list script creates two Entity member lists and one Account
to
member list:
ed
ct
tri
Dim aEntityLists(2)
es
R

-
y
r
ta
ie
o pr

Pr
e®
cl
End If
ra
End Sub
O
Sub EnumMembersInList()
If HS.MemberListID=1 Then

HS.AddEntityToList "UnitedStates","California"
HS.AddEntityToList "UnitedStates","Connecticut"
ElseIf HS.MemberListID=2 Then
HS.AddEntityToList "Europe","Italy"
HS.AddEntityToList "Europe","France"
HS.AddEntityToList "Europe","UK"
End If
se
ur
co
If HS.MemberListID=1 Then
ng
HS.AddMemberToList "Sales"
i
HS.AddMemberToList "SalesInterco"
in
tra
HS.AddMemberToList "Purchases"
HS.AddMemberToList "PurchasesInterco"
er
End If
rtn
End If
pa
End Sub
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Creating Dynamic Member Lists

for the Entity Dimension
Dynamic member lists select members from a dimension based
se
on specified criteria.
ur
co
ng
Loops through the dimension members
i
in
I f HS. Dimen sion = "Ent ity" Then
tra
I f HS. Membe rList ID=1 Then
ELi =HS.E ntity .List ("","" )
er
rtn
For i=Lb ound( ELi) to Ubo und(E Li)
I f (St rComp (HS.E ntity .DefCu rrenc y(ELi (i)),
pa
“ USD”, vbTex tComp are)= 0) The n
e®
H S.Add Entit yToLi st "" ,ELi(i )
E nd If
cl
Nex t
ra
E nd If
O
E nd If
Creates an arr ay of the an
Checks the currency property
in
dimension members of each mem ber
e
us
al
on
rs
pe
to
Creating Dynamic Member Lists for the Entity Dimension

ed
For Dynamic member lists, instead of listing all members of the member list, you enter
ct
tri
rules to select members that meet specified criteria. Criteria are member properties such
es
as currency or account type. The list is generated dynamically each time it is accessed
R
by a user.
-
y
r
For the example on the slide, the list of entities is received into an array. For each entity
ta
ie
in the array, the value of the DefaultCurrency property is compared with the preferred
pr
value of USD. If the value is equal to USD, the entity is added to the list. Then the next
o
Pr
entity in the array is processed.

e®
cl
ra
O

Creating Dynamic Member Lists

for Other Dimensions
se
ur
Cr eates an array of the Loops through the
co
dimension member s dimension members
ngi
in
A li=HS .Acco unt.L ist(" ","")
tra
F or i= Lboun d(ALi ) to Uboun d(ALi)
er
If ( StrCo mp(HS .Acco unt.A ccount Type( ALi(i )),"a sset" ,vbTe xtComp are)= 0) Th en
rtn
HS. AddMe mbert oList ALi( i)
End If
pa
Next
e®
cl
ra
Checks the account type
O
property of each member
an
in
e
us
al
on
rs
pe
to
Creating Dynamic Member Lists for Other Dimensions

ed
The example on the slide shows the following syntax for creating a dynamic member list
ct
tri
in the Account dimension for all accounts of the Asset account type:
es
R
Ali=HS.Account. List(““,””)
-
For i=Lbound(ALi) to Ubound(ALi)

ry
If (StrComp(HS.Account.AccountType(ALi(i)),”asset”,vbTextCompare)=0)
ta
ie
Then HS.AddMembertoList ALi(i)

pr
End If
o
Pr
Next
e®
cl
ra
O

Loading Member Lists
You access the Load Member Lists task from the Load Tasks
se
menu in the view pane.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Loading Member Lists

ed
ct
After creating a member list script file, you load it into your application. You access the
tri
Load Member Lists page from the Tasks section of the Web client. Before loading the file,
es
you can scan to verify that it is formatted correctly. When you modify the file, you must
R
reload it into the application.

-
y
r
ta
ie
TIP: If you click the Scan button, the syntax is checked; the members that are
opr
retrieved are not checked.

Pr
e®
cl
ra
To load member lists:

O
1. In View pane, select Tasks, then Load Tasks, and then Load Member Lists.
The Load Member Lists page is displayed.

2. Click Browse to find the member list you want to load.

3. Select the member list and click Open.
4. Optional: On the Load Members Lists, click Scan to check the syntax of the member
list.
5. Click Load to load the member list.
se
ur
6. Confirm that the member list is loaded successfully.
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Extracting Member Lists
You access the Extract Member Lists task from the Extract
se
Tasks menu in the view pane.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Extracting Member Lists

ed
ct
You extract member lists in the Extract Member Lists page. Extracted member lists are
tri
saved as ASCII files. By default, member lists have the file extension LST.
es
R
To extract member lists:

-
y
r
ta
1. In View pane, select Tasks, then Extract Tasks, and then Extract Member Lists.
ie
pr
The Extract Member Lists page is displayed.

o
Pr
2. Follow the instructions on the page to extract member lists.

e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe system-defined and user-defined member lists
er
• Create static and dynamic member lists
rtn
pa
• Load and extract member lists
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

L E S S O N 1 0
Managing Rules with Calculation

Manager 10
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe Financial Management rules and Calculation Manager
pa
• Create rules
e®
cl
• Create rules sets
ra
O
• Validate rules
• Deploy rules an
in
e
• Import and export Calculation Manager objects

us
al
• Import script-based rules files

on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 10 Managing Rules with Calculation Manager
Financial Management Rules
Financial Management rules provide powerful, customized
se
calculations, such as:
ur
co
• Ratios and variance analyses
ng
• Currency conversions and exchange rate differences
i
in
tra
• Custom consolidations
er
• View-only cells
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Financial Management Rules

ed
ct
Financial Management rules provide powerful, customized calculations, such as:

tri
es
• Calculate data that cannot be calculated through a hierarchical aggregation, such as

R
ratios and variance analyses

-
y
• Perform complex currency conversions and calculate exchange rate differences

r
ta
ie
• Perform custom consolidations for statutory reporting requirements

opr
Pr
• Prevent data entry for specific combinations of members

e®
cl
ra
O

Calculation Manager Overview
se
ur
co
ngi
Calculation Manager
in
tra
er
rtn
pa
e®
cl
ra
O
Design Validatean Deploy
in
e
us
al
on
rs
pe
to
Calculation Manager Overview

ed
ct
You use Calculation Manager to design, validate, and deploy calculations that enable you
tri
to solve business problems. The user interface provides a graphical design environment
es
that enables you to build complex calculations easily.

R
-
Calculation Manager enables you to break rules into individual rule components that can
y
r
ta
be shared between applications. For example, you can create a formula to calculate days
ie
sales outstanding, and then reuse the formula in all applications that require this
pr
calculation.
o
Pr
Rules created in Calculation Manager are stored in the Calculation Manager database.
e®
The rules are validated against the dimension metadata in Performance Management
cl
ra
Architect. To activate the rules in your Financial Management applications, you deploy
O
the rules from Calculation Manager to your Financial Management application server.

Calculation Manager for Classic Applications
se
ur
co
ngi
in
tra
er
rtn
Classic application
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Calculation Manager for Classic Applications

ed
In addition to Performance Management Architect applications, you can also create and
ct
tri
deploy rules to classic applications from Calculation Manager. Run Length Encoding
es
(RLE) scripts are supported for both classic and Performance Management Architect
R
applications.
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Rule Types and Rule Sets
se
The Calculate rules run
ur
when you select Calculate
co
in a data grid or data form.
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Rule Types and Rule Sets

ed
The rules for each Financial Management application are organized into nine rule types.
ct
tri
For each rule type, you create a rule set. You can create more than one rule set for each
es
type, but you can deploy only one rule set for each type to the application.
R
You execute the rules for a rule type by performing actions within Financial
-
y
Management. For the example on the slide, when you select Calculate from the shortcut
r
ta
menu of a data grid, the rules for the Calculate rule type are executed.
ie
opr
Pr
e®
cl
ra
O

The following table describes the Financial Management rule types:
Rule Type Description

Calculate Set account values based on formulas. You can run Calculate rules from
data grids, data forms, and the Process Control task. Calculate rules are
executed automatically when you consolidate an entity.
se
Dynamic Create formulas for accounts with the Dynamic account type. Dynamic
ur
accounts accurately calculate YTD and Periodic values that are not
co
calculated correctly by the aggregation of base member values.
ng
Dynamic rules are valid only for dynamic accounts, and are executed
i
in
automatically when you open data grids and data forms that contain
tra
accounts with the account type Dynamic.
er
Translate Perform custom currency translations. You can run Translate rules from
rtn
data grids, data forms, and the Process Control task. Translate rules are
pa
executed automatically when you consolidate if the parent currency is
different than the child currency.
e®
cl
Consolidate Perform customized consolidation and elimination calculations. You run
ra
Consolidate rules from data grids and the Process Control task.
O
Equity Pick Up Perform customized ownership calculations for entities. You run Equity
an
Pick Up rules from data grids or the Manage Equity Pick Up task.
in
Allocate Set allocate data from a source to multiple destinations. You run Allocate
e
us
rules from data grids or data forms.

al
Input Configure parent members to allow data entry. Input rules are executed
on
when you open an application.

rs
pe
No Input Configure members to prevent data entry. No Input rules are executed
when you open an application.
to
ed
Transaction Configure accounts to allow posting of data from the Intercompany

ct
Transaction module. Transaction rules are executed when you open an

tri
application.
es
R
Generic Reuse rules in rule sets for more than one rule type. For example, you
create a rule for rounding that you use in your Calculate and Translate
-
y
rule sets. You must add Generic rules to a rule set for one or more of the
r
ta
other rule types in order to deploy them in a Financial Management

ie
application. You can nest generic rule sets within rules sets for any rule
pr
type.
o
Pr
Global Use Generic rules to set global values that you can use in all calculation
e®
types. These rules run before all other rule types. For example, you
could create a rule that defines variables for names of your exchange
cl
ra
rate accounts and then reuse the variables as needed in rules for other
O
calculation types.

Rules
Loop
component
se
Condition
Formula
ur
component
com ponent
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
Scope of the Condition component
The formula and range components ar e
in
located within the scope of the Condition
e
us
com ponent.
al
on
rs
pe
to
Rules
ed
A rule is a Calculation Manager object that consists of calculations grouped into

ct
tri
components. You design a rule by dragging components from the Rule Palette to the
es
flow chart. Each component performs a separate task.

R
-
y
Condition Components
r
ta
A condition component comprises conditional statements (If...Then statements) that are

ie
pr
either true or false. You insert other rule components within the scope of the condition
o
component. If the condition is true, Calculation Manager executes the components within
Pr
the scope of the condition component. If the condition is false, the components within the
e®
condition are skipped.

cl
ra
You use condition components to limit the members for which a rule is executed. For
O
example, if a calculation is valid only for the Forecast scenario, you can create a
condition to test whether the current scenario in the point of view is Forecast.
For the example on the slide, the loop and formula components are within the scope of
the condition component. They are executed only if the condition specified for the
condition component evaluates to true.
Loop Components
A loop component repeats the execution of the components within its scope based on
specified criteria.
Types of loop components:
se
• A member range component creates a loop for a range of members based on a
ur
Financial Management member list. Execution of the components within the scope of
co
the loop is repeated for each member in the list.
ng
i
• A data range component creates a loop for all accounts that have data for a
in
tra
specified point of view. For example, if you create a data range component for
California, Actual, January, the components in its scope are executed for all accounts
er
rtn
that have data for the California entity for the January period and the Actual scenario.
pa
• A fixed loop component creates a loop that repeats for a specified number of
e®
iterations. For example, you could specify a loop that repeats the execution of the
cl
components in its scope 10 times.
ra
O
The example on the slide shows a member range component that uses the Descendants
an
member list of the TotalAssets account as its range. Because the OpeningBalance
in
formula component is within the scope of the member range component, it is executed
e
us
for each account that is a descendant of the TotalAssets account.

al
on
Script Components
rs
A script component contains rules written in the Microsoft Visual Basic Script (VB Script)
pe
programming language. Prior to version 11.1.1 of Financial Management, you were

to
required to write all rules in VB Script. You can use the script component to incorporate
ed
rules written in VB Script into Financial Management 11.1.1 and later applications.
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Formula Components
se
ur
co
ngi
in
tra
er
rtn
Destination Source
pa
e®
cl
ra
O
Condition an
Functions
in
e
us
al
on
rs
pe
to
Formula Components
ed
Formula components are the primary components of a rule. You use them to assign
ct
values to accounts or to clear account values.

tri
es
The formula component comprises calculation statements that assign values to accounts
R
based on your defined formula. To create the calculation statements, you add rows to
-
y
grids in the formula component.

r
ta
ie
Each calculation statement in the grid consists of a destination expression and a source
pr
expression.The destination expression is displayed on the left of the equal sign, and the
o
Pr
source expression is displayed on the right. You use dimension keywords to identify the
e®
dimensions for the members included in the expressions. Dimension keywords consist of
cl
the first letter of the dimension followed by a pound sign ( # ). For example, A#Sales
ra
identifies the Sales member of the account dimension.

O

Data is retrieved from the dimension members specified in the source expression and
written to the members specified in the destination expression.
• You can specify members from the account, custom, and ICP dimensions in the
destination expressions.
• You can specify members from any dimension in the source expression.
se
• You can use standard math operators to perform calculations on the source data
ur
co
before it is written to the destination. For example, you increase the source data
values by 10% before writing the values to the destination.
ng
i
in
• You can also add condition statements to grids. The calculation statements in the
tra
grid are executed only if the condition evaluates to true.
er
rtn
The example on the slide shows a formula component with two grids:
pa
• In the first row of the first grid, the destination is the Surplus member of the Account
e®
dimension. The source expression retrieves values for the TotalLiabEquity and
cl
TotalAssets accounts and calculates their difference.
ra
O
• You can use functions within source and destination expressions. In the second grid,
an
the Last function is used with the P# keyword and the Prior function is used with the
in
Y# keyword to retrieve values for the last period of the prior year. The condition
e
us
statement verifies that it is not the application’s first year. If the condition is true, the
al
calculation statement in the grid is executed; otherwise, it is skipped.

on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
o pr
Pr
e®
cl
ra
O

Creating Rules
Drag com ponents from the Rule Palette to th e flow chart.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
Use the Property pane tabs to configure the selected component.

al
on
rs
pe
to
Creating Rules
ed
ct
You create rules for the rule types required by your application. When you add
tri
components to a rule, you can create components for the rule or you can reuse
es
components. For example, you create a formula component for Rule1 named Balances
R
that retrieves opening balances for accounts. When you create Rule 2, you can reuse the
-
y
Balances component.
r
ta
ie
opr
NOTE: You cannot reuse loop or condition components. However, you can copy and
Pr
paste loop or condition components between rules.

e®
cl
ra
O

To create rules:
1. Log on to Workspace.
2. In Performance Management Architect, select Navigate, then Administer, and then
Calculation Manager.
3. Expand Financial Management.
se
ur
4. Expand the application for which you want to create a rule.
co
5. Expand the rule type for the rule. For example, if you are creating Calculation rules,
ng
expand Calculate.
i
in
tra
6. Under the rule type, right-click Rules and then select New.
er
rtn
The New Rule dialog box is displayed.
pa
7. In the Name text box, enter a name for the rule.
e®
8. Click OK.
cl
ra
O
Rule Designer is displayed.
an
9. Add components to the Rule Designer flow chart in the order that you want them to
in
be executed:
e
us
• Add a new component to the rule: Drag a component from the New Objects
al
section of the Rule Palette to the Rule Designer flow chart.

on
rs
• Reuse a component from an existing rule: Drag a component from the Existing
pe
Objects section of the Rule Palette to the Rule Designer flow chart.
to
ed
10. Select each component in the flow chart, and configure the component as required
ct
for your calculation.

tri
es
11. Select File, and then Save.

R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Rule Sets
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Rule Sets

ed
ct
Before you can deploy the rules for a rule type, you must create a rule set and add the
tri
rules to it. The order that you place the rules in the rule set determines their order of
es
execution.
R
-
You can include one rule set inside another rule set. For the example on the slide, you
yr
create a rule set named SalesAndPrice for all sales-related rules. You include the
ta
ie
SalesAndPrice rule set within another rule set named CalcRules, which contains all rules
pr
for the Calculate rules type.

o
Pr
e®
To create rule sets:

cl
ra
1. In Calculation Manager, expand Consolidation.

O
2. Expand an application.
3. Expand the rule type for the rule set that you want to create.

4. Under the rule type, right-click Rule Sets and then select New.
The New Rule Set dialog box is displayed.
5. In the Name text box, enter a name for the rule set.
6. Click OK.
se
Ruleset Designer is displayed.
ur
co
7. In Rule Set Palette, drag the first rule or rule set to Ruleset Designer.
ng
8. Continue dragging rules and rule sets from Rule Set Palette to Ruleset Designer until
i
in
you add all rules required for the current rule set.
tra
er
rtn
NOTE: The order in which the rules are displayed in Ruleset Designer
pa
determines the execution order for the rules. You can use the Up
e®
and Down arrows to reorder the rules.
cl
ra
O
9. Select File, and then Save.
an
in
10. Select File, then Close, and then Current.
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

Validating Rules
Form ula
components
se
ur
co
ngi
in
tra
er
rtn
pa
Rules Rule sets
e®
cl
ra
O
Script
an components
in
e
us
al
on
rs
pe
to
Validating Rules
ed
ct
You validate rules to verify that the syntax does not contain errors and that all dimension
tri
members referenced in the rules exist in the application. You can validate an entire rule
es
set, an individual rule, or an individual formula or script component. You cannot deploy
R
rules to Financial Management applications until all validation errors are corrected.
-
y r
ta
To validate rules:
ie
opr

Pr
e®
2. Expand an application.
cl
3. Right-click a rule set, rule, formula component, or script component, and select
ra
O
Validate.
The Information dialog box displays any validation errors.
4. Click OK.

Deploying Rules
se
ur
co
ngi
in
tra
er
rtn
Rule sets
pa
currently
deployed
e®
cl
ra
O
an
in
Rule set selected
e
us
for deployment
al
on
rs
pe
to
Deploying Rules
ed
ct
You cannot execute rules within Financial Management applications until you deploy the
tri
rules from Calculation Manager to the application.

es
R
Deployment guidelines:
-
y
• You can deploy only one rule set from each rule type. However, the rule set can have
r
ta
other rule sets nested within it.

ie
opr
• You do not need to deploy rules sets for all rule types. For example, you can deploy
Pr
only a rule set for the Calculate rule type.

e®
• When you deploy rules, all existing rule sets in the application are erased and
cl
ra
replaced with the rules sets that you deploy.

O
To deploy rules to an application:

1. In Calculation Manager, select View, and then Deployment View.
2. Expand Consolidation.

3. Expand the application for which you want to deploy rules.

4. Expand the To Be Deployed node.
5. Expand the rule type for which you want to deploy rules.
6. Select the rule set to deploy.
se
7. Right-click the application name, and select Deploy.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Importing and Exporting

Calculation Manager Objects
se
ur
co
ng
Import
i
in
tra
er
rtn
pa
Export
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Importing and Exporting Calculation Manager Objects

ed
ct
You can import Calculation Manager objects from or export them to XML files. You can
tri
import and export individual Calculation Manager objects or an entire application. If you
es
import or export an entire application, all rules, rules sets, rule components, and
R
variables for the application are in a single XML file.

-
yr
When you export Calculation Manager objects from an application to an XML file, the
ta
ie
application name is included in the file. When you import the file, the Calculation
pr
Manager objects are imported into the application named in the file. You can override the
o
Pr
target application at the time of import.

e®
cl
To import Calculation Manager objects:

ra
O
1. In Calculation Manager, select File, and then Import.

The Import dialog box is displayed.

2. Click Browse and select an XML file.

3. Optional: Click Update Details to modify the target application.
NOTE: If you do not modify the target application, the Calculation Manager
objects are imported into the same application from which they were
se
exported.
ur
co
ng
4. Select one of the following import options:
i
in
tra
• Select Override Existing Objects to replace Calculation Manager objects that have
er
the same name as objects in the XML file.
rtn
• Select Skip Existing Objects to skip objects in the XML file that exist in Calculation
pa
Manager.
e®
cl
• Select Error out for duplicates to halt the import process if duplicate object names are
ra
in Calculation Manager and the XML file.
O
5. Click OK. an
in
e
us
To export individual Calculation Manager objects:

al

on
rs
2. Expand the application that contains the object to export.

pe
to
3. Right-click a rule set, rule, formula component, or script component, and select
ed
Export.
ct
tri
The File Download dialog box is displayed.

es
R
4. Click Save.
-
y
The Save As dialog box is displayed.

r
ta
ie
5. In the File Name text box, enter a name for the file.
opr
6. Browse to the location where you want to save the file.

Pr
e®
7. Click Save.
cl
ra
O

To export all Calculation Manager objects for an application:

2. Right-click an application, and select Export.
The File Download dialog box is displayed.
se
3. Click Save.
ur
The Save As dialog box is displayed.
co
ng
4. In the File Name text box, enter a name for the file.
i
in
tra
5. Browse to the location where you want to save the file.
er
6. Click Save.
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Importing Script-Based Rules Files
se
ur
co
ng
Sub Translate
i
in
'Calculate change du e to exchange rates
tra
HS.Trans "C1#Rate","C1#Open ing","A#EopRate"
HS.Trans "C1#Move","C1#P_L","A#Eo pRate",A#A
er
End Sub
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Importing Script-Based Rules Files

ed
ct
Prior to version 11.1.1 of Financial Management, you were required to create rules by
tri
using VB Script. Rules for all calculation types were included in a single script-based
es
rules file (RLE) that you loaded into Financial Management. You can import RLE files
R
into Calculation Manager using either the import menu or the Rules Migration tool.
-
y
r
ta
ie
Importing Using the Import Menu

pr
o
You can import RLE files using the same procedure that you use to import Calculation
Pr
Manager objects from XML files. When you import RLE files, for each SUB procedure of
e®
a valid calculation type in the RLE file, a rule set containing one business rule and one
cl
script component is created. The example in the slide shows the SUB TRANSLATE
ra
procedure of an RLE file and the following Translate type objects that are created in
O
Calculation Manager:
• A script component named Translate_Component that contains all script from the
procedure

• A rule named Translate_Rule that includes Translate_Component as a component

• A rule set name Translate_Ruleset that includes Translate_Rule as a member
Importing with the Rules Migration Tool

You can use the Financial Manager Rules Migration tool to import RLE files. The tool
se
creates Calculation Manager components for each VB Script statement found in an RLE
ur
file. For example, a Calculation Manager If...Then component is created for each VB
co
Script If...Then statement in the RLE file. The Rules Migration tool save the components
ng
to a single XML file. You import the XML file into Calculation Manager using the Import
i
in
menu.
tra
er
The Financial Manager Rules Migration tool is located in the Consultant Utilities folder of
rtn
the Financial Management folder on your Financial Management application server.
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe Financial Management rules and Calculation Manager
er
• Create rules
rtn
pa
• Create rules sets
e®
• Validate rules
cl
ra
• Deploy rules
O
an
• Import and export Calculation Manager objects
in
• Import script-based rules files
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 1
Provisioning Users and Groups 11
se
ur
co
ng
i
Objectives
in
tra
er
rtn
• Describe the four levels of security in Financial Management
pa
• Assign user roles
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 11 Provisioning Users and Groups
Levels of Security
There are four levels of security in Financial Management.
se
ur
co
ng
User authentication Task security Artifact security Data security
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Levels of Security
ed
ct
Financial Management provides security at four levels: task, artifact, and data security,
tri
and user authentication.

es
R
Security guidelines:
-
y
• Users must provide a valid ID and password to log on to the system.

r
ta
ie
• Users can launch only tasks to which they have access. For example, users can be
pr
given the ability to create journals but not to post journals.

o
Pr
• Users can open only artifacts (documents and objects) to which they have access.
e®
Securable documents and objects include data grids, data forms, journals,
cl
ra
workspaces, and system reports.

O
• Users can view and modify data, and filter metadata within selection lists, only for
dimension members to which they have access.

User Authentication
• Users must provide a valid user ID and password to
se
access applications.
ur
co
• Financial Management leverages authentication providers
ng
such as LDAP and MSAD.
i
in
• User and groups must exist in the authentication directory.
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
User Authentication
ed
User login information is stored outside the applications in an authentication directory. An

ct
tri
authentication directory is a centralized store of users and passwords, user groups, and
es
corporate information, such as employee IDs and e-mail addresses. The following types
R
of authentication directories are supported:

-
ry
• LDAP version 3 or later

ta
ie
• MSAD on Windows 2000 SP3 or later

o pr
You can grant access to your Financial Management applications to any user or group
Pr
that is identified in the authentication directory. When, for an application, you grant
e®
access to a group, the users in the group are also granted access to the application.
cl
ra
O

Task Security
• You can specify the tasks that users and groups are
se
authorized to perform.
ur
co
• Other tasks are removed from the menus to present a
ng
customized user interface.
i
in
• Task security is assigned through user roles.
tra
er
rtn
Journals administrator ’s view Journals user’s view
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Task Security
ed
Task security determines the tasks that a user can access within an application. You
ct
tri
assign task security by assigning one or more user roles to a user. Each role is
es
associated with a set of tasks. For the example on the slide, a journal administrator can
R
access more tasks than a journal user and remove other tasks from menus to present a
-
customized user interface.

y
r
ta
ie
Online help lists available user roles.

o pr
Pr
e®
cl
ra
O

Artifact Security
Access levels for security classes:
se
• All
ur
co
• Metadata
ng
• Read
i
in
tra
• Promote
er
• None
rtn
pa
e®
cl
ra
O
Security class = SalaryRelated
an
in Access = Payroll
e
us
al
on
rs
pe
to
Artifact Security
ed
Artifact security is assigned through security classes. Security classes are a grouping
ct
tri
mechanism for assigning security access to sets of related members, documents, or

es
other objects.
R
-
For the example on the slide, for salary accounts, you assign the SalaryRelated security
yr
class to data grids and forms. You then assign the SalaryRelated security class to Payroll
ta
ie
department users and no access to other users. Then, the salary account data grids and
pr
forms are available only to Payroll department users.

o
Pr
e®
cl
ra
O

Data Security
• Data security is also assigned through security classes.
se
• To users, for specified dimension members, you assign All,
ur
co
Metadata, Read, Promote, or None access.
ngi
in
tra
er
Secur ity Class Assigned Access Level
rtn
pa
East Region All
West Region Metadata
e®
United Kingdom Read
cl
Singapore None
ra
O
an
in
e
us
al
on
rs
pe
to
Data Security
ed
Setting up data security enables you to protect data and prevent unauthorized users from
ct
tri
changing data. For example, you can restrict access to certain data elements within an
es
application.
R
-
For the example on the slide, different security classes are assigned different access
ry
levels. East Region is assigned access level of All, West Region is assigned access level
ta
ie
of Metadata, United Kingdom is assigned access level of Read, and Singapore is

pr
assigned access level of None.

o
Pr
e®
cl
ra
O

User Roles Overview
• User roles determine what tasks a user can perform in the
se
application.
ur
co
• Financial Management provides user roles that can be
ng
assigned to users and groups of an application.
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
User Roles Overview

ed
ct
You use user roles to limit the tasks that users can perform in an application.
tri
es
• For each user role, you set access to Yes or No.

R
• You can assign roles by user and by group.

-
y
r
ta
• If you provision a group, you do not need to provision the users within the group.
ie
pr
Three special roles are Administrator, Advanced, and Default.

o
Pr
• The Administrator role grants access to all application tasks.

e®
• The Advanced role specifies a user as advanced or basic. Basic users can access
cl
ra
only task lists. They cannot access the Browser View tab. As a result, they can
O
launch only tasks that are included in the task lists to which they are granted access.
Advanced users can access the Browser view and all tasks.
• Within an application, users and groups who are assigned the Default role can
perform default tasks in each module; for example, define application profiles, open
data grids, create reports, manage metadata, load data, and extract member lists.

User Role Categories
se
ur
Extr act Application level
co
ngi
in
tra
er
Load Data access
rtn
pa
e®
cl
ra
O
an
Manage in Reports
e
us
al
on
rs
pe
to
User Role Categories

ed
Fifty user roles address six areas. Refer to the Oracle® Hyperion Financial Management,
ct
tri
Fusion Edition 11.1.2 Administrator’s Guide for explanations of the Financial

es
Management user roles.

R
Within Shared Services and Performance Management Architect, users and groups who
-
y r
are assigned the Global user role can perform tasks: for example, create users and
ta
ie
groups, create and delete projects, assign access to integrations, view an integration,
pr
run EPM Systems Life Cycle Management, create and modify dimensions in
o
Pr
Performance Management Architect, create calculation rules, and create Financial

e®
Management, Planning, Profitability, and Essbase applications from Performance

Management Architect.
cl
ra
O

Assigning User Roles
Select an application
se
and role .
ur
co
ngi
in
tra
er
rtn
Assign
pa
roles.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Assigning User Roles

ed
Shared Services User Management Console provides a centralized location from which
ct
tri
you manage security for your Financial Management applications.

es
R
User Management Console provides a list of users and groups from your authentication
provider. You provision users and groups by assigning them user roles in an application.
-
y
r
If user roles are assigned to a user both individually and through one or more groups, the
ta
ie
user receives both the individual and group role assignments.

opr
Any user who, within an application, is assigned the Provisioning Manager role can
Pr
assign user roles.

e®
cl
ra
To assign user roles:

O
1. Log on to Workspace.
2. Select Navigate, then Administer, and then User Management to display User
Management Console.
3. From User Directories, select Users or Groups to display the Search Criteria page.

4. In one of the search criteria fields, select an option, and then click Search.
5. Select a user or group from the list.
6. Select Administration, and then Provision.
7. From the Available Roles list, select an application and a role, and then click the
right-arrow button.
se
ur
The role is added to the Selected Roles list.
co
8. Repeat step 7 to add other roles.
i ng
in
9. Click Save.
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe the four levels of security in Financial Management
er
• Assign user roles
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 2
Assigning Access to Data and Documents 12
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe application settings for security
pa
• Assign access to security classes
e®
cl
• Configure security auditing
ra
O
• Load and extract security files
• Migrate security an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 12 Assigning Access to Data and Documents
Application Settings and Security
Application settings
UseSecur ityForEntities = Y
se
UseSecur ityForAccounts = Y
ur
UseSecur ityForScenario = Y
co
ngi
in
tra
er
Entity dimension Security classes
rtn
pa
East Sales US
(Member Attribute) Europe
e®
Australia
cl
SecurityClass = US
ra
O
an
in
e
us
Account Scenario ICP Custom1 Custom2 Custom3 Custom4

al
on
rs
[
pe
to
Application Settings and Security

ed
ct
Before setting up security for users and groups, you should ensure that your security-
tri
related application settings are configured correctly.

es
R
The following application settings, which you set in Performance Management Architect,
-
enable dimension security. You set each setting to Yes or No:

y r
ta
ie
• UseSecurityForAccounts
pr
o
• UseSecurityForEntities
Pr
• UseSecurityForScenarios
e®
cl
• UseSecurityForCustom1
ra
O
• UseSecurityForICP

For the example on the slide, the security-related application settings for the Entity,
Account, and Scenario dimensions are set to Yes.
Other security settings:
• EnableMetadataSecurityFiltering—Specifies whether users can view all dimension
members or only dimension members to which they have access.
se
ur
• NodeSecurity—For nodes, specifies one of two types of security access. Select
co
Entity to check node data based on the entity’s access. Select Parent to check node
ng
data based on the parent’s access.
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Data Access
Access to a data cell is determined by the user’s most
se
restrictive member access.
ur
co
ng
i
in
All/All All/None
tra
Read/All R ead/None
er
rtn
pa
User Access
Member
e®
to Member
cl
Sales All
ra
O
Costs Read
Florida an
All
in
e
France None
us
al
on
rs
pe
to
Data Access
ed
You assign users access rights to members indirectly through a security class. For
ct
tri
example, assume that the security class for the Sales and Net Profit members is
es
Revenue Accounts. If you assign a user Read access to the Revenue Accounts security
R
class, the user receives Read access to the Sales and NetProfit members.
-
yr
Data cells represent intersections of dimension members. Users may be assigned

ta
ie
multiple levels of access for the multiple members of a data cell. In this case, to
pr
determine the user’s access to the cell, the most restrictive access right is applied.
o
Pr
For the example on the slide, at the intersection of Costs and Florida, the user has Read
e®
access to the Costs member and All access to the Florida member. Therefore, the user
cl
has Read access to the cell. Similarly, at the intersection of Costs and France, the user
ra
O
has Read access to the Costs member and None access to the France member.
Therefore, the user has no access to the cell.

If metadata filtering is enabled for an application, user access rights also control member
filtering. Users see only the members of the Scenario, Entity, ICP, Account, and custom
dimensions to which they have access. Metadata filtering applies to member selection
lists and to the rows and columns of data grids and data forms.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Document Access
Every document has a security class.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Document Access
ed
Every Financial Management document is assigned a security class. The users’ access
ct
tri
to a document is determined by their access rights to the security class. Document

es
access rights are described in the following table:

R
-
y
Document
r
ta
Access Description
ie
pr
None The document is not included in the list of documents.

o
Pr
Read • Users can open the document. Users can also save a private grid.
e®
Metadata • For data forms and data grids, based on their access rights to the row and
column members, users can modify data.
cl
Promote
ra
• For journals, data is read-only.

O
• Users cannot modify the document. For example, they cannot add rows or
columns to a data grid.
All • Users can open, modify, and save the document. Users must have the
Manage Data Entry Forms role to save data forms.

Security Classes
You associate the security class dimension with the Security
se
Class properties of the dimensions for which security is
ur
co
enabled.
ngi
in
tra
er
rtn
[Default] is a
pa
system -generated
security class.
e®
cl
ra
O
Dimension
association
an
in
e
us
al
on
rs
pe
to
Security Classes
ed
Security classes define user and group access rights to application elements. As
ct
tri
previously discussed, you create security classes in Performance Management Architect

es
by adding a dimension of the security class type.

R
-
After creating a dimension for security classes, you associate the security class
y
r
dimension with the Security Class properties of the dimensions for which security is
ta
ie
enabled.
pr
o
A system-generated security class called [Default] is created as part of an application,

Pr
and has the following properties:

e®
cl
• It cannot be deleted or modified by users.

ra
O
• Access rights can be assigned to the security class [Default].

• Any member without a security class (where security class = <blank>) is treated as if
it has the security class [Default].

Assigning Access to Security Classes

Assigns access for the currently
se
selected cells
ur
Enables email alerts
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Assigning Access to Security Classes

ed
ct
Within applications, after you provision users and groups and create security classes,
tri
you can specify the type of access that each user and group has to each security class.
es
R
You can assign users one of five access types: None, Metadata, Read, Promote, and All.
-
You can use the Pivot Table feature to toggle between two views for the assign access
yr
table. For example, if users and groups are on the rows and security classes are on the
ta
ie
columns and you click Pivot Table, the users and groups move to the columns and the
pr
security classes move to the rows.

o
Pr
When you grant users access to a security class, you can enable e-mail alerts. E-mail
e®
alerts can be used for intercompany reporting and also to inform the users of process
cl
ra
unit status changes for entities and scenarios that use the security class.To receive e-
O
mail alerts, a user must have All or Promote access to the security class.

To select users, groups, and classes:

1. From the Application Groups section in User Management Console, select an
application.
2. Right-click the application, and select Assign Access Control to display the Select
Users and Groups task.
se
3. Select Users or Groups.
ur
co
ng
• In the search criteria box, enter a search criteria and click Search to display a
i
in
tra
specific user or group.
er
• Click Show All to display all users and groups.
rtn
pa
5. In the Available Users and Groups area, select a user or group.
e®
6. Click the right-arrow button to add the user or group to the Selected Users and
cl
Groups area.
ra
O
7. Click Next to display the Select Classes task.
an
in
8. In the Available Classes area, select a class or classes.
e
us
9. Click the right-arrow button to add the classes to the Selected Classes area.
al
on
To assign access to security classes:

rs
pe
1. In the Select Classes task page, click Next to display the Assign Access task, which
to
displays users in rows and security classes in columns.

ed
ct
2. Optional: Click Pivot Table to display the users in columns and security classes in
tri
rows.
es
R
3. Select a cell for a user and class and, in the Assign Rights drop-down list, select an
-
access type.
y r
ta
4. Click Set to assign the user the access type.

ie
opr
5. Optional: Click Add Alert to enable e-mail alerts.

Pr
e®
cl
NOTE: The alerting process uses the e-mail addresses that are stored in
ra
your external authentication provider, such as LDAP or MSAD. To

O
receive e-mail alerts, users must be on either MSAD or LDAP. Cells

with e-mail alerts display a mail icon.

6. Repeat steps 3, 4, and 5 to grant other users access to each security class.
7. Click Save.
Deleting Security Classes

When you no longer need a security class, you can delete it from the security class
se
dimension. However, you cannot delete a security class that is associated with other
ur
dimension’s metadata. For example, if the security class Corporate is assigned to the
co
Security Class property of the NetProfit member of the Account dimension, you cannot
ng
delete Corporate from the security class dimension until you clear the Security Class
i
in
property of the Net Income member.
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Running Security Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Running Security Reports

ed
You can run security reports to review security that you set up for the application.
ct
tri
es
To run security reports:

R
-
1. On the Assign Access task, click Next.

y
r
ta

ie
opr
• Select Rights, and then select Classes by User or Roles by User or both.
Pr
• Select Users by Group.

e®
cl
3. Select a report format and template.

ra
O

• Click Launch Report to view the report.
• Click Export to File to export the report to a CSV file, which can be opened in
Microsoft Excel.

Configuring Security Auditing
Configure auditing at
se
• Global level for all applications
ur
co
• Project level for specified projects
ng
• Application level for specified applications
i
in
tra
Specify activities to audit at global, project, and application
er
levels
rtn
pa
e®
cl
ra
O
Global Project an Application
in
e
us
al
on
rs
pe
to
Configuring Security Auditing

ed
ct
You can configure security auditing to track provisioning and Lifecycle Management
tri
activities at the global, project, and application levels.

es
R
Global-level auditing enables you to audit security and artifacts handled by Shared
-
Services. Project-level and application-level auditing enables you to audit security

y
r
activities related to a specific project or application performed through Shared Services.

ta
ie
opr
Pr
NOTE: Project and application security activities that are performed outside Shared
e®
Services—for example, assigning calculation scripts in Essbase—cannot be

cl
audited. Also, assignment of security classes to artifacts cannot be audited.

ra
O

To configure auditing at the global level:

1. Log on to Shared Services.
2. In the Navigation pane, select Shared Services.
3. Select Administration, and then Configure Auditing to display the Audit Configuration
window.
se
ur
4. Select Enable Auditing.
co
If you do not select this option, Shared Services will not support
ng
auditing at any level.
i
in
tra
5. Select Enable Global Setting Over-ride to override project and application-level auditing.
er
rtn
6. Optional: In the Purge Data Older Than box, enter the number of days for retaining
pa
the audit data, and then click Purge.
e®
Old audit data is removed.
cl
ra
7. Under Select Tasks, select the tasks for which audit data is to be configured.
O
8. Click OK.
an
in
e
To configure auditing at the project and application levels:

us
al

on
rs
2. In the Navigation pane, expand Application Groups and perform one of the following
pe
actions:
to
• Select a project, select Administration, and then select Configure Auditing to configure
ed
auditing for a project.

ct
tri
es
• Expand a project, select an application, select Administration, and then select

R
Configure Auditing to configure auditing for an application.

-
y
3. On the Audit Configuration page, under Select Tasks, select the tasks for which
r
ta
auditing is to be configured.
ie
pr
4. Click OK.
o
Pr
e®
cl
ra
O

Running Auditing Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Running Auditing Reports

ed
You can run and view audit reports to track changes made to the security data over a
ct
tri
period of time.
es
R
-
NOTE: Auditing must be configured before you can generate audit reports.
y
r
ta
ie
opr
To run audit reports:

Pr
e®

cl
ra
2. Select Administration, then Audit Reports, and then Security Reports to display audit
O
information related to the security tasks for which auditing is configured.

3. Select the user and the period for which the report is to be generated.

4. Perform one of the following tasks:

• Click View Report.
• Click Detailed View and then View Report to display the report on the modified
attribute and the new attribute value.
5. Optional: Click Export to export the report to a CSV file, which can be opened in
se
Microsoft Excel.
ur
co
By default, the security report file is named auditsecurityreport.txt.
ing
6. Click Close.
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Loading Security Information from Text Files
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Loading Security Information from Text Files

ed
ct
In addition to using Shared Services to provision users and groups and assign access,
tri
you can use it to load security information from a text file.

es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Security Files
se
!USERS_AND_GROUPS
ur
FINAPPS\AdminGroup
co
FINAPPS\ChrisW
FINAPPS\PatM
ngi
in
!ROLE_ACCESS
tra
Administrator;FINAPPS\trnadmin
er
Load System; FINAPPS\AdminGroup
rtn
Reviewer1; FINAPPS\PatM
pa
!SECURITY_CLASS_ACCESS
e®
System;FINAPPS\AdminGroup;All;Y
System;FINAPPS\ChrisW;Read;Y
cl
ra
Europe;FINAPPS\ChrisW;All;Y
O
an
in
e
us
al
on
rs
pe
to
Security Files
ed
Security files have three sections:

ct
tri
es
• Users and groups

R
• Role access
-
y
r
• Security class access

ta
ie
pr
The USERS_AND_GROUPS section contains a list of users and groups that have
o
access to a Financial Management application.The section includes the Microsoft

Pr
Windows domain name and the user or group name, each name separated by a
e®
backslash, as follows:
cl
ra
O
Domain\Username or Domain\Groupname
The ROLE_ACCESS section contains a list of users and groups that are assigned to
predefined Financial Management roles, as follows:

role;Domain\Group
The SECURITY_CLASS_ACCESS section contains a list of rights, by security class, for

users and groups. By default, the rights for users and groups is None. The default for
e-mail alerts is also None. Therefore, specifying None for a user or group is not
necessary, unless you are changing a user’s or group’s rights from All or Read to None.
se
The section includes the security class, the Microsoft Windows domain name for the user
ur
or group, the user or group name, the access right, and Y or N for the e-mail alert right. A
co
backslash separates the security class from the Microsoft Windows domain name. The
ng
following is an example:
i
in
tra
class;Domain\User;rights;alerts
er
rtn
class;Domain\Group;rights;alerts
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Loading Security Files
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Loading Security Files

ed
Security information load files can be in an ASCII format, supporting multibyte character
ct
tri
sets (MBCS), or in a Unicode format, using little endian byte ordering. The default file
es
name extension for security information load files is SEC.

R
-
When you load a security information file, you can clear application security information
y
r
(before beginning the load). You also can verify that the load file users and groups are
ta
ie
valid Microsoft Windows users and groups. Any user or group that is not verified is not
pr
added to the application, and a warning message is saved in the log file. If you do not
o
Pr
select the validate option, all users and groups are added, whether or not they are valid
e®
Microsoft Windows users and groups. Financial Management attempts to validate users
cl
and groups when they try to access an application.

ra
O

To load security files:

1. In the view pane, select Tasks, then Load Tasks, and then Load Security.
The Load Security page is displayed.
2. Click Browse to locate the file that you want to load.
se
3. Select the file, and click OK.
ur
4. On the Load Security page, select the following:
co
ng
• Delimiter character
i
in
tra
• Load options
er
• Security options
rtn
pa
5. Click Load.
e®
6. Confirm that the security file was loaded successfully.
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Extracting Security
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Extracting Security
ed
You can extract security information to a file. You select a delimiter for the file and the
ct
tri
security elements that you want to include.

es
R
Valid delimiter characters: , ~ @ # $ % & ^ | : ; ? \

-
y
r
ta
To extract security:
ie
pr
1. In the view pane, select Tasks, then Extract Tasks, and then Extract Security.
o
Pr
The Extract Security page is displayed.

e®
2. Select sections that you want to extract, and then click Extract.
cl
ra
3. Confirm that the security sections were extracted successfully.

O

Migrating Security
Use the Application Migration Wizard to migrate security
se
artifacts.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
Define Migration
al
on
rs
pe
to
Migrating Security
ed
ct
You use Application Migration Wizard to export users, groups, roles, delegated lists, and
tri
assigned roles from one operating environment to another environment. Application

es
Migration Wizard migrates security artifacts the same way that it migrates application
R
artifacts. You can export these artifacts to the intermediary file, make updates, and load
-
y
them into the destination environment.

r
ta
ie
pr
To migrate security artifacts:

o
Pr

e®
cl
2. In the view pane, expand Application Groups.

ra
O
3. Expand Foundation.
4. Right-click Shared Services, and select Explore to display the Native Directory.

• Select Native Directory to select all users, groups, roles, delegated lists, and
assigned roles.
• Expand Native Directory, and then select security artifacts.
6. Click Define Migration to display Application Migration Wizard.
7. On the Source page, select the source applications, and click Next to display the
se
Source Options page.
ur
co
8. Specify the following information for the source:
ng
i
• Export file format
in
tra
• User, group, and role
er
rtn
9. Click Next to display the Destination page.
pa
10. Specify a destination by performing one of the following actions:
e®
cl
• Expand File System, enable the text box, and then enter the file name.
ra
O
• Expand Shared Services, and then select the destination application.
11. Click Next to display the Destination Options page.an
in
e
12. Review the destination options, and then click Next to display the Migration Summary
us
page.
al
on
13. Optional: Click Save Definition to save the file for later migration.
rs
pe
14. Click Execute Migration to start the migration.

to
A message confirms that the migration started.

ed
ct

tri
es
• Click OK to exit Application Migration Wizard.

R
-
• Click Launch Migration Status Report to view the status of the migration.
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe application settings for security
er
• Assign access to security classes
rtn
pa
• Configure security auditing
e®
• Load and extract security files
cl
ra
• Migrate security
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 3
Creating Data Forms 13
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe data forms
pa
• Create data forms with Form Builder
e®
cl
• Define points of view and columns and rows
ra
O
• Set column and row options
an
• Export to and import from spreadsheets
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 13 Creating Data Forms
Data Forms Overview
Data forms provide the following types of flexibility:
se
• Add columns or rows for text input
ur
co
• Add blank rows or columns for spacing
ng
• Apply row and column formatting
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Data Forms Overview

ed
Data forms are templates, with predefined row and columns, that users can use to input
ct
tri
and view specified data elements. Users cannot add rows and columns to or remove
es
rows and columns from data forms.

R
-
If you use Financial Data Quality Management (FDM) to load data into an application,
yr
users can drill from data forms to FDM to view the source data. The process of drilling
ta
ie
down is similar to one used in data grids.

pr
o
On data forms, users can change point of view selections only for the dimensions that
Pr
you specify when you set up the form. For example, you can set up the point of view for
e®
a form so that users can select the period but not the scenario and entity for which they
cl
ra
want to enter data.

O
You can define links from one form to another to enable users to drill through to view data
in the linked form.

Data Form Toolbar Buttons

The following table describes the data form toolbar buttons:
Toolbar Button Function

Submit
se
ur
Refresh
co
ng
Calculate
i
in
tra
Force Calculate
er
rtn
pa
Cell Text
e®
cl
Instructions
ra
O
Print
an
in
e
us
Export to Excel
al
on
Import from Excel

rs
pe
Suppress Rows
to
ed
ct
Suppress Columns
tri
es
R
Suppress Lines
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Data Forms–Context Menu
Data forms provide a shortcut context menu with the same
se
options as the data grid context menu.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Data Forms-Context Menu

ed
In data forms, you can right-click a data cell and use the shortcut menu commands. The
ct
tri
commands are similar to the data grid menu commands. The availability of menu
es
commands depends on the cell status and your security rights.

R
-
y
r
ta
NOTE: When you perform consolidation actions in data forms, you must click
ie
Refresh to refresh the data in the form.

pr
o
Pr
e®
cl
ra
O

Creating Data Forms with Form Builder
To define a data form, you use the options on the Form Builder
se
tabs.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Data Forms with Form Builder

ed
ct
Financial Management provides a graphical user interface for creating and maintaining
tri
data forms. You can enter up to 20 characters for the form label and up to 40 characters
es
for the description. In the Instructions text box, you can enter instructions for use on the
R
form. When the user selects the Instruction button, the information is displayed in a
-
y
separate window.
r
ta
ie
pr
To create data forms with Form Builder:

o
Pr
1. In the application, select Administration, and then Manage Documents.

e®
cl
2. Select the Data Forms tab.

ra
O
3. Click New.
Form Builder is displayed with the Properties tab selected.
4. In the Label text box, enter a name.

5. In the Security Class drop-down list, select a security class.

6. In the Description text box, enter a description.
7. In the Instructions text box, enter instructions for using the form.
8. Click Next.
se
ur
co
ing
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Defining the Point of View
Specifies the initial value Specifies a member list
se
for the dimension from which to select
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Defining the Point of View

ed
The Member column specifies, for each dimension, the initial value that is displayed on
ct
tri
the data form. The Selectable column specifies member lists for the dimensions.
es
R
A user can change a point of view by selecting a member from the dimension’s member
-
list. If, for a dimension, the Selectable column is blank, users cannot change the point of
r y
view.
ta
ie
pr
To define the point of view:

o
Pr
1. On the POV tab, in the Member column, select the dimension that you want to
e®
display on the data form.

cl
ra
O
2. In the Selectable column, specify the member list for the dimension.
3. Click Next.

Defining Columns and Rows
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Defining Columns and Rows

ed
You define columns and rows to specify the members to be displayed in the columns
ct
tri
and rows.
es
R
To define columns and rows:

-
yr
ta
• On the Columns and Rows tab, define the column’s and row’s POVs, display
ie
options, formats, and cell text according to the following guidelines:

pr
o
Pr
e®
cl
ra
O

Guidelines for Defining Columns and Rows

Dimension Specification:
You can use a keyword to define dimensions for columns and rows. Use the following
syntax to specify a keyword:
se
Keyword#Member
ur
co
Where Keyword identifies a dimension type, such as S for the dimension type Scenario,
ng
and Member is a member name. You can enter the dimension keyword and the member
i
in
or browse to select from lists. The following example creates a column or row for Budget:
tra
er
S#Budget
rtn
pa
You can specify multiple dimensions for one column or row by separating entries by
periods. The following example creates a column or row for the Budget scenario and the
e®
YTD view:
cl
ra
O
S#Budget.W#YTD
The following table lists the dimension keywords: an

in
e
us
Keyword Description
al
S# Scenario
on
Y# Year
rs
pe
P# Period
to
V# Value
ed
E# Entity
ct
W# View
tri
es
A# Account
R
I# Intercompany Partner
-
y
C1# Custom1
r
ta
C2# Custom2
ie
pr
C3# Custom3
o
Pr
C4# Custom4
e®
Member Lists
cl
ra
You can also use member lists to define columns or rows. A column or row is added to
O
the form for each member in the list. Use the following syntax to specify a member list:
Keyword{Member List}

Where Keyword identifies a dimension and Member List is the name of a member list.
The following example uses the Months member list:
P{Months}
Dynamic Columns and Rows
You can use the @CUR keyword with system-defined member lists to create rows and
se
columns dynamically. The rows and columns are created based on the selected point of
ur
co
view member. The following example uses the [Children] member list with @CUR. If
NetProfit is selected in the point of view, the data form displays rows or columns for
ng
NetProfit and its children. If TotalAssets is selected, the data form displays rows or
i
in
tra
columns for TotalAssets and its children.
er
A{@CUR.[Children]}
rtn
pa
Blank Rows
e®
You can insert blank rows for spacing by entering the keyword Blank, and then pressing
cl
the Tab key.
ra
O
Relative Time Periods
an
in
For rows and columns, you can use the following keywords to select a period relative to
e
the current POV:

us
al
• CUR
on
• FIRST
rs
pe
• LAST
to
• NEXT
ed
ct
• PREV
tri
es
Consider the following example. If the period selected in the POV is January, the column
R
or row that is created displays data for February.

-
y
r
P#CUR+1
ta
ie
pr
Column and Row Calculations—Scalc

o
Pr
You can use the Scalc function to create, in columns or rows, custom formulas that use
e®
standard mathematical operators. The specified calculations are performed in the client’s
cl
Web browser. The following example subtracts column 2 from column 1:

ra
O
Scal(C1 - C2)
You can use the Scalc function to specify more complicated calculations in rows,
columns, or cells. The specified calculations are performed in the application server.

You can also use the following types of items:

• References to dimension members. The following example references the Account
dimension members Purchases and OtherCosts:
R6=SCalc(((A#Purchases)-(A#OtherCosts))*100)
• Cell references, using the syntax Cell(rowIndex,columnIndex). The following
se
example refers to the cell in the fourth row of the second column:
ur
R1=SCalc(Cell(4,2))
co
• Row references, using the syntax Row(rowIndex). The following example divides row
ng
i
4 by row 2:
in
tra
R3=SCalc(Row(4)/Row(2))
er
rtn
pa
NOTE: For rows or columns that contain member lists, the calculation is performed
on the total for the members of the list.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Setting Column and Row Options
You can set options for individual rows and columns.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Column and Row Options

ed
Options that you set for individual rows or columns override the defaults for the form. The
ct
tri
following table describes options available for row and column:

es
R
Option Description
-
y
Override Specify a POV dimension member or formula calculation for one or

r
ta
more consecutive columns. You can also specify a format to override

ie
the formatting.
o pr
Decimal Places Specify the number of decimal places. Valid values are 0 to 9.
Pr
Scale Specify the scale. Valid values are -12 to 12.

e®
cl
Cell Text Specify whether the row or column accepts cell text input. For text input
ra
rows or columns, enter 1.

O
Custom Header Specify the custom header text to be displayed in place of the member
label or description. You can also specify a heading for calculated
columns. In custom headers, you cannot use commas ( , ), colons ( : ), or
ampersands ( & ).

Option Description
Cust Header Style Enter formatting keywords for the row heading or column heading.
Style Enter formatting keywords for the row or column.
No Suppress Turn off suppression for the specified row. Thus, regardless of the
se
suppression options that are set for the form, the row is displayed.
ur
Other Enter a valid data form script to set options that are not provided by
co
Form Builder.
ng
i
in
The following table describes options available only for rows:
tra
er
Option Description
rtn
pa
Add Member For forms that suppress NoData cells, enable users to enter data for
suppressed members. The option adds an icon that users can click to
e®
select members and enter data. You specify the dimension and member
cl
list from which users can select.
ra
The following example adds an icon that enables users to select
O
members from the Markets member list of the Custom1 dimension:
an
in
C1{Markets}
e
Link Specify a URL to another Web data form.

us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

Formatting Columns and Rows
Formatting assigned to rows overrides formatting assigned to
se
columns.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
Initial semicolon
ra
enables com bined row
O
and column for matting.
an
in
e
us
al
on
rs
pe
to
Formatting Columns and Rows

ed
Each style property consists of a property name, a colon, and a value. The value may be
ct
tri
one or more words, separated by spaces; for example:

es
R
color:red; text-align:right
-
The Style option is interpreted by the browser, not by Financial Management, so it is

y
r
ta
limited only by what the browser supports. The Style option uses the standards
ie
supported by the World Wide Web Consortium (W3C). For information about style
o pr
standards, see http://www.w3.org/TR/REC-CSS2.

Pr
e®
By default, formatting assigned to rows overrides formatting assigned to columns. For

cl
example, if column 2 is italic and row 5 is bold, the cell at the intersection of column 2
ra
and row 5 is displayed in bold.

O

You can combine styles at row and column intersections by including, for a row, a
semicolon as the first character in the Style text box or Cust Header Style text box. For
the example on the slide, because the first character in the Style text box for the
TotalRevenues row is a semicolon, the cell at the intersection of TotalRevenues and Year
is displayed in bold italic.
The following table lists some of the properties and potential values that you can use:
se
ur
co
Property Value Example
ng
Color (foreground) Color name or the standard color: red
i
in
Background-color hexadecimal RGB notation. color: rgb(255,0,0)
tra
For a quick reference for colors, go background-color: #ff0000
er
to http://www.cross-
rtn
background-color: yellow
browser.com/docs/color_cha
pa
rts.html.
e®
Font-family Font name. font-family: Arial
cl
Font Font style. You can combine up to
ra
font: italic Courier
O
six font properties, separated by font: Arial Italic extra-
an
spaces, in one Style value. in bold 12pt
Font-weight Font weight. Values include demi- font-weight: extra-bold
e
bold, demi-light, extra-bold, light,

us
extra-light, demi-light.
al
on
Font-size Font point size. font-size: 12pt

rs
font-size: 12pt
pe
Text-align Alignment of the text. Values

to
text-align: center
include left, right, center, and justify.
ed
ct
tri
For a full list, see the Property Index at http://www.w3.org/TR/REC

es
CSS2/propidx.html.
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

Setting Up Text Columns and Rows
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Up Text Columns and Rows

ed
You can set up columns and rows for input of cell text, thereby enabling users to enter
ct
tri
text annotations directly in the data form, instead of in the Cell Text dialog box.
es
R
For the example on the slide, column 4 displays data for the Quarter1 member. The 1 in
-
the Cell Text field of Col 5 Options designates column 5 as a text column. The reference
y
r
to the Quarter1 member, in the column definition for column 5, connects the text entered
ta
ie
in the cells for column 5 to the Quarter1 member.

opr
Pr
e®
cl
ra
O

Setting Column and Row Defaults
Use the Details tab to set default display options for all rows
se
and columns of a form.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Column and Row Defaults

ed
Default settings do not override the settings for individual rows and columns.
ct
tri
es
To set up column and row defaults:

R
-
1. On the Details tab, set the grid, print, and suppression options for columns and rows.
y
r
ta
2. Under Display Options, select one of the following options:

ie
opr
• Select Single Period to view, in the line-item entry window, only the period for the
Pr
selected cell.
e®
• Select CalcbyRow to change the default calculation order (columns first) to rows
cl
ra
first. For some calculations, for correct results, rows may need to be calculated
O
first.

Setting Heading Defaults
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Heading Defaults

ed
You can specify heading defaults for each dimension.

ct
tri
es
To set heading defaults:

R
-
1. On the Headers tab, in the Show drop-down list, select Label or Description to display
y
r
ta
member labels or descriptions for dimension headings.

ie
pr
2. In the Style box, enter style keywords.

o
Pr
3. In the Length box, specify the maximum length for row headings.
e®
4. Optional: Perform one or both of the following actions:

cl
ra
O
• Select Fixed, if you want the maximum and minimum length to be the same.
• In the Other column, enter a valid data form scripts for header options that are not
provided by Form Builder.

Viewing Scripts
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Scripts
ed
On the Script tab, you can view, modify, and print scripts by entering the syntax in the text
ct
tri
box.
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Exporting to and Importing from Spreadsheets
se
ur
co
Export to and im port from spreadsheets
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Exporting to and Importing from Spreadsheets

ed
ct
You can use the toolbar to export data forms from Financial Management to Microsoft
tri
Excel and to import spreadsheets from Excel to Financial Management. For example,
es
you can export a form to Excel, enter or edit data, and then load the modified data into
R
Financial Management.
-
yr
When you export from a data form to Excel, the POV of the data form is exported and
ta
ie
saved in the spreadsheet. When you import from the Excel spreadsheet into the Web
pr
client, data is imported to the saved POV, regardless of the POV settings for the data
o
Pr
form.
e®
You can also access data forms using Smart View.

cl
ra
O

To export data forms:

1. Open the data form to export.
2. On the toolbar, click Export to Excel.
3. From File Download, click Save, enter a file name, and click Save.
se
4. Confirm that the download completed successfully, and click Close.
ur
co
5. Navigate to the saved file and open it.
ng
6. In Excel, enter or edit data.
i
in
tra
7. Select File, then Save or Save As and save the file.
er
rtn
To import a form from Microsoft Excel:
pa
1. Open the data form into which to import data.
e®
cl
2. On the toolbar, click Import from Excel.
ra
O
3. Click Browse to locate the file to import, and click Open.
4. Click OK.
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe data forms
er
• Create data forms with Form Builder
rtn
pa
• Define points of view and columns and rows
e®
• Set row and column options
cl
ra
• Export to and import from spreadsheets
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 4
Creating and Managing Task Lists 14
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe task lists
pa
• Create task lists
e®
cl
• Add items to task lists
ra
O
• Organize and manage task lists
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 14 Creating and Managing Task Lists
Task Lists Overview
se
ur
co
Monthly Close
Task List
ngi
in
tra
Enter Journals
er
rtn
pa
Review
e®
cl
ra
Consolidate
O
an
in
Report
e
us
al
on
rs
pe
to
Task Lists Overview

ed
ct
A task list contains items and tasks that you use frequently; for example, data forms, data
tri
grids, and reports. By setting up task lists, you can complete your workflow without
es
navigating among forms, grids, and report modules, and you can view and manage items
R
and tasks from Project View or Browser View.

-
yr
For the example on the slide, the Monthly Close task list consists of the following tasks:
ta
ie
enter journals, review, consolidate, report.

pr
o
In Browser View, task lists are listed in the top pane, and items contained in the selected
Pr
task list are listed in the bottom pane. In Project View, task lists are displayed in a drop-
e®
down list that identifies the task list items.

cl
ra
O

Creating Task Lists
You can create task lists on the Tasklists tab of the Manage
se
Documents page.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Task Lists

ed
ct
You can create private or public task lists. Private task lists can be accessed only by the
tri
users who create them. To limit access to a list, you can assign a security class to the list.
es
For example, you can assign the Admin security class to a task list that you want to limit
R
to administrators.
-
y
r
ta
ie
To create task lists:

opr
1. Open the application, select Administration, and then select Manage Documents.
Pr
e®
The Manage Documents page is displayed.

cl
2. Select the Tasklists tab.

ra
O
3. Click New Tasklist.

The Manage Tasklist page is displayed.
4. Add items to the task list. See “Adding Items to Task Lists” on page 4.

Adding Items to Task Lists
Add Add item to a task list.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Adding Items to Task Lists

ed
You can add the following items to task lists:

ct
tri
es
• Tasks
R
• Data forms
-
y
• Data grids
r
ta
• Intercompany reports
ie
pr
• Journal reports
o
Pr
• Links to Web sites or files

e®
• Related content (documents in Financial Reporting or Web Analysis)

cl
• Folders
ra
O
• Other task lists

• Custom documents
You can include multiple instances of an item or object in task lists.
You can also access task lists through Excel and Outlook.

To add items to task lists:

1. In the Add drop-down list, select an item.
The list of the selected item is displayed.
2. Select the specific item that you want to add to the task list, and click Add to Task List.
se
ur
The selected item is added to the task list.
co
3. Repeat steps 1 and 2 to add other items to the task list.
ng
i
in
4. Click Save.
tra
5. Enter the name and description of the task list.
er
rtn
6. From the Security Class drop-down, select the security class.
pa
7. Click OK.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Organizing Task List Items
se
ur
Folder
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
Journals task list is
nested inside the
MonthlyClose task list. an
in
e
us
al
on
rs
pe
to
Organizing Task List Items

ed
To organize the documents of a task list, you can incorporate folders or subfolders. Users
ct
tri
can then expand folders and select one or more documents.

es
R
If your workflow involves many tasks, you can nest tasks. Nesting task lists makes
-
navigation easier for end users. For the example on the slide, the Journals task list is
y
r
nested inside the MonthlyClose task list.

ta
ie
pr
If you want to include a report to a task list, you can create a related content document to
o
include Web Analysis reports, Financial Reporting reports, and Planning forms.
Pr
e®
You can also add Web page or file links to task lists.
cl
ra
O
Creating Folders in Task Lists

Folders simplify task list maintenance. Documents are available to task list users without
the need for an administrator to edit the task list.

To create folders in task lists:

3. Click New Folder.
se
ur
4. In the Name box, enter the name of the folder.
co
ng
5. In the Description box, enter a description.
i
in
6. In the Content Type drop-down list, select Tasklists.
tra
er
7. In the Security Class drop-down list, select a security class.
rtn
pa
8. Click OK.
e®
cl
Nesting Task Lists
ra
O
You can nest task lists within a task list.
an
in
To nest task lists within a task list:
e
us

al
on

rs
pe
3. Select a task list in which you want to nest another task list, and click Edit to display
the Manage Tasklist page.
to
ed
4. In the Add drop-down list, select Tasklist to display the Tasklist page.
ct
tri
5. Select the task list that you want to nest, and click Add to Tasklist.
es
R
The task list is added.

-
y
6. Click Save.
r
ta
ie
7. Click OK.
opr
Pr
e®
cl
ra
O

Adding Related Content
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Adding Related Content

ed
In Financial Management, when you create a related content document, the document
ct
tri
serves as a link to a resource in another product. For example, you can add a report from
es
Financial Reporting to a task list or you can launch the report from the Related Content
R
menu in the view pane.

-
r y
ta
To add related content:

ie
pr
1. Select File, then New, and then Related Content.

o
Pr
2. In the Resource Server drop-down list, select the resource server for the product for
e®
which you want to add related content.

cl
ra
3. Select the document that you want to make available as related content.
O
4. Click Save.

5. Enter a name and description for the document.

The name and description are displayed in the document list of
the Related Content tab.
6. Click Close.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Adding Links
se
ur
co
ng
Click View
i
in
to test the
tra
link.
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Adding Links
ed
Before you can add a link to a task list, you must create the link.
ct
tri
es
• When you create a link, you can specify whether it should be displayed in the task list
R
pane or in a separate window.

-
y
• For links to Web pages that are time-consuming to open, you may want to specify
r
ta
that the system prompt the user before opening the Web page.
ie
pr
• You can launch links from the Links menu in the view pane.
o
Pr
e®
To add links:
cl
ra
1. Open the application, and select File, then New, and then Link to display the New Link
O
page.
2. In the Link box, enter the name of the link.

3. Optional: Click View, to test the link.

4. Specify how you want the link to open and display.
5. Click Save.
6. Enter the name and description of the link, and select a security class.
se
7. Click OK.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Managing Task Lists
se
Remove item for tasklist.
ur
Add item to
co
tasklist.
ng
i
in
tra
er
rtn
pa
Reor der the
tasklist item s.
e®
cl
ra
O
Displays the task list
each time a basic an
in
user logs on.
e
us
al
on
rs
pe
to
Managing Task Lists

ed
ct
You can add, reorder, and remove items from a task list and also set the current task list
tri
as the default task list.

es
R
To manage task lists:

-
y
r
ta
1. Select Administration, then Documents.

ie
pr

o
Pr
A list of tasklists is displayed.

e®
cl
3. Select a tasklist.
ra
O
The Manage Tasklist page is displayed.

4. Perform any of the following actions:
• Add items to the task list: On the toolbar, click Add.

• Remove task list items: Select the item and on the toolbar, click Remove.
• Reorder the task list items: On the Manage Tasklist page, select an item click the
up-arrow and down-arrow buttons.
• Set the current task list as the default task list: On the Manage Tasklist page, select
the check box named This is my default tasklist to select the task list that is displayed
se
when a basic user logs on to the application.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe task lists
er
• Create task lists
rtn
pa
• Add items to task lists
e®
• Organize and manage task lists
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 5
Entering Intercompany Data 15
se
ur
co
i ng
Objectives
in
tra
er
rtn
• Describe how intercompany data is eliminated in Financial
pa
Management
e®
• Set up entities and accounts for intercompany transactions
cl
ra
• Create and run intercompany matching reports
O
an
• Format intercompany reports with Oracle BI Publisher
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 15 Entering Intercompany Data
Intercompany Transactions Overview
se
ur
East Sales Sale Customer
co
1
ng
3
i
in
tra
er
rtn
West Factory
pa
e®
cl
Intercom pany
ra
O
invoice
(transaction) 2 Goods shipped from
an separate organization
in
e
us
al
on
rs
pe
to
Intercompany Transactions Overview

ed
ct
Transactions between two entities in an organization are called intercompany

tri
transactions.
es
R
The example on the slide illustrates the intercompany transaction process:

-
y
1. The East Sales organization makes a sale to an outside customer.

r
ta
ie
2. The goods are shipped from an internal factory, (West Factory).

pr
o
Pr
3. West Factory sends an intercompany invoice to East Sales for the goods that West
Factory shipped.
e®
cl
Entities that conduct intercompany transactions are known as intercompany partners

ra
(ICPs).
O

Intercompany Account Balances
Intercompany balances are not relevant for external financial
se
reporting. According to accounting rules, intercompany account
ur
co
balances are eliminated prior to external financial statement
ng
generation.
i
in
USA
tra
2
er
rtn
pa
California Connecticut 1
e®
cl
ra
O
Plant1 2 West Sales an
Administration
1
Marketing
2
in
East East
East Sales 1
e
us
al
on
rs
pe
to
Intercompany Account Balances

ed
ct
Intercompany transactions produce intercompany account balances.

tri
es
To avoid overstatement, intercompany account balances must be eliminated before

R
external financial statements are generated. Balances are eliminated at the first common
-
parent of the intercompany partners.

r y
ta
During data consolidation, Financial Management automatically eliminates intercompany

ie
pr
balances.
o
Pr
For the example on the slide, intercompany balances in Administration East or East
e®
Sales are eliminated at the Connecticut entity. Intercompany balances between Plant1
cl
and Marketing East are eliminated at the USA entity.

ra
O

Elimination Process
se
ur
USA
co
RentalR evenue: 0
ng
RentalExpense: 0
i
in
tra
California Connecticut
er
RentalRevenue: 1500 RentalRevenue: 0
rtn
RentalExpense: 0 RentalExpense: 1500
pa
e®
Plant1 Sales West Administration Marketing
cl
East East
ra
R entalRevenue: 1500
East Sales
O
R entalExpense: 0
RentalRevenue: 0
an RentalExpense: 1500
in
e
us
al
on
rs
pe
to
Elimination Process
ed
ct
Elimination of intercompany balances occurs during data consolidation. During the

tri
elimination process, differences between intercompany account balances are posted to

es
a plug account.
R
-
For the example on the slide, East Sales leased equipment worth USD $1,500 from
yr
Plant1. When data is consolidated, the intercompany account balances for the
ta
ie
RentalExpense and RentalRevenue intercompany accounts are eliminated at the first

pr
common parent, the USA entity.

o
Pr
e®
cl
ra
O

Plug Accounts
se
ur
Intercom pany Accounts Non-In tercompany Account
co
Sales - Intercompany Purchases - Intercompany IntercoDiffPL
ng
500 600 -100
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Plug Accounts
ed
Because balances for intercompany partners may not agree, you need accounts that,
ct
tri
upon consolidation, record the differences between pairs of intercompany account

es
balances. In Financial Management, these storage accounts are called plug accounts.
R
-
y
r
ta
NOTE: You use plug accounts to track eliminations. If you do not use a plug account
ie
you can still track intercompany data but the data will not be eliminated
pr
during consolidation.
o
Pr
e®
cl
The example on the slide shows a USD $500 Sales intercompany balance against a
ra
USD $600 Purchases intercompany balance. When consolidation is performed, the USD
O
$100 difference is placed in the intercompany difference plug account (IntercoDiffPL).

Intercompany Eliminations
and the Value Dimension
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Intercompany Eliminations and the Value Dimension

ed
Intercompany eliminations are stored in the Value dimension. Because Value dimension
ct
members are displayed in data grids and reports, you can easily audit intercompany
tri
es
eliminations.
R
For the Entity Currency members that are associated with intercompany balance
-
y
accounts, reversing entries are created in Elimination members. The reversals result in
r
ta
the following:
ie
pr
• Zero balances being consolidated to the first common parent of the Entity Currency
o
Pr
member that is associated with the parent account.

e®
• The differences between the eliminated balance are posted to the Entity Currency
cl
ra
member of the plug account.

O

For the example on the slide, California.1000 and California.Plant1 have intercompany
account balances in the SalesInterco and PurchasesInterco accounts. The Elimination
member provides reversing entries for the account balances. Therefore, the Entity
Currency members for the SalesInterco and PurchasesInterco accounts for the parent
California have zero balances. The balances eliminated from SalesInterco and
se
PurchasesInterco are posted to the IntercoDiffPL plug account. California displays a
ur
balance of -100 for IntercoDiffPL, which is the difference between the eliminations
co
posted from the intercompany accounts.
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Setting Up Entities for Intercompany Data
se
ur
co
ng
Specifies whether
i
in
the entity is
tra
displayed as a
er
member in the ICP
rtn
dimension
pa
e®
cl
ra
Specifies a security
O
class for the entity
for the ICP
an
in
dimension
e
us
al
on
rs
pe
to
Setting Up Entities for Intercompany Data

ed
You must set the Is ICP property for all entities that act as intercompany partners and
ct
tri
have intercompany data.

es
R
The SecurityAsPartner property assigns the security class to be used for an entity when
-
the entity acts as an intercompany partner in the ICP dimension. For example, you may
y
r
want users in Europe to be able to enter intercompany transactions between European

ta
ie
entities and United States entities, but not be able to modify data for United States
pr
entities. To achieve this objective, you make the following security assignments:
o
Pr
• For United States entities, you assign USA for the Security Class property and
e®
Intercompany for the SecurityAsPartner property.

cl
ra
• You give users in Europe read-only access to the USA security class and read/write
O
access to the Intercompany security class. Thus, you enable users in Europe to enter
data for United States entities only when the entities are selected in the ICP
dimension.
For instructions on setting member properties, see Lesson 3, “Managing Dimensions.”

Setting Up Accounts for Intercompany Data
The following properties need to be set for intercompany
se
accounts:
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
Is ICP
O
an
in
Plug account
e
us
al
on
rs
pe
to
Setting Up Accounts for Intercompany Data

ed
ct
To use accounts in intercompany transaction processing, you must set two member
tri
properties:
es
R
• Is ICP—To flag the account as an intercompany account

-
y
• Plug Account—To store differences between intercompany balances

r
ta
ie
For instructions on configuring accounts, see Lesson 8, “Configuring Accounts and

pr
Custom Dimensions.”
o
Pr
e®
cl
ra
O

Creating Intercompany Matching Reports
se
ur
co
ing
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Intercompany Matching Reports

ed
ct
Intercompany matching reports help you track intercompany transactions for analysis
tri
and auditing purposes. After consolidating data, you can run intercompany matching
es
reports, which provide details on intercompany account balances that were eliminated.
R
-
When creating intercompany reports, you can select intercompany entities and their
y
r
partners, as well as intercompany accounts.

ta
ie
pr
• Entity and Partner are the entities for which you want to match intercompany
o
transactions.
Pr
e®
• Accounts and Matching Accounts are the intercompany accounts for which you want
cl
to match transactions.
ra
O
• If you select a plug account, all accounts for which the selected account is the plug
account are included in the report.
You can also select one or more of the following report options:

• Suppress Matches: Suppress transactions for which the entity and partner amounts
are less than the amount set in Matching Tolerance.
• Matching Tolerance: To see only out-of-balance transactions that exceed the value
that you specify, enter a value or use the default value of 0.
se
• Matching Tolerance (%): To see only out-of-balance transactions that exceed the
ur
percentage that you specify. Enter a percent of the total or use the default value of 0.
co
The smaller total of the entity or partner is used.
i ng
• Suppress Reversed: For each entity transaction, suppress reversed transactions
in
tra
from partners.
er
• Suppress Details: Suppress intercompany detail and print only the total difference for
rtn
each entity-partner section.
pa
e®
• Suppress Customs: Suppress custom dimensions.
cl
• Scale Factor: Select a scale factor or use the default value of 0. For example, if you
ra
O
enter a scale factor of 3, the report amount is displayed in thousands. If the scale
an
factor is 0, the report amount is displayed in units.
in
• Decimal Override: Select a decimal setting, to override the setting defined in the
e
us
account, or use the default value.

al
• Member Display: Display the member label, member description, or both.

on
rs
• Plug Account Display: Display a summary of plug accounts that are affected by the
pe
intercompany transaction.
to
ed
ct
To create intercompany matching reports:

tri
es
1. Open the application, and select Administration, then Management Documents.

R
The Manage Document page is displayed.

-
y
r
ta
2. Select the Reporting tab.

ie
pr
3. In the Report Type drop-down list, select Intercompany.

o
Pr
4. In the File Type drop-down list, specify a file type.

e®
5. Click New Report to display the New Intercompany Report page.

cl
ra
O
6. Select intercompany entities and their partners, report options, as well as

intercompany accounts.
7. Click Preview.


• Click Save Remote to save the report on the server.
• Click Save Local to save the file on the computer.
9. Click Close.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Running Intercompany Matching Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Running Intercompany Matching Reports

ed
ct
You can access the list of saved intercompany matching reports on the Manage
tri
Documents page. When you run a report, you can override the default report settings.
es
For example, you can select a different partner entity. For reports, the date, time, and
R
user are displayed as header information.

-
y
r
ta
ie
To run intercompany matching reports:

pr
o
1. Open the application, select Administration, and then Manage Documents.

Pr
e®
The Manage Documents page is displayed.

cl
2. Select the Reporting tab.

ra
O
A list of intercompany reports is displayed.

3. Select a report, and click Print.

The “Report output format options” page is displayed.
4. In the Select Report Format drop-down list, select a format.
se
NOTE: You can select PDF, RTF, HTML, or XLS format.
ur
co
ng
5. In the Select Template drop-down list, select a report template.
i
in
6. Click OK.
tra
er
The Report Override page is displayed.
rtn
7. Optional: Select any value to override the default report settings.
pa
e®
8. Click OK.
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

Formatting Intercompany Reports

with Oracle BI Publisher
Format the default template and select the saved template
se
when printing reports.
ur
co
ngi
in
Save the formatted
tra
template.
er
rtn
pa
e®
cl
ra
Select the template when
O
printing the r eport.
an
in
e
us
al
on
rs
pe
to
Formatting Intercompany Reports with Oracle BI Publisher

ed
ct
Oracle BI Publisher (BI Publisher) is a reporting solution from Oracle that enables you to
tri
create and format reports.

es
R
You can use BI Publisher report templates to format intercompany reports. The
-
templates offer report print options, including PDF, RTF, HTML, or XLS. Additionally, you
y
r
can modify these templates in Microsoft Word.

ta
ie
opr
To format intercompany reports with BI Publisher:

Pr
e®
1. Open Microsoft Word.

cl
2. Navigate to your Server Working folder\Report Style Sheet\Templates\Intercompany in your

ra
O
Financial Management directory, and open the intercompany report template.

3. Make format changes to the template.

4. Navigate to your Server Working folder\Report Style Sheets\Sample XML\Intercompany in

your Financial Management directory, and open the ICP.XML file.
5. Preview your changes.
NOTE: You can preview your changes in PDF, RTF, HTML, or XLS.
se
ur
co
6. In the template directory, save the modified template with a new name.
ng
i
in
tra
NOTE: If you have more than one Financial Management server, you must
er
save the modified template in the template directory of each server.
rtn
pa
e®
7. In the application, select a report format, select the modified template, and click OK.
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe how intercompany data is eliminated in Financial Management
er
• Set up entities and accounts for intercompany transactions
rtn
pa
• Create and run intercompany matching reports
e®
• Format intercompany reports with Oracle BI Publisher
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 6
Adjusting Data with Journals 16
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe the purpose of journals
pa
• Open periods for journal entry
e®
cl
• Create journal templates and journals
ra
O
• Submit, review, and post journals
• View adjusted data an
in
e
• Create and format journal reports

us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 16 Adjusting Data with Journals
Journals Overview
se
ur
co
Adjusted
Account Journal
ng
Account
B alance Adjustm ents
B alance
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Journals Overview
ed
ct
Financial Management journals provide an audit trail of changes made in an application.

tri
Journals tell you which users made adjustments and which accounts, entities, and time
es
periods are affected. All adjustments through journals must be reviewed and approved
R
before you can post them.

-
y
r
With journals, you can:

ta
ie
pr
• Create double-sided journal entries by using debits and credits.

o
Pr
• Balance entries, or you can permit single-sided, out-of-balance entries.

e®
• Create recurring journals that are repeated for a number of future periods.
cl
ra
• Create auto-reversing journals that generate reversing entries in the next time
O
period.
• Use the journal approval process to provide accountability.
After creating a journal, you submit it to your supervisor for approval before posting it to
the Financial Management database.

Viewing Automated Consolidation Journals
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Automated Consolidation Journals

ed
You can view automated consolidation transactions as automated consolidation journals.

ct
tri
You can extract the journals to external files, and print them through journal reports. This
es
option is available only on the Web.

R
-
Automated Consolidated Journals are automatically created during consolidation and

y
r
facilitate reporting on the consolidation process. Automated consolidation journals

ta
ie
generated from the consolidation process are displayed in the [Elimination] or

pr
[Proportion] Value dimension and provide a user friendly way to report the amount in the
o
Pr
child entity that is rolled up into the parent entity during consolidation.
e®
To generate automated consolidation journals, you must specify the Nature value in the
cl
rule file for the consolidation process. For more information, see the Oracle® Hyperion
ra
O
Financial Management, Fusion Edition 11.1.2 Administrator's Guide.

NOTE: You cannot edit, scan, submit, approve, reject, post, unpost, or delete the
automated consolidation journals. You can only open and view journals, run
reports, and extract journals.
se
ur
To view automated consolidation journals:
co
1. On the Process Journals page, perform the following actions:
ng
i
in
• Select the Scenario, Year, and Period POVs for the consolidation data that you
tra
want to view.
er
rtn
• For the Value member, select [Proportion] or [Elimination], and then click OK.
pa
A list of journals generated during the consolidation process is
e®
displayed.
cl
ra
2. Click on a journal to view the transactions.
O
an
in
NOTE: You can view transactions based on your security rights to the members in
e
the POV and to the journal security class. You must also have the Read
us
Journals or Journal Administrator security role.

al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Journals and the Value Dimension
se
ur
co
<Entity Currency> 500 Value entered in data form
ng
<Entity Currency Adjs> -75 Value posted from journal
i
in
< Entity Currency Total> 425 Adjusted value rolled up to parent
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Journals and the Value Dimension

ed
The Value dimension plays an important role in journal processing. When you load data
ct
tri
from a file or use a data form or grid to enter data, the values are stored in the Entity
es
Currency member of the Value dimension. When you post adjustments from a journal,
R
the adjustment values are stored in the specified adjustment member.

-
yr
Financial Management stores the posted adjusted data by combining the values in the
ta
ie
Entity Currency and Entity Currency Adjs members and storing the result in the Entity
pr
Currency Total member. The posted adjusted value is used during the consolidation
o
Pr
process.
e®
cl
ra
O

Multiple Journal Postings
Postings from multiple journals are cumulative.
se
ur
co
ngi
in
Journal A:
tra
<Entity Currency> 500 -100
er
<Entity C urrency Adjs> -75
rtn
<Entity Currency Total> 425 Journal B:
pa
+25
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Multiple Journal Postings

ed
If more than one journal is posted to the Entity Currency Adjs member for the same
ct
tri
account, the results are cumulative. The total from the current journal is added to or
es
subtracted from the existing total in Entity Currency Adjs.

R
-
For the example on the slide, Journal A posts -100 to Entity Currency Adjs, and Journal
yr
B posts 25 to Entity Currency Adjs. The total in Entity Currency Adjs is -75.
ta
ie
pr
o
Pr
e®
cl
ra
O

Creating Parent and Contribution Adjustments
se
ur
You can make a parent adjustment to
co
You can adjust the WestSales that affects only SalesServices or
ng
amount after percent only California.
ownership is applied.
i
in
tra
er
You can adjust the
amount before percent
rtn
ownership is applied.
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Parent and Contribution Adjustments

ed
If entities roll up to more than one parent, you can create parent adjustments. Parent
ct
tri
adjustments enable you to apply an adjustment for a child to a selected parent, rather
es
than to all parents.

R
-
For the example on the slide, if WestSales is a child of both SalesServices and
y
r
California, parent adjustments made to WestSales will affect only SalesServices or

ta
ie
California.
opr
Pr
To create parent and contribution adjustments:

e®
1. Open a journal.
cl
ra
2. In the journal point of view, select the Parent Adjs member.

O

NOTE: Parent adjustments are available only for parent entities for which
the AllowAdjFromChildren application setting is selected (On).
3. Select the Contribution Adjs member, and adjust the value that is contributed to the
se
parent after percent ownership is applied.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Opening Periods for Journal Entries
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Opening Periods for Journal Entries

ed
ct
For each scenario, you must open time periods before you can post journal entries to
tri
them. By default, all periods in Financial Management have an initial status of

es
Unopened. You can open and close periods at any time, but you cannot change an
R
opened period to unopened.

-
y
r
ta
ie
NOTE: You must have the Administrator or Journals Administrator security role to
opr
manage periods.
Pr
e®
cl
ra
O

To open periods:
1. In the view pane, select Tasks, then Journal Tasks, and then Manage Periods to display
the Manage Periods page.
2. Select a scenario and year of the periods that you want to open.
3. In the Period area, select the periods that you want to open.
se
ur
4. Click Open.
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Journal Creation Process
1. Create Journal Templates
se
2. Set the Point of View
ur
co
3. Create Journals
ng
4. Enter Journal Data
i
in
tra
5. Review, Submit, and Post Journals
er
6. View Journal Adjustments
rtn
pa
7. Create and Format Journal Reports
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Journal Creation Process

ed
In Financial Management, you use the Process Journals task to create journals and to
ct
tri
enter information into the journals. You enter journal information by using journal
es
templates or by creating blank journals.

R
-
You can create journal groups to help classify journals by type:

y
r
ta
• Reclasses
ie
pr
• Entry corrections
o
Pr
• Reversals
e®
cl
• Accruals
ra
O
• Minority interest accounting entries

• Elimination of adjusting entries
• Allocations

• Overhead
NOTE: You must have the Administrator or Journals Administrator security role to
create journal groups.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Journal Templates

Journal tem plate Entity (F or single-entity journals)
se
ur
POV WestSales
co
ngi
in
tra
Description Reclass balances
er
Set up in advance
rtn
Interest Expense
pa
Accounts
e®
C1..C4
cl
ra
O
Amounts Debit Credit
an
in
e
us
al
on
rs
pe
to
Creating Journal Templates

ed
ct
You can create a journal template to post adjustments that have common information,
tri
such as entities or accounts. Then, you use this template to create journals with similar
es
information.
R
-
You can create two types of journal templates:

y
r
ta
• Standard templates contain accounts and entities for adjustments that you enter
ie
pr
frequently.
o
Pr
• Recurring templates contain complete information for identical journal entities that
e®
occur for more than one period.

cl
ra
Journal templates are independent of scenario and year. You select a scenario and a
O
year when you create a journal based on a template. However, you must select a Value
dimension member for recurring templates.

To create journal templates:

1. Open an application and in the view pane, select Tasks, then Journal Tasks, and then
Manage Journal Templates.
2. Click New.
se
3. Optional: Clear Use Single Entity to create multiple entities template.
ur
co
4. In the Label box, enter a template label.
ng
5. Optional: In the Group drop-down list, select a group to assign to the journal.
i
in
tra
er
NOTE: The journal group that you assign must exist in the application.
rtn
pa
e®
6. In the Balance Type drop-down list, select a balance type to specify the status of the
cl
ra
journal before you post it. The following table describes the balance options:
O
Type Description an
in
Balanced Total journal debits and credits must balance.
e
us
Unbalanced Total journal debits and credits do not have to balance.

al
on
Balanced by Entity Total debits and credits for each entity must balance.
rs
pe
7. Optional: In the Security drop-down list, select a security class.

to
ed
8. In the Description box, enter a description for the template.

ct
tri
9. For each dimension, enter a member.

es
R
-
NOTE: If you clear the Use Single Entity option, you must select an entity.
ry
ta
ie
pr
10. Click Save.

o
Pr
e®
cl
ra
O

Use this button Set the point of view
se
to create a
before you create a
ur
journal. journal.
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
Lists journals for the an
in
current point of view.
e
us
al
on
rs
pe
to

ed
ct
Before creating journals, you must set the point of view based on your requirements. The
tri
point of view determines the members that are displayed for the Scenario, Year, Period,
es
and Value dimensions.

R
-
y
r
ta
NOTE: To create journals for parent adjustments, select the Parent Adjs member for
ie
the Value dimension.

pr
o
Pr
e®
cl
To set the point of view:

ra
O
1. In the view pane, select Tasks, then Journal Tasks, and then Process Journals.
2. In the Point of View, select members.
3. Click New to display the New Journal page.

Creating Journals
se
ur
co
ngi
in
tra
er
rtn
pa
Blank Journal Journal Template
e®
D escription Description Reclass Balance
cl
ra
O
Accounts Accounts Interest Expense
an
in C1..C4
Amounts Amounts Debit Credit

e
us
al
on
rs
pe
to
Creating Journals
ed
ct
You can start with a blank journal or you can create the journal from a template.
tri
es
R
To create journals:
-
1. Under New, perform one of the following actions:

y
r
ta
ie
• Select Start with a blank Journal.

opr
• Optional: Select Create as Single Entity Journal to add Entity to the journal POV bar,
Pr
so that you can select a single entity for the journal.

e®
cl
ra
O
NOTE: If you clear Create as Single Entity Journal, you must select entities
in the journal rows.

• Select Create from Template.

2. Under Type, perform one of the following actions:
• Select Regular to create a regular journal entry.
• Select Auto-reversing to create an auto-reversing journal entry.
se
3. Click OK to display the Edit Journal page.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Entering Journal Data

Select a balance type.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
Select members for each row.

al
on
rs
pe
to
Entering Journal Data

ed
ct
After creating a journal, you enter the journal data on the Edit Journal page.
tri
es
R
To enter journal data:

-
1. Optional: For single-entity journals, select the entity on the POV bar.
y
r
ta
ie
2. Enter a label and description.

opr
3. Select the balance type.

Pr
e®
4. Optional: Assign a security class.

cl
ra
5. Click Pick Members to select an account and a member for the other dimensions of
O
each row.

NOTE: For multiple-entity journals, select the entity for each row.
6. Enter the amount for the journal.

7. Optional: Click Scan to verify that all entries are valid.
se
ur
If the journal contains errors, a separate window displays the scan
co
results by row number.
ng
i
8. Click Save, and then Close.
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Submitting, Reviewing, Approving, and

Posting Journals
se
ur
co
ng
Status: Submitted
i
in
Accountant or Accounting Manager /
tra
Financial Analyst Supervisor
er
rtn
pa
e®
cl
ra
O
Status: OR
Status:
an
Journal Status:
Approved Rejected
Posted
in
If Approved, user can post
e
us
journal
al
on
rs
pe
to
Submitting, Reviewing, Approving, and Posting Journals

ed
ct
After creating journals and entering journal data, you must submit them to your
tri
supervisor for approval before you can post it to the Financial Management database.
es
R
1. Users review and submit journals one at a time or in batches.

-
y
2. The status of the journal changes from Working to Submitted.

r
ta
ie
3. A reviewer (a user with the Journal Approver security role) approves or rejects the
pr
journal.
o
Pr
4. If the journal is approved, the user can post it.

e®
cl
Guidelines:
ra
O
• If you have the Post Journals security role, and the period is opened, you can post a
journal with a Submitted, Working, or Rejected status.

• You can unpost a posted journal. Reversing journal entries are created in the
database, and the status of the journal changes to Rejected.
• At any time, you can process journals by selecting them from the list of journals on
the Process Journals page. You can also use this method to process multiple
journals at the same time.
se
ur
To submit, review, approve, and post journals:
co
1. In the view pane, select Tasks, then Journal Tasks, and then Process Journals.
ng
i
in
The Process Journals page is displayed.
tra
2. Select the journal that you want to process.
er
rtn
3. In the toolbar, based on your security, perform one of the following actions:
pa
• Click Submit to submit the journal.
e®
cl
• Click Review to review the journal.
ra
O
• Click Approve to approve the journal.
• Click Post to post the journal.
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

Viewing Journal Adjustments
You can view journal adjustments in a data grid or in the Entity
se
Details report.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Journal Adjustments

ed
ct
After reviewing and posting the journal adjustments, you can view them in a data grid or
tri
in the Entity Details report.

es
R
-
yr
ta
ie
o pr
Pr
e®
cl
ra
O

Viewing Adjusted Data in Data Grids
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Adjusted Data in Data Grids

ed
You can use a data grid to view the adjustments made to the accounts for an entity. You
ct
tri
can change the Value dimension in the grid POV to view the values in the Entity
es
Currency Adjs, Entity Currency, and Entity Currency Total members.

R
-
When you select the Entity Currency Adjs member, accounts that have posted
y
r
adjustments from several journals display cumulative values.

ta
ie
pr
To view adjusted data in data grids:

o
Pr
1. In the view pane, select Documents, and then Data Grids.

e®
cl
2. Select the data grid.

ra
O
3. Right-click a cell, and select Cell Adjustments.

Viewing Adjustments in the Entity Details

Report
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
Journal Adjustments
us
al
on
rs
pe
to
Viewing Adjustments in the Entity Details Report

ed
You can use the Entity Details report to view details of the entire consolidation path for a
ct
tri
specific cell, including the journal entries that were generated in the journal posting
es
process.
R
-
y
To view adjustments in the Entity Details report:

r
ta
ie
1. In the data grid, select a valid intersection.

opr
Pr
2. Right-click the valid intersection cell, and select Entity Details.

e®
cl
ra
NOTE: In an entity report for a Parent entity, the data shows only the totals
O
from its children.

Creating and Formatting Journal Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating and Formatting Journal Reports

ed
ct
You can create and format journal reports to check the status of journals and to review
tri
journal adjustments. You can also set journal report properties, select columns and
es
filters, preview the reports, save journal reports remotely and locally, and run journal
R
reports.
-
y
r
ta
ie
To create journal reports:

pr
o
1. In the view pane, select Tasks, then Journal Tasks, and then Process Journals to display
Pr
the Process Journals page.

e®
cl
2. Click Reports to display the Journal Report Properties page.

ra
O
After creating a journal report, you can use Oracle BI Publisher to format the report. The
procedure is similar to the one you use to format intercompany reports with Oracle BI
Publisher.

• Navigate to your
“Middleware\EPMSystem11R1\products\FinancialManagement\Server Working
Folder\Report Style Sheet\Templates\Journal” to access the journal template report.
• Navigate to your
“Middleware\EPMSystem11R1\products\FinancialManagement\Server Working
Folder\Report Style Sheets\Sample XML\Journal” to access the sample XML data
se
file.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Setting Journal Report Properties
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Journal Report Properties

ed
You can set properties for a journal report on the Journal Report Properties page.
ct
tri
es
To set journal report properties:

R
-
1. From the Select Report Format drop-down list, select a report format.
y
r
ta
2. From the Select Template drop-down list, select a template.

ie
opr
3. Optional: In the Label box, enter a label.

Pr
e®
cl
NOTE: If the label is not printed on the final report, only the description and
ra
POV sections are visible on the final report.

O
4. In the Description box, enter a description.

5. In the Point of View, specify the point of view for the report.

Selecting Columns and Filters
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Selecting Columns and Filters

ed
When setting up a journal report, first you select the columns to be displayed on the
ct
tri
report. Next you define filters to specify which journals to include in the report.
es
R
To select columns:
-
y
r
ta
1. Click the Columns tab.

ie
pr
2. Perform one or both of the following actions:

o
Pr
• Sort each column in ascending or descending order.

e®
• If a column is a dimension, choose to display dimension labels, descriptions, or

cl
ra
both.
O

To select filters:
1. Click the Filters tab.
2. Select from the following filter options: Entity, Label, Group, Description, Status,
Type, and Balance Type. For example, you can filter a report to include only
unposted journals.
se
Only journals or journal templates that meet all filter criteria are
ur
included in the report.
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Previewing Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Previewing Reports
ed
After specifying properties, columns, and filters, you can preview the report.
ct
tri
es
To preview the report:

R
-
1. On the Process Journals page, click Print/Preview.

ry
ta
A report with your selected options is displayed in a new window.

ie
pr

o
Pr
• Select Print to print the report.

e®
cl
• Select File, then Close to return to the Journals window and save your report
ra
setting.
O

Saving Journal Reports Remotely
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Saving Journal Reports Remotely

ed
If you have the proper security rights, after specifying the layout for the journal report,
ct
tri
you can save the report on the Financial Management server.

es
R
To save journal reports remotely:

-
y
r
ta
1. On the Process Journals page, click Save Remote.

ie
pr
2. Optional: Select the Private check box if you do not want other users to be able to run
o
Pr
the report.
e®
3. Click OK.
cl
ra
4. Click Close.
O

Saving Journal Reports Locally
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Saving Journal Reports Locally

ed
You can save reports that you use on a regular basis to your hard drive or to a network
ct
tri
drive. You can then open the reports on the Web and change the columns and filters as
es
needed.
R
-
y
To save journal reports locally:

r
ta
ie
1. On the Process Journals page, click Save Local.

opr
Pr
The Download Instructions page is displayed.

e®
2. Follow the instructions on the page.

cl
ra
O

Printing Journal Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Printing Journal Reports

ed
When you print the report, you can select to override the report POV and style sheet.
ct
tri
es
To print journal reports:

R
-
1. Open the application and, in the view pane, select Documents, then Reporting, and
y r
ta
then Journal.
ie
pr
A list of saved journal reports is displayed in the view pane.

o
Pr
2. Select a report.
e®
The Journal Report Override dialog box is displayed.

cl
ra
3. Optional: Select and change the point of view and style sheet.
O
4. Click OK.

se
ur
Summary
co
ng
i
in
tra
• Describe the purpose of journals
er
• Open periods for journal entry
rtn
pa
• Create journal templates and journals
e®
• Submit, review and post journals
cl
ra
• View adjusted data
O
• Create and format journal reports an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 7
Translating Data 17
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe the translation process
pa
• Enter exchange rates
e®
cl
• Check translation status
ra
O
• Translate financial data in data grids
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 17 Translating Data
Data Translation Overview
se
ur
co
i ng
in
tra
USD
er
rtn
Entity Currency = USD
pa
Geographical
e®
cl
EUR
ra
O
an
Europe Parent Currency = USD
in
e
Entity Currency = EUR

us
al
on
rs
pe
to
Data Translation Overview

ed
ct
Currency translation converts account data from one currency to another. When you
tri
consolidate data, currency translation occurs if the parent entity has a different default
es
currency than the child entities. Data in the Entity Currency Total member of the child is
R
translated to the parent’s currency, and the result is stored in the corresponding child
-
y
currency member.
r
ta
ie
For example, if EntityA has a default currency of USD and its parent, Europe, has a
pr
default currency of EUR, data in the Entity Currency Total member of EntityA is
o
Pr
translated to EUR and is written to the EUR member of EntityA. The data in the EUR
e®
member of EntityA is then consolidated to the Entity Currency member of Europe.

cl
ra
You may need to translate to currencies other than the parent currency. The Value
O
dimension contains members for all application currencies.

Default Translation Process
se
Compare currencies Geographical April
ur
co
DefCurrency Entity Currency
ng
Europe EUR Gross Sales 240
i
in
Geographical USD Cash 420
tra
er
Europe April
rtn
UsePVAForFlow Yes Entity Currency
pa
UsePVAForBalance No Total USD
e®
Gross Sales 200 240
cl
DefaultRateForFlow AvgRate Cash 300 420
ra
O
DefaultRateForBalance EndRate April
AvgRate an 1.2
in
EndRate 1.4
e
us
al
on
rs
pe
to
Default Translation Process

ed
ct
The example on the slide shows the following steps of the translation process during
tri
consolidation:
es
R
1. The Currency property of the child being consolidated is compared to the Currency
-
property of the parent. If the currencies are different, translation is initiated.

y
r
ta
2. The exchange rate account and translation method are selected based on the
ie
pr
account type:
o
Pr
• For Revenue and Expense accounts, the rate account specified by the Default
e®
Rate For Flow setting is used. If PVA For Flow is enabled, the PVA method is
cl
selected; otherwise the VAR method is selected.

ra
O
• For Asset and Liability accounts, the rate account specified by the Default Rate For
Balance setting is used. If PVA For Balance is enabled, the PVA method is
selected; otherwise the VAR method is selected.

3. The value in the Entity Currency Total member is translated by using the selected
rate account and translation method. The result is stored in the Value dimension
currency member that corresponds to the parent’s default currency.
4. The translated value is consolidated to the Entity Currency member of the parent.
Default Rate For Flow, Default Rate For Balance, Use PVA For Flow, and Use PVA For
se
Flow are application-wide settings that apply to all accounts. You can use custom
ur
translation rules to override these settings. For example, you create a custom translation
co
rule to use a historical rate for some balance sheet accounts but not for others.
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
pr
o
Pr
e®
cl
ra
O

Entering Exchange Rates
Exchange rate account
se
ur
co
ngi
in
tra
er
rtn
pa
Custom dimensions contain system-defined
e®
currency mem bers. In this example, Custom1 is
cl
the source currency, and Custom2 is the
ra
destination currency.
O
an
in
e
us
al
on
rs
pe
to
Entering Exchange Rates

ed
ct
You maintain currency rates by inputting data to the currency members of the Custom1
tri
and Custom2 dimensions. For each application currency, the Custom1 and Custom2
es
dimensions contain system-defined currency members. You must input currency rates to
R
accounts that have the Currencyrate account type.

-
y
r
You translate the currency in Custom1 to the currency in Custom2.

ta
ie
You enter currency rates by using the points of view described in the following table:
o pr
Pr
e®
Scenario The scenario to which the currency rate is applied

cl
ra
Year The year to which the currency rate is applied

O
Period The period to which the currency rate is applied

View YTD
Entity [None]
Value [None]

Account The account that you create to contain currency rates
(The account type must be Currencyrate.)
ICP [ICP None]
Custom1 Source currency
se
Custom2 Destination currency
ur
Custom3 [None]
co
Custom4 [None]
ng
i
in
tra
To enter exchange rates:
er
rtn
pa
2. Click the Data Grids tab, and select a data grid.
e®
3. On the data grid, select the POV for the data grid according to the preceding table.
cl
ra
4. Enter the following currency rate settings:
O
an
• For row, enter the Custom1 dimension. For the example on the slide, the Custom1
in
dimension is LineOfBusiness.
e
us
• For column, enter the Custom2 dimension. For the example on the slide, the
al
Custom2 dimension is Markets.

on
rs
• For the row and column lists, enter the application currencies. For the example on
pe
the slide, both rows and columns contain application currencies of USD, EUR, and
to
GBP.
ed
ct
5. Click Submit.
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Checking Translation Status
Currency EUR
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Checking Translation Status

ed
ct
When a current value member in the Point of View is a currency other than the local
tri
currency of the member, the calculation status indicates whether data needs to be
es
translated.
R
-
y
To check translation status:

r
ta
ie

opr
Pr

e®
3. On the data grid, click Grid Settings.

cl
ra
4. Click the Display Options tab and, under Cell, select Calculation Status.
O
5. Click OK.

The following table describes translation statuses:
Status Description
OK None of the data for the specified Scenario, Year, Period, Entity, and Value
dimensions changed.
TR Needs Translation. The selected Value dimension member is not the entity’s
se
default currency, and its translated values may not be current.
ur
co
TR ND Needs Translation. The parent has no data, but data for a child entity changed.
ng
NoData No data exists for the specified Scenario, Year, Period, Entity, and Value
i
dimensions.
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Translating Financial Data in Data Grids
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
Select Translate to translate Entities with a currency different from the
data to the cur rency shown
in
one shown in the POV bar show a status
in the POV bar.
e
of TR or TR ND until the data is translated.

us
al
on
rs
pe
to
Translating Financial Data in Data Grids

ed
ct
After entering the exchange rates, you can translate the currency for an entity to any
tri
application currency in the Value dimension. If the Value dimension is not on the grid
es
rows or columns, the destination currency is specified in the point of view.

R
-
y
To translate data in data grids:

r
ta
ie

opr
Pr

e®
3. Right-click the cell for the currency, and select Translate.

cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe the translation process
er
• Enter exchange rates
rtn
pa
• Check translation status
e®
• Translate financial data in data grids
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 8
Running Consolidations 18
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe the consolidation process
pa
• Check the calculation status
e®
cl
• Understand consolidation of children by percentages
ra
O
• Assign ownership by period
• Consolidate data an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 18 Running Consolidations
Financial Management Business Process
se
ur
co
Load and Calculate data
add data Adjust data
ng
i
in
tra
Translate &
er
consolidate
rtn
pa
e®
cl
ra
O
an
in
e
us
Run and publish financial reports Lock data Approve data

al
on
rs
pe
to
Financial Management Business Process

ed
ct
Data consolidation is one step of the business process for large (or public) companies.
tri
For the example on the slide, consolidation is typically performed after data is collected,
es
calculated, and adjusted for base-level entities.

R
-
You use the consolidation features in Financial Management to consolidate financial

y
r
data for reporting and analysis.

ta
ie
pr
o
Pr
e®
cl
ra
O

Consolidation Overview
se
NetProfit
ur
co
Connecticut 20000
Consolidated data
ng
for Connecticut entity
i
in
tra
Administration East 6000
er
rtn
Marketing East 5000
pa
e®
Development 4000
cl
ra
O
EastSales 5000
an
in
e
us
al
on
rs
pe
to
Consolidation Overview
ed
ct
Consolidation is the process of gathering data from descendants and aggregating the
tri
data to parent entities. Consolidation applies only to the Entity dimension. After entering
es
or loading data into base-level entities, you run a consolidation for a selected scenario
R
and period to aggregate the data throughout the organization.

-
y
r
The example shown on the slide displays the consolidated data for the NetProfit account
ta
ie
of the Connecticut entity. During consolidation, the data values from the base-level
pr
entities (Administration East, Marketing East, Development, and EastSales) are rolled up
o
Pr
to the parent-level entity, Connecticut.

e®
cl
ra
O

Consolidation Process
• Run calculations
se
ur
• Perform currency translations
co
• Apply ownership percentages
ngi
in
• Eliminate intercompany balances
tra
er
US
rtn
pa
e®
cl
ra
O
Connecticut an
in
e
us
California
al
on
rs
pe
to
Consolidation Process
ed
When you consolidate an entity, processes that are required for the descendants of the
ct
tri
entity run automatically.

es
R
• Calculation rules are run for all descendants of the entity for the period being
-
consolidated and for all prior periods.

ry
ta
• If the data for the child entity and the data for the parent entity are in different
ie
currencies, the data is translated based on the exchange rate. For the child entity, the
o pr
translated value is stored in the Parent Currency member of the Value dimension.
Pr
The translated value in Parent Currency is rolled up to the parent.

e®
cl
• If the parent’s ownership of the child is less than 100%, the ownership percentage is
ra
applied. Intercompany transactions between entities are eliminated at their first

O
common parent.

Consolidation and the Value Dimension
[Contribution Total]
se
[Contribution] [Contribution Adjs]
ur
co
[Proportion] [Elimination]
ngi
in
tra
[Parent Total]
er
[Parent] [Parent Adjs]
rtn
pa
e®
<Parent Currency Total>
cl
<Parent Curr Adjs>
ra
<Parent Currency>
O
<Entity Currency Total> an
in
e
<Entity Currency> <Entity Currency Adjs>

us
al
on
rs
pe
to
Consolidation and the Value Dimension

ed
During the consolidation process, the value in the Entity Currency member of the child
ct
tri
members may be transformed before being aggregated to the parent. The Value
es
dimension stores data for the intermediary steps in the transformation. You can display
R
Value dimension members on data grids and reports. This information provides an audit
-
trail that you can use to determine how the value that each entity contributed to the
y
r
ta
parent was derived.

ie
pr
For the example on the slide, the Contribution Adjs, Proportion, Elimination, Parent Adjs,
o
Pr
Parent Currency, Parent Curr Adjs, and Entity Currency Adjs value dimension members
e®
store data.
cl
Keep in mind the following points about the consolidation process:

ra
O
• Proportion detail is generated when consolidation rules are executed. The Proportion
member also stores the results of the consolidation percentage that is applied to the
base values.
• Based on elimination rules, elimination detail contains eliminating balances that
result during consolidation.
• Contribution Total is the contribution of the base entity to its parent. This amount is
added to the other immediate dependent contributions of the parent to obtain the
parent consolidated data. Intermediate contribution level aggregations are not stored
during calculation.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Checking Calculation Status
Grid Settings
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Checking Calculation Status

ed
ct
Financial Management maintains the calculation status for every Scenario, Year, Period,
tri
Entity, Parent, and Value combination. The calculation status indicates whether data
es
needs to be calculated, translated, or consolidated.

R
-
You can view the calculation status from the Process Control panel or from a data grid.
y r
ta
ie
To check calculation status:

opr
Pr

e®

cl
ra
3. On the toolbar, click Grid Settings.

O
4. Click the Display Options tab and, under Cell, select Calculation Status.
5. Click OK.

The following table describes calculation statuses:
Status Description
OK None of the data for the specified Scenario, Year, Period, Entity, and Value
dimensions changed.
OK SC OK, System Changed. A change may affect the data for the specified Scenario,
se
Year, Period, Entity, and Value dimensions. For example, a new rules file or
ur
metadata file was loaded. The data itself, such as a value of 10,000, has not
co
changed. For a dimension member attribute, the number of decimal places
ng
associated with the account was set to two, and requires the value to be changed
to 10,000.00.
i
in
tra
OK ND OK, No Data. No data has been loaded but calculations were run
er
CH Needs Calculation. At least one data cell for the specified Scenario, Year, Period,
rtn
Entity, and Value dimensions changed, or metadata parameters or rules changed.
pa
As a result, because calculation was not run, other data cells in the dimension
may not be current. For base-level entities, you may have entered the data cell
e®
through data entry or by a data file load. For any entity, the data cell may have
cl
been entered by a journal posting.
ra
O
TR Needs Translation. The selected Value dimension member is not the entity’s
an
default currency, and its translated values may not be current.
in
CN Needs Consolidation. The data for the specified Scenario, Year, Period, Entity,
e
and Value dimensions may not be current because any of the following items
us
changed:
al
on
• Data for a child entity

rs
• Data for the entity's default currency

pe
• Metadata parameters or rules

to
ed
CN ND Needs Consolidation. The parent has no data, but data for a child entity changed.
ct
Locked An administrator locked the data for the specified Scenario, Year, Period, Entity,
tri
and Value dimensions. The data can no longer be modified manually or through
es
calculations.
R
-
NoData No data exists for the specified Scenario, Year, Period, Entity, and Value
y
dimensions.
r
ta
ie
NoAccess The user does not have rights for the specified dimension member.
opr
Pr
e®
cl
ra
O

Consolidation of Children by Percentages
Sample Organization Ownership Structure
se
ur
co
Geographical
ng
100% 100%
i
in
tra
United States Europe
er
100% 90%
rtn
pa
California Connecticut France Italy
e®
cl
80% 50%
ra
O
Plant 1 East Sales Plant 2
an
in
e
us
al
on
rs
pe
to
Consolidation of Children by Percentages

ed
ct
By default, parents consolidate their children 100 percent. However, you can specify a
tri
consolidation percentage. The consolidation percentage determines what percent of a

es
child entity is consolidated to the parent entity.

R
-
For the example on the slide, 100% of California is consolidated into United States, but
ry
only 80% of Plant 1 is consolidated into California. Similarly,100% of Europe is

ta
ie
consolidated into Geographical, but only 90% of Italy is consolidated into Europe and
pr
50% of Plant 2 is consolidated into Italy.

o
Pr
e®
cl
ra
O

Ownership Management
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
System account
us
for consolidation percentage

al
on
rs
pe
to
Ownership Management
ed
You use the Ownership Management page to enter consolidation information for your
ct
tri
child entities:
es
R
• Active status
-
y
• Consolidation percentage
r
ta
ie
• Consolidation method
opr
For the example on the slide, the rows list child entities of the entity that you are using as
Pr
the parent entity in the point of view.

e®
cl
ra
O

About Manage Equity Pickup
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
About Manage Equity Pickup

ed
Normally, investments in subsidiaries are valued at their historical price. However, due to
ct
tri
profit or loss incurred in the subsidiary since the acquisition, historical cost may differ
es
from the actual value of the investment owned.

R
-
During a consolidation, you use Equity Pickup to reflect the current value of the share in
y
r
the equity of the subsidiary.

ta
ie
You create entity pick up calculations by defining and deploying rules for the Equity
opr
Pickup rule type in Calculation Manager. Equity pickup functionality enables you to:
Pr
e®
• Revaluate the investments owned by a holding company

cl
ra
• Replace the historical value of the investments with its current value
O
• Adjust the local currency of the holding company before the holding company is
consolidated into the group

You use the Manage Equity Pick Up task in conjunction with Equity Pickup rules to
perform the following tasks:
• Enter ownership percentages to be used for equity pickup calculations. You
reference these percentages in Equity Pickup rules.
se
• Run Equity Pickup rules.
ur
co
• Run Equity Pickup reports to show ownership percentages.
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Assigning Ownership by Period
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Assigning Ownership by Period

ed
ct
You can assign ownership by period to an entity by selecting whether the status of a
tri
child is active or inactive. To specify an active status, you must have selected the
es
Organization by Period in the application settings.

R
-
Organization by Period enables you to preserve historical organization structures and

y
r
have them coexist in an application with the current organization structure.

ta
ie
Organizational changes may be due to acquisitions, disposals, mergers, or

pr
reorganizations.
o
Pr
In Financial Management, Organization by Period is determined through the use of the

e®
Active system account. The Active account is used as the flag that determines whether
cl
ra
an entity is active or inactive.

O
An active status is used for the following purposes:

• Consolidate a child entity to its parent entity. Inactive entities are not consolidated.

• Affect the data of a parent with an active child. An inactive child does not affect the
parent data.
• Determine Process Management validation. An inactive child is ignored.
• Determine how journal validation rules are followed. No parent adjustments or
contribution adjustments can be posted to inactive children.
se
• Invalidate cells that are associated with [Proportional] or [Elimination] Value
ur
co
dimension members for inactive children.
ng
• Return only active entities when Organization by Period is selected for the Entity
i
in
dimension.
tra
er
• Run the ownership calculation routine only for active children. Inactive children are
rtn
ignored.
pa
Use the Ownership Management page to specify the active status.
e®
cl
ra
To assign ownership by period:
O
an
1. In the view pane, select Data Tasks, and then Ownership Management.
in
The Ownership Management page is displayed.
e
us
2. Select members for the scenario, year, period, and entity dimensions.
al
on
3. In the Entities area, select an entity.

rs
pe
4. In the Active list, select Yes.

to
5. Click Save.
ed
ct
tri
es
R
-
ry
ta
ie
opr
Pr
e®
cl
ra
O

Consolidating Data
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Consolidating Data
ed
ct
You run consolidations from the Consolidate options list on the Process Control Panel
tri
and data grids. You can use the Task Automation functionality to automate the process.
es
When a parent is consolidated, all descendants of the parent are also consolidated.
R
-
If you consolidate data for a period and the data for prior periods was not consolidated,
yr
the data for the prior periods is also consolidated.

ta
ie
opr
Pr
e®
cl
ra
O

The following table describes the three options for consolidating data:
Option Description
Consolidate Available for any parent entity with a status of CN or CN ND.
When you select this option for a parent entity, the system performs
calculations (Calculate, Translate, and Consolidate) for any dependent
se
entity that has a status of CN, CN ND, CH, TR, or TR ND.
ur
co
Consolidate is the most efficient option because only entities that require
consolidation are updated.
ng
i
Consolidate All Available for any parent entity, regardless of its status.
in
tra
Consolidate All consolidates all intersections of the dependants, whether
data exists or not.
er
rtn
Given performance considerations, it is generally not recommended to use
pa
Consolidate All. Subsequent use of Consolidate All With Data will
unnecessarily process more POV than is required
e®
cl
Consolidate All Available for any parent entity, regardless of its status.
ra
With Data
Consolidate All With Data consolidates every dependent entity that
O
contains data, regardless of its status.
an
The system also executes calculation rules for the dependent entities.
in
e
us
When a consolidation starts, the consolidation progress bar (Running Tasks) is

al
automatically displayed in a separate window. You can view information about the
on
completion status of the consolidation, the start time, and the point of view. The
rs
pe
consolidation progress bar enables you to perform other tasks while the consolidation is
to
running, without starting a new session. You can stop a consolidation by clicking the red
ed
circle icon in the Stop Task column.

ct
tri
es
To consolidate data:
R
1. Select an entity.
-
ry
2. On the toolbar, click Consolidate and perform one of the following actions:
ta
ie
pr
• Select Consolidate.
o
Pr
• Select Consolidate All.

e®
• Select Consolidate All with Data.

cl
ra
3. Confirm that the consolidation process is completed successfully.

O

se
ur
Summary
co
ng
i
in
tra
• Describe the consolidation process
er
• Check the calculation status
rtn
pa
• Understand consolidation of children by percentages
e®
• Assign ownership by period
cl
ra
• Consolidate data
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 1 9
Managing the Review Cycle Using

Process Management 19
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe process management and phased submissions
pa
• Describe the process for setting up phased submissions
e®
cl
• View process unit status
ra
O
• Validate process units
an
• Move process units through the review cycle
in
e
• View and manage process units in data grids

us
al
• Lock process units

on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 19 Managing the Review Cycle Using Process Management
Process Management Overview
Use process management to review, promote, submit, approve,
se
reject, and publish process units.
ur
co
ngi
in
tra
Review Promote Subm it Approve Publish
er
rtn
pa
Reject
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Process Management Overview

ed
ct
Process management is the management of the review and approval of financial data.
tri
You can use process management to submit budget plans and have them approved
es
efficiently, and to transfer ownership of data. In a centralized environment, you can also
R
use process management to provide review control and to ensure data privacy.
-
yr
If process management is enabled for a scenario, validation checks are performed for
ta
ie
each process unit as the data moves from one level to the next. Validation checks are
pr
defined by the administrator to ensure that accounts are in balance.

o
Pr
e®
cl
ra
O

Process Units
se
ur
Example
co
ng
• Scenario Actual
i
in
• Year 2010
tra
• Period January
• Entity West Sales
er
• Value USD
rtn
pa
e®
cl
Process unit
ra
O
an
in
e
us
al
on
rs
pe
to
Process Units
ed
For the purpose of review, data is organized into process units. A process unit is the
ct
tri
combination of data for a specific Scenario, Year, Period, Entity, and Value dimension. In
es
the Value dimension, you can select Local, Translated, or Contribution data.
R
-
For the example on the slide, the process unit is a combination of data for Actual, 2010,
yr
January, WestSales, and USD.

ta
ie
During the review cycle, users perform actions on process units, such as promote,
opr
submit, approve, reject, and publish.

Pr
e®
cl
ra
O

Process States
Every process unit has one of the following states:
se
ur
Not Started
co
ngi
in
First Pass
tra
er
rtn
Review Level 1, 2,…
pa
e®
Submitted
cl
ra
O
Approved
an
in
e
Published
us
al
on
rs
pe
to
Process States
ed
Process units pass through a number of process states during the review cycle. The
ct
tri
following table describes the process states:

es
R
Task Description
-
y
Not Started The review supervisor has not started the process unit, and only the
r
ta
supervisor can enter data.

ie
pr
First Pass The process unit is started and is in the initial stage for data to be
o
entered by users with the proper access rights.

Pr
e®
Review Level 1–10 The process unit is at the designated review level.
cl
Submitted The process unit was submitted and is ready for final approval.
ra
O
Approved The process unit was approved.

Published The process unit was published for public access.

Process Management Security Roles
• Security roles determine the review actions that users can
se
perform.
ur
co
• Security roles aid compliance with Sarbanes-Oxley,
ng
especially requirements imposed by Section 404.
i
in
tra
er
rtn
pa
e®
cl
ra
O
Reviewer 1 Reviewer 10 Submitter Review
an
in Supervisor
e
us
al
on
rs
pe
to
Process Management Security Roles

ed
The actions that users can perform are determined by their assigned security roles. The
ct
following table describes the actions permitted for each security role:
tri
es
R
Security Role Description

-
y
Reviewers 1 Can promote a process unit to the next level or reject it. When a reviewer
r
ta
through 9 promotes a unit to the next level, data for that unit becomes read-only for
ie
users at the current level.

o pr
Reviewer 10 Can reject a process unit, but cannot promote it because a next level is not
Pr
available. To move a process unit to the Submitted level for final approval,
e®
Reviewer 10 must be a Submitter.

cl
ra
O

Security Role Description

Submitter Can move the process unit to the final stage of the review process so that it
is ready for approval. Although the default action is to promote the process
unit to the next level, the Submitter can omit many levels of review and go
to the last process level (Submitted) before final approval.
Review Has access rights to start a process unit that allows input to the entity’s
se
Supervisor data. Can also approve and publish the data.
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Process Management Options
To set up process management:
se
• Perform the following actions for the Scenario dimension
ur
co
member:
ng
– Select Y for the Enable Process Management attribute.
i
in
tra
– Specify the phased submission start year.
er
• Enter the validation account in the ValidationAccount field
rtn
in the Application Settings.
pa
• Assign security roles to users.
e®
• Assign security classes to users (promote access, alerts).
cl
ra
O
an
in
e
us
Reviewer 2
al
on
rs
pe
to
Process Management Options

ed
Before you can use the Process Management option, you must enable scenarios in
ct
tri
Dimension Library. The system performs validation checks for each process unit as the
es
data moves from one level to the next.

R
-
When you select a single cell, process management is available only for the input
ry
frequency of the scenario. For example, if the input frequency is months, process
ta
ie
management is available when you select January, but it is not available when you select
pr
a quarter, such as Q1. In addition, if you select multiple cells and your selection includes
o
Pr
a data cell in which process management is not supported, the option is not available.
e®
For instructions on enabling scenarios in Dimension Library, see Lesson 9, “Setting Up

cl
Entities, Calendars, and Scenarios.”

ra
O
For instructions on configuring validation account settings, see Lesson 7, “Configuring

Application Settings.”

About Phased Submission
Phased submission has:
se
• Flexible assignment of account, custom, and ICP
ur
co
dimensions
ng
• Support for 99 submission groups
i
in
tra
• Nine submission phases with different validation accounts
er
rtn
pa
e®
cl
ra
O
Expenses Incom e Liabilities Assets
an
in
Phase 4 Phase 3 Phase 2 Phase 1
e
us
al
on
rs
pe
to
About Phased Submission

ed
ct
Because process unit data could be related to hundreds of accounts, reviewers and
tri
approvers may have difficulty effectively analyzing the data. With submission phases,
es
you can divide a process unit into submission groups defined by account, custom, and
R
ICP dimensions. You then assign submission phases to the submission groups and
-
y
place the groups in hierarchical order to publish in process management.

r
ta
ie
For example, in the Actual scenario, you submit the Balance Sheet and Profit/Loss
pr
accounts for review in Phase 1, and supplemental data in Phase 2. In the Budget
o
Pr
scenario, you submit Intercompany data in Phase 1, Balance sheet and Profit/Loss
e®
accounts in Phase 2, and supplemental data in Phase 3. With the process unit divided,
cl
smaller chunks of data are published, giving reviewers and approvers tighter quality
ra
control.
O

Submission Group Guidelines

• You must modify application and dimension metadata files to use submission
groups.
• The maximum number of submission groups is 99.
• Submission groups can vary by account, custom, and ICP dimension.
se
ur
• You cannot assign the same group to multiple phases in the same period. For
co
example, you cannot assign Groups 2 through 5 to Phase 1, and Groups 3 and 8 to
ng
Phase 2, because Group 3 cannot be assigned to Phases 1 and 2 in the same
i
in
period.
tra
• If you move all groups from one submission phase to another, the original phase is
er
rtn
cleared entirely from the system for the specified scenario and period.
pa
• You can skip submission phase assignments. For example, you can assign groups to
e®
submission Phases 1 and 3 without assigning groups to Phase 2.
cl
ra
• During the review process, you can promote each submission group in the process
O
unit rather than the entire process unit.
an
• Groups not assigned to a submission phase are not considered part of the review
in
e
process.
us
• Base accounts do not inherit submission groups from parent accounts.

al
on
• Parent accounts do not assume submission groups from their children.

rs
pe
• A blank submission group defaults to Submission Group 1.

to
ed
ct
Submission Phase Guidelines

tri
• You must modify application and dimension metadata files to use submission
es
R
phases.
-
• The maximum number of submission phases allowed in the review process is 9.

yr
ta
ie
• Submission phases can vary by period and scenario.

opr
Pr
e®
cl
ra
O

Process for Setting Up Phased Submissions

Assign Validation Accounts
Set Application and Metadata Attributes to Submission Phases
se
Validation Account 2
ur
co
Phase 1 – Balance Sheet
ng
1 Phase 2 – Supp. Data
i
in
tra
Phase 3 – Income Stmt.
er
rtn
Assign Submission Gr oups Assign Subm ission Groups to
pa
to Subm ission Phases Dimension Member s
e®
4
cl
Submission Phases
ra
O
Phase 1 – Balance Sheet
Phase 2 – Supplemental Data an

in
e
Phase 3 – Income Statement

3
us
al
on
rs
pe
to
Process for Setting Up Phased Submissions

ed
ct
You perform the following tasks to set up submission phases:

tri
es
1. Set the application and dimension metadata attributes to use submission phases.
R
2. Assign validation accounts to submission phases.

-
y
r
ta
3. Assign submission groups to dimension members.

ie
pr
4. Assign submission groups to submission phases.

o
Pr
e®
cl
ra
O

Setting Application and Metadata Attributes
Set Application and Metadata Attr ibutes
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Application and Metadata Attributes

ed
By default, the setting for submission phases is turned off, and the administrator must
ct
tri
enable phased submissions in the application:

es
R
UseSubmissionPhase=Y/N
-
y
The administrator must then define which dimensions (Account, Custom 1-4, and ICP
r
ta
Members) will be enabled for process management. At a minimum, you must enable at
ie
pr
least one dimension.

o
Pr
For example, if the application needs submission by accounts, Custom 1 to 4, and ICP
e®
dimensions, you can select the SupportSubmissionPhase setting for accounts, Custom 1
cl
to 4, and ICP dimensions.

ra
O
For instructions on setting application and metadata attributes, see Lesson 6, “Creating
Applications.”

Assigning Validation Accounts

to Submission Phases
se
ur
co
ng
Validation accounts
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Assigning Validation Accounts to Submission Phases

ed
You assign validation accounts to submission phases to ensure that the value equals
ct
tri
zero before a process unit is promoted to the next review level. Financial Management
es
application settings include one validation account for each of the nine submission
R
phases.
-
yr
ta
ie
NOTE: If a validation account is not set for a submission phase, validation is not
pr
needed for that phase. You can use the same validation account across
o
Pr
multiple submission phases.

e®
cl
ra
For instructions on assigning validation accounts to submission groups, see Lesson 6,

O
“Creating Applications.”

Setting Up Submission Groups
Set Up Submission Groups
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Up Submission Groups

ed
For each application, the administrator must decide which dimension members to
ct
tri
include in a submission group.

es
R
In the metadata file, you set the following attribute for submission groups:
-
y
SubmissionGroup=0 to 99 or <blank>
r
ta
ie
Notes:
opr
• The default is blank. A <blank> value defaults to the value of 1.

Pr
e®
• If you set the submission group to zero, the account is not included in the review
cl
process.
ra
O
• You can specify the submission groups for [ICP None], and [ICP Entities]. The
submission group value assigned to [ICP Entities] applies to all ICP entities in the
[ICP Entities] subtree.

To easily work with dimension members, you should categorize them into appropriate
groups. For example, you can define Cash accounts and Investment accounts for
Submission Group 1.
When a submission group has an assignment of 0, the account does not require a review
process. The following tables show examples of dimension members categorized into
submission groups by account and by product:
se
ur
co
Accounts Submission Groups
ng
HistData 0 0
i
in
Cash 1
tra
Invest 1
er
rtn
ICRec 2
pa
ICPay 2
e®
Liability 3
cl
ra
Equity 8
O
Revenue 4
Expense 4 an
in
e
us
al
on
rs
C1 (Product) Submission Group

pe
[None] 1
to
Golf Balls 5
ed
ct
Tennis Balls 6
tri
es
Soccer Balls 7
R
-
yr
ta
NOTE: For the dimensions that support phased submission (Accounts, Custom 1-4,
ie
and ICP), you should include every member for the dimension in a
o pr
submission group (0 to 99).

Pr
e®
cl
For instructions on setting submission groups, see Lesson 6, “Creating Applications.”

ra
O

Assigning Submission Groups

Display setting
to display 1-9 phases
se
ur
co
ng
Assignm ent
i
in
tra
er
rtn
pa
Submission
e®
groups
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Assigning Submission Groups

ed
Administrators can assign submission groups to each submission phase. The

ct
tri
assignment applies only to the scenario that supports process management. If a group is
es
not specified, process management is not applied to the dimensional members within
R
that group.
-
r y
You can display and manage submission phases using the “Manage Submission
ta
ie
Phases” task. This task displays if you enable the UseSubmissionPhase application
pr
setting in the metadata file. You must also be assigned to the administrator or Review
o
Pr
Supervisor security role.

e®
cl
To access the Manage Submission Phases Task:

ra
O
1. In the view pane, select Tasks, then Data Tasks, and then Manage Submission Phases.
2. Perform any of the following tasks:

• Specify the submission phase (1 to 9). You can change the setting as needed to
display different submission phases.
• Enter one or more groups for a submission phase, and use a comma as a
separator for multiple group assignments (for example, 1, 5, 6, 9, 10).
• Specify a range of groups. For example, to assign groups 1, 2, 3, 4, 5, 7, and 8 to
se
a submission phase, specify 1-5, 7-8.
ur
co
You can have up to 99 submission groups. You can enter ALL to indicate all groups.
The default for Submission Phase 1 is ALL to indicate all groups.
ng
i
in
tra
NOTE: All groups belongs to Submission Phase 1 until you change their
er
rtn
assignment.
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Security Access for Process Units
You access data in a process unit based on a combination of
se
the following items:
ur
co
• Your assigned security role
ng
• Your access rights to the process unit (through security
i
in
classes)
tra
er
– None
rtn
– Read
pa
– Promote
e®
– All
cl
ra
• The current review level of the process unit
O
an
in
e
us
al
on
rs
pe
to
Security Access for Process Units

ed
ct
Access rights for process units can be None, Read, Promote, or All. The following table
tri
describes the access rights:

es
R
Access Description
-
ry
None No access to the process unit

ta
ie
Read Ability to view only data for the process unit

o pr
Promote Ability to view data and promote an entity without All access
Pr
e®
All Complete access, including viewing and modifying data

cl
ra
O

Viewing Process Unit Status
se
ur
co
Click a process unit Process Control toolbar
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
Process unit status

al
on
rs
pe
to
Viewing Process Unit Status

ed
ct
You view the status for process units on the Process Control panel. The panel contains a
tri
point of view with the Scenario, Year, and Period dimensions. If you enabled submission
es
phases, the review level for each process unit is stored by submission phase.
R
-
y
To view process unit status:

r
ta
ie
1. In the view pane, select Tasks, then Data Tasks, and then Process Control.
opr
Pr
2. For Top Member, click Browse, select a top member, and select a member list.
e®
3. In the Data View list, select Local, Translation, or Contribution.

cl
ra
O

The following table describes the options on the Process Control toolbar:
Icon Name Description

Options Displays the Options dialog box, with options for
displaying, filtering, and sorting
se
ur
co
Refresh grid Refreshes the grid after process control actions
ngi
in
tra
Manage Process Displays a menu with the following options:
er
• Start
rtn
pa
• Promote
e®
• Submit
cl
• Approve
ra
O
• Publish
• Sign Off
an
in
• Reject
e
us
Consolidate Displays a menu with the following options:

al
• Consolidate
on
• Consolidate All
rs
pe
• Consolidate All With Data

to
• Calculate Contribution
ed
• Force Calculate Contribution

ct
tri
Calculate Displays a menu with the following options:

es
• Calculate
R
• Force Calculate
-
yr
ta
Translate Displays a menu with the following options:

ie
• Translate
opr
• Force Translate
Pr
Summary Displays a menu with the following options:

e®
• Review Level Summary

cl
ra
• Calculate Status Summary

O
Rates Displays a predefined Web grid with rate data

(The grid label for the predefined Web grid must
be named Rates.)

Icon Name Description

Ownership Displays the Ownership Management page
Management
Page Up, Page Displays the next or the previous page
se
Down
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Setting Process Control Panel Options
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Setting Process Control Panel Options

ed
You can display entities in a flat list or as a tree hierarchy. Use the tree hierarchy only if
ct
tri
you select the [Hierarchy] system member list. All other member lists are displayed as a
es
flat list. In tree hierarchy view, row sorting or filtering is unavailable.

R
-
y
To set process control panel options:

r
ta
ie
pr
o
Pr
The Process Control page is displayed.

e®
2. On the Process Control toolbar, select Options.

cl
ra
The Options page is displayed.

O
3. On the Row tab, under Style, select List or Tree.

4. Optional: Next to an entity, click the plus (+) or minus (-) sign to expand and collapse
a hierarchy (tree view only).

Filters and Sorting

When you use a list view, row sorting and filtering are available. For example, you can
filter rows based on the review level and display all rows above or below a specific
review level, such as all levels above First Pass.
After you set the following filtering options, the settings are displayed in tooltips for the
columns in the Process Control panel:
se
ur
• Filter by review level, such as First Pass, Review Level 1.
co
• Filter rows by validation status, such as Pass Only or Fail Only.
ng
i
in
• Filter rows by calculation status, such as OK, CN, or TR.
tra
er
rtn
Entity View
pa
You can view entity information using the entity label, the description, or both. The
default setting is to display the label.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Viewing Status for Multiple Submission Phases
se
Use the Columns tab
ur
to select phases.
co
Options
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Status for Multiple Submission Phases

ed
You can select the submission phases for which you want to view status. You can also
ct
tri
select the review and status information for which you want to include columns.
es
R
To view status for multiple submission phases:

-
y r
ta
ie
pr

o
Pr

e®

cl
ra
3. Select the Col tab.

O
4. Under Phase, select the phases for which you want to view status.
5. Click OK.

Viewing Status for All Periods
se
ur
co
Options
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Status for All Periods

ed
You can view either a single period or all periods. When you choose all periods, you can
ct
tri
view status for only one submission phase at a time, and you must choose to view either
es
the Process Review Level or Calculation Status.

R
-
y
To view status for all periods:

r
ta
ie
opr
Pr

e®

cl
ra
3. Select the Col tab.

O
4. For Period View, select All.

5. Click OK.

Validating Process Units
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
This column indicates A check mark is displayed
whether there are an if the Validation account and
in
unposted journals. the calculation status are OK.
e
us
al
on
rs
pe
to
Validating Process Units

ed
ct
Process units can be promoted only if their calculation status is OK, OK SC, or NODATA
tri
and the validation account amount is equal to zero. The Pass/Fail column displays a
es
check mark or an X to show whether the conditions are met. If the calculation status is
R
OK,OK SC, or NODATA and the validation account amount is equal to zero, a check
-
y
mark is displayed in the Pass/Fail column, indicating that the unit is ready for promotion.
r
ta
If the process unit fails, an X is displayed in the Pass/Fail column.

ie
pr
If the process unit fails, you must perform the calculation in the current period to ensure
o
Pr
that the data is valid for promotion. After calculation, if the validation account is equal to
e®
zero, the calculation status is updated to OK and the status of the column changes to
cl
Pass.
ra
O

The journal status column displays the status of journals. The column title varies based
on the member selected for data view. The following table describes the column titles for
the data views:
Data View Column Title

Local Entity Currency Adjustments (ECA)
se
Translation Parent Currency Adjustments (PCA)
ur
co
Contribution One column for Parent Adjustments (PA) and one column for Contribution
ng
Adjustments (CA).
i
in
tra
In the journal status column, a green flag indicates that there are no unposted journals. A
er
red flag indicates that unposted journals must be posted for the entity. However,
rtn
unposted journals do not prevent an entity from being promoted.
pa
When you hover the cursor over a flag in the journal status column, the number of
e®
unposted journals is displayed. When you click the flag, the Journals module opens so
cl
ra
that you can view the unposted journals for the selected process unit. You can then post
O
the journals that need to be posted.
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

Validation Accounts Overview
Validation accounts:
se
• Must have an account balance equal to zero before a
ur
co
process unit can be promoted to the next review level
ng
• Must have a formula defined in the rules file to generate its
i
in
balance
tra
er
**********************************************************************
rtn
'Validation Rules
'Validation Rules will only run at the legal entity level
pa
'User defined field # 1 has been set to LEGAL for all legal entities
e®
'**********************************************************************
cl
ra
O
If HS.Entity.UD1("") = "LEGAL" then
If HS.Year.Member > 2010 Then
HS.EXP "A#V7900 = A#7900"
an
in
Validation account 100 100
e
us
Account calculation = Assets – (Liabilities+ Equity)

al
on
rs
pe
to
Validation Accounts Overview

ed
Validation accounts are used as a balancing mechanism. You use rules to customize
ct
tri
validations in process management.

es
R
For the example on the slide, a validation rule runs only at the legal entity level, a
-
customer-defined level. The user-defined field #1 member attribute is populated with

yr
LEGAL to define and identify the legal entities.

ta
ie
If you are using phased submissions, you can have separate validation accounts for
opr
each submission phase. Financial Management application settings include additional

Pr
validation accounts that you can use for each submission phase:
e®
cl
Validation Account= (current validation account; now used for Submission Phase 1)
ra
O
Validation Account2 =<valid account> (for Submission Phase 2)



se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Viewing Validation Account Details
se
Click the check mar k in
ur
the Pass/Fail column.
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Validation Account Details

ed
The Pass/Fail column is linked to the Validation Account Detail page so that you can
ct
tri
view additional details about calculation status and validation account information. This
es
link displays all children associated with the validation account and balances. When you
R
drill down to the detail screen, the system displays the following information:
-
y
r
• Calculation status for Entity Currency, Entity Curr Adjs, and Entity Curr Total
ta
ie
• Validation account amount for Entity Currency, Entity Curr Adjs, and Entity Curr Total
opr
Pr
To view validation account details:

e®
cl
• Click the check mark in the Pass/Fail column.

ra
O

Calculating and Consolidating Data
se
ur
Calculate and Consolidate options
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Calculating and Consolidating Data

ed
ct
If you need to promote a process unit that does not have the correct status (for example,
tri
CN or CN ND), you can calculate or consolidate the process unit directly from the
es
Consolidate options drop-down list on the Process Control toolbar. You must have the
R
appropriate security access.

-
y
r
ta
ie
To calculate and consolidate data:

opr
Pr
e®

cl
2. On the Process Control toolbar, select Consolidate, and perform one of the following
ra
O
actions:
• Select Consolidate.
• Select Consolidate All.

• Select Consolidate All with Data.

• Select Calculate Contribution.
• Select Force Calculate Contribution.
3. Confirm that the process is completed successfully.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Moving Process Units Through the Review Cycle
Manage Process
se
ur
co
Manage Process commands
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Moving Process Units Through the Review Cycle

ed
ct
You use the Manage Process commands to move process units through the review
tri
cycle.
es
R
Process units must have a calculation status of OK, OK SC, or NO DATA and a zero
-
balance in the validation account before you can promote them. Process units with
yr
unposted journals can be promoted.

ta
ie
pr
When you promote parent entity data to the next process level, validation checks are
o
performed to verify that the child entities are at the level to which you are trying to
Pr
promote the parent. A parent can be promoted only to a level that is less than or equal to
e®
the lowest level of its children.

cl
ra
O

To move process units through the review cycle:

2. Select the units and, on the Process Control toolbar, select Manage Process, and then
Promote.
se
ur
co
Submission Phases and Review Levels
ng
The review level for each process unit is stored by submission phase. You must promote
i
in
each submission phase independently. All rules for promotion to each review level apply.
tra
In addition, be aware of the following dependency based on the submission phase
er
number: The review level of a submission phase must be less than or equal to the review
rtn
level of the lower-numbered phases in that process unit.
pa
e®
For example, you divide Income, Balance Sheet, and Supplemental accounts into three
submission groups. The groups for Income and Balance Sheet accounts are assigned to
cl
ra
Phase 1 and the group for Supplemental accounts is assigned to Phase 2.
O
an
If the Phase 1 accounts, Balance Sheet and Income, are at Review Level 4, you cannot
in
promote Phase 2 accounts, Supplemental, to a review level greater than 4. In the same
e
way, you cannot reject a submission group if it violates the submission phase rule.
us
al
The following table describes the commands on the Manage Process menu:
on
rs
Command Description
pe
Start Brings data to First Pass. Cells on data entry forms and grids display
to
NOACCESS until the Review Supervisor starts the process unit.

ed
ct
Promote Promotes process units for all review levels. After a process unit is promoted for
tri
review, data can be viewed only by a user with the appropriate review-level
es
security role. For example, if the process unit is promoted to Review Level 2,
R
only a user with the security roles of Review Level 2 or higher can view the data.
-
Submit Submits process units for final approval.

y
r
ta
Approve Approves process units. A process unit must have a status of OK, OK SC, or
ie
pr
NO DATA to be approved.
o
Pr
Publish Publishes process units after they are approved. When process units are
published, the data is available for viewing by all users with security access to
e®
the data in the process unit.

cl
ra
Sign Off Signs off on process units from Review Level 1 or higher. When a process unit
O
is signed off, its status does not change.

Reject Rejects process units and demotes them to their previous review level.

Selecting Review Levels
se
ur
co
ng
Available
i
in
review levels
tra
er
rtn
pa
e®
Promote
cl
ra
current entity
O
only or include
an
descendants in
e
us
al
on
rs
pe
to
Selecting Review Levels

ed
When you select Promote from the Manage Process menu, the Promote dialog box is
ct
tri
displayed. You use the Promote To list to select the review level. If the entity is a parent,
es
you can also promote its descendants.

R
-
y
To select review levels:

r
ta
ie
1. On the Process Control toolbar, select Manage Process, and then Promote.
opr
Pr
2. In the Promote To list, select a review level.

e®
3. In the Apply Action To list, perform one of the following actions:

cl
ra
• Select Selected Entity Only.

O
• Select Selected Entity and Descendants.

4. Click Promote.

E-mail Alerts
se
ur
co
ng
i
in
tra
Users at review
Review L evel 4
er
Review Level 5 level 5
rtn
E-m ail
pa
alerts
e®
cl
ra
O
an
in
User s at review
e
level 4
us
al
on
rs
pe
to
E-mail Alerts
ed
If e-mail alerting is enabled for the process unit scenario, process management triggers
ct
tri
e-mail alerts based on a change of status for the process unit. Alerts are sent for the
es
following actions: First Pass, Review Levels 1 through 10, Submitted, Approved, and
R
Published. Alerts are not generated when the process unit is at the Not Started level or
-
for the Sign Off action.

y
r
ta
ie
The system automatically generates e-mail alerts to the appropriate users for the action,
pr
according to the review level assignments. The system sends e-mail alerts to both the
o
Pr
users at the level before the process control action and to the users at the current level
e®
after the action.

cl
For example, User A and User B have Reviewer 4 role access, and Users C and D have
ra
O
Reviewer 5 role access. When the process unit is at Level 4 and is promoted to Level 5,
Users A and B receive e-mail alerts because they are at Level 4 before the promote
action. Users C and D receive e-mail alerts because they are at Level 5, which is the
current level after the promote action.

When the e-mail alert is generated, the user who performed the action receives a
confirmation e-mail that contains the action performed, the process units affected as part
of the action, and the names of the users receiving the e-mail alerts for each process
unit.
Requirements for e-mail alerts:
se
• An SMTP mail server must be specified on the Web Server tab of the EPM System
ur
Confugurator.
co
• The alerting process uses the e-mail addresses that are stored in your external
ng
i
authentication files. To receive e-mail alerts, users must be on either LDAP or
in
tra
Microsoft Active Directory.
er
• The Supports Process Management-A attribute, which is set in the Metadata
rtn
Manager, must be enabled for the process unit scenario.
pa
e®
• The user must have the Receive Email Alerts from Process Management user role.
cl
• The user must have e-mail alert access to the security class for the process unit
ra
O
entity and scenario.
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Viewing Review History
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Review History

ed
The Process Flow History window displays process history by date and time, user, action
ct
tri
taken, process level, and comments.The information cannot be changed or deleted. It is

es
automatically updated as units are processed by individual users.

R
-
y
To view review histor y:

r
ta
ie
opr
Pr

e®
2. For Top Member, click Browse, select a top member, and select a member list.
cl
ra
3. Right-click an entity, and select Process Flow History.

O

Viewing Process Level in Data Grids
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Viewing Process Level in Data Grids

ed
ct
You can perform process management tasks in data grids.

tri
es
R
To view process level in data grids:

-
1. Open a data grid.

y r
ta
ie
2. In the tool bar, click Grid Settings.

opr
The Grid Settings page is displayed.

Pr
e®
3. Select the Display Options tab.

cl
4. Under Cell, select Process Level.

ra
O
5. Click OK.
The data grid displays the process levels for all cells.

Managing Process Unit States in Data Grids
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Managing Process Unit States in Data Grids

ed
ct
You can promote, submit, approve, publish, and lock a process unit from a data grid.
tri
es
Criteria for phased submissions in data grids:

R
• If a cell is selected in a data grid and Process Management is selected, the system
-
y
determines the submission phase that applies to the cell.

r
ta
ie
• You can have one review status for each submission phase. When cells are
pr
promoted, you promote all cells for that submission phase.

o
Pr
e®
To manage process units in data grids:

cl
ra
1. In a data grid, right-click one or more cells.

O
2. Select Manage Process.

The Manage Process page is displayed.
3. Under the Action list, select to start, promote, reject, sign off, submit, approve, or
publish the units.
Locking and Unlocking Data

Submit Data for Review
se
ur
co
i ng
in
tra
Appr ove/Publish Data
er
rtn
pa
e®
cl
ra
O
an Lock Data
in
e
Change display settings

us
to calculation status.
al
on
rs
pe
to
Locking and Unlocking Data

ed
ct
After publishing submitted data, you may need to lock the data to prevent changes to the
tri
data for a selected category, year, and period. Once the data is published, only
es
administrators and review supervisor can modify the data.

R
-
y
r
ta
NOTE: You can lock and unlock data either in a data grid or web form.
ie
opr
Pr
You can lock data only if the following conditions are met:
e®
• The calculation status for the entity is OK.

cl
ra
• All prior periods are locked.

O
• The validation account for the Entity Currency and Entity Currency Adjs members of
the Value dimension is zero.

• If the current scenario is enabled for Process Management, the process unit status is
Published.
The locked status is a calculation status and applies to the entire process unit. Before
applying locked status, the system checks for the following conditions:
• All processing unit cells reached the Published status or are “Not Supported.”
se
• All validation accounts have the appropriate phases and a zero value.
ur
co
ng
To lock and unlock data:
i
in
tra
In a data grid, perform an action:
er
• Right-click one or more cells and select Lock.
rtn
pa
• Right-click one or more locked cells and select Unlock.
e®
cl
ra
TIP: To lock or unlock data for an entire entity hierarchy, select only the top parent.
O
When you lock or unlock a parent entity, the descendants of the parent are also
an
locked and unlocked. When unlocking data, you must unlock a parent entity
in
before you unlock its children.
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe process management and phased submissions
er
• Describe the process for setting up phased submissions
rtn
pa
• View process unit status
e®
• Validate process units
cl
ra
• Move process units through the review cycle
O
an
• View and manage process units in data grids
in
• Lock process units
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 2 0
Analyzing Data with Smart View 20
se
ur
co
ing
Objectives
in
tra
er
rtn
• Navigate Smart View
pa
• Connect to data sources
e®
cl
• View and analyze data with the ad hoc analysis tool
ra
O
• Add smart slices and cascading reports
• Submit data an
in
e
• Work with data forms in Smart View

us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 20 Analyzing Data with Smart View
Navigating Smart View
• Smart View is a Microsoft Excel add-in that enables you to
se
use the familiar Excel interface to view and analyze data.
ur
co
• Using menu-driven options in Microsoft Office, you can
ng
retrieve Financial Management data into Office.
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Navigating Smart View

ed
ct
Smart View is a Microsoft add-in that provides the framework to integrate Microsoft
tri
Office products with Financial Management, Planning, Financial Reporting, and Web
es
Analysis information.
R
-
Using menus in Microsoft Office, you can retrieve Financial Management data in Smart
ry
View.
ta
ie
o pr
Pr
e®
cl
ra
O

Smart View Installation Components
• Server-side provider
se
• Client component
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Smart View Installation Components

ed
Smart View consists of the following parts:

ct
tri
es
• A provider on the Financial Management Web server

R
• A client component so that end users can access the Smart View menu in Microsoft
-
y
Office
r
ta
ie
o pr
Pr
e®
cl
ra
O

Business Process for Smart View
se
ur
co
ngi
in
tra
View and analyz e data in a spreadsheet.
er
Connect to a data source.
rtn
pa
e®
cl
ra
O
Save spr eadsheet and submit data an
in
to Financial Management (optional).
e
us
al
on
rs
pe
to
Business Process for Smart View

ed
1. Connect to the Financial Management data source.

ct
tri
es
2. View and analyze data in the Microsoft Excel spreadsheet.

R
3. Optional: Save the spreadsheet, and submit the data to Financial Management to
-
y
update the database.

r
ta
ie
opr
Pr
e®
cl
ra
O

Components of Smart View
se
ur
co
ngi
in
tra
er
rtn
Smar t View ribbon
pa
e®
cl
Smart View panel
ra
O
an
in
e
us
al
on
rs
pe
to
Components of Smart View

ed
You connect to data sources and access Smart View functionality through ribbon
ct
tri
commands and the Smart View panel.

es
R
The Smart View ribbon, which contains commands for common Smart View operations,
-
is displayed on the Smart View tab and is always present. When you enter ad hoc
y
r
analysis, the HFM Ad Hoc tab is also displayed. When you open a Financial
ta
ie
Management form in Smart View, the HFM Ad Hoc tab is replaced by the HFM tab.
opr
From the Smart View panel, you can manage data source connections, access data and
Pr
task lists, open Financial Management data forms, and create reports.
e®
cl
ra
O

Connecting to Data Sources
• Use Data Source Manager to establish a connection to a
se
Financial Management data source.
ur
co
• Data connections can be shared or private.
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
Shared connection Private connection
e
us
al
on
rs
pe
to
Connecting to Data Sources

ed
ct
You use Data Source Manager to manage data source connections. A connection is a
tri
communication line between users and the data source; the data source can be
es
connected to or disconnected from the provider server.

R
-
You can add, delete, and modify connections for each Excel instance. These
y
r
connections have no relationship to worksheets. You can establish multiple connections

ta
ie
for each Excel instance.

o pr
Data connections are of two types:

Pr
e®
• Shared connections are created by Administrators, stored in a central location, and

cl
are available to multiple users through the Shared Services panel.

ra
O
• Private connections are created by users by saving the shared connections locally or
by entering a URL to a provider that was not configured for shared connections.

To connect to data sources:

1. In Excel, select the Smart View tab.
The Smart View ribbon is displayed.
2. Click Open.
se
The Smart View Home panel is displayed.
ur
3. In the Smart View Home list, perform one of the following actions:
co
ng
• Click Shared Connections to display the Shared Connections list.
i
in
tra
• Click Private Connections to display the Private Connections list.
er
4. In the Shared Connections or Private Connections list, select a connection, enter
rtn
your user name and password, and click Connect.
pa
The data source is displayed in the Smart View panel.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Viewing and Analyzing Data

with the Ad Hoc Analysis Tool
• Use the Ad Hoc Analysis tool to analyze
se
data from a data source.
ur
co
• After connecting to a data source and
ng
opening a worksheet, open the default
i
in
grid to begin analysis. (The default grid is
tra
specific to the data source.)
er
rtn
• Pivot dimensions.
pa
• Create free-form ad hoc queries by
e®
entering member names directly on the
cl
ra
spreadsheet.
O
an
in
e
us
al
on
rs
pe
to
Viewing and Analyzing Data with the Ad Hoc Analysis Tool

ed
ct
With the Ad Hoc Analysis tool, you can perform the following actions:
tri
• Create a grid
es
R
• Change the Point of View

-
• Change members
ry
ta
• Drill down and up dimension hierarchies

ie
pr
• Pivot dimensions
o
Pr
• Display cell texts

e®
• Add formulas and preserve formatting

cl
ra
• Create free-form ad hoc queries

O
The default grid layout is specific to the Financial Management data source. You can
begin working with data by using the default grid, or you can update the columns and
rows with additional or different dimension members.

The default ad hoc grid displays accounts in the rows and periods in the columns. The
remaining dimensions default to the first member of the dimension.
By default, cells are formatted using the color scheme that is used for data grids in the
Web client. For example, cells with modified data are shaded yellow, and invalid cells are
shaded orange. You can customize cell formatting by selecting Cell Styles on the
Options page, which you access from the Smart View ribbon.
se
ur
co
To analyze data with the ad hoc analysis tool:
ng
1. Connect to a data source.
i
in
tra
2. In the Smart View panel, right-click the data source and select Ad hoc Analysis.
er
The default Ad hoc grid is displayed.
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Changing the Point of View
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Changing the Point of View

ed
You can use the POV toolbar to change the POV settings for a grid.
ct
tri
es
If, in a worksheet, you want to save changes that you made to the POV settings, refresh
R
the worksheet before you save it.

-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Changing Members
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Changing Members
ed
To change members, you use the Member Selection dialog box.

ct
tri
es
To change members:
R
-
1. In Smart View, select the HFM Ad Hoc tab, and then Member Selection to display the
y r
ta
Member Selection dialog box.

ie
pr
2. In the Dimension drop-down list, select a dimension.

o
Pr
3. Optional: In the Filter drop-down list, select a filter.

e®
4. In the Members area, select a member, and click the right-arrow button.
cl
ra
O
The member is displayed in the Selection area.

5. Repeat steps 2, 3, and 4 to select members for other dimensions.
6. Click OK.

Drilling Down and Up Dimension Hierarchies
• You drill down or up by double-clicking the member or by
se
clicking the zoom commands on the ribbon.
ur
co
• Options determine the next level for drilling down.
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Drilling Down and Up Dimension Hierarchies

ed
You drill down or up by clicking the zoom commands on the HFM Ad Hoc ribbon. On the
ct
tri
Smart View ribbon, you can select Options and for Member Options, set options to
es
double-click a dimension member to expand to the next level, to all levels, or directly to
R
the bottom level.

-
ry
For the example on the slide, UnitedStates.California was expanded (Zoom In) to display
ta
ie
its children: California.1000, California.Plant1, California.WestSales, and

pr
California.WestAdmin.
o
Pr
e®
cl
ra
O

Pivoting Dimensions
Drag dimensions fr om the POV

toolbar to the rows or columns.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
Right-click and drag to pivot row or colum n
e
us
dimensions or to m ove them to the POV toolbar.

al
on
rs
pe
to
Pivoting Dimensions
ed
You can change the dimensions on the grid. On the POV toolbar, drag a dimension to a
ct
tri
row or column. The dimension is moved to the outer-most row or column on the opposite
es
axis. For the example on the slide, the Scenario dimension was dragged from the POV
R
toolbar to the columns.

-
y
r
You also can pivot a dimension from the rows to the columns or the POV toolbar, or from
ta
ie
the columns to the rows or the POV toolbar.

opr
The grid must have at least one dimension on rows and one dimension on columns.
Pr
Before you remove a dimension from a grid, you must first pivot the replacement
e®
dimension onto the grid.

cl
ra
O
To pivot dimensions:
• Right-click the dimension, and drag it to the destination.

Displaying Cell Text
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Displaying Cell Text

ed
If a worksheet cell contains cell text, you can view it on an ad hoc grid. Cells that contain
ct
tri
text are indicated by dark blue borders.

es
The example on the slide displays an explanation for the high shipping costs for
R
Quarter 2, for Connecticut.1100.

-
y
r
ta
ie
To display cell text:

opr
• Right-click the cell and, in the Smart View ribbon, select Cell Text.
Pr
e®
cl
ra
O

Adding Formulas and Preserving Formatting
se
ur
co
ng
i
Cell with formula
in
tra
er
rtn
pa
e®
Use the Preserve Format
cl
m enu comm and to preserve
ra
data cell formats.
O
an
in
e
us
al
on
rs
pe
to
Adding Formulas and Preserving Formatting

ed
You can add Excel formulas and formatting to data cells. For the example on the slide,
ct
tri
you can add a formula to the Budget column to calculate the Budget column values
es
based on the values of the Actual column plus a percentage.

R
-
You can also format data cells to display a currency symbol or to display negative
yr
numbers in red. When you submit data, the values calculated by formulas are saved to
ta
ie
the database.
opr
Formulas that you add to data cells are automatically preserved, even when you perform
Pr
the following actions:

e®
cl
• Refresh the ad hoc grid

ra
O
• Zoom in or zoom out (Referential formulas are updated with their new relative
positions.)
• Apply the Keep Only or Remove Only function

Formulas are not preserved if you change the grid by pivoting data (for example,
selecting Pivot to POV or Pivot to Column) or by clearing the grid.
Rows and columns that you insert in the grid are preserved. For example, you insert a
column for rates and enter salary rates. In the Salaries row, to calculate salary increases,
you use an Excel formula to reference the values in the rates column.
se
If you apply formatting to cells other than data cells (for example, row and column
ur
heading cells), the formatting is not preserved.
co
ng
To add formulas:
i
in
tra
1. In Smart View, select a cell for which you want to add a formula.
er
rtn
2. In the Formula bar, enter a formula.
pa
3. Press Enter on the keyboard.
e®
4. On the HFM Ad Hoc tab, from the Calculate list, select Calculate.
cl
ra
The cell is updated with the new value.
O
an
in
To preser ve formatting:
e
us
1. Right-click the cells.

al
on
2. On the Smart View menu, select Preserve Format.

rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Free-Form Worksheets
You can create ad hoc queries quickly by typing member labels
se
on the worksheet.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Free-Form Worksheets

ed
Free-form worksheets enable you to quickly create an ad hoc analysis by typing member
ct
labels on the worksheet. When you construct an analysis by entering names directly on
tri
es
a worksheet, Smart View queries the connected data source, interprets the member
R
names that you entered, and creates a default view that is based on the location of the
-
labels.
y
r
ta
The layout for free-form entry requires you to type the member labels for the row
ie
pr
dimensions to the left and one row below the member labels for the column dimensions.
o
When you select Refresh from the HFM Ad Hoc ribbon, the data is retrieved from the
Pr
database.
e®
cl
Guidelines:
ra
O
• You cannot place members from the same dimension on both the rows and the
columns.
• You must precede all member names that consist of numbers with a single quotation
mark.
• You can apply cell styles in free-form mode.

Drilling Through to ERP Integrator and FDM
ERP Systems EPM Applications
se
ur
General Ledgers FDM
co
E-Business
S uite
ng
E-Business Data .
Data
i
Data
in
Suite
tra
ERP
er
Integrator
rtn
Drill
pa
Drill Drill
PeopleSoft through
through thro ugh
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Drilling Through to ERP Integrator and FDM

ed
When you load data into Financial Management from an ERP System (Oracle E-
ct
tri
Business Suite General Ledger or PeopleSoft General Ledger) with ERP Integrator or
es
FDM, and access the data in Smart View, you can drill through the Financial
R
Management application to view detailed data in ERP Integrator or FDM.

-
r y
When you drill through to ERP Integrator or FDM, a landing page displays general ledger
ta
ie
accounts and the hyperlinked balances that were used to populate the cells in the
pr
Financial Management application. When you click a hyperlinked data value, you can
o
Pr
drill through to the ERP source system and view the associated journal entries for the
e®
selected general ledger account.

cl
Before you can drill through from the Financial Management application, you must first
ra
O
register it in ERP Integrator and create a drill-through region. In Smart View, you can
apply custom formatting to identify drillable cells.

For more information about configuring Financial Management in ERP Integrator and
FDM, see Oracle® Hyperion Financial Data Quality Management ERP Integration
Adaptor For Oracle Applications, 11.1.2.0 and Oracle® Hyperion Financial Data Quality
Management, Fusion Edition 11.1.2 Administrator’s Guide.
To drill through to ERP Integrator:
se
ur
1. In Smart View, select a cell that is configured for drill-through.
co
2. On the HFM Ad Hoc ribbon, select Drill -Through to display a list of reports that are
ng
associated with the cell.
i
in
tra
3. Select Drill -Through to ERPI and click Launch.
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Smart Slices
A smart slice is a reusable view of a data source that contains a
se
restricted set of dimension members.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Smart Slices

ed
ct
You can use smart slices to perform the following tasks:

tri
es
• Filter on data sources

R
• Define default POVs on data sources

-
y
r
ta
• Set a default query for a data source

ie
pr
• Set smart slice options (for example, suppress rows and decimal precision)
o
Pr
Your organization can have as many smart slices as it needs to accommodate the data
e®
requirements of your users. For example, you can create smart slices for geographical
cl
regions or product lines or any combination of such dimensions.

ra
O
Smart slices are stored in Provider Services, and users can access the smart slices only
for the data sources to which they have access in Financial Management. For example, if
users have access to the Travel Expenses data form, they can access the smart slices
defined for that data source.

To create smart slices:

1. Connect to a data source.
2. Right-click the data source, and select Create new Smart Slice.
The POV New SmartSlice-Design sheet is displayed.
se
3. Define column, row, and POV members.
ur
4. Optional: Click Options to set smart slice preferences.
co
ng
5. Click Done.
i
in
tra
The Member Selection dialog box is displayed.
er
6. Optional: Select the default POV that you want to display when you open the smart
rtn
slice.
pa
7. Click OK.
e®
cl
The Smart View panel is displayed.
ra
O
8. In the “Enter new name” text box, enter a name.
9. Click OK.
an
in
e
us
The smart slice is listed in the Smart View panel, under the name
of the data source.
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
pr
o
Pr
e®
cl
ra
O

Designing Reports in Report Designer
Report Designer enables you to perform the following actions:
se
• Create reports with smart slices
ur
co
• Create queries and insert them into Excel, Word, and
ng
PowerPoint
i
in
tra
• Use components from multiple sources to create
er
customizable reports
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Designing Reports in Report Designer

ed
In Report Designer, you design reports based on smart slices. The reports can be
ct
tri
displayed as function grids, tables, or charts. You cannot modify queries inserted from a
es
smart slice into Report Designer, but you can use a slider to change their POVs. You can
R
use components from multiple sources to create custom reports.

-
y
r
ta
ie
NOTE: Function grids are supported for Excel, Word, and PowerPoint. Tables,
pr
charts, and sliders are supported for Excel and PowerPoint.

o
Pr
e®
cl
ra
To design reports in report designer:

O
1. Right-click a smart slice, and select Insert Smart Slice into report.
The Report Designer interface is displayed.

2. In the Query View list, select Query View.

3. In the Insert list, select Function Grid, Table, Chart, POV, or Slider.
4. On the Smart View ribbon, click Refresh.
The report is displayed on the worksheet.
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Cascading Reports
• You can create separate reports for members of one
se
dimension.
ur
co
• You can use a smart slice or an ad hoc grid.
ngi
in
Entity
tra
er
Co nnecticut
rtn
pa
California
e®
Texas
cl
ra
O
Florida
POV an
in
e
Cascade Report Across the Wor kbook

us
al
on
rs
pe
to
Creating Cascading Reports

ed
You can create separate reports for members of a POV dimension based on the Report
ct
tri
Designer query.
es
R
For the example on the slide, you can create separate reports for Connecticut, California,
-
Texas, and Florida, which are members of the Entity dimension.

ry
ta
You can create reports from a smart slice or ad hoc grid, and cascade these reports
ie
across Excel worksheets.

o pr
Pr
To create cascading reports with smart slices:

e®
cl
1. In Report Designer, select a query.

ra
O
2. Select Cascade Report Across the Workbook.

3. Select the POV dimension for the reports.

4. Select members for which you want to create reports.

5. Click OK to begin cascading.
An Excel workbook is created for each report, and the original
report is retained intact. Each worksheet is named for the
dimension and member of the report that the worksheet contains.
se
ur
To create cascading reports with ad hoc grids:
co
ng
1. In Excel, create an ad hoc grid.
i
in
2. On the HFM Ad Hoc ribbon, select Cascade.
tra
er
rtn
• Select Same Workbook to create the cascading reports in the same worksheet.
pa
e®
• Select New Workbook to create the cascading reports in a new workbook.
cl
ra
O
4. Select the POV dimension for the reports.
an
in
5. Select all members for which you want to create reports.
e
us
6. Click OK to begin cascading.

al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Viewing Calculation and Process Management

Status in Smart View
• These features work the same way in Smart View as they
se
do in Financial Management.
ur
co
• The same security rules apply in Smart View.
ng
• When you are using these features in Smart View, use the
i
in
Refresh option to ensure that you look at the latest data.
tra
er
rtn
pa
e®
USD
cl
ra
O
an
GBP in
e
Calculate data Translate data Consolidate data

us
al
on
rs
pe
to
Viewing Calculation and Process Management Status in

ed
Smart View
ct
tri
Users who have the proper access can calculate and translate data. Users can also view
es
R
and execute consolidations, and view calculation or process management status.

-
y r
To view calculation and process management status:

ta
ie
pr
1. On the Smart View ribbon, select Options.

o
Pr

e®
2. On the left side of the page, select Data Options.

cl
ra
3. Under Cell Status, perform one of the following actions:

O
• Select Calculation Status.

• Select Process Management.
4. Click OK.

Submitting Data
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an Submit data
in
to Financial Management
e
us
al
on
rs
pe
to
Submitting Data
ed
ct
After data has been calculated, translated, or consolidated, you can submit the data to
tri
ensure that the data source uses the latest information from the worksheet.
es
R
You must have the Load Excel Data security role to submit data to Financial
-
Management.
y
r
ta
ie
To submit data:
pr
o
Pr
• On the HFM Ad Hoc ribbon, select Submit Data.

e®
cl
ra
O

Working with Data Forms in Smart View
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Working with Data Forms in Smart View

ed
ct
From the Smart View panel, you can open data forms that were created in the Financial
tri
Management Web client.

es
R
Add Line Item Detail functionality is not supported in data forms that are opened in Smart
-
View.
yr
ta
When you open a data form in Smart View, the point of view defined for the form is
ie
pr
displayed. You can select dimension members for the dimensions that are designated as
o
Selectable in the data form definition.

Pr
e®
You can add members on data forms that are opened in Smart View. A red border is
cl
displayed around cells to which you can add members.

ra
O

To add members to data forms:

1. In the Smart View panel, right-click a form, and select Open Form.
se
• Select the POV members for the dimensions, and click OK.
ur
• Click Cancel.
co
ng
3. Select the cell configured to add members and, in the HFM ribbon, select Add
i
in
Member.
tra
4. From the member selector, select the members for which you want to enter data.
er
rtn
5. Click OK.
pa
e®
You can also open linked forms from a form opened in Smart View. For rows that contain
links to forms, the cell text is displayed in red.
cl
ra
O
To open linked forms:
an
in
1. In the Smart View panel, right-click a form and select Open Form.
e
us

al
on

rs
pe
• Select the POV members for the dimensions, and click OK.
to
• Click Cancel.
ed
ct
3. Select a row that contains linked forms, and right-click in the row.
tri
es
4. Select Smart View, and select the form name.

R
A new form is displayed in a separate browser window.

-
y
r
5. Perform the same range of functions as you would in the Web client, such as
ta
ie
calculating data, adding cell text, and submitting data.

opr
6. Click Close.
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Navigate Smart View
er
• Connect to data sources
rtn
pa
• View and analyze data with the ad hoc analysis tool
e®
• Add smart slices and cascading reports
cl
ra
• Submit data
O
• Work with data forms in Smart View an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 2 1
Managing Intercompany Transactions 21
se
ur
co
ngi
Objectives
in
tra
er
rtn
• Describe the Intercompany Transactions module
pa
• Open periods for intercompany transactions
e®
cl
• Create intercompany transactions
ra
O
• Match intercompany transactions
• Post intercompany transactions an
in
e
• Create intercompany reports

us
al
• Lock entities
on
rs
• Close intercompany periods

pe
• Monitor intercompany transactions

to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 21 Managing Intercompany Transactions
Intercompany Transactions Module
Use the intercompany transactions module to enter or load
se
intercompany transactions at an invoice or transaction level.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to

ed
ct
Financial Management enables you to track and reconcile intercompany transaction

tri
details across accounts and custom dimensions.

es
R
The Intercompany Transactions module provides an efficient way to identify, report, and
-
reconcile intercompany account differences. With the ability to view the details of
y r
transactions at any time, you can reconcile intercompany account differences frequently,
ta
ie
and thus minimize the impact of such differences on the closing cycle. You can also
pr
analyze differences due to real errors in transaction currency or differences due to

o
Pr
exchange rates.
e®
cl
ra
O

Business Process for the

IC = Intercom pany
se
ur
co
Create IC Match IC
Open IC period
tr ansaction transaction
i ng
in
tra
er
rtn
Generate Drill through
Post IC
pa
matching from account
transaction
reports balance
e®
cl
ra
O
Lock entities Close IC period an
in
e
us
al
on
rs
pe
to
Business Process for the Intercompany Transactions Module

ed
With the Intercompany Transactions module, you can perform the following business
ct
tri
processes:
es
R
• Open periods for intercompany transactions.

-
• Create intercompany transaction details at the invoice level.

y
r
ta
• Match transactions at the invoice level, in the transaction currency, and in the
ie
pr
reporting or parent currency.

o
Pr
• Post transactions.
e®
• Create intercompany matching reports.

cl
ra
• Drill through an account balance to transactional details from intercompany matching

O
reports, data grids, or data forms.

• Lock entities and close periods to prevent unauthorized input.

Setup Considerations for Intercompany

Transactions
se
The following needs to be considered as part of the setup for
ur
the Intercompany Transactions module:
co
ng
• IC periods must be open.
i
in
• Intercompany transaction rules must be defined in the
tra
rules file and loaded into the application (error message
er
results if rules are not defined).
rtn
pa
• The scaling factor affects the display of the transaction
e®
amount.
cl
• Matching tolerances need to be determined.
ra
O
• Reason codes need to be defined.
• Currency conversion rates must be entered. an
in
e
us
al
on
rs
pe
to
Setup Considerations for Intercompany Transactions

ed
Before you can enter intercompany transactions, you must open intercompany periods,
ct
tri
define and load intercompany transaction rules into the application, determine matching
es
tolerances, define reason codes, and enter currency conversion rates. The
R
HS.SupportsTran function, when used with members of the Scenario and Account
-
dimensions (and, optionally, with members of the custom dimensions), creates a valid
y r
ta
cell intersection for an intercompany transaction. You need a rule for every valid cell
ie
intersection.
pr
o
Pr
e®
cl
ra
O

Opening Intercompany Periods
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
Matching tolerances are set
when periods are opened.
in
e
us
al
on
rs
pe
to
Opening Intercompany Periods

ed
ct
You must open the intercompany period before you can enter intercompany transactions.
tri
You can specify matching tolerances for the period. You can input separate matching
es
tolerance amounts for transaction ID, account, and manual tolerance. For transaction ID
R
tolerance, you can also specify a percentage. The percentage is applied to the smaller of
-
y
the entity or partner transaction.

r
ta
ie
You can also select the option for matching and validation:
opr
• If you select the Match/Validate Before Post option, you must match transactions or
Pr
assign a reason code before they can be posted. Before you can close a period or
e®
lock an entity, you must post all matched transactions or mismatched transactions
cl
ra
with reason codes.

O
• If you select the Restrict option, you must match transactions before you can post
them, but you can close periods or lock entities that have unposted transactions.

To open intercompany periods:

1. In the view pane, select Tasks, then IC Transaction Tasks, and then Manage IC Periods.
The Manage IC Periods page is displayed.
2. Select a scenario and year.
se
3. In the Periods column, select a period.
ur
4. Specify a matching tolerance for the period.
co
ng
5. Select an option for matching and validation.
i
in
tra
6. Click Open Period.
er
The current status of the period changes to Opened.
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Creating Intercompany Transactions
Invoices can be loaded from a file or entered manually.
se
ur
co
ngi
in
tra
er
rtn
pa
OR
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating Intercompany Transactions

ed
ct
In Financial Management, you can create intercompany transactions as follows:

tri
es
• Load intercompany transactions from ASCII files.

R
• Manually enter transactions from the Process IC Transactions page.

-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Loading Intercompany Transactions Files
You can select multiple external files in one load process and
se
select whether to merge or replace the existing transactions.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Loading Intercompany Transactions Files

ed
The Load IC Transactions task enables you to load transaction details from external
ct
tri
ASCII files.
es
R
To load IC transactions:
-
ry
ta
1. In the view pane, select Load Tasks, and then Load IC Transactions.
ie
pr
2. Select the delimiter character: @ # $ % ^ & | : ; ? \

o
Pr
3. Select a load method: Merge or Replace.

e®
4. Click Browse, and select a file.

cl
ra
O
5. Click Open.
6. Click Load.

About Process IC Transactions
se
ur
co
ng
Alert Filter Report New Edit Delete Match Post Unpost
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
About Process IC Transactions

ed
The Process IC Transactions page is the main page from which you perform most
ct
tri
intercompany transaction processes. You use the toolbar on the page to perform the
es
following tasks:
R
-
• Unpost and post intercompany transactions

yr
ta
• Match and unmatch intercompany transactions

ie
pr
• Delete intercompany transactions

o
Pr
• Edit intercompany transactions

e®
cl

ra
O
• Report on intercompany transactions

• Filter intercompany transactions
• View intercompany transactions

Creating IC Transactions
from Process IC Transactions
se
New
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Creating IC Transactions from Process IC Transactions

ed
You can manually enter intercompany transactions on the Process IC Transactions page.
ct
tri
es
To create IC transactions from Process IC transactions:

R
-
1. In the view pane, select Tasks, then IC Transaction Tasks, and then Process IC
y
r
ta
Transactions.
ie
pr
The Process IC Transactions page is displayed.

o
Pr
2. On the toolbar, click New.

e®
The New Intercompany Transaction page is displayed.

cl
ra
3. Optional: Select a category, year, and period.

O
4. In the Transaction ID text box, enter a transaction ID.

5. Optional: Enter a transaction Sub ID and reference ID.

6. In the Transaction Date text box, enter the date of the transaction.
7. Click Pick Members.
The Member Selector page is displayed.
8. Select the members for the transaction.
se
9. Click OK.
ur
co
10. In the Transaction Amount text box, perform the following actions:
ng
• Enter the transaction amount.
i
in
tra
• Select a currency.
er
11. Enter the conversion rule and operator.
rtn
pa
12. Click Save.
e®
13. Click Close.
cl
ra
The transaction is displayed on the Process IC Transactions
O
page.
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Matching Intercompany Transactions
Question: Why match intercompany transactions?
se
Answer: Matching helps reduce the gap that can exist between
ur
co
intercompany account balances.
ngi
in
Entity A Entity B
tra
er
rtn
Accts. Receivable Inter company Accts. Payable Intercompany
pa
e®
500 500
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Matching Intercompany Transactions

ed
ct
Before posting intercompany transactions to a Financial Management intercompany

tri
account, you can perform a matching process to ensure that both the entity and its
es
partner entered the transaction. For example, for an intercompany sales transaction from
R
Entity A to Entity B, an Accts. Receivable entry in Entity A should have a corresponding

-
y
Accts. Payable entry in Entity B.

r
ta
ie
If your administrator set up the period to require matching before posting, you must
pr
match the transactions before you can post them.

o
Pr
e®
cl
ra
O

Intercompany Transaction Matching Methods
• Automatic matching by transaction ID, reference ID, or
se
account with or without tolerance amount
ur
co
• Manual matching with or without tolerance amount
ngi
in
tra
er
Autom atic Manual with toler ance Manual without toler ance
rtn
pa
e®
cl
ra
O
< 10 USD an 1: 1
in
e
us
al
on
rs
pe
to
Intercompany Transaction Matching Methods

ed
ct
You can match transactions by several methods. You can allow the system to
tri
automatically match transactions based on criteria that you specify. If the transactions
es
are not matched by the automatic matching process, you can also manually match
R
specific transactions, with tolerance or without a tolerance.

-
y
r
ta
To automatically match intercompany transactions:

ie
o pr
1. Navigate to the Process IC Transactions page.

Pr
e®

cl
• Select the IC transactions that you want to match.

ra
O
• Select the box next to the Status column to select all transactions.

3. On the toolbar, click Match, and select Auto Match.

The AutoMatch page is displayed.
4. Optional: If you use an auto-matching template, select a template from the Template
list.
5. On the POV, select a scenario, year, and base period.
se
ur
6. Select an Entity and Partner dimension member.
co
7. Optional: To auto-match by currency, perform the following actions:
ng
i
in
• Select Include During Processing.
tra
er
• In the “Only if Transaction Currency” list, select a currency.
rtn
pa
e®
• Select Match by ID, select Transaction ID or Reference ID from the Match by ID list, and
cl
enter an ID in the text field.
ra
O
• Select Match by Account, click Add and select the account dimension member, and
an
then click Add and select the matching account dimension member.
in
9. Click Match.
e
us
10. Click Close.

al
on
On the Process IC Transactions page, the selected transactions

rs
display a green square over a square icon, indicating that the

pe
transactions are matched.

to
ed
To manually match intercompany transactions:

ct
tri
es

R
2. Select the IC transactions that you want to match.

-
r y
3. On the toolbar, click Match, and select Manual Match.

ta
ie
pr

o
display a green square over a square icon, indicating that the

Pr
transactions are matched.

e®
cl
ra
O

Posting Intercompany Transactions
• Intercompany transactions must be posted in order to be
se
included in an account balance.
ur
co
• After a transaction is posted, no changes can be made to
ng
it.
i
in
tra
Accts. Receivable - Intercompany
er
rtn
Inv 001 100
pa
Inv 002 300
----
e®
400
cl
Inv 003 500
ra
----
O
900
an
in
500 USD
e
us
al
on
rs
pe
to
Posting Intercompany Transactions

ed
ct
When you create or load an intercompany transaction, by default it has a status of

tri
Unposted and no amount is shown in the account balance. For example, you may input
es
an intercompany transaction for Entity A with Entity B for the amount of USD $100.
R
However, the amount was not recorded in the ICRec account. The ICRec account
-
y
balance remains at zero until the transaction is posted.

r
ta
ie
When you post the selected intercompany transactions to the account, the system
pr
updates the status of the transactions to Posted, and the total transaction amount is
o
Pr
reflected in the account balance.

e®
After a transaction is posted, you cannot change it. If changes are needed to a posted
cl
ra
transaction, you must unpost it, make the changes, and then rematch and repost the
O
transaction.

To post intercompany transactions:

• Select the IC transactions that you want to post.
se
• Select the box next to the Status column to select all transactions.
ur
co
3. On the toolbar, click Post, and select Post Selected or Post All.
ng
4. Confirm that the process is completed successfully.
i
in
tra
er
display a green triangle, indicating that the transactions are
rtn
posted.
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Generating Matching Reports
Generate matching reports by:
se
• Transaction ID
ur
co
• Account Transaction ID
ng
• Transaction
i
in
tra
er
rtn
pa
Accts. Receivable Accts. Payable
- Intercompany - Intercom pany
e®
500 500
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Generating Matching Reports

ed
ct
After loading transactions into the application and viewing the transactions on the
tri
Process Transactions page or in the transaction detail report, you may want to run a
es
matching report to check potential matching transactions and mismatched transactions.

R
You can run a matching report by account, transaction ID, or reference ID.
-
ry
You can create a matching report by the following methods:

ta
ie
pr
• Using the Report Wizard

o
Pr
• Writing a script in a text file

e®
cl
To generate matching reports:

ra
O

2. On the toolbar, click Report, and perform one of the following actions:

• Select By Transaction ID. On the General tab, enter or select the name, description,
style sheet, security class, point of view, entity, partner, matching currency, and
transaction or reference ID. On the Display tab, select the items that you want to
display on the report.
• Select By Account. On the General tab, enter or select the name, description, style
sheet, security class, point of view, entity, partner, matching currency, and matched
se
and posted statuses. On the Accounts tab, select the accounts and matching
ur
co
accounts that you want to display on the report. On the Display tab, select the
items that you want to display on the report.
ng
i
in
• Select Transaction. On the Column Filter tab, select the column filters. On the Row
tra
Filter tab, select the row filters.
er
rtn
pa
• Click Print/Preview to print or preview the report.
e®
cl
• Click Save Remote to save the report remotely.
ra
O
• Click Save Local to save the report locally.
• Click Close to close the report dialog box. an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

Drill-Through Reports
se
ur
co
ngi
in
tra
er
rtn
pa
e®
View supporting transaction
cl
details in the matching reports.
ra
O
an
in
e
us
al
on
rs
pe
to
Drill-Through Reports
ed
ct
When you run an intercompany matching report at the account balance level, a link is
tri
displayed on the report if the administrator set up the report to display intercompany
es
transaction detail for the matching group. When you click the link, you can view the
R
matching report at the transaction detail level.

-
y
r
You can only view intercompany transactions in the report; you cannot change the
ta
ie
transactions in the report.

opr
Pr
e®
cl
ra
O

Locking Entities
After intercompany processing is complete, lock entities to
se
ensure that no further changes are made.
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Locking Entities
ed
ct
You can apply a lock to an entity for a scenario, year, and period to prevent future
tri
changes to intercompany transactions for the entity. If the Match/Validate Before Post
es
option is selected for the period, you must post all matched transactions and all
R
mismatched transactions with a reason code before you can lock the entity.
-
y
r
When an entity is locked, you cannot enter new intercompany transactions. You also
ta
ie
cannot delete or change existing transactions. You cannot post or unpost transactions to
pr
a locked entity, or update the match status of a transaction that involves a locked entity.
o
Pr
Therefore, even if the partner entity is not locked, the partner cannot match transactions
e®
because the match status cannot be updated for the entity.

cl
ra
O

To lock entities:
1. In the view pane, select Tasks, then IC Transaction Tasks, and then Lock/Unlock IC
Entities.
The Lock and Unlock Entities page is displayed.
2. Select the scenario, year, and period.
se
ur
3. Select the entity that you want to lock.
co
4. Click Lock.
ng
i
in
The entity displays a status of Locked.
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
r y
ta
ie
opr
Pr
e®
cl
ra
O

Closing Intercompany Periods
• When a period is closed, no intercompany transactions
se
can be entered.
ur
co
• You can still view transactions and run reports.
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
Co pyri ght © 2011, Ora cle an d/or its a ffil ia te s. Al l righ ts reserved.
rs
pe
to
Closing Intercompany Periods

ed
ct
After processing intercompany transactions, you can close the period to prevent
tri
modifications. If you select Match/Validate Before Post, you must post all matched
es
transactions and all mismatched transactions with a reason code. Although the period is
R
locked for future transactions, you can view transactions and run reports for the period.
-
y
r
ta
ie
To close intercompany periods:

o pr
1. In the view pane, select Tasks, then IC Transaction Tasks, and then Manage IC Periods.
Pr
e®
The Manage IC Periods page is displayed.

cl
2. Select the scenario and year.

ra
O
3. Select the period that you want to close.

4. Click Close Period.
The period displays a current status of Closed.

Monitoring Intercompany Entity Status
Summary of Started and
se
Not Started Transactions.
ur
co
Filter by status.
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
Cl ick an enti ty to vi ew detail .

al
on
rs
pe
to
Monitoring Intercompany Entity Status

ed
ct
The Monitor Intercompany Transactions task provides a status overview for your
tri
intercompany entities. You can filter the list of entities by any combination of Started, Not
es
Started, Not Lockable, Lockable, and Locked.

R
-
• An entity has a status of Not Started if it has no intercompany transaction for the
y
r
scenario, year, and period in the point of view.

ta
ie
pr
• An entity has a status of Started if has at least one intercompany transaction for the
o
scenario, year, and period in the point of view.

Pr
e®
• An entity has a status of Not Lockable if you selected Match/Validate Before Post for
cl
the period, but you did not post matched transactions or mismatched transactions
ra
with a reason code.

O
You can click an entity in the list to view a detail window with additional details for the
entity. The detail window displays the total number of posted and unposted transactions
for the entity, categorized by matching status.

To monitor intercompany transactions:

1. In the view pane, select Tasks, then IC Transaction Tasks, and then Monitor IC
Transactions.
The Monitor IC Periods page is displayed.
2. Select a category, year, and period.
se
ur
3. In the Entity text box, enter a name or click Browse to search for an entity.
co
i ng
in
NOTE: If you leave the Entity text box blank, the system returns all entities
tra
in the list.
er
rtn
pa
4. Select any combination of the following options to filter the transactions:
e®
• Not Started
cl
ra
• Started
O
• Not Lockable an
in
• Lockable
e
us
• Locked
al
on
5. Click Update.
rs
pe
The filtered transactions are displayed.

to
ed
ct
tri
es
R
-
y r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• Describe the Intercompany Transactions module
er
• Open periods for intercompany transactions
rtn
pa
e®
• Match intercompany transactions
cl
ra
• Post intercompany transactions
O
• Create intercompany reports an
in
e
• Lock entities
us
• Close intercompany periods

al
on
• Monitor intercompany transactions

rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

L E S S O N 2 2
Enterprise Performance Management

Architect 22
se
ur
co
ng
i
Objectives
in
tra
er
rtn
• List Performance Management Architect features
pa
• Describe Performance Management Architect modules
e®
cl
• Describe Performance Management Architect architecture
ra
O
• Access Performance Management Architect
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O
Lesson 22 Enterprise Performance Management Architect
Performance Management Architect Features

• Design applications graphically, within one environment
• Create subject-specific applications that us e existing LCM artifac ts
se
• Configure dimensions and define properties
ur
• Create filters to select s pec ified member s of a dimension
co
• Duplicate applications for testing or what-if analys is
ng
• Upgrade applications from previous releases to place them in the
i
in
Dimension Library
tra
• Visually link and manage applications
er
• Use dimensions and attributes across multiple applications
rtn
• Graphically manage data flows
pa
• Perform impact analysis-graphically view and model relations hips across
e®
applications
cl
• Handle and evaluate the impact of exceptions and changes to all models
ra
• Eliminate manual dimensional and data reconciliation between
O
applications
• an
Integrate applic ations with Enterprise Resource Planning (ERP)
in
metadata and data sources us ing ERP integrator
e
us
al
on
Co pyri ght © 2 011, Ora cle an d/or its a ffil ia tes. Al l righ ts rese rved.
rs
pe
to
Performance Management Architect Features

ed
ct
Oracle Hyperion EPM Architect, Fusion Edition is a feature of Oracle's Hyperion®

tri
Foundation Services and is integrated with Oracle Hyperion Financial Management,

es
Fusion Edition, Oracle Hyperion Planning, Fusion Edition, Oracle Essbase, and Oracle
R
Hyperion Profitability and Cost Management, Fusion Edition. Performance Management

-
y
Architect enables administrators to manage, create, and deploy Hyperion applications

r
ta
within one interface.

ie
opr
Pr
Creation and Deployment

e®
• Create applications by dragging and dropping dimensions to the application

cl
ra
• Design applications graphically, within one environment

O
• Create subject-specific applications that use existing artifacts

• Configure dimensions and define properties from predefined, sample libraries

• Create filters to select specified members of a dimension. For example, select the
Balance Sheet accounts of the Account dimension. This enables you to have one
dimension to maintain but not use the full dimension in all applications.
• Duplicate applications for testing or what-if analyses
• Transform applications administered in Classic application administration to the
se
Dimension Library and Application Library. This ensures that you are ready to get
ur
started with the functionality within Performance Management Architect.
co
ng
i
Calculating Business Rules for Applications
in
tra
Hyperion Calculation Manager enables you to create, validate, and deploy sophisticated
er
calculations to solve Financial Management and Planning business problems. You can
rtn
use Calculation Manager to create any of these calculations:
pa
• Allocating costs among entities
e®
cl
• Performing revenue modeling
ra
O
• Performing expense modeling
• Preparing a balance sheet an
in
e
• Calculating cash flow

us
al
• Calculating currency translation adjustments

on
rs
• Calculating group and minority interest

pe
• Calculating deferred taxes

to
ed
ct
Management
tri
es
• Visually link and manage applications

R
• Use dimensions and attributes across multiple applications. (For example, you can
-
y
create one Account dimension and use it in multiple applications.) Performance

r
ta
Management Architect leverages existing applications and dimensionality to spin off

ie
pr
other applications with previously constructed dimensions.

o
Pr
• Graphically manage data flows

e®
• Perform impact analysis—graphically view and model relationships across

cl
ra
applications
O
• Handle and evaluate the impact of exceptions and changes to all models
• Eliminate manual dimensional and data reconciliation between applications

Performance Management Architect Modules
se
ur
co
ing
in
tra
Dimension Lib rary Ap plicat ion L ib rary Calculation Manag er
er
rtn
pa
e®
cl
ra
O
an
Data Synchronizat ion Tran sform Classic to EPMA
in Job Con sole
e
us
al
on
rs
pe
to
Performance Management Architect Modules

ed
ct
tri
es
R
-
y r
ta
ie
pr
o
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Dimension Library
ed
A centralized location to manage dimensions and dimension properties. You can use the
ct
tri
Dimension Library to:

es
R
• Create dimension import profiles—enabling dimension updates from flat files and
-
relational database interface tables

yr
ta
• Add, delete, and modify dimension members in the Shared Library or directly in
ie
applications
opr
Pr
Performance Management Architect applications can contain dimensions of two different

e®
states: shared and local.

cl
ra
O

• Shared Dimensions are created in an area of the Dimension Library called the
Shared Library. These dimensions are available to all applications and can be
individually linked to one or more applications when included in each application as a
shared dimension. Changes made to the dimension in the Shared Library are
automatically inherited to every application sharing that dimension. All types of
modifications can be made to the dimension within the Shared Library but only
se
certain types of changes can be made to the shared dimension within the application.
ur
co
Once a dimension has been included in an application as a shared dimension,
changes can be applied to the shared dimension within the application to handle
ng
exceptions that may only be relevant to that application.
i
in
tra
• Local Dimensions originate within a single application and can be created directly
er
within the application or as a copy of a dimension from the Shared Library or another
rtn
dimension in the application. Local dimensions are separate dimensions and do not
pa
inherit any changes made to the dimension in the Shared Library.
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Application Library
ed
A summary of applications that have been created and/or deployed to Financial

ct
tri
Management, Planning, Profitability and Cost Management, Essbase Aggregate Storage

es
Option (ASO), or Essbase Block Storage Option (BSO). Applications contain dimensions
R
and dimension attributes that are designed to meet specific requirements for Financial
-
Management, Planning, Profitability and Cost Management, and Essbase (ASO) and
y
r
ta
(BSO) needs. You can use the Application Library to:

ie
pr
• Create Financial Management, Planning, Profitability and Cost Management,

o
Pr
Essbase (ASO), or Essbase (BSO) applications based on Financial Management,

e®
Planning, and Profitability and Cost Management applications

cl
• Manage applications in one centralized location

ra
O
• View the data flow between applications

• Migrate applications to different servers

• Deploy applications to Financial Management, Planning, Profitability and Cost

Management, Essbase (ASO), or Essbase (BSO)
You can create Planning applications manually or using the Application Creation Wizard.
Manual Workflow
Using the manual method, you can create blank applications and define the application
se
ur
in seven steps:
co
1. In the application wizard select an application type, then select Create Blank
ng
Application.
i
in
tra
2. Drag dimensions (or dimension hierarchy subsets) from the Shared Library to the
er
application or create local dimensions in the application.
rtn
pa
3. Activate all dimension associations.
e®
4. Modify dimension, application, and member properties (only if the application
cl
properties differ from the Shared Library properties).
ra
O
5. Validate the application.
an
6. Deploy the application to the Hyperion product environment.
in
e
us
7. Define access permissions.

al
on
Application Wizard Workflow

rs
The application wizard makes it easy to create applications and guides you through the
pe
following screens:
to
ed
• Application Type—enables you to enter the name, select the type, and enter a
ct
description. Depending on the application type, additional options display.

tri
es
• Dimension Selection—enables you to select or create dimensions.

R
-
• Application Settings—enables you to associate dimensions, set the dimension alias,

y
r
and modify other application properties.

ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Calculation Manager
ed
Enables you to create, validate, and deploy business rules and business rule sets. There
ct
tri
are three types of objects that can be calculated in Calculation Manager:

es
R
• Components, which are objects that comprise business rules and can contain
-
formulas, scripts, conditions, ranges, fixed loops, and allocations

y
r
ta
• Rules, which are objects that contain groups of components that perform calculations
ie
pr
• Rule Sets, which are objects that contain two or more rules that are calculated
o
Pr
simultaneously or sequentially
e®
If you are using a Financial Management, Planning, or Essbase block storage

cl
ra
application, you can include Calculation Manager system templates in business rules.
O
For example, you can use a system template that copies data from one location to
another. You can also create custom defined templates to perform calculations that solve
problems unique to your business.

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Data Synchronization
ed
Enables data synchronization between or within Hyperion applications. You can use the
ct
tri
Data Synchronizer to:

es
R
• Create data synchronizations between Financial Management, Planning, Profitability

-
and Cost Management, Essbase (ASO), and Essbase (BSO) as destinations, and
ry
the following sources:

ta
ie
- Financial Management
opr
Pr
- Planning
e®
- Profitability and Cost Management

cl
ra
- Essbase ASO
O
- Essbase BSO
- External source (flat file)

- Interface table
For example, an administrator can synchronize data between two Financial
Management applications; two Planning applications, and between one Financial
Management and a Planning application.
• Create data mappings for reuse
se
• Create flat file and interface table mappings to import data into Hyperion applications
ur
co
Performance Management Architect enables you to synchronize data in three locations:
ng
i
• Application Library
in
tra
• Data Flow
er
rtn
• Data Synchronizer
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
y
r
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Transform Classic to EPM Architect

ed
Enables transformations of applications managed in Classic Financial Management and

ct
tri
Planning releases to Performance Management Architect.

es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Library Job Console

ed
Provides a summary, including status, of Dimension Library and application processes,

ct
tri
including imports, deployments, and data synchronizations.

es
R
You can view an application's deployment history to troubleshoot problems with

-
deployment. You must have specific roles assigned in Shared Services to view
yr
application deployment history:

ta
ie
• For applications that have not been deployed, you must have Performance
opr
Management Architect Application Creator rights to view the deployment history.

Pr
e®
• For deployed applications, you must have Shared Services Application Administrator
cl
rights to view the deployment history.

ra
O
The Job Console view is filtered by the source application and these job types: Export,
Transform Classic to EPM Architect, Application Migration, and Application Deployment.
(Application Deployment jobs include deployment, redeployment, and deploy business
rules only.)

The Job Console supports the following job types:
Job Type Job associated with...

Dimension Import importing dimensions into the Dimension Library
Application Deployment deploying a Consolidation, Planning, Analytic Services, or
Profitability application
se
ur
Data Synchronization executing data synchronizations
co
Compare comparison of applications
ng
Property Query property queries
i
in
tra
Export export of application
er
Query Member session level jobs created when running member queries
rtn
specifically from Hyperion Calculation
pa
Manager (these queries can be very large)
e®
Transaction Log Export export of transaction logs
cl
ra
Transform Classic to EPM transforming applications managed in Classic Planning,
O
Architect Financial Management, or Essbase
Application Migration an
migrating existing Hyperion applications
in
e
Application Validation validation of existing Hyperion applications

us
Detach Dimension changing a shared dimension to local in an application

al
on
Share Local Dimension changing a local dimension to shared

rs
pe
Application Copy copying an application

to
Dimension Copy copying a dimension

ed
Dimension Export exporting a dimension

ct
tri
es
R
-
y
r
ta
ie
o pr
Pr
e®
cl
ra
O

Performance Management Architect Architecture
se
ur
co
ngi
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
Performance Management Architect Architecture

ed
Performance Management Architect provides an interface to various sources for

ct
tri
metadata and data including Enterprise Resource Planning systems, relational

es
databases, and data warehouses. Data (dimensional hierarchies as well as data) from
R
these sources can be imported into the system via flat files or Hyperion interface tables.
-
y
r
Performance Management Architect provides a direct interface to Financial

ta
ie
Management, Profitability and Cost Management, and Planning applications enabling

pr
the creation, maintenance, and synchronization of these applications directly from

o
Pr
Performance Management Architect.

e®
The middle tier of Performance Management Architect includes the required application
cl
service for application construction, metadata management, data synchronization, and

ra
O
surfacing the user interface.

End users access Performance Management Architect and reporting and application
content through Oracle Enterprise Performance Management Workspace, Fusion
Edition.
se
ur
co
ng
i
in
tra
er
rtn
pa
e®
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

Workspace Navigate Menu
se
ur
co
ng
i
in
tra
er
rtn
Performance
pa
Management
Architect tasks
e®
cl
ra
O
an
in
e
us
al
on
Copyri ght © 2011, Oracle and/or its affil ia te s. Al l righ ts rese rved.
rs
pe
to
Workspace Navigate Menu

ed
ct
You use the Navigate menu to navigate to the modules that are available within
tri
Workspace.
es
R
The Applications menu enables you to access Planning, Financial Management,

-
Performance Scorecard, Profitability and Cost Management, and Oracle Business

y
r
Intelligence applications. Applications are displayed only when a user has rights, and
ta
ie
applications are available.

opr
Highlighted on the slide are the Performance Management Architect tasks on the
Pr
Administer menu. The tasks include Dimension Library, Application Library, Data
e®
Synchronization, Calculation Manager, Application Upgrade, and Library Job Console.

cl
ra
O

se
ur
Summary
co
ng
i
in
tra
• List Performance Management Architect features
er
• Describe Performance Management Architect modules
rtn
pa
• Describe Performance Management Architect architecture
e®
• Access Performance Management Architect
cl
ra
O
an
in
e
us
al
on
rs
pe
to
ed
ct
tri
es
R
-
yr
ta
ie
opr
Pr
e®
cl
ra
O

PTS FM11.1.2 SG

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

PTS FM11.1.2 SG

Uploaded by

Copyright:

Available Formats

Oracle® Hyperion

Partner Technology Solutions

Mark Mitsock Disclaimer

Editor Restricted Rights Notice

Graphic Designer U.S. GOVERNMENT RIGHTS

Publisher Trademark Notice

Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Management of the Extended Close Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Related Oracle Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Financial Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Financial Management Business Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Financial Management Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Logging On to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Navigating in Financial Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

View Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

Advanced and Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

Setting the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Financial Management 11.1.2 Administration i

Related Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33

Lesson 2: Creating Financial Management Applications

Creating Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Accessing the Process Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Entering Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Defining the Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Editing Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Editing Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Saving Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Creating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Lesson 4: Setting Up Dimensions

Accessing Metadata Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Editing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Adding and Deleting Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Editing Groups of Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Creating Alternate Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Assigning Members to Multiple Parents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

ii Financial Management 11.1.2 Administration

Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Other Account Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Setting Up Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

Frequency and View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46

View and Missing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47

Scenarios and Process Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48

Lesson 5: Configuring Application Settings

Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Exchange Rate Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

PVA Translation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Consolidation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Org by Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Intercompany Aggregations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Consolidation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Phased Submission Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11

Validation Account Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Dimension Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Metadata Security Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Financial Management 11.1.2 Administration iii

FDM Application Name Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18