FDQM SG1

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY.
COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED
'
Edition 1.
January 2010
D56780GC11
Administration
Volume I • Student Guide
Quality Management 11.1.1
Oracle Hyperion Financial Data
Oracle University and Businessmind Colombia SA use only

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED
Author Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
Lea Jensen Disclaimer
This document contains proprietary information and is protected by copyright and

Technical Contributors other intellectual property laws. You may copy and print this document solely for your
and Reviewers own use in an Oracle training course. The document may not be modified or altered in
any way. Except where your use constitutes "fair use" under copyright law, you may
Philip Attea 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
Eric Davidson express authorization of Oracle.
Jeffrey Jones
The information contained in this document is subject to change without notice. If you
Todd Newman find any problems in the document, please report them in writing to: Oracle University,
500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not

Shawn Stalker
warranted to be error-free.
Michael Van Der Merwe
Restricted Rights Notice
Editor If this documentation is delivered to the United States Government or anyone using
Susan Moxley the documentation on behalf of the United States Government, the following notice is
applicable:
Publisher U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
Lea Jensen disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other

names may be trademarks of their respective owners.
Preface 0

Welcome to Financial Data Quality Management 11.1.1 Administration!
Before you begin, please take a moment to review this section. The
preface presents an overview of the following information:
• Course objectives
• Structure of the course
• Course materials used in the class
• Conventions used in the book
• Additional resources to enhance your learning
• Relevant follow-up courses that you might want to attend in the future
Course Objectives
After completing this course, you should be able to:
• Create FDM applications
• Integrate FDM applications with target applications from disparate
systems
• Import mappings
• Create import formats for source applications
• Create validation rules and entities
• Load data to target systems
• Apply financial controls to comply with Sarbanes-Oxley legislation
• Set up user and object security
• Create scripts
Preface
Course Structure
Oracke Hyperion Financial Data Quality Management 11.1.1 Administration is a 3-day,
instructor-led training course consisting of lectures, demonstrations, and hands-on
exercises. In this course, the instructor presents a topic conceptually by explaining its
purpose, demonstrating how it works, and then guiding the students through the
exercises. Demonstrations and hands-on exercises reinforce the concepts and skills
introduced during lectures.

Course Materials
You use two books in class—the student guide and the activity guide. The instructor may
also give you handouts.
Student Guide
The student guide is designed to be used by students and the instructor during lecture
time. It has six modules:
• Module 1 describes FDM and navigating in FDM.
• Module 2 describes the methods that are used to create FDM applications, integrate
applications, and set up control tables and locations.
• Module 3 describes the methods that are used to set up mapping tables, build import
formats, load data, build validation rules and validation entities, and process batch
files.
• Module 4 describes the methods that are used to create logic accounts, load FDM
journals, and load data with multiload files.
• Module 5 describes the methods that are used to set up security and apply financial
controls.
• Module 6 describes the methods that are used to create import, import integration,
and event scripts.
Each module contains lessons. Each lesson begins with a list of objectives followed by
the presentation of slides and accompanying text. The lesson ends with a summary of
the topics covered in the lesson.
Activity Guide
The activity guide has two sections—exercises and exercise solutions.
Exercises
A critical part of the learning process is the challenge of completing real tasks associated
with each lesson. Each exercise is an opportunity to apply your new knowledge.
iv Financial Data Quality Management 11.1.1 Administration

Preface
Exercise Solutions
The exercise solutions present the detailed steps to successfully complete the exercises.
Conventions
The following text conventions are used in this course book:
• Text to be typed, options to be selected, names of files and modules, and menu
selections are displayed in bold type. Examples:

- Select Clear Profile.
- Click YES to clear the profile.
• When available, figures are used to identify an object or task. Example:
Click Edit.
• Keyboard shortcuts are displayed as follows: Ctrl+Enter

• Alerts are used to direct your attention to different types of information.
NOTE
A note provides related information, common mistakes, or
cautions about the current topic.
TIP
A tip provides information that helps you work more
efficiently.
Additional Resources
Use the following resources to enhance your learning:
• Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11.1.1
Administrator’s Guide (fdm_admin.pdf)
Configuration Guide (fdm_config.pdf)
Readme (fdm_11110_readme.pdf)
• http://oracle.com
Financial Data Quality Management 11.1.1 Administration v

vi
Preface
Financial Data Quality Management 11.1.1 Administration

Table of Contents 0
Preface
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Course Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Course Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Student Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Activity Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Module 1: Introduction to FDM
Lesson 1: Product Orientation

Oracle’s Enterprise Performance Management System . . . . . . . . . . . . . . . . . . . . . . . 1-2
Oracle BI Suite Enterprise Edition Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Benefits of FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Features of FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Processing Data Through FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Importing Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Validating Dimension Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Correcting Mapping Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Loading Data to Target Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Checking Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Lesson 2: Navigating FDM

Accessing FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Accessing Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Workbench Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Accessing the FDM Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
FDM Web Client Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Setting the POV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Rules That Determine the Default POV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table of Contents
Changing the POV Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Changing the POV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Searching for POV Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Locking Out Users for Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Running Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Running Process Monitor Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Changing Report and Group Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Viewing Graphical Timelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Viewing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Changing the Timeline Viewer Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Module 2: Building FDM Applications
Lesson 3: Creating FDM Applications

About FDM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Application-Building Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Creating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Selecting Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Directory Structure of Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
Managing Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Modifying Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Removing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Adding Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Lesson 4: Integrating Applications

Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Importing and Registering Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Adapter Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Importing and Configuring Source System Adapters. . . . . . . . . . . . . . . . . . . . . . . 4-5
Importing Target System Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Registering Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Adding Machine Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Verifying Application Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Updating Integration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Application Name Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Logon Method Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Global Logon Information Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
viii Financial Data Quality Management 11.1.1 Administration

Table of Contents
Integrating Hyperion Enterprise Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Associating Dimensions Between Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Testing Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Importing Standard Reports and Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Standard Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Standard Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Lesson 5: Setting Up Control Tables and Locations
Viewing Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Modifying Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Deleting Periods and Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Adding Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Adding Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Modifying Control Tables with Excel Worksheets . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Viewing Currency Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Viewing Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Controls Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Adding Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Setting Location Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Setting General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Setting Workflow Behaviors Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Setting Financial Controls Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Setting Integration Options Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Searching Control Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Module 3: Building the Workflow Process
Lesson 6: Setting Up Mapping Tables

Mapping Dimension Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Activating Map Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Assigning Dimension Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Opening Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Building Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Map Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Explicit Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Rules-Based Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Wildcard Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Financial Data Quality Management 11.1.1 Administration ix

Table of Contents
Processing Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Processing Order in Multiple Mapping Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Processing Order in the Same Mapping Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Building Maps Externally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Building Maps with MapLoader Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Importing Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Building Maps with Hyperion LedgerLink Files . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24

Building Maps with Hyperion Enterprise Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Copying Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Sharing Dimension Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Setting Up Conditional Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
VarValues Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Conditional Mapping Script Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Conditional Mapping Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . 6-33
Lesson 7: Building Import Formats

About Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Creating Import Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Building Import Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Building Fixed Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Building Delimited Import Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Building Import Formats for EBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Skipping Lines in Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Concatenating Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Assigning Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Adding Import Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Sign Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
DRCRSplit Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Fill and Fill=EuroToUS Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Fill and Fill=EuroToUS Expressions: Example. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
FillL Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Factor Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
NZP Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Expression Stacking and Processing Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Lesson 8: Loading Data

About Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Selecting Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
x Financial Data Quality Management 11.1.1 Administration

Table of Contents
Importing Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Working with Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Sorting Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Finding Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Filtering Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Deleting Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Validating Dimension Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11

Validation Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Fixing Validation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Intersection Validation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Loading Data to Target Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Drilling Up on Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Displaying Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Displaying Conversion Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Displaying Archive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Displaying Source Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Displaying Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
Displaying Processing Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Restoring Source Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Drilling Down on Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Drilling Up on a Drilldown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Drilling Back to FDM from Target Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28
Drilling Back from Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Drilling Back from Essbase Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
Drilling Back from Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
Drilling Back from Strategic Finance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Lesson 9: Building Validation Rules

About Validation Rules and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Creating Validation Rule Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Creating Validation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Selecting Display Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Defining Rule Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Adding Rule Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Creating Validation Rules in Validation Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Adding Rules and Display Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Looking Up Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Testing Rules and Display Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Assigning Validation Rules to Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Financial Data Quality Management 11.1.1 Administration xi

Table of Contents
Checking Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Lesson 10: Setting Up Validation Entities

About Validation Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Creating Validation Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Creating Validation Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Assigning Validation Entity Groups to Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Verifying Consolidations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Lesson 11: Processing Batch Files

About Batch Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
Enabling Batch Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
Setting Up Batch-Load Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5
Processing Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
Batch Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7
Batch Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
Creating Batch Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10
Scheduling Batch Scripts in Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-12
Module 4: Creating Additional Loading Options
Lesson 12: Creating Logic Accounts

About Logic Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Creating Logic Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Creating Simple Logic Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Selecting Source Accounts for Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Grouping Accounts by Source Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-11
Selecting Operators and Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Retrieving Source Account Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
Assigning Function Return Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Simple Logic Function Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Creating Logic Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Creating Complex Logic Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
Applying Criteria Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Complex Logic Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Complex Logic Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
Assigning Logic Groups to Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
xii Financial Data Quality Management 11.1.1 Administration

Table of Contents
Lesson 13: Loading FDM Journals

About FDM Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Creating Journal Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Adding Metadata Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Load Method Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Dimension Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Loading Journal Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9

Checking In Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
Posting Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Lesson 14: Loading Data with Multiload Files

About Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Creating Multiload Excel Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Adding Metadata Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Adding Load Control Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Adding Dimension Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13
Creating Multiload Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Loading Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Checking In Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19
Executing Workflow Tasks for Multiload Files . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Viewing Data-Load Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Module 5: Enhancing FDM
Lesson 15: Setting Up Security

About FDM Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Security Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
About Object Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Setting Up Object Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
About User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Setting Up User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Adding Authentication Providers for FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Provisioning Users in Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Adding Shared Services Users to FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
Modifying User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20
Financial Data Quality Management 11.1.1 Administration xiii

Table of Contents
Migrating Users to Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-21

Locking and Unlocking the Local Point of View Mode . . . . . . . . . . . . . . . . . . . . . . . 15-23
Setting Up Report Group Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-24
Lesson 16: Working with Financial Controls

About Financial Controls in FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Creating Controls Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Adding Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Adding Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Setting an Effective Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Creating Question Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Importing Questions From Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
Deleting Groups, Sections, or Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Restoring Groups, Sections, or Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16
Assigning Reviewer, Submitter, and Proxy Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18
Assigning Reviewers and Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
Assigning Submitters and Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21
Assigning Risk Levels to Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-22
Accessing Financial Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
Adding Memos and Attaching Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . 16-25
Reviewing and Submitting Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-30
Selecting Application Settings for Financial Controls. . . . . . . . . . . . . . . . . . . . . . . . 16-32
Module 6: Creating Scripts
Lesson 17: Working with Import Scripts

About Scripting in FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
Working with Scripting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Accessing Script Editor in the FDM Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Accessing Script Editor in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Accessing Accelerators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Creating Import Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Import Script Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Creating Import Scripts in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Creating Import Scripts: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Assigning Import Scripts to Import Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Applying Scripting Functions to Import Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Applying the Left Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
xiv Financial Data Quality Management 11.1.1 Administration

Table of Contents
Applying the Right Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17

Applying the Mid Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Applying the fParseString Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Applying the RES.PblnSkip Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Applying the RES.PblnSkip Function: Example. . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Working with Temporary Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Assigning Temporary Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23

Importing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
Manually Executing Custom Web Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-27
Lesson 18: Working with Import Integration Scripts

About Import Integration Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Import Integration Script Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Population of FDM Table Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Creating Import Integration Scripts in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Creating Import Integration Scripts: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Creating Import Integration Scripts: Example (cont.) . . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Assigning Import Integration Scripts to Import Formats. . . . . . . . . . . . . . . . . . . . . . 18-10
Lesson 19: Working with Event Scripts

Event Scripts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Types of Event Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
ImportAction Subevents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Event Script Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Creating Event Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Changing Import Formats Dynamically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Changing Import Formats Dynamically: Example . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Changing Other Location Attributes Dynamically . . . . . . . . . . . . . . . . . . . . . . . 19-10
Appendix A: Setting Up Multilanguage Support

About Multilanguage Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Changing Language Settings in FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Changing Browser Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Setting Decimal Formatting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Creating Reports for Multiple Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Translating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Selecting Validation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Financial Data Quality Management 11.1.1 Administration xv

Table of Contents
Appendix B: ERP Integrator

About ERP Integrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
ERP Integrator Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
ERP Integrator Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Security in ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Source System and Target Application Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Accessing ERP Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9

Dimension and Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Account Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Entity and Intercompany Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
Scenario Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
Version Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
View Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Year and Period Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Alias Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Custom Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
Source System Hierarchies and EPM Dimensions . . . . . . . . . . . . . . . . . . . . . . . B-16
Registering ERP Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17
Selecting Source Accounting Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20
Registering EPM Target Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
Defining Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24
Defining Single-Segment or Single Chartfield Mappings . . . . . . . . . . . . . . . . . . . B-26
Defining Concatenated Segments or Concatenated Chartfields Mappings. . . . . B-29
Defining Detailed Member Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32
Defining Dimension Mappings for FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-34
Managing Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Editing Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37
Running Metadata Rules to Extract Dimensions and Hierarchies . . . . . . . . . . . . B-37
Checking Metadata Rule Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Deleting Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Defining Calendar Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-40
Defining Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42
Defining Data Rules Source Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44
Defining Target Application Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47
Defining Exchange Rate Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-50
Submitting Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-52
Managing Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54
Editing Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54
Running Data Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-55
xvi Financial Data Quality Management 11.1.1 Administration

Table of Contents
Checking the Data Rule Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-55

Deleting Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-55
Drilling Through to View Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-57
Drilling Through from Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . B-59
Drilling Through from Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-60
Drilling Through from Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-61
Drilling Through from Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-62

Drilling Through from the ERP Integrator Landing Page . . . . . . . . . . . . . . . . . . . . . . B-63
Drilling Through from the E-Business Suite Landing Page . . . . . . . . . . . . . . . . . B-64
Drilling Through from the Summary Balances Page . . . . . . . . . . . . . . . . . . . . . . B-65
Drilling Through from the Detail Balances Page . . . . . . . . . . . . . . . . . . . . . . . . . B-66
Journal Lines Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-67
Drilling Through from the PeopleSoft Landing Page . . . . . . . . . . . . . . . . . . . . . . B-68
Financial Data Quality Management 11.1.1 Administration xvii

xviii
Table of Contents

M O D U L E 1
Introduction to FDM 0

Overview
The aim of this module is to provide an overview of the FDM features,
benefits, and data load process. You learn to navigate in Workbench and in
Web client, to set the user Point of View, and to run reports.
Lessons in this module include:
• Product Orientation
• Navigating FDM

L E S S O N 1
Product Orientation 1

Objectives
At the end of this lesson, you should be able to:
• Describe Oracle’s Enterprise Performance Management System
• Describe Oracle’s Business Intelligence Suite Enterprise Edition Plus
• Discuss the benefits and features of FDM
• Explain the data-load process
Module 1 Introduction to FDM
Lesson 1 Product Orientation
Oracle’s Enterprise Performance

Management System
EPM Workspace

Performance Management
Applications BIBIApplications
Applications
Business Intelligence Foundation
Fusion Middleware
OLTP & ODS Data OLAP SAP, Oracle, Siebel, Excel Business
Systems Warehouse PeopleSoft, Custom XML Process
Data Mart
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
Oracle’s Enterprise Performance Management System

Oracle’s Enterprise Performance Management System is a portfolio of technology and
applications that includes category-leading financial performance management
applications, operational BI applications, BI foundation and tools, and data warehousing.
It also leverages Oracle’s Fusion Middleware technologies, such as Oracle Application
Server and Oracle Identity Management.
It has the following characteristics:
• Pervasive—It enables all levels of your organization to see information optimized for
their role.
• Comprehensive—It incorporates information from your financial performance
management, operational intelligence, and transactional applications.
• Hot-pluggable—It integrates with any data source, extraction, transformation, and
load (ETL) tool, major business application, application server, security
infrastructure, portal technology, front-end and analytical tools, and database.
1-2 Financial Data Quality Management 11.1.1 Administration

Performance Management Applications

Oracle’s performance management applications are a modular suite of integrated
applications that support the entire financial management cycle of goal setting, modeling,
planning, monitoring, analysis, and reporting. Applications include the following:
• Oracle® Hyperion Financial Management, Fusion Edition
• Oracle® Hyperion Performance Scorecard, Fusion Edition

• Oracle® Hyperion Strategic Finance, Fusion Edition
• Oracle® Hyperion Planning, Fusion Edition
• Oracle® Hyperion Capital Asset Planning, Fusion Edition
• Oracle® Hyperion Workforce Planning, Fusion Edition
• Oracle® Hyperion Profitability and Cost Management, Fusion Edition
• Oracle® Hyperion Financial Data Quality Management, Fusion Edition
• Oracle® Strategic Operational Planning, Fusion Edition
BI Applications
Oracle BI applications are prebuilt vertical and horizontal analytic applications that
enable organizations to gain greater insight and value from a range of data sources and
applications, including Oracle E-Business Suite, PeopleSoft, Siebel (Customer
Relationship Management system), and third-party systems such as SAP (Enterprise
Resource Planning system). Applications include the following:
• Oracle® Financial Analytics
• Oracle® HR Analytics
• Oracle® Order Management and Fulfillment Analytics
• Oracle® Supply Chain Analytics
• Oracle® Sales Analytics
• Oracle® Service Analytics
• Oracle® Contact Center Analytics
• Oracle® Marketing Analytics
• Oracle® Usage Accelerator Analytics for CRM
Financial Data Quality Management 11.1.1 Administration 1-3

Business Intelligence Foundation

The core technology of Oracle’s EPM System is a highly scalable Business Intelligence
Foundation. This foundation utilizes a common enterprise information model as the
consistent semantic layer. This foundation has three specialized servers to meet your
reporting and analytical needs:
• Essbase—Leading OLAP Server for building forward-looking analytic applications

• BI Server—Highly scalable federated query engine for aggregating disparate data
sources
• Predictive Analytics—Oracle Real-Time Decisions, a predictive analytics engine for
embedding BI into operational processes
Fusion Middleware
Fusion Middleware provides an open, comprehensive, standards-based approach for
deploying service-oriented architectures (SOAs) by using Web Services, an enterprise
service bus, and Oracle BPEL (Business Process Execution Language) Process
Manager. Its portfolio includes products for integration, business process management,
business intelligence, and data management; developer tools for applications,
databases, and BI; and many other components.
Examples:
• Oracle Application Server (Java application server)
• Oracle Coherence (scaling)
• Oracle Master Data Management Suite (data management)
• Oracle Collaboration Suite (e-mail and content management)
• Oracle Identity and Access Management Suite (identity management)
• Oracle WebCenter Suite (context-rich user interface with Web 2.0)
• Oracle SOA Suite (business rules, process deployment, Java development, business
activity monitoring with dashboards and alerts, application integration over the
Internet and across other applications)
• Oracle Portal (out-of-the box enterprise portal)

Oracle BI Suite Enterprise Edition Plus
• Is part of Business Intelligence Foundation

• Delivers a full range of analysis and reporting capabilities

Hyperion BI Tools
Oracle BI Suite
Financial Reporting
SQR Production Reporting Enterprise Edition
Interactive Reporting
Web Analysis
Oracle BI Suite Enterprise Edition Plus

Part of the Business Intelligence Foundation, Oracle Business Intelligence Suite
Enterprise Edition Plus (Oracle BI Suite EE Plus) brings together Hyperion Business
Intelligence tools and Oracle Business Intelligence Suite Enterprise Edition (Oracle BI
Suite EE) to provide a single solution for Enterprise Business Intelligence with a full
range of analysis and reporting capabilities.
Oracle BI Suite EE Plus capabilities include interactive dashboards, full ad hoc queries
and analysis, proactive intelligence delivery and alerts, enterprise and financial reporting,
online analytical processing (OLAP) analysis and presentation, high-volume production
reporting, real-time predictive intelligence, disconnected analytics, as well as integration
with Microsoft Office.

Oracle Business Intelligence Suite Enterprise Edition

Oracle BI Suite EE is a comprehensive, next-generation BI platform that features a full
range of BI capabilities, all built on a single, unified architecture that delivers intelligence
from all enterprise data sources. Components include the following:
Oracle BI Server • Highly scalable, highly efficient query and analysis

server

• Integrates and aggregates data through
sophisticated query federation capabilities
• Relational, unstructured, OLAP, and prepackaged
application data sources (Oracle and non-Oracle)
Oracle BI Answers • Ad hoc query and analysis tool that works against a
logical view of information
• Multiple data sources
• Web environment
Oracle BI Interactive Dashboard • Interactive dashboards
• Web environment
Oracle BI Publisher • Highly scalable reporting engine
• Generates reports in multiple formats
• Multiple data sources
Oracle Briefing Books • Reports that capture a series of snapshots of an
Oracle BI Dashboard or report
• Offline viewing
Oracle BI Disconnected Analytics • Answers and Dashboards for non-networked
computers
Office BI Office Plug-in • Synchronizes information from Answers to
Microsoft Word, Excel, and PowerPoint
Oracle Delivers • Alerting engine to capture and distribute
notifications through multiple channels

Hyperion BI Tools
Hyperion BI tools, under the umbrella name Hyperion® Reporting and Analysis, offer
complementary functionality to Oracle BI Suite EE. They enable you to create analytical,
financial, and production reports, as well as dashboards against most data sources.
They include strong integration with multidimensional data sources, such as Oracle®
Essbase, and have native access to SAP data. Components include the following:

Oracle® Hyperion Interactive • Interactive reporting and dashboarding
Reporting
• Relational and multidimensional data sources
• Web and client-server environments
Oracle® Hyperion SQR Production • Pixel-perfect reporting
Reporting
• Relational and multidimensional data sources
• Development language for advanced data
processing and report formatting
• Web and client-server environments
Oracle® Hyperion Financial • Highly formatted financial and operational reporting
Reporting, Fusion Edition
• Multidimensional data
• Web environment
Oracle® Hyperion Web Analysis • Web-based interactive reporting against
• Multidimensional data sources
• Web environment


FDM
Oracle Hyperion Financial Data Quality Management (FDM), Fusion Edition is an out-of-
the-box data transformation tool that loads source-level financial data to consolidation,
reporting, planning, and analytical applications. More than just a data translation tool, it
provides an audit trail to the source financial data, helping to ensure data integrity and
mapping consistency that allows easy reconciliation of financial data. The audit trail also
saves end users, administrators, and auditors the time associated with data error
investigation, identification, and correction.
Overview of processing data in FDM:
1. Import source data
2. Validate source data against mapping tables
3. Export source data to target system

4. Consolidate target system data

5. Check target system data
6. Review and validate the company’s internal financial controls

Benefits of FDM
• Increase your financial data quality and confidence in the

numbers

• Simplify financial data collection, transformation, and
verification
• Centralize and standardize on repeatable financial
processes
• Lower the cost of compliance with Sarbanes-Oxley
legislation
• Improve the productivity of finance staff
Benefits of FDM
Finance organizations need to eliminate the data integrity risks that are associated with
collecting, mapping, verifying, and moving critical financial data across the entire
organization.
FDM requires minimal IT involvement and offers a user-friendly environment that
provides uniform data collection processes for all reporting units within the organization.
FDM also contains financial controls functionality to assist corporations with their internal
financial controls process.


Features of FDM
• Audit trails deliver process transparency.
• Web-based, guided workflow user interface helps users easily create timely, accurate
financial data management processes.
• Data preparation server aids the integration and validation of financial data from any
source system.
• Prepackaged EPM adapters for Oracle Hyperion applications further reduce
integration costs and data-mapping complexities.
• Sarbanes-Oxley 302 Sub Certifications and 404 Assessments can be incorporated in
the closing process.
• Data validation and quality checking are performed at every step in the process.
• FDM contains over 100 prebuilt audit, log, system, and process management
reports.

Processing Data Through FDM

Create GL Import GL Validate Create and Pass the
extract file extract file imported load file validation
GL data to target check
system
Processing Data Through FDM

In the FDM data-load process, the goal of the end user is to move data through the four
FDM Workflow tasks—Import, Validate, Export, and Check. At the start of the process,
no status bar icons are displayed in the Workflow area. The default status bar icon is a
fish. As you successfully complete the tasks, an orange fish is displayed under each
task. If a task results in an error, a white fish is displayed under the task. You can allow
end users to change the status bar icon—for example, to a check mark.

Importing Source Data
1. Click Upload File. 2. Browse for load file.

Current

window
3. Click
Import.
4. Imported data for Texas location.

You load source data files into FDM locations by using the Import task. Data load
locations are holding units that enable you to load imported source data to target
systems. Typically, there is one location for each source data file that you load to target
systems.
For the example on the slide, you import the Texas_GL.glo source file to the Texas
location.
Before you can import a source data file, you assign an import format to the data-load
location. In the import format, you define how to transform the source data file into data
that you can load to FDM locations. For example, you specify the location and length of
the account dimension in the source data file.

Validating Dimension Mappings
Click Validate to validate the imported source data against the

location mapping tables and target system application

intersections.

All source dimensions must be properly mapped to target system dimensions before you
can load data to the target system. In the Validate task, FDM compares the imported
source data against mapping tables that are assigned to the location. Mapping tables
map the source dimension members to their corresponding target system dimension
members. This mapping ensures that the source data loads to the correct target system
members. For example, in the Entity mapping table, you can map the source Texas entity
to the target system TX entity.
When all dimension members are mapped correctly, the Validate task runs successfully
and an orange fish is displayed.
NOTE
During the validation process, FDM also validates the intersections of all
dimensions in Financial Management target system applications.

Correcting Mapping Errors
Validation error

Unmapped
dimension members
Correcting Mapping Errors

If you load and validate a file that contains unmapped dimension members, a validation
error occurs and a white fish is displayed under Validate. This error typically occurs when
you add new accounts to the general ledger, but you have not added the accounts to the
mapping tables.
FDM displays the unmapped members in the upper table of the Validate window. You
must fix all mapping errors before you can continue with the next step.
For the example on the slide, the unmapped account, 1100-104, is displayed. You can fix
the mapping by browsing to the corresponding target system account. After correcting all
mapping errors, run the Validate task again.

Loading Data to Target Systems

Load
options

After successfully validating the source data and target system application intersections,
you use the Export task to load the data to the target system. In the Export task, FDM
creates the load file and prompts you for load options. If the data loads successfully, an
orange fish is displayed under Export.

Checking Validation Rules

Validation report

After you load data to target systems, FDM performs a validation check based on criteria
that you specify in validation rules. You use validation rules to enforce data integrity
when loading data to target systems. You create validation rules in a validation rule
group, which you assign to locations. FDM performs a validation check and generates a
validation report only if you assign a validation rules group to the location.
The validation report displays target system account balances and custom validation
rules. If the validation rules are not met, the Check task fails and you must investigate
why the values are out of balance.

Summary
In this lesson, you should have learned to:

• Describe Oracle’s Enterprise Performance Management System
• Describe Oracle’s Business Intelligence Suite Enterprise Edition Plus
• Discuss the benefits and features of FDM
• Explain the data-load process

L E S S O N 2
Navigating FDM 2

Objectives
• Access Workbench and the FDM Web client
• Navigate the user interface
• Set the point of view
• Lock the system
• Run reports
• View graphical timelines
Lesson 2 Navigating FDM
Accessing FDM
Accessing Workbench:
1. From the Windows desktop, select Start > Programs >

Oracle EPM System > Financial Data Quality
Management > Workbench > Workbench Client.
2. Select the application name, enter the user name and
password, and click OK.
Accessing FDM
You build and maintain FDM applications in Workbench and the FDM Web client.
Workbench is a Windows-based interface that is used only by administrators. The FDM
Web client is a Web-based interface that is used by both administrators and end users.
Accessing Workbench
Administrators access Workbench to configure and modify FDM applications in a
Windows-based interface. When you log on to Workbench, you open the application in
which you want to work.
In Workbench, you perform the following tasks:
• Set up integration adapters
• Create and maintain scripts and reports

• Import and export applications

• Set up and monitor batch processing
• Create and modify reports

Workbench Interface
Integration
Adapters

options
POV bar
Navigation tabs
Workbench Interface
The Workbench interface includes a navigation pane with three tabs—Adapters, Scripts,
and Reports. When you select a tab, its options are displayed in the navigation pane.
Tab Description
Adapters Import and maintain adapters that applications use to connect to source
and target systems
Scripts Create and maintain import, custom, and event scripts
Reports Create and modify reports
The Workbench interface also includes a POV bar that displays the FDM application
point of view (POV). The POV indicates the current location, period, categories, POV
mode, and system lock status.

Accessing the FDM Web Client
1. From the Windows desktop, select Start > Programs >

Oracle EPM System > Financial Data Quality

Management > Web Server Components > Web Logon.
2. Select the application name, enter the user name and
password, and click Logon.
Accessing the FDM Web Client

The FDM Web client desktop is the control center from which you build and administer
an FDM application. When you log on to the FDM Web client, you select the application
that you want to open. When the application opens, the desktop is displayed.
In the FDM Web client, you perform the following tasks:
• Manage metadata and maintain control tables
• Set application, integration, configuration, and Web settings
• Create and maintain maps, locations, import formats, logic groups, and control
groups
• Create and maintain validation rule groups and validation entity groups
• Execute workflow tasks to import, validate, export, and check data
• Run reports
• Maintain security

FDM Web Client Interface
Menu bar

Window
indicator
Workflow
tab and
menu
Menu
rollup
POV bar
FDM Web Client Interface

The FDM Web client desktop has three main areas:
Window indicator—Current window name; for the example on the slide, the Home
window is displayed.
Menus—Menus that access all functions available in the FDM Web client. The menu
rollup on the left side of the window contains six tabs. When you select a tab, its
underlying menu is displayed. For the example on the slide, the Workflow tab is selected
and the Workflow menu is displayed. You can also access the menu commands from the
menu bar located at the top of the desktop.
POV bar—FDM application POV. The POV indicates the active user, current application,
location, period, categories, POV mode, system lock status, and current adapter.

Setting the POV
Active
System Lock
Current Active Target
Status

Application Period Category
Current Current Active Point of Active

User Location FDM View Mode Adapter
Category
Setting the POV

You use the POV to set the location, period, and category on which you want to focus.
For the example on the slide, the focus is on Actual data for the Texas location for
January 2009. All tasks that you perform from the FDM Web client desktop affect data for
the current location set in the POV bar.
Administrators can control the period and category POV for all users by locking the POV
mode, to ensure that end users load data only to the proper period and category. Locking
the POV mode is covered in a later lesson.

The following table describes the tabs on the POV bar:
Tab Description
Current User Current user logged on to FDM
Current Application Currently open FDM application
Current Location Currently active FDM location

Active Period Currently active FDM period (This period corresponds to a target
system period.)
Active FDM Category Currently active FDM category (This category corresponds to a
target system category.)
Active Target Category Target system category that is associated with the currently active
FDM category
Point of View Mode Current POV Mode, either Global or Local
System Lock Status Status of the system lock, either Open or Locked
Active Adapter Adapter that is used for the current location
Rules That Determine the Default POV

When users log on to an application, FDM executes the following steps to set the default
POV:
• Retrieves the user’s security profile to set the default location POV
• Sets the POV mode to Global by default
• Retrieves the system global category to set the category POV
• Retrieves the system global period to set the period POV

Changing the POV Mode
Click the Point of View Mode tab to toggle between Global and
Local modes.

Global
Point of View
Mode
Local
Changing the POV Mode

The POV mode determines whether users can change their current category and period
POV. There are two POV modes—Global and Local.
Global POV mode restricts category and period processing to a global value that the
administrator assigns by default to all users in the application. In Global POV mode, end
users cannot change the category and period POV. For the example on the slide,
Jan - 2009 and FDM_Actual are the global POV values that are assigned to all users.
Local POV mode allows end users to select any category or period POV for data
processing. End users can access Local mode only if the administrator disables the POV
Mode Lock system option. Usually, only administrators have rights to switch to Local
POV mode, which enables them to change their period and category POV without
changing the POV for all other users.

Changing the POV
1. On the POV bar, click the location, period, or FDM category

name.

2. Select a location, period, or FDM category, and click OK.
Changing the POV

You change the location, period, and category POV by selecting the corresponding tabs
on the POV bar.
Location POV
• Each user has a default location. This location is displayed on the POV bar when the
user logs on to the application.
• Administrators determine user access to locations.
• Users can select and view only those locations to which they have access.
Period POV
• Administrators usually control the period POV for users to ensure that they load data
only to the proper period in the target system.

• When users log on to an application, their period POV is automatically set to the
current global period value.
• A change to the period POV also changes the target system period.
Category POV
• Administrators usually control the category POV for users to ensure that they load
data only to the proper category in the target system.

• When users log on to an application, their category POV is automatically set to the
current global category value.
• FDM categories are associated with target system categories.
• A change to the FDM Category POV also changes the target system category.

Searching for POV Members
1. In the Change Point-of-View dialog box, click .

2. Enter the search text, and click OK.

Searching for POV Members

Applications can contain many locations, periods, and categories. To find POV members,
you can search by entering an entire member name or a portion of it. The example on
the slide searches for members that begin with n.

Locking Out Users for Maintenance
1. On the POV bar, click the System Lock Status tab.

2. In the Change System Lock Status dialog box, select the

On/Off check box, and click OK.
Locking Out Users for Maintenance

All users must be logged off the application before you can perform database
maintenance, such as updating dimension maps, import formats, and validation rules. As
the administrator, you must lock the system to force users out of the application and to
prevent them from logging on again. You can send a message to users when they are
disconnected from FDM, informing them that the application is locked for maintenance
and giving them an estimate of the length of time.
NOTE
FDM does not terminate user sessions if the users are currently writing records to
the database.

Running Reports

Running Reports
FDM includes many predefined audit, log, system, and process management reports.
To run reports:
1. In the FDM Web client, select Analysis > Reports.
The Reports window is displayed.
2. From Groups, select a group of reports.
The Reports window lists reports that are associated with the
selected group.
3. Select a report.

4. From the output format list, select the output format: Excel, Word, PDF, Rich Text Format,
or HTML.
5. Click Publish.
Depending on the report, either the Report Parameters window or
the File Download dialog box is displayed.
6. If prompted for report parameters, select the parameter values, and click OK.

The File Download dialog box is displayed.
7. Perform one of the following actions:
• Click Open to open the report in the selected output format.
• Click Save to save the report in the selected output format.
8. If you opened the report, select File > Exit to close the report.
9. Select File > Close to close the Report Parameters window.

Running Process Monitor Reports
1. From Groups, select Process Monitor Reports.

2. Select a report and the output format, and click Publish.

Process Monitor (Cat, Per) report
Running Process Monitor Reports

You display process monitor reports to monitor the status of the closing process. Process
monitor reports display locations, their status, and positions within the workflow process.
The reports contain a time stamp that indicates when data was loaded.
The example in the slide shows that you completed the workflow process for the Texas
location, and its status is a green CHK. For the California location, the red VALx status
indicates that the validation task was not successful.

Changing Report and Group Descriptions

Report Group Properties Report Properties
Changing Report and Group Descriptions

From Workbench, you can modify report group descriptions and report descriptions.
To change report group descriptions:

1. In Workbench Client, select the Reports tab.
2. Expand the report folder for the language of your choice.
The report groups are displayed.
3. Right-click a report group, and select Properties.
The Report Group Properties dialog box is displayed.
4. In the Description field, edit the title of the report group, and click OK.

To change report descriptions:

1. In Workbench Client, select the Reports tab.
2. Expand the report folder for the language of your choice.
The report groups are displayed.
3. Expand a report group.

A list of the reports in the group is displayed.
4. Right-click a report, and select Report Definition Properties.
The Report Properties dialog box is displayed.
5. In the Description field, edit the title of the report, and click OK.

Viewing Graphical Timelines

Period
tab
Viewing Graphical Timelines

With the Timeline Viewer, you can filter and analyze data-loading events in a linear
graphical format. You can filter the timeline to display events for specific dates, periods,
and categories.
The timeline displays the following events: the date and time locations started the
workflow process, when they ended in errors, when they repeated steps, and when they
made map changes within a time range. The timeline enables you to find locations that
have problems with the load portion of the close process.
To run Timeline Viewer:

1. In the FDM Web client, select Analysis > Timeline.
The Timeline Viewer window is displayed.

2. Select a tab:
• Select the Dates tab to filter the timeline by a range of dates.
• Select the Period tab to filter the timeline by a period.
• On the Dates tab, select a start date and end date.

• On the Period tab, select a period.
4. Select the events to display on the timeline:
• From Category, select a category, or select [All Categories].
• From Workflow Events, select the events to display—Import, Export, Review/Submit,
and Check.
• From Mapping Events, select the events to display—Import and Changes.
• Select Multiload to display Multiload events on the timeline.
• Select All Events to display all events on the timeline.
5. From Locations, select the locations to display on the timeline.
6. Click Get Timeline.
The timeline displays the selected events and locations.

Viewing Events

Single event
for Texas
Multiple events
for Indiana
Viewing Events
The timeline displays the selected events for each location.
• The events on the timeline are color-coded.
• You can roll the cursor over an event to reveal the tooltip with the event details.
• Black markers on the timeline designate multiple, overlapping events. Left-click a
marker to display all events that correspond with the marker.
• By default, the timeline displays only the last instance of an event. You can view all
instances of an event and its subevents. Subevents include processing tasks such as
processing maps, writing to and deleting temporary tables, exporting data, and
loading files.

To view all instances of an event:

1. In the timeline view of events, left-click an event, and select All <name of event> Events
or All (name of event) Events and Subevents.
A timeline displays all instances of the selected event, with or
without subevents, depending on the option that you selected.
2. Roll the cursor over an event in the timeline.

The event details are displayed.
3. Click Back to return to the previous timeline view.

Changing the Timeline Viewer Display

Changing the Timeline Viewer Display

You can change the number of locations that are displayed in Timeline Viewer. The
default number of locations per page is three.
To change the number of locations that are displayed on a Timeline

Viewer page:
1. In the FDM Web client, select Administration > Configuration Settings.
The Configuration Settings dialog box is displayed.
2. From Options, select Number of Locations per Page.
3. From Value, select the number of locations to display (2–10).
4. Click Save.

Summary

• Access Workbench and the FDM Web client
• Navigate the user interface
• Set the point of view
• Lock the system
• Run reports
• View graphical timelines

M O D U L E 2
Building FDM Applications 2

Overview
The aim of this module is to create FDM applications. You learn to create
FDM applications and integrate the applications with target systems. You
also learn to set up control tables and locations.
• Creating FDM Applications
• Integrating Applications
• Setting Up Control Tables and Locations

L E S S O N 3
Creating FDM Applications 3

Objectives
• Describe the application-building process
• Explain the directory structure of applications
• Modify, remove, and add applications
Module 2 Building FDM Applications
Lesson 3 Creating FDM Applications
About FDM Applications

Relational Database
Management Application directories
System database
FDM application
About FDM Applications

FDM applications consist of a Relational Database Management System (RDBMS)
database and application directories. The RDBMS database stores the application
metadata and data. The directories contain script files, logs, reports, and other files such
as source and load files that you use in the FDM application. You can load data from one
FDM application to multiple target system applications.
Supported target systems:
• Hyperion Enterprise
• Financial Management
• Planning
• Essbase
• Other consolidation, reporting, planning, and analytical applications

Data Requirements

Account mapping file
Source GL extract file Custom dimension

mapping files
Entity mapping file
Data Requirements
To build an application, you should have a source general ledger (GL) extract file and
mapping files.
• Source general ledger extract file—ASCII text file or report from a source system.
Each record in the source file must contain an account number, an amount, and any
additional dimensions that describe the record. If the file contains multiple entities,
you must identify the entity for each record.
• Account mapping file—File that maps the source system accounts to the target
system accounts. Valid mapping files include LedgerLink extract files (TRA),
Hyperion Enterprise conversion table extracts, Microsoft Excel maps, and any other
mapping sources such as databases.

• Entity mapping file—File that maps the source system entities to the target system
entities. Valid mapping files include LedgerLink extract files (TRN), Hyperion
Enterprise conversion table extracts, Excel maps, and any other mapping sources
such as databases.
• Intercompany Partner (ICP) and custom dimension mapping files—Files that
map source system ICP and custom dimensions to target system custom
dimensions.

You must create mappings for all dimensions in the target system application. In addition
to creating the mappings by using external files, you can manually create dimension
mappings in the FDM Web client.

Application-Building Process
1. Create application

2. Integrate with target application
3. Populate control tables
4. Set up locations
5. Build and import maps
6. Build import formats
7. Import, validate, and export data
8. Build validation rules and reports
Application-Building Process
Follow these steps to build an application:
1. Create an FDM application and identify its database type.
2. Integrate the application with a target system application to which you want to load
data. Integrating an application includes tasks such as importing and registering the
target system adapter, adding a machine profile, verifying application settings, and
selecting and testing the integration settings.
3. Populate control tables to define the valid periods and categories that correspond to
the target system application, and to verify the list of currency codes used in reports.
4. Set up data-load locations that accept data from source systems and set up controls-
review locations for financial reviews to comply with the Sarbanes-Oxley Act.

5. Build and import maps to map the source dimension members to their corresponding
target system dimension members.
6. Build import formats for locations to interpret source data files and import them into
FDM applications.
7. Import data from source systems into FDM applications by using import formats.
Validate the dimension mappings and export the data to target system applications.

8. Build validation rules and reports to enforce data integrity during the data export to
target system applications.

Creating Applications
1. Launch the FDM Web client, select <New Application>,

enter a user name and password, and click Logon.

2. On the New Application General tab, enter the application
name, description, path, and application group.
Creating Applications
You create an application by using the FDM Web client or Workbench. The user name
and password that you provide is the administrator for the new application.
When creating an application, you must provide general and database information. The
general information includes the application name, description, and path, as described in
the following table:
Field Description
Name Application name (The name must begin with a letter and can consist of
letters, numbers, and underscores.)
Description Application description

Field Description
Path Location for the application’s directory structure (FDM creates a
directory with the same name as the application name under this path.)
App Group Application group name in Shared Services (This field is displayed when
Shared Services is the authentication provider.)

NOTE
If users access the application by using multiple Web and application servers, it is
recommended that you use the Universal Naming Convention (UNC) for the path
to avoid problems with inconsistent driver letter mapping. The UNC format is
\\server-name\shared-directory-name.

Selecting Database Settings

Selecting Database Settings

When creating an application, you provide database information to define the RDBMS
database that stores the FDM transaction data. The example on the slide defines an
Oracle RDBMS database.
The following table describes the database settings:
Field Description
OLE DB Provider RDBMS database used by the application; either
ORAOLEDB.ORACLE or SQLOLEDB
Database Server Database server name of the database used by the application
(SQL only)
Database Name Name of the RDBMS database; typically the same as the application
(SQL only) name
Service (Oracle only) Oracle service used to connect to the Oracle database

Field Description
Use Windows Local user ID for database access
Integrated Security
Username Database administrator name; for example, the SQLOLEDB
administrator ID
Password Database administrator password

Options (Oracle only) Options to override the default table space for the application
NOTE
You must create table space for the user in the Oracle instance before you create
an FDM application that uses an Oracle RDBMS database.
When you create an application, FDM performs the following tasks:

• Creates the RDBMS database
• Creates the application directory structure below the application path
• Adds the application name to the HyperionFDMApplications.xml file located in the
<installation directory>\FDM\SharedComponents\Config directory

Directory Structure of Applications

Application path
Application name
Directory Structure of Applications

FDM creates an application directory structure for each application. The directory
structure contains Data, Inbox, Outbox, and Reports directories.
Data Directory
The Data directory stores all imported source files, import logs, journal entries, multiload
files, target system load files, and attached memo documents. All files processed by
FDM are automatically archived in this directory. Each file provides a complete audit trail.

The Data directory also contains a Scripts directory to store FDM script files. The Scripts
directory contains subdirectories for each type of script:
Subdirectory Contents
Custom Custom script files that you execute through a custom menu created in the
Menu Maker form
Event Event script files that are executed when a particular event occurs (Each
event script has the same name as its corresponding event.)

Import Import script files that you create when defining import formats (Import
scripts are executed during the source file import process.)
Inbox Directory
The Inbox directory is the default location for import files. You use the Inbox directory as
a central location for all ledger extract files. You can add subdirectories to categorize files
for each location; for example, create a Texas subdirectory for the Texas import files.
The Inbox directory contains two subdirectories:
ArchiveRestore Restored import source files and logs that were previously archived
Batches Two subdirectories for batch files that you load by using the batch loader:
• The OpenBatch subdirectory contains standard batch files.
• The OpenBatchML subdirectory contains multiload batch files.
Outbox Directory
The Outbox directory is the default location for exporting data files. You use this directory
as a central location for all export files that you subsequently load into a target system
application.
The Outbox directory contains four subdirectories:
ArchiveRestore Restored data load files that were previously archived
ExcelFiles Excel files that are created when you export the contents of a grid to
Excel
Logs Log files that are created when you import source files; also error logs
named with the user name and ERR file type
Templates Files that are used to manage and distribute custom journal or multiload
templates
Reports Directory
The Reports directory contains the Active Report files. These files have an RPX file type.

Managing Applications
1. Launch the FDM Web client, select <Add Application>,

enter a user name and password, and click Logon.

2. In the Applications dialog box, select the application.
3. Click Add, Modify, or Remove.
Managing Applications
You can modify, remove, and add applications. FDM displays the application names in
the Applications dialog box by retrieving the names from the file named
HyperionFDMApplications.xml.
Modifying Applications
You can modify all application settings except for the application name. To change the
application name, you must remove the application and add it again. To change
application settings, you complete the same General and Database dialog boxes that are
used for creating an application.

Removing Applications
You can remove applications from the application XML file. For example, you can create
and work with a test application and later remove it so that other users cannot see it in
the application list. When you remove applications, the application data and directory
structure are not deleted or affected.
Adding Applications

You can add applications to the application XML file.You must add an application when
the application exists, but there is no pointer to it in the application XML file. When you
add an application, you complete the same General and Database dialog boxes that are
used for creating an application, but you specify the path of an existing application. You
can specify another name for the added application that is different from the existing
application name.

Summary

• Describe the application-building process
• Explain the directory structure of applications
• Modify, remove, and add applications

3-16

L E S S O N 4
Integrating Applications 4

Objectives
• Import and register adapters
• Add machine profiles and verify application settings
• Update integration settings
• Associate dimensions
• Test integrations
• Import standard reports and templates
Lesson 4 Integrating Applications
Integration Overview
Integration process:

1. Import and register adapters
2. Add machine profiles
3. Verify application settings
4. Update integration settings
5. Associate FDM dimensions
6. Test integration settings
7. Import standard reports and templates
Integration Overview
You use integration settings to point FDM applications to target applications, such as
Financial Management and Essbase.
You can load data from one FDM application to an unlimited number of target
applications. For example, you can load data from some locations in the FDM application
to a Hyperion Enterprise application, while other locations load data to a Financial
Management application. In addition, you can configure one FDM application to load to
several different target applications from the same product, such as two different
Essbase applications.
After integrating the FDM application with the target application, you import the standard
reports and copy the standard templates into the directory structure of the FDM
application.
You complete the integration process in Workbench.

Importing and Registering Adapters
FDM

Adapters
Source systems Target systems
Importing and Registering Adapters

Adapters are predefined software codes that communicate with source and target
applications. Each adapter integrates with a specific target system (for example,
Essbase or Financial Management) or source system (for example, Oracle E-Business
Suite Financials or SQL).
Adapter Components
Adapters consist of two components—the XML and the DLL-EXE.

Adapter XML
The adapter XML contains all data relating to the integrated FDM application. The XML
acts as a second layer between FDM and target applications. It stores application setup
parameters and scripts to call API functions that return the results from target
applications. The XML file can also contain information that you need to set up other
FDM applications, such as locations, security, import formats, and reports.
The following table describes the XML sections:

Section Description
Dimensions Available dimensions for the target application
Actions Scripts that interact with the target application and use API calls to
perform functions, such as Connect, Load, ValueGet, and Export
Machine Profiles Location of source and target systems
Options Default options for the FDM integration and application settings for the
target application
Adapter DLL or EXE

The adapter DLL or EXE acts as a buffer between FDM and target or source
applications. The DLL or EXE contains the instructions for FDM to communicate with the
applications, such as connecting to the database, loading data, extracting data, and so
on. Each DLL contains the API calls for specific target applications. This flexibility
enables FDM to integrate with many target systems and not have to maintain large
amounts of application-specific calls within the FDM program.

Importing and Configuring

Source System Adapters
On the Adapters tab in Workbench, select File > Import.

Select source
adapter XML file.
Select items
to import. Imported source adapter.
Importing and Configuring Source System Adapters

You can import data from Oracle E-Business Suite (EBS) Financials into FDM with the
FDM source adapter for EBS Financials. After importing the data to FDM, you can drill
back from FDM to EBS to view the source data.
You configure EBS source-adapter options so that FDM can pull data from EBS and drill
back to EBS. For example, to pull data from EBS, you define the EBS database server
name, schema name, and password. To drill back to EBS, you enable drillback, define
the URL of the EBS Financials Web server, and the URL for the EBS Financials landing
page.
NOTE
For complete details about required options, see the Oracle Hyperion Financial
Data Quality Management Source Adapter for Oracle E-Business Suite Financials
readme file.

To import source system adapters:

1. In Workbench, select the Adapters tab.
2. Select File > Import.
The Open Metadata Import File window is displayed.
NOTE

The location of the adapter XML file depends on the location of the extracted
file. You typically place the file in the FDM installation directory.
3. Browse to select the adapter file, and click Open.

The General tab of the Import dialog box is displayed.
4. Click Select All.
5. Select the Options tab.
6. Select the Save existing machine profiles check box.
If you do not select this box, FDM deletes existing machine
profiles.
7. Click OK.
The imported source adapter is displayed in the Integration
Adapters window.
To configure E-Business Suite Financials adapters:

2. Expand Source System Adapters.
3. Right-click (EBS-FIN-B) Oracle Hyperion FDM Source Adapter for EBS Financials, and select
Options.
The Adapter Options dialog box is displayed.
4. From the Options list, select an option.
5. Enter or select the value for the option.
6. Repeat steps 4 and 5 for other required options.
7. Click Save and Close.

Importing Target System Adapters
1. On the Adapters tab in Workbench, select File > Import.

2. Select the target adapter XML file, and click Open.

Select items to import. Select import options. Imported target adapter.
Importing Target System Adapters

You must import an adapter XML for each FDM application. You import the adapter from
the Adapters tab in Workbench. For the example on the slide, you import an adapter for
Financial Management.
Typically, you work with one adapter in an FDM application, but you can also work with
multiple adapters to load data from one FDM application to multiple target system
applications.
The adapter XML file names vary for each release, as shown in the following table:
Adapter File Name Target System

FMxx.xml and HFMxx.xml Financial Management
ESxx.xml and Essxx.xml Essbase and Planning
HExx.xml and HETxx.xml Hyperion Enterprise

Adapter File Name Target System

SFxx.xml Strategic Finance
Pullxx.xml not applicable
To import target system adapters:


NOTE
The location of the adapter XML file depends on the location of the extracted
file. You typically place the file in the FDM installation directory.
3. Browse to select the adapter file, and click Open.

If you do not select this box, FDM deletes existing machine
profiles.
7. Select the Remove all report groups before updating reports check box to delete existing
report groups before updating the application with new reports.
8. Select the Import maps with locations check box to import maps that are assigned to
locations.
9. Click OK.
The imported adapter is displayed in the Integration Adapters
window.

Financial Management Adapters
Dimension properties

Right-click the
dimension,
Available and select
dimensions. Properties.
Financial Management Adapters

The Dimensions folder for Financial Management adapters contains a list of available
dimensions for Financial Management target systems. The dimmed dimension names
represent inactive dimensions. You can modify the properties of dimensions and
dimension labels; for example, you can activate a dimension or change the dimension
alias.
NOTE
Every dimension has an icon to the left of its name. Dimensions with a green M
are dimensions that you can map to target system dimensions. Dimensions with a
red G are not mappable and receive their values in other ways; for example, from
the POV (Category, Period, Year).

Hyperion Enterprise Adapters
Imported
Hyperion

Enterprise
Available
adapter
dimensions
Hyperion Enterprise Adapters

The Dimensions folder for Hyperion Enterprise adapters contains a list of available
dimensions for Hyperion Enterprise target systems. The dimmed dimension names
alias.

Essbase Adapters
Imported
Essbase

Available adapter
dimensions
Essbase Adapters
The Dimensions folder for Essbase adapters contains a list of the available dimensions
for Essbase target systems. The dimmed dimension names represent inactive
dimensions. You can modify the properties of dimensions and dimension labels; for
example, you can activate a dimension or change the dimension alias.

Strategic Finance Adapters
Imported

Strategic Finance
Available adapter
dimensions
Strategic Finance Adapters

The Dimensions folder for Strategic Finance adapters contains a list of the available
dimensions for Strategic Finance target systems. The dimmed dimension names
alias.
You configure the Strategic Finance adapter so that FDM can connect to the target
Strategic Finance database.
To configure Strategic Finance adapters:

2. Expand Target System Adapters.

3. Right-click the Strategic Finance adapter, and select Options.

The Adapter Options dialog box is displayed.
4. From the Options list, select an option.
5. Enter or select the value for the option.
6. Repeat steps 4 and 5 for other required options.

NOTE
For complete details about required options, see the Oracle Hyperion
Financial Data Quality Management Adapter for Strategic Finance readme
file.
7. Click Save and Close.

Registering Adapters
1. In Workbench, select File > Register Adapter.

2. Select the adapter DLL-EXE file, and click Open.

Registering Adapters
After importing the adapter, you must register it. You must import an adapter XML for
each FDM application, but you register the adapter DLL-EXE only one time for each
adapter on a machine. For example, if you create two FDM applications to integrate with
two Financial Management applications, you must import the Financial Management
adapter XML for each FDM application, but you must register the Financial Management
adapter DLL once for each application server or Workbench installation.
The adapter DLL-EXE file names vary for each release, as shown in the following table:
Adapter File Name System

oraEBSFINxxx.dll E-Business Suite Financials source system
upsFMxxx.dll Financial Management target system
upsEBxxx.exe Essbase and Planning target system

Adapter File Name System

upsENxxx.exe Hyperion Enterprise target system
upsHSFxxx.dll Strategic Finance target system

Adding Machine Profiles

2. Expand the adapters folder and the adapter name.

3. Right click Machine Profiles, and select Add Machine
Profile.
4. Complete the Add Machine Profile dialog box, and click OK.
Adding Machine Profiles

Machine profiles specify the location of the source and target systems, and also store
global logon information to connect to target applications.
You must set up a machine profile for every adapter in the FDM application. For
example, if you import the Financial Management and Essbase adapters into the FDM
application, you must set up a machine profile for each adapter. The machine profile for
the Financial Management adapter specifies the location of the Financial Management
target system, and the machine profile for the Essbase adapter specifies the location of
the Essbase target system.

The following table describes the machine profile fields:
Field Description
Source Machine FDM application server name
Target Machine Computer name or IP address of the target or source application server
or cluster
User Name Local machine user name that overrides the global logon method in

Integration Settings
Password and Password for the target machine
Confirm Password
Domain (optional) Domain name of the target machine
Most often, you do not enter a user name and password in the machine profile. In that
case, FDM employs user network authentication to access target systems. However, if
you select the global logon integration setting, and you enter a user name and password
in the machine profile, then FDM uses this user name and password to log on to the
target system. The user name that you specify in the machine profile must have access
to the target server and have the appropriate security privileges in the target application.
NOTE
The user name and password are required in Essbase machine profiles.
Integration settings are covered later in this lesson.

Verifying Application Settings
1. In FDM Web client, select Administration > Application

Settings.

2. From Options, select System Code.
3. Verify the name of the target system adapter, and click Save.
Financial Management
target system adapter
Verifying Application Settings

Application settings are global system options that affect the behavior of an FDM
application. You specify values for application settings options, such as the target
system, to integrate with FDM, license keys, and location folder options.
After setting up one or more adapters and machine profiles, you use the System Code
application setting to select the name of the default adapter to integrate with the FDM
application. The System Code list includes the adapters that you added to the
application.
NOTE
You can override the default adapter for each location.

Updating Integration Settings
1. In FDM Web client, select Administration > Integration

Settings.
2. From Options, select an option.

3. Select or enter the option value, and click Save.
Updating Integration Settings

You select integration settings to set the levels of integration between FDM applications
and target systems. You can update options such as the target application name, logon
method, and global logon information.
The examples on the slide are for Financial Management and Essbase adapters.
Integration settings for Hyperion Enterprise are covered later in the lesson.
Application Name Option

You select the Application Name option to specify the name of the target application to
integrate with the FDM application.

Logon Method Option

You select the Logon Method option to specify the method that FDM uses to log on to the
target system. There are two logon methods, Unified and Global:
• Unified—The FDM user name and password are used to log on to the target system.
The user name and password must be valid in the target system.
• Global—The user name and password specified in the Global Logon Information

option are used to log on to the target system. With this option, all users connect to
the target system by using the same user name and password.
NOTE
If you specify a user name and password in the machine profile, the user name
and password override the integration settings logon method.
Global Logon Information Option

If the Logon Method option is set to Global, you use the Global Logon Information option
to specify the user name and password that FDM uses to log on to the target system.

Integrating Hyperion Enterprise Applications
In Workbench, select Tools > Integration Settings.

Integrating Hyperion Enterprise Applications

In Workbench, you specify integration settings between FDM applications and Hyperion
Enterprise target systems.
You first set up Hyperion Enterprise as the default adapter by modifying the System
Code option in Application Settings. You then perform the following Integration Settings
tasks:
1. On the Integration tab, select the Hyperion Enterprise target application name and
logon method.
2. On the NameCat Editor tab, select the Hyperion Enterprise entity and category
members.
3. Optional: On the Dimension Caching tab, update the dimension cache.

When you integrate Hyperion Enterprise target applications, you must specify the
Hyperion Enterprise name and category that FDM uses to determine whether an
Enterprise account is calculated. Select a name that represents a typical base-level
name, and then select a category that stores actual data. FDM stores this information in
the NameCat.txt file.
Hyperion Enterprise adapters can store Hyperion Enterprise Account and Entity
dimension members within FDM applications. This feature enables FDM to cache the

dimension members and display them more quickly than by retrieving the members from
the target system. You should update the dimension cache whenever you update
Account and Entity dimension members in Hyperion Enterprise.
To specify integration settings for Hyperion Enterprise target

systems:
1. In Workbench, select Tools > Integration Settings.
The Integration tab of the Hyperion Enterprise Integration Setup
dialog box is displayed.
2. In the Application Name box, enter the Hyperion Enterprise target application name.
3. For Logon Method, select 1 - Unified or 2 - Global.
4. Select the NameCat.txt Editor tab.
5. Click the entity lookup button and select a base name from the Hyperion
Enterprise target application.
6. Click the category lookup button and select a category from the Hyperion
Enterprise target application.
7. Select the Dimension Caching tab, and click Update Cache.
The dimension cache is updated, and the update statistics are
displayed.
8. Click Save and Close to save the integration settings and close the dialog box.

Associating Dimensions Between Applications

Essbase dimensions
on the Workbench
Adapters tab
Outline in Essbase
Administration Services
Associating Dimensions Between Applications

To integrate FDM applications with Essbase target applications, you must associate the
FDM dimensions with Essbase target database dimensions.
To associate FDM dimensions with Essbase dimensions:

2. Open the Essbase database outline and Workbench side by side:
• In Oracle Essbase Administration Services Console, open the Essbase database
outline.
• On the Adapters tab in Workbench, for the Essbase adapter, expand the
Dimensions folder.

3. In Workbench, right-click the ACCOUNT dimension, and select Properties.

The ACCOUNT (EBAccount) Properties dialog box is displayed.
4. Update the Foreign Name and Alias boxes to reflect the associated Essbase
dimension name and alias.
5. Repeat steps 3 and 4 for each FDM dimension.

Testing Integrations
1. In the FDM Web client, select Activities > Maps, and click
Add to add a row.

2. Double-click in the Target FM Account field, and select
Browse for Target Value.
Testing Integrations
In the Maps window in the FDM Web client, you can test the integration of the FDM
application with the target system. If you configured the integration settings correctly,
when you browse for a target account, a window displays the list of accounts from the
target system.

Importing Standard Reports and Templates
In Workbench, select the Reports tab, and select File > Import.

Importing Standard Reports and Templates

FDM includes many predefined reports and templates that you can add to an FDM
application.
Standard Templates
You must extract the standard templates from the FinancialDataManagement-
Templates11110.zip file to the <application-name>\Outbox\Templates directory.
Standard Reports
The standard reports are defined in an XML file applicable to the RDBMS database
(Oracle or SQL) that you selected for the FDM application. You must extract the
appropriate XML file from the FinancialDataManagement-Reports11110.zip file before
importing the XML file into FDM.

To import standard reports:

1. In Workbench, select the Reports tab.
3. Browse to select the StandardReportsOracle1111Active.xml file for an Oracle database or
the StandardReportsSQLServer1111Active.xml file for a SQL database, and click Open.

If you do not select this check box, existing machine profiles are
deleted.
7. Select the Remove all report groups before updating reports check box to delete existing
report groups before updating the application with new reports.
8. Select the Import maps with locations check box to import maps that are assigned to
locations.
9. Click OK.
The reports are displayed in the Reports window. The Active
reports are located in the <app-name>\Reports directory and
have an RPX file type.

Summary

• Import and register adapters
• Add machine profiles and verify application settings
• Update integration settings
• Associate dimensions
• Test integrations
• Import standard reports and templates

L E S S O N 5
Setting Up Control Tables and Locations 5

Objectives
• View control tables
• Modify control tables
• View locations
• Add locations
• Set location attributes
• Search control trees
Lesson 5 Setting Up Control Tables and Locations
Viewing Control Tables
1. In the FDM Web client, select MetaData > Control Tables.

2. From Control Table, select the control table that you want to

view.
Viewing Control Tables

Control tables enable you to control the POV values that users can select. You maintain
two control tables, Periods and Categories, for each target system. You specify the target
system with which to work by selecting the adapter name in the Control Tables window.
In the Periods and Categories control tables, you add members to define the FDM
periods and categories and their corresponding members in the target application. These
periods and categories define the selectable members in the POV. The members also
define the periods and categories for which you can load data for the target application.
For the example on the slide, three categories are defined for the FDM category POV for
the Financial Management global adapter.
You can also view a third table, Currency Codes, which is global for all target systems.
The Currency Code control table lists the currencies that are displayed in reports.

Modifying Control Tables
Add a row. Save the changes.

Enter row attributes. Browse for
target members.
Modifying Control Tables

You can add, modify, and delete periods, categories, and currencies in control tables.
NOTE
You can modify the Currency Codes control table only with Excel worksheets, as
described later in this lesson.
You must select the global adapter to add periods and categories to the control tables.
You map the periods and categories to target periods and target categories from the
target application. After the periods and categories are added for the global adapter, you
can map them for other adapters in the FDM application.

For the example on the slide, you add four FDM categories for the Financial
Management global adapter. You map the categories to target categories in the Financial
Management target application. When you select the Essbase adapter, the four FDM
categories are displayed, and you must map them to target categories in the Essbase
target application.
To add periods and categories to control tables:

1. In FDM Web client, select MetaData > Control Tables.
2. Click Control Table and select Periods or Categories.
3. Click .
A blank row is added to the control table.
4. Double-click in each column to enter member attributes.
5. Double-click in the Target Category or Target Per column, click the arrow, and select
Browse for Target Category or Browse for Target Period to select a valid member from the
target application.
The Target Category Lookup or Target Period Lookup dialog box
is displayed.
6. Select the corresponding target member and click OK.
7. Click to save the changes.

Deleting Periods and Categories

Pending Pending
update deletion
button button
Deleting Periods and Categories

You can modify and delete periods and categories that are not currently selected in the
POV. You can also modify currency codes.
When you add or modify a row, a pending update button is displayed to the left of the
row. When you delete a row, a pending deletion button is displayed. When you save the
changes, the buttons are automatically removed.
To delete periods and categories from control tables:

2. From Control Table, select Periods or Categories.
3. Select the row that you want to delete, and click .
A pending deletion button is displayed to the left of the row.

4. Click Update Grid to save the changes.

The row is deleted from the control table, and the pending
deletion button is removed.
NOTE
You must lock the system before you delete periods and categories. Deleted
periods are removed from all categories in all locations. Imported data that is

associated with the deleted periods and categories is also deleted.
You can cancel changes made to control tables.
To cancel updates to control tables:

• Click the pending deletion button or pending update button and then click
Cancel Row Changes.

Adding Categories

Adding Categories
Categories that you define in the Categories control table identify the list of categories
that users can select in the FDM category POV. You associate each FDM category with a
target system category. For the example on the slide, the Target Category Lookup dialog
box displays the scenarios from a Financial Management application. If you change the
FDM category POV, the target system category where you load data also changes.
You define the following attributes for FDM periods:
Attribute Description
Category Key Numeric value generated by FDM to identify records
Category FDM category name
Description Long name for FDM category

Target Category Target system category where the data will be loaded
Frequency Category frequency—Monthly, Quarterly, Yearly, or Daily
You do not enter a value in the Category Key column. FDM assigns a numeric value to
each category, and stores the value during the trial balance load process. The category
key is part of the key that uniquely identifies each set of trial balance records.

Adding Periods

Adding Periods
Periods that you define in the Periods control table identify the list of periods that users
can select in the period POV. You associate each FDM period with a target system
period. If you change the FDM period POV, the target system period where you load data
also changes.
You define the following attributes for FDM periods:
Period Date value stored in the database during the trial balance
load process (Each value is part of a key that identifies a set
of trial-balance records.)
Prior Date Key Prior fiscal period
Text Description Description of the date

Target Per (M), (Q), (Y), (D) Target system period to which data is loaded (Target periods
are (M) monthly, (Q) quarterly, (Y) yearly, and (D) daily.)
Year Target Year value
By default, FDM populates the Text Description column when you save changes to the
control table. For the example on the slide, you add the period 4/30/2008, and when you

save the changes, Apr - 2008 is displayed in the Text Description column. You control the
format of the description with the Period Key Date Format Mask application setting. To
create custom period descriptions that override the default values, you must enable the
“Allow custom description in period” configuration setting.

Modifying Control Tables with Excel Worksheets

Unhide rows 6 and 7.
Modifying Control Tables with Excel Worksheets

You can define metadata in control tables by exporting a few metadata rows to an Excel
worksheet, adding metadata rows to the worksheet in Excel, and then importing the
Excel worksheet to the FDM control tables. With this method, you can import large
amounts of application metadata without entering each line manually in the FDM Web
client control tables.
Exporting Metadata to Excel

With the Export to Excel option, you export metadata rows from FDM control tables to an
Excel worksheet.

For the example on the slide, the default file name for the exported periods is
Periods54955.xls. When you open the file in Excel, you can display hidden rows 6 and 7.
These rows include metadata tags that FDM uses to interpret the metadata that you want
to load. The file also contain metadata rows that you want to import into the FDM control
table.
To export metadata from control tables:

2. From Control Table, select Periods, Categories, or Currency Codes.
3. Click Export to Excel.
The File Download dialog box is displayed.
• Click Open to open the metadata list in Excel.
• Click Save to save the metadata list as an Excel worksheet that you can open later.
NOTE
By default, FDM saves the file in the <application-name>/Outbox/ExcelFiles
directory.

Modifying the upstPOVPeriod Range
• In this example, the upstPOVPeriod range is rows 6 - 12.

• The first cell of the range contains the FDM control table

name, tPOVPeriod.
• The second row of the range contains the control table field
names.
Modifying the upstPOVPeriod Range

To use the Excel worksheet as an import source, the worksheet must have an import
range that contains the control table name, the field names in the control table, and the
metadata that you want to import.
The range names begin with the prefix ups. For the example on the slide, the range
name, upstPOVPeriod, includes the control table information in rows 6 and 7, and the
metadata in rows 8 through 12.
Dates in the metadata should be formatted text.

To modify the upstPOVPeriod range:

1. In Excel, open the exported period file.
2. Select Insert > Name > Define.
The Define Name dialog box is displayed.
3. From the “Names in workbook” area, select upstPOVPeriod.

The defined range is displayed in the “Refers to” box.
4. In the “Refers to” box, modify the range of rows that you want to import.
5. Click OK.
6. In the name box at the top left of the worksheet, click the down arrow, and select
upstPOVPeriod.
The range of rows is highlighted.

Importing Metadata from Excel
In the FDM Web client, select Tools > Import XLS.

Method 1:
Upload
File tab
Method 2:
Select File
From Inbox tab
Importing Metadata from Excel

With the Import XLS tool, you import metadata into control tables in the current FDM
application.
To import metadata from Excel worksheets:

1. In the FDM Web client, select Tools > Import XLS.
The Import XLS window is displayed.
• On the Upload File tab, browse to select the file, and click Import.

• On the Select File From Inbox tab, click Select File, select the file from the
appropriate Inbox directory or subdirectory, and click OK.
FDM loads the periods, categories, or currency codes to the
corresponding control table.

Viewing Currency Codes

Viewing Currency Codes

The Currency Codes control table contains a list of currency codes that you can assign to
locations. The currency codes are displayed in reports and are used only for notations.
FDM currency codes do not affect calculations because FDM does not perform currency
translation.
To view currencies in the Currency Code control table:

2. From Control Table, select Currency Codes.

Viewing Locations
In the FDM Web client, select MetaData > Locations, and

select the location name.

Viewing Locations
Locations are reporting units that you use to load source data to target systems.
Typically, there is one location for each source data file that you load. You create multiple
locations (for example, for divisions or geographical areas) to split up the data loads and
improve performance.
End users have access to one or more locations, with one location designated as their
default location. When a user logs on to FDM, the user’s POV is set to that person’s
default location.

There are two types of locations—data load and controls review.
Data Load
Data-load locations accept data from source systems and load the data to target
systems. You can assign financial controls to data-load locations to assist with a
company’s internal financial control policies. Data-load locations can only be children in
the Controls tree structure; they cannot be parents. You create maps and assign import

formats for data-load locations.
Controls Review
Controls review locations are assigned financial controls to assist with a company’s
internal financial control policies. You do not load data into a controls review location.
Controls review locations are typically parents in the Controls tree structure. A controls
review location can also be a child of another controls review location.
When you create an FDM application, one sample financial controls location named
Controls Review and one sample data-load location named Sample are created.

Adding Locations

Select Data Load or
Controls Review.
Select Add Sibling

or Add Child.
Adding Locations
Before adding locations, you should develop a naming convention for locations. After
creating a location, you can change its name.
When you create a location in the Controls structure, FDM adds a location directory to
the FDM application’s Inbox directory. By default, the directory name is the same as the
location name. You can use location directories to organize general ledger files, journals,
and other documents for each location.
When you delete a location, the location, its children, and all associated data are deleted.
By default, deleting a location does not delete the location directory. You cannot delete a
location if it is currently selected in the POV.

In Financial Management, you can use the phased submissions feature to divide a
process unit into submission groups defined by account, custom, and ICP dimensions.
With the process unit divided, smaller chunks of data are published, giving reviewers and
approvers tighter quality control. However, using the phased submissions feature in
Financial Management when loading data from FDM can cause issues with audit trails
and result in failed exports.
For example, after you submit phase one, any subsequent loads of the same data fail

because of locked intersections. When you reload data in FDM to the same location,
FDM erases the audit trail of the previous export to Financial Management.
To preserve the audit trail and to avoid failed exports, Oracle recommends that you
create a separate FDM location for each Financial Management phase. For example, for
the Texas location, you can set up locations named Texas1, Texas2, and Texas3 to load
data for phase 1, phase 2, and phase 3, respectively. Oracle also recommends that you
separate the source data and the FDM maps by these phased locations.
To add locations:
1. In the FDM Web client, select MetaData > Locations.
2. In the Controls structure, right-click a location name, and select Add Sibling or Add
Child.
The Add Sibling Location or Add Child Location dialog box is
displayed.
3. From Location Type, select Data Load or Controls Review.
4. In the Location Name box, enter the location name, and click OK.
Location names can include alphanumeric characters and
underscores.
To move locations:
2. In the Controls structure, right-click a location name, and select Move.
The Move Location dialog box is displayed.
3. From Move Type, select Move as Child of or Move as Sibling of.
4. From Target Location, select a location name, and click OK.

To rename locations:
2. In the Controls structure, right-click a location name, and select Rename.
The Rename Location dialog box is displayed.
3. In the Type in new Location Name box, enter the location name, and click OK.

To delete locations:
2. In the Controls structure, right-click a location name, and select Delete.
A confirmation prompt is displayed to delete the location, its
children, and all associated data.
3. Click OK.

Setting Location Attributes

Setting Location Attributes

You can assign attributes to locations. For data-load locations, certain attributes are
required for the location to import data into the location properly (Import Formats, for
example) while other attributes are optional (Logic Groups, for example). You define
location attributes on the four attribute tabs—General, Workflow Behaviors, Financial
Controls, and Integration Options.
This lesson covers the location attributes that you define on the General and Workflow
Behaviors tabs. See Lesson 16 for information about the Financial Controls location
attributes.
You use the Integration Options attributes to customize the integration for locations. With
these attributes you can customize up to four options to use in scripts to reference
selected locations.

Setting General Attributes

On the General tab, you specify location attributes such as the description, currency, and
target adapter. The following table describes the attributes:
Description Location description
Currency Currency code that is displayed in certain reports and forms that display

data for this location
Parent Location Name of location whose mapping table is inherited by this location
Load Type Data-load method, either SQL Insert or Bulk Insert
SQL Insert: Default load method that is used for loading smaller files of
6000 records or less
Bulk Insert: Load method that is more efficient for loading larger files
Sequence Map Displays a sequencing field on the Map form that controls the
processing of maps by numeric values rather than alphabetically by the
rule name
Group Tag Group name used to group multiple locations (In certain Process
Monitor reports, grouped locations are displayed in their grouping order
rather than alphabetically.)
Data Value Additional dimension value entered for every data line loaded by this
location (This value is used when integrating with multidimensional
target systems.)
Target Adapter Name of location’s target adapter (The value of [None] defaults to the
global adapter selected in Application Settings.)
Parent Location Attribute

You assign mapping tables to locations to map source system dimension members to
their corresponding target system dimension members. With the Parent Location
attribute, you can share the same mapping table among multiple locations. This method
is useful when multiple locations use the same chart of accounts.
For example, the Texas and Nevada locations use the same chart of accounts. You can
define a mapping table for Nevada, and specify that Nevada is the parent location for
Texas. When you load data for Texas, it uses the same mapping table as Nevada. If you
change the mapping table, the change takes place for both Texas and Nevada. To delete
the mapping table, you must delete it at the parent location.

Data Value Attribute

The Data Value attribute is an additional dimension value that FDM enters for every data
line loaded in a location. For example, the Texas location loads data to a Financial
Management target system. In the Texas location attributes, you specify that the data
value is associated with a Value dimension member from Financial Management. By
default, it is the <Entity Currency> member. When you load Texas data, FDM uses the
default data value, <Entity Currency>, in every data line.

Target Adapter Attribute
Multiple adapters in an FDM application enable you to load data to multiple target
systems. You specify the default adapter for all locations in the System Code application
setting. To override the default location adapter, use the Target Adapter attribute.

Setting Workflow Behaviors Attributes

Setting Workflow Behaviors Attributes

On the Workflow Behaviors tab, you assign an import format, logic group, validation
rules, and validation entities to data-load locations.
Import Format
Import formats define the layout of source data-load files. You must assign an import
format to data-load locations before you can load source data files to the locations. You
do not need to assign import formats when you initially create locations. You can set up
the data-load locations all at once without knowing all the source data-file layouts.

Logic Groups
Logic groups contain one or more logic accounts that FDM generates to calculate values
not provided in the source data file. Logic accounts are calculated accounts that are
derived from the source data. You assign a logic group to locations to dynamically
generate the logic accounts when you load the source data files to the locations.
Validation Rules

Validation rule groups contain validation rules that enforce data integrity during the data-
load process. When you assign a validation rule group to locations, FDM generates the
Validation Report following a data load to the target system. FDM uses the validation
rules to retrieve target system data, and displays the data in the report.
Validation Entities
A validation entity group contains target system entities that you want to consolidate after
a data load and to display in the Validation Report. When you assign a validation entity
group to locations, FDM generates the Validation Report for all entities defined in the
group.

Setting Financial Controls Attributes

Setting Financial Controls Attributes

On the Financial Controls tab, you set up certification and assessment reviewers for
locations.
NOTE
For more information about Financial Controls, see lesson 16, “Working With
Financial Controls”.

Setting Integration Options Attributes

Setting Integration Options Attributes

On the Integration Options tab, you assign custom adapter (for example, Oracle EBS
Financials) options for locations.

Searching Control Trees
1. In the Locations window in the FDM Web client, right-click in

the control tree area, and select Search.

2. In the prompt dialog box, enter a search string, and click OK.
Search
results
Searching Control Trees

You can search for nodes in windows that include control trees, such as the Locations
window. To find locations easily, you enter the entire location name or part of it in the
search text box. The search string is not case-sensitive. The example on the slide
searches for locations that begin with div.

Summary

• View control tables
• Modify control tables
• View locations
• Add locations
• Set location attributes
• Search control trees

5-32

M O D U L E 3
Building the Workflow Process 5

Overview
The aim of this module is to build the workflow process for loading data to
target systems. You learn to set up mapping tables, build import formats,
and load data. You also learn to build validation rules and set up validation
entities to enforce data integrity during the data load process. You process
and schedule batch files to execute the workflow process tasks.
• Setting Up Mapping Tables
• Building Import Formats
• Loading Data
• Building Validation Rules
• Setting Up Validation Entities
• Processing Batch Files

L E S S O N 6
Setting Up Mapping Tables 6

Objectives
• Map dimension members
• Build maps in the FDM Web client
• Describe map types
• Explain processing order
• Build maps externally
• Copy maps
• Share dimension maps
• Set up conditional mapping
Module 3 Building the Workflow Process
Lesson 6 Setting Up Mapping Tables
Mapping Dimension Members

Maps for Texas Maps for Nevada
location location
Mapping Dimension Members

You create maps in FDM to map source dimension members to their corresponding
target system dimension members. For each location, you define a set of maps for each
target system dimension. For example, the Texas maps define the dimension mapping
for a Financial Management target system application, and the Nevada maps define the
mapping for a Hyperion Enterprise target system application.
Map creation tasks in FDM Web client:
1. Activate the map dimensions
2. Assign dimension labels
3. Open the Maps window
4. Build maps
You can also build maps externally and import them to FDM.

Activating Map Dimensions
1. In the FDM Web client, select MetaData > Dimensions.

2. In the Enabled column, select the check box for the

dimension that you want to activate.
3. Click Update Grid.
Activating Map Dimensions

You must activate dimensions to enable mapping, importing, and loading data into the
dimensions. When loading data to Hyperion Enterprise, you typically enable only the
Account and Entity dimensions. When loading data to other target systems, you can
enable all FDM dimensions (Account, Entity, ICP, and Custom 1 through Custom 20).
The following dimension attributes are displayed in the Dimensions window:
Dimension FDM dimension name. You cannot change dimension names.
Alias Alternate name for the dimension that corresponds to the target
system dimension name. FDM displays the alias in the Maps,
Validate, and Export windows.

Calc Sequence Calculation order. The default order is the order in which the
dimensions are displayed. You can override the default dimension
calculation order with conditional mappings.
Enabled Dimension activation status. When you select the check box, you
activate the dimension.
Use As Lookup Custom lookup status. You select the check box to use the dimension

for a custom lookup table in scripting. If you select this attribute, then
you cannot activate the dimension.
NOTE
Later topics in this lesson contain information on conditional mappings.

Assigning Dimension Labels
1. In the FDM Web client, select MetaData > Dimension

Labels.

2. Double-click in the Label column for the selected dimension.
3. Enter a label, and click Update Grid.
Financial Management adapter
Assigning Dimension Labels

Default FDM dimension labels are displayed in the Maps and Import Format windows.
You can assign source and target labels to the dimensions to make the windows more
readable. For example, you can modify the default labels of the UserDefined1 and Target
UserDefined1 dimensions to Source Department and FM Department.
Dimension labels are specific to each adapter. For the example on the slide, you change
the labels for the Financial Management adapter. To change the dimension labels for
another adapter, change the POV to a location assigned to the adapter.
NOTE
You cannot modify the dimension name.

Opening Maps
In the FDM Web client, select Activities > Maps, and select a
dimension from the list.

Dimension
list
Opening Maps
You open the Maps window to create, import, display, and manage maps for locations.
You use the Dimension list to select a dimension to map. By default, the window displays
the Explicit map type, which displays three columns—source dimension, description, and
target dimension. For the Account dimension, the map contains an extra column that you
use to control sign conversion.
You use the following methods to set up maps for locations:
• Build maps externally and import them to FDM
• Copy maps to other locations
• Share maps with other locations

Building Maps
Select a dimension and map type.

Add a blank row. Save the changes. Browse for a target member.
Building Maps
You can build maps in FDM to map source dimension members to target dimension
members. You can map source dimension members only to valid input target dimension
members. When you browse for target members, FDM displays only input target
members.
To build maps:
1. In the POV, select the location for which you want to build a map.
2. Select Activities > Maps.
3. From the Dimension list, select a dimension.
4. From the Type list, select Explicit, Between, In, or Like.

5. Click Add.
A blank row is added to the mapping table.
6. Double-click in the columns to define the mapping.
7. In the target dimension column, place your cursor over the arrow, and select Browse
for Target Value to select a valid member from the target system.

The Target Key Lookup dialog box is displayed.
8. Select the corresponding target member, and click OK.

Map Types

Map types
Map Types
You can map dimension members with one-to-one mapping or rules-based mapping. In
FDM, one-to-one mapping is referred to as Explicit mapping, and rules-based mapping is
referred to as Between, In, or Like mapping.

Explicit Mapping
From the Type drop-down list, select Explicit.

One-to-one mapping
Explicit Mapping
You select explicit mapping when the translation is one to one, where you map each
source dimension member to one target dimension member. The example on the slide
maps source account 001100 to target account 10000005, and source account 223501
to target account 20500.

Rules-Based Mapping

Rules-Based Mapping
In rules-based maps, you use translation rules to map dimensions. Translation rules offer
more flexibility in mapping source members to target members. For example, you can
map a range of source accounts to one target account, or you can map several
nonsequential accounts to one target account. By mapping multiple source members in
one translation rule, you reduce the number of records in the map and the amount of
time required to maintain the map.
You must provide a rule name, rule definition, and target dimension member for each
record in a rules-based map. The rule description is optional. When mapping accounts,
you can change the sign of source accounts from positive to negative or from negative to
positive. You can also define a script for conditional mapping in the translation rule.
You define rules-based mappings with the Between, In, and Like map types.

The example on the slide defines a Between map. The map contains the rCash rule for
mapping cash accounts. The translation rule maps source accounts 1000 through 2000
to the target account 10000015.
FDM stamps all mapped source dimension records with the translation rule that was
used to provide the record with its target values. This process creates a static map for
each location, category, and period combination, ensuring a static audit trail.

FDM offers additional flexibility and power when it comes to account mapping. You can
group general ledger accounts into a calculated account, and map the calculated
account to a target account.

Between Mapping
From the Type drop-down list, select Between.

Between Mapping
The Between map type enables you to map a range of source dimension members to
one target dimension member. You define the range of source members in the Rule
Definition column by entering the beginning member and the ending member, separated
by a comma. The range includes the beginning and ending members.
Each side of the mapping range must be the same length. For example, the range
2000.00, 2991.99 is a valid mapping, while 2000.00, 2991 is not. The range 2000.00,
2991 fails to map accounts 2991.00 through 2991.99.
When each side of the mapping range is the same length, you must also ensure that the
accounts use the correct map. For example, you define two mappings—1530,1540 and
153000,154000. Due to the FDM processing order, when you import the source account
1540, FDM maps it by using the second mapping (1530000,1540000).

In Mapping
From the Type drop-down list, select In.

In Mapping
The In map type enables you to map a list of nonsequential source dimension members
to one target dimension member. When you map multiple source members in a single
translation rule, you eliminate the need to create multiple mappings in an Explicit map.
You define the list of source members in the Rule Definition column by entering the
members, separated by a comma. For the example on the slide, source accounts 1503,
1510, and 1515 map to the target account 15000010, and source accounts 2430, 2435,
and 2438 map to the target account 24000035.

Like Mapping
From the Type drop-down list, select Like.

Like Mapping
The Like map type enables you to map multiple source dimension members with the
wildcard characters asterisk (*) and question mark (?).
The asterisk wildcard acts as a placeholder for any number of characters. For example,
with the rule definition 1190*, you can map accounts 1190, 1190100, and 1190-200 to
one target account.
The question mark wildcard acts as a placeholder for one character. For example, with
the rule definition 1221?, you can map source accounts that begin with 1221 and contain
only five characters.

Wildcard Mapping

Wildcard Mapping
FDM can derive target dimension members if you specify wildcard characters in the
source and target dimensions of a map. This type of map entry is a wildcard map.
When you include wildcard characters in the target dimension of a map, FDM looks at
the source dimension members, and replaces the wildcard characters in the target
dimension members with characters from the source member.
For example, you want to map source accounts 001120, 001125, and 001130 to
corresponding Cash target accounts. You set up the rule definition as 0011?? and the
target account as Cash.??. FDM uses the characters represented by the two question
marks in the source accounts to replace the two question marks in the target accounts,
as shown in the following table:

Source account Resulting target account

001120 Cash.20
001125 Cash.25
001130 Cash.30

NOTE
FDM ensures that the target accounts are valid accounts in the target system.

Processing Order

Locations
window
Maps
window
Processing Order
By default, FDM sorts and processes rule-based maps alphabetically by the rule name.
You can override the default order and sort the mapping rules by a sequence number.
First, you must enable the sequence map for the location, which adds a Sequence
column in the Maps window. Next, you enter a numeric value to designate the sequence
order of the mapping rules.
NOTE
Once you enable map sequencing, you cannot disable it without first clearing the
sequence numbers from the map table.
To map dimensions correctly, you must understand the FDM map-processing order. The
order is important if the same source dimension member falls within multiple maps (that
is, Explicit, Between, In, Like) or within the same mapping type multiple times.

Processing Order in Multiple Mapping Types

If the same source dimension member falls within multiple mapping types, FDM
processes the member in the following order: Explicit, Between, In, and Like. In other
words, Explicit maps override every other mapping type; Between maps override In and
Like maps; and In maps override Like maps.
Processing Order in the Same Mapping Type

When a source dimension member falls within the same mapping type multiple times,
FDM processes the member in the following order:
Map Type Processing Order

Between If the source member is picked up by multiple Between mappings, then
the source member is assigned to the last Between map in the mapping
table.
In If the source member is picked up by multiple In mappings, then the
source member is assigned to the first In map in the mapping table.
Like If the source member is picked up by multiple Like mappings, then the
source member is assigned to the first Like map in the mapping table.


Building Maps Externally
You can build the following conversion tables outside FDM and import them to locations
in FDM.
• MapLoader.xls files in Excel
• Hyperion LedgerLink account and name conversion tables
• Hyperion Enterprise conversion tables

Building Maps with MapLoader Files

Map tab
Building Maps with MapLoader Files

You can build maps with MapLoader files in Excel and import them into FDM. You
typically use Excel to build conversion tables when no prior maps exist.
The application’s Outbox/Templates directory contains an Excel map template,
MapLoader.xls, that you use to build maps for any valid dimension. You need a separate
MapLoader file for each dimension that you want to map.
TIP
Refer to the Instructions tab of the MapLoader template for instructions and
syntax examples.

You build the map on the Map tab of the template by adding the location name and ID,
selecting the dimension to map, and entering the source and target dimension members.
The location ID must match the location ID assigned by FDM to the selected location.
You can specify one-to-one mapping and rule-based mapping (Between and Like), but
not the In mapping type.
NOTE
Do not add rows on the Map tab of the MapLoader template, because the rows

contain hidden formulas that are used by FDM.
You can copy input-level target members and their descriptions to the DimensionLists tab
of the template. You can then access the target members on the Map tab by right-clicking
in the target member cells.
After building the MapLoader files for each dimension, you load the mapping files into
FDM.

Importing Maps
Method 1

Method 2
Importing Maps
You can import the MapLoader mapping files into FDM by selecting the file from the
application’s Inbox directory or subdirectory, or by browsing for the mapping file in
another location.
To import MapLoader files into FDM:

1. In the FDM Web client, select Activities > Maps.
• From the Upload File tab, browse to select the mapping file, and click Import.
• From the Select File From Inbox tab, click Select File, select the mapping file from
the appropriate Inbox directory or subdirectory, and click OK.
The mapping file loads into FDM for the location indicated in the
mapping file.

Building Maps with Hyperion LedgerLink Files
Source
member or Target

members member Description
00113401, 1000.01, Cash Account 1

00113402, 1000.02, Cash Account 2
0022>0055,1000.50, Petty Cash
0130045*, 1250, Accounts Receivable
Account conversion table (TRA)
One-to-one mapping 200; OHIO.INP

320>350; TEXAS.INP Range mapping
Wildcard mapping 400*; UK.INP
Name conversion table (TRN)
Building Maps with Hyperion LedgerLink Files

You can import Hyperion LedgerLink account conversion tables (TRA files) and name
conversion tables (TRN files) into FDM. If you include a range of members in the
conversion table, FDM properly interprets these records as wildcards and generates the
appropriate mapping table entries in FDM.
Hyperion LedgerLink conversion tables include the source members, target members,
and (optional) member descriptions, separated by delimiters (pipe, semicolon, comma,
or exclamation point). If you include member descriptions, you must place them at the
end of each entry.
NOTE
Hyperion LedgerLink files do not include a location ID or dimension. You import
these files to the selected Maps dimension and to the currently selected location
POV.

To import LedgerLink Files into FDM:

1. In the FDM Web client, select the POV location to which you want to load the files.
3. From the Dimension list, select the dimension to which you want to load the map.

• From the Upload File tab, browse to select the LedgerLink file, and click Import.
• From the Select File From Inbox tab, click Select File, select the LedgerLink file from
the appropriate Inbox directory or subdirectory, and click OK.
The LedgerLink conversion table loads into FDM for the selected
dimension and location.

Building Maps with Hyperion Enterprise Files
ENGLAND ! UK.INP
TEXAS ! TX.INP

OHIO ! OH.INP
Name conversion table (ASC)
Source Target Switch

member member sign
10001 ! 100.01 ! ADD

10002 ! 100.02 ! ADD
10003 ! 100.03 ! ADD
54300 ! 25077 ! SUB
Account conversion table (ASC)
Building Maps with Hyperion Enterprise Files

You can import Hyperion Enterprise account and name conversion tables (ASC files) into
FDM. The conversion tables include the source members and target members,
separated by delimiters (pipe, semicolon, comma, or exclamation point).
NOTE
Hyperion Enterprise conversion tables do not include a location ID or dimension.
You import these files to the selected Maps dimension and to the currently
selected location POV.

In account conversion tables, the word add, false, or no designates that the account’s
sign is not changed when it is loaded to the target system. The word sub, subtract, true,
or yes designates that the account’s sign is changed from positive to negative or
negative to positive. FDM indicates a sign change with a check mark in the Minus
column of the Account dimension map.
To import Hyperion Enterprise Files into FDM:

1. In the FDM Web client, select the POV location to which you want to load the files.
3. From the Dimension list, select the dimension to which you want to load the map.
• From the Upload File tab, browse to select the Hyperion Enterprise file, and click
Import.
• From the Select File From Inbox tab, click Select File, select the Hyperion
Enterprise file from the appropriate Inbox directory or subdirectory, and click OK.
The Hyperion Enterprise conversion table loads into FDM for the
selected dimension and location.

Copying Maps

Location POV
Copying Maps
You can copy maps for selected dimensions from one location to another. For the
example on the slide, you copy the FM Account map for the current Texas location to the
Michigan location.
To copy maps from one location to another:

1. In the FDM Web client, set the POV to the location that you want copied.
3. Click Copy.
The Select Target Location dialog box is displayed.
4. Select a target location, and click OK.
FDM copies the map for the active dimension from the current
location to the target location.

Sharing Dimension Maps

2. In the Controls tree, select the location.

3. From Parent Location, select the parent location whose
maps you want to share with Nevada.
4. Click Save.
Sharing Dimension Maps

You can build dimension maps for one location and share the maps with multiple
locations. When you assign a parent map to locations, the locations use the same
dimension maps as the parent location. Sharing maps among locations is useful when
multiple locations use the same chart of accounts. If you make a change to the child or
parent map, the change affects all children and parent locations.
For the example on the slide, you assign the Texas parent location to the Nevada
location. The two locations now share the same dimension maps.

Setting Up Conditional Mapping

If varValues(14) = “InterCoAP”
Then Result = “Michigan”
Else Result = “[ICP None]”
End If
Setting Up Conditional Mapping

Conditional mapping enables you to map source dimension members to a script
expression rather than to a hard-coded target system dimension member. When you use
conditional mapping in conjunction with dimension processing order, you can base the
mapping of the current dimension on previously mapped dimensions. That is, you can
map different values for an ICP or Custom member based on account and entity
mappings.
Conditional mapping is valid only for rule-based mapping (Between, In, and Like). You
activate conditional mapping by placing the value #Script in the Target member column
of the map. This value triggers FDM to execute the conditional mapping script in the
Script column.
You write conditional mapping script in VBScript. The logic provides all the functionality
included in the VBScript language, as well as access to the running instance of the
application programming interface (API).

VarValues Variables
You typically include the varValues variable in conditional mapping scripts. VarValues is a
variant array that contains the mapped values for previously mapped dimensions, while
the mapped values for all other dimensions are null. In the script, you can use varValues
to test the value of an account or entity, and map the current dimension member based
on the account and entity values.
The following table shows common variables for conditional script expressions:

Variable Record Value Mapped
varValues(1) Current location ID number
varValues(2) Current category ID number
varValues(3) Current period key value
varValues(5) Current data view
varValues(9) Amount for current record
varValues(11) Account description for current record
varValues(13) Source account
varValues(14) Target account
varValues(15) Source entity
varValues(16) Target entity
varValues(17) Source ICP
varValues(18) Target ICP
varValues(19) Source UD1
varValues(20) Target UD1
For a complete list of variables, values mapped, and value type, see Oracle Hyperion
Financial Data Quality Management, Fusion Edition Release 11.1.1 Administrator’s
Guide.
Conditional Mapping Script Example

If you map the Account and Entity dimensions before the ICP dimension, the varValues
array contains the mapped values for accounts and entities when FDM processes the
map for the ICP dimension.

For the script example in the slide, you check the mapped value of the target account,
varValues(14), to determine the mapping for the ICP dimension member. If the target
account is equal to InterCoAP, then the ICP member maps to Michigan; otherwise, it
maps to [ICP None].

Conditional Mapping Performance Considerations
To optimize memory utilization and process rules faster:

• Restrict conditional range mappings.

• Restrict the list of In mappings.
• Restrict Like mapping criteria.
Conditional Mapping Performance Considerations

The conditional mapping process requires FDM to return a set of records containing all
dimension fields back to the application server. This action causes high memory
utilization and a time-consuming transfer of a great deal of data.
Usage guidelines for conditional rule types:
Conditional Rule Type Usage

Range map Restrict conditional ranges. Rather than using one large range
(0000 to 9999), break up the range into multiple smaller ranges
(0000 to 1000 and 1001 to 2000).

Conditional Rule Type Usage

In map Restrict the In list. Rather than using one large list that returns a
large volume of records, break up the list into smaller lists.
Like map Restrict Like criteria. Never use an asterisk (*) wildcard without
any other criteria in the rule definition because the * wildcard
returns a very large volume of records to the application server for
processing. Limit each query to a small number of members to
map, such as 1*, 2*, or A*.

By restricting the number of records that FDM processes in a conditional mapping rule,
you keep memory utilization optimal and enable FDM to process the rules faster.

Summary

• Map dimension members
• Describe map types
• Explain processing order
• Build maps externally
• Copy maps
• Share dimension maps
• Set up conditional mapping

6-36

L E S S O N 7
Building Import Formats 7

Objectives
• Create import groups
• Build import formats
• Assign import formats to locations
• Add import expressions
Lesson 7 Building Import Formats
About Import Formats
Import formats define the data file layout.

1. The accounts start at character 1 1. The fields are separated
and are up to 11 characters long. by commas.
2. The descriptions start at character 2. The entities are in the
14 and are up to 24 characters first field.
long. 3. The accounts are in the
3. The amounts (Ending Balance) second field.
start at character 40 and are up to 4. The amounts are in the
19 characters long. third field.
About Import Formats

You create import formats to define the layout of data files so that you can load them into
FDM. You must assign an import format to each data-load location.
After you create the import format, the data file layout must remain the same when you
load data. If the layout of the data file for a location changes, you must update the import
format for that location.
Import format tasks:
1. Create import groups
2. Build the import format for each group
3. Assign the import formats to data-load locations

Creating Import Groups
Add an import group.

Types of
import groups.
Creating Import Groups

You create import groups to hold import formats for data-load locations. You define the
import group names and attributes; for example, whether the import group defines the
format for fixed or delimited data files. The Import Formats window includes two tables.
The top table displays the list of import groups, and the bottom table displays the fields
for the selected import group.
When you select a fixed import group, the bottom table displays columns for the field
names, the starting position of the fields, and their length. In a delimited import group, the
bottom table displays columns for the field names, their field number, and the total
number of fields in the data file. Both types of import groups also display a column for
expressions that further define how FDM interprets each data record.

Rather than importing data files into FDM, you can also build an integration script or use
an integration adapter to import the ledger data directly from an ODBC-compliant data
source. For these options, you select the Adapter and Script import group file types. For
more information about the Script import format type, see Oracle Hyperion Financial
Data Quality Management, Fusion Edition Release 11.1.1 Administrator’s Guide.
To create import groups:

1. In the FDM Web client, select MetaData > Import Formats.
The Import Formats window displays an import group table at the
top of the window and a table for field names at the bottom of the
window.
2. In the table at the top of the window, click Add.
A row is added to the import group table.
3. In the Import Group column, enter the import group name.
4. In the Description column, enter a description for the import group.
5. In the File Type column, select Adapter, Delimited, Fixed, or Script.
6. In the Delimiter column, perform one of the following actions:
• For Delimited import groups, select the appropriate data file delimiter.
• For the Fixed, Adapter, or Script import group, select the NA delimiter.

Building Import Formats
Fixed import format

Field names Field attributes
Building Import Formats

In fixed and delimited import formats, each row in the bottom table of the Import Formats
window represents a field in the file. Each field represents a possible data-load
dimension. You must add a row for each field in the file that you want to import into FDM.
You can assign multiple data file fields to the same FDM field name. FDM automatically
concatenates these string values during the file-load process.
When you import a data file, FDM automatically skips every record that does not contain
a valid amount.

To create fixed or delimited import formats:

2. From the top table of the Import Formats window, select a fixed or delimited import
group.
The table for the fields of the selected import group is displayed at
the bottom of the window.

3. In the bottom table, click Add.
A row is added to the bottom table with Amount in the Field Name
column.
4. Double-click in the Field Name column and, from the list, select a field name to
import from the data file into FDM.
5. Enter the field attributes.
7. Repeat steps 3 through 6 for each field that you want to import from the data file.

Building Fixed Import Formats
In Import Format Builder,

select the data file.

Drag the highlighted text.
Building Fixed Import Formats

Fixed import formats define the format for data files that contain fixed fields. Each field in
the file has a starting position and a length. You can define four attributes for each field,
as described in the following table:
Field Name Name of FDM source field
Start Starting position of the field
Length Length of the field
Expression (optional) Value or script that further defines or interprets the field
You can enter the starting position and length directly on the form, or you can use Import
Format Builder to drag the values to the appropriate columns.

You open the data file in Import Format Builder to display the layout of the fields. You can
then select the text that you want to import for each field, and use the drag feature to
automatically populate the start and length attributes in the import format.
For the example on the slide, you drag the Description field to the “Drag and drop text
here” button to define its starting position and length. You also define the entity name,
Center, in the Expression column to define Center as the entity for each record in the
data file. The entity is a required field, even though it is not in this data file.

To create import formats with Import Format Builder:
2. From the top table in the Import Formats window, select an import group.
The table for the fields of the selected import group is displayed at
A row is added to the bottom table with Amount in the Field Name
column.
4. Double-click in the Field Name column and, from the list, select a field name.
5. Click Build.
The Import Format Builder window is displayed.
6. Click Select File.
The File Browser dialog box displays the application directory
structure. You can upload a data file if it does not exist in the
application directory structure.
7. Perform the following actions:
a. If the data file does not exist in the application directory structure, click Browse,
locate the file, click Open, and click Upload. Otherwise, proceed to step 7b.
The file is copied to the selected directory in the application
directory structure.
b. Select the application directory that contains the data file, select the data file, and
click OK.
The file is displayed in the Import Format Builder window.

8. Highlight the text that represents the field to import, such as the account number,
description, or amount.
9. Drag the highlighted text to the target .
For a fixed import format, the Start and Length columns are
automatically populated in the bottom table of the Import Formats
window. For a delimited import format, the Field Number and
Number of Fields columns are automatically populated.

10. Continue to add fields to the import format, and set their attributes with Import Format
Builder.
11. Click Close to close Import Format Builder.
12. Optional: In the Expression column of a field, define an expression.
13. In the bottom table of the Import Formats window, click Update Grid to save the
changes.

Building Delimited Import Formats

Drag the
highlighted
text.
Building Delimited Import Formats

Delimited import formats define the format for data files that contain fields delimited by
characters, such as commas or semicolons. You can define four attributes for each field,
as described in the following table:
Field Name Name of FDM source field
Field Number Position of the field in the data file
Number of Fields Total number of fields in the data file
Expression (optional) Value or script that further defines or interprets the field
You can enter the field name and number directly on the form, or you can use Import
Format Builder to drag the values to the appropriate columns.

For the example on the slide, the field delimiter is a comma. You drag the Description
field to the “Drag and drop text here” button to define it as the second of three fields in
the data file.

Building Import Formats for EBS
Adapter import group.

Delimited import group.
Import format specifies

source adapter name.
Import format specifies

layout of the generated
data file from EBS.
Building Import Formats for EBS

You can use the source adapter for Oracle EBS Financials to import data directly from
EBS to FDM.
Process for setting up the import formats to pull data from EBS:
1. Import the source adapter for Oracle EBS Financials into FDM, and define the
adapter options required for pulling data from EBS and for drilling back to EBS.
2. Create an import format group that specifies the name of the Oracle EBS Financials
source adapter.
3. Generate the data file from EBS.

4. Create a delimited import format group for the data file that was generated from EBS.
If you want to enable drillback to EBS, ensure that the required fields
(Set_of_Books_ID, Period_Name, Code_Combination_ID, and Currency_Code) are
defined in the import format. If you do not need these four fields for loading data to
the target system, then define them as attributes in the import format.
NOTE
For the complete list of 43 fields that are pulled from EBS, see the Oracle

Hyperion Financial Data Quality Management Source Adapter for Oracle
E-Business Suite Financials readme file.
5. Assign import formats to locations:

- Assign the adapter import format in the Import Format field of the Locations >
Workflow Behaviors tab.
- Assign the delimited import format in the Option 1 field of the Locations >
Integration Options tab.

Skipping Lines in Import Files

Specify the
starting position
and text length.
Enter the
Select the Skip text value.
field name.
Skipping Lines in Import Files

With the Skip expression, you can skip lines that you do not want to import into FDM
from the data file. Usually, these lines are report headers, totals, and subtotals that can
lead to inaccurate data in target systems.
For the example on the slide, the data file includes a description and subtotal for each
group of accounts. Each subtotal line has no characters in columns 1 through 11, and it
has a semicolon at the end of the subtotal description. You can use either of these values
in the Expression column of the Skip field name to select the source lines to skip. In this
example, you skip lines with a colon in position 43.

Concatenating Fields

Account in
data file
Imported account = 6210-60
Concatenate fields in import format
Concatenating Fields
You can join multiple fields from data files to form a string of characters. You can
concatenate all field names (for example, accounts, entities, and descriptions), except
for amounts. The Amount field name must be only one row in an import format.
The concatenation order is based on the order of the lines in the import format. For the
example on the slide, you concatenate the three Source Account fields in the order in
which they appear in the import format. You take the four characters starting at position 7
of the data file, add a hyphen, and add the two characters starting in position 4. FDM
concatenates the source account 10-60-6210 to 6210-60.

Assigning Import Formats

2. From the Controls tree, select a data load location.

3. Select the Workflow Behaviors tab.
4. From Import Format, select an import format, and click Save.
Available import formats
Assigning Import Formats

After you assign import formats to locations, FDM automatically uses the import formats
when you import data files to the data-load locations. You can assign the same import
format to multiple locations. If your company has a standard data file format, then all
locations can share the same import format.

Adding Import Expressions

Add an expression in
the Add Expression
dialog box.
Adding Import Expressions

FDM includes a set of powerful import expressions that make it possible to read and
parse virtually any data file into the FDM database. Import expressions and scripts work
on the value that FDM reads from the data file for the field to which you assigned the
expression.
When you import a data file, FDM automatically skips every record that does not contain
a valid amount, although FDM still executes scripts in the amount field.
With import expressions, you can perform tasks such as hard-coding field values,
skipping source data lines, concatenating fields, factoring amounts, and parsing numeric
columns.

To add import expressions:

2. In the top table, select an import group.
3. For a field in the bottom table, double-click in the Expression column.

• Enter the expression directly in the column, and then skip to step 6.
• Add an expression: Proceed to step 5.
5. Place your cursor over the arrow in the column, select Add Expression to display the
Add Expression dialog box, and then perform the following actions:
a. From the Expression Type drop-down list, select the type of expression, such as
Fill, Sign, or Factor. The expression types vary depending on the selected field
(that is, account, entity, amount, and so on). For the example in the slide, the
Expression Type is DRCRSplit.
b. In the Expression Value box, enter the value for the expression, and click OK.
The expression is displayed in the Expression column for the
selected field.
6. In the bottom table of the Import Formats window, click Update Grid to save the
changes.

Sign Expressions

Source data value = 10,000.00CR
Imported data value = -10,000.00
Sign Expressions
FDM interprets leading and trailing minus signs, as well as parentheses, as negative
numbers. However, some data files trail numbers with other characters (such as CR and
DR) to indicate negative or positive amounts. You use Sign expressions in Amount fields
to interpret nonstandard numeric sign conventions.
For the example on the slide, you add the expression Sign = ,CR to the Amount field.
This expression defines all amounts with a trailing CR as a credit balance and assigns a
negative sign to the imported numbers. Positive numbers in this data file are unsigned
and require no conversion.
If positive numbers in the data file are followed by DR (1,000.00DR) and negative
numbers are followed by CR (1,000.00CR), you define the Sign expression as
Sign=DR,CR. This expression causes FDM to interpret numbers followed by DR as
positive numbers, and those followed by CR as negative numbers.

DRCRSplit Expressions

Source data Imported data
DRCRSplit Expressions
By default, FDM assumes that numeric values in amount fields are debits. However,
many data files position debit values in the first half of the field, and credit values in the
second half. With the DRCRSplit expression, FDM can interpret this positioning and
assign the correct sign to amounts.
Syntax
DRCRSplit = [Midpoint of the DR and CR columns]
FDM assigns a negative sign to amounts to the right of the midpoint of the DRCRSplit
field.

For the example on the slide, the Amount field starts in position 46 of the data file and is
31 characters long. Debit amounts are in the first half of the field, and credit amounts are
in the second half. The midpoint of the Amount field is 16, and you define the expression
as DRCRSplit=16. When you import the file, FDM interprets amounts to the left of the
midpoint as debits and those to the right of the midpoint as credits. After you import the
data file, all credit amounts are displayed with a negative sign.

Fill and Fill=EuroToUS Expressions

Use Fill to Use
add trailing Fill=EuroToUS
characters. to format data.
Fill and Fill=EuroToUS Expressions

You use Fill expressions to pad a field with trailing characters to ensure that all imported
members of the field are the same length. For the data file on the slide, some of the
accounts are 7 characters long and others are 10 characters. Using a Fill expression,
FDM evaluates the source field text value; if it is shorter than the fill expression, the text
value is padded with the Fill characters.
Some data files contain European formatted amounts with the period as the thousands
separator and the comma as the decimal separator. You add the Fill=EuroToUS
expression to amount fields to convert the amounts to a U.S. format, with the comma as
the thousands separator and the period as the decimal point.
NOTE
You define the default thousands and decimal separators in the Decimal
Replacement option of the FDM configuration settings.

Fill and Fill=EuroToUS Expressions: Example
Import format

Imported results
Fill and Fill=EuroToUS Expressions: Example

For the example on the slide, accounts shorter than 10 characters are padded with
trailing zeros during the file import. FDM converts account 103950- from the data file to
account 103950-000.
During the file import, FDM converts the European number formats to the U.S. formats.
The amounts are displayed with a comma for the thousands separator and a period for
the decimal separator.

FillL Expressions

Accounts in Accounts
data file after import
FillL Expressions
You use FillL expressions to pad a field with leading characters to ensure that all
imported members of the field are the same length. For the data file shown on the slide,
some of the accounts are 4 characters long and others are 7 characters long. Using a
FillL expression, FDM evaluates the source field text value; if it is shorter than the FillL
expression, the text value is padded with leading characters.
For the example on the slide, FDM imports account 1100 from the data file and converts
it to account 0001100.

Factor Expressions

Source data
Imported data
Factor Expressions
You use Factor expressions to multiply amounts read from data files by user-defined
values. To define a factor, the expression follows the format Factor=[user-defined value].
The example on the slide defines a factor of 1000 for the Amount field. FDM reads the
data file amounts and multiplies them by 1000 during the data-load process. FDM
imports source amount 56,701 as 56,701,000.
You can also use Factor expressions to multiply source amounts by decimals. If you
define a factor of .001, FDM imports the source amount 56,701as 56.701.

NZP Expressions

Source data
Imported data
NZP Expressions
By default, FDM bypasses accounts in data files that have zero balances. You may want
to load all accounts to ensure that values that should be zero are replaced in the target
system. You use NZP expressions in Amount fields to disable zero suppression during
the data-load process.
For the example on the slide, FDM imports the accounts with zero balances. The Tooling
& Prototype Rec and the Interest Receivable accounts are displayed in the imported data
list with their zero balance.

Expression Stacking and Processing Order
Processing order for the Amount field in this import format: .

1. Fill=EuroToUS expression

2. NZP expression
Separate stacked
expressions with a
semicolon.
Expression Stacking and Processing Order

You can define multiple (stacked) import expressions for a field. When stacking
expressions, take into consideration their processing order, as follows:
Amount Field All Other Fields

1. DRCRSplit 1. Script
2. Fill=EuroToUS 2. Excel
3. Script 3. Fill or FillL
4. Excel
5. Sign
6. Factor
7. Scale
8. NZP

Summary

• Create import groups
• Build import formats
• Assign import formats to locations
• Add import expressions

L E S S O N 8
Loading Data 8

Objectives
• Import source data
• Sort, find, filter, and delete records
• Validate dimension mappings
• Drill up and down on values
• Drill back to FDM from target applications
Lesson 8 Loading Data
About Loading Data

Source data Target systems

Oracle E-Business
Suite, OLE DB, Export Essbase
and ODBC data to
target
Import
systems. Hyperion
source
data. Enterprise
FDM
Financial
Flat files Validate Management
dimension
mappings.
OLAP
Applications
Excel files Oracle, SQL Server,

and DB2 Databases
About Loading Data

FDM end users repeat the following tasks every month to load general ledger source
data into target systems:
1. Import source data into FDM
2. Validate the mappings of source dimension members to target dimension members
3. Export mapped data to target systems

Selecting Data Files
In the FDM Web client, select Workflow > Import.

Method 1:
Upload
File tab
Method 2:
Select File
From Inbox
tab
Selecting Data Files

After creating import formats and assigning them to data load locations, you can import
the source data into FDM.
There are two ways to select the data file to load. You can select the file from the
application’s Inbox directory or subdirectory, or you can browse for the file in another
location.
Import types:
• Replace (default)—Deletes existing data for the selected location, period, and
category prior to loading another data file.
• Append—Appends the lines in the data file to the existing data for the selected
location, period, and category. This method does not merge the data, because new
lines do not affect existing lines.

Successful import

Imported records for current POV

You import source data into the location, category, and period that you select in the POV.
FDM uses the import format that you assigned to the selected location to interpret the
layout of the data file and import the data into FDM.
After a successful import, FDM displays the data records at the bottom of the Import
window and displays a success icon below Import at the top of the window.
To import source data into FDM:

1. In the FDM Web client, select Workflow > Import.
2. In the POV, select the location, period, and category for the data load.
• From the Upload File tab, browse to select the data file, and then click Import.

• From the Select File From Inbox tab, click Select File, select the data file from the
appropriate Inbox directory or subdirectory, and click OK.
FDM displays the imported records at the bottom of the Import
window.

Working with Records
Sorting records by

the Source Account
column
Descending sort
Working with Records

You can perform the following tasks on records:
• Sort records by any column
• Find records
• Filter records to display a subset of records
• Delete records
Sorting Records
You can sort records in ascending or descending order by any column.
For the example on the slide, you activate the Source Account column and sort the
records in descending order.

To sort records:
1. In the FDM Web client, select the Import, Validate, Export, or Maps window.
2. Click in a column heading to activate the column for sorting.
A sort button ( ) is displayed to the left of the column heading.
3. Click the sort button to toggle the sort between ascending ( ) and descending ( )
order.

Finding Records
1. Select the column to search, and click Find .

2. Enter the search criteria, and click OK.

Find Find Next
Finding Records
You can search for records in the Import, Validate, Export, and Maps windows. For the
example on the slide, you activate the Account Description column and search for
records whose description begins with OTH. FDM highlights the first record that matches
the search criteria. You can click the Find Next button to move to the next record.

Filtering Records
1. Select the column to filter, and click Filter .

2. Select the filter method.

3. Enter the filter value, and click OK.
Click the Filter button

to turn off the filter.
Filtering Records
You can filter records to display only a subset of the records. You can filter records in the
Import, Validate, Export, and Maps windows. For the example on the slide, you activate
the Account Description column and display only the records whose description begins
with OTH. When you filter records, FDM displays the filter button with a green
background.
You can use the following filtering methods: Like, In, Between, =, <>, and All.

Deleting Records
1. Click Delete All.

2. At the confirmation prompt, click OK.

Deleting Records
You can delete all records in the Import and Maps windows to clear the list of records
before processing another import. Only users with administrator rights can perform this
function.

Successful validation

Records with mapped dimension members

After creating mapping tables for locations and import the source data into FDM, you
must validate all dimension mappings before you can export the data to target systems.
During the Validate task, FDM compares the imported data records to the dimension
mappings and checks for any source dimension members that you did not map. If all
members are mapped, the validation check is successful, and a success icon is
displayed under Validate at the top of the window. FDM displays the records with the
mapped members at the bottom of the Validate window.
If the imported data records contain unmapped dimension members, the validation check
fails, and FDM displays a list of the unmapped members. The data load process cannot
continue until you map all unmapped members to valid target members.

To validate dimension mappings in the FDM Web client:

1. In the POV, select the location whose imported data records you want to validate.
2. Select Workflow > Import to verify that imported records exist in the selected location.
3. Select Workflow > Validate to display the Validate window.
4. At the top of the Validate window, click Validate.

The Validate window displays unmapped dimension members in
one table and mapped members in another table.

Validation Errors
Validation error

Unmapped dimension members
Validation Errors
Validation errors typically occur when you add accounts to the general ledger. New
general ledger accounts that you extract to data files are likely to be unmapped in FDM.
If you do not add mappings for the new accounts, the validation check fails. FDM
displays the unmapped members in a table above the mapped members.

Fixing Validation Errors
Unmapped

account
Accounts mapping table Target accounts
Fixing Validation Errors

The data load process cannot continue until you map all unmapped dimension members
to valid target system members. After mapping all unmapped members, run the
validation check again to confirm the new mappings.
To fix validation errors:

1. In the Validate window, select the row that you want to map.
2. Click Fix.
The Maps dialog box is displayed for the selected dimension. The
selected row is added to the bottom of the mapping table.

3. Double-click in the target member column for the unmapped row, point to the arrow,
and select Browse for Target Value.
The Target Key Lookup dialog box displays dimension members
from the target system.
4. Select the corresponding target member for the mapping, and click OK to return to
the Maps dialog box.

5. Click Update Grid to save the changes
6. Click Close to close the Maps dialog box.

Intersection Validation Reports

Invalid member in
target system
Intersection Validation Reports

During the validation process, FDM verifies that the dimension mappings in FDM are
valid base member intersections in the target system application. If any invalid
intersections exist, FDM displays the members and their status on the Intersection
Validation report.
For the example on the slide, an invalid FM Department member, Marketig, is displayed.
In this case, the member name is misspelled. You must correct the mapping for this
member and run the validation check again to confirm the new mapping. You should also
correct the source mapping file (MapLoader.xls files, LedgerLink or Enterprise
conversion table files) if the invalid member exists in the data file.
NOTE
Intersection Validation reports run only for Financial Management integrations.



After validating the dimension mappings for the source data, you can export the data to
the target system. During the Export task, FDM first creates the load file for the target
system in the FDM application’s Outbox directory. FDM creates the load file in the format
required by the target system.
FDM then prompts you for the load method and load operation in the Target System
Load dialog box. The options displayed in the dialog box are specific to each adapter.
Refer to the target system documentation for information about the export options.

For example, there are four load methods for Financial Management, as described in the
following table:
Load Method Description

0-Replace Clears all account values from the target application, and replaces
the data in the application with the data in the load file.
1-Merge Overwrites the data in the target application with the data in the load

file. If the load file includes multiple values for the same point of view,
the value for the last entry loads; data that is not changed by the
data load file remains in the target application.
2-Accumulate Accumulates the data in the target application with the data in the
load file.
3-Replace by Security Loads data to the target application only for members to which you
have access.
For Essbase, only the Replace and Merge load methods apply. You can also specify
which Essbase load rule to execute during data loads by setting the Load Rule Name
option in Integration Settings.
To load data to target systems:

1. In the POV, select the location, period, and category whose data you want to load to
a target system.
2. Select Workflow > Export, and verify that the Import and Validate tasks were executed
successfully.
3. At the top of the Export window, click Export.
An information bar message displays “Export file was created
successfully,” and the Target System Load dialog box is
displayed.
4. From the Load Method list, select the load method for the target system.
5. From the Load Operation list, select 0 - Load or 1 - Scan.
6. Select the adapter-specific options.
7. Click OK.
FDM loads the data to the target system and displays a success
icon below Export at the top of the Export window.

Drilling Up on Values
1. In the FDM Web client POV, select the

current location, period, and category.

2. Select Workflow > Import.
3. In the Amount column, click a value.
4. From the menu, select a command.
Menu for drilling up
Drilling Up on Values
The Import form offers drill-up analysis. In the Import window, you can access amount
information by using the drill-up menu shown on the slide.

Displaying Attributes

Attributes Drill Up form
Displaying Attributes
In addition to custom dimensions UD1 through UD20, FDM also features 14 custom
Attribute dimensions. You cannot map these dimensions, but you can use them for
custom data warehousing tasks. You enable the Attribute dimensions in Workbench.
Each line in the Import window can include attributes that you loaded during the Import
process. To view data loaded to the Attribute dimensions, you must open the Attributes
Drill Up form.

Displaying Conversion Rules

Displaying Conversion Rules

You can display the dimension mapping for each line in the Import form. When you select
Show Conversion Rules for an amount, the Drill Up form displays the conversion rule for
each dimension. For the example on the slide, the conversion rules for the Account,
Entity, and ICP dimensions are displayed.
From the Drill Up form, you can select a dimension alias to display the original map entry
for that dimension. The example on the slide shows the FM Account map with the
conversion rule for accounts that begin with 1190.

Displaying Archive Information

Displaying Archive Information

FDM archives all imported data files, import logs, journal entries, multiload files, target
system load files, and attached memo documents. FDM assigns a unique name and ID
to the files and stores them in the FDM application’s Data directory. You can retrieve the
files’ archive information from the Import window for a complete audit trail.

Displaying Source Documents

Imported source data file
Displaying Source Documents

You can display the source data file for records in the Import form. When you select
Open Source Document for an amount, the Archive Source Document form displays the
original source document, such as the general ledger file, journal entry, or multiload
template. For data that was pulled from Oracle E-Business Suite, the file that is created
by FDM upon import is displayed.

Displaying Source Systems

Oracle EBS 11i GL
Displaying Source Systems

In the Import form, you can display the source system for data that was pulled from
Oracle EBS Financials. When you select Open Source System, the Oracle EBS
Financials source system opens a new session, and the Account Balances window is
displayed. From there, you can drill down for more detail.

Displaying Processing Logs

Skipped
records
Displaying Processing Logs

FDM keeps a log of every line that it skipped while loading a data file. The codes for each
line in the processing log describe why the lines were skipped. You can display the
processing log from the Import form. For the example on the slide, FDM skipped some
lines because they are blank and other lines because they contain 0 balances.
Restoring Source Documents

With this option, you remove the original source document and its import log from the
archive, and you restore the files to the FDM application’s Inbox/ArchiveRestore
directory.

Drilling Down on Values
1. In the FDM Web client POV, select the current location,

period, and category.

2. In the Validate or Export window, click an amount.
Drilling Down on Values

The Validate and Export windows offer drill-down analysis. The Drill Down form displays
a list of the source accounts that sum to the amount that you load to the target system.
For the example on the slide, accounts 1190, 1190-101, and 1190-102 comprise the
balance for the target account, 10000020.

Drilling Up on a Drilldown
Drill Down window

Drill-up menu options
Drilling Up on a Drilldown
You can click amounts in the Drill Down form to display and select analysis options from
the drill-up menu.

Drilling Back to FDM from Target Applications
Data input cells in

target application.

Drill back to FDM.
Drill down in FDM

to the detail data.
Drilling Back to FDM from Target Applications

After exporting data to target applications, you can drill back from the target applications
to FDM to view the source data.
In Financial Management and Planning target applications, you create a data grid or form
that includes data input cells that were loaded by FDM. For Essbase applications that
you create with Essbase Studio, you drill back to the source data through Smart View. In
Strategic Finance, you navigate to the entity window that includes amounts loaded by
FDM.
When you right-click the data input cells of the target application and drill back to FDM,
the Drillback from Target System window is displayed. The top pane of the drill-back
window lists all sources that were loaded to that data cell in the target application. The
Summary pane at the bottom of the window provides information about the item selected
in the top pane. From the Drillback from Target System window, you can click on an
amount to drill down in FDM to the detail source data.

Drilling Back from Financial Management

In a Financial Management grid, right-click a data input cell,
and select Audit Intersection.
Drilling Back from Financial Management

If you run FDM and Financial Management with Shared Services, you enable FDM
drillback from Financial Management by performing the following tasks:
• Specify the FDM application name as a property of the Financial Management
application
• Create a link to FDM in Financial Management
After enabling FDM drillback for Financial Management, you create a data grid in
Financial Management that includes data input cells that were loaded from FDM. You
can then right-click the data input cell and drill back to the source data in FDM.
If you are running FDM and Financial Management without Shared Services, refer to the
Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11.1.1
Readme file for details on how to enable the FDM drillback from Financial Management.

Drilling Back from Essbase Studio

Drill-through
report created in
Essbase Studio.
In Smart View, right-click a data cell, and drill back to

FDM by selecting a drill-through report.
NOTE
If you are running FDM and Financial Management without Shared Services, refer
to the Oracle Hyperion Financial Data Quality Management, Fusion Edition
Release 11.1.1 Readme file for details on how to enable the FDM drillback from
Financial Management.
Drilling Back from Essbase Studio

You complete the following steps to set up FDM drillback for Essbase:
1. Create the Essbase database in Essbase Studio.
2. Set up the Essbase database and FDM application for Shared Services
authentication.

3. In Essbase Studio, create a drill-through report to the dynamic URL for FDM.
NOTE
For details about creating drill-through reports, refer to the Drill-through
Reports chapter in the Oracle Essbase Studio Release 11.1.1 User’s Guide.
4. In Smart View, create a worksheet that contains base-level amounts that were

loaded by FDM, and drill back to FDM.
To drill back to FDM from Smart View:

1. In Smart View, create a worksheet that contains base-level data loaded by FDM.
2. Select a base-level data cell.
3. Right-click the data cell, and select Hyperion > Ad Hoc Analysis > Drill-Through Reports.
The Drill-Through Reports dialog box displays the drill-through
reports that are associated with the data cell.
4. Select the drill-through URL report for FDM, and click Launch.
The Drillback from Target System window is displayed.

Drilling Back from Planning

In a Planning data form, right-click a data input cell, and
select Drill Back to Source.
Drilling Back from Planning

To enable FDM drillback from Planning applications, set the following values for the
application properties in Planning:
• ENABLE_FOR_FDM—True
• FDM_ADAPTER_KEY—Name of the FDM adapter key (for example, ES9x-G4-B)
• FDM_APPLICATION_NAME—Name of the FDM application
After setting the application properties and restarting the application server, you create a
data form in Planning that includes base-level amounts that were loaded by FDM. You
can then right-click the data input cell and drill back to the source data in FDM.

Drilling Back from Strategic Finance

Data loaded by FDM is
designated by an orange
arrow in the cell.
In Strategic Finance, right-click a data-input cell,

and select Audit Intersection.
Drilling Back from Strategic Finance

To enable FDM drillback from Strategic Finance databases, set the following FDM
settings in Hyperion Strategic Finance Administrator:
• Adapter Name—Name of the FDM adapter key (for example, SF11x-G3-A)
• Application Name—Name of the FDM application
In the entity window of Strategic Finance, data input cells that were loaded by FDM are
designated by an orange arrow in the lower-right corner of the cell. You can right-click the
data input cell, and select Audit Intersection to drill back to the source data in FDM.

Summary

• Import source data
• Sort, find, filter, and delete records
• Validate dimension mappings
• Drill up and down on values
• Drill back to FDM from target applications

L E S S O N 9
Building Validation Rules 9

Objectives
• Create validation rule groups
• Create validation rules in the FDM Web client
• Create validation rules in Validation Editor
• Assign validation rules to locations
• Check validation rules
Lesson 9 Building Validation Rules
About Validation Rules and Reports

Validation
rules
Validation
report
About Validation Rules and Reports

Validation rule groups enable you to define a set of rules and annotations to enforce data
integrity during the data collection process. When you assign a validation rule group to a
location and then load data to the target system, FDM generates a Validation report.
FDM runs the report for all entities that you define in the validation entity group that you
also assign to the same location. If you do not assign a validation entity group to the
location, FDM runs the Validation report for each target entity that you load to the target
system.
NOTE
Setting up validation entity groups is covered in Lesson 10, “Setting up Validation
Entities.”

You can retrieve data from three data sources through validation rules:
• Target system—Retrieves values from target systems
• FDM source—Retrieves values from the data that you import from the source
system into FDM
• FDM converted—Retrieves values from the data that you validate in FDM

This lesson focuses on setting up rules for target system data. For information about
retrieving FDM source and FDM converted data, see Oracle Hyperion Financial Data
Quality Management, Fusion Edition Release 11.1.1 Administrator’s Guide.
You perform the following tasks to set up and check validation rules:
1. Create validation rule groups
2. Create validation rules
3. Assign validation rule groups to locations
4. Check validation rules

Creating Validation Rule Groups
Add a validation group. Save the changes.

Creating Validation Rule Groups

You create validation rule groups to hold validation rules that perform checks and
balances against target systems. You define the validation rule group names and
descriptions, and FDM fills in the creation date. The Validation Rules window contains
two tables. The top table displays the list of validation rule groups, and the bottom table
displays the validation rules for the selected validation rule group.
To create validation rule groups:

1. In the FDM Web client, select MetaData > Validation Rules.
The Validation Rules window displays a validation rule group table
at the top of the window and a table for validation rules at the
bottom of the window.


A row is added to the validation rule group table.
3. In the Validation Group column, enter the validation rule group name.
4. In the Description column, enter a description for the validation rule group.

FDM fills in the current date in the Date Created column.

Creating Validation Rules

Display Value
menu commands
Creating Validation Rules

Each validation rule represents a line on the Validation report. You define rules to display
values on the report from the target system and to check on balances in the target
system. Rules can also display titles and subtitles on the report to make it more
readable.
You create validation rules in the bottom table of the Validation Rules window for the
selected validation rule group. The validation rules table contains columns for the rule
attributes—Display Value, Description, Rule Name, Rule Text, Type, Category,
Sequence, and Rule Logic. In the Display Value column, you can create a custom
expression, select a target account, or select a format code.

To create validation rules:

1. In the FDM Web client, select MetaData > Validation Rules, and select a validation rule
group from the top table of the Validation Rules window.
The table for the validation rules of the selected validation rule
group is displayed at the bottom of the window.

A blank row is added to the table.
3. Double-click in the Display Value column, and point to the arrow.
A menu displays the commands Zoom, Browse For Target
Account, and Select Format Code.
• Select Zoom, enter the text for a custom expression, account, or format code in the
Zoom Editor dialog box, and click OK.
• Select Browse For Target Account, select a target system account in the Validation
Rule Target Account Lookup dialog box, and click OK.
• Select Select Format Code, select #Title, #SubTitle, #ModeList, or #ModeRule from the
Select Format Code list, and click OK.
5. Enter or select the validation rule attributes.
7. Repeat steps 2 through 6 for each validation rule that you want to add to the
validation rule group.

Selecting Display Values

Selecting Display Values

The Display Value column controls how FDM formats each rule that you define. You can
create a custom expression, select a target account, or select a report format code.
FDM processes the contents of the Display Value column with the following rules:
• If the column contains a report format code, FDM does not look up target system
values.
• If the column contains a valid target account, FDM retrieves the value of the account.
The account value is displayed in the Value column of the Validation report.
• If the column contains a custom expression, FDM displays the result of the
expression. The expression result is displayed in the Value column of the Validation
report.

Creating Custom Expressions

You create custom expressions to perform calculations and display their results on the
Validation report. For example, you can sum the values of target accounts or subtract a
prior period account value from the current period account value. You must limit custom
expressions to 75 characters.
Browsing for Target System Accounts

You can easily select target system accounts by using Browse for Target Account. This
option opens a list of target accounts that you can browse and search. The account that
you select is displayed in the Display Value column.
Selecting Format Codes

You use format codes to display titles and subtitles on the Validation report and to define
the report mode.
There are two report modes:
• Listing mode—Displays target account values or custom expression results on the
report. Rules that you define below the ModeList format are displayed on the report
with their name, description, and value.
• Rule mode—Displays rule results on the report. Rules that you define below the
ModeRule format are displayed on the report with their rule name, rule description,
and value. FDM evaluates the expression in the Rule Logic column of each rule, and
tests whether the rule is true or false. The status of the rule, OK or Error, is displayed
on the report to the left of each rule.
There are four format codes, as described in the following table:
Format Code Description

#Title Inserts a title line on the report. The text that you enter in the
Description column of the title is formatted and displayed as the report
title.
#SubTitle Inserts a subtitle line on the report. The text that you enter in the
Description column of the subtitle is formatted and displayed as a
group subtitle.
#ModeList Sets the report mode to Listing.
#ModeRule Sets the report mode to Rule.

Defining Rule Attributes
Report title or Rule

account description description Category

Format code, Name Type of Rule Rule logic expression
target account, or of rule entity processing or function
custom expression order
Defining Rule Attributes

In addition to the display value of the rule, you can define the following rule attributes:
Description If the report is in Listing mode, displays the account description, report
titles, or report subtitles on the report. The description is limited to 50
characters.
Rule Name If the report is in Rule mode, displays the identifier for the rule on the report.
Enter a unique name for the rule, and limit the name to 255 characters.
Rule Text If the report is in Rule mode, explains the basis or logic behind the rule on
the report. Limit the explanatory text to 255 characters.
Type Displays the rule on the report for base entities, parent entities, or all
entities.

Category Defines the rule for a specific category or for all categories. If the selected
category is the same as the category in the FDM POV, displays the rule on
the report.
Select All to display the rule on the report regardless of the category in the
FDM POV.
Sequence Controls the order in which FDM processes the format codes and rules. It is

good practice to increment the sequence numbers by 10 to allow for the
addition of rules.
Rule Logic Defines the lookup function or validation rule expression to display on the
report.
The validation rule Type attribute corresponds to the Type attribute of the validation
entities. There are three Type attribute options:
• All—Displays the validation rule on the Validation report for all entities.
• Base—Displays the validation rule on the Validation report only for validation entities
whose Type attribute is set to Base or All.
• Parent—Displays the validation rule on the Validation report only for validation
entities whose Type attribute is set to Parent or All.
For more information about validation entities, see Lesson 10, “Setting Up Validation
Entities.”

Adding Rule Logic

Rule logic expression
or function
Adding Rule Logic

You create rule logic with validation rule expressions, lookup functions, and advanced
functions to display and validate target system account balances.
Validation rule expressions and functions validate account balances and display the
results on the Validation report. You use standard Microsoft VB script language to create
the expressions and to test for a true or false condition. FDM flags each rule on the
report as either passing (OK) or failing (Error).
Lookup functions display target system account values in the Value column of the
Validation report.
Multi-Dimension Lookup Function

You use the Multi-Dimension Lookup function to retrieve account values from target
systems other than Hyperion Enterprise. You enter the function in the Rule Logic or
Display Value column.

You reference the target system account by enclosing it in pipes (|). Within the pipes,
you can also include dimension parameters to define which target system account you
want to retrieve. The dimension parameters, except for the account, are optional. You
define the parameters in the following order, separated by commas:
|Scenario, Period, Year, View, Entity, Account, ICP, UD1, UD2, UD3, UD4, UD5, UD6,
UD7, UD8, UD9, UD10, UD11, UD12, UD13, UD14, UD15, UD16, UD17, UD18, UD19,
UD20, DataValue|

If you omit dimensions from the Lookup function, you must include the commas as
placeholders for the parameters. In the following example, you retrieve the value for the
target account Tot_Net_Sls for the TotDepts and TotProd custom dimension members:
|,,,,,,Tot_Net_Sls,,TotDepts,TotProd,,,,,,,,,,,,,,,,,,,|
Hyperion Enterprise Lookup Function

You use the Hyperion Enterprise Lookup function to retrieve account values from
Hyperion Enterprise target systems. You simply add the target account to the function,
and allow FDM to retrieve the other dimensions dynamically.
In the following example, FDM retrieves the Balance target account for the target period
and category set in the FDM POV:
|Balance|
In the following validation rule expression, FDM retrieves and checks the Balance target
account value. If the value is between -10.00 and 10.00, FDM flags the rule as OK;
otherwise, FDM flags it as an error.
|Balance| >= -10.00 AND |Balance| <= 10.00

Rule Logic Examples
Example 1:
|Actual,March,2008,YTD,Ohio,Balance,Michigan,

Engines,Ford,Trucks,[None],,,,,USD,,,,,,,,,,,,|
Example 2:
|Actual,-1,2008,,,Balance,,,,,,,,,,,,,,,,,,,,,,|>0
Example 3:
|,,,,,Balance,,,,,,,,,,,,,,,,,,,,,,|> -10.00 AND
|,,,,,Balance,,,,,,,,,,,,,,,,,,,,,,|< 10.00
Rule Logic Examples

The examples on the slide illustrate ways that you can retrieve and check values from
target systems other than Hyperion Enterprise.
In the first example, FDM looks up the value of the target account, Balance, for the
dimensions that you specified in the rule. All missing custom dimensions default to
[None]. FDM retrieves the value during the validation check, and displays it on the
Validation report.
In the second example, FDM looks up the value of the Balance target account for the
Actual category, the prior period (-1), and the year 2008. The ICP dimension defaults to
[ICP None], the View dimension defaults to YTD, and the Currency dimension defaults
to 0. FDM retrieves the value for each entity in the Validation Entity Group that you
assign to this location. After retrieving the value, FDM checks whether the value is
greater than 0, displays the result on the Validation report, and flags the line as either OK
or Error.

In the third example, FDM looks up the value of the Balance target account for the target
period and category set in the FDM POV. The Year dimension defaults to the current
year set in the active FDM POV. The rule passes the validation check if the target
account is between -10.00 and 10.00.

Creating Validation Rules in Validation Editor

Start Validation Editor.
Creating Validation Rules in Validation Editor

Validation Editor enables you to create validation rules more easily. With the editor, you
can develop rule logic for rules that you defined under the ModeList or ModeRule format
code.
For the example on the slide, you want to define a Lookup function to retrieve the
OUT_OF_BALANCE_ACCT target system account value for selected dimensions, and
test if it is equal to zero.
The Validation Editor dialog box contains three tabs—Rule, Look Up, and Test.

Adding Rules and Display Values

Rule tab in Validation Editor
Adding Rules and Display Values

You use the Rule tab to build the validation rule logic expression and display value.
The Rule tab contains two areas:
• Rule—Area for building the rule that you want to test.
• Display—Area for building the value that you want to display on the Validation report.
This value can be different from the value that is tested in the rule.
You can enter Lookup functions manually in the Rule area, or you can select the
dimensions on the Look Up tab. When you enter the Lookup functions manually, you
must type the dimension member names correctly, include the dimensions in the correct
order, and add the correct number of commas as placeholders for missing dimensions.
On the Rule tab, you can activate the Look Up tab by typing two pipes in the Rule or
Display area.

Looking Up Members

Lookup tab in Validation Editor
Looking Up Members
You use the Look Up tab to select dimension members that you want to retrieve from the
target system. This method ensures that you enter each dimension member correctly. As
you select the dimension members, FDM places the dimensions in the proper order for
the Lookup function, and includes all necessary comma separators.
The Look Up tab contains the following items:
Item Description
Rule area Displays the rule that you are creating. The rule comprises Retrieve
functions and other VBA script calls. Each Retrieve function is
displayed on a separate line from VBA script functions.
Display area Shows the display rule that you are creating. The rule comprises
Retrieve functions and other VBA script calls. Each Retrieve function
is displayed on a separate line from VBA script functions.

Item Description
Rule intersection tree When a Retrieve function is selected from the Rule or Display areas,
the rule intersection tree is enabled. This tree enables users to enter
the values for each dimension in the Retrieve. The text for each active
dimension is colored blue while those that are not active are dimmed.
Copy Tree/Paste to Copies the values in all dimensions for the selected rule. After
Editor button copying, the button text changes to Past to Editor. To paste the values
to a different rule, select the new rule, and then click the Paste to

Editor button.
Update button Closes Validation Editor, and saves the contents of the Rule and
Display areas to the Validation Rules frame.
Cancel button Closes Validation Editor without saving changes.
For the example on the slide, you select the target account OUT_OF_BALANCE_ACCT.
For this account, you select the top ICP dimension member, [ICP Top]. It is important to
select the correct members for all custom dimensions; if you leave these dimensions
blank, FDM can retrieve the wrong values from the target system.
To select members for Lookup functions:

1. Launch the FDM Web client, and select MetaData > Validation Rules.
2. In the top table, select a validation rule group.
3. For a row in the bottom table that contains a rule or display value, double-click in the
Rule Logic column, and point to the arrow.
A menu displays the commands Validation Editor and Zoom.
4. Select Validation Editor.
The Rule tab in the Validation Editor dialog box is displayed.
5. Enter two pipes in the Rule area to activate the Look Up tab.
6. Select the Look Up tab.
7. In the left pane, click a dimension name, and select Browse.
The dialog box with target system dimension members is
displayed.
8. Select a dimension member.
The selected dimension member is displayed in the Lookup
function in the Rule area.

9. Repeat steps 7 and 8 to add a member for other dimensions.

10. Select the Rule tab.
The updated rule with the selected members is displayed.
11. Select Update to save the changes.
The Validation Rules window is displayed.

Testing Rules and Display Values

Test
results
Test tab in Validation Editor
Testing Rules and Display Values

You can test validation rules to ensure that FDM generates the correct results before you
put the rules into production. You use the Test Rule and Test Display buttons to test the
rule in the Rule and Display areas on the Rule tab.
If the location that you are testing with the rule passes the validation test, FDM returns
True in the Expression Result box; otherwise, FDM returns False.
The Test tab contains the following items:
Item Description
Test Rule button Runs the rule in the Rule area for the selected location, pulls values
from the target system, and returns the rule results
Test Display button Runs the rule in the Display area for the selected location, pulls
values from the target system, and returns the display results

Item Description
Reset button Resets all fields in the Test tab
Expression Eval button Calculates expressions in the Expression After Lookup Substitution
area
Expression area Displays the rule that you are testing
Expression After Lookup Returns the results of the expression that you are testing after FDM

Substitution area performs the lookup from the target system
Lookup Errors area Displays errors that FDM finds during the rule test
Expression Result area Displays the result of the rule test—True or False
Update button Closes the Validation Editor, and saves the contents of the Rule
and Display fields to the Validation Rules table
To test rules and display values:

1. Launch the FDM Web client, and select MetaData > Validation Rules.
2. In the top table, select a validation rule group.
3. For a row in the bottom table that contains a rule or display value, double-click in the
Rule Logic column, and point to the arrow.
A menu displays the commands Validation Editor and Zoom.
4. Select Validation Editor.
The Rule tab in the Validation Editor dialog box is displayed.
5. Select the Test tab.
6. From Select Test Entity, select a target system entity.
7. Click Test Rule or Test Display.
A dialog box warns that the process may take a few minutes.
8. Click OK.
FDM runs the test and displays the results.
9. Correct any errors on the Rule or Look Up tab, and repeat the test.
10. Click Update to save changes, or click Cancel to close the dialog box without saving
changes.
The Validation Rules table is displayed.

Assigning Validation Rules to Locations
1. In the FDM Web client, select MetaData > Locations, and

select the location.

3. From Validation Rules, select the validation group.
4. Click Save.
Assigning Validation Rules to Locations

When you assign validation rules to locations, FDM automatically uses the validation
rules when you export data from the locations to the target systems. FDM executes a
validation check only if you assign a validation rules group to the locations.
You can assign the same validation rules group to multiple locations.


Report status:
Pass or Fail
Rule status:
OK or Error

After you export data to the target system, FDM performs a validation check based on
the criteria in the validation rules group that you assigned to the location.
When the validation rules are executed successfully, a validation report is displayed with
a Pass status. The report displays the accounts and rules that you defined in the group
and the results of the rules. When you close the report, a success icon is displayed
below Check at the top of the Export window.
If the validation rules are not met, the validation check fails, and a Fail status is displayed
at the top of the report. You must follow up and investigate why the numbers are out of
balance before you can complete the Check task.

Summary

• Create validation rule groups
• Create validation rules in the FDM Web client
• Create validation rules in Validation Editor
• Assign validation rules to locations
• Check validation rules

9-26

L E S S O N 1 0
Setting Up Validation Entities 10

Objectives
• Create validation entity groups
• Create validation entities
• Assign validation entity groups to locations
• Verify consolidations
Lesson 10 Setting Up Validation Entities
About Validation Entities

Validation
entities
Portion of
Validation
report
About Validation Entities

You use validation entity groups to select a set of target system entities that FDM
consolidates and can then display on Validation reports. You activate validation entity
groups by assigning them to locations. When you assign validation entity groups to
locations, FDM triggers a consolidation of the target system entities after a data load.
You perform the following tasks to set up validation entities for locations:
1. Create validation entity groups
2. Create validation entities
3. Assign validation entity groups to locations

Creating Validation Entity Groups
Add a validation
entity group. Save the changes.

Creating Validation Entity Groups

You create validation entity groups to hold validation entities that you want to consolidate
and display on Validation reports.
The Validation Entities window contains two tables. The top table displays the list of
validation entity groups, and the bottom table displays the validation entities for the
selected validation entity group.
To create validation entity groups:

1. In the FDM Web client, select MetaData > Validation Entities.
The Validation Entities window displays a validation entity group
table at the top of the window and a table for validation entities at


A row is added to the validation entity group table.
3. In the Validation Entity Group column, enter the validation entity group name.
4. In the Description column, enter a description for the validation entity group.

Creating Validation Entities

Browse for the parent entity
from the target system.
Creating Validation Entities

Validation entities define the target system entities that you want to consolidate. After
consolidation, FDM can display the validation entities on the Validation report. You can
define multiple validation entities in a validation entity group.
The following table describes validation entity attributes:
Parent or Organization in which to consolidate the Hyperion Enterprise entity or
Organization the parent of the entity to consolidate for all other target systems. This
attribute is used only if you also select the Consolidate attribute.
Entity Target system entity that you want to consolidate. If you select the On
Report attribute, FDM displays the entity on the Validation report.

Consolidate Check box used to signal FDM to consolidate the entity before
displaying the entity on the Validation report. FDM displays the entity
on the report if you also select the On Report attribute.
Start Period Starting period that controls how FDM consolidates the target system
entity.
Value of 0—FDM consolidates only the current period.

Value of 1—FDM consolidates the entity for period 1 through the
current period.
Type All, Base, or Parent entities to display on the Validation report.
On Report Check box used to signal FDM to include the entity on the Validation
report. If you select the Consolidate attribute but not the On Report
attribute, FDM consolidates the entity but does not display it on the
report.
Sequence Number that indicates the order in which the validation entities are
consolidated and arranged on the Validation report. It is good practice
to increment the sequence numbers by 10 to allow for the addition of
validation entities.
The validation entity Type attribute corresponds to the Type attribute of the validation
rules. There are three Type attribute options:
• All—Displays the entity on the Validation report for all validation rules, regardless of
the validation rule Type attribute.
• Base—Displays the entity on the Validation report only for validation rules whose
Type attribute is set to Base or All.
• Parent—Displays the entity on the Validation report only for validation rules whose
Type attribute is set to Parent or All.
To create validation entities:

1. In the FDM Web client, select MetaData > Validation Entities, and then select a validation
entity group from the top table of the Validation Entities window.
The table for the validation entities of the selected group is
displayed at the bottom of the window.
A blank row is added to the table.

3. Double-click in the Parent column, point to the arrow, and select Browse for Parent.
The Organization Lookup dialog box is displayed.
TIP
You can search for entities in the Organization Lookup dialog box.

4. Select a parent entity, and click OK.
The parent entity is displayed in the Parent column.
5. Double-click in the Entity column, point to the arrow, and select Browse for Entity.
The Entity Lookup dialog box is displayed.
6. Select an entity, and click OK.
The entity is displayed in the Entity column.
7. In the Consolidate column, double-click the check box to consolidate the entity in the
target system after a data load.
8. Double-click in the Start Period column, and enter the period to consolidate.
9. Double-click in the Type column, and select All, Parent, or Base.
10. In the On Report column, double-click the check box to display the entity on the
Validation report.
11. Optional: Double-click in the Sequence column, and enter a sequence number.
12. In the bottom table, click Update Grid to save the changes.
13. Repeat steps 2 through 12 for each validation entity that you want to add to the
validation entity group.

Assigning Validation Entity Groups to Locations
1. In the FDM Web client, select MetaData > Locations and


3. From Validation Entities, select the validation entity group.
4. Click Save.
Assigning Validation Entity Groups to Locations

After you assign validation rules to locations, FDM generates the Validation reports when
you export data from the locations to the target systems. By default, FDM runs the
reports for each entity that you loaded to the target system.
When you assign validation entity groups to locations, FDM runs the Validation reports
for the entities that you defined in the validation entity groups that are assigned to the
locations.
You can assign the same validation entity group to multiple locations.

Verifying Consolidations

Validation
entity
Validation
entity
Verifying Consolidations
After you export data to the target system, FDM performs a validation check based on
the criteria in the validation rules group and validation entity group that you assigned to
the location. FDM uses the validation entity group to select the entities to consolidate and
display on the report.
For the example on the slide, FDM runs the Validation report for the Texas location and
displays the validation rules for the validation entities, NA and TX.

Summary

• Create validation entity groups
• Create validation entities
• Assign validation entity groups to locations
• Verify consolidations

L E S S O N 1 1
Processing Batch Files 11

Objectives
• Describe the Batch Loader process
• Set up batch-load files
• Process batch-load files
• Create batch scripts
• Schedule batch scripts in Task Manager
Lesson 11 Processing Batch Files
About Batch Processing
Batch Processing
tool in Workbench

or
Hyperion FDM
Batch-load Task Manager
files
Completed
Workflow
tasks
About Batch Processing

Batch Loader enables you to move data files through the FDM Workflow tasks in a batch
environment. You can process any Workflow task—Import, Validate, Export, Load,
Consolidate, and Check. You can also process load files up to a particular task. For
example, when you select to process the files Up-To-Validate, Batch Loader imports and
validates the data, but does not continue with the export.
NOTE
Batch Loader is part of the FDM Adapter Suite and is available only with a Batch
Loader license. Contact your Oracle sales representative for information about
Batch Loader licensing options.

To process batch-load files, you launch Batch Loader from the Batch Processing tool in
Workbench or from the Hyperion FDM Task Manager. In Workbench, you can select the
batch options and execute the batch immediately, or you can create a script that you can
schedule in Task Manager. After creating a script, you use Task Manager to schedule the
batch script to run immediately or later, and you can run it once or on a recurring basis,
such as weekly or monthly.
Overview of batch processing in FDM:

1. Enable batch processing in Application Settings.
2. Set up the batch-load files and copy them to the OpenBatch or OpenBatchML
directory.
3. Perform one of the following actions to process the batches:
• From the Batch Processing window in Workbench, select batch control options,
and execute the batch.
• From the Batch Processing window in Workbench, create a script with the selected
batch control options. In Workbench, you can also manually create the script on
the Scripts tab.
• From Task Manager, create and schedule a task to run a batch script.

Enabling Batch Processing
1. In the FDM Web client, select Administration > Application

Settings.

2. From Options, select Batch Loader.
3. Select the On/Off check box, and click Save.
Enabling Batch Processing

You must enable batch processing in Application Settings to activate the Batch
Processing command in Workbench.

Setting Up Batch-Load Files
• File name format for standard batch-load files:

a_Texas_Actuals_Jan-2009_RR.txt
File ID Location Category Period Load method
• Directories for batch-load files:
FDM application name\Inbox\Batches\OpenBatch

FDM application name\Inbox\Batches\OpenBatchML
Setting Up Batch-Load Files

You can process two types of files in Batch Loader:
• Standard—Text files that contain data for one month. Standard files require a file
name format that defines the batch load order, location, category, period, and load
methods. Place these files in the FDM application\Inbox\Batches\OpenBatch
directory before you execute the batch.
• Multiload—Text or Excel files that contain data for multiple periods and locations.
The files contain metadata and do not require a specific file name format. Place
these files in the FDM application\Inbox\Batches\OpenBatchML directory before you
execute the batch.

Standard batch-load files require a file name format that consists of five segments in the
following order:
1. FileID—Free-form field that you use to control the load order. Batch files load in
alphabetical order by file name. A file named a_Texas_Actuals_Jan-2009_RR.txt
loads before a file named b_Texas_Actuals_Feb-2009_RR.txt.
2. Location—FDM location.

3. Category—FDM category.
4. Period—FDM period.
5. Load Method—Two characters that define the FDM and target applications load
methods. The first character defines the load method for the FDM application, and
the second character defines the load method for the target application. Valid
characters are A (append) and R (replace).

Processing Batches
In Workbench, select Tools > Batch Processing.

Batch
controls
Batch
results
Processing Batches
After copying the batch-load files to the appropriate directory, you process the files from
the Batch Processing tool in Workbench, or you create a batch script in Workbench that
you later schedule in Task Manager.
Batch Controls
From the Batch Processing tool, you select batch controls that define the batch options:
• Batch Type—Determines whether the batch loads standard or multiload files.
• Process Level—Determines the Workflow tasks to process (for example, Import,
Export, Up-To-Validate, or Consolidate Only).

• Process Method—Determines whether the batch loads in serial or parallel mode.

Serial mode processes files sequentially, requiring that one file complete its process
before the next file starts its process. Parallel mode processes files simultaneously.
• No. of Parallel Processes—If Process Method is set to parallel, determines the
number of processes that the batch runs concurrently. For example, if a batch
contains 20 load files and the number of processes is set to 5, five sequential
processes, each with four load files, run concurrently.

NOTE
When processing batch-load files in parallel, FDM groups files that load to
one FDM location in one process. This action avoids invalid results by
ensuring that multiple processes do not attempt to load data to one location
simultaneously.
• Load Balance Server—Determines the load balance server that processes the
batch.
• File Name Delimiter—Defines the character (~, _, or @) that is used to separate the
five segments of a standard batch-load file name.
• AutoMap Correct—Enables or disables automapping for the batch-load files.
FDM can automatically map all unmapped members in batch-load files. For unmapped
members, FDM creates map entries in the location maps that are associated with the
members. The mapped entries are based on predetermined suspense accounts. Before
setting up suspense accounts, you must add a location named AutoMapCorrect to the
FDM application. Then, in the Explicit map, you create a map for each dimension. The
source value for each map must be named AutoCorrect, but the target value can be any
member in the selected dimension.
Batch Results
As Batch Loader processes the batch-load files, the batch results are displayed in the
Batch Monitor area of the Batch Processing window. The results display the batch ID, the
status of the tasks, the status of each load file, and whether the batch was completed
successfully. If the batch failed, an error message is displayed.
After the batch is completed, Batch Loader moves the batch-load files from the
OpenBatch or OpenBatchML directory to a new directory. For standard files, the
directory name is the unique batch ID. For multiload files, the directory name is the
unique batch ID with a prefix of ML. These batch IDs are referenced in import logs.

To process batch-load files in Workbench:

1. Create the batch-load files, and place them in the appropriate FDM directory.
2. From Workbench, select Tools > Batch Processing.
The Batch Processing window is displayed.
3. Set the batch controls.

• Click Execute to run the batch with the selected controls.
The Batch Monitor area displays the batch status and the batch-
load files that Batch Loader is processing.
• Click Create Script, and enter a script name to create a batch script with the selected
batch controls.
In Task Manager, you can schedule the batch script to run once or
on a recurring basis.

Creating Batch Scripts
Batch Processing
tool in Workbench

Scripts tab in
Workbench
Creating Batch Scripts

With batch scripts, you can run Workflow tasks in a scheduled batch environment. You
create the scripts in Workbench, either manually or with the Batch Processing tool. The
Batch Processing tool stores the scripts in the Custom > General folder on the Scripts
tab in Workbench.
For the example on the slide, you create a batch script with the Batch Processing tool.
The batch controls specify standard files with the @ character delimiter, and a serial
processing method. The process level is Up-To-Check. The Batch Processing tool
creates the following batch script:
Sub Batch_UpToCheck()
‘--------------------------------------
‘FDM CUSTOM Script:
‘Created By: trnadmin
‘Date Created: 2/7/2009 1/20/2009 3:59:04 PM

‘Purpose: Execute a Batch Loader task.

‘--------------------------------------
‘Execute a STANDARD batch
‘--------------------------------------
‘Use Serial Processing
‘--------------------------------------
‘Declare Local Variables
Dim lngProcessLevel

Dim strDelimiter
Dim blnAutoMapCorrect
‘Initialize Variables
lngProcessLevel = 12 ‘Up-To-Check
strDelimiter = “@”
blnAutoMapCorrect = 0
‘Create the file collection

Set BATCHENG.PcolFiles =
BATCHENG.fFileCollectionCreate(CStr(strDelimiter))
‘Execute a Standard Serial batch

BATCHENG.mFileCollectionProcess BATCHENG.PcolFiles,
CLng(lngProcessLevel), ,CBool(blnAutoMapCorrect)
End Sub
NOTE
For more information about creating scripts in Workbench, see the last three
lessons of the course.

Scheduling Batch Scripts in Task Manager
In Hyperion FDM Task Manager, select Task > New Task.

Set Set
General Schedule
properties. properties.
Results
Scheduling Batch Scripts in Task Manager

After creating a batch script, you use Task Manager to schedule the script to run
immediately or later. You can run the batch script once or on a recurring basis, such as
weekly or monthly.
To schedule batch scripts in Task Manager:

1. Create the batch load files, and place them in the appropriate FDM directory,
OpenBatch or OpenBatchML.
2. Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Task
Manager > Task Manager.
The Hyperion FDM Task Manager window is displayed.

3. Select Task > New Task.

The General tab of the Task Properties dialog box is displayed.
4. For Task Name, enter a name to identify the task.
5. For Application, select the FDM application name.
6. For Action Script, select the batch script to run in the batch load process.

7. For User Name, Password, and Confirm Password, enter the FDM user name and
password.
8. Select the Enabled check box to enable the batch to run at the specified time.
9. Select the Schedule tab.
10. For Frequency, select Repeat, Weekly, or Monthly.
• For the Repeat frequency, select how often to repeat the task by typing the number
of seconds.
• For the Weekly frequency, select the start time and the day of the week to run the
task.
• For the Monthly frequency, select the start time, month, and day of the month to
run the task.
The scheduled task is displayed in the Hyperion FDM Task
Manager window, with the task name, frequency, script name, last
time executed, and status.
12. Select View > Refresh Tasks to refresh the batch status and monitor the batch tasks.

Summary

• Describe the Batch Loader process
• Set up batch-load files
• Process batch-load files
• Create batch scripts
• Schedule batch scripts in Task Manager

M O D U L E 4
Creating Additional Loading Options 11

Overview
The aim of this module is to use additional options for loading data to target
systems. You learn to set up logic accounts and to load FDM journals. You
also learn to load data to target systems with multiload files.
• Creating Logic Accounts
• Loading FDM Journals
• Loading Data with Multiload Files

L E S S O N 1 2
Creating Logic Accounts 12

Objectives
• Describe logic accounts
• Create logic groups
• Create simple logic accounts
• Create complex logic accounts
• Assign logic groups to locations
Module 4 Creating Additional Loading Options
Lesson 12 Creating Logic Accounts
About Logic Accounts
Set up logic account L1100 for the

Texas location to summarize source

accounts that begin with 11.
FDM creates logic account

L1100 with a total amount
Import source data records of 60,500, and displays the
for the Texas location. account in the Import
window.
Account Entity ICP Amount
1150 TX 07 50,500
1176 TX 04 10,000
1222 TX 04 9,500
About Logic Accounts

You create logic accounts to calculate data values that are not provided in the source
data files. When you associate logic accounts with data locations, FDM generates the
logic accounts and their values when you import the source data to the locations. Just
like source accounts, you can map and load logic accounts to target systems.
You typically use logic accounts for the following tasks:
• Statistical loading—Map a source account to multiple target accounts
• Conditional mapping—Map source accounts based on their values
• Arithmetic mapping—Perform arithmetic operations on source values
Because you create logic accounts in FDM, detailed audit trails for the logic account
values are not available.

Logic tasks:
1. Create logic groups
2. Define the logic accounts for each group
3. Assign the logic groups to data-load locations

Creating Logic Groups
Add a logic group.

Types of logic groups.
Creating Logic Groups

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

FDM administrators can view and modify all logic groups and logic accounts. FDM end
users can view and modify only the logic groups and accounts that they created, and
only if the administrator changes object security to allow end users to open the Logic
Groups window.
To create logic groups:

1. In the FDM Web client, select MetaData > Logic Groups.

The Logic Groups window displays a logic group table at the top
of the window and a table for logic accounts at the bottom of the
window.
A row is added to the logic group table.
3. In the Logic Group column, enter the logic group name.
4. In the Description column, enter a description for the logic group.
5. In the Logic Type column, select Simple Logic or Complex Logic.

Creating Simple Logic Accounts

Simple
logic
group.
Enter the logic account name, or click Zoom

to enter the account name in Zoom Editor.
Creating Simple Logic Accounts

After creating a simple logic group, you define the logic accounts for the group in the
bottom table of the Logic Groups window. Each row in this table represents logic
accounts that you want to calculate based only on source accounts.
When you import source data, FDM generates the logic accounts and displays their
names in the Account column of the Import window. You should precede logic account
names with a character, such as an L, to distinguish the logic accounts from the source
accounts. If you intend to load the logic account values to target systems, you must map
the logic account names to valid target system accounts.

You can define the following attributes for simple logic accounts:
Item Logic account name. FDM displays the name in the Account column of
the Import window.
Description Logic account description. FDM displays the description in the Account
Description column of the Import window.

Type Operator (Between, In, or Like) that works with the Criteria Value attribute
to determine the source accounts for the logic account calculation.
Criteria Value Criteria that work with the Type attribute to determine the source accounts
for the logic account calculation.
Operator Operator (+, -, *, /, NA, Fun, or Exp) that works with the Value/Exp
attribute to perform calculations and derive the logic account values.
Value/Exp Value or logic expression that works with the Operator attribute to perform
calculations and derive the logic account values.
Seq Sequence in which FDM processes the logic account calculations. The
order allows FDM to use one logic account to calculate other logic
accounts, as long as FDM first calculates the dependent account.
Exp On-off switch that determines whether you must map the logic account to
a target system account so that FDM can export the logic account to the
target system.
NOTE
Later topics in this lesson contain more information about the Type, Criteria Value,
Operator, and Value/Exp attributes.
To create simple logic accounts:

1. In the FDM Web client, select MetaData > Logic Groups, and then select a simple logic
group from the top table of the Logic Groups window.
The table for the logic accounts of the selected logic group is
A row is added to the bottom table.
3. In the Item column, enter the logic account name.

4. In the other columns, enter or select the logic account attributes.

6. Repeat steps 2 through 5 for each logic account that you want to create in the logic
group.

Selecting Source Accounts for Calculations
Type Criteria Value Selected Source Accounts

Range of accounts between account 1000 and
Between 1000, 1999
account 1999
In 1031 Single account 1031
In 1017, 1028, 1215 Accounts 1017, 1028, and 1215
Accounts that begin with 25 followed by two

Like 25??
characters
Accounts that begin with 10 followed by any
Like 10*
number of characters
Selecting Source Accounts for Calculations

You can derive a logic account value from multiple source accounts. The logic account
Type and Criteria Value attributes work in tandem to select the source accounts that
FDM processes to derive the logic account value.
For the Type attribute, you select the operator—Between, In, or Like. In the Criteria Value
attribute, you specify the source account names.
Type Description
Between Specifies a range of source accounts. In the Criteria Value attribute, separate
the two source accounts with a comma.

Type Description
In Includes a single source account or a list of nonsequential source accounts.
In the Criteria Value attribute, separate the list of source accounts with
commas.
Like Specifies multiple source accounts with wildcards. Use the question mark (?)
wildcard as a placeholder for one character and the asterisk (*) wildcard as a
placeholder for any number of characters.

Grouping Accounts by Source Locations
Example Criteria Value Result

FDM creates a logic account for each source location
1 12300
that FDM finds in the source data file.
FDM creates a summarized logic account for account
12300. The summarized logic account includes all
2 12300;3
source locations that have the same first three
characters.
3 12300;3,4
source locations that have the same three characters
in the source location, starting at position 4.
4 12300;Dept100
source locations. FDM assigns location Dept100 to
this logic account.
Grouping Accounts by Source Locations

Example 1—By default, when the source data file includes multiple source locations,
FDM creates separate logic accounts for each location.
Example 2—You can create a logic account that summarizes multiple source locations
by placing a semicolon after the account and entering a number that corresponds to the
number of characters in the location that you want to group by. FDM assigns these
characters to the location of this logic account. If you have locations 32520 and 32540 in
the source data file, and you group the locations by the first three characters, FDM
assigns 325 to the location of the logic account.
Example 3—You can group multiple source locations that have the same characters
starting at a specified position in the location name. If you have locations 10-325-17 and
10-325-22, and you group the locations by the three characters that start at position 4,
FDM assigns location 325 to the logic account.

Example 4—You can create a logic account that summarizes all source locations from
the source data file. When you place a semicolon after the source account and enter a
text value, such as Dept100, FDM assigns this value to the location of the summarized
logic account.

Selecting Operators and Values

Select the Enter the value,
operator. logic expression, or
logic function.
Selecting Operators and Values

The operator that you select in the Operator column works in tandem with the value in
the Value/Exp column to perform calculations and derive values for the logic accounts.
For example, you can multiply source account values by a decimal value.
You can select the following operators for logic account calculations:
Operator Description
+ Numeric operator to perform addition
- Numeric operator to perform subtraction
* Numeric operator to perform multiplication
/ Numeric operator to perform division
NA Operator that performs no calculation

Operator Description
Fun Operator that executes a logic function that you define
in the Value/Exp column
Exp Operator that executes a logic expression which you
define in the Value/Exp column
When you select a numeric operator, you must enter a numeric value in the Value/Exp

column for the operator to calculate on. With the NA operator, you do not specify a value
in the Value/Exp column, and FDM totals the values of the source accounts that are
listed in the Criteria Value column.
NOTE
Later topics in this lesson contain information about the Fun and Exp operators.

Retrieving Source Account Values
• To retrieve the source account value for source location 325,

FDM category key 13, FDM period 12/31/2008, and source

account 1028, enter the syntax
|325,13,12/31/08,1028|.
• To retrieve the source account value for the current source
location, the FDM category key 14, the current FDM period,
and the source account 1215, enter the syntax
|,14,,1215|.
FDM
category
keys
Retrieving Source Account Values

The Lookup function retrieves source account values from FDM. You can use the Lookup
function in logic functions and logic expressions.
You place the parameters of the Lookup function within pipes (||). The syntax for the
Lookup function is the following:
|source location, FDM category key, FDM period, source account|
To retrieve the source account value for the current source location, FDM category, and
FDM period, you need to include only the source account in the Lookup function. For
example, to retrieve the value of source account 810 for the current source location,
FDM category, and period, enter the syntax |810|.

Assigning Function Return Values

Select the Define a logic
Fun operator. function.
Assigning Function Return Values

The Fun operator executes a logic function that you define in the Value/Exp column. You
typically use logic functions for conditional mapping and complex operations that involve
multiple source accounts. Logic functions enable you to use If statements for conditional
mapping and also enable the use of variables. You can use Lookup functions within logic
functions to retrieve the value of source accounts.
You can use the following parameters in logic functions:
Parameter Description
CurVal Value assigned from the source accounts to the logic account
strLocation Current FDM location in the POV
strCenter Current source location from the source data file

Parameter Description
strCatKey Category key of the current FDM category in the POV
strPerKey Current FDM period in the POV
You must assign the result of a logic function to the keyword Result. For example, you
can look up the value of account 810, multiply the value by .5, and add it to the current
value of the source account:

Result = CurVal + (|810| * .5)
If the logic account calculation results in no return value, FDM assigns a 0 value to the
Result keyword. In this case, FDM skips the calculation and does not create a logic
account for the source location.
For the first example on the slide, FDM retrieves the value of account 1100-104 from the
data file and assigns it to the CurVal parameter. If the value is greater than 0, FDM
assigns the value to logic account L100-104A. If the value is less than 0, FDM skips the
record and does not create the logic account.
For the second example on the slide, FDM retrieves the value of account 1100-104 from
the data file and assigns it to the CurVal parameter. If the value is less than 0, FDM
assigns the value to logic account L100-104L. If the value is greater than 0, FDM skips
the record and does not create the logic account.

Simple Logic Function Examples
Example Operator Value/Exp

If strCatKey=“14” Then Result = CurVal

1 Fun
Else Result = “Skip” End If
If strCenter=“325” Then Result = CurVal * 100
2 Fun
If strPerKey=“12/31/2008”
3 Fun Then Result = CurVal + |4000-100|
If strLocation=“Texas”
4 Fun Then Result = CurVal + |325, 14, 09/30/2008, 1540|
Logic functions containing the strCatKey,

strCenter, strPerKey, and strLocation parameters
Simple Logic Function Examples

Example 1—If 14 is the category key of the FDM category POV, FDM assigns the
current values of the source accounts to the logic account.
Example 2—If the current location in the data file is location 325, FDM assigns the result
of the calculation (CurVal * 100) to the logic account.
Example 3—If the current FDM period POV is December 2008, FDM assigns the result
of the calculation (CurVal + |4000-100|) to the logic account.
Example 4—If the current FDM location POV is Texas, FDM adds a source account from
a different source location, FDM category, and FDM period to the current value of the
logic account.

Creating Logic Expressions
Example Operator Value/Exp

1 Exp |Curval| + |810| + |238|

2 Exp (|Curval| + |325, 14, 12/31/2008, 1630|) * 100
Select the Type the custom

Exp operator. logic expression.
Creating Logic Expressions

The Exp operator executes a logic expression that you define in the Value/Exp column.
Logic expressions are simpler than logic functions and are executed faster than logic
functions. You cannot include If statements or variables in logic expressions.
Logic expressions contain one parameter, CurVal, which you must enclose in pipes. You
do not need to assign the value of the expressions to the Result keyword, as you do in
logic functions.
In the first example on the slide, the logic expression uses the Lookup function to retrieve
the values of accounts 810 and 238, and adds the values to the current logic account
value.
In the second example on the slide, the logic expression uses the Lookup function to add
a source account (1630) from a different location, FDM category, and FDM period to the
current logic account value, and multiplies the result by 100.

Creating Complex Logic Accounts

Complex
logic
group.
Enter the logic account name, or click Zoom

to enter the account name in Zoom Editor.
Creating Complex Logic Accounts

After creating a complex logic group, you define the logic accounts for the group in the
bottom table of the Logic Groups window. Each row in this table represents logic
accounts that you want to calculate based on values from any combination of
dimensions.
The attributes for complex logic accounts are the same as those for simple logic
accounts, except for the Criteria Value attribute and the Include Calc attribute.
FDM processes logic account calculations by the sequence order. With the Include Calc
attribute, you can include previously calculated FDM values in the logic account
calculation, provided that the previously calculated values meet the logic account criteria.

To create complex logic accounts:

1. In the FDM Web client, select MetaData > Logic Groups, and then select a complex logic
group from the top table of the Logic Groups window.
The table for the logic accounts of the selected logic group is

A row is added to the bottom table.
3. In the Item column, enter the logic account name.
4. In the Description column, enter the description for the logic account.
6. In the Criteria Value column, point to the arrow, and click View Complex Logic Account
Criteria.
The Complex Logic Criteria Account dialog box is displayed.
7. Click Add.
A row is added to the criteria table.
8. Double-click in the Dimension column, and select a dimension name from the list.
9. In the other columns, enter or select the dimension criteria.
11. Select File > Close to return to the Logic Groups window.
12. In the bottom table, enter or select the logic account attributes in the Operator,
Value/Exp, Include Calc, Seq, and Exp columns.
14. Repeat steps 2 through 13 for each logic account that you want to create in the logic
group.

Applying Criteria Values

Dimension
names
Applying Criteria Values

You define criteria values for complex logic accounts to define the selection criteria for
dimensions. The logic accounts are derived only from the source data records that meet
the criteria specified for the dimensions. For example, you can select values for accounts
that begin with 15, only for the Texas entity, and for all ICP members.
You create dimension criteria in the Complex Logic Criteria Account dialog box with the
following criteria attributes:
Dimension Source dimension that is enabled for loading; you can select each
dimension only once
Criteria Type Operator (Between, In, or Like) that works with the Dimension and Criteria
Value attributes to determine the dimension members for the logic account
calculation

Criteria Value Criteria that work with the Dimension and Criteria Type attribute to
determine the dimension members for the logic account calculation
Group By Name that overrides the dimension member name in the Import window
Group Level Number that works with the Group By attribute to override the dimension
member name in the Import window

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

Complex Logic Example 1

Complex
logic criteria
Import window

In the Complex Logic Criteria Account dialog box, the Account dimension criteria retrieve
source accounts that begin with 151. The Entity, UD1, and UD2 dimension criteria
specify that source data records for all entity, UD1, and UD2 members are included in the
calculation. The ICP dimension criteria reduces the results to those source data records
that have an ICP value between 1515-107 and 1518-112. Imported source data records
that do not meet all e criteria are excluded from the calculated results.
In this example, FDM calculates one logic account from multiple source data records.
The Group By attribute for the Account, Entity, and ICP dimensions includes hard-coded
values. For every source data record that passes the criteria, FDM replaces the original
imported member with the member that is listed in the Group By attribute.

Complex
logic criteria


The criteria values in this example are the same as in example 1 except for the Group By
and Group Level attributes of the ICP dimension. The Group By value contains ICP-*,
which means that for every source data record that passes the specified criteria, FDM
returns ICP-, followed by the source member. The Group Level value is 7, which causes
FDM to return the first seven characters of the Group By member values.
In this example, FDM generates three logic accounts from the source data records.
Source ICP members 1515-107 and 1515-108 are grouped into a logic account with the
ICP member name ICP-1515-10.

Assigning Logic Groups to Locations
1. In the FDM Web client, select MetaData > Locations and


3. From Logic Group, select the logic group.
4. Click Save.
Assigning Logic Groups to Locations

After you assign logic groups to locations, FDM generates the logic accounts when you
import data files to the data-load locations. You can assign the same logic group to
multiple locations.

Summary

• Describe logic accounts
• Create logic groups
• Create simple logic accounts
• Create complex logic accounts
• Assign logic groups to locations

12-28

L E S S O N
Objectives
1 3
• Add metadata tags

• Create journal templates
• Check in and post journals

Loading FDM Journals

13

Lesson 13 Loading FDM Journals
About FDM Journals
Headcount

imported
from data file
Headcount data loaded from journal template
About FDM Journals

You can make adjustments to imported source data by loading FDM journal templates
into FDM. The journal templates add or replace data records that you want to load to
target systems. After posting the FDM journals, you can verify the adjustments by
displaying the Import window for the current location, period, and category. When you
have all the imported source data and adjustments, you can validate the data and export
it to target systems.
You typically use FDM journal templates for the following types of adjustments:
• GAAP adjustments to general ledger files
• Account breakdown into roll-forward accounts (Beginning Balance, Additions,
Disposals)
• Supplemental data entry (Head Count, Ratios)

These changes are usually adjustments that you could not make in the general ledger of
the original system because of statutory requirements or general ledger limitations.
NOTE
You should make as many entries as possible in the original source system to
enhance the data-load process and reduce the amount of manual work in FDM.

Creating Journal Templates

Where
to load
the data
Hidden
metadata
rows Data to
load
Creating Journal Templates

Journal templates are Excel spreadsheets that you format as journal entry input screens
with metadata tags and journal entries. You use the metadata tags to specify where to
load the journal entries. You add journal entries to specify the dimensions and
adjustment amounts that you want to load. For the example on the slide, you want to
load adjustments to four headcount accounts for the Indiana location, the FDM_Actual
category, and the 1/31/2008 period.
FDM provides a starting journal template (Journal.xls). You can find the template in the
application’s Outbox\Templates directory, or you can access it in the FDM Web client
from the Tools > Templates menu. Any user with access to Excel can create journal
templates.

The Journal.xls file has a range name that includes all metadata tag rows and data rows.
The metadata tags are the first five rows of the range, and are hidden between rows 15
and 23 of the spreadsheet example. You must enter all data rows between the two red
lines in the range. There is no limit to the number of data rows that you import into FDM,
as long as the rows are between the two red lines.
Guidelines for journal templates:

• You can insert and delete rows between the red lines.
• You should not cut and paste rows in the template.
• You can use formulas.
• You can have more than one journal template in a Journal.xls file, as long as each
template has a unique range name.

Adding Metadata Tags

Metadata tags
are in the first
five rows of
the range.
The upsJournal range is rows 16 through 26.

The journal template must have a range name that contains the metadata tags and
journal entries. This range name must begin with the prefix ups. For the example on the
slide, the range name, upsJournal, includes the metadata tags in rows 16 through 20 and
the data in rows 23 through 26.
You must keep the metadata tags in a specific tabular format. The metadata row order is
important, but the column order is not. When you prepare journal templates, the first five
rows of the range must contain the metadata tags for the data rows.

The following table describes the metadata tags and their required positions in the
journal template:
Row Tag Description

1 Journal ID Journal name. Place this tag in the Account column.
1 Location Location where you want to load the journal. Place this tag in the
Amount column.

2 Category Valid FDM category where you want to load the journal. Place this
tag in the Amount column.
3 Period Valid FDM period where you want to load the journal. Place this
tag in the Amount column.
4 Load Method Journal load method where you specify whether to append or
replace the journal data. Place this tag in the Amount column
5 Dimension Dimensions that specify where you want to load the journal. Place
these tags in separate columns.
Load Method Tags

You can append or replace data when loading the journal entries.
• Append—Appends data to an existing journal with the same journal ID. If journal
entries exist with the same journal ID within the same POV, FDM appends the journal
entries in the Import window.
• Replace—Replaces data in an existing journal with the same journal ID. If journal
entries exist with the same journal ID within the same POV, FDM replaces the old
journal entries with the new journal entries.
There are four load method tags, as shown in the following table. The AZ and RZ load
methods work the same as the append and replace load methods, except that FDM
suppresses all zero value amounts.
Load Method Valid Tag

Append Journal A, Append
Replace Journal (default) R, Replace
Append Journal - Zero Suppress AZ
Replace Journal - Zero Suppress RZ

Dimension Tags
You place dimension tags in separate columns in the fifth row of the range. The tags
define the dimensions that you want to load in the journal entries. For the example on the
slide, you load the Account, Center (location), Amount, and Description dimensions. The
Account and Center dimensions are the names of the accounts and centers from the
source system or the target system.
You can include the following dimensions in journal templates:

Dimension Valid Tags
Account (required) A, Account, SrcAcctKey
Center (required) C, Center, SrcCenterKey
Description (optional) D, Description, SrcAcctDesc
IC Counter Party (optional, except for Financial I, IC, ICCoParty
Management target systems)
User Defined 1 through User Defined 20 (required 1, UD1, UserDefined1 through
only if they are used by the target systems)
20, UD20, UserDefined20
Amount (required) V, Amount, SrcAmount

Loading Journal Templates

Method 1:
Upload File
tab
Method 2:
Select File
From Inbox
tab
Loading Journal Templates

You load journal templates into FDM to post the journal entries to the data that you
imported from data files.
To load journal templates:

1. In the FDM Web client, select the location, category, and period POV for which you
want to load the journal template.
2. Select Activities > Journal.
The Journal window is displayed.
• On the Upload File tab, browse to select the journal template, click Open, and then
click Check-In.

• On the Select File From Inbox tab, click Select File, select the journal template from
the appropriate Inbox directory or subdirectory, and then click OK.
FDM compares the template’s location, period, and category with
the corresponding dimensions in the POV. If the check is
successful, FDM displays a Post button in the Journal window.
4. Click Post.

FDM loads the journal entries to the data that you imported from
data files.

Checking In Journals

Successful check-in.
FDM displays the

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

Posting Journals

Headcount data loaded from journal template.
Posting Journals
When you post journals, FDM either appends or replaces the data in the Import window
based on the load method that you specified in the template. You must successfully
check in a journal template before you can post it.
NOTE
Administrators and end users can post journal templates only to the Global POV,
unless they turn off the POV Lock option.

Summary

• Create journal templates
• Add metadata tags
• Check in and post journals

13-14

L E S S O N 1 4
Loading Data with Multiload Files 14

Objectives
• Create multiload Excel templates
• Create multiload text files
• Load multiload files into FDM
• Execute Workflow tasks for multiload files
• View data-load errors
Lesson 14 Loading Data with Multiload Files
About Multiload Files

Metadata
tags
Data for multiple time periods
About Multiload Files

Multiload files are text files or Excel templates that you use to load data into multiple
periods, categories, and locations. The files require metadata tags that FDM uses to
interpret the data that you want to load. The files also contain data rows that you want to
import into FDM.
The data columns in multiload files must contain a value. The data columns must have a
zero in every field that does not contain a value to load. If you include blank values in
data columns, FDM cannot successfully complete the multiload process.
You typically use multiload files for the following tasks:
• Plan data collection (budget, forecast)
• Historical data loading
• Administrator data maintenance

During the multiload process, FDM users import data into FDM and load the data to
target systems. FDM users can load multiload files to all periods and categories, but only
to locations to which they have access. As the administrator, you can load multiload files
to all periods, categories, and locations.
NOTE
You can load a maximum of 12 periods with multiload text files, and you can load
an unlimited number of periods with multiload Excel templates.

Creating Multiload Excel Templates

Budget-12-Period.xls
sample template
Hidden
metadata
rows
Budget-12-Period_All_Dims.xls sample template
Creating Multiload Excel Templates

To create multiload Excel templates, you must define the metadata tags that FDM uses
to interpret the data in the template. The metadata tags define the columns that you
import into FDM and load to target systems.
FDM provides starting multiload Excel templates—Budget-12-Period.xls and Budget-12-
Period_All_Dims.xls. You can find the templates in the application’s Outbox\Templates
directory, or you can access them in the FDM Web client from the Tools > Templates
menu. Any user with access to Excel can create multiload templates.
Both sample templates have a range name that includes the metadata tag rows and data
rows. The metadata tags are the first five rows of the range, and are hidden between
rows 9 and 16 in the templates. You must enter data rows between the two red lines in
the range. There is no limit to the number of data rows that you can import into FDM, as
long as the rows are between the two red lines.

Guidelines for multiload Excel templates:

• You can insert and delete rows between the red lines.
• You should not cut and paste rows in the template.
• You can use formulas.


The Metadata tags
upsBudget are in the first
range is rows five rows of
10 through 24. the range.

Multiload templates must have a range name that contains the metadata tags,
dimensions, and amounts that you want to import. Range names must begin with the
prefix ups. For the example on the slide, the range name, upsBudget, includes the
metadata tags in rows 10 through 14 and the data in rows 16 through 24.
You must keep the metadata tags in a specific tabular format. The metadata row order is
important, but the column order is not. When you prepare multiload templates, the first
five rows of the range must contain the metadata tags for the data rows.

The following table describes the metadata tags and their required positions in multiload
Excel templates:
Row Tags Description

1 Location FDM locations where you want to load the data. Place these tags
in Amount columns.
2 Category FDM categories where you want to load the data. Place these

tags in Amount columns.
3 Period FDM periods where you want to load the data. Place these tags in
Amount columns.
4 Load Method Data-load methods for FDM and the target system; control tags
vary by target system. Place these tags in Amount columns.
5 Dimension Dimensions that specify where you want to load the data. Place
these tags in separate columns.
Adding Load Control Tags

You control the load methods for both FDM and the target system with the load control
tags in row 4. The tags that you specify depend on the target system. Target systems do
not require all of the tags. The following table lists the 10 load control tags that FDM
supports:
Load Tag
Number Load Control Tag Name Description
1 FDM Load Method FDM data-load method
2 Target System Load Method Target system data-load method
3, 4, and 5 List Box 1, List Box 2, and List Box 3 Varies by integration block
6 Check Box Calc Data calculation (Y/N)
7, 8, and 9 Check Box 1, Check Box 2, and Varies by integration block
Check Box 3
10 Data View YTD, Periodic, or Qtr Year-to-Date
data view


for Financial Management
• Place the load control tags in row 4 of the range.
• Separate the load control tags with commas.

• Type commas as placeholders for default tag values and
for unused tags.
Load control tags
Adding Load Control Tags for Financial Management

The following table lists the tags that you use to control the data-load method for
Financial Management target systems:
Load Tag Number and Name Option Valid Tags

1—FDM Load Method Append A
Replace (default) R
Append - Zero Suppress AZ
Replace - Zero Suppress RZ
2—Financial Management Load Merge M, Merge
Method
Replace R, Replace
Accumulate A, Accumulate


3—Financial Management Load Load 0, Load
Process
Scan 1, Scan
7—Accumulate in File Yes Y, Yes, True, T
No N, No, False, F

8—File has Share Data Yes Y, Yes, True, T
No N, No, False, F
10—Data View Year-to-Date (default) Y, YTD, Year-To-Date
Periodic P, Per, Periodic
Qtr Year-To-Date Q, QYTD, Qtr
Half-Year H, HYTD, Half-Year
If you do not enter values for tags 2, 3, 7, and 8, the values default to the data-load
options that you define in the FDM application’s integration settings.
NOTE
You do not use load tags 4, 5, 6, and 9 with Financial Management target
systems. You must insert a comma as a placeholder to accommodate these
unused tags.
When you include the Data View tag in the header, FDM loads each data row with the
same data view. As an alternative method, you can create a Data View column in row 5
and specify a Data View tag for each row. If you do not define a Data View tag in the
header, and no Data View column exists, FDM sets the default data view to YTD.
Examples of Financial Management Load Control Tags

In the following example, you specify a valid tag for each load control tag item. You must
use commas as placeholders for the load tags that Financial Management does not
use—tags 4, 5, 6, and 9. With this syntax you define the replace load method for FDM,
the merge load method for Financial Management, and the Load process. You also
specify that data is accumulated in the file, that the load file does not contain share data,
and that the data view is YTD.
R,M,0,,,,Y,N,,YTD

In the following example, you define only the FDM load method tag (A-append) and the
Financial Management load method tag (M-merge). The Data View tag defaults to YTD.
All other tags default to the load settings that you define in the application’s integration
settings. You do not need trailing commas after the last supplied argument.
A,M


for Hyperion Enterprise
• Place the load control tags in row 4 of the range.
• Separate the load control tags with commas.

• Type commas as placeholders for default tag values and
for unused tags.
Load control tags
Adding Load Control Tags for Hyperion Enterprise

The following table lists the tags that you use to control the data-load method for
Hyperion Enterprise target systems:

1—FDM Load Method Append A
Replace (default) R
Append - Zero Suppress AZ
Replace - Zero Suppress RZ
2—Hyperion Enterprise Load Method Merge M, Merge
Replace R, Replace
Accumulate A, Accumulate


3—Data View Category C, Cat, Category
Periodic P, Per, Periodic
Year-To-Date Y, YTD, Year-To-Date
4—Scale None N, -1, None
Thousands TH, 3, Thousands

Millions ML, 6, Millions
Billions B, 9, Billions
7—Zero No Data Yes Y, Yes, T, True
No N, No, F, False
For a complete list of the Scale tag options, see Oracle Hyperion Financial Data Quality
Management, Fusion Edition Release 11.1.1 Administrator’s Guide.
If you do not enter values for tags 2, 3, 4, and 7, the values default to the data-load
options that you define in the FDM application’s integration settings.
NOTE
You do not use load tags 5, 6, 8, 9, and 10 with Hyperion Enterprise systems. You
must insert a comma as a placeholder to accommodate these unused tags.
Examples of Hyperion Enterprise Load Control Tags (Multiload Excel File)

In the following example, you specify a valid tag for each load control tag item. You must
use commas as placeholders for the load tags that Hyperion Enterprise does not use—
tags 5 and 6. With this syntax, you define the replace load method for FDM, the merge
load method for Hyperion Enterprise, and the Category data view. You also specify the
scale as None and the Zero No Data option.
R,M,C,N,,,Y
In the following example, you define only the FDM load method tag (A-append) and the
Hyperion Enterprise load method tag (M-merge). All other tags default to the load
settings that you define in the application’s integration settings. You do not need trailing
commas after the last supplied argument.
A,M

Adding Dimension Tags
• Place the dimension tags in row 5 of the range.

• Place the dimension tags in separate columns.

Dimension tags
Adding Dimension Tags

You place dimension tags in separate columns in the fifth row of the range. The tags
define the dimensions for the data that you want to load. For the first example on the
slide, you specify tags for the Account, Center (location), and Description dimensions, as
well as for two Value columns. For the second example on the slide, you specify tags for
the Account, Center (location), Description, View, Intercompany, and custom
dimensions, as well as two Value columns.
Accounts in multiload files can be existing accounts in the location mapping, or they can
be accounts that you must map during the Validate process.
When you load memos in a multiload file, FDM enters the same memo specified in the
row for every period.

You can include the following dimension tags in multiload files:
Dimension Valid Tags

Account (required) A, Account, SrcAcctKey
Center (required) C, Center, SrcCenterKey
Description (optional) D, Description, SrcAcctDesc

Data View (optional) W, DV, DataView
Accepted values:
Y, YTD, Year-To-Date
P, Per, Periodic
Q, QYTD, Qtr
H, HYTD, Half-Year
IC Counter Party (optional) I, IC, ICCoParty
User Defined 1 through User Defined 8 1, UD1, UserDefined1
(optional)
2, UD2, UserDefined2, and so on
Memo ID (optional except when using M1
Memo Detail)
Memo Detail (optional) M2
Amount (required) V, Amount, VZ (zero suppress),
AmountZ (zero suppress)

Creating Multiload Text Files

Metadata
tags
Data for
multiple time
periods
Creating Multiload Text Files

You can also load data into multiple periods by using multiload text files. These files must
include the metadata tags in the first six rows, followed by the data rows. You must keep
the metadata tags in a specific tabular format. The metadata row order is important, but
the dimension tag order is not.
The following table describes the metadata tags and their required positions in multiload
text files:
Row Tag Description

1 Location FDM location where you want to load the data.
2 Category FDM category where you want to load the data.
3 Starting Period FDM period where you want to load the data.

Row Tag Description

4 Number of Periods Number of periods that you want to load. FDM uses this tag in
combination with the Starting Period tag to derive the periods
of data to load.
5 Load Control Data-load methods for FDM and the target system. Control
tags vary by target system.
6 Dimension Dimensions that specify where you want to load the data. A

valid delimiter must separate each dimension.
You can use the same load control tags and dimension tags for multiload text files as for
multiload Excel templates. You separate the load control tags and dimension tags with
delimiters. Valid delimiters include commas, semicolons, pipes, tabs, and exclamation
points. You must use the same delimiter in row 6 (to separate dimension tags) and in the
data rows (to separate dimension members and data values).
For the multiload text file on the slide, the first six lines contain the metadata tags, and
the last seven lines contain the account name, account description, and data values. The
file defines the data that you want to load for the Texas location, the FDM_Budget
category, and the January through April time periods. With the load control tags for
Financial Management (R,M,0), you specify that you want to replace the data in FDM,
merge the data in the Financial Management target system, and load rather than scan
the data.
Depending on the amount of data, FDM processes multiload text files at a much faster
rate than multiload Excel templates. FDM creates a single load file and consolidates a
range of periods when processing a multiload text file. However, when processing a
multiload Excel template, FDM creates separate load files for each period and
consolidates one period at a time.

Loading Multiload Files

Method 1:
Upload File
tab
Method 2:
Select File
From Inbox
tab
Loading Multiload Files

You load multiload files into FDM to load data to multiple periods, categories, and
locations. FDM does not require the POV on the FDM desktop to match the POV in the
multiload file.
To load multiload files:

1. In the FDM Web client, select Activities > Multi-Load.
The Multi-Load window is displayed.
• On the Upload File tab, browse to select the file, click Open, and then click Check-In.

• On the Select File From Inbox tab, click Select File, select the file from the
appropriate Inbox directory or subdirectory, and then click OK.
FDM displays the POV for the locations, categories, and periods
that you want to load. FDM also displays the Status, Import,
Validate, Export, Consolidate, and Check buttons.
3. Click Status.

FDM expands the POV rows and displays the status of the Import,
Validate, Export, Load, and Check tasks.
4. Click Import.
If the task is completed successfully, FDM imports the data and
displays a check mark next to the Import task.
5. Click Validate.
If the task is completed successfully, FDM validates the data and
displays a check mark next to the Validate task.
6. Click Export.
If the task is completed successfully, FDM exports the data to the
target system and displays a check mark next to the Export and
Load tasks.
7. Optional: Click Consolidate to consolidate the data in the target system.
8. Click Check.
FDM checks the data and, if the task is completed successfully,
displays a check mark next to the Check task.

Checking In Multiload Files

Successful check-in.
FDM displays these

buttons after a
Errors during check-in.
successful check-in.
Checking In Multiload Files

When you check in multiload files, FDM processes the metadata tags in the multiload
file, and checks that the POV for each period in the file matches a valid POV in FDM. If
the POV is valid, FDM displays the POV for each period in the File Contents area of the
Multi-Load window. If the POV is invalid, FDM displays errors.
You must check in files that you select on the Upload File tab. FDM automatically checks
in files that you select on the Select File From Inbox tab.
For the check-in error on the slide, the FDM_Bud category in the multiload file does not
match a valid FDM category. You must change the category in the file to a valid FDM
category and repeat the check-in process.

Executing Workflow Tasks for Multiload Files
Workflow tasks

Successful tasks
Executing Workflow Tasks for Multiload Files

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

Viewing Data-Load Errors

Click [Load Error].
Review the error log file.
Viewing Data-Load Errors

For the example on the slide, FDM encounters a load error while loading data to the
target system for the February time period. When you click [Load Error], FDM displays a
link to the error log file in the Processing Details area of the window. You must review the
error log and fix the errors before you can continue with the load process.

Summary

• Create multiload Excel templates
• Create multiload text files
• Load multiload files into FDM
• Execute Workflow tasks for multiload files
• View data-load errors

FDQM SG1

Uploaded by

Copyright:

Available Formats

You might also like

FDQM SG1

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

FDQM SG1

Uploaded by

Copyright:

Available Formats

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY.

COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED

Oracle University and Businessmind Colombia SA use only

Lea Jensen Disclaimer

This document contains proprietary information and is protected by copyright and

Oracle University and Businessmind Colombia SA use only

Publisher U.S. GOVERNMENT RIGHTS

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

Oracle University and Businessmind Colombia SA use only

Oracle University and Businessmind Colombia SA use only

iv Financial Data Quality Management 11.1.1 Administration

Oracle University and Businessmind Colombia SA use only

• Keyboard shortcuts are displayed as follows: Ctrl+Enter

Financial Data Quality Management 11.1.1 Administration v

Financial Data Quality Management 11.1.1 Administration

Oracle University and Businessmind Colombia SA use only

Module 1: Introduction to FDM

Lesson 1: Product Orientation

Lesson 2: Navigating FDM

Changing the POV Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Oracle University and Businessmind Colombia SA use only

Module 2: Building FDM Applications

Lesson 3: Creating FDM Applications

Lesson 4: Integrating Applications

viii Financial Data Quality Management 11.1.1 Administration

Integrating Hyperion Enterprise Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Oracle University and Businessmind Colombia SA use only

Module 3: Building the Workflow Process

Lesson 6: Setting Up Mapping Tables

Financial Data Quality Management 11.1.1 Administration ix

Processing Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Oracle University and Businessmind Colombia SA use only

Lesson 7: Building Import Formats

Lesson 8: Loading Data

x Financial Data Quality Management 11.1.1 Administration

Importing Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Oracle University and Businessmind Colombia SA use only

Lesson 9: Building Validation Rules

Financial Data Quality Management 11.1.1 Administration xi

Checking Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

Lesson 10: Setting Up Validation Entities

Oracle University and Businessmind Colombia SA use only

Lesson 11: Processing Batch Files

Module 4: Creating Additional Loading Options

Lesson 12: Creating Logic Accounts

xii Financial Data Quality Management 11.1.1 Administration

Lesson 13: Loading FDM Journals

Oracle University and Businessmind Colombia SA use only

Lesson 14: Loading Data with Multiload Files

Module 5: Enhancing FDM

Lesson 15: Setting Up Security

Financial Data Quality Management 11.1.1 Administration xiii

Migrating Users to Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-21

Lesson 16: Working with Financial Controls

Oracle University and Businessmind Colombia SA use only

Module 6: Creating Scripts

Lesson 17: Working with Import Scripts

xiv Financial Data Quality Management 11.1.1 Administration

Applying the Right Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17