Oracle HFM Vol2

Oracle Hyperion
Financial Management 11.1.1:

Create and Manage Applications
Volume II • Student Guide
D70013GC10
Edition 1.0
September 2008
D56009
®
Author Copyright © 2008, 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
Tom LeFebvre express authorization of Oracle.
Yuen Man Boronski
The information contained in this document is subject to change without notice. If you
Ron Reiley find any problems in the document, please report them in writing to: Oracle University,
Phil Attea 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
the documentation on behalf of the United States Government, the following notice is
applicable:
Graphic Designer
U.S. GOVERNMENT RIGHTS
Priya Saxena The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
disclose these training materials are restricted by the terms of the applicable Oracle
Publisher license agreement and/or the applicable U.S. Government contract.
Mark Mitsock Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other

names may be trademarks of their respective owners.
Table of Contents
Table of Contents i
Preface
Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Activity Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Module 1: Introduction
Lesson 1: Introduction to Financial Management

Oracle’s Enterprise Performance Management System . . . . . . . . . . . . . . . . . . . . . . . 1-2
Oracle Hyperion Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Financial Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Financial Consolidation, Reporting, and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Related Oracle Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Lesson 2: Navigating Financial Management

Financial Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Workspace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Navigating Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Financial Management Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Dimension Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11
Dimensions and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Financial Management Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Logging On to Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Navigating Financial Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Financial Management 11.1.1: Create and Manage Applications i

Table of Contents
View Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Advanced and Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Setting the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Selecting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Managing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Custom Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Related Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Module 2: Creating the Application Structure
Lesson 3: Managing Dimensions with Performance Management Architect

Dimension Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Creating Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Creating Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Guidelines for Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Modifying Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Common Consolidation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
System and Statistical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Property Value Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Creating Alternate Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Inserting Shared Members Using Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Moving Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Deleting Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Managing Orphan Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Finding Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Creating Associations Between Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Setting Up Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Organizing the Shared Library with Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Filtering the Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Sorting Dimensions in the Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Managing Members with Grid Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Running the Grid Editor Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Modifying Property Values in Grid Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Creating and Deleting Members in Grid Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
ii Financial Management 11.1.1: Create and Manage Applications

Table of Contents
Lesson 4: Loading Metadata

Metadata Load Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Formatting Metadata Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Setting Up Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Dimensions Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Members Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Managing Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Hierarchy Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
DimensionAssociations Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Loading Metadata Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Creating Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Defining Load Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Mapping Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Mapping Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Running Import Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Viewing Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Process for Loading Metadata from Interface Tables . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Lesson 5: Creating Applications

Applications and Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Local and Shared Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Creating Applications with the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Selecting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Validating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Adding Dimensions from the Shared Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Changing Local Dimensions to Shared Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Shared Dimensions: Overriding Property Settings . . . . . . . . . . . . . . . . . . . . . . . 5-15
Shared Dimensions: Activating Dimension Associations. . . . . . . . . . . . . . . . . . . 5-17
Shared Dimensions: Excluding and Showing Members . . . . . . . . . . . . . . . . . . . 5-19
Synchronizing Local with Shared Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Configuring Exchange Rate and Translation Settings . . . . . . . . . . . . . . . . . . . . . 5-24
PVA Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Consolidation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Org by Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Intercompany Aggregations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Consolidation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Configuring Phased Submission Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Financial Management 11.1.1: Create and Manage Applications iii

Table of Contents
Configuring Validation Account Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

Configuring Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Enabling Metadata Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Node Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Setting Document Attachment Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Configuring FDM Drill-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Lesson 6: Configuring Accounts and Custom Dimensions

Overview: Accounts and Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Setting Up Account Types and Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Time Balance and Account Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Dynamic Account Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Group Label Account Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Setting Up Accounts and Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Assigning Custom Members to Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Balance Sheet Accounts and Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . 6-13
Custom Dimensions and Account Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Setting Up Custom Members for Balance Sheet Movement . . . . . . . . . . . . . . . . 6-15
Auditing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Intercompany Account Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Other Account Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Lesson 7: Setting Up Entities, Calendars, and Scenarios

Setting Up Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Requirements for Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Entities and Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Entities and Intercompany Partners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Entities and the ICP Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Adding Currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Setting Up Calendars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Setting Up Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
Frequency and View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
View and Missing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Scenarios and Process Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Lesson 8: Deploying Applications

Deploying Applications Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
iv Financial Management 11.1.1: Create and Manage Applications

Table of Contents
Validating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Comparing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Duplicating Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Deploying Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Viewing Job Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Migrating Applications Using Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Migration on Connected and Disconnected Environments . . . . . . . . . . . . . . . . . 8-12
Migration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Migrating Applications to an Intermediary File . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Migrating Applications from an Intermediary File to a Destination Application . . 8-17
Exporting and Importing Individual Artifacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Viewing Lifecycle Management Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Module 3: Adding Data to Your Application
Lesson 9: Loading Data

Data Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Group Dimension Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Line-Item Detail Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Submission Phase Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Financial Management Data Storage and Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Subcube Dimensions and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Guidelines for Managing Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Loading Data from a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Merge Option: Overwriting Application Data with Load File Data . . . . . . . . . . . . 9-16
Replace Option: Replacing Data with Load Data File . . . . . . . . . . . . . . . . . . . . . 9-17
Replace by Security Option: Loading Members. . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Accumulate Option: Accumulating Application Data with Load File Data . . . . . . 9-18
Accumulate Within File Option: Loading Totals into Applications . . . . . . . . . . . . 9-19
Extracting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Exporting Data with Extended Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Copying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Removing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Lesson 10: Entering Data by Using Data Grids

Data Grids Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Financial Management 11.1.1: Create and Manage Applications v

Table of Contents
Accessing Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Creating Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Changing Grid Layout and Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Selecting Members for Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Selecting Members for Rows and Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Selecting Members Through Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Saving Data Grid Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11
Entering and Saving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Cell Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Saving Data and Parent Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Clearing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Filling Multiple Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Spreading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Calculating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Adding Cell Text and Custom Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Cell Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Custom Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Adding Line-Item Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Retrieving Data from FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Lesson 11: Creating, Loading, and Extracting Member Lists

Member Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
System-Defined Member Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3
User-Defined Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
Creating Member Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5
Identifying Member Lists in a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6
Creating Static Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
Creating Dynamic Member Lists for the Entity Dimension. . . . . . . . . . . . . . . . . . . . .11-11
Creating Dynamic Member Lists for Other Dimensions. . . . . . . . . . . . . . . . . . . . . . .11-12
Loading Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-13
Extracting Member Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-14
Lesson 12: Managing Rules with Calculation Manager

Financial Management Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Calculation Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Rule Types and Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Formula Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
vi Financial Management 11.1.1: Create and Manage Applications

Table of Contents
Creating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Creating Rule Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Validating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Deploying Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Importing and Exporting Calculation Manager Objects . . . . . . . . . . . . . . . . . . . . . . 12-18
Module 4: Setting Up Security
Lesson 13: Provisioning Users and Groups

Levels of Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Task Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Document Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
User Roles Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
User Role Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Assigning User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Lesson 14: Assigning Access to Data and Documents

Application Settings and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Document Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Defining Security Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Assigning Access to Security Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Running Security Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Configuring Security Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Running Auditing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Loading Security Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
Loading Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Extracting Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Migrating Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22
Module 5: Creating Data Forms and Task Lists
Lesson 15: Creating Data Forms

Data Forms Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Financial Management 11.1.1: Create and Manage Applications vii

Table of Contents
Creating Data Forms with Form Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

Defining the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Defining Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Setting Column and Row Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-11
Formatting Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Setting Up Text Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Setting Column and Row Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
Setting Heading Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17
Viewing Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
Exporting to and Importing from Spreadsheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19
Lesson 16: Creating and Managing Task Lists

Task Lists Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Creating Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Adding Items to Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Organizing Task List Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Folder Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Nesting Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Adding Related Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Adding Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-11
Managing Task Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
Module 6: Managing Intercompany Balances and Adjustments
Lesson 17: Entering Intercompany Data

Intercompany Transactions Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
Intercompany Account Balances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Elimination Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Plug Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Intercompany Eliminations and the Value Dimension . . . . . . . . . . . . . . . . . . . . . 17-6
Setting Up Entities for Intercompany Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Setting Up Accounts for Intercompany Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Creating Intercompany Matching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-11
Running Intercompany Matching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Formatting Intercompany Reports with Oracle BI Publisher . . . . . . . . . . . . . . . . . . 17-16
viii Financial Management 11.1.1: Create and Manage Applications

Table of Contents
Lesson 18: Adjusting Data with Journals

Journals Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Journals and the Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Multiple Journal Postings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Creating Parent and Contribution Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Opening Periods for Journal Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Journal Creation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Creating Journal Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Setting the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Creating Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
Entering Journal Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Submitting, Reviewing, and Posting Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Viewing Journal Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
Viewing Adjusted Data in Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Viewing Adjustments in the Entity Details Report . . . . . . . . . . . . . . . . . . . . . . . 18-23
Creating and Formatting Journal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
Setting Journal Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
Selecting Columns and Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Previewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-30
Saving Journal Reports Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
Saving Journal Reports Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32
Running Journal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33
Module 7: Calculating and Consolidating Data
Lesson 19: Running Consolidations

Financial Management Business Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Consolidation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Consolidation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Consolidation and the Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Checking Calculation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Translating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Entering Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Translating Data in Data Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Consolidating Children by Percentages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-13
Ownership Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
About Manage Equity Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Setting Up Organization by Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-17
Financial Management 11.1.1: Create and Manage Applications ix

Table of Contents
Consolidating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19
Lesson 20: Managing the Review Cycle Using Process Management

Process Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Process Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Process Management Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Enabling Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
About Phased Submission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-8
Submission Group Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Submission Phase Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Process for Setting Up Phased Submissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Setting Application and Metadata Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-11
Assigning Validation Accounts to Submission Phases . . . . . . . . . . . . . . . . . . . 20-12
Setting Up Submission Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-13
Assigning Submission Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-15
Security Access for Process Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-17
Viewing Process Unit Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-18
Process Control Panel Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21
Viewing Status for Multiple Submission Phases . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Viewing Status for All Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24
Validating Process Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Validation Accounts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Viewing Validation Account Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Calculating and Consolidating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-30
Moving Process Units Through the Review Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . 20-31
Selecting Review Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-33
Email Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-34
Viewing Review History in Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-36
Viewing Process Level in Data Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-37
Managing Process Unit States in Data Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . 20-38
Locking and Unlocking Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-39
Lesson 21: Sharing Data Using Data Synchronization

Data Synchronization Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Creating Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Data Synchronization Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Specifying Source and Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
x Financial Management 11.1.1: Create and Manage Applications

Table of Contents
Mapping Source Dimensions to Destination Dimensions . . . . . . . . . . . . . . . . . . . . . 21-8

Creating Filters for Source Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Applying Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
Inserting Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-12
Saving Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13
Validating Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14
Executing Data Synchronizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-16
Viewing Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-18
Lesson 22: Analyzing Data with Smart View

Smart View Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Smart View Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Typical Business Process for Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Connecting to Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5
Viewing and Analyzing Data with the Ad Hoc Analysis Tool . . . . . . . . . . . . . . . . . . . 22-7
Changing the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-9
Changing Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Drilling Down and Up Dimension Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . .22-11
Pivoting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-12
Displaying Cell Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-13
Adding Formulas and Formatting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-14
Creating Free-form Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16
Calculating, Translating, and Consolidating in Smart View . . . . . . . . . . . . . . . . 22-18
Submitting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-19
Working with Data Forms in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-20
Functions in Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-23
Methods for Creating Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-24
Smart View Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-25
Creating Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-26
Setting the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-27
Appendix A: Automating Tasks

Task Automation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Tasks Available for Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Uses for Task Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Taskflow Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Components of Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Creating Taskflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Financial Management 11.1.1: Create and Manage Applications xi

Table of Contents
Stage Definition—General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Stage Definition—Processing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Stage Definition—Starting Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Adding Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Testing Taskflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Taskflow Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Viewing Taskflow Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Viewing Task Audit Detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Viewing Data Audit Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
Appendix B: Managing Intercompany Transactions

Intercompany Transactions Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Business Process for the Intercompany Transactions Module . . . . . . . . . . . . . . . . . . B-3
Setup Considerations for Intercompany Transactions . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Opening Intercompany Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Creating Intercompany Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Loading Intercompany Transactions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
About Process IC Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Creating Transactions from Process IC Transactions . . . . . . . . . . . . . . . . . . . . . B-10
Matching Intercompany Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Intercompany Transaction Matching Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
Posting Intercompany Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
Generating Matching Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Drill-Through Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
Locking Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16
Closing Intercompany Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17
Monitoring Intercompany Entity Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Appendix C: Managing Applications with Classic Administration

Classic Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Creating Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Accessing the Process Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Defining Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Defining the Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Editing Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
Editing Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Saving Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
xii Financial Management 11.1.1: Create and Manage Applications

Table of Contents
Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12

Creating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Creating Metadata Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Editing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Building Member Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
Assigning Members to Multiple Parents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
Editing Groups of Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18
Configuring Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
Loading and Extracting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
Load Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Merge Versus Replace—Rules of Thumb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22
Metadata Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Format for APP Load Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
Extracting Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
Financial Management 11.1.1: Create and Manage Applications xiii

Table of Contents
xiv Financial Management 11.1.1: Create and Manage Applications

M O D U L E 5
Creating Data Forms and Task Lists 14
Overview
You can create data forms and task lists for frequently performed tasks.
Data forms provide predefined rows and columns for data entry. Task
lists enable users to access tasks without navigating the product.
Lessons in this unit include:
• Creating Data Forms
• Creating and Managing Task Lists
L E S S O N 1 5
Creating Data Forms 15
Objectives
At the end of this lesson, you should be able to:
• Describe data forms
• Create data forms with Form Builder
• Define points of view
• Define columns and rows
• Set column and row options
• Export to and import from spreadsheets
Module 5 Creating Data Forms and Task Lists
Lesson 15 Creating Data Forms
Data Forms Overview
Data forms provide the following types of flexibility:

• Add columns or rows for text input
• Add blank rows or columns for spacing
• Apply row and column formatting
Copyright © 2008, Oracle. All rights reserved.
Data Forms Overview

Data forms are templates, with predefined row and columns, that users can use to input
and view specified data elements. Users cannot add rows and columns to or remove
rows and columns from data forms.
If you use Financial Data Quality Management (FDM) to load data into an application,
users can drill from data forms to FDM to view the source data. The process of drilling
down is similiar to one used in data grids.
On data forms, users can change point-of-view selections only for the dimensions that
you specify when you set up the form. For example, you can set up the point of view for
a form so that users can select the period but not the scenario and entity for which they
want to enter data.
You can define links from one form to another to enable users to drill-through to view
data in the linked form.
15-2 Financial Management 11.1.1: Create and Manage Applications

Data form toolbar buttons:
Toolbar Button Function

Submit
Refresh
Calculate
Force Calculate
Cell Text
Instructions
Print
Export to Excel
Import from Excel
Suppress Rows
Suppress Columns
Suppress Lines
Financial Management 11.1.1: Create and Manage Applications 15-3

Creating Data Forms with Form Builder
To define a data form, you use the options on the Form Builder
tabs.
Creating Data Forms with Form Builder

Financial Management provides a graphical user interface for creating and maintaining
data forms. You can enter up to 20 characters for the form label and up to 40 characters
for the description. In the Instructions text box, you can enter instructions for use on the
form. When the user selects the Instruction button, the information is displayed in a
separate window.
To create data forms with form builder:

1. In the application, select Adminstration > Manage Documents.
2. Select the Data Forms tab.
3. Click New.
The 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.

Defining the Point of View
Specifies the initial value Specifies a m em ber list from

for the dimension which to select
Defining the Point of View

The Member column specifies, for each dimension, the initial value that is displayed on
the data form. The Selectable column specifies member lists for the dimensions.
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
view.
To define the point of view:

1. On the POV tab, in the Member column, select the dimension that you want to
display on the data form.
2. In the Selectable column, specify the member list for the dimension.
3. Click Next.

Defining Columns and Rows
Defining Columns and Rows

You define columns and rows to specify the members to be displayed in the columns and
rows.
To define columns and rows:

1. On the Columns tab, define the column’s POVs, display options, formats, and cell
text as per the following guidelines.
2. On the Rows tab, define the row’s POVs, display options, formats, and cell text as
per the following guidelines.

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:
Keyword#Member
Where Keyword identifies a dimension type, such as S for the dimension type Scenario,
and Member is a member name. You can enter the dimension keyword and the member
or browse to select from lists. The following example creates a column or row for
Budget:
S#Budget
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
YTD view:
S#Budget.W#YTD
Dimension Keywords:
Keyword Description
S# Scenario
Y# Year
P# Period
V# Value
E# Entity
W# View
A# Account
I# Intercompany Partner
C1# Custom1
C2# Custom2
C3# Custom3
C4# Custom4
Member Lists
You can also use member lists to define columns or rows. A column or row is added to
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
columns dynamically. The rows and columns are created based on the selected point-of-
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
NetProfit and its children. If TotalAssets is selected, the data form displays rows or
columns for TotalAssets and its children.
A{@CUR.[Children]}
Blank Rows
You can insert blank rows for spacing by typing the keyword Blank, and press the Tab
key.
Relative Time Periods
For rows and columns, you can use the following keywords to select a period relative to
the current point of view:
• CUR
• FIRST
• LAST
• NEXT
• PRIOR
Consider the following example. If the period selected in the point of view is January, the
column or row that is created displays data for February.
P#CUR+1
Column and Row Calculations—Calc1 and Scalc

You can use the Calc1 function to create, in columns or rows, custom formulas that use
standard mathematical operators. The specified calculations are performed in the client’s
Web browser. The following example subtracts column 2 from column 1:
Calc1(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.
In Scalc calculations, you can 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
example refers to the cell in the fourth row of the second column:
R1=SCalc(Cell(4,2))
• Row references, using the syntax Row(rowIndex). The following example divides row
4 by row 2:
R3=SCalc(Row(4)/Row(2))
NOTE
For rows or columns that contain member lists, the calculation is performed on the
total for the members of the list.

Setting Column and Row Options
You can set options for individual rows and columns.
Setting Column and Row Options

Options that you set for individual rows or columns override the defaults for the form.
Row and column options:
Option Description
Override Specify a point-of-view dimension member or formula calculation for
one or more consecutive columns.
Decimal Places Specify the number of decimal places. Valid values are 0 to 9.
Scale Specify the scale. Valid values are -12 to 12.
Cell Text Specify whether the row or column accepts cell-text input. For text-
input rows or columns, enter 1.

Option Description
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 (&).
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
suppression options set for the form, the row is displayed.
Other Enter a valid data form script to set options that are not provided by
Form Builder.
Options available only for rows:
Option Description
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 select members and enter data. You specify the dimension and
member list from which users can select. The following example
adds an icon that enables users to select members from the Markets
member list of the Custom1 dimension:
C1{Markets}
Link Specify a link to another Web data form.

Formatting Columns and Rows
Formatting assigned to rows overrides formatting assig ned to

columns.
Initial semicolon
enables combined row
and column formatting.
Formatting Columns and Rows

Each style property consists of a property name, a colon, and a value. The value may be
one or more words, separated by spaces; for example:
color:red; text-align:right
The Style option is interpreted by the browser, not by Financial Management, so it is

limited only by what the browser supports. The Style option uses the standards
supported by the World Wide Web Consortium (W3C). For information about style
standards, see http://www.w3.org/TR/REC-CSS2.
By default, formatting assigned to rows overrides formatting assigned to columns. For
example, if column 2 is italic and row 5 is bold, the cell at the intersection of column 2
and row 5 is displayed bold.

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 shown 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 bold italic.
The following table lists some of the properties and potential values that you can use. For
a full list, see the Property Index at http://www.w3.org/TR/REC-CSS2/propidx.html.
Property Value Example

Color (foreground) Color name or the standard color: red
Background-color hexadecimal RGB notation. color: rgb(255,0,0)
For a quick reference for colors, go background-color: #ff0000
to http://www.cross-
background-color: yellow
browser.com/docs/color_cha
rts.html.
Font-family Font name. font-family: Arial
Font Font style. font: italic Courier
You can combine up to six font font: Arial Italic extra-
properties, separated by spaces, in bold 12pt
one Style value.
Font-weight Font weight. Values include demi- font-weight: extra-bold
bold, demi-light, extra-bold, light,
extra-light, demi-light.
Font-size Font point size. font-size: 12pt
font-size: 12pt
Text-align Alignment of the text. Values text-align: center
include left, right, center, and justify.

Setting Up Text Columns and Rows
Setting Up Text Columns and Rows

You can set up columns and rows for input of cell text, thereby enabling users to enter
text annotations directly on the data form, instead of from the Cell Text dialog box.
For the example shown 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 to the Quarter1 member, in the column definition for column 5, connects the
text entered in the cells for column 5 to the Quarter1 member.

Setting Column and Row Defaults
Use the Details tab to set default display options for all rows
and columns of a form.
Setting Column and Row Defaults

Default settings do not override the settings for individual rows and columns.
To set up column and row defaults:

• On the Details tab, set the Grid, Print, Display, and Supression options for columns
and rows.
Under Display Options, select the Single Period option to view, in the line-item entry
window, only the period for the selected cell. Select the CalcbyRow option to change
the default calculation order (columns first) to rows first. For some calculations, for
correct results, rows may need to be calculated first.

Setting Heading Defaults
Setting Heading Defaults

You can specify defaults for headings for each dimension.
To set heading defaults:

1. On the Headers tab, in the Show drop-down list, select Label or Description to display
member labels or descriptions for dimension headings.
2. In the Style box, enter style keywords.
3. In the Length box, specify the maximum length for row headings.
4. Optional: Select Fixed, if you want the maximum and minimum length to be the
same.
5. Optional: In the Other column, enter a valid data form scripts for header options that
are not provided by Form Builder.

Viewing Scripts
Viewing Scripts
On the Script tab, you can view, modify, and print scripts by entering the syntax in the
text box.

Exporting to and Importing from Spreadsheets
Import from and export to spreadsheets
Exporting to and Importing from Spreadsheets

You can use the toolbar to export data forms from Financial Management to Microsoft
Excel and to import spreadsheets from Excel to Financial Management. For example,
you can export a form to Excel, enter or edit data, and then load the modified data into
Financial Management.
When you export from a data form to Excel, the point of view of the data form is exported
and saved in the spreadsheet. When you import from the Excel spreadsheet into the
Web client, data is imported to the saved point of view, regardless of the point-of-view
settings for the data form.

Summary
In this lesson, you should have learned to:
• Describe data forms

• Create data forms with Form Builder
• Define points of view
• Define rows and columns
• Set row and column options
• Export to and import from spreadsheets

L E S S O N 1 6
Creating and Managing Task Lists 16
Objectives
• Describe task lists
• Create task lists
• Add items to task lists
• Organize and manage task lists
Lesson 16 Creating and Managing Task Lists
Task Lists Overview
Monthly Close
Task List
Enter Journals
Review
Consolidate
Report
Task Lists Overview

A task list contains items and tasks that you use frequently; for example, data forms,
data grids, and reports. By setting up task lists, you can complete your workflow without
navigating among forms, grids, and report modules, and you can view and manage items
and tasks from Project or Browser view.
In Browser view, task lists are listed in the top pane and items contained in the selected
task list are listed in the bottom pane. In Project view, task lists, are displayed in a drop-
down list that identifies the task list items.

Creating Task Lists
You can create task lists on the Tasklists tab of the Manage
Documents window.
Creating Task Lists

You can create private or public task lists. Private task lists can be accessed only by the
users who create them. To limit access to a list, you can assign a security class to the
list. For example, you can assign the Admin security class to a task list that you want to
limit to administrators.
To create task lists:

1. Open the application and select Administration > Manage Documents.
The Manage Documents page is displayed.
2. Select Task List tab.
3. Select New Tasklist.
The Manage Tasklist page is displayed.

4. Add items to the tasklist.

See “Adding Items to Task Lists” on page 5.

Adding Items to Task Lists
Add item to a task list.
Adding Items to Task Lists

You can add the following items to a task list:
• Tasks
• Data forms
• Data grids
• Intercompany reports
• Journal reports
• Links to Web sites or files
• Related content (documents in Financial Reporting or Web Analysis)
• Folders
• Other task lists
You can include multiple instances of one item or object in a task list.

To add items to tasklist:

1. In the Add drop-down list, select the item you want to add to the tasklist.
The list of the selected item is displayed.
2. Select the specific item you want to add to the tasklist, and click Add to Task List.
The selected item is added to the task list.
3. Repeat steps 1 and 2 to add other items to the task list.
4. Click Save.
5. Enter the name and description of the tasklist
6. From the Security Class drop-down, select the security class.
7. Click OK.

Organizing Task List Items
Folder.
Journals task list is nested

inside the Closing task list.
Organizing Task List Items

To organize the documents of a task list, you can incorporate folders or sub-folders.
Users can expand a folder and select one or more documents.
Folders simplify task-list maintenance. Documents are available to task-list users without
the need for an administrator to edit the task list.
Folder Benefits
You can use folders in task lists for various purposes:
• Organize data forms, system reports, data grids, and other task lists
• Facilitate navigation when you have numerous task list items
• Combine common tasks

To create a folder in a task list:

1. In the application, select Administration > Manage Documents.
2. Select the Tasklists tab.
3. Select New Folder.
4. In the Name box, enter the name of the folder.
5. In the Description box, enter a description.
6. In the Content Type drop-down list, select Tasklists.
7. In the Security Class drop-down list, select a security class.
8. Click OK.
Nesting Task Lists

You can nest task lists within a task list. If your workflow involves many tasks, nesting
task lists makes navigation easier for end users.
To nest task lists within a task list:

2. Select the Tasklists tab.
3. Select a task list in which you want to nest another task list, and click Edit to display
the Manage Tasklist page.
4. In Add drop-down list, select Tasklist to display the Tasklist page.
5. Select the task list you want to nest, and click Add to Tasklist.
The task list is added.
6. Click Save.
7. Click OK.

Adding Related Content
Adding Related Content

In Financial Management task lists, you can include Web Analysis reports, Financial
Reporting reports, and Planning forms. When, in Financial Management, you create a
related content document, the document serves as a link to a resource in another
product. For example, you can add a report from Financial Reporting to a task list or
launch the report from the Related Content menu in the view pane.
To add related content:

1. Select File > New > Related Content.
2. In the Resource Server drop-down list, select the resource server for the product for
which you want to add related content.
3. Select the document that you want to make available as related content.
4. Click Save.

5. Enter a name and description for the document.

The name and description is displayed in the document list of the
Related Content tab.
6. Click Close.

Adding Links
Test the link.
Adding Links
You can add Web page or file links to task lists. Before you can add a link to a task list,
you must create the link.
• When you create a link, you can specify whether it should be displayed in the task list
pane or in a separate window.
• For links to Web pages that are time-consuming to open, you may want to specify
that the system prompt the user before opening the Web page.
• You can launch links from the Links menu in the view pane.
When you select Add Link from the Manage Tasklists task, the links that you have
created are available.

To add links:
1. Open the application and select File > New > Link to display the New Link page.
2. In the Link box, enter the name of the link.
3. Optional: Click View, to test the link.
4. Specify how to want the link to open and display.
5. Click Save.
6. Enter the name and description of the link and select a security class.
7. Click OK.

Managing Task Lists
Add item to
tasklist.
Reorder the
tasklist item s.
Displays the task list

each time a basic
user logs on.
Managing Task Lists

You use the buttons in the Manage Tasklist page to reorder or remove items and to set
the current task list as the default task list (the task list that is displayed when a basic
user logs on to the application).

Summary
• Describe task lists

• Create task lists
• Add items to task lists
• Organize and manage task lists

M O D U L E 6
Managing Intercompany Balances and

Adjustments 16
Overview
During a financial period, you may have to adjust data after it is entered
or loaded into the base-level entities. The reasons why you may need
to adjust data include a required restatement of data, a directive from
management, or an input error. You may also need to manage
intercompany transactions.
You can use intercompany accounts and the Intercompany Partner
(ICP) dimension to manage intercompany transactions. Financial
Management journals provide an audit trail of the changes made in the
application.

• Entering Intercompany Data
• Adjusting Data with Journals
L E S S O N 1 7
Entering Intercompany Data 17
Objectives
• Describe how intercompany data is eliminated in Financial
Management
• Set up entities and accounts for intercompany transactions
• Enter intercompany data.
• Report on intercompany data
• Format intercompany reports with Oracle BI Publisher
Module 6 Managing Intercompany Balances and Adjustments
Lesson 17 Entering Intercompany Data
Intercompany Transactions Overview
A transaction between two entities in an organization is an

intercompany transaction.
East Sales Sale Customer
1
3
West Factory
Intercompany
invoice
(transaction) 2 Goods shipped from
separate organization
Intercompany Transactions Overview

The example on the slide illustrates the following process:
1. The East Sales organization makes a sale to an outside customer.
2. The goods are shipped from an internal factory, organization (West Factory).
3. West Factory sends an intercompany invoice to East Sales for the goods that West
Factory shipped.
Entities that conduct intercompany transactions are known as intercompany partners
(ICPs).

Intercompany Account Balances
Intercompany balances are not relevant for external financial

reporting. According to accounting rules, intercompany account
balances are eliminated prior to external financial statement
generation.
USA
2
California Connecticut 1
Plant1 West Sales Administration 1 Marketing

2 2
East East
EastSales 1
Intercompany Account Balances

Intercompany transactions produce intercompany account balances.
To avoid overstatement, intercompany account balances must be eliminated before
external financial statements are generated. Balances are eliminated at the first common
parent of the intercompany partners.
During data consolidation, Financial Management automatically eliminates intercompany
balances.
In the example on the slide, intercompany balances in Administration East (1) or East
Sales (1) are eliminated at the Connecticut (1) entity. Intercompany balances between
Plant1 (2) and Marketing East (2) are eliminated at the USA (2) entity.

Elimination Process
USA
RentalRevenue: 0
RentalExpense: 0
California Connecticut
RentalRevenue: 1500 RentalRevenue: 0
RentalExpense: 0 RentalExpense: 1500
Plant1 Sales West Administration Marketing

RentalRevenue: 1500 East East
EastSales
RentalExpense: 0
RentalRevenue: 0
RentalExpense: 1500
Elimination Process
Elimination of intercompany balances occurs during data consolidation. During the
elimination process, differences between intercompany account balances are posted to
a plug account.
For the example on the slide, EastSales leased equipment worth USD $1,500 from
Plant1. When data is consolidated, the intercompany account balances for the
RentalExpense and RentalRevenue intercompany accounts are eliminated at the first
common parent, the USA entity.

Plug Accounts
Intercompany Accounts Non-Intercom pany Account

Sales - Intercompany Purchases - Intercompany IntercoDiffPL
500 600 -100
Plug Accounts
Because balances for intercompany partners may not agree, you need accounts that,
upon consolidation, record the differences between pairs of intercompany account
balances. In Financial Management, these storage accounts are referred to as plug
accounts.
The example on the slide shows a USD $500 Sales intercompany balance against a
USD $600 Purchases intercompany balance. When consolidation is performed, the USD
$100 difference is placed in the intercompany difference plug account (IntercoDiffPL).

Intercompany Eliminations
and the Value Dimension
Intercompany Eliminations and the Value Dimension

Intercompany eliminations are stored in the Value dimension. Because Value dimension
members are displayed in data grids and reports, you can easily audit intercompany
eliminations.
For the Entity Currency members that are associated with intercompany balance
accounts, reversing entries are created in Elimination members. The reversals result in
the following:
• Zero balances being consolidated to the Entity Currency member that is associated
with the parent account.
• The differences between the eliminated balance are posted to the Entity Currency
member of the plug account.

For the example of 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 a zero balances. The balances eliminated from SalesInterco and
PurchasesInterco are posted to the IntercoDiffPL plug account. California displays a
balance of -100 for IntercoDiffPL, which is the difference between the eliminations
posted from the intercompany accounts.

Setting Up Entities for Intercompany Data
Specifies whether the entity is

displaye d as a member in the
ICP dimension
Specifies a security class

for the entit y for the ICP
dimension
Setting Up Entities for Intercompany Data

You must set the IsICP property for all entities that act as intercompany partners and
have intercompany data.
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
want users in Europe to be able to enter intercompany transactions between European
entities and United States entities, but not be able to modify data for United States
entities. To achieve this objective, you make the following security assignments:
• For United States entities, you assign USA for the Security Class property and
Intercompany for the SecurityAsPartner property.
• You give users in Europe read-only access to the USA security class and read-and-
write 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 with
Performance Management Architect.

Setting Up Accounts for Intercompany Data
The following properties need

to be set for intercompany
accounts:
Is ICP
Plug account
Copyright © 2008, Oracle. All r ights reserved.
Setting Up Accounts for Intercompany Data

To use accounts in intercompany transaction processing, you must set two member
properties:
• IsICP—To flag the account as an intercompany account
• PlugAcct —To store differences between intercompany balances
For instructions on configuring accounts, see Lesson 6, Configuring Accounts and
Custom Dimensions.

Creating Intercompany Matching Reports
Copyright © 2008, O racle. All r ights reserved.
Creating Intercompany Matching Reports

Intercompany matching reports help you track intercompany transactions for analysis and
auditing purposes. After you consolidate data, you can run intercompany matching
reports that provide detail on intercompany account balances that were eliminated.
When creating intercompany reports, you can select intercompany entities and their
partners, as well as intercompany accounts.
• Entity and Partner are the entities for which you want to match intercompany
transactions.
• Accounts and Matching Accounts are the intercompany accounts for which you want
to match transactions.
• 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 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.
• Matching Tolerance (%): To see only out-of-balance transactions that exceed the
percentage that you specify. Enter a percent of the total, or use the default value of 0.
The smaller total of the entity or partner is used.
• Suppress Reversed: Suppress, for each entity transaction, reversed transactions
from partners.
• Suppress Details: Suppress intercompany detail and print only the total difference for
each entity-partner section.
• Suppress Customs: Suppress custom dimensions.
• Scale Factor: Select a scale factor, or use the default value of 0. For example, if you
enter a scale factor of 3, the report amount is displayed in thousands. If the scale
factor is 0, the report amount is displayed in units.
• Decimal Override: Select a decimal setting, to override the setting defined in the
account, or use the default value.
• Member Display: Display the member label, member description, or both.
• Plug Account Display: Display a summary of plug accounts that are affected by the
intercompany transaction.
To create intercompany reports:

1. Open the application, and select Administration > Management Documents.
The Manage Document page is displayed.
2. Select the Reporting Tab.
3. In the Report Type drop-down list, select Intercompany.
4. In the File Type drop-down list, specify a file type.
5. Click New Report to display the New Intercompany Report page.
6. Select intercompany entities and their partners, report options, as well as
intercompany accounts.

7. Click Preview.
8. Perform an action:
• Click Save Remote to save the report on the server.
• Click Save Local to save the file on the computer.
9. Click Close.

Running Intercompany Matching Reports
Running Intercompany Matching Reports

You can access the list of saved intercompany matching reports on the Manage
Documents page. When you run a report, you can override the default report settings.
For example, you can select a different partner entity. On reports, the date, time, and
user are displayed as header information.
To run intercompany reports:

1. Open the application and select Administration > Manage Documents.
The Manage Documents page is displayed.
2. Select the Reporting tab.
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 box, select a format.
NOTE
You can select a PDF, RTF, HTML, or XLS format.
5. In the Select Template drop-down box, select a report template.

6. Click OK.
The Report Override page is displayed.
7. Optional: Select any value to override the default report settings.
8. Click OK.

Formatting Intercompany Reports

with Oracle BI Publisher
Format the default template and select the saved template when printing reports.
Save the formatted template.
Select the template when printing

the report.
Formatting Intercompany Reports with Oracle BI Publisher

Oracle BI Publisher (BI Publisher) is a reporting solution from Oracle that enables you to
create and format reports.
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 can modify these templates using Microsoft Word.
To format intercompany reports with BI Publisher:

1. Open Microsoft Word.
2. Navigate to your Server Working folder\Report Style
Sheet\Templates\Intercompany in your Financial Management directory, and open
the intercompany report template.

3. Make format changes to the template using Microsoft Word formatting.

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, HTML, etc.
6. In the template directory, save the mofified template with a new name.
NOTE
If you have more than one Financial Management server, you must save the
modified template in the template directory of each server.
7. In the application, select a report format, select the modified template, and click the
OK button.

Summary
• Describe how intercompany data is eliminated in Financial Management

• Set up entities and accounts for intercompany transactions
• Enter intercompany transactions
• Report on intercompany transactions
• Format intercompany reports with Oracle BI Publisher

L E S S O N 1 8
Adjusting Data with Journals 18
Objectives
• Describe the purpose of journals
• Open periods for journal entry
• Create journal templates and journals
• Submit, review, and post journals
• View adjusted data
• Create and format journal reports
Lesson 18 Adjusting Data with Journals
Journals Overview
Adjusted
Account Journal
Account
Balance Adjustments
Balance
Journals Overview
Financial Management journals provide an audit trail of changes made in an application.
Journals tell you which users made adjustments and which accounts, entities, and time
periods are affected. All adjustments through journals must be reviewed and approved
before you can post them.
Journal features:
• You can create double-sided journal entries by using debits and credits.
• You can balance entries, or you can permit single-sided, out-of-balance entries.
• You can create recurring journals that are repeated for a number of future periods.
• You can create autoreversing journals that generate automatic reversing entries in
the next time period.
• You can use the journal approval process to provide accountability.

After you create a journal, you need to submit it to your supervisor for approval. After
your supervisor approves the journal, you can post it to the Financial Management
database.
The approval process is covered later in this lesson.

Journals and the Value Dimension
<Entity Currency> 500 Value entered in data form

<Entity Currenc y Adjs> -75 Value posted from journal
<Entity Currency Total> 425 Adjusted value rolled up to parent
Journals and the Value Dimension

The Value dimension plays an important role in journal processing. When you load data
from a file or use a data form or grid to enter data, the values are stored in the Entity
Currency member of the Value dimension. When you post adjustments from a journal,
the adjustment values are stored in the Entity Currency Adjs member.
Financial Management stores the posted adjusted data by combining the values in the
Entity Currency and Entity Currency Adjs members and storing the result in the Entity
Currency Total member. The posted adjusted value is used during the consolidation
process.

Multiple Journal Postings
Postings from multiple journals are cumulative.
Journal A:
<Entity Currency> 500 -100
<Entity Currency Adjs> -75
<Entity Currency Total> 425 Journal B:
+25
Multiple Journal Postings

If more than one journal is posted to the Entity Currency Adjs member for the same
account, the results are cumulative. The total from the current journal is added to or
subtracted from the existing total in Entity Currency Adjs.

Creating Parent and Contribution Adjustments
You can make a parent adjustment to

You can adjust the WestSales that affects only SalesServices or
amount after perc ent only California.
ownership is applied.
You can adjust the

amount before percent
ownership is applied.
Creating Parent and Contribution Adjustments

If entities roll up to more than one parent, you can create parent adjustments. Parent
adjustments enable you to apply an adjustment for a child to a selected parent, rather
than to all parents.
To create parent and contribution adjustments:

1. Open a journal.
2. In the journal point of view, select the Parent Adjs member.
NOTE
Parent adjustments are available only for parent entities for which the
AllowAdjFromChildren application setting is selected (On).

3. Select the Contibution Adjs member and adjust the value that is contributed to the
parent after percent ownership is applied.

Opening Periods for Journal Entries
Opening Periods for Journal Entries

For each scenario, you must open time periods before you can post journal entries to
them. By default, all periods in Financial Management have an initial status of
Unopened. You can open and close periods at any time, but you cannot change an
opened period to unopened.
NOTE
You must have the Administrator or Journals Administrator security role to
manage periods.

To open periods:
1. In the View pane, select Tasks > Journal Tasks > Manage Periods to display the Manage
Periods page.
2. Select a scenario and year of the periods you want to open.
3. In the Period area, select the periods you want to open.
4. Click Open.

Journal Creation Process
1. Create Journal Templates

2. Set the Point of View
3. Create Journals
4. Enter Journal Data
5. Review, Submit, and Post Journals
6. View Journal Adjustments
7. Create and Format Journal Reports
Journal Creation Process

In Financial Management, you use the Process Journals task to create journals and to
enter information into the journals. You enter journal information by using journal
templates or creating blank journals.
You can create journal groups to help classify journals by type:
• Reclasses
• Entry corrections
• Reversals
• Accruals
• 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.

Creating Journal Templates
Journal template Entity (For single-entity journals)
POV WestSales
Description Reclass balances
Set up in advance
Interest Expense
Accounts
C1..C4
Amounts Debit Credit
Creating Journal Templates

You can create a journal template to post adjustments that have common information,
such as entities or accounts. Then, you use this template to create journals with similar
information.
You can create two types of journal templates:
• Standard templates contain accounts and entities for adjustments that you enter
frequently.
• Recurring templates contain complete information for identical journal entities that
occur for more than one period.
Journal templates are independent of scenario and year. You select a scenario and a
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 > Journal Tasks > Manage
Journal Templates.
2. Click New.
3. Optional: Clear Use Single Entity to create multiple entities template.
4. In the Label box, enter a template label.
5. Optional: In the Group drop-down list, select a group to assign to the journal.
NOTE
The journal group that you assign must exist in the application.
6. In the Balance Type drop-down, select a balance type to specify the status of the
journal before you post it.
Type Description
Balanced Total journal debits and credits must balance.
Unbalanced Total journal debits and credits need not balance.
Balanced Total debits and credits for each entity must balance.
by Entity
7. Optional: In the Security drop-down, select a security class.
8. In the Description box, enter a description for the template.
9. For each dimension, enter a member.
NOTE
If you clear Use Single Entity option, you must select an entity.
10. Click Save.

Setting the Point of View
Set the point of view

before you create a
journal.
Use this button

to create a
journal.
Lists journals for the

current point of view.

Before creating journals, you must set the point of view based on your requirements. The
point of view determines the members that are displayed for the Scenario, Year, Period,
and Value dimensions.
NOTE
To create journals for parent adjustments, select the Parent Adjs member for
the Value dimension.
To set point of view:

1. In the view pane, select Tasks > Journal Tasks > Process Journals.
2. In the Point of View, select members.
3. Click New to display the New Journal page.

Creating Journals
Blank Journal Journal Template
Description Description Reclass Balance
Accounts Accounts Interest Expense

C1..C4
Amounts Amounts Debit Credit
Creating Journals
You can choose either to start with a blank journal or to create the journal from a
template.
To create journals:
1. Under New, perform an action:
• Select Start with a blank Journal.

• Optional: Select Create as Single Entity Journal to add Entity to the journal POV bar,
so that you can select a single entity for the journal.
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 an action:
• Select Regular to create a regular journal entry.
• Select Auto-reversing to create an auto-reversing journal entry.
3. Click OK to display the Edit Journal page.

Entering Journal Data
Selec t a balance type.
Select members for each row.
Entering Journal Data

After creating a journal, you enter the journal data on the Edit Journal page.
To enter journal data:

1. Optional: For single entity journals, select the entity on the POV bar.
2. Type a label and description.
3. Select the balance type.
4. Optional: Assign a security class.
5. Select an account and a member for the other dimensions of 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.
If the journal contains errors, a separate window displays the scan results by row
number.
8. Click Save, and then Close.

Submitting, Reviewing, and Posting Journals
Status: Submitted
Accountant or Accounting Manager/

Financial Analyst Supervisor
Status: OR
Status:
Journal Status: Approved Rejected
Posted
If Approved, user can post
journal
Submitting, Reviewing, and Posting Journals

After creating journals and entering journal data, you must submit them to your
supervisor for approval. After your supervisor approves the journal, you can post it to the
Financial Management database.
1. Users review and submit journals one at a time or in batches.
2. The status of the journal changes from Working to Submitted.
3. A reviewer (a user with the Journal Approver security role) approves or rejects the
journal.
4. If the journal is approved, the user can post it.
Guidelines:
• 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.
To submit, review, and post journals:

1. In the view pane, select Tasks > Journal Tasks > Process Journals.
The Process Journals page is displayed.
2. Select the journal you want to process.
3. In the Process drop-down list, based on your security, perform an action:
• Select Submit to submit the journal.
• Select Review to review the journal.
• Select Post to post the journal.

Viewing Journal Adjustments
You can view journal adjustments in a data grid or in the Entity

Details report.
Viewing Journal Adjustments

After you have reviewing and posting the journal adjustments you can view them in a
data grid or in the Entity Details report.

Viewing Adjusted Data in Data Grids
Viewing Adjusted Data in Data Grids

You can use a data grid to view the adjustments made to the accounts for an entity. You
can change the Value dimension in the grid point of view to view the values in the Entity
Currency Adjs, Entity Currency, and Entity Currency Total members.
When you select the Entity Currency Adjs member, accounts that have adjustments
posted from several journals display cumulative values.
To view adjusted data in data grids:

1. In the view pane, select Documents > Data Grids.
2. Select the data grid.
3. Right-click a cell and select Cell Adjustments.

Viewing Adjustments
in the Entity Details Report
Journal Adjustments
Viewing Adjustments in the Entity Details Report

You can use the Entity Details report to view details of the entire consolidation path for a
specific cell, including the journal entries that generated in the journal posting process.
To view adjustments in the entity details report:

1. In the data grid, select a valid intersection.
2. Right-click the valid intersection cell and select Entity Details.
NOTE
In an entity report for a Parent entity, the data shows only the totals from its
children.

Creating and Formatting Journal Reports
Creating and Formatting Journal Reports

You can create and format journal reports to check the status of journals and to review
journal adjustments. You can also set journal report properties, select columns and
filters, and preview the reports.
To create journal reports:

1. In the view pane, select Tasks > Journal Tasks > Process Journals to display the Process
Journals page.
2. Select Reports to display the Journal Report Properties page.
After you create a journal report, you can use Oracle BI Publisher to format the report.
The procedure is similiar to the one you use in formatting intercompany reports with
Oracle BI Publisher.

• Navigate to: C:\Hyperion\products\FinancialManagement\Server Working

Folder\Report Style Sheet\Templates\Journal to access the journal template
report.
• Navigate to: C:\Hyperion\products\FinancialManagement\Server Working
Folder\Report Style Sheets\Sample XML\Journal to access the sample XML data
file.

Setting Journal Report Properties
Setting Journal Report Properties

You can set properties for a journal report on the Journal Report Properties page.
To set journal report properties:

1. From the Select Report Format drop-down list, select a report format.
2. From the Select Template drop-down list, select a template.
3. Optional: In the Label box, enter a label.
NOTE
If the label is not printed on the final report, only the description and point-of-
view sections are visible on the final report.
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
Selecting Columns and Filters

When setting up a journal report, first you select the columns to be displayed on the
report. Next, you define filters to specify which journals to include in the report.
To select columns:
1. Click the Columns tab.
2. Perform one or both actions:
• Sort each column in either ascending or descending order.
• If a column is a dimension, choose to display dimension labels, descriptions, or
both.

To select filters:
1. Click the Filters tab.
2. Select to filter the report by the following:
• Entity
• Label
• Group
• Description
• Status
• Type
• Balance type.
For example, you can filter a report to include only unposted journals. Only journals
or journal templates that meet all filter criteria are included in the report.

Previewing Reports
Previewing Reports
After you specify properties, columns, and filters you can preview the report.
To preview the report:

1. On the Process Journals page, select Print/Preview.
A report with your selected options is generated in a new window.
• Select Print to print the report.
• Select File > Close to return to the Journals window to save your report setting either
remotely or locally.

Saving Journal Reports Remotely
Saving Journal Reports Remotely

If you have the proper security rights, after specifying the layout for the journal report,
you can save the report on the Financial Management server.
To save journal reports remotely:

1. On the Process Journals page, select Save Remote.
2. Optional: Select Private if you do not want other users to be able to run the report.
3. Click OK.
4. Click Close.

Saving Journal Reports Locally
Saving Journal Reports Locally

You can save reports that you use on a regular basis to your hard drive or to a network
drive. You can then open the reports on the Web and change the columns and filters as
needed.
To save journal reports locally:

1. On the Process Journals page, select Save Local.
The Download Instructions page is displayed.
2. Follow the instructions on the page.

Running Journal Reports
Running Journal Reports

When you run the report, you can select to override the report point of view and style
sheet.
To print journal reports:

1. Open the application and in the view pane, select Documents > Reporting > Journal.
A list of saved journal reports is displayed in the view pane.
2. Select a report.
The Journal Report Override dialog box is displayed.
3. Optional: Select and change the point of view and style sheet.
4. Click OK.

Summary
• Describe the purpose of journals

• Open periods for journal entry
• Create journal templates and journals
• Submit, review and post journals
• View adjusted data
• Create and format journal reports

M O D U L E 7
Calculating and Consolidating Data 18
Overview
Consolidation is the process of gathering data from descendants and
aggregating the data to parent entities. After you enter or load data into
base level entities, you run a consolidation for a selected scenario and
period to aggregate the data through the organization.
• Running Consolidations
• Managing the Review Cycle Using Process Management
• Sharing Data Using Data Synchronization
• Analyzing Data with Smart View
L E S S O N 1 9
Running Consolidations 19
Objectives
• Describe the consolidation process
• Translate financial data into another currency
• Consolidate children by percentages
• Set up Organization by Period
• Consolidate data
Module 7 Calculating and Consolidating Data
Lesson 19 Running Consolidations
Financial Management Business Process
Load Calculate data

and add data Adjust data
Translate &
consolidate
Run and publish financial reports Lock data Approve data
Financial Management Business Process

Data consolidation is one step of the business process for large (or public) companies.
Consolidation is typically performed after data has been collected, calculated, and
adjusted for base-level entities.
You use the consolidation features in Financial Management to consolidate financial
data for reporting and analysis.

Consolidation Overview
NetProfit
Connecticut 20000
Consolidated data
for Connecticut entity
Administration East 6000
Marketing East 5000
Development 4000
EastSales 5000
Consolidation Overview
Consolidation is the process of gathering data from descendants and aggregating the
data to parent entities. Consolidation applies only to the Entity dimension. After you enter
or load data into base-level entities, you run a consolidation for a selected scenario and
period to aggregate the data throughout the organization.
The example shown in the slide displays the consolidated data for the NetProfit account
of the Connecticut entity. During consolidation, the data values from the base-level
entities (Administration East, Marketing East, Development, and EastSales) are rolled up
to the parent-level entity, Connecticut.

Consolidation Process
Processes:
• Run calculation
• Perform currency
translations
• Apply ownership
percentag es US
• Eliminate intercompany
balances
Connecticut
California
Consolidation Process
When you consolidate an entity, processes that are required for the descendants of the
entity run automatically.
• Calculation rules are run for all descendants of the entity for the period being
consolidated and for all prior periods.
• If the data for the child entity and the data for the parent entity are in different
currencies, the data is translated based on the exchange rate. For the child entity,
the translated value is stored in the Parent Currency member of the Value
dimension. The translated value in Parent Currency is rolled up to the parent.
• If the parent’s ownership of the child is less than 100%, the ownership percentage is
applied. Intercompany transactions between entities are eliminated at their first
common parent.

Consolidation and the Value Dimension
[Contribution Total]
[Contribution] [Contribution Adjs]
[P roportion] [Elimination]
[Parent Total]
[Parent] [Parent Adjs]
<Parent Currency Total>
<Parent Currency> <Parent Curr Adjs>
<Entity Currency Total>
<E ntity Currency> <Entity Currency Adjs>
Consolidation and the Value Dimension

During the consolidation process, the value in the Entity Currency member of the child
members may be transformed before being aggregated to the parent. The Value
dimension stores data for the intermediary steps in the transformation. You can display
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
parent was derived.
In the slide, the gray circles indicate the value dimension members that store data.
Keep in mind the following points about the consolidation process:
• 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.

Checking Calculation Status
Checking Calculation Status

Financial Management maintains the calculation status for every Scenario, Year, Period,
Entity, Parent, and Value combination. The calculation status indicates whether data
needs to be calculated, translated, or consolidated.
You can view the calculation status from the Process Control panel or from a data grid.
To check calculation status:

2. Click the Data Grids tab, and select a data grid.
3. On the data grid, click Grid Settings.
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 has changed.
OK SC OK, System Changed. A change may affect the data for the specified Scenario,
Year, Period, Entity, and Value dimensions. For example, a new rules file or
metadata file was loaded. The data itself, such as a value of 10,000, has not
changed. For a dimension member attribute, the number of decimal places
associated with the account was set to two, and requires the value to be changed
to 10,000.00.
OK ND OK, No Data. The calculation was run, but calculations were not run for no data.
CH Needs Calculation. At least one data cell for the specified Scenario, Year, Period,
Entity, and Value dimensions has changed, or metadata parameters or rules have
changed. As a result, because calculation has not been run, other data cells in the
dimension may not be current. For base-level entities, you may have entered the
data cell through data entry or by a data file load. For any entity, the data cell may
have been entered by a journal posting.
TR Needs Translation. The selected Value dimension member is not the entity’s
default currency, and its translated values may not be current.
CN Needs Consolidation. The data for the specified Scenario, Year, Period, Entity,
and Value dimensions may not be current because any of the following items
have changed:
• Data for a child entity
• Data for the entity's default currency
• Metadata parameters or rules
CN ND Needs Consolidation. The parent has no data, but data for a child entity has
changed.
Locked An administrator locked the data for the specified Scenario, Year, Period, Entity,
and Value dimensions. The data can no longer be modified manually or through
calculations.
NoData No data exists for the specified Scenario, Year, Period, Entity, and Value
dimensions.
NoAccess The user does not have rights for the specified dimension member.

Translating Data
USD
Entity Currency = USD
Geographical
EUR
Europe Parent Currency = US D
E ntity Currency = EUR
Translating Data
Translation converts values from one currency to another. When you consolidate,
currency translation occurs only if the parent currency is different from the child currency.
The translated value is stored in the Parent Currency member.
• For Revenue and Expense accounts, values are translated using the rate account
that is specified by the DefaultRateForFlow application setting. If the PVAForFlow
application setting is enabled, the PVA translation method is selected; otherwise the
VAR method is selected.
• For Asset and Liability accounts, values are translated using the rate account
specified by the DefaultRateForBalance application setting. If the PVAForBalance
application setting is enabled, the PVA translation method is selected; otherwise the
VAR method is selected.
You may need to translate to currencies other than the parent currency. The Value
dimension contains members for all application currencies.

Entering Exchange Rates
Exchange rate account
The custom dimensions contain

system -defined currenc y members.
In this example, Custom 1 is the
source currency and Custom2 is the
destination currenc y.
Entering Exchange Rates

You maintain currency rates by inputting data to the currency members of the Custom1
and Custom2 dimensions. For each application currency, the Custom1 and Custom2
dimensions contain system-defined currency members. You must input currency rates to
accounts that have the Currencyrate account type.
In data grids, you can enter currency rates by using the following settings:
• Row dimension = Custom1
• Column dimension = Custom2
• Row list and column list = Member lists that contain the application currencies
You translate the currency in Custom1 to the currency in Custom2.

You enter currency rates by using the points of view described in the following table:
Dimension Description
Scenario The scenario to which the currency rate is applied
Year The year to which the currency rate is applied
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
Custom2 Destination currency
Custom3 [None]
Custom4 [None]

Translating Data in Data Grids
E ntities with a currency

different from the one show n in Select translate
to translate data to the
the POV bar show a status of
currency show n in
TR or TR ND until the data is
the POV bar.
translated.
Translating Data in Data Grids

After you have entered the exchange rates, you can translate the currency for an entity
to any application currency in the Value dimension. If the Value dimension is not on the
grid rows or columns, the destination currency is specified in the point of view.
To translate data in data grids:

2. Click the Data Grids tab and select a data grid.
3. Right-click the cell for the currency and select Translate.

Consolidating Children by Percentages
Sample Organization Ownership S tructure
Geographical
100% 100%
100% United States Europe 90%
California Connecticut France Italy
80% 50%
Plant 1 East Sales Plant 2
Consolidating Children by Percentages

By default, parents consolidate their children 100 percent. However, you can specify a
consolidation percentage. The consolidation percentage determines what percent of a
child entity is consolidated to the parent entity.

Ownership Management
System account for consolidation

percentage
You use the Ownership Management page to enter consolidation information for your
child entities:
• Active status
• Consolidation percentage
• Consolidation method
In the slide, the rows list child entities of the entity that you are using as the parent entity
in the point of view.

About Manage Equity Pickup
About Manage Equity Pickup

Normally, investments in subsidiaries are valued at their historical price. However, due to
profit or loss incurred in the subsidiary since the acquisition, historical cost may differ
from the actual value of the investment owned.
During a consolidation, you use Equity Pickup to reflect the current value of the share in
the equity of the subsidiary.
You create entity pick up calculations by defining and deploying rules for the Equity
Pickup rule type in Calculation Manager. Equity pickup functionality enables you to:
• Revaluate the investments owned by a holding company
• Replace the historical value of the investments with its current value
• 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 do
the following:
• Enter ownership percentages to be used for equity pickup calculations. You
reference these percentages in Equity Pickup rules.
• Run Equity Pickup rules.
• Run Equity Pickup reports to show ownership percentages.

Setting Up Organization by Period
Use the Ownership Management page to specify the active

status.
Setting Up Organization by Period

Organization by Period enables you to preserve historical organization structures and
have them coexist in an application with the current organization structure.
Organizational changes may be due to acquisitions, disposals, mergers, or
reorganizations.
In Financial Management, Organization by Period is determined through the use of the
Active system account. The Active account is used as the flag that determines whether
an entity is active or inactive.
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.
• Invalidate cells that are associated with [Proportional] or [Elimination] Value
dimension members for inactive children.
• Return only active entities when Organization by Period is selected for the Entity
dimension.
• Run the ownership calculation routine only for active children. Inactive children are
ignored.

Consolidating Data
Consolidating Data
You run consolidations from the Consolidate options list on the Process Control Panel
and data grids. You can use the Task Automation functionality to automate the process.
When a parent is consolidated, all descendants of the parent are also consolidated.
If you consolidate data for a period and the data for prior periods has not been
consolidated, the data for the prior periods is also consolidated.

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
entity that has a status of CN, CN ND, CH, TR, or TR ND.
Consolidate is the most efficient option because only entities that require
consolidation are updated.
Consolidate All Available for any parent entity, regardless of its status.
Consolidate All consolidates all intersections of the dependants, whether
data exists or not.
The system also executes any calculation rule that exists for the dependent
entities. This option is useful when an update from prior periods is required
or when an entity with no data needs to be populated using allocations.
Consolidate All Available for any parent entity, regardless of its status.
With Data
Consolidate All With Data consolidates every dependent entity that
contains data, regardless of its status.
The system also executes any calculation rules for the dependent entities.
When a consolidation starts, the consolidation progress bar is automatically displayed in

a separate window. You can view information about the completion status of the
consolidation, the start time, and the point of view. The consolidation progress bar
enables you to perform other tasks while the consolidation is running, without starting a
new session. You can stop a running consolidation by clicking the red circle icon in the
Stop Task column.
dimension.
ignored.
• 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.
• Invalidate cells that are associated with [Proportional] or [Elimination] Value
dimension members for inactive children.

dimension.
ignored.

Summary
• Describe the consolidation process

• Translate financial data into another currency
• Consolidate children by percentages
• Set up Organization by Period
• Consolidate data

L E S S O N 2 0
Managing the Review Cycle Using

Process Management 20
Objectives
• Describe Process Management and phased submissions
• Enable Process Management
• Set up phased submission processes
• Process and validate units
• Start the review cycle for process units
• Lock process units
Lesson 20 Managing the Review Cycle Using Process Management
Process Management Overview
Use Process Management to review, promote, submit,

approve, reject, and publish process units.
Review Promote Submit Approve Publish
Reject
Process Management Overview

Process Management is the management of the review and approval of financial data.
You can use Process Management to submit budget plans and have them approved
efficiently, and to transfer ownership of data. In a centralized environment, you can also
use Process Management to provide review control and to ensure data privacy.
If Process Management is enabled for a scenario, validation checks are performed for
each process unit as the data moves from one level to the next. Validation checks are
defined by the administrator to ensure that accounts are in balance.

Process Units
Example
• Scenario Actual
• Year 2005
• Period January
• Entity West Sales
• Value USD
Process unit
Process Units
For the purpose of review, data is organized into process units. A process unit is the
combination of data for a specific Scenario, Year, Period, Entity, and Value dimension. In
the Value dimension, you can select Local, Translated, or Contribution data.
During the review cycle, users perform actions on process units, such as promote,
submit, approve, reject, and publish.

Process States
Every process unit has one of the following states.
Not Started
First Pass
Review Level 1, 2,…
Submitted
Approved
Published
Process States
Process units pass through a number of process states during the review cycle:
Task Description
Not Started The review supervisor has not yet started the process unit, and only the
supervisor can enter data.
First Pass The process unit is started and is in the initial stage for data to be
entered by users with the proper access rights.
Review Level 1-10 The process unit is at the designated review level.
Submitted The process unit was submitted and is ready for final approval.
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

perform.
• Use security roles to aid compliance with Sarbanes-Oxley,
especially requirements imposed by Section 404.
Reviewer 1 Reviewer 2 Submitter Review

Supervisor
Process Management Security Roles

The actions that users can perform are determined by their assigned security roles:
Security Role Description

Reviewers 1 through 9 Can promote a process unit to the next level or reject it. After a
reviewer promotes a unit the next level, data for that unit becomes
read-only for users at the current level.
Reviewer 10 Can reject a process unit, but cannot promote it because there is no
next level available. To move a process unit to the Submitted level
for final approval, Reviewer 10 must be a Submitter.
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.

Security Role Description

Review Supervisor Has access rights to start a process unit that allows input to the
entity’s data. Can also approve and publish the data.

Enabling Process Management
To set up Process Management:

• Perform the following actions for the Scenario dimension
member:
– Select Y for the Enable Process Management attribute.
– Specify the phased submission start year.
• Enter the validation account in the ValidationAccount field
in the Application Settings.
• Assign security roles to users.
• Assign security classes to users (Promote access, alerts).
Reviewe r 2
Enabling Process Management

Before you can use the Process Management option, you must enable scenarios in the
Dimension Library. The system performs validation checks for each process unit as the
data moves from one level to the next.
When you select a single cell, Process Management is available only for the input
frequency of the scenario. For example, if the input frequency is months, Process
Management is available when you select January, but it is not available when you select
a quarter, such as Q1. In addition, if you select multiple cells and your selection includes
a data cell in which Process Management is not supported, the option is not available.
For instructions on enabling scenarios in the Dimension Library, see Lesson 7, Setting
Up Entities , Calendars, and Scenarios.
For instructions on configuring validation account settings, see Lesson 5, Creating
Application Views.

About Phased Submission
Phased Submission has:

• Flexible assignment of accounts, customs, and ICP
dimensions
• Support for 99 submission groups
• 9 submission phases with different validation accounts
• Enhanced Process Management module to support
multiple-phase submission
Expenses Income Liabilities Assets
Phase 4 P hase 3 Phase 2 Phase 1
About Phased Submission

Because process unit data could be related to hundreds of accounts, reviewers and
approvers may have difficulty effectively analyzing the data. With submission phases,
you can divide a process unit into submission groups defined by account, custom, and
ICP dimensions. You then assign submission phases to the submission groups and
place the groups in hierarchical order to publish in Process Management.
For example, in the Actual scenario, you might submit the Balance Sheet and Profit/Loss
accounts for review in Phase 1, and supplemental data in Phase 2. In the Budget
scenario, you might submit Intercompany data in Phase 1, Balance sheet and Profit/Loss
accounts in Phase 2, and supplemental data in Phase 3. With the process unit divided,
smaller chunks of data are published, giving reviewers and approvers tighter quality
control.

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.
• You cannot assign the same group to multiple phases in the same period. For
example, you cannot assign Groups 2 through 5 to Phase 1, and Groups 3 and 8 to
Phase 2, because Group 3 cannot be assigned to Phases 1 and 2 in the same
period.
• If you move all groups from one submission phase to another, the original phase is
cleared entirely from the system for the specified scenario and period.
• You can skip submission phase assignments. For example, you can assign groups to
submission Phases 1 and 3 without assigning groups to Phase 2.
• During the review process, you can promote each submission group in the process
unit rather than the entire Process Unit.
• Groups not assigned to a submission phase are not considered part of the review
process.
• Base accounts do not inherit submission groups from parent accounts.
• Parent accounts do not assume submission groups from their children.
• A blank submission group defaults to Submission Group 1.
Submission Phase Guidelines

• You must modify application and dimension metadata files to use submission
phases.
• The maximum number of submission phases allowed in the review process is 9.
• Submission phases can vary by period and scenario.

Process for Setting Up Phased Submissions

Assign Validation Accounts to
Set Application and Metadata At tributes
Submission Phases
Validation Account
Phase 1 – Balance Sheet
Phase 2 – Supp. Data
Phase 3 – Income Stmt.
Assign Submission Groups to

Set Up Submission Groups
Subm ission Phases
Submission Phases
Phase 1 – Balance Sheet
Phase 2 – Supplemental Data
Phase 3 – Income Statement
Process for Setting Up Phased Submissions

You perform these tasks to set up submission phases:
1. Set the application and dimension metadata attributes to use submission phases.
2. Assign validation accounts to submission phases.
3. Assign submission groups to dimension members.
4. Assign submission groups to submission phases.

Setting Application and Metadata Attributes
These metadata attributes are available for submission phases:
Set Application and Metadata Attributes
Setting Application and Metadata Attributes

By default, the setting for submission phases is turned off, and the administrator must
enable phased submissions in the application view:
UseSubmissionPhase=Y/N
The administrator must then define which dimensions (Account, Custom 1-4, and ICP
Members) will be enabled for Process Management. At a minimum, at least one
dimension must be enabled.
For example, if the application needs submission only by accounts and not for Custom 1
to 4 or ICP dimensions, you can select the SupportSubmissionPhase setting only for
accounts.
For instructions on setting application and metadata attributes, see Lesson 5, Creating
Applications.

Assigning Validation Accounts

to Submission Phases
Validation Accounts
Assigning Validation Accounts to Submission Phases

You assign validation accounts to submission phases to ensure that the value equals
zero before a process unit is promoted to the next review level. Financial Management
application settings include nine validation accounts for each submission phase.
NOTE
If a validation account is not set for a submission phase, no validation needs to be
done for that phase. You can use the same validation account across multiple
submission phases.
For instructions on assigning validation accounts to submission groups, see Lesson 5,

Creating Applications.

Setting Up Submission Groups
Set Up Submission Groups
Setting Up Submission Groups

For each application, the administrator must decide which dimension members to
include in a submission group.
In the metadata file, you set the following attribute for submission groups:
SubmissionGroup=0 to 99 or <blank>
Notes:
• The default is blank. A <blank> value defaults to the value of 1.
• If you set the submission group to zero, the account is not included in the review
process.
• 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.
The following example shows dimension members categorized into submission groups:
When a submission group has an assignment of 0, the account does not require a review
process.
Accounts Submission Groups
HistData 0 0
Cash 1
Invest 1
ICRec 2
ICPay 2
Liability 3
Equity 8
Revenue 4
Expense 4
C1 (Product) Submission Group

[None] 1
Golf Balls 5
Tennis Balls 6
Soccer Balls 7
NOTE
For the dimensions that support phased submission (Accounts, Custom 1-4, and
ICP), you should include every member for the dimension in a submission group
(0 to 99).
For instructions on setting submission groups, see Lesson 5, Creating Applications.

Assigning Submission Groups
Assignm ent
Display setting
to display 1 -9
phases
S ubmission
groups
Assigning Submission Groups

Administrators can assign submission groups to each of the submission phases. The
assignment applies only to the scenario that supports Process Management. If a group is
not specified, process management is not applied to the dimensional members within
that group.
You can display and manage submission phases using the “Manage Submission
Phases” task. This task displays if you enable the UseSubmissionPhase application
setting in the metadata file. You must also be assigned to the administrator or Review
Supervisor security role.
To access the Manage Submission Phases window:

1. Click the Browser view.
2. In the view pane, select Tasks > Data Tasks > Manage Submission Phases.

3. 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
a submission phase, you can specify 1-5, 7-8.
• 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.
NOTE
All groups belongs to Submission Phase 1 until you change their
assignment.

Security Access for Process Units
You access data in a process unit based on a combination of

the following items:
• Your assigned security role
• Your access rights to the process unit (through security
classes)
– None
– Read
– Promote
– All
• The current review level of the process unit
Security Access for Process Units

Access rights for process units can be None, Read, Promote, or All.
Access Description
None No access to the process unit
Read Ability to view only data for the process unit
Promote Ability to view data and promote an entity without All access
All Complete access, including viewing and modifying data

Viewing Process Unit Status
Click a process unit
Process Control tool bar
Submission phas e
Process unit status
Viewing Process Unit Status

You view the status for process units on the Process Control panel. The panel contains a
point of view with the Scenario, Year, and Period dimensions. If you enabled submission
phases, the review level for each process unit is stored by submission phase.
Tasks:
• Access the Process Control panel: In the view pane, select Tasks > Data Tasks >
Process Control.
• Specify the displayed entities to display: From the Entity list, select a member list.
• Set the Value dimension member: From the Data View drop-down list, select Local,
Translation, or Contribution.

Process control toolbar:
Button Description
Options for displaying, filtering, and sorting
Refresh grid—Refreshes grid after process control actions.
Manage Process
• Start
• Promote
• Submit
• Approve
• Publish
• Sign Off
• Reject
Consolidate options
• Consolidate
• Consolidate All
• Consolidate All With Data
• Calculate Contribution
• Force Calculate Contribution
Calculate options
• Calculate
• Force Calculate
Translate options
• Translate
• Force Translate
Summary views
• Review Level Summary
• Calculate Status Summary
Rates—Link to a predefined Web grid with rate data (The grid label for the
predefined Web grid must be named Rates.)

Button Description
Page Up and Page Down

Process Control Panel Options
List view
Process Control Panel Options

You use the Process Control Options dialog box to specify how process unit status is
displayed. You can display entities in a flat list or as a tree hierarchy. Use the hierarchy
only if you select the [Hierarchy] system member list. All other member lists are
displayed as a flat list. In tree hierarchy view, row sorting or filtering is unavailable.
Tasks:
• Set display options for the Process Control panel: On the Process Control toolbar,
select Options.
• Expand and collapse a hierarchy (tree view only): Next to an entity, click the plus (+)
or minus (-) sign.

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:
• Filter by review level, such as First Pass, Review Level 1.
• Filter rows by validation status, such as Pass Only or Fail Only.
• Filter rows by calculation status, such as OK, CN, or TR.
Entity View
You can view entity information using the entity label, the description, or both. The
default setting is to display the label.

Viewing Status for Multiple Submission Phases
Use the Columns tab to select phases.
Viewing Status for Multiple Submission Phases

You use the Columns tab of the Process Control Options dialog box to select the
submission phases for which you want to view status. You also select the review and
status information for which you want to include columns.

Viewing Status for All Periods
Viewing Status for All Periods

The Columns tab of the Process Control Options dialog box enables you to view either a
single period or all periods. When you choose all periods, you can view status for only
one submission phase at a time, and you must choose to view either the Process Review
Level or Calculation Status.

Validating Process Units
A check mark is displayed This column indicates

if both the Validation whether there are
account and the unposted journals.
calculation status are OK.
Validating Process Units

Process units can be promoted only if their calculation status is OK or NODATA and the
validation account amount is equal to zero. The Pass/Fail column displays icons to show
whether these conditions are met. If the calculation status is OK or NODATA and the
validation account amount is equal to zero, a check mark is displayed in the Pass/Fail
column, indicating that the unit is ready for promotion. If the process unit fails, an X is
displayed in the Pass/Fail column.
If the process unit fails, you must perform calculation in the current period to ensure that
the data is valid for promotion. After calculation, if the validation account is equal to zero,
the calculation status is updated to OK and the status of the column changes to Pass.

The journal status column displays the status of journals. The column title varies based
on the member selected for data view:
Data View Column Title

Local The column displays the status of Entity Currency Adjustments (ECA).
Translation The column displays the status of Parent Currency Adjustments (PCA).
Contribution The system displays a column for the status of Parent Adjustments (PA)
and a column for Contribution Adjustments (CA).
In the journal status column, a green flag indicates that there are no unposted journals. A
red flag indicates that unposted journals must be posted for the entity. However,
unposted journals does not prevent an entity from being promoted.
When you hover the cursor over a flag in the journal status column, the number of
unposted journals is displayed. When you click the flag, the Journals module opens so
that you can view the unposted journals for the selected process unit. You can then post
the journals that need to be posted.

Validation Accounts Overview
Validation accounts:
• Must have an account balance equal to zero before a
process unit can be promoted to the next review level
• Must have a formula defined in the rules file to generate its
balance
**********************************************************************
'Validation Rules
'Validation Rules will only run at the legal entity level
'User defined field # 1 has been set to LEGAL for all legal entities
'****** ********* ********** ********** *********** ********* ********** *****
If HS.Entity.UD1("") = "LEGAL" then

If HS.Year.Member > 2007 Then
HS.EXP "A#V7900 = A#7900"
Validation account
100 100
Account calculation = Assets – (Liabilities+ Equity)
Validation Accounts Overview

Validation accounts are used as a balancing mechanism. You use rules to customize
validations in Process Management.
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
LEGAL to define and identify the legal entities.
If you are using phased submissions, you can have separate validation accounts for
each submission phase. Financial Management application settings include additional
validation accounts that you can use for each submission phase:
Validation Account= (current validation account; now used for Submission Phase 1)
Validation Account2 =<valid account> (for Submission Phase 2)



Viewing Validation Account Detail
Viewing Validation Account Detail

The Pass/Fail column is linked to the Validation Account Detail page so that you can
view additional details about calculation status and validation account information. This
link displays all children associated with the validation account and balances. When you
drill down to the detail screen, the system displays the following information:
• Calculation status for Entity Currency, Entity Curr Adjs, and Entity Curr Total
• Validation account amount for Entity Currency, Entity Curr Adjs, and Entity Curr Total

Calculating and Consolidating Data
Consolidate
options
Calculating and Consolidating Data

If you need to promote a process unit that does not have the correct status (for example,
CN or CN ND), you can calculate or consolidate the process unit directly from the
Consolidate options drop-down list on the Process Control panel. You must have the
appropriate security access.

Moving Process Units Through the Review Cycle
You use the Manage Process options to move process units

through the review cycle.
Manage Process options
Moving Process Units Through the Review Cycle

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
unposted journals can be promoted.
When you promote parent entity data to the next process level, validation checks are
performed to verify that the child entities are at the level to which you are trying to
promote the parent. A parent can be promoted only to a level that is less than or equal to
the lowest level of its children.
• To promote process units for review, select the units and select Manage Process >
Promote.

Submission Phases and Review Levels

The review level for each process unit is stored by submission phase. You must promote
each submission phase independently. All rules for promotion to each review level apply.
In addition, there is the following dependency based on the submission phase number:
The review level of a submission phase must be less than or equal to the review level of
the lower-numbered phases in that process unit.
For example, you could divide Income, Balance Sheet, and Supplemental accounts into
three submission groups. The groups for Income and Balance Sheet accounts are
assigned to Phase 1 and the group for Supplemental accounts is assigned to Phase 2.
If the Phase 1 accounts, Balance Sheet and Income, are at Review Level 4, you cannot
promote Phase 2 accounts, Supplemental, to a review level greater than 4. In the same
way, you cannot reject a submission group if it violates the submission phase rule.
The following table describes the options on the Manage Process menu:
Option Description
Start Used by the Review Supervisor to bring data to First Pass. Cells on data entry
forms and grids for a process unit display NOACCESS until the process unit is
started.
Promote Promotes process units for all review levels. After a process unit is promoted for
review, data for the process unit can viewed only by a user with the appropriate
review-level security role. For example, if the process unit is promoted to Review
Level 2, only a user with the Review Level 2 or higher security role can view the
data.
Submit Submits process units for final approval.
Approve Approves process units. A process unit must have a status of OK, OK SC, or NO
DATA to be approved.
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
the data in the process unit.
Sign Off Signs off on process units from Review Level 1 or higher. When a process unit is
signed off, its status does not change.
Reject Rejects process units and demotes them to their previous review level.

Selecting Review Levels
Available
review
levels
Prom ote
current entity
only or
include
descendants
Selecting Review Levels

When you select the Promote option from the Manage Process menu, the Promote
window is displayed. You use the Promote To drop-down list to select the review level. If
the entity is a parent, you can also promote its descendants.

Email Alerts
Email Alerts
If email alerting is enabled for the process unit scenario, Process Management triggers
email alerts based on a change of status for the process unit. Alerts are sent for the
following actions: First Pass, Review Levels 1 through 10, Submitted, Approved, and
Published. Alerts are not generated when the process unit is at the Not Started level or
for the Sign Off action.
The system automatically generates email alerts to the appropriate users for the action,
according to the review level assignments. The system sends email alerts to both the
users at the level before the process control action and to the users at the current level
after the action.

For example, User A and User B have Reviewer 4 role access, and Users C and D have
Reviewer 5 role access. When the process unit is at Level 4 and is promoted to Level 5,
Users A and B receive email alerts because they are at Level 4 before the promote
action. Users C and D receive email alerts because they are at Level 5, which is the
current level after the promote action.
When the email alert is generated, the user who performed the action receives a
confirmation email that contains the action performed, the process units affected as part
of the action, and the names of the users receiving the email alerts for each process unit.
Requirements for email alerts:
• An SMTP mail server must be specified on the Web Server tab of the Financial
Management Configuration Utility.
• The alerting process uses the email addresses that are stored in your external
authentication files. To receive email alerts, users must be on either LDAP or
Microsoft Active Directory; external authentication does not support email addresses
from NTLM providers.
• The Supports Process Management-A attribute, which is set in the Metadata
Manager, must be enabled for the process unit scenario.
• The user must have the Receive Email Alerts from Process Management user role.
• The user must have email alert access to the security class for the process unit entity
and scenario.

Viewing Review History in Data Grids
Viewing Review History in Data Grids

The Process Flow History window displays process history by date and time, user, action
taken, process level, and comments.The information in this window cannot be changed
or deleted. It is automatically updated as units are processed by individual users.
• To view review history, right-click an entity and select Process Flow History.

Viewing Process Level in Data Grids
Viewing Process Level in Data Grids

You can perform Process Management tasks in data grids.
• To view process status, in the Grid Settings dialog box, select Process Level.

Managing Process Unit States in Data Grids
Managing Process Unit States in Data Grids

You can promote, submit, approve, publish, and lock a process unit from a data grid by
selecting one or more cells, right-clicking the cells, and selecting Manage Process.
Criteria for Phased Submissions in data grids:
• If a cell is selected in a data grid and Process Management is selected, the system
determines the submission phase that applies to the cell.
• You can have one review status for each submission phase. When cells are
promoted, you promote all cells for that submission phase.

Locking and Unlocking Data

Submit Data for Review
Approve/Publish Data
Lock Data
Change display settings
to calculation status.
Locking and Unlocking Data

After publishing submitted data, you may need to lock the data for the entity to prevent
modifications. Locking prevents changes to the data for a selected category, year, and
period.
NOTE
You can lock and unlock data only in a data grid.
• To Lock data, right-click one or more cells and select Lock.

• To lock data for an entire entity hierarchy, select only the top parent. When you lock
a parent entity, the descendants of the parent are also locked.
• To unlock data, right-click one or more cells and select Unlock. When unlocking data,
you must unlock a parent entity before you unlock its children.

You can lock data only if the following conditions are met:
• The calculation status for the entity must be OK.
• All prior periods must be locked.
• The validation account for the Entity Currency and Entity Currency Adjs members of
the Value dimension must be zero.
• If the current scenario is enabled for Process Management, the process unit status
must be Published.
Process for Locking Phased Submissions
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.”
• All validation accounts have the appropriate phases and a zero value.

Summary
• Describe Process Management and phased submissions

• Enable Process Management
• Set up phased submission processes
• Process and validate units
• Start the review cycle for process units
• Lock process units


L E S S O N 2 1
Sharing Data Using Data

Synchronization 21
Objectives
• Describe data synchronization
• Create mappings and synchronizations
• Set data synchronization filters
• Validate data synchronizations
• Execute data synchronizations
• View data flows
Lesson 21 Sharing Data Using Data Synchronization
Data Synchronization Overview
NA Consol Application Sales Report Application
Mapping table
Sales revenue Sales revenue
Data Synchronization Overview

You use data synchronization to transfer data automatically from a source application to a
destination application. Data synchronization provides filters for selecting specific data
needed for other applications. You can schedule data synchronization to run during off-
peak business hours, and you can view data flows between applications after data is
synchronized.
For example, you want to transfer data from one application, NA Consol (source
application) to another, Sales Report (destination application). NA Consol is the master
application where all the data is stored for consolidations. It contains both balance sheet
and income statement data. Sales Report meets sales reporting needs.
The data needed to generate these reports resides in the Net Income hierarchy in the
Account dimension of the NA Consol application. You use data synchronization to
transfer the data from the Net Income hierarchy of the NA Consol application to the Net
Income hierarchy of the Sales Report application.

Creating Mapping Tables
To create a mapping table, you specify source and destination

dimensions.
Data is retrieved from the The destination

source application. application receives the
data.
Creating Mapping Tables

In order for the data synchronization to transfer data for a dimension, the dimension
member names in the source and destination applications must match.
If the member names do not match, you must create a mapping table. For example, you
could map data from the Sales member in the source application to the Revenue
member in the target application.
After creating a mapping table, you can insert it into data synchronizations.
To create mapping tables:

1. Select Navigate > Administer > Data Synchronization to display the Data Synchronization
page.
2. Select File > New > Mapping Table to display the Mapping Table Designer.

3. Select the source application, the destination application, and the dimension for
which you want to map data.
4. Click Next.
5. For each member to be mapped:
a. In the source dimension, select the member.
b. In the destination dimension, select the member to which the source dimension
should be mapped.
6. Repeat step 5 for each member to be mapped.
7. Click Next.
8. Click Validate and confirm that the mapping between the two applications is correct.
9. Click Next to display the Mapping Properties page.
10. Enter the name and description of the mapping, and click Finish.

Data Synchronization Process
You use a wizard to create a data

synchronization.
Data synchronization toolbar
Insert
Execute
mapping
synchronization
table
Validate
synchronization
Data Synchronization Process

1. Specify the source type, data source, and destination application.
2. Map source dimensions to destination dimensions.
3. Optional: Create filters for source dimensions.
4. Optional: Apply filter criteria.
5. Optional: Insert mapping tables.
6. Save synchronization.
7. Validate synchronization.
8. Execute synchronization.

Specifying Source and Destination
The New Synchronization Wizard has three pages:
Data Synchronization P age Description

Source Type Data source type that is sending the data.
Select Sourc e Object or application that is receiving the

data.
Select Destination Application that is receiving the data. The
target application can be a Financial
Management or a P lanning application.
Specifying Source and Destination

You use the New Synchronization Wizard to specify the source type, data source, and
destination for a synchronization.
Data source types:
• Financial Management or Planning application
• Interface table
• Flat file

To specify source and destination:

1. In Workspace, navigate to Administer > Data Synchronization.
2. Select File > New > Synchronization.
The New Synchronization Wizard is displayed.
3. Under Source Type, select a source type, and click Next.
4. Under Select Source, select a source, and click Next.
5. Under Destination, select a destination application, and click Finish to display the
Dimension Mapping page.

Mapping Source Dimensions

to Destination Dimensions
Mapping Source Dimensions to Destination Dimensions

After you define the destination application, the Dimension Mapping page is displayed.
For each dimension in the source, you specify a matching dimension in the destination
application. For example, you map for the HFM_Value dimension in the source to the
Value dimension in the destination application.
To map dimensions:
• Drag a dimension from the source application to the destination application.
A link is displayed as a line connecting the source dimension to
the destination dimension.

Creating Filters for Source Dimensions
Creating Filters for Source Dimensions

By default, data for all dimension members of each dimension is transferred when you
synchronize data. You can create filters so that only member data needed in the
destination application is transferred from the source.
For instance, the Sales Report application needs to receive data from the NA Consol
application. However, Sales Report needs data only from the WestSales entity. By
applying a filter to the Entity dimension in NA Consol, you transfer only the data for
WestSales.
To create filters:
• In the Dimension Mapping page, right-click a source dimension and select Create
Filter to display the Filter Criteria dialog box.

Applying Filter Criteria
Select members in the

Member Selector dialog
box.
Applying Filter Criteria

After creating filters, you set filter criteria for the selected member:
Filter Criteria Description

Equal Filter what is equal to the dimension name in the selector field.
Like Filter to perform pattern-matching functionality on partial dimension names.
To apply filter criteria:

1. In the Filter drop-down, select a filter criteria.
2. In the Selector field, click the Explore icon.
The Member Selection page dialog box is displayed.
3. Select the members whose data you want to transfer in the synchronization, and
click the right-arrow button.

4. Click OK.
NOTE
After the filter is applied to the dimension, a filter icon is inserted next to the
dimension name in the Dimension Mapping page.

Inserting Mapping Tables
Insert Mapping Table

button
Inserting Mapping Tables

The last step before validating data synchronizations is to insert mapping tables. Not all
data synchronizations require mapping tables. You insert them for those applications
that are not able to link dimension to dimension, because the dimension member names
differ from one application to the other.
Data synchronization tables display two types of lines that link from the source to the
destintation:
• Dashed line—Inserted mapping table
• Solid line—Linked dimension members without inserted mapping tables
To insert mapping tables:

1. On the Data Synchronization toolbar, click Insert Mapping Table.
2. From the list of mapped tables, select the mapped table and click OK.

Saving Data Synchronizations
Save S ynchronization
button
Saving Data Synchronizations

After creating filters and inserting mapping tables you save the data synchronization.
To save data synchronizations:

1. On the Data Synchronization toolbar, click Save.
The Save Data Synchronization page is displayed.
2. Enter the name and description of the synchronization, and click OK.
3. Select Navigate > Administer > Data Synchronization.
4. Optional: On the toolbar, click the Refresh icon.
The synchronization is displayed on the Synchronization page.

Validating Data Synchronizations
Validate Synchronization button
Validating Data Synchronizations

When you validate a synchronization, the data is retrieved from the source application
and transformed according to mapping rules. The data is not written to the destination
application so that the source and destination can process the request and resulting data
and generate errors. You can quickly identify issues and fix them.
To validate data synchronizations:

1. In Workspace select Navigate > Administer > Data Synchronization.
The newly created synchronization is displayed.
2. On the Data Synchronization toolbar, click Validate.
The Data Sync Validation Options dialog box is displayed.

3. Optional: Define a calculation to perform on the data if the values from the source
are on a different scale than the destination.
a. In the Operator text box, enter a standard mathematical operator.
b. In the Value text box, enter a numeric value.
4. Click OK.

Executing Data Synchronizations
Execute S ynchronization button
Executing Data Synchronizations

When you execute a synchronization, the data is retrieved from the source application,
transformed according to mapping rules, and pushed to the destination application.
When you execute data synchronizations, you can specify a calculation to apply to the
data being transferred. For example, if you are transferring data from Actual to Budget,
you could specify that the values should be increased by 10%.
To execute synchronizations:
1. On the Data Synchronization toolbar, click Execute.
The Data Sync Execution Options dialog box is displayed.
2. Optional: Define a calculation to perform on the data.
a. In the Operator text box, enter a standard mathematical operator.

b. In the Value text box, enter a numeric value.

3. Click OK.

Viewing Data Flows
Viewing Data Flows

After setting up data synchronization between applications, you can view the
applications in a graphical representation that shows the data flow from the source
application to the destination application.
• The Source Applications label is displayed in a rectangular box whose right side is
shaped like an arrow that points outward toward the destination application. The
arrow indicates that the data is flowing from the source application to the destination
application.
• The Destination Applications label is displayed in a similar box, only the arrow on its
left points inward to the destination application. The arrow indicates that the data
coming from the source is being received by the destination application.

To view data flow:

1. Select Navigate > Administer > Application Library.
2. Right-click the application and select Data Flow.
You can view data flows from either the source application or the destination
application.

Summary
• Describe data synchronization

• Create mappings and synchronizations
• Set data synchronization filters
• Validate data synchronizations
• Execute data synchronizations
• View data flows

L E S S O N 2 2
Analyzing Data with Smart View 22
Objectives
• Describe Smart View
• Connect to data sources
• View data with Ad Hoc Analysis tool
• Add formulas and worksheets
• Work with data forms in Smart View
• Create functions in Smart View
Lesson 22 Analyzing Data with Smart View
Smart View Overview
• Smart View is a Microsoft Excel add-in that enables you to

use the familiar Excel interface to view and analyze data.
• Using menu-driven options in Microsoft Office, you can
retrieve Financial Management data into Office.
Smart View Overview

Smart View provides the framework to integrate Microsoft Office products with Financial
Management, Planning, Financial Reporting, and Web Analysis information.

Smart View Installation Components
• Server-side provider
• Client component
Smart View Installation Components

Smart View consists of two parts: a provider that is installed on the Financial
Management Web server, and a client component. The client component must be
installed in order for end users to access the Hyperion menu in Microsoft Office.

Typical Business Process for Smart View
V iew and analyze data in

a spreadsheet.
Connect to a data source.
S ave spreadsheet and submit data

back to Financial Management
(optional).
Typical Business Process for Smart View

1. Connect to the Financial Management data source.
2. View and analyze data in the Microsoft Excel spreadsheet.
3. Optional: Send data back to Financial Management to update the database.

Connecting to Data Sources
Use Data Source Manager to establish a connection to a

Financial Management data source.
Switch
To
Connecting to Data Sources

You use Data Source Manager to manage data source connections. A connection is a
communication line between users and the data source, regardless whether the data
source is connected to or disconnected from the provider server.
You can add, delete, and modify connections for each Excel instance. These
connections have no relationship to worksheets. You can establish multiple connections
for each Excel instance.
To connect to a data source:

1. In Smart View, select Hyperion > Data Source Manager.
2. From the Switch To drop-down list, select Independent Provider Connections.

3. Double-click the application you want to connect to.

The Connect to Data Source dialog box is displayed.
4. Enter your user name and password, and click Connect.
NOTE
You can tell whether a data source is connected by selecting Hyperion >
Active Connections and confirming that a check mark is displayed for the data
source.

Viewing and Analyzing Data with

the Ad Hoc Analysis Tool
• Use the Ad Hoc Analysis tool to
analyze data from a data source.
• After you connect to a data source and
open a worksheet, open the default
grid to begin analysis. (The default grid
is specific to the data source.)
• Drag and drop dimension members
directly onto the spreadsheet.
• Create free-form ad hoc queries by
typing member names directly on the
spreadsheet.
Viewing and Analyzing Data with the Ad Hoc Analysis Tool

With the Ad Hoc Analysis tool, you can perform the following actions:
• Create a grid
• Zoom in and out on a dimension
• Nest dimensions in columns and rows
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 displays 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 using the Cell Styles tab of the
Options dialog box, which you access from the Hyperion menu.

Changing the Point of View
Use the POV toolbar to change the point of view.
Changing the Point of View

You can use the point of view (POV) toolbar to change the POV settings for a grid.
If, in a worksheet, you want to save changes that you made to the POV settings, refresh
the worksheet before you save it.

Changing Members
Changing Members
To change members, you use the Member Selection dialog box.
To change members:
1. In Smart View, select Hyperion > Member Selection to display the dialog box.
2. In the Dimension drop-down list, select a dimension.
3. Optional: In the Filter drop-down list, select a filter.
4. In the Members area, select a member, and click the right -arrow button.
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
• To drill down or up, double-click the

member or use the toolbar icons.
• Options determine the next level for
drilling down.
Drilling Down and Up Dimension Hierarchies

Use drill down and drill up (also known as zoom in and zoom out) to expand or contract
to the next level.
You can also double-click a dimension member to expand to the next level, to all levels,
or directly to the bottom level.

Pivoting Dimensions
Drag dimensions from the POV

toolbar to the rows or
columns.
Right-click and drag to pivot

row or column dimensions or
to move them to the POV
toolbar.
Pivoting Dimensions
You can change the dimensions on the grid. On the POV toolbar, drag a dimension and
drop it on a row or column. The dimension is moved to the outermost row or column on
the opposite axis.
You also can pivot a dimension from the rows to the columns or the POV toolbar, or from
the columns to the rows or the POV toolbar.
The grid must have at least one dimension on rows and one dimension on columns.
Before you remove a dimension from a grid, you must first pivot the replacement
dimension onto the grid.
To pivot dimensions:
• Right-click the dimension and drag it to the destination.

Displaying Cell Text
Displaying Cell Text

If a worksheet cell contains cell text, you can view it on an Ad Hoc grid. Cells that contain
text are indicated by dark blue borders.
To display cell text:

• Right-click the cell, and, in the Hyperion menu, select Cell Text.

Adding Formulas and Formatting
Cell with formula
Use the Capture

Formatting m enu
command to
preserve data
cell form ats.
Adding Formulas and Formatting

You can add Excel formulas and formatting to data cells. For example, you can add a
formula to the Budget column. The formula calculates the Budget column values based
on the values of the Actual column plus a percentage. Or you can format data cells to
display a currency symbol or to display negative numbers in red. When you submit data,
the values calculated by formulas are saved to the database.
Formulas that you add to data cells are automatically preserved, even when you perform
these actions:
• Refreshing the Ad Hoc grid
• Zooming in or zooming out (referential formulas are updated with their new relative
positions)
• Using the Keep Only or Remove Only function
Formulas are not preserved if you change the grid by any of these actions:

• Pivoting data (for example, by selecting Pivot to POV or Pivot to Column)

• Clearing the grid
Rows and columns that you insert in the grid are preserved. For example, you can insert a
column for rates and enter salary rates. In the Salaries row, to calculate salary increases,
you can use an Excel formula to reference the values in the rates column.
To preserve formatting of data cells, you must apply the Capture Formatting menu
command (on the Hyperion menu) to the cells. If you apply formatting to cells other than
data cells (for example, row and column heading cells), the formatting is not preserved.

Creating Free-form Worksheets
You can create ad hoc queries quickly by typing member labels

on the worksheet.
Creating Free-form Worksheets

Free-form worksheets enable you to quickly create an ad hoc analysis by typing member
labels on the worksheet. This free-form mode is especially useful when you are familiar
with the dimensions and members in the application. When you construct an analysis by
entering names directly on a worksheet, Smart View queries the connected data source,
interprets the member names that you entered, and creates a default view that is based
on the location of the labels.
The layout for free-form entry requires you to type the member labels for the row
dimensions to the left and one row below the member labels for the column dimensions.
When you select Refresh from the Hyperion menu, the data is retrieved from the
database.
Guidelines:
• 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.

Calculating, Translating, and Consolidating

in Smart View
• These features work the same way in Smart View as they
do in Financial Management.
• The same security rules apply in Smart View.
• When you are using these features in Smart View, use the
Refresh option to ensure that you are looking at the latest
data.
US D
GBP
Calculate data Translate data Consolidate data
Calculating, Translating, and Consolidating in Smart View

Users who have the proper access can calculate and translate data. Users can also view
and execute consolidations, and view calculation or process management status.
To view calculation and process management status:

1. In Smart View,select Hyperion > End User Options.
The End User Options dialog box is displayed.
2. Select the Display tab.
• Select Calculation Status
• Select Process Management Status

Submitting Data
Submit data back to Financial

Management
Submitting Data
After calculating, translating, or consolidating data, you can submit the data to ensure
that the data source uses the latest information from the worksheet.
You must have the Load Excel Data security role to submit data to Financial
Management.

Working with Data Forms in Smart View
Working with Data Forms in Smart View

You use the Forms menu command on the Hyperion menu to open data forms that were
created in the Financial Management Web client. You can perform the same range of
functions in Smart View as in the Web client, such as calculating data, adding cell text,
and submitting data.
NOTE
Add Line Item Detail functionality is not supported in data forms that are opened in
Smart View.
When you open a data form in Smart View, the point of view defined for the form is
displayed. You can select dimension members for the dimensions that are designated as
Selectable in the data form definition.

You can add members on data forms opened in Smart View. A red border is displayed
around cells to which you can add members.
To add members to data forms:

1. In Smart View, select Hyperion > Forms > Select Forms.
The Select Form page is displayed.
2. Select a form and click OK.
The Member Selection dialog box is displayed.
• Select the POV members for the dimensions, and click OK.
• Click Cancel.
4. Right-click the cell configured to add members, and select Hyperion.
5. Select Forms.
6. Select Add Member.
7. From the member selector, select the members for which you want to enter data.
8. Click OK.
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.
To open linked forms:

1. In Smart View, select Hyperion > Forms > Select Forms.
The Select Form page is displayed.
2. Select a form and click OK .
The Member Selection dialog box is displayed.
• Select the POV members for the dimensions, and click OK.
• Click Cancel.
4. Select a row that contains linked forms, and right-click in the row.

5. Select HFM Linked Forms, and select the form name.

A new form is displayed in a separate browser window.
6. When finished, click Close.

Functions in Smart View
Use functions to send data from worksheets to data sources

and from data sources to worksheets.
Functions in Smart View

You can use functions to retrieve data from an Excel worksheet and save it to a data
source or to send data from a data source to a worksheet. You can also use functions to
retrieve currency values, display member descriptions and labels, and send and retrieve
cell text.
Functions enable you to bring data from multiple Financial Management applications into
a worksheet.
NOTE
The ad hoc grid allows only one application per worksheet.

Methods for Creating Functions
Manual entry
Function Builder
Methods for Creating Functions

Smart View includes Function Builder, which you use to select functions and members.
To access function features, from the Hyperion menu, select Functions > Function
Builder.

Smart View Functions
These are Smart View functions, along with their counterparts

from the prior Excel add-In.
• HsGetValue = HFMVal
• HsSetValue = HFMLnk
• HsCurrency = HFMCur
• HsDescription = HFMDes
• HsLabel = HFMLab
• HsGetText – Displays cell text
• HsSetText – Sends cell text to the Financial Management
application
Smart View Functions

The following table describes the Smart View functions:
Function Description
HsGetValue For a given POV, retrieves data from a data source
HsSetValue For a given POV, sends values to the data source.
HsCurrency Retrieves the entity currency for the selected members
HsDescription Displays the description for the default POV member
HsLabel Displays the label for the default POV member
HsGetText Retrieves cell text from the data source
HsSetText Sends cell text to the data source

Creating Functions
The Function Builder

provides a graphical
interface for creating
functions. Select a function.
Select members.
Click Add to Function.
Review the function.
Creating Functions
You can create functions manually, or you can use Smart View Function Builder. Its
graphical user interface makes it easy to select the function and dimension members for
the POV. You can view and validate the function before you paste it into a worksheet.
Guidelines:
• If a dimension does not apply to the selected function, the dimension is not available
for selection.
• If you do not select a member for a dimension, the system uses the default POV
members.
• You can use either the member or a cell reference.

Use the POV Manager to define the dimension setting s.
To change
members,
click the Edit
button.
Background
point of view
members.

When you work with functions, the system retrieves and calculates values for the point of
view dimension settings from the data source, unless you specify different settings.
Use POV Manager to set a POV for a particular workbook or worksheet. In functions that
do not include all 12 dimensions, the dimension members specified in POV Manager are
used as the background POV members.
For example, in POV Manager, you can set a dimension member for the custom
dimensions 1 through 4. Once set, these dimensions do not need to be reflected in an
HsGetValue function. Instead, the system relies on the background POV that is supplied
by POV Manager.
To access POV Manager, from the Hyperion menu, select the POV Manager.

Summary
• Describe Smart View

• Connect to data sources
• View data with the Ad Hoc Analysis tool
• Add formulas and worksheets
• Work with data forms in Smart View
• Create fiunctions in Smart View

A P P E N D I X A
Automating Tasks A
Objectives
• Describe the purpose of task automation
• Automate a task
Appendix A Automating Tasks
Task Automation Overview
• Task automation automates tasks commonly performed in

Financial Management.
• Task automation provides designated users the ability to
schedule critical Financial Management tasks to be run as
required.
Task Automation Overview

Task automation provides a method for linking a series of tasks into a taskflow. You can
use task automation to automate tasks that you commonly perform using Financial
Management. To use task automation, you must be assigned the Task Automation user
role.
A-2 Financial Management 11.1.1: Create and Manage Applications

Tasks Available for Automation
The following activities are available for task automation:

• Allocate
• Calculate
• Translate
• Consolidate
• Load and extract journals
• Load and extract data
• Process journals
• Extended analytics
• Process control
Tasks Available for Automation

The slide lists the tasks that are available for automation.
Note that there are a few areas in which automation is not available, specifically, certain
loading tasks such as loading metadata, security, and member lists.
Financial Management 11.1.1: Create and Manage Applications A-3

Uses for Task Automation
A taskflow can be created for the following purposes:

• Translating and calculating all base entities
• Loading data files and consolidating data
• Extracting data from one application and loading it into
another application
• Reconsolidating all prior periods and scenarios
• Regularly consolidating main points of view overnight
during the close process
Uses for Task Automation

The ability to automate loading, calculating, translating, and consolidating tasks
(including notifications) provides an opportunity to improve the efficiency of your monthly
and quarterly closing and reporting business processes.

Taskflow Overview
• A taskflow is a sequence of tasks that you can create in

task automation.
• A typical taskflow is to load, calculate, and consolidate
data.
Calculate
Load
Taskflow Overview
Any user who has the Task Automation role can access, create, and maintain taskflows
that perform required Financial Management operations.

Components of Taskflows
• Stages define specific tasks, such as calculations,

consolidations, data loads, and so on.
• Links tell the system how to proceed after completion of
the step.
Success Success
Stage 1 Stage 2 Stage 3
Links Links
Failure Fail ure
End
Components of Taskflows
A stage describes a step in a taskflow. Each stage has an action, such as load data,
calculate data, and so on. These actions have parameters for which values are supplied
at runtime.
Each stage contains two tabs, except for the first stage, which has three tabs.
• General
• Processing
• Starting Event (first stage only)

Creating Taskflows
Creating Taskflows
You create taskflows by navigating to the Taskflow Listing Summary page. Select New to
create a taskflow. Use the description field to provide detail about the taskflow.

Stage Definition – General Tab
Select Save to save the taskflow definition.
Three
tabs
E nter Name
and Description
Stage Definition—General Tab

The General tab defines the stage name, description, and user ID of the user responsible
for completing the stage. The user can be an initiator, that is, the owner of the first stage
of the taskflow or another user for the other stages.

Stage Definition – Processing Tab
All fields must be

entered.
Stage Definition—Processing Tab

The Processing tab defines the actions to be performed when the stage is run and
defines all required parameters.

Stage Definition – Starting Event
Used to define
the scheduled
times for the
event to occur
Stage Definition—Starting Event

The Starting Event tab defines the event that initiates the taskflow and the scheduled
times for the event to occur. The scheduled time is based on the time of the application
server, not on the time of the local user’s computer.
This functionality is schedule related. You can schedule the taskflow to run according to
a schedule, such as weekly, monthly, at the first of the month, and so on.

Adding Links
Click Add Link to add a link to a stage.
Adding Links
A link is the point during the execution of the taskflow at which the activity in one stage
completes and the taskflow ends or control passes to another stage. A link can be
unconditional, where the completion of one stage always leads to the start of another, or
conditional, where the sequence of operation depends on one or more link conditions.
A link instructs the system about the action to take next. In general, most stages have
two links, Success and Failure.
You can specify that, if the first stage is successful, the system should proceed to the
second stage (receiving stage). For example, if the first stage of LoadData is successful,
the system should proceed to the receiving stage of consolidation.
You can specify conditions for a link. For example, you can add a condition for a
consolidation task (stage), such as Consolidation_Success = = ‘True’.
You must enter two equal signs (= =) after the variable and place single quotation marks
(‘) around the condition that you are evaluating. The value can be True or False.

Testing Taskflows
After the taskflow is created and saved, select the taskflow,

and then click Run Now to test.
Testing Taskflows
You can run a taskflow manually instead of waiting for it to start automatically. You may
want to test a taskflow before the time that it is scheduled to run. Testing enables you to
make adjustments to the taskflow before it actually runs.

Taskflow Status Summary
Taskflow Status Summary

Taskflow Status Summary enables you to check the status of taskflows, including
taskflows that are active, completed, or stopped. You can view all taskflows, or you can
filter the list of taskflows by status or application or by the date or range of dates on which
the taskflow was initiated.

Viewing Taskflow Summary Information
Select the link in the ID column to

view taskflow s ummary information.
Viewing Taskflow Summary Information

In Taskflow Participant Summary, you can drill down on individual taskflows to view
details. Taskflow Participant Summary displays the status for each stage of the taskflow
and the time that each stage was completed. You can see the stages that were
completed successfully and the stages that failed. This information can be used to
troubleshoot the task automation.

Viewing Task Audit Detail
Use the Task Audit page to view and

verify that the tasks have been run.
Use the filters at the top to filter based

on date, task type, and so on.
Viewing Task Audit Detail

You can use Task Audit functionality in conjunction with task automation (especially for
troubleshooting). Task auditing provides information on tasks that have been run.
The filters at the top of the Task Audit page can be used to select certain tasks.

Viewing Data Audit Detail
Viewing Data Audit Detail

Use the Data Audit feature to view data changes performed by users.
Use filters to view the data changes by date range, user, or dimension members.
You must enable dimension members for data auditing by turning on the Enable Data
Audit member attribute. The default is Off.
NOTE
You must have the Administrator security role to use the data auditing
functionality.

Summary
• Describe the purpose of task automation

• Automate a task


A P P E N D I X B
Managing Intercompany Transactions B
Objectives
• Describe the Intercompany Transactions Module
• Open periods for intercompany transactions
• Match intercompany transactions
• Post intercompany transactions
• Create intercompany reports
• Lock intercompany transactions
• Close intercompany periods
Appendix B Managing Intercompany Transactions
Intercompany Transactions Module
Use the intercompany transactions module to enter or load

intercompany transactions at an invoice or transaction level.
Intercompany Transactions Module

Financial Management enables you to track and reconcile intercompany transaction
details across accounts and custom dimensions.
The Intercompany Transactions module provides an efficient way to identify, report, and
reconcile intercompany account differences. With the ability to view the details of
transactions at any time, you can reconcile intercompany account differences frequently
and thus minimize the impact of such differences on the closing cycle. You can also
analyze differences due to real errors in transaction currency or differences due to
exchange rates.
B-2 Financial Management 11.1.1: Create and Manage Applications

Business Process for the

Intercompany Transaction Module
IC = Intercom pany
Create IC Match IC
Open IC perio d
transaction transaction
Generate Perform drill-

Post IC
matchin g through from
transaction
reports account balance
Lock entities Close IC period
Business Process for the Intercompany Transactions Module

The Intercompany Transactions module enables the following business process:
• Create intercompany transaction details at the invoice level.
• Match transactions at the invoice level and match transactions in the transaction
currency as well as in the reporting or parent currency.
• Post transactions
• Create intercompany matching reports
• Drill through an account balance to transactional details from intercompany matching
reports, data grids or data forms.
• Lock entities and close periods to prevent unauthorized input.
Financial Management 11.1.1: Create and Manage Applications B-3

Setup Considerations for Intercompany

Transactions
The following needs to be considered as part of the setup for
the Intercompany Transactions module:
• IC periods must be open.
• Intercompany transaction rules must be defined in the
rules file and loaded into the application (error message
results if rules are not defined).
• The scaling factor affects the display of the transaction
amount.
• Matching tolerances need to be determined.
• Reason codes need to be defined.
• Currency conversion rates must be entered.
Setup Considerations for Intercompany Transactions

Before you can enter intercompany transactions, you must load Intercompany
transaction rules into the application. The HS.SupportsTran function, when used with
members of the Scenario and Account dimensions (and, optionally, with members of the
custom dimensions), creates a valid cell intersection for an intercompany transaction.
You need a rule for every valid cell intersection.

Opening Intercompany Periods
The period must be open before you can enter intercompany

transactions.
Matching tolerances are set

when periods are opened .
Opening Intercompany Periods

You must open the intercompany period before you can enter intercompany
transactions. You can specify matching tolerances for the period. You can input separate
matching tolerance amounts for transaction ID, account, and manual tolerance. For
transaction ID tolerance, you can also specify a percentage. The percentage is applied
to the smaller of the entity or partner transaction.
You can also select the option for matching and validation:
• If you select the Match/Validate Before Post option, you must match transactions or
assign a reason code before they can be posted. Before you can close a period or
lock an entity, you must post all matched transactions or mismatched transactions
with reason codes.
• If you select the Restrict option, transactions must be matched before you can post
them, but you can close periods or lock entities that have unposted transactions.

Creating Intercompany Transactions
Invoices can be loaded from a file or entered manually.
OR
Creating Intercompany Transactions

Financial Management provides two methods by which you can create intercompany
transactions:
• Load intercompany transactions from ASCII files.
• Manually enter transactions from the Process IC Transactions window.

Loading Intercompany Transactions Files

You can select multiple external files in one load process and
select whether to merge or replace the existing transactions.
Loading Intercompany Transactions Files

The Load IC Transactions task enables you to load transaction details from external
ASCII files.
To load IC transactions:
1. In Browser View, select Load Tasks > Load IC Transactions.
2. Select the delimiter character:@, #, $, %, ^, &, |, :, ; ?, \.
3. Select Load Method.
4. Click Browse, and select a file.
5. Click Open.
6. Click Load.

About Process IC Transactions

Use Process IC Transactions to create and to perform other
intercompany transaction processes.
Transaction Entries per pa ge
About Process IC Transactions

The Process IC Transactions window is the main window from which you perform most
intercompany transaction processes. You use the Process IC Transactions window for
these tasks:
• Create intercompany transactions
• View intercompany transactions
• Edit intercompany transactions
• Unmatch intercompany transactions
• Unpost intercompany transactions

• Filter intercompany transactions

• Delete intercompany transactions
• Report on intercompany transactions

Creating IC Transactions
from Process IC Transactions
Save entered IC Transaction
Creating Transactions from Process IC Transactions

You can manually enter intercompany transactions from the Process IC Transactions
window. To navigate to the Process IC Transactions window, select Tasks > IC
Transaction Tasks > Process IC Transactions. Click New to create an intercompany
transaction.

Matching Intercompany Transactions
Question: Why match intercompany transactions?

Answer: Matching helps reduce the gap that can exist between
intercompany account balances.
Entity A Entity B
Accts. Receivable Intercompany Accts. Payable Intercompany
500 500
Matching Intercompany Transactions

Before posting intercompany transactions to a Financial Management intercompany
account, you can perform a matching process to ensure that both the entity and its
partner entered the transaction.
If your administrator set up the period to require matching before posting, you must
match the transactions before you can post them.

Intercompany Transaction
Matching Methods
• Automatic matching by transaction ID, reference ID, or
account with or without tolerance amount
• Manual matching with or without tolerance amount
Automatic Manual w ith tolerance Manual without tolerance
< 10 USD 1: 1
Intercompany Transaction Matching Methods

You can match transactions by several methods. You can allow the system to
automatically match transactions based on criteria that you specify. You can also
manually match specific transactions, if the transactions are not matched by the
automatic matching process.

Posting Intercompany Transactions
• Intercompany transactions must be posted in order to be

included in an account balance.
• After a transaction is posted, no changes can be made to it.
• If changes are needed to a posted transaction, you must
unpost it, make the changes, and then rematch and repost
the transaction.
Accounts Receivable - Intercompany
Inv 001 1 00
Inv 002 3 00
----
4 00
Inv 003 5 00
----
9 00
500 USD
Posting Intercompany Transactions

When you create or load an intercompany transaction, by default it has a status of
Unposted and no amount is shown in the account balance. For example, you may input
an intercompany transaction for Entity A with Entity B for the amount of USD $100.
However, the amount was not recorded in the ICRec account. The ICRec account
balance remains at zero until the transaction is posted.
When you post the selected intercompany transactions to the account, the system
updates the status of the transactions to Posted, and the total transaction amount is
reflected in the account balance.

Generating Matching Reports
Generate matching reports by:

• Account
Transaction ID
• Transaction ID
• Reference ID Reference ID
Receivables - Interco Payables - Interco
500 500
Generating Matching Reports

After loading transactions into the application and viewing the transactions in the
Process Transactions window or in the transaction detail report, you may want to run a
matching report to check the potential matching transactions as well as the mismatched
transactions. You can run a matching report by account, by transaction ID, or by
reference ID.
You can create a matching report by the following methods:
• Using the Report Wizard
• Writing a script in a text file

Drill-Through Reports
View supporting transaction details in the matching reports.
Drill-Through Reports
When you run an intercompany matching report at the account balance level, a link is
displayed on the report if the administrator set up the report to display intercompany
transaction detail for the matching group. When you click the link, you can view the
matching report at the transaction detail level.
You can only view intercompany transactions in the report; you cannot make changes to
the transactions from the report.

Locking Entities
After intercompany processing is complete, lock entities to

ensure that no further changes are made.
Locking Entities
You can apply a lock to an entity for a scenario, year, and period to prevent future
changes to intercompany transactions for the entity. If the Match/Validate Before Post
option is selected for the period, all matched transactions and all mismatched
transactions with a reason code must be posted before the entity can be locked.
When an entity is locked, you cannot enter new intercompany transactions for the entity.
You also cannot delete or make changes to existing transactions for the entity. You
cannot post or unpost transactions to a locked entity, or update the match status of a
transaction that involves a locked entity. Therefore, even if the partner entity is not
locked, the partner cannot match transactions because the match status cannot be
updated for the entity.

Closing Intercompany Periods

• When a period is closed, no intercompany transactions can
be entered.
• You can still view transactions and run reports.
Closing Intercompany Periods

At the end of the closing cycle, after you finish processing intercompany transactions,
you can close the period to prevent additional modifications to the transactions. If the
Match/Validate Before Post option is selected for the period, all matched transactions
and all mismatched transactions with a reason code must be posted before the period
can be closed.
When you close a period, the period is locked for future transactions. However, you can
continue to view transactions and run reports on the transactions for the period.

Monitoring Intercompany Entity Status

The Monitor Intercompany Transactions task provides status
information for intercompany entities.
Filter by status.
Sum mary of Started and
Not Started Transactions.
Click an entit y to view detail.
Monitoring Intercompany Entity Status

The Monitor Intercompany Transactions task provides a status overview for your
intercompany entities. You can filter the list of entities by any combination of Started, Not
Started, Not Lockable, Lockable, Locked.
• An entity has a status of Not Started if has no intercompany transaction for the
scenario, year, and period in the point of view.
• An entity has a status of Started if has at least one intercompany transaction for the
scenario, year, and period in the point of view.
• An entity has a status of Not Lockable if the Match/Validate Before Post option is
selected for the period, but matched transactions, or mismatched transactions with a
reason code, are not posted.

You can click an entity in the list to view a detail window with additional detail for the
entity. The detail window displays the total number of posted and unposted transactions
for the entity, categorized by matching status.

Summary
• Describe the Intercompany Transactions Module

• Create intercompany reports
• Lock intercompany transactions
• Close intercompany periods

A P P E N D I X C
Managing Applications with Classic

Administration C
Objectives
• Describe Classic Administration
• Create application profiles
• Create applications
• Create metadata files
• Load metadata files
• Extract metadata files
Appendix C Managing Applications with Classic Administration
Classic Administration Overview
p
Create profile.
Create application.
Create metadata file.
Load the metadata

file into the application.
Classic Administration Overview

Classic Administration enables you to administer Financial Management on an
application-by-application basis. With Classic Administration, each application has its
own metadata file, which defines the dimensions for the application. Each application
also has an application profile file that defines the calendar and the languages for the
application. To manage applications using Classic Administration, you must perform the
following tasks:
• Create an application profile that defines the time periods, number of years, and
languages for the application.
• Create the application, referencing the application profile.
• Create a metadata file that defines the account, entity, scenario, and custom
dimensions, as well as the application settings.
• Load the metadata file into the application.
C-2 Financial Management 11.1.1: Create and Manage Applications

Dimensions for applications created using Classic Administration cannot be edited in

Performance Management Architect. However, applications that were created in Classic
Administration can be upgraded to Performance Management Architect. When an
application is upgraded, it is added to the Dimension Library and Application Library.
When an application upgraded to Performance Management Architect, it can no longer
be edited by using Classic Administration.
Financial Management 11.1.1: Create and Manage Applications C-3

Creating Application Profiles
You use application profiles for the following purposes:

• To define the languages available for entering descriptions
• To define the application calendar
• To define the application frequencies
Creating Application Profiles

You create application profiles before you create applications. Each application can
contain only one application profile. However, you can use one application profile to
create many applications. You perform the following tasks to create an application profile:
• Access the Define Application Profile process pad
• Enter languages
• Define the calendar
• Edit frequencies
• Edit periods
• Save the application profile
NOTE
You can create application profiles only from the Windows desktop client.

Accessing the Process Pad
You can access the process pad from the Financial

Management W indows desktop client.
Accessing the Process Pad

The Define Application Profile process pad guides you through the steps for defining an
application profile. To access the process pad, select Define Application Profile on the
Financial Management Desktop. You can edit a profile or create a profile.

Defining Languages
You can enter up to 10 languages.
Defining Languages
You can define up to 10 languages so that you can create descriptions in multiple
languages for each item in your application.

Defining the Calendar
Financial Management provides a flexible calendar that

enables you to customize the base periods, summary periods,
start year, and number of years.
S ummary Period
Quarter 1
Base Periods
Defining the Calendar

After creating an application, you cannot change the total number of years. Therefore, be
sure to allow enough years in your calendar to accommodate both historical data
and forecast data. You can use the standard, custom, or manual method to define
the calendar.
Standard Calendar
You can select half-years, quarters, trimesters, or months as base periods. Base periods
are created based on your selections. When you use a standard calendar, the available
summary periods are determined by the base periods that you select.
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 specify the number of base periods that
you want to create. Base periods are created automatically. You must create the
summary periods manually.
Manual Calendar
You must create both base periods and summary periods manually.

Editing Frequencies
• You can edit the frequency labels and descriptions, which

are displayed in the View dimension.
• You can add frequencies, which you set up later in the
period editor.
Editing Frequencies
Frequencies define the running totals for the time periods that are available in your
application; for example, quarter-to-date or year-to-date. You can define up to six
frequencies.

Editing Periods
• You can edit period labels and add descriptions.

• Each hierarchy level corresponds to a frequency.
Add multiple Add Add

periods child sibling
.
Editing Periods
You can add or delete base and summary periods. You can drag periods to new
locations in the hierarchy. Each level in the hierarchy corresponds to a frequency. You
can add levels to the hierarchy corresponding to the added frequencies.

Saving Application Profiles
Save application profiles either locally or on the application

sever with the extension PER.
Saving Application Profiles

You can save the application profile locally or on the application server, using the PER
file extension.
You reference the PER file when you create an application. You can also modify an
application profile by opening the PER file on the Financial Management Desktop. If you
modify an application profile, the changes do not affect existing applications that were
created using the profile. However, the changes will affect new applications that you
create using the profile.

Application Requirements
Have this information on hand before you create an application:

• Name of the application server cluster
• Name and description of the application
• File name and path of the application profile (PER file)
Application Requirements
An application consists of a set of entities, accounts, scenarios, and other dimensions
that you use together. You can create as many applications as you need. For example,
you may want to set up one application to report on tax data for several organizations
and another application to report on Security and Exchange Commission data for other
organizations.
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.

Creating Applications
You access the Create Application task from the Classic

Application Administration menu.
Creating Applications
To create applications:
1. Select Navigate > Administer > Classic Application Administration > Consolidation Application
Administration.
2. In the view pane, select Tasks > Create Application.
3. Type a name and description for the application.
4. In the Application Profile text box, type the path and name of the PER file for the
application.
5. In the User Management Project list, select the Shared Services project for the
application.
6. Click Create.

Creating Metadata Files
Create and edit metadata files.
Load metadata file into the application.
Creating Metadata Files

You use the Manage Metadata task on the Windows desktop client to work with
metadata files. You can perform the following tasks:
• Create or edit metadata files without opening an application
• Store metadata files locally or on the server
• 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
You also can create and edit metadata files by using a text editor.

Editing Metadata
Select the
metadata type.
Search for a
member.
Select a member to
edit from the list.
Create a file.
Open a file. Save changes.
Editing Metadata
You use the Manage Metadata pane to add and edit dimension members. You also use
it to configure application settings and to add currencies and consolidation methods. You
save your edits for all metadata types in a single file. For example, if you name your
metadata file AppElements, metadata for accounts, entities, scenarios, and all other
application elements are saved in the AppElements file.

Building Member Hierarchies
Create the m ember hierarchy.
Edit member hierarchies.
Building Member Hierarchies

You use the Tree View tab on the Manage Metadata pane to set up member hierarchies.
You manage the hierarchies with the buttons above the Members area, as well as with
shortcut menus.
You use the shortcut menu to delete members.To delete a member, right-click the
member, and select Remove from Parent to remove the member from its current parent
or select Delete from Dimension to remove the member from the dimension.

Assigning Members to Multiple Parents
You can add a member to more than one parent.
Assigning Members to Multiple Parents

You use the Member List tab to assign members to multiple parents. The Member List
tab displays a flat list of all members in the current dimension. You can drag members
from the Member List tab to the hierarchy in the Tree View tab.
Any member not a part of the hierarchy defined on the Tree View tab is an orphaned
member because it has no parent. Orphaned members are not allowed in Financial
Management. If you load a metadata file that has orphaned members, an error results.
By selecting the Only Show Orphaned Members check box, you can filter the member
list to show orphaned members. You can then assign the orphaned members to parents
or delete them.

Editing Groups of Members
Delete mem ber.

Validate members.
Add member. Cut, copy or paste.
Editing Groups of Members

You can manipulate groups of members in a flat-list format on the List View tab. The
spreadsheet-like interface displays a row for each metadata item and a column for each
attribute. You can perform the following tasks:
• Copy cells, columns, or rows
• Disable combo boxes (Member information that you add or edit in list view is not
validated until you change views.)
• Force a validation by clicking Validate or by selecting another dimension
You cannot assign parents to members or work with hierarchies in list view. All members
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.

Configuring Application Settings
• Exchange rate and translation • Security settings

settings • Audit settings
• Consolidation settings • Document attachment
• Validation account settings limits
Configuring Application Settings

With Classic Administration, you use the Application Setting options in Metadata
Manager to configure application settings. The settings are saved when you save the
metadata file.
To configure application settings:

1. In Metadata Manager, open the metadata file for the application.
2. In the Metadata Item list, select Application Settings.
3. Select the application settings.
4. Save the metadata file.

Loading and Extracting Metadata
You access the Load Metadata and Extract Metadata tasks

from Browser View.
Loading and Extracting Metadata

You can load the following types of metadata into your applications:
• Application settings
• Currencies
• Scenarios
• Entities
• Accounts
• Custom1, Custom2, Custom3, and Custom4
• Consolidation methods
• System-generated accounts
• System-generated ICP and Value dimension members

Load Options
You can merge the metadata in the file with the existing
application metadata or you can replace the existing metadata.
Load Options
You can merge or replace metadata:
• The Merge option updates members with the information in the file. If the file contains
members that do not exist in the application, the Merge option adds them.
• The Replace option replaces the existing metadata with the metadata in the file. If a
dimension member that exists in the application is not present in the metadata file
that you are loading, the Replace option removes the member from the application.

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 Financial Management application
for the current dimension. You cannot use the “Clear all metadata before loading” option
and the Replace option at the same time.
Before clearing or loading metadata, you can scan the load file to make sure that it is in
the correct format.
NOTE
The Check Integrity attribute validates that there are no conflicts with any posted
journals in the system.
Merge Versus Replace—Rules of Thumb

• Use Merge if you are adding members or updating member properties.
• Use Replace if you are moving members or deleting members.
• Use Merge with Clear all metadata before loading if you are promoting members.

Metadata Load Files
• Metadata load files can be in APP or XML format.

• They can contain metadata for:
– Account, Entity, Scenario, Custom, and ICP dimensions
– Currencies
– Application settings
– Consolidation methods
• They cannot contain metadata for:
– Periods
– Years
– View
Metadata Load Files

The Year, Period, and View dimensions are defined in the application profile. For
system-generated members, you can modify some member properties, but you cannot
add members. For example, you can modify the description and security class for
members of the ICP dimension, but you cannot add ICP members.

Format for APP Load Files
• APP load files are divided into sections with am

exclamation point as the section delimiter.
• Sections can be in any order in the file.
• Fields for the items within a section are delimited with
any of these characters:
,~ @ #$^ &_ |:;? \
!CURRENCIES
EUR;0;English=Euro;;French=Euro
USD;0;English=US Dollar;;French=Dollar Americaine
GBP;0;English=British Pound;;French=Livre Anglaise
Format for APP Load Files

You can save files created in Metadata Manager in either XML format or APP format.
You should save the file in APP format if you plan to edit the file manually.

Extracting Metadata
Select to save extract

files in Financial
Management APP
format; otherwise, XML
format is used.
Extracting Metadata
You can extract metadata from an application and save it in XML format or in Financial
Management APP format. Use APP format if you want to edit the file manually in a text
editor. APP format is an easier-to-read format for manual editing.
After making modifications to the file with either Metadata Manager or a text editor, you
need to reload it into the application for the changes to take effect.

Summary
• Describe Classic Administration

• Create application profiles
• Create applications
• Create metadata files
• Load metadata files
• Extract metadata files

Oracle HFM Vol2

Uploaded by

Document Information

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

Oracle HFM Vol2

Uploaded by

Copyright:

Available Formats

Oracle Hyperion

Financial Management 11.1.1:

Volume II • Student Guide

Mark Mitsock Disclaimer

Editor Restricted Rights Notice

Mark Mitsock Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other

Lesson 1: Introduction to Financial Management

Lesson 2: Navigating Financial Management

Financial Management 11.1.1: Create and Manage Applications i

View Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Module 2: Creating the Application Structure

Lesson 3: Managing Dimensions with Performance Management Architect

ii Financial Management 11.1.1: Create and Manage Applications

Lesson 4: Loading Metadata

Lesson 5: Creating Applications

Financial Management 11.1.1: Create and Manage Applications iii

Configuring Validation Account Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

Lesson 6: Configuring Accounts and Custom Dimensions

Lesson 7: Setting Up Entities, Calendars, and Scenarios

Lesson 8: Deploying Applications

iv Financial Management 11.1.1: Create and Manage Applications

Validating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Module 3: Adding Data to Your Application

Lesson 9: Loading Data

Lesson 10: Entering Data by Using Data Grids

Financial Management 11.1.1: Create and Manage Applications v

Accessing Data Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Lesson 11: Creating, Loading, and Extracting Member Lists

Lesson 12: Managing Rules with Calculation Manager

vi Financial Management 11.1.1: Create and Manage Applications

Creating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Module 4: Setting Up Security

Lesson 13: Provisioning Users and Groups

Lesson 14: Assigning Access to Data and Documents

Module 5: Creating Data Forms and Task Lists

Lesson 15: Creating Data Forms

Financial Management 11.1.1: Create and Manage Applications vii

Creating Data Forms with Form Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

Lesson 16: Creating and Managing Task Lists

Module 6: Managing Intercompany Balances and Adjustments

Lesson 17: Entering Intercompany Data

viii Financial Management 11.1.1: Create and Manage Applications

Lesson 18: Adjusting Data with Journals

Module 7: Calculating and Consolidating Data

Lesson 19: Running Consolidations

Financial Management 11.1.1: Create and Manage Applications ix

Consolidating Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19

Lesson 20: Managing the Review Cycle Using Process Management

Lesson 21: Sharing Data Using Data Synchronization

x Financial Management 11.1.1: Create and Manage Applications

Mapping Source Dimensions to Destination Dimensions . . . . . . . . . . . . . . . . . . . . . 21-8

Lesson 22: Analyzing Data with Smart View

Appendix A: Automating Tasks

Financial Management 11.1.1: Create and Manage Applications xi

Stage Definition—General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Appendix B: Managing Intercompany Transactions

Appendix C: Managing Applications with Classic Administration

xii Financial Management 11.1.1: Create and Manage Applications

Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12

Financial Management 11.1.1: Create and Manage Applications xiii

xiv Financial Management 11.1.1: Create and Manage Applications

Creating Data Forms and Task Lists 14

Creating Data Forms 15