hyperion fdm

of 279 /279
Hyperion ® System 9 Financial Data Quality Management Administrator Training Guide WebLink Version 8.3, 8.31, and Hyperion System 9 Financial Data Quality Management Version 9.2.0 Hyperion Financial Management® (HFM) & Hyperion Enterprise®

Author: vantuong

Post on 21-Dec-2016

243 views

Category:

Documents


1 download

Embed Size (px)

TRANSCRIPT

  • Hyperion System 9 Financial Data Quality

    Management

    Administrator Training Guide

    WebLink Version 8.3, 8.31, and Hyperion System 9 Financial Data Quality Management Version 9.2.0

    Hyperion Financial Management (HFM)& Hyperion Enterprise

  • 2000 2006 - Hyperion Solutions Corporation. All rights reserved. Hyperion, the Hyperion logo and Hyperions product names are trademarks of Hyperion. No portion hereof may be reproduced or distributed in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the licensees personal use, without the express written permission of Hyperion. This software is licensed according to the conditions set forth in your Hyperion software license agreement.

    Hyperion, LedgerLink, Hyperion Enterprise, and Essbase are registered trademarks of Hyperion Solutions Corporation.

    Hyperion Solutions, Hyperion Planning, and Hyperion Financial Management are trademarks of Hyperion Solutions Corporation.

    Citrix is a registered trademark of Citrix Systems Inc.

    Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries.

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

  • i

    Table of ContentsHow to Use this Guide ............................................................................................................................... v

    Organization................................................................................................................................................................. vInstructor.Demonstrations........................................................................................................................................... viWalkthroughs............................................................................................................................................................... viExercises..................................................................................................................................................................... vi

    Section A Hyperion FDM BasicsModule 1: Overview of Hyperion FDM

    Introduction ............................................................................................................................................. 1-1Definition of a Hyperion FDM Application ............................................................................................ 1-2Hyperion FDM Application Architecture ............................................................................................... 1-2

    Data.Directory............................................................................................................................................................1-2Inbox.Directory..........................................................................................................................................................1-3Outbox.Directory........................................................................................................................................................1-3Reports.Directory.......................................................................................................................................................1-4

    Managing Hyperion FDM Applications ................................................................................................. 1-5Opening.Applications.................................................................................................................................................1-5Creating.Applications.................................................................................................................................................1-7Removing.Applications..............................................................................................................................................1-9Adding.Applications.................................................................................................................................................1-10

    End User Process ................................................................................................................................. 1-13

    Module 2: Hyperion FDM NavigationHyperion FDM Desktop .......................................................................................................................... 2-1Point of View (POV) ................................................................................................................................ 2-2

    POV.Mode.Local.vs..Global......................................................................................................................................2-3Changing.POV.Mode.................................................................................................................................................2-3Setting.Location.POV................................................................................................................................................2-3Setting.Category.POV...............................................................................................................................................2-4Setting.Period.POV...................................................................................................................................................2-4POV.Search...............................................................................................................................................................2-4Locking.and.Unlocking.the.System...........................................................................................................................2-5How.a.Users.Default.Point-of-View.is.Determined...................................................................................................2-5

    Module 3: Building a Hyperion FDM Application OverviewIntroduction ............................................................................................................................................. 3-1Pre-Implementation Data Requirements .............................................................................................. 3-1

    Section B: Building a Hyperion FDM ApplicationModule 4: Creating a Hyperion FDM Application

    Overview .................................................................................................................................................. 4-1a..Log.onto.Hyperion.FDM.Using.the..Option..............................................................................4-2b..Complete.the.New.Application.Dialog.Box............................................................................................................4-2

    Module 5: Integrate with the Target ApplicationIntegration Overview .............................................................................................................................. 5-1

    a..Import.the.Target.System.Adaptor.........................................................................................................................5-2b...Register.the.Adaptor.............................................................................................................................................5-4c. Add Machine Profile...............................................................................................................................................5-5d..Verify.Application.Settings.....................................................................................................................................5-6

  • ii

    e..Update.Integration.Settings...................................................................................................................................5-7f..Update.DCOM.Settings..........................................................................................................................................5-9g..Map.Hyperion.FDM.Dimensions.to.Target.Dimensions.......................................................................................5-11i..Test.the.Integration.from.within.the.Web.Client....................................................................................................5-13

    Import the Standard Reports ............................................................................................................... 5-15Import the Standard Templates ........................................................................................................... 5-16

    Module 6: Populating Control TablesControl Tables Overview ........................................................................................................................ 6-1

    a..Open.the.Control.Tables.Screen...........................................................................................................................6-2b..Add.the.Periods.....................................................................................................................................................6-3c..Add.the.Categories................................................................................................................................................6-4d..Verify.the.Currency.Codes.....................................................................................................................................6-6

    Module 7: Setting Up LocationsHyperion FDM Locations Overview ...................................................................................................... 7-1

    Hyperion.FDM.Location.Types..................................................................................................................................7-1a..Open.the.Locations.Screen...................................................................................................................................7-2b..Add.New.Location..................................................................................................................................................7-3c..Apply.Attributes.to.the.New.Location.....................................................................................................................7-4

    Module 8: Importing Mapping TablesMaps Overview........................................................................................................................................ 8-1

    a. Define Map Dimensions........................................................................................................................................8-2b..Set.the.Appropriate.Dimension.Labels..................................................................................................................8-3c..Open.the.Maps.Screen..........................................................................................................................................8-5Map.Types.................................................................................................................................................................8-5Building.Maps.in.MapLoader.....................................................................................................................................8-9d1..Import.Maps.......................................................................................................................................................8-10d2..Copy.Mapping.Tables........................................................................................................................................8-15d3..Assign.a.Parent.Map.........................................................................................................................................8-16

    Additional Hyperion FDM Mapping Features and Information ......................................................... 8-17Conditional.Mapping................................................................................................................................................8-17

    Module 9: Build Import FormatsOverview of Import Formats .................................................................................................................. 9-1

    a..Create.a.New.Import.Group..................................................................................................................................9-2b. Define Fields for the Import Group........................................................................................................................9-3c..Assign.Import.Formats.........................................................................................................................................9-11

    Advanced Import Expressions ............................................................................................................ 9-14Sign.9-15DRCRSplit.=.(Split.Debit.and.Credit.Columns)........................................................................................................9-16Fill.=.(Trailing.Fill)....................................................................................................................................................9-19Fill=EuroToUS..........................................................................................................................................................9-19FillL.=.(Leading.Fill).................................................................................................................................................9-22Factor.=.(Value).......................................................................................................................................................9-24NZP.(No.Zero.Suppress).........................................................................................................................................9-26Expression.Stacking.and.Processing.Order............................................................................................................9-27

    Module 10: Test Data LoadingData Loading Overview ........................................................................................................................ 10-1

    a..Import.Source.File...............................................................................................................................................10-2b..Validate.the.Mapping...........................................................................................................................................10-3c..Export.Mapped.File.to.Target.System..................................................................................................................10-7

  • iii

    Section C Enhancing the ApplicationModule 11: Validation Rules and Reports

    Validation Rules and Reports Overview ............................................................................................. 11-1a. Define Validation Rule Groups............................................................................................................................11-2b. Define Validation Rules.......................................................................................................................................11-3c..Attach.Validation.Rules.to.a.Location................................................................................................................11-15d..Check.Validation.Rules......................................................................................................................................11-16

    Module 12: Validation EntitiesOverview ................................................................................................................................................ 12-1

    a..Create.Validation.Entity.Group............................................................................................................................12-2b. Define Validation Entities.....................................................................................................................................12-3c..Attach.Validation.Entity.to.a.Location...................................................................................................................12-7

    Section D Additional FunctionalityModule 13: Logic Accounts

    Overview ................................................................................................................................................ 13-1Creating Logic Groups ......................................................................................................................... 13-2

    Logic.Type...............................................................................................................................................................13-2Logic.Group.Security...............................................................................................................................................13-2Simple.Logic.Accounts............................................................................................................................................13-3Assigning.Function.Return.Values...........................................................................................................................13-6Hyperion.FDM.Lookup.Function..............................................................................................................................13-8Creating.Complex.Logic.Accounts...........................................................................................................................13-8

    Module 14: JournalsUsing a Journal Template .................................................................................................................... 14-1Defining a Journal Template ................................................................................................................ 14-1Metadata Structure ............................................................................................................................... 14-2

    Row.1.(Journal.ID.&.Location.Tag)..........................................................................................................................14-2Row.2.(Hyperion.FDM.Category.Tag).....................................................................................................................14-2Row.3.(Hyperion.FDM.Period.Tag)..........................................................................................................................14-2Row.4.(Load.Method.Tag).......................................................................................................................................14-2Row.5.(Dimension.Tags).........................................................................................................................................14-2

    Module 15: MultiloadDefinition of a Multiload File ................................................................................................................ 15-1

    Text.File.Multiload.vs..Excel.Multiload.....................................................................................................................15-1Defining a Multiload Excel Template........................................................................................................................15-1Metadata.Tags.Structure.........................................................................................................................................15-2

    Process Summary .............................................................................................................................. 15-12

    Section E Hyperion FDM AdministrationModule 16: Key Tips and Navigation

    Sorting Records .................................................................................................................................... 16-1Finding Records ................................................................................................................................... 16-2Filtering Records .................................................................................................................................. 16-3

    Shortcut.to.Deleting.All.Records.on.the.Import.Screen...........................................................................................16-4Drilling Up .............................................................................................................................................. 16-5

    Show.Attributes........................................................................................................................................................16-5Show.Conversion.Rules..........................................................................................................................................16-5

  • iv

    Show.Archive.Information........................................................................................................................................16-6Open.Source.Document..........................................................................................................................................16-6Open.Processing.Log..............................................................................................................................................16-7Restore.Source.Document......................................................................................................................................16-7

    Drilling Down ......................................................................................................................................... 16-8Drilling Up on a Drill-Down .................................................................................................................. 16-8Searching Control Trees ...................................................................................................................... 16-9

    Module 17: Hyperion FDM SecuritySecurity Overview................................................................................................................................. 17-1

    Levels.of.Security....................................................................................................................................................17-1User Security......................................................................................................................................... 17-2

    Setting.up.User.Security..........................................................................................................................................17-2Deleting.a.User........................................................................................................................................................17-4Changing.Target.System.Password........................................................................................................................17-6Modifying.a.Users.Rights........................................................................................................................................17-7

    Object Maintenance .............................................................................................................................. 17-9Report.Groups.Security.........................................................................................................................................17-12

    Module 18: Financial ControlsFinancial Controls ................................................................................................................................ 18-1

    Controls.Groups......................................................................................................................................................18-1Sections...................................................................................................................................................................18-4Questions................................................................................................................................................................18-6Importing.Questions.from.Excel..............................................................................................................................18-9Effective.Date........................................................................................................................................................18-11Recycle.Bin............................................................................................................................................................18-11Question Profiles...................................................................................................................................................18-14Reviewers.and.Proxy.............................................................................................................................................18-17Submitter.and.Proxy..............................................................................................................................................18-17Risk.Flag.Level......................................................................................................................................................18-17Process.Explorer...................................................................................................................................................18-20Adding.Memos.and.Attaching.Documentation.......................................................................................................18-21Certification Process..............................................................................................................................................18-26Answering.Questions.............................................................................................................................................18-26Application.Settings...............................................................................................................................................18-28

    Module 19: Map ConverterOverview ................................................................................................................................................ 19-1

  • Section A Section B Section C Section D Section E

    How to Use this GuideOrganizationThis manual is divided into five main sections: Hyperion FDM Basics, Building a Hyperion FDM Application, Enhancing Your Application, Additional Functionality, and Hyperion FDM Administration. Each of these sections is further divided into modules.

    Section A Hyperion FDM BasicsModule 1: Overview of Hyperion FDMModule 2: Hyperion FDM NavigationModule 3: Building a Hyperion FDM Application Overview

    Section B Building a Hyperion FDM Application

    Module 4: Create a New Hyperion FDM ApplicationModule 5: Integrate with Target ApplicationModule 6: Populate Control TablesModule 7: Set up LocationsModule 8: Build and/or Import MapsModule 9: Build Import FormatsModule 10: Test Data Loading

    Section C Enhancing the ApplicationModule 11: Validation Rules and ReportsModule 12: Validation Entities

    Section D Additional FunctionalityModule 13: Logic AccountsModule 14: JournalsModule 15: Multiload

    Section E Hyperion FDM AdministrationModule 16: Key Tips and NavigationModule 17: Hyperion FDM SecurityModule 18: Financial ControlsModule 19: Map Converter

    This diagram illustrates the page format. All right-side pages include navigation information (current section number, module number, and page number).

  • Hyperion FDM Administrator Training Guide

    i

    Instructor DemonstrationsThe instructor will demonstrate a feature or function on the screen. Instructor demonstrations are written in a numbered format procedure, and can be identified by the icon to the left.

    WalkthroughsWalkthroughs are like instructor demonstrations in which the students also participate. The instructor and student work through a function or procedure simultaneously. Walkthroughs can be identified by the icon on the left.

    ExercisesExercises are identified by the pushup icon. Some exercises are specific to Hyperion

    Enterprise. Those are designated by the HE icon ( ). HFM-specific exercises are

    designated by the HFM icon ( ). Some exercises can be completed in either application, and will contain both icons.

  • Section A Hyperion FDM Basics

    In this Section:

    Module 1: Overview of Hyperion FDM

    Module 2: Hyperion FDM Navigation

    Module 3: Building a Hyperion FDM Application Overview

  • Module 1: overview of Hyperion fdM

  • 1-1

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    IntroductionHyperion System 9 Financial Data Quality Management (Hyperion FDM) is an advanced Data Transformation Management (DTM) solution. Hyperion FDM provides a single, systematic process for loading source data from disparate systems into target analytical applications. The Hyperion FDM process provides data visibility, integrity, and verification.

    Hyperion FDM features and benefits include the following:Acting central repository of all source financial dataDrill-down audit trailAbility to archive source files, error logs, and load filesInternal controls assessment and certification feature aids in compliance with sections 302 and 404 of the Sarbanes-Oxley ActCorporate-wide process monitoringAbility to import source data from any formatted text file or data sourceMultiple dimension mapping and validating capabilityData validation and quality checkingError identification and notificationConsolidation of target system dataValidation and reporting on target system dataLoad adjustments capability through Excel journalsBudget data loading for multiple periodsAdvanced reporting and audit functionsLights out batch loading (requires batch loader license)Support for unlimited concurrent usersZero footprint Web deploymentSQL & Oracle Database support

  • Hyperion FDM Administrator Training Guide

    1-2

    Definition of a Hyperion FDM ApplicationA Hyperion FDM application consists of a Relational Database Management System (RDBMS) database and directories that contain all the transactional data, metadata, reports, and other files that are used when integrating with an individual target system application.

    A new Hyperion FDM application is required for each target system application that Hyperion FDM will be loading. Valid target systems include Hyperion Enterprise, Hyperion Financial Management, Hyperion Financial Planning, Hyperion Essbase, and all other consolidation, reporting, planning, and analytical applications. There is no limit to the number of Hyperion FDM applications that can be created.

    Hyperion FDM Application ArchitectureA Hyperion FDM application contains a Data, Inbox, Outbox, and Reports directories. Figure 1-1 illustrates the directories and directory structure that are created when a new Hyperion FDM application is created.

    Figure 11: Hyperion FDM Application Data Structure

    The following topics provide more information about each of the folders in the application directory:

    Data DirectoryThe Data directory contains a Scripts sub-directory where Hyperion FDM scripts are stored. The Data directory is also where Hyperion FDM archives all source files, journals, multiload files, logs, output data files, and attachments.

  • 1-3

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    Scripts DirectoryThe Scripts directory is where all Hyperion FDM script files are stored and contains sub-directories for each type of script.

    Custom Directory contains script files that can be executed through a Hyperion FDM custom menu created in the Menu Maker form.

    Event Directory contains script files that are executed when a particular Hyperion FDM event executes. All scripts contained in this directory will be named for the event in which they correspond.

    Import Directory includes import scripts that are created when defining import formats. Import scripts are executed during the source file import process.

    Inbox DirectoryThe Inbox directory is the default directory used by Hyperion FDM when importing a source file. Please note that it is not necessary to place the source file in this directory as Hyperion FDM can import source files from any accessible directory. The Inbox directory can be used as a central repository for all the ledger extract files. Sub-directories can be added to the Inbox directory for easy categorization of files, i.e., one sub-directory for each Hyperion FDM location.

    Archive RestoreThe Archive Restore directory is used to store restored import source files and logs that Hyperion FDM previously archived. Hyperion FDM stores the original archived source files and logs in the Data\Archive directory.

    BatchesThe Batches directory is used to store files used during batch loading. All files that are loaded using the batch loader must be placed in the OpenBatch folder inside the application directory.

    OpenBatch all files that are loaded using the batch loader must be placed here.OpenBatchML all files that are loaded using the Multiload function must be placed here.

    Locations FoldersThe locations folders shown in the example (Indiana, Michigan, etc.) are created when a location is created from within the Hyperion FDM application. This feature can be disabled, therefore, an application with Locations Folders disabled will not have these in the Inbox.

    Outbox DirectoryThe Outbox directory is the default directory used by Hyperion FDM for exporting data files. This directory provides a central location for all export files that are subsequently loaded into the target system. This directory also contains four sub-directories; Archive Restore, ExcelFiles, Logs, and Templates.

    Archive RestoreThe Archive Restore directory is used to store restored data load files that Hyperion FDM previously archived. Hyperion FDM stores the original archived data load files in the Data directory.

  • Hyperion FDM Administrator Training Guide

    1-4

    ExcelFilesThe ExcelFiles directory contains Microsoft Excel files that are created by Hyperion FDM when exporting the contents of a grid to Excel.

    LogsThe Logs directory primarily contains log files that are created when source files are imported. These log files contain all the data lines that Hyperion FDM was not able to import and include an explanation why the line was skipped. The Logs directory also contains logs of any errors that have occurred. Error files are named with the user name and an .err extension (. ). This directory can be purged periodically in order to reclaim disk space.

    TemplatesThis directory is used to manage and distribute custom journal or multiload templates created by headquarters for use by reporting locations. The contents of the Templates directory are displayed as links within Hyperion FDM Web Client. The system administrator publishes a template by placing the template here.

    Reports DirectoryThe Reports directory stores the report files. Active Reports files are designated by an extension of .rpx. Each report also has an associated Data Definition file that was used to design the report.

  • 1-5

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    Managing Hyperion FDM ApplicationsOpening Applications

    Hyperion FDM WorkbenchOpen the Hyperion FDM Workbench by selecting Programs Hyperion System 9 Financial Data Quality Management-Workbench Workbench Client from the Windows Start menu.

    Select the Hyperion FDM application to open from the Application: dropdown window (Figure 1-2). Enter the username and password for the application and click . Hyperion FDM will launch and display the Hyperion FDM desktop (Figure 1-3).

    Figure 1-2 (right): Open an application from the Hyperion FDM Workbench screen

    Figure 1-3: Hyperion FDM Workbench Desktop

  • Hyperion FDM Administrator Training Guide

    1-6

    Hyperion FDM Web ClientOpen the Hyperion FDM Web Client by selecting Programs Hyperion System 9 Financial Data Quality Management- WebServer Components Web Logon from the Windows Start menu (right)

    Select the Hyperion FDM application to open from the Application: dropdown window (Figure 1-4). Enter the username and password for the application and click

    . Hyperion FDM will launch and display the Hyperion FDM desktop (Figure 1-5).

    Figure 1-4 (right): Open an application from the Hyperion FDM Web Client Logon screen.

    Figure 1-5: Hyperion FDM Web Client Desktop

  • 1-7

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    Creating ApplicationsA new Hyperion FDM application is created by selecting from the Application: dropdown window in the Hyperion FDM Logon screen (Figure 1-6) and entering a name and password. The User Name and Password should be for the person who will be the administrator for the new application.

    After clicking the New Application dialog will be displayed (Figure 1-7).

    Figure 1-6: Create a new Hyperion FDM Application when logging onto Hyperion FDM

    using the Option

    The New Application is comprised of two pages accessible by tabs - a General tab and a Database tab.

    General TabThe General tab (Figure 1-7) is used to define the Hyperion FDM application name and the application description. The General tab is also used to establish where the Hyperion FDM application architecture will be stored (Path field).

    Name this field used to define the application name. The application name may contain up to twenty alphanumeric characters. Do not use spaces. Underscores (_) are acceptable.Description enter a description of the application here.Path use this field to define the file path where the new application will be created. The application consists of the directory that includes the Inbox, Outbox, Data, and Reports folders. If users will be accessing the application via multiple web and application servers then it is recommended to use the UNC naming convention to avoid problems with inconsistent drive letter mapping.

    Figure 1-7: Add/New/Modify Application Dialog Box (General Tab)

    When the Hyperion FDM application is created, a new folder is created that is named the same name as the Hyperion FDM application name. The application name is also added to the WebLinkDMApplications.xml file which is stored in the installation directory.

  • Hyperion FDM Administrator Training Guide

    1-8

    Database TabThe Database tab (Figure 1-8) is used to name the RDBMS database that will store all of the Hyperion FDM transaction data.

    Figure 1-8: New/Add/Modify Application Dialog Box Database Tabs for SQL (left) and Oracle (right)

    OLE DB Provider specifies the database that will be used by the application. The default database is SQLOLEDB. However, ORAOLEDB.ORACLE is also supported.Database Server specifies the database server. The database server is the location of the database used by the application (used by SQL Server only).Database Name use this to define the database name. The database name is typically the same as the application name. The database name you define will be the name of the RDBMS database (used by SQL Server only.)Service enter the Oracle service used for connecting to the Oracle database here.Username enter the database administrator ID here. For example, the SQLOLEDB administrator ID.Password enter the database administrator password here.Options Button click to override of the default table space where the Hyperion FDM application is created (Oracle only).

    After the new application has been defined, select . A message box will be displayed to confirm that the new application has been created.

  • 1-9

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    Removing ApplicationsRemoval of an application is performed using the Hyperion FDM Logon screen. Launch the Hyperion FDM Logon page, select from the Application dropdown list, and enter the username and password for the application.

    Figure 1-9: Remove a Hyperion FDM Application by logging onto Hyperion FDM and selecting from the Application dropdown list.

    Click to log onto Hyperion FDM and prompt the Add Application screen (Figure 1-10).

    In the Add Application screen highlight the application to be deleted and click .

    Note: Removing an application does not delete or impact the data in the Hyperion FDM application that is being removed. This task only deletes the current users pointer to the application from the Hyperion FDM DataMart Application XML file. The directory that contains all the information will remain intact.

    Figure 1-10: Remove an application from the Add Application screen. Highlight the application

    to be removed and click .

  • Hyperion FDM Administrator Training Guide

    1-10

    Adding ApplicationsAddition of an application is performed using the Hyperion FDM Logon screen. Launch the Hyperion FDM Logon page, select from the Application dropdown list, and enter the username and password for the application. The domain name may be required for certain configurations.

    Note: The procedure for creating a new application is used when the application does not exist. The Add Application procedure is used when the application already exists, but there is no pointer to the application in the application .xml file.

    Figure 1-11: Select from the Hyperion FDM Logon Screen

    Click to log onto Hyperion FDM and prompt the Add Application screen (Figure 1-12).

    The Applications screen lists all of the applications that have been defined on the current computer.

    Click to display the Add Application screen (Figure 1-13).

    The Add Application form contains the information that defines the name and location of a Hyperion FDM application. The form is comprised of two pages accessible by tabs a General tab and a Database tab.

    Figure 1-12: Select from the Add Application Dialog.

  • 1-11

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    General TabName enter the name of the application here. Do not use spaces. Underscores (_) are acceptable (Figure 1-13).Description enter a description of the application in this field.Path use this field to specify the file path where the application resides.

    Figure 1-13: Add Application Dialog General Tab

    Database TabThe Database tab is used to name the RDBMS database that will store all of the Hyperion FDM transaction data.

    Figure 1-14: Add Application Dialog Database Tab

  • Hyperion FDM Administrator Training Guide

    1-12

    OLE DB Provider this field is used to define the database that will be used by the application. The default database is SQLOLEDB however ORAOLEDB.ORACLE is also supported.Database Server this field is used to define the database server. The database server is the location of the database used by the application. (This section is used by SQL Server only).Database Name use this to define the database name. The database name is typically the same as the application name. The database name you define will be the name of the RDBMS database (used by SQL Server only.)Service enter the Oracle service used for connecting to the Oracle database here.Username enter the database administrator ID here. For example, the SQLOLEDB administrator ID.Password use this field to define the database administrator password.Options Button click to override of the default table space where the Hyperion FDM application is created (Oracle only).

    When the application has been defined, select .

  • 1-13

    Section A Section B Section C Section D Section ESection A

    Hyperion FDM Basics

    Module 1 Oeriew of Hyperion FDM

    End User ProcessThe normal data load process for Hyperion FDM users moves the fish up stream in the header of the Hyperion FDM Home Page (Figure 1-15). The process starts with importing the GL data, and it moves up stream through Import, Validate, Export, and Check.

    Figure 1-15: Hyperion FDM page header. The data load process moves the fish up stream from Import through to Check.

    Before Import, there will be no fish displayed in the header. After a successful import by the Hyperion FDM user an orange fish will be displayed under Import in the header. After successfully passing the Validate stage, an additional fish will appear under Validate. Export and Check work in the same manner. The notebook icon after check is the Process Explorer. This is used to access financial controls options (if enabled).

    The end users will not be aware of the one time work the administrator had to do to prepare Hyperion FDM to process the users data files and complete the data load.

    The end users will receive training on the following 6-step process:

    Step 1: Create a GL extract file (from source application)

    Step 2: Import the GL file (to Hyperion FDM)

    Step 3: Validate the source file against the mapping

    Step 4: Export the data

    Step 5: Load the data to the target application

    Step 6: Pass the validation check

    End user training focuses on the above six-step process. The administrators training focuses on the setup required to build the back end of the application.

  • Hyperion FDM Administrator Training Guide

    1-14

  • Module 2: Hyperion fdM navigation

  • 2-1

    Section A Section B Section C Section D Section E

    Module 2 Hyperion FDM Naigation

    Section A

    Hyperion FDM Basics

    Hyperion FDM DesktopThe Hyperion FDM desktop is the control center from where a Hyperion FDM application is built and administered. The desktop is displayed after logging into a Hyperion FDM application (Figure 2-1). The desktop has three main areas: Screen Indicator, Hyperion FDM Menus, and the POV bar.

    Figure 2-1: Hyperion FDM Desktop

    Screen Indicator This tab displays the screen in which Hyperion FDM is currently set.

    Hyperion FDM Menu Rollup The menu rollup contains six tabs. Clicking on a tab will expose the underlying menu. All Hyperion FDM functions available in the Web Client can be accessed from one of the six Hyperion FDM menus. The example depicted in Figure 2-1 show the Workflow tab has been selected, and the Workflow Menu is displayed. All menu items can also be accessed from the menu bar located at the top of the desktop.

    POV Bar The Hyperion FDM application Point of View (POV) is also displayed and managed from the desktop. The POV indicates the active user, current application, location, period, Hyperion FDM category, target category, the mode (global or local), system lock status, and the adaptor in use for the current location.

  • Hyperion FDM Administrator Training Guide

    2-2

    Point of View (POV)Hyperion FDM is location-based. All tasks performed from the desktop will affect data for the location currently selected in the POV. The following is a description of the POV items:

    Hyperion FDM User Name the user name of the user currently logged onto Hyperion FDM.

    Hyperion FDM Application the Hyperion FDM application that is currently open.

    Hyperion FDM Location the Hyperion FDM location that is currently active. The user can view and load to locations for which they have permissions. Each location will have its own mapping tables.

    Hyperion FDM Period indicates the Hyperion FDM period that is currently active. The Hyperion FDM period corresponds to a target system period.

    Hyperion FDM Category shows which Hyperion FDM category is currently active. The Hyperion FDM category corresponds to a target system category.

    Target Category indicates the target system category associated with the active Hyperion FDM category. The Target system category can only be changed by changing the Hyperion FDM category.

    Global/Local Mode shows the current Hyperion FDM mode. Usually, only administrators have rights to switch to Local mode. Local mode allows an administrator to change the Hyperion FDM period and category without changing the POV for all other users.

    System Lock Status shows the status of the system lock. Administrators have the ability to lock Hyperion FDM to prevent users from working within Hyperion FDM.

    Adaptor shows which adaptor is being used for the current location. All locations default to the adaptor set in the Application Settings option unless specifically overridden.

    Figure 2-2: Hyperion FDM Desktop

  • 2-3

    Section A Section B Section C Section D Section E

    Module 2 Hyperion FDM Naigation

    Section A

    Hyperion FDM Basics

    POV is a control feature used to set the data focus. When the POV Lock system option is active, the period and category values are globally controlled across the system. Only the system administrator can change these values when the POV Lock is active. This ensures that end users can only load data to the proper period and proper category.

    However, if more flexibility is desired, the POV Lock can be disabled which will allow end users to change to Local POV mode in order to perform processing for any category or period.

    POV Mode Local vs. GlobalLocal POV Mode allows any category and/or period to be selected for processing.

    Global POV Mode restricts category and period processing to a global value that is active for all users on the system.

    Changing POV ModeThe POV mode is changed by double-clicking the POV mode tab on the bottom of the screen.

    Note: System administrators can always change their POV mode to the Local setting, but end users can only access this option if the POV Lock system option is disabled.

    Setting Location POVUsers can only view locations that they have permission to access. Location permission is determined and granted by the system administrator. When a user is created they must be assigned one default location. This location will be the one displayed on the POV when they log onto the application.

    Other locations can also be accessed by clicking the location tab at the bottom of the screen. This will prompt the Change Point-of-View form with the Location tab activated. Users can select the location(s) that they have permission to access.

    Note: The period and category can be changed by activating the associated tabs.

    Figure 2-3: Set Location Dialog

  • Hyperion FDM Administrator Training Guide

    2-4

    Setting Category POVThis is an administrator-controlled setting. The designated Hyperion FDM administrator will control the data category that is active for all users. This feature prevents users from inadvertently loading data to incorrect categories.

    Setting the system global category or your local category can be accomplished by clicking the category tab at the bottom of the screen.

    Note: The same method is used to change either the global or local value, and which value is changed depends on the current POV setting.

    Note: The location and period can be changed by activating the associated tabs.

    Changing the Hyperion FDM category also changes the target systems category. When a Hyperion FDM category is defined on the Control Tables form, it is associated with a target systems category.

    Figure 2-4 Select Category Dialog

    Setting Period POVThis is an administrator-controlled setting. The Hyperion FDM administrator will control the accounting period that is active for all users. This feature prevents users from inadvertently loading data into an incorrect period.

    When a user logs into Hyperion FDM, the application will check the global period value and automatically set the users POV to its current value. Setting the active system global period can be accomplished by double-clicking the period tab at the bottom of the screen.

    Note: The same method is used to change either the global or local value, and which value is changed depends on the current POV setting.

    Note: The location and category can be changed by activating the associated tabs.

    Changing the Hyperion FDM period also changes the target systems period. Figure 2-5: Select Period Dialog

    POV SearchUse the in the POV (location, periods, or category tabs) to find information. In the POV Search Dialog, enter a full or partial string to search the current POV and click .

  • 2-5

    Section A Section B Section C Section D Section E

    Module 2 Hyperion FDM Naigation

    Section A

    Hyperion FDM Basics

    Figure 2-6: POV Search Dialog

    Locking and Unlocking the SystemLock the system by clicking the category System Lock at the bottom of the screen.

    Note: Locking/unlocking the system privileges are restricted to administrators.

    Use this option to terminate user sessions that are logged into the database and to disallow new users from logging into the database. You can also type in the message you want displayed to users when they are disconnected. You will need to terminate user sessions before performing database maintenance activities.

    When the system is locked users will not be able to log on. A user session will not be terminated if they are currently writing records to the database.

    Figure 2-7: System Lock Dialog

    How a Users Default Point-of-View is DeterminedWhen a user logs into Hyperion FDM, the following sequence of events is executed to set the users default point-of-view options:

    Location POV is set by retrieving the users security profile.POV Mode is set to Global as default mode.Category POV is set by retrieving the system global category.Period POV is set by retrieving the system global period.

  • Hyperion FDM Administrator Training Guide

    2-6

  • Module 3: Building a Hyperion fdM application overview

  • 3-1

    Section A Section B Section C Section D Section E

    Module 3 Building a Hyperion FDM Application Oeriew

    Section A

    Hyperion FDM Basics

    IntroductionThe following steps outline the process for building a Hyperion FDM application:

    Step 1: Create a new Hyperion FDM application

    Step 2: Integrate the new application with the target system

    Step 3: Populate the Hyperion FDM control tables

    Step 4: Create the Hyperion FDM locations

    Step 5: Import maps for each location

    Step 6: Build import formats

    Step 7: Test data loading

    Step 8: Build validation rules and reports

    Figure 3-1 (right): Building a Hyperion FDM Application Flowchart. The next page includes the process flowchart expanded to show the individual

    sub-processes associated with building a Hyperion FDM application.

    Pre-Implementation Data RequirementsThe pre-implementation data requirements are information that must be provided by the customer in order to build a new Hyperion FDM application.

    Source GL Extract File an ASCII (text) file or report extracted directly from source system that has not been modified or manipulated by the end-user. The source file must contain account number, account description, amount and any additional dimensions for each record. Ideally, this file should not be an *.xls (Microsoft Excel) file. If the file contains multiple entities, the entities must also be identified for each record.

    Account Mapping File this file maps the source system accounts to the target system accounts. Valid mapping files include LedgerLink extracts (*.tra), Hyperion Conversion Table extracts, Microsoft Excel maps, any other mapping sources including databases.

    Entity Mapping File this file maps the source system entities to the target system entities. Valid mapping files include LedgerLink extracts (*.trn), Hyperion Conversion Table extracts, Microsoft Excel maps, any other mapping sources including databases.

    Custom Dimension Mapping Files source system custom dimensions mapped to target system custom dimensions.

  • Section B: Building a Hyperion FDM Application

    In this Section:

    Module 4: Creating a Hyperion FDM Application

    Module 5: Integrating the Adaptor

    Module 6: Populating Control Tables

    Module 7: Creating Hyperion FDM Locations

    Module 8: Importing Mapping Tables

    Module 9: Building Import Formats

    Module 10: Testing Data Load

  • Module 4: creating a Hyperion fdM application

  • 4-1

    Section A Section B Section C Section D Section E

    Module 4 Creating a Hyperion FDM Application

    Section B

    Building a Hyperion FDM Application

    OverviewThe first step in building a Hyperion FDM application is to create a new application when you first log onto Hyperion FDM. A new Hyperion FDM application can be created using the Hyperion FDM Web Client or the Hyperion FDM Workbench.

    The procedure outlined in this section is a summarized version of the procedure demonstrated in Section A. Refer to Section A for detailed information about creating a new application.

    Procedure Creating a New Hyperion FDM Application

    a. Log onto Hyperion FDM using the option.

    b. Complete the New Application dialog box.

  • Hyperion FDM Administrator Training Guide

    4-2

    a. Log onto Hyperion FDM Using the OptionLaunching the Hyperion FDM Web Logon or Workbench Client will display the Logon screen (Web Client shown).

    Select from the Application: dropdown window and enter the name and password.

    Click . The New Application dialog will be displayed.

    Figure 4-1: Create a new Hyperion FDM Application when logging onto Hyperion FDM using the Application dropdown.

    b. Complete the New Application Dialog BoxThe New Application form contains the information that defines the name and location of a Hyperion FDM application. The form is comprised of two pages accessible by tabs a General tab and a Database tab.

    The General tab is used to define the Hyperion FDM application name and the application description. The General tab is also used to establish where the Hyperion FDM application architecture will be stored (Path field).

    The Database tab is used to name the RDBMS database that will store all of the Hyperion FDM transaction data

    For more detailed information about the options for the database tab, refer to Creating.Applications.in Section A.

    Figure 4-2: New/Add/Modify Application Dialog Box General Tab (left) and Database Tabs (left).

    After the new application has been defined, select . A message box will be displayed to confirm that the new application has been created.

  • Module 5: integrate witH tHe target application

  • 5-1

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    Integration OverviewIntegration settings are used to point a Hyperion FDM application to the target application. The target application is the application to which you want to load data. Hyperion Enterprise and Hyperion Financial Management (HFM) are examples of valid target applications.

    After integrating with either of the target applications, import the standard reports from an XML file and copy the standard templates into the new applications folder structure.

    The process of integrating with the target application is competed from within the Hyperion FDM Workbench client.

    Note: The information in this module includes procedures for setting up integration adaptors for Hyperion Enterprise and Hyperion Financial Management. Refer to the Hyperion FDM Installation Guide for procedures to set up an Essbase adaptor.

    Procedure Integrating with the Target Application

    a. Import the target system adaptor.

    b. Register the adaptor.

    c. Add machine profile.

    d. Verify application settings.

    e. Update integration settings.

    f. Update DCOM settings (Enterprise only)

    g. Map Hyperion FDM Dimensions to Target Dimensions (Enterprise only).

    h. Test integration settings.

    i. Test integration settings from within the Web Client.

  • Hyperion FDM Administrator Training Guide

    5-2

    a. Import the Target System AdaptorFrom the Workbench desktop activate the Adaptors page by clicking on the Adaptors tab.

    Select FileImport. This will prompt the Open Import File dialog (Figure 5-1).

    Figure 5-1: Open File Import dialog. Locate and select the target system adaptor file from here.

    From within the Open Import File dialog, locate and select the target system adaptor file then click on to display the Import window (Figure 5-1).

    Note: HETxx.xml files are Enterprise adaptors and HFMxx.xml files are HFM adaptors. The filename of the current release of the adaptor and location of the adaptor may vary. Refer to the WebLink.DM.Admin.Guide or the Hyperion web site for more information about adaptors.

    From within the Import popup screen (General tab), check the items to import (Figure 5-2).

    Click the Options tab. This tab contains the following options:

    Save existing machine profile if this box is not checked, all existing machine profiles will be deleted.

    Remove all report groups before updating reports this option deletes existing report groups before updating the application with new reports.

  • 5-3

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    Figure 5-2: Import File Dialog. Import of adaptor General Tab (HFM left), (HE center) and Options tab (right).

    Select/deselect the options to be used and click . The selections will be imported and displayed on the desktop under Target System Adaptors (Figure 5-3).

    Figure 5-3: After importing the target system adaptor it is displayed on the Hyperion FDM Workbench desktop under Target System Adaptors. Enterprise (left) and HFM (right).

  • Hyperion FDM Administrator Training Guide

    5-4

    b. Register the AdaptorNote: Adding the adaptor and setting up machine profiles needs to be completed once for every Hyperion

    FDM application that is created. Registering the adaptor needs only to be done one time. Skip Step C if a Hyperion FDM application using the same adaptor that has already been registered. The file will be registered for any future applications.

    From the Workbench desktop, select FileRegister Adaptor to display the Register Adaptor dialog (Figure 5-4).

    Figure 5-4: Select FileRegister Adaptor to prompt the Register Adaptor dialog. Register the adaptor using the .exe file for Enterprise or the .dll for HFM.

    Select the file from the list (upsENxxx.exe for Enterprise, upsFMxxx.dll for HFM) and click on (Figure 5-4).

    Note: The adaptors may not be in the directory used in this example. Adaptors may also be located in the root directory of the Hyperion FDM Install folder.

  • 5-5

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    c. Add Machine ProfileWorking from the Adaptor tab in the Hyperion FDM Workbench desktop, expand the directory titled Target System Adaptors by clicking to expand the Adaptors directory, then clicking next to the adaptor listed to open the adaptor subdirectory.

    Right-click on the Machine Profiles folder and select Add Machine Profile from the flyout menu (Figure 5-5). The Add Machine Profile dialog box will be displayed (Figure 5-6).

    Complete the Source Machine and Target Machine information in the Add Machine Profile dialog box.

    Source Machine Name enter the Hyperion FDM Application server name here.

    Target Machine Name enter the computer name or IP address of the application server or application cluster here.

    User Name specify a user name, password, and domain for the local machine to override the logon method specified in the Integration Settings logon method. This computer will always use the specified user name and password to log onto the target application server and the application. The user account specified here must have access to the target application server and have appropriate security privileges, regardless of the user who is logged into Hyperion FDM. This option is generally not used, but rather the unified logon functionality in Hyperion FDM to that provides network authentication is the more preferred method.

    Password the Windows password for the target machine.

    Domain the domain for target machine.

    Select when finished.

    Figure 5-5: Right-click on the Machine Profiles folder to add a machine

    profile (example for HFM).

    Figure 5-6: Add Machine Profile Dialog box.

  • Hyperion FDM Administrator Training Guide

    5-6

    d. Verify Application SettingsFrom the Hyperion FDM desktop, open the Administration Menu by selecting the Administration Tab.

    Figure 5-7: Clicking on the Administration Tab in the left menu will expose the Administration Menu.

    From the Administration Menu click the Application Settings link to switch to the Application Settings screen (Figure 5-8).

    The Applications Settings screen includes an Options pulldown field. Confirm that the System Code contains the name of the adaptor that was just added. If several adaptors currently exist in the application, they will be selectable in this field. Use the pull-down menu to select the correct system code key/adaptor for the target system and click (Figure 5-8).

    Figure 5-8 (right): Application Settings Screen. Select the correct system code for the target application. This example is for HFM.

  • 5-7

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    e. Update Integration SettingsFrom the Administration Menu select Integration Settings to display the Integration Settings Screen (Figure 5-9). Select Application Name from the Options field dropdown.

    In the App Name field type in the name of the target application. Click to update the integration settings.

    Figure 5-9: Setting the target application name and logon method is performed from the Integration Settings screen.

    Logon MethodFrom the Integration Settings menu, click the dropdown in the Options Field and select Logon Method (Figure 5-10).

    This option controls the method that Hyperion FDM uses to log onto the target system whenever Hyperion FDM makes a connection. There are two logon methods, Unified and Global.

    Unified the Hyperion FDM username and password are used to log onto the target system. The username and password for users to log onto the target must be the same as the Hyperion FDM username and password in order to use this option. Figure 5-10: Select Logon Method from

    the Integration Settings screen.

    Global the username and password specified in the Global Logon Information Option is passed to the target system. Using this option, all users connect to the target system using the same username and password.

    If a machine-specific username and password is specified in the Workbench then it will override the logon method specified above for this specific machine.

  • Hyperion FDM Administrator Training Guide

    5-8

    Global Logon InformationThis option is used in conjunction with the Logon Method option. If the Logon Method option is set to Global then use this option to set the user ID and password used to log onto the target system. Separate the user ID and password with a semicolon, i.e.. UserID;Password (Figure 5-11).

    Figure 5-11 (right): Global Logon Method options

  • 5-9

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    f. Update DCOM SettingsNote: This procedure is for integrating Hyperion FDM with Hyperion Enterprise only. If integrating with

    Hyperion Financial Management proceed to Step H.

    The upsIntBlockHE6xG.clsHypWindow object must be configured to allow access by the same UserID as is configured in the application servers. To do this first launch DCOM Config from the Run command.

    Figure 5-12: Launch the DCOM Configuration from the Windows Run prompt.

    Change DCOM Identity settings on the upsIntBlockHE6xG.clsHypWindow object by right clicking on the object and selecting Properties.

    Figure 5-13: Right click on the object and select Properties

  • Hyperion FDM Administrator Training Guide

    5-10

    From the Properties Window, select the security tab, then click .

    Figure 5-14: Properties Dialog - Security Tab

    Change DCOM Security settings for Launch/Activation Permissions & Access permissions, to Custom. Click the Edit button and ensure that the User ID running the application servers is added to the Custom permissions. If any users will be running the Workbench their User ID must also be configured in this manner.

    Figure 5-15: Launch Permissions Screen

  • 5-11

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    g. Map Hyperion FDM Dimensions to Target DimensionsNote: The procedures described here apply only to an Enterprise target applications. It is not necessary for

    HFM. To continue with the integration for HFM, proceed to Step H.

    The NameCat.txt file is used to hold the Hyperion Enterprise name and category that are used to determine if an Enterprise account is calculated. The name selected should represent a typical base name, and the category selected should represent a category used to store actual data.

    Return to the Hyperion FDM Workbench Client and click on the scripts tab. The Script Editor directory will appear (Figure 5-16).

    Figure 5-16: Script Editor Directory

  • Hyperion FDM Administrator Training Guide

    5-12

    Open the Custom\General folder and double-click on the HET_EditNameCat script. The script will be displayed in the right side window (Figure 5-17).

    Figure 5-17: Script Editor

    Click on the run button. The Editor dialog box will be displayed (Figure 5-18).

    Click and select a typical base name from the target application. Click and select a category that represents one that will be loaded by the Hyperion FDM application then click . A message box will appear confirming that the script has run.

    Note: The Default for the Dimension Cache Switch is set to off. When set to On the dimension list values are retrieved from Hyperion FDM cache tables and not from the target system. When set to On, then the HET_UpdateDimensionCache script must be run from the Workbench in order to update the tables with the current target application dimension list values.

    Figure 5-18 (right): Editor

  • 5-13

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    i. Test the Integration from within the Web ClientLog onto the Hyperion FDM Web Client.

    Open the Activities Menu by clicking the Activities Link on the left desktop menu. Select Maps from the Activities Menu (Figure 5-19).

    Figure 5-19: Click Maps from the Activities Menu to start testing the target application integration.

  • Hyperion FDM Administrator Training Guide

    5-14

    On the Maps screen (Figure 5-20) click . A new row will be added to the grid.

    Click Browse For Target Value to display the list of target accounts. If another window is displayed with the list of accounts then the integration settings are configured correctly. Otherwise, an error will be displayed.

    Figure 5-20: Maps Screen

    Figure 5-21: List of target accounts retrieved from the target application. When this screen appears, the integration was successful.

  • 5-15

    Section A Section B Section C Section D Section E

    Module 5 Integrate with the Target Application

    Section B

    Building a Hyperion FDM Application

    Import the Standard ReportsNote: The reports may be in a compressed file (.zip). Zipped files must be extracted before importing into

    Hyperion FDM. Unzip the file into the \Templates folder.

    From the Hyperion FDM Workbench desktop activate the Reports screen by clicking the Reports tab.

    Select FileImport to prompt the Open Import File dialog box (Figure 5-22).

    Figure 5-22 Open Import File Dialog

    Locate and select the standard reports XML file applicable to the database that you are using (SQL or Oracle). Click and the Import dialog will be displayed. The Import box contains two tabs -- General and Options (Figure 5-23).

    Figure 5-23: Import dialog used to import reports into the Hyperion FDM

  • Hyperion FDM Administrator Training Guide

    5-16

    application. General tab (left) and Options tab (right).

    General select the reports folder in the Import dialog (Figure 5-24).

    Options contains two checkboxes. The Save Existing Machine Profiles box enables/disables the machine profile override. The Remove All Report Groups checkbox enables/disables the Report Groups override. Checking this box will delete existing report groups before updating the application with new reports. Leave this box unchecked.

    Click when completed with the two tabs and the reports directory will appear on the Reports tab (Figure 5-24).

    Figure 5-24: After importing the reports, the reports directory will appear on the Reports tab.

    Import the Standard TemplatesNote: The standard template folder may be in a compressed file (.zip) named templates.zip. Extract this file into

    the \Outbox\Templates folder.

  • Module 6: populating control taBles

  • 6-1

    Section A Section B Section C Section D Section E

    Module 6 Populating Control Tables

    Section B

    Building a Hyperion FDM Application

    Control Tables OverviewControl tables are used to supply the values displayed in system options. These tables allow the system administrator to control the system options and POV values that users can select.

    The setup of the control tables can be performed in either the Hyperion FDM Web Client or the Hyperion FDM Workbench. The examples presented here were generated using the Web Client.

    Procedure Populating Hyperion FDM Control Tables

    a. Open the Control Tables screen.

    b. Add the Periods.

    c. Add the Categories.

    d. Verify the Currency Codes.

  • Hyperion FDM Administrator Training Guide

    6-2

    a. Open the Control Tables ScreenTo access the control tables from Hyperion FDM Web Client desktop, select the Metadata Tab from the left desktop menu to display the Metadata menu. Then click on Control Tables to open the Control Tables Screen.

    Figure 6-1: Control Tables Screen. Switch between the Periods Table, Categories Table, and Currency Codes Table by selecting them from the dropdown menu.

    There are three control tables used by Hyperion FDM -- Periods, Categories, and Currency Codes. Switch between tables by selecting them from the Control Table dropdown list. The Periods Control Table allows for the definition of the valid fiscal periods that can be used by Hyperion FDM. The values in this table provide the list of possible periods that can be selected from the Period POV link. Changing the Hyperion FDM period will change where data is loaded in the target system.

  • 6-3

    Section A Section B Section C Section D Section E

    Module 6 Populating Control Tables

    Section B

    Building a Hyperion FDM Application

    b. Add the PeriodsThe Period control table allows for the definition of the valid fiscal periods available to Hyperion FDM. The values in this table provide the list of possible periods that can be selected from the Period POV link. Changing the Hyperion FDM period will change where data is loaded in the target system.

    Period actual date value that will be stored in the database during the trial balance load process. This field becomes part of the key that uniquely identifies each set of TB records.

    Prior Date Key prior fiscal period key. Used during the export process to determine if a $0.00 entry must be made in order to prevent ghosting in Hyperion Enterprise versions 4.3 or below, caused by YTD values being loaded into a periodic category.

    Text Description holds a text-based description of the Date key. The format of the text description is controlled by the system configuration. The format is defaulted to a monthly granularity, but can be changed to allow loading of more than 12 periods.

    Target Period (M), (Q), (Y), (D) holds the target systems period to which data will be loaded.

    Year holds the year.

    Select to add additional periods to the table. Click in any field to activate it and add/modify the information.

    Figure 6-2 Double-click in a field to activate it and add/modify information.

    Click Browse for Target Periods in the Target Period column to select a valid target application period.

    To delete a row, select the row and click . The icon will show at the left end of the row indicating that a deletion is pending.

    When a row has been edited, the icon will show at the left of the column to indicate that the change is pending.

    Changes to the table will be saved when the button is selected and the icons on the left of the rows will be removed.

    To cancel a pending change to a row, click the or icon at the end of the row and select Cancel Row Changes.

    Note: The current period (period selected in the POV) cannot be edited.

  • Hyperion FDM Administrator Training Guide

    6-4

    c. Add the CategoriesThe Categories Table contains the definition of data categories. These categories represent buckets in which data can be loaded.

    Figure 6-3: Control Tables Screen Categories View

    The values in this table provide the list of possible categories that can be selected from the Category POV link. Each Hyperion FDM category is associated with a target systems category. Changing the Hyperion FDM category will change where data is loaded in the target system.

    Category Key automatically generated by Hyperion FDM. The numeric key assigned to each category is the value that is stored during the trial balance load process. This field becomes part of the key that uniquely identifies each set of trial balance records.

    Category Hyperion FDM category name.

    Description long name for Hyperion FDM category.

    Target Category holds the target systems category in which the data will be loaded.

    Frequency holds the category frequency.

    Select to insert additional categories to the table. Select a cell to activate it in order to add/update information. The current category (selected in the POV) cannot be edited.

    Figure 6-4: Click to add a new category. Highlight an existing row to make updates to it.

  • 6-5

    Section A Section B Section C Section D Section E

    Module 6 Populating Control Tables

    Section B

    Building a Hyperion FDM Application

    Use the Browse in the Target Category column to select a valid target category.

    To delete a row, select the row and click . The icon will show at the left end of the row indicating that a deletion is pending.

    When a row has been edited, the icon will show at the left of the column to indicate that the change is pending.

    Changes to the table will be saved when the button is selected. After updating, the icons on the left of the rows will be removed.

    To cancel a pending change to a row, click the or icon at the end of the row and select Cancel Row Changes.

    Figure 6-5: Click the icon at the left of the row to cancel changes.

  • Hyperion FDM Administrator Training Guide

    6-6

    [ Verify the Currency CodesThe Foreign Currency Table contains a list of currency codes. Currency codes are assigned to locations. The currency code will be displayed on reports. This code does not impact any calculations, and is used for notation purposes only.

    Currency Code contains the short description/code for the currency.

    Description field to provide a more detailed description of the currency.

    The Currency Code table is loaded with many currencies. If needed, select to add additional currencies to the table. Select a row to make updates to an existing currency.

    Figure 6-6: Control Tables Screen Currency Codes View

    Additions or updates to a table will take effect after clicking the button.

  • 6-7

    Section A Section B Section C Section D Section E

    Module 6 Populating Control Tables

    Section B

    Building a Hyperion FDM Application

    ExErcisE 6-1a: sEtting Up control tablEs

    Use the Hyperion FDM Web Client to complete this exercise.

    1. From the Hyperion FDM Web Client log onto the Hyperion FDM application named WLTraining.

    2. Add the period control tables for January through December.Remember, you must de-select the current period in order to modify it. The completed Period Control Table should look like the following:

    3. Set up control tables for the following categories:WL_Actual Enter a description of FY 2005 Actuals, and a frequency of Monthly. Link to target category Actual.WL_Budget Enter a description of FY Budget, and a frequency of Monthly. Link to target category Plan.

    4. Delete the category titled WLCat.

    The completed Category Control Table should look similar to the following.

  • Hyperion FDM Administrator Training Guide

    6-8

    ExErcisE 6-1b: sEtting Up control tablEs

    Use the Hyperion FDM Web Client to complete this exercise.

    1. Using the Web Client, log onto the Hyperion FDM Application named WLTraining.

    2. Add the Period control tables for January through December.Remember, you must de-select the active period in order to modify it.

    The completed Period Control Table should look like the following:

    3. Add the following categories:ACTUAL Enter FY Actual for the description. Select CYACT as the target category and Monthly as the Frequency.Budget Enter FY Budget for the description. Select Budget as the target category and Monthly as the frequency.

    4. Delete the WLCat category.

    Your completed Category Control Table should look similar to the following:

  • Module 7: setting up locations

  • 7-1

    Section A Section B Section C Section D Section E

    Module 7 Setting Up Locations

    Section B

    Building a Hyperion FDM Application

    Hyperion FDM Locations OverviewLocations are maintained in the Locations screen. The setup of the locations can be performed in either the Hyperion FDM Web Client or the Hyperion FDM Workbench Client. Examples presented here were generated using the Web Client.

    Hyperion FDM Location TypesHyperion FDM maintains two types of locations; Data Load and Controls Review.

    Data Load location that accepts data from a source system and loads data via mapping rules to a target system. A data load location can also be assigned financial controls. Data load locations can only be children in the controls structure, they cannot be parents. Data load locations are designated by the icon.

    Controls Review location assigned only to financial controls. No data is loaded from a controls review location. Controls review locations are typically parents in the controls structure. A controls review location can also be a child of another controls review location. A controls review location is designated by the icon.

    Data loading locations have maps and are assigned an import format. Optionally, each data loading location may be assigned a logic group and validation rules.

    Figure 7-1: Location Types: Controls Review and Data Load

    Procedure Creating Hyperion FDM Locations

    a. Open the Locations screen.

    b. Add a location as data load or controls review.

    c. Apply attributes to the new location.

  • Hyperion FDM Administrator Training Guide

    7-2

    a. Open the Locations ScreenThe Location Maintenance screen is accessed from the Metadata Menu. Select the Metadata Tab on the Web Client desktop to display the Metadata menu, then select Locations.

    Figure 7-2: Locations Screen

  • 7-3

    Section A Section B Section C Section D Section E

    Module 7 Setting Up Locations

    Section B

    Building a Hyperion FDM Application

    b. Add New LocationSelect any existing location in the control structure tree and right-click on the location to access the location flyout menu.

    Select Add Sibling or Add Child to add a new location. Depending on your selection, the Add Sibling or Add Child dialog box will be displayed (Figure 7-3).

    Figure 7-3: Location Flyout Menu

    Select the Location Type from the dropdown (Data Load or Controls Review), name the location and select .

    Location names are restricted to twenty alphanumeric characters with no spaces (underscores are allowed). At this point the new location will be created.

    By default, a location folder will be added to the Hyperion FDM applications inbox for each location that is added. The new folder will be named the same as the location. The location folders can be used to organize GL files, journals, and other documents per location.

    By default, deleting a location will not delete the location folder. Refer to the WebLink. DM. Admin.Guide for more information regarding location folder options.

    Figure 7-4: Add Sibling Dialog

    Moving LocationsLocations can be moved within the locations tree by right-clicking the location to display the flyout menu and selecting Move. This will display the Move Location Dialog box. Select the appropriate options and click .

    Figure 7-5: Move Location Dialog

  • Hyperion FDM Administrator Training Guide

    7-4

    c. Apply Attributes to the New LocationThe Location screen contains four tabs General, Workflow Behaviors, Financial Controls, and Integration Options.

    Figure 7-6: Locations Screen General Tab

    General TabDescription field used to store additional information about the location. This is useful for tracking which GL systems are in use, or other system-related information about a location. When creating a new location the default description is the same as the name of the location.Currency identifies the currency that will be loaded into the location. This currency code is only used for identification purposes in certain Hyperion FDM reports and other forms within Hyperion FDM that display data. The currency code does not impact any calculations because Hyperion FDM does not perform currency translation (optional).Parent Location a location assigned a parent will use the same mapping table as the parent. Multiple locations may have the same parent location. This is useful when multiple locations employ the same chart of accounts. If a change is made to a child or parent mapping table then the change takes place for all children and parent locations (optional).Load Type each data load location uses one of two load types, SQL Insert or Bulk Insert. SQL Insert is the default load method and should be used for locations loading smaller files (6000 records or less). The Bulk Insert load type should be selected for locations that load larger files as it is more efficient in handling larger files.Seq Map by default Hyperion FDM wildcard maps (Like, In, Between) are sorted in the Maps Form alphabetically by their rule name. The Seq. Map option allows sorting and processing maps by a numeric value rather than t