hyperion® strategic finance - oracle · tmi e tabel ... acvtianitg and managnig assumpoitns change...

H Y P E R I O N ® S T R A T E G I C F I N A N C E

R E L E A S E 9 . 3 . 1

A D M I N I S T R A T O R ’ S G U I D E

Strategic Finance Administrator’s Guide, 9.3.1

Copyright © 1996, 2007, Oracle and/or its affiliates. All rights reserved.

Authors: Will MacLean

The Programs (which include both the software and documentation) contain proprietary information; they are providedunder a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, andother intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, exceptto the extent required to obtain interoperability with other independently created software or as specified by law, isprohibited.

The information contained in this document is subject to change without notice. If you find any problems in thedocumentation, please report them to us in writing. This document is not warranted to be error-free. Except as may beexpressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced ortransmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of theUnited States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered toU.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to theapplicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subjectto the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additionalrights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerousapplications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measuresto ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for anydamages caused by such use of the Programs.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of theirrespective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle isnot responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated withthe use of such content. If you choose to purchase any products or services from a third party, the relationship is directlybetween you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b)fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warrantyobligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that youmay incur from dealing with any third party.

Contents

Chapter 1. Architecture and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Strategic Finance Client-Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Client Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Server Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Database Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Staging Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Entities and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

The Administration Utility and Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Users Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Databases Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Entities Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Entity Groups Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Locks Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

ECM Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Batches Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Maps Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Transactions Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Logs Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Sessions Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Event Logs Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Authentication and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

About Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

External Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2. Performing Server-Related Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Managing Strategic Finance Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Logging on Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Selecting, Creating, or Deleting Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . 18

Creating and Editing Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Selecting Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Contents iii

Closing Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Selecting Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Using Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Taskflow for Creating and Editing Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Selecting General Options for Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Selecting Accounts Options for Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Selecting the Time Options for Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Selecting Scenario Options in Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Adding Scenario Types for Time Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Time Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

@basepd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

@closing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

@deal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

@firstfore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

@firstpd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

@lastfore, vXXXX(@lastfore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

@lasthist, vXXXX(@lasthist) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

@opening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

@period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Working With Scenario Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Managing Scenario Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Creating and Editing Scenario Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deleting Scenario Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring and Transferring Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Taskflow for Configuring Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring General Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring Event Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring Email Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Configuring Advanced Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Importing and Exporting Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configuring External Connection Settings for Staging Databases . . . . . . . . . . . . . . . . . . . 35

Chapter 3. Working With Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating, Selecting, and Deleting Databases on Strategic Finance Servers . . . . . . . . . . . . . 37

Creating Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating Databases from Consolidation Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Selecting Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Deleting a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Backing Up, Restoring, and Transmitting Backed Up Databases . . . . . . . . . . . . . . . . . . . . 39

iv Contents

Installing PKZip® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Backing Up Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Transmitting Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Scheduling Automatic Archives and Transmissions . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Restoring Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Viewing Error Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Relational Database Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Creating Connections to External Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

The Export Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Financial Data Available Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Entity Scalar Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Variable Info Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Financial Variable Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Alcrdt Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Extended Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Reporting Utilities for Use with Extended Analytics . . . . . . . . . . . . . . . . . . . . . . . . . 48

Taskflow for Extended Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring External Extended Analytics Databases . . . . . . . . . . . . . . . . . . . . . . . . . 49

Creating Extended Analytics Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Setting Extended Analytics Rule Sets General Options . . . . . . . . . . . . . . . . . . . . . 50

Setting Extended Analytics Rule Sets Accounts Options . . . . . . . . . . . . . . . . . . . . 51

Setting Extended Analytics Rule Sets Time Options . . . . . . . . . . . . . . . . . . . . . . . 51

Setting Extended Analytics Rule Sets Scenarios Options . . . . . . . . . . . . . . . . . . . . 52

Setting Extended Analytics Rule Sets Custom Dimensions . . . . . . . . . . . . . . . . . . 53

Optional: Creating Reference Databases and Entities . . . . . . . . . . . . . . . . . . . . . . . . . 53

The Extended Analytics Star Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Fact Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Header Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Analysis Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Entity Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Scenario Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Account Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Time Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Uddim Tables 1-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Transaction Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 4. Managing Users and User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Contents v

Adding and Editing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Looking Up Users in External Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Renaming Users or Changing Network Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Viewing License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Managing User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Creating User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Adding Users to User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Deleting Users from User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Deleting User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 5. Managing Entities and Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Managing Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Accessing Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Changing Entity Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Breaking Entity Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Manually Exporting Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Manually Exporting Extended Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Converting Entities After an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Converting Database Entities in Bulk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Converting Selected Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Managing Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Adding Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Editing Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Deleting Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Setting Entity Check-In Rules and Managing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Setting Entity Check-In Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Managing Entity Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Inspecting Entity Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 6. Providing Access to Databases and Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring General Database SettingsAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring General Database Access for Users and User Groups . . . . . . . . . . . . . . . . 73

Assigning Database General Options to Users and User Groups . . . . . . . . . . . . . . . . . 74

Configuring Default Access to Databases, Entities, and Entity Groups . . . . . . . . . . . . . . . 74

About Assigning Default Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring Entities Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configuring Accounts Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Adding Permissions Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring Time Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

vi Contents

Configuring Reports Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuring Scenario Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configuring Dimension Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configuring Consolidation Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Configuring Reference Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Configuring Default Access for New Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Adding Users and User Groups to Databases, Entities, or Entity Groups . . . . . . . . . . . . . . 83

Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Selecting Users from the User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Adding User Groups to Databases, Entities, or Entity Groups . . . . . . . . . . . . . . . . . . 84

Chapter 7. Activating and Managing Client-Side Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Activating and Managing Entity Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Activating Entity Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Managing Access to ECM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Adding Users for ECM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Adding User Groups for ECM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Editing Access to ECM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Changing the Owner of ECM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Breaking Locks on ECM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Activating and Managing Assumptions Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . 90

Activating Assumptions Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Managing ACM Document Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Changing ACM Document Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Breaking ACM Document Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Managing Batches, Maps, and Servers for Import and Export . . . . . . . . . . . . . . . . . . . . . . 92

Managing Connections to Other Hyperion Product Servers . . . . . . . . . . . . . . . . . . . . 92

Managing Connections to Other Hyperion Product Servers . . . . . . . . . . . . . . . . . 92

Creating Connections to Other Hyperion Product Servers . . . . . . . . . . . . . . . . . . 92

Managing Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Setting Access to Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Overriding Default Access to Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Changing Owners of Batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Managing Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Managing Access to Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Overriding Default Access to Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Changing Owners of Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 8. Managing Locks, Logs, Transactions, and Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Managing Entity Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Contents vii

Breaking Locks on Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Managing Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Managing Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Managing User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Managing Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Appendix A. Server Registry and Database Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Server Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Hyperion Strategic Finance Service Registry Parameters . . . . . . . . . . . . . . . . . . . . . 103

HSF Service Shared Services Registry Parameters . . . . . . . . . . . . . . . . . . . . . . . . 104

HSF Service License Manager Registry Parameters . . . . . . . . . . . . . . . . . . . . . . 105

HSF Server Registry Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Database Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

..\HSFData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

..\ADB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

..\ADB\_delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

..\ADB\<Database Name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

..\ADB\<Database Name>\<Entity Name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

..\Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

..\Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

..\UserLogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

..\Hyperion\StrategicFinance\<release>\Server\DB . . . . . . . . . . . . . . . . . . . . . . . . . 108

..\DB\Oracle\New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

..\DB\Oracle\Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

..\DB\SQL Server\New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

..\DB\SQL Server\Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Appendix B. RDBMS Export Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

RDBMS Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Setting Up the Export Database for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Creating an Instance of SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Creating the Export Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Setting Up the Export Database for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Setting Up Oracle Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Creating the Export Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

For Oracle Real Application Clusters (RAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configuring the Strategic Finance Server for Database Export . . . . . . . . . . . . . . . . . . . . 116

Selecting Database Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

viii Contents

Creating Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Setting up the External Database Connection in Strategic Finance Server . . . . . . . . . 116

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Contents ix

x Contents

1Architecture and Administration

In This Chapter

Overview ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Strategic Finance Client-Server Architecture ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Using Administrator .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Authentication and Security.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

OverviewOracle's Hyperion® Strategic Finance integrates and consolidates financial forecast modelsamong a company's planning, business development, treasury, and investor relation groups,storing that information in network-accessible databases. The Administration utility controlsclient access to Strategic Finance databases, and provides features such as:

● Database export and backup

● Entity Change Management control

● Assumptions Change Management control

Strategic Finance Client-Server ArchitectureIn client-server implementations, multiple Strategic Finance clients may exist on a network,accessing shared data stored in databases on the Strategic Finance server.

Overview 11

Figure 1 Strategic Finance Client-Server Architecture

● “Client Tier” on page 12

● “Server Tier” on page 12

● “Database Tier” on page 12

● “Staging Database” on page 13

● “Entities and Templates” on page 13

Client TierThe Strategic Finance client creates financial models, which can be stored on the client, or on aStrategic Finance server. See “Server Tier” on page 12.

Server TierThe Strategic Finance server is a centrally-managed, networked version control system,containing databases for storing entities—see “Entities and Templates” on page 13.

Clients check out entities, which the server locks from access by other clients, ensuring dataintegrity. After users modify entities, they check them back into the database.

You use Administrator to control database access and perform database-related tasks—see“Using Administrator” on page 13. Servers convert entities during upgrades, archive entities,and enable Entity Change Management and Assumptions Change Management.

Database TierServer can contain multiple databases. Database are repositories for storing and sharing entities.See “Entities and Templates” on page 13.

12 Architecture and Administration

Figure 2 Database Tier

Staging DatabaseStaging databases are for exporting to external databases, and can message between the StrategicFinance server and external databases.

Entities and TemplatesStrategic Finance entities contain financial models. Entities can be stored locally as *.alc files.Entities are the primary mechanism for storing and manipulating data.

Templates are frameworks for creating entities. They can be stored in the server, or locally as*.alt files.

Figure 3 Templates and Entities

Using AdministratorAdministrator manages security and maintenance for Strategic Finance, including: user rights,entity access, and message logs.

● “The Administration Utility and Shared Services” on page 14

Using Administrator 13

● “Users Tab” on page 14

● “Databases Tab” on page 14

● “Entities Tab” on page 14

● “Entity Groups Tab” on page 14

● “Locks Tab” on page 15

● “ECM Tab” on page 15

● “Batches Tab” on page 15

● “Maps Tab” on page 15

● “Transactions Tab” on page 15

● “Logs Tab” on page 15

● “Sessions Tab” on page 15

● “Event Logs Tab” on page 15

The Administration Utility and Shared ServicesFor implementations of Strategic Finance using Oracle's Hyperion® Shared Services, the Userstab is not available. The other tabs are still available for fine-tuning user access.

Users TabYou use the Users tab to define users and user groups, and control user access. To loweradministrative overhead, you use user groups for bulk-managing users.

Databases TabYou use the Databases tab to create and manage Strategic Finance databases. To select databases,double-click one on this tab. You can assign user access per database.

Entities TabYou use the Entities tab to view entities in a selected database. With multiple databases, an entitycan exist only once. To select entities, double-click one on this tab. You can assign user accessper entity.

Entity Groups TabYou use the Entity Groups tab to create and maintain entity groups for bulk-managing entities.


Locks TabYou use the Locks tab to view locked entities by user. You can break entity locks.

ECM TabYou use the ECM (Entity Change Management) tab to view ECM documents. You must enableEntity Change Management—see “Configuring Default Access to Databases, Entities, and EntityGroups” on page 74.

Batches TabYou use Batches tab to manage batches for importing and exporting with other Hyperionproducts. You must enable batches—see “Configuring Default Access to Databases, Entities,and Entity Groups” on page 74.

Maps TabYou use the Maps tab manage maps for importing and exporting with other Hyperion products.You must enables maps—see “Configuring Default Access to Databases, Entities, and EntityGroups” on page 74.

Transactions TabYou use the Transactions tab to view server transactions.

Logs TabYou use the Logs tab to view logged information on server actions.

Sessions TabYou use the Sessions tab to view user server sessions. A session is the duration from user log onto log off.

Event Logs TabYou use the Event Logs tab to view server events configured in “Configuring Event Log Settings”on page 30.

Using Administrator 15

Authentication and Security● “About Authentication” on page 16

● “External Authentication” on page 16

About AuthenticationAuthentication determines user access toStrategic Finance. Users can be authenticated throughan external user base defined using a Security Provider. A Security Provider is stored on aDirectory Server, and maintains lists of all network users.

If an implementation uses Strategic Finance as a stand-alone system, it uses Windows NT LANManager (NTLM) as a Security Provider. If you integrate Strategic Finance with other Hyperionproducts, you must modify the XML security configuration file to enable single sign-on andconfigure the security provider you use to authenticate users.

Using external authentication to manage users accounts provides these benefits:

● Your existing corporate structure of user accounts is used and does not have to be redefined.

● You can enable single sign-on which means users do not have to log on to each Hyperionapplication that they use.

External AuthenticationExternal Authentication facilitates single sign-on, enabling user access to multiple Hyperionapplications. When externally authenticated users log on to a Hyperion application, an encryptedtoken contains their logon credentials, including passwords. If you use trusted authenticationdirectories, passwords are not included. The token is shared by Hyperion applications to re-authenticate users in the background.

Single sign-on only occurs when one Hyperion application launches another, such as whenimporting or exporting. If users manually launch another Hyperion application, they must enterlogon credentials.

Note:

Although tokens are encrypted, apply additional security such as Secure Sockets Layer (SSL) toprevent replay attacks and man-in-the-middle attacks.

To enable single sign-on:

● Use one XML-based security configuration file shared by multiple products.

● If you use multiple XML-based security configuration files, ensure each contains identicalSecurity Provider information.


2Performing Server-Related Tasks

In This Chapter

Managing Strategic Finance Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Using Rule Sets .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Working With Scenario Types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Configuring and Transferring Server Settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Configuring External Connection Settings for Staging Databases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

The Strategic Finance server is the central storage location of the client-server implementationof Strategic Finance. The server houses databases and enables clients to access and share entities.

Managing Strategic Finance ServersYou create servers and databases from Administrator. Make a server the default to:

● Use only that server

● Automatically connect to that server at start up

● “Logging on Servers” on page 17

● “Selecting, Creating, or Deleting Server Connections” on page 18

● “Creating and Editing Server Connections” on page 18

● “Selecting Databases” on page 19

● “Closing Server Connections” on page 19

● “Selecting Items” on page 19

Logging on Servers

Note:

The first time you use Administrator, create a server. See “Creating and Editing ServerConnections” on page 18.

Managing Strategic Finance Servers 17

➤ To log on to servers:

1 From the desktop, select Start > Programs > Hyperion > Strategic Finance > Server > ServerAdministrator.

2 Select Server > Open.

3 Perform one:

● To access servers, in Server, select a server and click OK.

Note:

Select Make Default to automatically access servers on startup.

● To select databases, see “Selecting Databases” on page 19.

● To create servers, click .... See “Creating and Editing Server Connections” on page 18.

4 Click OK.

Selecting, Creating, or Deleting Server Connections

➤ To select, create, or delete server connections:

1 Log on to Administrator and click ....

See “Logging on Servers” on page 17.

2 In Server , select a server and perform an action:

● Click OK to access.

● Click Edit to edit.

Note:

Select Make Default to make the default.

● To create servers, click ....

See “Creating and Editing Server Connections” on page 18.

● To delete servers, click Delete.

3 Click OK.

Creating and Editing Server ConnectionsWhen you create servers, you must define connection settings, which you can edit later.

➤ To create or edit server connections:

1 Log on to Administrator and click ....

See “Logging on Servers” on page 17.

18 Performing Server-Related Tasks

2 On Select Server, perform a task:

● To create servers, click New.

● To edit servers, in Server, select a server and click Edit.

3 In Address of Server on Network (IP or DNS), enter the server network address.

Note:

Default: HSFServer.

4 In Protocol , enter the protocol information.

Note:

Default: ncacn_ip_tcp.

5 In Port Number, enter the port number of the Strategic Finance server.

Used by clients to connect to servers. Corresponds to the RPCPort register. Overrides the defaultserver port.

6 In Name for this Server Connection, enter or change the connection name.

7 Click OK.

8 On Select Servers, click OK.

9 On Hyperion Strategic Finance Login, select the server and click OK.

Selecting Databases

➤ To select databasex:

1 Perform a task:

● Select Server > Change Database.

● Select the database while logging in to a server. See “Logging on Servers” on page 17.

2 On Select Database, select a database and click OK.

Note:

Select Make Default to make the database the default.

Closing Server ConnectionsClose server connections by selectingServer > Close.

Selecting ItemsThe Select dialog box accesses different items depending on from where it is accessed.

Managing Strategic Finance Servers 19

➤ To select items, select one and click OK.

Using Rule SetsRule sets define the scenarios, accounts, and time periods exports contain. You define rule setson the server to configure access to export databases. Rules are compiled in an XML file on thehost.

● “Taskflow for Creating and Editing Rule Sets” on page 20

● “Selecting General Options for Rule Sets” on page 21

● “Selecting Accounts Options for Rule Sets” on page 21

● “Selecting the Time Options for Rule Sets” on page 22

● “Selecting Scenario Options in Rule Sets” on page 23

● “Adding Scenario Types for Time Rules” on page 23

● “Time Functions” on page 24

Taskflow for Creating and Editing Rule SetsUse the Rule Sets dialog box for creating and editing rule sets.

➤ To create or edit rule sets:

1 Select Server > Edit Rule Sets.

2 Perform a task:

● To edit rule sets, select a set and click Edit.

● To create rules set, click New.

3 Select general options.

See “Selecting General Options for Rule Sets” on page 21.

4 Select account options.

See “Selecting Accounts Options for Rule Sets” on page 21.

5 Select time options.

See “Selecting the Time Options for Rule Sets” on page 22.

6 Select scenario options.

See “Selecting Scenario Options in Rule Sets” on page 23.

7 Click OK.


Selecting General Options for Rule SetsUse the Create/Edit Rule Set dialog box to create or edit rule set. The General tab contains generaloptions.

➤ To set general options:

1 Access Rule Sets.

See “Using Rule Sets” on page 20.

2 Select the General tab.

3 In Name, enter or edit the name.

Must be unique within the server.

4 Optional: Select Export on Entity Create to export entities when they are first created.

Default: on

5 Optional: Select Clean Up on Deletion to delete entities from exports if they are deleted from servers.

Default: on

6 Optional: Select Clean Up on Error to automatically delete incomplete writes if there are errors.

Default: off

7 Optional: Select Clean Up on Completion to trigger transferring data from staging tables to exportdatabases.

Default = Disabled

8 Optional: Select Run in Verbose Mode to log error messages.

Default: off

9 Optional: Select Do not export when funds flow out of balance to cancel exports if the funds in the modelare out of balance.

Default: off

10 Optional: Select Calculate Scenarios on Export to calculate exported scenarios.

Default: off

Selecting Accounts Options for Rule SetsYou use the Accounts tab to select accounts for rule sets.

➤ To select accounts:

1 Access Rule Sets.


2 Select the Accounts tab.

3 Optional: Select Send All Accounts to export entire entities,

Using Rule Sets 21

4 Optional: Select Browse for List to browse:

a. On Select Database, select a database and click OK.

b. In Select Entity, select an entity and click OK.

c. In Time Period Accounts, select accounts and click > to add them to the rule set.

d. In Entity Scalar Account, select accounts and click > to add them to the rule set.

Selecting the Time Options for Rule SetsYou use the Time tab to select time periods for rule sets.

➤ To select the time options:

1 Access Rule Sets.


2 Select the Time tab.

3 Optional: Click Add to add a scenario type.

See “Adding Scenario Types for Time Rules” on page 23.

4 In Scenario Type, select a scenario type.

5 Optional: Select Use Default to use default time settings.

6 Optional: In Beginning Boundary and Ending Boundary, enter the start and end times.

● You can set boundaries using the time codes. For example, if an entity is in quarters, thetime codes might be Q04 (first quarter of 2004), 2Q04, 3Q04, and 4Q04.

● You can set boundaries using functions. For example, yenter “@firstpd” in the BeginningBoundary and “@lastpd” in the Ending Boundary box to export the entire entity. See “TimeFunctions” on page 24.

7 Optional: Select Synthesize by Aggregate only to roll-up time periods.

For example, week roll-up into months.

8 Optional: Select Export Trailing Periods if Present to include trailing periods.

9 Optional: Select Export Closing Periods if Present to include closing periods.

10 Optional: Select Export Deal Periods if Present to include deal periods.

11 In the time period table, select time periods to include.

Time periods are based on scale:

● Year

● Half-Year

● Quarter

● Month

● Week


a. In Include, select a time period scale.

b. Optional: In Synthesize Period, select time periods that do not exist in the source entity,but must be created for the destination entity.

If the source and target are in different time scales, select a scale to extrapolate from existinginformation into missing time periods.

For example, if an entity is in months but you need weeks in the export, the serversynthesizes week information based on the month information.

c. Optional: In Period to Date, select time periods for which to generate period to dateinformation.

If no Period to Date information exists in the entity, this option synthesizes theinformation. For example, for an export to contain Period to Date information for eachweek, select the Week option.

Selecting Scenario Options in Rule SetsYou use the Scenario tab to select the scenarios for rule sets.

➤ To select scenarios:

1 Access Rule Sets.


2 Select the Scenarios tab.

3 Select a When to Export to determine a time to export scenarios:

● Never

● Always

When the Entity is checked in.

● At Audit Point

Then the entity is archived.

4 Click OK.

Adding Scenario Types for Time Rules

➤ To add scenario types to rule sets:

1 Click Add.

2 In Scenario Type, select a scenario type.

3 Click OK.

Using Rule Sets 23

Time FunctionsYou can use time functions to enter beginning and ending boundaries in rule sets.

● “@basepd” on page 24

● “@closing” on page 24

● “@deal” on page 25

● “@firstfore” on page 25

● “@firstpd” on page 25

● “@lastfore, vXXXX(@lastfore)” on page 26

● “@lasthist, vXXXX(@lasthist)” on page 26

● “@opening” on page 27

● “@period” on page 27

@basepd

Definition

Base period.

Returns

A relative time reference that returns the value for an account in the base period.

Example

If 2007 is the base period, this equation:

v1000(@basepd)

returns the value of Sales (v1000) for 2007.

@closing

Definition

Closing period.

Returns

A relative time reference that returns the value for the closing period of an account.

Example

This formula:

v1000(@closing)

returns the closing period value for Sales (v1000).


@deal

Definition

Deal period.

Returns

A relative time reference that returns the value for the closing period of an account.

Example

This formula:

v1000(@closing)

returns the closing period value for Sales (v1000).

@firstfore

Definition

First forecasted period.

Returns

A relative time reference that returns the first forecasted time period value for an account.

Example

To return the first forecasted period output value for Sales, if the last historical value (e.g. 1999)of sales is 10 and a 10% growth rate in all following periods:

v1000(@firstfore)

The value returned is 11 (10* 1.1) or 2000's sales.

@firstpd

Definition

First period.

Returns

A relative time reference that returns the first period in the model's value for an account.

Example

If 2007 is the first period in the model, the formula:

v1000(@firstpd)

Using Rule Sets 25

return the value for 2007 Sales (v1000). If 2007 is in quarters, Strategic Finance returns the firstquarter for 2007 Sales (v1000).

@lastfore, vXXXX(@lastfore)

Definition

Last forecasted value.

Returns

● The value of an account in the last forecasted period.

● N/A for other periods.

Example

For this formula and values:

v1000(@lastfore)

V1000 1998H 1999H 2000F 2001F 2002F 2003F 2004F

Sales 10 15 16.5 18.15 19.965 21.962 24.158

The formula returns 24.158 in 2004 and N/A in other periods.

@lasthist, vXXXX(@lasthist)

Definition

Last historical value.

Returns

● The value in the last historical period.

● N/A for all periods up to the last historical period.

Example

For this formula and values:

v1000(@lasthist)

V1000 1998H 1999H 2000F 2001F 2002F 2003F 2004F

Sales 10 15 16.5 18.15 19.965 21.962 24.158

The formula returns and N/A in 1998, a 15.000 in 1999 and remaining periods.


@opening

Definition

Opening period.

Returns

A relative time reference that retrieves the value for an account in the opening period. Theopening period is the aggregate of the closing and deal periods. For example, for a deal periodin Mar99, Strategic Finance creates the accounts Mar99:Closing and Mar99:Deal, whichaggregate to Mar99. Mar99 is the opening period.

Example

The formula:

v2000(@opening)

returns the opening period value of Cash (v2000).

@period

Definition

Period number (starting from the first forecasted time period).

This function walks through the aggregates and input columns. The last historical time columnis 0 and increases by 1 each column following.

Returns

True if the period number equals that of a number in an @if function.

Example

@if(@period= 2, 1, 2)

Returns 1 when reaching the second forecasted time column.

Working With Scenario TypesScenarios types are defined on the Strategic Finance server and loaded into clients for use infinancial models, ensuring uniform scenarios through all entities.

● “Managing Scenario Types” on page 28

● “Creating and Editing Scenario Types” on page 28

● “Deleting Scenario Types” on page 28

Working With Scenario Types 27

Managing Scenario TypesYou use the Scenario Types dialog box to create and maintain the scenario types.

➤ To access and manage scenario types, select Server > Scenario Types.

On the Scenario Types dialog box box, you can:

● Create and edit scenario types.

See “Creating and Editing Scenario Types” on page 28.

● Delete scenario types.

See “Deleting Scenario Types” on page 28.

● Reorder the scenario type list.

To reorder the list, select a scenario and click Move Up or Move Down.

Creating and Editing Scenario Types

➤ To edit scenario types:

1 Access Scenario Types.

See “Managing Scenario Types” on page 28.

2 Perform a task:

● To create scenario types, click New.

● To edit scenario types, select one and click Edit.

3 In Scenario Type, enter a name and click OK.

4 In Scenario Types, click OK.

Deleting Scenario Types

➤ To delete scenario types:

1 Access Scenario Types.

See “Managing Scenario Types” on page 28.

2 In Scenario Types, select a scenario type.

3 Click Delete.

4 Click OK.


Configuring and Transferring Server SettingsYou use server settings to adjust server operation.

● “Taskflow for Configuring Server Settings” on page 29

● “Importing and Exporting Server Information” on page 35

Taskflow for Configuring Server SettingsServer settings affect all databases within the server.

➤ To change server settings:

1 Select Server > Settings .

2 Optional: Configure general server settings.

See “Configuring General Server Settings” on page 29.

3 Optional: Configure event log.

See “Configuring Event Log Settings” on page 30.

4 Optional: Configure email.

See “Configuring Email Settings” on page 32.

5 Optional: Configure advanced settings.

See “Configuring Advanced Server Settings” on page 32.

6 Click OK.

Note:

You must restart the HSF Service for these changes to take effect.

Configuring General Server Settings

➤ To configure general server settings:

1 Access Server Settings.

See “Taskflow for Configuring Server Settings” on page 29.


3 Optional: In Default Compression Level, select a compression.

The default compression is used in transferring data with the client.

Default = No Compression

4 Optional: Select Force User's Compression Setting to Client to override client compression with servercompression.

Configuring and Transferring Server Settings 29

Default: off

5 Optional:In Security Mechanism, select a security type.

● Standard NTLM

For stand-alone Strategic Finance implementations.

● External Authentication

For use with Shared Services.

6 In Configuration File, verify the CSS version.

Configuring Event Log SettingsEvent logs settings determine the system activities written to the Event Logs tab.

➤ To configure event log settings:



2 Select the Event Logs tab.

3 Optional: In Enter Number of Days to Retain Logs, enter a number of days to retain the server event logs.

Between 1 and 30.

Default: 14

4 Optional: Select Event Logging On to enable the event log.

Default: Enabled

5 Optional: Select Entity Add/Copy/Delete options:

● Open As Copy

● Copy Local File to Server

● Create New Entity

● Archive Retrieval

● Entity Delete

● Convert Entity

6 Optional: Select Entity Modify options:

● Check-In

● Check-Out

● Save Draft

7 Optional: Select Entity Change Management options:

● Create ECM

● Check out ECM


● Check in ECM

● Run ECM

● Delete ECM

8 Optional: Select Consolidation and Reports options:

● Consolidation

● Global Assumptions

● Freestyle Reports

● Database Export

9 Optional: Select Consolidation Modify options:

● Create Consolidation

● Add to Consolidation

● Delete from Consolidation

● Remove Consolidation

● Paste to Consolidation

● Convert Structure

10 Optional: Select Access options:

● Database Add/Delete

● Modify Access

● Change Ownership

11 Optional: Select Map Activities options:

● Create Map

● Check Out Map

● Check In Map

● Delete Map

12 Optional: Select Batch Activities options:

● Create Batch

● Check Out Batch

● Check In Batch

● Run Batch

● Delete Batch

13 Optional: Select System Activities options:

● Auto-Retrieve Events Display

● Log User Logins

● Log License Activity


● Service Startup

Configuring Email SettingsYou use the Email Configuration to send emails communicating data export success or failure.

➤ To configure email notifications:



2 Select the Email Configuration tab.

3 In SMTP Server, enter the email server IP address.

4 In Sender Email Address, enter the destination email address.

5 Optional: In Sender Name, enter the addressee name.

6 Optional: Configure the resending of undeliverable mail:

● Under Number of Retries for Email Failures, enter a number.

● Under Retry Frequency for Email Failures, enter a number and select a time scale:

❍ Days

❍ Hours

❍ Minutes

7 Optional:If the email server requires a username and password, select My server requiresauthenticationand enter the information:

● Under Username, enter a username.

● Under Password, enter a password.

Note:

Deselecting this option, usernames or passwords deleted.

Configuring Advanced Server Settings

Caution!

Please consult Hyperion Support before configuring advanced parameters to help avoid damageto the system.

➤ To configure register entries:




2 Select the Advanced tab.

3 Optional: In Max number of worker processes, enter a number for the MaxBackgroundWorkersregister.

Defines the number of slots available for simultaneous long runtime background processes suchas database exports, server consolidations, and Entity Change Manager runs.

If the number of long runtime processes exceeds MaxBackgroundWorkers, new processes arequeued until a BackgroundWorker slot becomes available.

Use this equation to estimate the MaxBackgroundWorkers setting:

● For consolidation-intensive servers: (Number of Physical Processors) - 1

● For database export-intensive servers: 2 x (Number of Physical Processors)

4 Optional: In Maximum Intensive Requests, enter a number for the MaximumIntensiveRequestsregister.

Defines the number of slots available on the server for large file operations, such as Entity Check-in/-out. This enables the server to consolidate resources.

If the number of large file operations exceeds the MaximumIntensiveRequests number, theuser receives a message to try again later.

Use this calculation to estimate the MaximumIntensiveRequests setting, where Max.Memory is, by default, 2048 MB:

(Avg. file size x 2) / (Max. memory - 100 MB)

5 In Minimum Free Memory, view the minimum amount of memory designated for use by HSF Service.

The HSF Service buffer size buffer guarding against running out of virtual memory.

6 Optional: From Error Trace Level, select an option for the TraceLevel register.

Determines the amount of information written to HSFData\Admin\Default.log. Messagesare stamped with the server startup date when they are written.

Valid values:

● Normal

Logs nothing.

● Info

Logs all actions.

● Error

Logs error messages only. Recommended.

7 Optional: In Most recent used file list size, enter a number for the MRUListSize register.

The number of entities held open in the server's in-memory cache. Increase this number tospeed-up access to data in recently used-files. Use only if the server machine the memorycapacity.

Default: 5


8 In Server ID, view the server ID.

A unique server ID for controlling the check-in/out of entities. With multiple production servers,use this parameter to assign unique identities:

Default: HYP00001

9 Optional: In Archive Warning Level, set the ArchiveWarningLevel registry.

You use the ArchiveWarningLevel to override the archive check, in case you keep the archiveswithout running the archive repair—see “Inspecting Entity Archives” on page 72

Valid values:

● Silent

Overrides the archive check, enabling the use of out-of-synchronization archives.

● Warn

Enables the use of out-of-synchronization archives, but when a user opens one, a messageis logged.

● Block

When someone tries to open an out-of-synchronization archive, the system displays awarning message and blocks the use of the archive. Default.

10 Optional: Select Insert NULL for root parent in Extended Analytics.

If an entity is a child of a parent in Strategic Finance, a reference to the parent is stored inEntityParentID of the Entity table. If this attribute must be NULL in exports, select thisoption. Default: Selected.

11 In Admin Directory, view the filepath where the administrator information is stored.

Default:

C:\HSFData\Admin

12 In Default Log File, view the filepath where logs are written.

Default:

C:\HSFData\Admin\Default.log

13 In HSF Data Directory view the filepath where HSF data is stored.

Default:

C:\HSFData

14 In Root Directory, view the root directory for the Strategic Finance server.

Default:

C:\HSFData

15 In Log Directory view the filepath where logs are written.

Default:

C:\HSFData

16 In User Log Directory view the filepath where user logs are written.


Default:

C:\HSFData\UserLogs

Importing and Exporting Server InformationYou can export server information from one server to an .xml file, then import that .xml file toanother server.

➤ To export server information:

1 Access Import/Export Server Settings:

● For exporting, select Server > Export Server Info.

● For importing, select Server > Import Server Info.

2 Enter the filepath and filename for the .xml file:

● To export, in Export server settings to, enter the information.

● To import, in Import server settings from, enter the information.

Click Browse to search.

3 Click OK.

4 With a success prompt, click OK.

5 Optional: To switch databases, in Select Database, select a database.

6 Click OK.

Configuring External Connection Settings for Staging DatabasesYou must set external database connectivity for connecting with staging databases.

➤ To configure external connection settings:

1 Select Server > External Connection Settings .

2 In Choose Database Connectivity, select a connection type:

● OLEDB

3 Click OK.

Configuring External Connection Settings for Staging Databases 35

3Working With Databases

In This Chapter

Creating, Selecting, and Deleting Databases on Strategic Finance Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Backing Up, Restoring, and Transmitting Backed Up Databases... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Relational Database Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Extended Analytics.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Databases are repositories for entities, consolidation structures, Entity Change Management(ECM) documents, and maps and batches. You create and maintain databases on StrategicFinance Servers. Multiple databases can reside in a server.

Creating, Selecting, and Deleting Databases on StrategicFinance Servers

● “Creating Databases” on page 37

● “Creating Databases from Consolidation Labels” on page 38

● “Selecting Databases” on page 38

● “Deleting a Database” on page 39

Creating DatabasesYou can create databases for use by Strategic Finance clients in these ways:

● Creating empty databases

● Creating by copying databases with new names

➤ To create databases:

1 From Administrator, select the Databases tab.

2 Select Database > Add.

3 In Database Name , enter a name.

Must be unique within the server.

4 Under Create Database, select a creation method:

Creating, Selecting, and Deleting Databases on Strategic Finance Servers 37

● Select From scratch to create an empty database.

● Select As a copy of an existing database to replicate the orginal database under a new name,and, in Database select the database.

The new database is an exact copy of the selected database, but under the new name

Note:

The runtime of this operation depends on the size of the database.

5 Click OK.

Creating Databases from Consolidation LabelsIf you label a consolidation run in the Strategic Finance client, you cannot change the data orrerun the consolidation under the label. You use Administrator to create a database based onthe label, enabling you to make changes or perform another consolidation run with the copy.When you create consolidation labels, you can create this database for use as a starting point inmodifying the consolidation.

➤ To create database from labels:

1 In Administrator, select Databases.

2 Select Database > Create from Label.

3 In Database name , enter a name.

40 characters maximum

4 In Label, select the consolidation label.

5 Under Archives to include, define how many versions of each entity to include in the new database:

● Select Current Version to include only the latest archive.

● Select Most recent _ archives and enter a number to include a range of archives.

● Select All Archives to include all archives.

6 Click OK.

Selecting Databases

➤ To select databases:

1 From Administrator, select Server > Change Database

2 Select a database.

3 Optional: Click Make Default to designate the default database.

4 Click OK.

38 Working With Databases

Deleting a Database

➤ To delete databases:


2 In Databases, select a database.

3 Select Database > Delete.

Backing Up, Restoring, and Transmitting Backed Up Databases● “Installing PKZip®” on page 39

● “Backing Up Databases” on page 39

● “Transmitting Database Backups” on page 40

● “Scheduling Automatic Archives and Transmissions” on page 41

● “Restoring Databases” on page 41

● “Viewing Error Email Notifications” on page 42

Installing PKZip®You use the PKZip®Command Line for backing up and restoring Strategic Finance databasesthrough Administrator. PKZip can be purchased from www.pkware.com.

Backing Up Databases

➤ To back up databases:

1 In Administrator, select the Databases tab.

2 Double-click a database.

3 Select Database > Backup.

4 In Select Root Entity, select the root entity or entities.

The backup includes all child entities.

● Select All

Backup all entities.

● Deselect All

Deselect entities.

5 Optional: Select Include Locking Information if the entities should remain locked within the backup.

6 Select the number of archives to include:

● Number of Archives

Backing Up, Restoring, and Transmitting Backed Up Databases 39

To include a range of archives, enter a number.

● All Archives

7 In Backup Directory , enter the path to the backup directory.

8 Optional: In Security Password, enter a password to protect the backup.

Note:

The password will be needed again to restore the database, and cannot contain spaces.

9 Click Backup Now to archive the database, or click Save settings to save information.

This information enables scheduled archiving and transmission. See “Scheduling AutomaticArchives and Transmissions” on page 41.

Transmitting Database BackupsYou can transmit backup to different servers.

Note:

The receiving server must function as an FTP server.

➤ To transmit archives:


2 Double-click on a database.

3 Select Database > Send.

4 In Server Name/IP Address, enter the IP Address or domain name of the target server.

5 In Login ID, enter the FTP user ID.

6 In Password, enter the FTP password.

7 In Target FTP Directory , enter the filepath on the destination machine.

Note:

If you do not enter a target FTP directory, the archive is sent to the default directory on the FTPserver.

8 Select an option:

● Select Send a specified file immediately to create a backup .zip file when you click Send.Enter a target filepath and directory in Archive Name.

● Select Save the above data for automatic backup to save this information and that on theBackup a Database box, as a single event that you can active from a command line or run.See “Scheduling Automatic Archives and Transmissions” on page 41.

9 Click Send or Save.


Note:

This button changes given the Action. If you select Send a specified file immediately, this buttonis Send. If you select Save the above data for automatic backup, this button is Save.

Scheduling Automatic Archives and TransmissionsIf you save the Backup Database and Sending Data settings, you can schedule archival ortransmission. You can run archives or transmissions at any time from the command line afterthese settings are saved.

➤ To schedule an archive and transmission:

1 From the desktop, select Start > Settings > Control Panel > Scheduled Tasks.

2 In Scheduled Tasks, double-click Add Scheduled Task.

3 In Scheduled Task Wizard, click Next.

4 Click Browse and locate HSFAdmin.exe.

Note:

The default location is C:\Program Files\Hyperion\Strategic Finance\Release\Admin, where Release is a variable representing the number of the current release.

5 Select a frequency to run the task, then click Next.

6 Select the time that the task should run, select a start date, and click Next.

7 Enter a valid user and password, then click Next.

8 Select open advanced properties for this task when I click Finish, then click Finish.

9 In Run, add this:

HSFAdmin.exe/auto/db name

where name is the database name.

➤ To run an archive and transmit only once:

1 Select Start > Run.

2 In the command line, type:

C:>HSFAdmin.exe/auto/db name

where name is the database name.

Restoring DatabasesWhen a database is archived with a date-stamped ZIP file, it can be restored . If the databasedoes not exist, create a database with the same name.

Backing Up, Restoring, and Transmitting Backed Up Databases 41

➤ To restore databases:


2 Double-click on a database.

3 Select Database > Restore.

4 In Directory/Filename of Archive, enter the filepath and name of the backup .zip file.


5 Optional: Select Restore Locks to restore the archived lock information.

6 Optional: Select Completely replace the current database to replace all current entities with those in thebackup .zip file.

Note:

Leaving this check box unchecked replaces only the entities for which an archived version isavailable.

7 Click Restore.

Viewing Error Email Notifications

➤ To view error email notifications:


2 Select Database > External Database.

3 By Email Addresses, click ....

The Receiver Email Addresses list box displays the User ID, Full Name, and Email Address allmessages.

4 Click OK.

Relational Database ExportYou can export entities to external databases. For creating relational export databases, see theHyperion Strategic Finance Installation Guide.

External database connections require rule sets. See “Using Rule Sets” on page 20.

● “Creating Connections to External Databases” on page 43

● “The Export Database Tables” on page 44


Creating Connections to External Databases

➤ To create external database connections:



3 In HSF Database, select a database.

4 In Connection Type, select an option:

● Export

● Import

N/A

● Extended Analytics

For use with Extended Analytics. See “Creating Extended Analytics Rule Sets” on page50 and “Extended Analytics” on page 47.

● In Data source , enter the data source.

Note:

With Extended Analytics, this text box becomes Connection String. Enter the connectionstring used to access the database.

If use Extended Analytics, use this format to enter a connection string:

Provider=’<type>’;Data Source=’<servername>’;Initial Catalog='<dbname>';

Use these variables:

● <type> = the type of database server and connection

● <servername> = the name of the database server

● <dbname> = the name of the target database

Note:

If you are using Oracle, do not use the Initial Catalog variable.

5 In User I.D., enter the user name or owner for accessing the destination database.

6 In Password, enter the password for accessing the target database.

7 In Rule Set Name, enter the Rule Set to be used in transfer. Disabled from Extended Analytics.

8 In Email Addresses , enter email addresses to send data transfer error messages.

9 Select Database Connectivity Enabled to enable the database connection.

10 Click OK.

Relational Database Export 43

The Export Database TablesExport formats data into the relation tabled in Figure 4 on page 44.

Figure 4 Relational Export Tables

● “Financial Data Available Table” on page 44

● “Entity Scalar Table” on page 45

● “Variable Info Table” on page 45

● “Financial Variable Table” on page 46

● “Alcrdt Translation Table” on page 46

Financial Data Available TableStores header information about each transaction and contains information about the sourceentity and database.


Table 1 The Financial Data Available Table

Attribute Data Type Definition

Transaction Id bigint Identifies the transaction

Checked In User Id varchar The last user to check the entity in to the server

Data Available Dt datetime The data that is available

Alcar Db varchar The source Strategic Finance database

Entity Id int Identifies the entity

Entity Name varchar The entity name

Records Expected int The records that should be present

Transaction State Cd char The transaction state

Transaction Error Cd int Errors

Transaction Type char The transaction type

Parent Transaction Id varchar The transaction ID related to the parent entity

Entity Scalar TableContains scalar values, which are not tied to time periods.

Table 2 The Entity Scalar Table



Variable Id bigint Identifies the variable

Result varchar Data if value is alphanumeric

Result Numeric decimal Data if value is a number

Variable Info TableContains variable data (accounts).

Table 3 The Variable Info Table




Variable Desc varchar Text description of variable

Relational Database Export 45


Native Data Type Cd char Code for the native data type

Aggregation Rule Cd char Code for the aggregation rule

Item Scale Cd char Code for the scale

Display Scale decimal Scale for display of output

Financial Variable TableContains financial values with each row in the table containing a single exported cell fromStrategic Finance.

Table 4 The Financial Variable Table




Scenario Name varchar The scenario of the exported financial model

Fin Fact Alcrdt varchar Financial fact

Scenario Type Desc varchar Description of the scenario

Result varchar Data if value is alphanumeric

Result Numeric decimal Data if value is a number

Alcrdt Translation TableUsed to translate Strategic Finance date labels into true calendar dates.

Table 5 The Alcrdt Transaction Table



Fin Fact Alcrdt varchar Financial fact

Period End Dt Txt datetime Ending period

Period End Dt Txt varchar Ending period in Strategic Finance entity

Data Source char Source of the data


Extended AnalyticsYou use External Analytics to export a group of entities as a star schema to relational databases,for use by other Hyperion products. Figure 5 on page 47 illustrates the flow and use of ExtendedAnalytics data.

Figure 5 Extended Analytics Components and Data Flow

External Analytics works like this:

● The External Extended Analytics Database (Star Schema)

You use Extended Analytics create an external database connection and rule set, and exportthe data. The rule set is specific to the database in which it is created, and each has only one.When you create and populate the Extended Analytics database on the external, the tablelayout is a star schema.

● Reporting with Hyperion System 9 BI+

Some Hyperion System 9 BI+ modules can report directly from the star schema data. See“Reporting Utilities for Use with Extended Analytics” on page 48.

● Optional: Reporting with Analytic Services

From the star schema database, you use Analytic Integration Services to transfer the datainto a multidimensional Oracle's Hyperion® Essbase® – System 9 database, from which otherHyperion System 9 BI+ Modules or Oracle's Hyperion® Smart View for Office can report.See “Reporting Utilities for Use with Extended Analytics” on page 48.

● Optional: Using a Reference Database

Create a separate Strategic Finance reference database and copy the entities from multipleStrategic Finance databases for reporting out of a central location. Because these entities areisolated, you can change the numbers in the financial models to analyze possibilities withoutaffecting your production data. You can refresh referenced entities.

Extended Analytics 47

Before using Extended Analytics, you must create an Extended Analytics connection to anexternal relational database. See “Creating Connections to External Databases” on page 43.

● “Reporting Utilities for Use with Extended Analytics” on page 48

● “Taskflow for Extended Analytics” on page 48

● “Configuring External Extended Analytics Databases” on page 49

● “Creating Extended Analytics Rule Sets” on page 50

● “Optional: Creating Reference Databases and Entities” on page 53

● “The Extended Analytics Star Schema” on page 54

Reporting Utilities for Use with Extended AnalyticsYou can use these Hyperion System 9 BI+ Modules directly off the star schema server, or withEssbase:

Hyperion System 9 BI+

Module

Relational Database

(Star Schema)

Essbase

Hyperion Analytic Integration

Hyperion System 9 Interactive Reporting™ Yes No

Oracle's Hyperion® Smart View for Office No Yes

Oracle's Hyperion® Financial Reporting – System 9 No Yes

Hyperion System 9 Web Analysis™ No Yes

Taskflow for Extended Analytics

➤ To use Extended Analytics:

1 Optional: Create a reference database.

See “Optional: Creating Reference Databases and Entities” on page 53.

2 Create an empty relational database.

See your RDBMS server documentation.

3 Create an Extended Analytics external database connection.

See “Creating Connections to External Databases” on page 43.

4 Configure the external Extended Analytics database (Star Schema).

See “Configuring External Extended Analytics Databases” on page 49.

5 Define the time periods, accounts, and general information for the export in the Extended Analytics rule set.

See “Creating Extended Analytics Rule Sets” on page 50.

6 Specify the entities for exporting.


See “Optional: Creating Reference Databases and Entities” on page 53.

7 Optional: Export from the relational database to Essbase.

Configuring External Extended Analytics DatabasesBefore exporting with Extended Analytics, you configure the external database (star schema) onthe relational database server.

Note:

Before you can create the tables in the relational database server, create a link to the externaldatabase server. See “Creating Connections to External Databases” on page 43.

➤ To create Extended Analytics tables:

1 Select the Databases tab.


3 Select Database > Extended Analytics > External Database Configuration.

4 Optional: Under User-Defined Columns for Entity Table, create user-defined columns.

You use User-Defined Dimensions tables to filter data, for client-defined field, or scalar accountsin Strategic Finance. See “Uddim Tables 1-4” on page 58.

● In Column to Add, enter name.

● In Column Data Type, select a data type.

Must be the same data type as the corresponding account inStrategic Finance. Data types:

❍ Text

❍ Date

❍ Numeric

● To add the column, click >.

● To remove a column, select one and click <.

● Up to 20 user-defined columns

● User-defined columns are in the Entity Table of the star schema database. See “Entity Table”on page 56.

● After user-defined columns are created, “Setting Extended Analytics Rule Sets AccountsOptions” on page 51 includes an option for mapping accounts from the source StrategicFinance entity to the star schema database.

5 Click Create Tables.

6 Click OK.


Creating Extended Analytics Rule SetsExtended Analytics rule sets define metadata of the exported entity.

➤ To create Extended Analytics rule sets:

1 Select Databases.

2 On Databases, double-click a database.

3 Select Database > Extended Analytics > Rule Sets.

4 Select general options.

See “Setting Extended Analytics Rule Sets General Options” on page 50.

5 Select accounts.

See “Setting Extended Analytics Rule Sets Accounts Options” on page 51.

6 Select time periods.

See “Setting Extended Analytics Rule Sets Time Options” on page 51.

7 Select scenarios.

See “Setting Extended Analytics Rule Sets Scenarios Options” on page 52.

8 Select custom dimensions.

See “Setting Extended Analytics Rule Sets Custom Dimensions” on page 53.

9 Click OK.

Setting Extended Analytics Rule Sets General Options

➤ To select general options:

1 Access Edit Rule Set.



3 Optional: Select Export Entity on Create to export entities when they are created.

4 Optional: Select Do not export when funds flow out of balance to block exporting when funds flows areunbalanced.

5 Optional: Select Calculate Scenarios on Export to calculate all scenarios before exporting.

Note:

Required, unless you Scenario Manager on the Strategic Finance client is configured to use theStore outputs for all accounts on the Outputs tab.


Setting Extended Analytics Rule Sets Accounts OptionsYou use the Accounts tab to define the Accounts table—see “The Extended Analytics StarSchema” on page 54.

➤ To select accounts:




3 To select an entity, click Browse for List.

4 To add accounts, in Time Period Accounts, select accounts and click >.

5 Optional: Map user-defined columns in the star schema database with scalar values in the source StrategicFinance entity:

● To add accounts, in Entity Scalar Accounts, select accounts and click >.

● For each account number in Account ID, enter the corresponding target column name inEntity Table Column Label.

● This maps scalar values from the Strategic Finance entity to any user-defined columnscreated in “Configuring External Extended Analytics Databases” on page 49.

● These mappings populate custom columns in the Entity Table of the star schema database.See “Entity Table” on page 56.

Setting Extended Analytics Rule Sets Time OptionsYou use the Time tab to select the time periods to populate the Time table—see “The ExtendedAnalytics Star Schema” on page 54.

➤ To select time periods:




3 Optional: In Beginning Boundary and Ending Boundary, enter the start and end times.

● You can set boundaries using the time codes. For example, if an entity is in quarters, thetime codes might be Q04 (first quarter of 2004), 2Q04, 3Q04, and 4Q04.

● You can set boundaries using functions. For example, yenter “@firstpd” in the BeginningBoundary and “@lastpd” in the Ending Boundary box to export the entire entity. See “TimeFunctions” on page 24.

4 Optional: Select Synthesize by Aggregate only to roll-up time periods.

For example, week roll-up into months.

5 Optional: Select Export Trailing Periods if Present to include trailing periods.


6 Optional: Select Export Closing Periods if Present to include closing periods.

7 Optional: Select Export Deal Periods if Present to include deal periods.

8 In the time period table, select time periods to include.

Time periods are based on scale:

● Year

● Half-Year

● Quarter

● Month

● Week

a. In Include, select a time period scale.

b. Optional: In Synthesize Period, select time periods that do not exist in the source entity,but must be created for the destination entity.

If the source and target are in different time scales, select a scale to extrapolate from existinginformation into missing time periods.

For example, if an entity is in months but you need weeks in the export, the serversynthesizes week information based on the month information.

c. Optional: In Period to Date, select time periods for which to generate period to dateinformation.

If no Period to Date information exists in the entity, this option synthesizes theinformation. For example, for an export to contain Period to Date information for eachweek, select the Week option.

Setting Extended Analytics Rule Sets Scenarios OptionsYou use the Scenario tab to select the scenarios to populate the Scenario table of the star schemadatabase—see “The Extended Analytics Star Schema” on page 54.





3 For each type underScenario Type , select an option under When to Export:

Note:

See “Working With Scenario Types” on page 27.

● Never

Not exported


● Always

Exported when the entity is checked in.

● At Audit Point

Exported when an audit point is archived.

Setting Extended Analytics Rule Sets Custom DimensionsYou use the Custom Dimensions tab to create dimensions populating the User-DefinedDimensions table of the star schema database—see “The Extended Analytics Star Schema” onpage 54.




2 Select the Custom Dimensions tab.

3 Enter the dimension structure, for example:

● User Defined Dimension 1: ‘Product’

● User Defined Dimension 2: ‘Region’

● User Defined Dimension 3: ‘Division’

● User Defined Dimension 4: ‘Team’

Optional: Creating Reference Databases and EntitiesTo ensure data integrity by isolating the original production data, create a reference database.Reference entities have links to production entities so you can refresh them with productiondata.

➤ To create reference databases and entities:

1 Select Databases.

2 Create database.

See “Creating Databases” on page 37.

3 In Databases, double-click the database.

4 Select Database > Entity Reference.

5 In Select Database, select the source database.

6 Optional: In Existing Entities, select entities and click >.

7 Optional: In Existing Entity Groups, select entity groups and click >.

8 Refresh entities:

● To refresh all entities, click Refresh All.


● To refresh some entities or entity groups, select them and click Refresh Selected.

9 Click OK.

The Extended Analytics Star SchemaData exported to an Extended Analytics star schema database is formatted into the tables inFigure 6 on page 54.

Figure 6 Extended Analytics Star Schema Database Tables


● “Fact Table” on page 55

● “Header Table” on page 55

● “Analysis Table” on page 56

● “Entity Table” on page 56

● “Scenario Table” on page 57

● “Account Table” on page 57

● “Time Table” on page 58

● “Uddim Tables 1-4” on page 58

● “Transaction Table” on page 58

Fact TableFact is the central control table, relating all other tables. It coordinates the other star schematables to create and populate multidimensional databases in Oracle's Hyperion® Essbase® –System 9 . The Fact table contains the exported data—each row is a single data cell, using thenames stored in the outlying tables.

Table 6 The Fact Table


AnalysisID int References the Analysis table.

EntityID int References the Entity table.

ScenarioID int References the Scenario table.

AccountID int References the Account table.

TimeID int References the Time table.

UDDim1 int References the User-Defined Dimension table 1.




DataValue numeric Stores numeric values

DataStringValue nvarchar Stores string values

Header TableThe Header table stores heading information for the entity and User-Defined Dimension tables.


Table 7 The Header Table


HeaderID int A key identifying a specific header.

HeaderName nvarchar Stores this data:

● 0: The rule set name (database name).

● 1– 4: Store the name of each User-Defined Dimension. See “Uddim Tables 1-4” onpage 58.

HeaderValue nvarchar The header string

Analysis TableThe Analysis table stores information identifying a specific analysis.

Table 8 The Analysis Table


AnalysisID int A key identifying a specific analysis.

AnalysisLabel nvarchar The label string.

Entity TableIdentifies the source entity in Strategic Finance.

Table 9 The Entity Table


EntityID int A key identifying a specific entity within the table.

EntityLabel nvarchar A string storing a label for the entity.

ServerID nvarchar A string identifying the Strategic Finance servercontaining the entity.

DatabaseName nvarchar A string identifying the source database containingthe entity.

EntityParentID int For child entities in the Strategic Finance database,this is a key referencing the parent entity.

EntityParentLabel nvarchar A string storing a label for the parent entity.

User-defined columns varies

The same data type in source entity.

This table stores each of up to 20 custom columns.

● See “Configuring External Extended AnalyticsDatabases” on page 49.

● See “Setting Extended Analytics Rule SetsAccounts Options” on page 51.


Scenario TableIdentifies the scenarios in the entity.

Table 10 The Scenario Table


ScenarioID int A key identifying a specific scenario in the table.

ScenarioLabel nvarchar A string storing the name of the scenario.

ScenarioType nvarchar A string storing a description of the scenario.

Account TableIdentifies the accounts in the entity.

Table 11 The Account Table


AccountID int A key identifying a specific account in the entity.

AccountLabel nvarchar A string containing the name of the account.

NativeDataType nvarchar Indicates the data type stored in the account.

Valid Values:

● N - number

● S - string

AggregationRule nvarchar Stores the aggregation rule.

Valid Values:

● N

Non-account

● B

Balance

● F

Flow account

● A

Rate

● D

Discount rate

● R - r

Ratio

AccountParentID int For related accounts and subaccounts, this stores the key of the account to whichthis specific account aggregates.


Time TableIdentifies the time periods used in the entity .

Table 12 The Time Table


TimeID int A key identifying a specific time period.

TimeLabel nvarchar A string name for the time period.

RealTime datetime A value indicating if the time period is real time.

TimeParentID int If a time period aggregates to another, this stores the key of the aggregatingtime period.

TimeSiblingSortOrder int If time periods are sibling, this stores the order in which they belong.

Uddim Tables 1-4Identifies User-Defined Dimensions in the entity.

Table 13 Uddim Table 1-4


MemberID int A key identifying a specific dimension value.

MemberLabel nvarchar A string storing the dimension value.

ParentID int A reference to the parent dimension key.

Transaction TableIdentifies transaction for the entity at its state upon export.

Table 14 The Transaction Table


TransactionID int A key identifying a specific transaction.

HSFTransID nvarchar Identifies the transaction number of the export transaction in Strategic Finance.

AnalysisID int A reference to the Analysis table.

ExportDate int The date of export.

HSFArchiveNumber int Stores the archive number.

UserName nvarchar Stores the username of the user who performed the transaction.

ServerID nvarchar A string identifying the sourceStrategic Finance server.



DBName nvarchar A string identifying the source database.

PushType nvarchar Identifies the event triggering the transaction. For example, consolidation run,entity check in, etc.


4Managing Users and User

Groups

In This Chapter

Managing Users .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Managing User Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

You use Administrator to grant user access to Strategic Finance. Users are selected from theservice provider (Standard NTLM or Common Security Service (CSS)) of the network domain.You create user groups to groups to bulk-manage users sharing the same privileges.

You must decide:

● How to set up security

● What access control to give user groups

● Which users to assign to groups

Access type determines user privileges to define tasks a user can perform in a server, database,or entity.

Consider:

● Which users to include

● Which user groups to create

● Which users to include in each group

● Which access types to assign to each user and user group

● Other access privileges for each server and database

When you add a user or create a user group, you must define the access control—see Chapter 6,“Providing Access to Databases and Entities”.

Managing UsersStrategic Finance uses a service provider to authenticate users, so Strategic Finance must existin the network domain. You assign user basic access types to determine the general access, andyou use the Edit Access dialog to refine access on a database, entity, or entity group level.

● “User Types” on page 62

● “Adding and Editing Users” on page 62

Managing Users 61

● “Looking Up Users in External Authentication” on page 63

● “Renaming Users or Changing Network Domains” on page 64

● “Deleting Users” on page 65

● “Viewing License Information” on page 65

User TypesUser types determine general access:

User Type Privileges Tasks

Administrator Unrestricted ● Add and maintain servers

● Add and maintain databases

● Add and maintain users

● Add and maintain user groups

● Create and maintain entities

● Design and view reports

Interactive User Restricted ● Create and maintain entities

● Enter data into entities

● Add scenarios

● Add subaccounts

● Add dimensions

● Design and view reports

Basic User Restricted ● Enter data into entities

● Add scenarios

● Add subaccounts

● View reports

View User Restricted ● View entities

● View reports

Adding and Editing Users

➤ To add or edit users:

1 In Administrator, select Users.

2 Optional: To edit users, select a name in User.

3 Perform a task:

● To add users, select User > Add.

● To edit users, select User > Edit.

62 Managing Users and User Groups

4 Enter the domain name or the user ID.

● Domain Name (Standard NTLM only)

The domain name of the the NTLM Directory Server. Click ... to search.

● User ID (Single sign-on only)

A unique name identifying the user within the server. Click Lookup User to search. See“Looking Up Users in External Authentication” on page 63.

5 Enter the user name or identity.

● User Name (Standard NTLM only)

Select the name of the user in the NTLM Directory Server. Click ... to search.

● User Identity (Single sign-on only)

The Security Identifier (SID) number of the user within the directory server. Read-only.

6 In Full Name , enter the first and last name of the user.

7 In Access Type, select an user type for general access:

● Power Manager

● Interactive User

● Basic User

● View User

● None

● See “User Types” on page 62.

8 Optional: In Compression Level, select a data compression level.

9 Optional: In Email Address, enter an email address for user notification.

Note:

To send a test email, click Send Email.

10 Optional: In Phone Number, enter a phone number.

11 Optional: In Notes , enter additional information.

12 Click OK.

Looking Up Users in External AuthenticationYou use the Lookup User dialog box to indicate a Security Provider and search for users.

Note:

The Lookup User dialog box is available only when External Authentication is configured.

Managing Users 63

➤ To search for users:

1 In Security Provider, select the security provider.

Each Security Provider should have a Directory Server, and list all users defined on that server.

● ALL

Users from all providers.

● <Name of Security Provider>

Security provider names as listed in the configuration file.

2 Optional: Select User Name tand enter the name to search by user name.

If you are unsure of the name, you use a wild card (*). For example: “St*” returns “Steve” and“Stephanie”.

The User Name text box follows these rules:

● The only search for an NTLM Security Provider.

● Wild cards can be used alone or in a string, but never as the first character of a string.

3 Optional: Select First and Last Name and enter their first and last name to search for a user by real name .

First and last names are required.

Note:

This does not work with NTLM Security Providers, and does not take wild cards.

4 Optional: Select Email Address and enter an email to search by email.

Note:

Not supported with NTLM Security Providers and wild cards.

5 Click Lookup.

6 In Results, select a user and click OK.

● Up to 100 results listed at a time.

● Only one user may be selected at a time.

Renaming Users or Changing Network DomainsIf the network domain or user IDs within the service provider, you use Rename User. When youchange the name or domain of a user, Rename User checks all user names to ensure it is unique.It searches User Groups, locks, entity and database owners, ECM docs, access records, and free-standing records to replace all instances of the old name with the new name.

➤ To rename user or change the network domain:


2 In User, select a name.


3 Select User > Rename User.

4 In New Domain Name, enter the domain name (Standard NTLM only).

Click ... to search available domains.

Note:

Not displayed under Single Sign-on.

5 In New User Name, enter a name.

Click ... to search.

6 Click OK.

Deleting Users

➤ To delete usesr:



3 Select User > Delete.

Viewing License Information

➤ To view license information:


2 Select User > License Information.

3 Click OK.

Managing User Groups● “Creating User Groups” on page 65

● “Adding Users to User Groups” on page 66

● “Deleting Users from User Groups” on page 66

● “Deleting User Groups” on page 66

Creating User GroupsYou bulk-manage users with user groups.

Managing User Groups 65

➤ To create user groups:


2 Select Groups > Add.

3 In Group Name, enter a name.

4 Optional: From Copy Membership From , select a source group from which to copy users.

Note:

Selecting None creates a new group with no members.

5 Click OK.

Adding Users to User Groups

➤ To add users to user groups:



3 Select Groups > Add User.

4 In Groups, select a group.

5 Click OK.

Deleting Users from User Groups

➤ To delete users from user groups:


2 In Group, select a group.

3 In User, select a user.

4 Select Groups > Delete User.

Deleting User Groups

➤ To delete user groups:


2 In Group, select a group.

3 FSelect Groups > Delete.


5Managing Entities and Entity

Groups

In This Chapter

Managing Entities .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Managing Entity Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Setting Entity Check-In Rules and Managing Archives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Entities are Strategic Finance (*.alc) files stored in the server. You use entity groups to bulk-manage entities.

Managing EntitiesBefore you can access entities, select a database.

● “Accessing Entities” on page 67

● “Changing Entity Owners” on page 67

● “Breaking Entity Locks” on page 68

● “Manually Exporting Entities” on page 68

● “Converting Entities After an Upgrade” on page 68

Accessing Entities

➤ To access entities:

1 In Administrator, select Database.


3 Select Entities.

Changing Entity Owners

➤ To change entity owners:

1 In Administrator, select Entities.

Managing Entities 67

2 Select an entity or batch.

3 Select Edit > Owner.

4 In Domain Name for New Owner, enter the network domain.


5 In User Name for New Owner, enter a user name.

6 Click OK.

Breaking Entity Locks

➤ To break entity locks:


2 Select the locked entity in the entity tree.

3 Select Edit > Break Lock.

Manually Exporting Entities

➤ To export entities:

1 Select Entities.

2 Select an entity.

● Press <Shift> to select a range of entities.

● Press <Ctrl> to select specific entities.

3 Select Edit > Export.

Manually Exporting Extended Analytics

➤ To manually export entities to Extended Analytics:

1 Select Entities.

2 Select an entity.

● Press <Shift> to select a range of entities.

● Press <Ctrl> to select specific entities.

3 Select Edit > Extended Analytics Export.

Converting Entities After an UpgradeIn upgrading from Alcar versions 2.x or 6.x, you use the convert feature to upgrade existing data.

68 Managing Entities and Entity Groups

● “Converting Database Entities in Bulk” on page 69

● “Converting Selected Entities” on page 69

Converting Database Entities in Bulk

➤ To convert the entire database in bulk:


2 Select Edit > Convert > All.

Converting Selected Entities

➤ To convert only specific entities:


2 Select one or more entities.

3 Select Edit > Convert > Selection.

Managing Entity GroupsYou use entity groups to bulk-manage entity access.

● “Adding Entity Groups” on page 69

● “Editing Entity Groups” on page 70

● “Deleting Entity Groups” on page 70

Adding Entity Groups

➤ To add entity groups:

1 In Administrator, select Entity Groups.

2 Select Group > Add.

3 In Add an Entity Group, enter a name.

4 Click OK.

5 Add entities.

See “Editing Entity Groups” on page 70.

Managing Entity Groups 69

Editing Entity Groups

➤ To edit an entity group:

1 In Administrator, select Entity Groups.

2 In Entity Group Name, select an entity group.

3 Select Group > Edit.

4 In Edit Entity Group, add or remove entities:

● Entities Available

Entities that are not part of the group, but may be added. Select one and click Add>>.

● Group Members

Entities in the entity group. To remove, select one and click <<Remove.

5 Click OK.

Deleting Entity GroupsThis delete all access privileges associated with all of the entities previously in this group. Theentities remain.

➤ To delete entity groups:

1 Select Entity Groups.

2 In Entity Group Name, select an entity group.

3 Select Group > Delete.

Setting Entity Check-In Rules and Managing ArchivesArchive and check-in rules are enforced when users check entities in to the server. You caninspect and repair archives.

● “Setting Entity Check-In Rules” on page 70

● “Managing Entity Archives” on page 71

● “Inspecting Entity Archives” on page 72

Setting Entity Check-In RulesCheck-in rules require a user to perform actions when they check in entities.

➤ To set entity check-in rules:



2 Select Edit > Check-In Rule.

3 Select the rules:

● Require comments at check-in

Forces users to enter comments explaining the state of the entity before the server allowscheck-in.

4 Click Close.

Managing Entity ArchivesArchive entity rules define entity version tracking, and can apply to all entities in a database orto a single entity.

➤ To set archive entity rules:


2 Optional: In the entity tree, select an entity.

To apply archive rules to a specific entity.

3 Select Edit > Archive Rules.

4 In Manage Archive Files, select an extent for the policy:

● Set Default Policy

Set the default policy applied to all entities.

● Individual Entity Archive Policy

Set the archive rules for specific entities.

5 Define archive rules:

● Use Default

Apply the default archive rules.

● Delete archive files after _ days

Delete archives after a number of days. Enter a number.

● Keep _ most recent archive files

Delete archives over a given number. Enter a number.

● Do not delete archive files

Never delete archived entities.

6 Optional: Click Show only entities that override a default setting to display only entities with overriddenarchive policies.

7 Optional: For damaged archives, select one and click Repair.

See “Inspecting Entity Archives” on page 72.

8 Click Save Settings.

Setting Entity Check-In Rules and Managing Archives 71

9 Click Close.

Inspecting Entity ArchivesStrategic Finance uses Archive Repair to fix archive numbers. When the archive and versionnumbers are out of synchronization, you cannot open the archive until Archive Repairresynchronizes them. When you run Archive Repair on an archived entity, the proper versionnumbers are restored and the archive is stored under a new filename.

Caution!

There are issues to consider before repairing archives. Consult Hyperion support before usingArchive Repair.

Because the repaired data is stored under a new filename, you may not want to repair the archive.For example, if you have FreeStyle Reports using Alias Manager to reference specific archivedentities, those references may break with Archive Repair.

When this happens:

● If you repair the archives, open the FreeStyle Report and manually change the alias toreference the new filename.

● If you do not repair the archives, you can use them to keep your FreeStyle Reports.

If you do not repair an archive, use the Archive Warning Level to override the archive check—see “Configuring Advanced Server Settings” on page 32.

➤ To inspect archives:


2 Select a database

3 Select the Entities tab.

4 select an entity.

5 Select Edit > Inspect Archive Contents.

6 Optional: Under Suspect, verify archive contents.

If an archive has an X under the Suspect column, it is corrupt. To fix these archives, use ArchiveRepair in “Managing Entity Archives” on page 71.

7 Click OK.


6Providing Access to Databases

and Entities

In This Chapter

Configuring General Database SettingsAccess... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Configuring Default Access to Databases, Entities, and Entity Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Adding Users and User Groups to Databases, Entities, or Entity Groups ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Default access is determined by user type, but you can refineaccess using Edit Default. You canmanage individual users, or bulk-manage users with user groups.

● Owner defines access for database owners

● Default defines access for standard users

Configuring General Database SettingsAccessYou can configure access at the database level, for specific users or user groups, or for defaultsettings.

● “Configuring General Database Access for Users and User Groups” on page 73

● “Assigning Database General Options to Users and User Groups” on page 74

Configuring General Database Access for Users and UserGroups

➤ To configure general database access:

1 Select Databases.


3 Select Access > Database Options.

4 Select Create / Edit Access.

When first installed, only the <Default> user is available.

5 Optional: Add users or user groups to the Create / Edit Access tab:

● To add users, see “Adding Users” on page 83 for instructions.

Configuring General Database SettingsAccess 73

● To add user groups, see “Adding User Groups to Databases, Entities, or Entity Groups” onpage 84 for instructions.

6 Optional: To set general access options for the default user, a specific user, or a specific user group, selectone in Edit Database Options for <databaseName>:

● Select <Default> to set the default access.

● Double-click Users or Groups to open browse and select.

7 Optional: Configure general database access.

See “Assigning Database General Options to Users and User Groups” on page 74.

8 Optional: To delete a user or group, in Edit Database Options for <databaseName>, select one and clickDelete.

9 Click OK.

Assigning Database General Options to Users and UserGroups

➤ To configure database general options:

1 In Create / Edit Access, select a user or user groupand click Edit.

2 Select the Database General tab.

3 Optional: Select View this Database to enable users to view the database.

4 Optional: Select Place at Root to enable users to create or add and entity as a root or parent.

5 Optional: Select Allow Entity Change Management to enable Entity Change Management.

6 Optional: Select Allow Assumptions Change Management to enable Assumptions Change Management.

7 Optional: Select Copy Local File to Server to enable users to copy local Strategic Finance (.alc) files tothe server.

8 Optional: Select Can create Server-based Maps to enable users to create import and export maps.

9 Optional: Select Can create Batches to enable users to create import and export batches.

10 Click OK.

Configuring Default Access to Databases, Entities, and EntityGroups

You use the Edit Default Access dialog box to assign access privileges to the Owner, Users, UserGroups, and the Default.

Note:

You can add Users and Groups from the Edit Default Access dialog box. U

74 Providing Access to Databases and Entities

● “About Assigning Default Access” on page 75

● “Configuring Entities Access Options” on page 76

● “Configuring Accounts Access Options” on page 77

● “Configuring Time Access Options” on page 78

● “Configuring Reports Access Options” on page 79

● “Configuring Scenario Access Options” on page 80

● “Configuring Consolidation Access Options” on page 81

● “Configuring Reference Access Options” on page 81

● “Configuring Default Access for New Entities” on page 82

● “Adding Permissions Groups” on page 78

About Assigning Default AccessYou use Edit Default Access to configure access for users or user groups to databases, entities,or entity groups. The context is determined by how you access the tab:

● For databases, on the Databases tab select the database, and select Access > Edit Default .

● For entities, on the Entities tab select entities and select Edit > Access .

● For entity groups, on the Entity Groups tab select a group, and select Group > Access .

➤ To configure access for users or user groups to databases, entities, or entity groups:

1 Select Databases.


3 Optional: Perform an action:

● To configure access to an entity, select Entities, and then an entity.

● To configure access to an entity group, select Entity Group, and then the entity group.

4 Perform an action:

● For a database, select Access > Database Options .

● For a database, select Access > Edit Default .

● For an entity, select Edit > Access .

● For an entity group, select Group > Access .

5 Optional: Add users or user groups to Edit Default Access.

● To add users, see “Adding Users” on page 83 for instructions.

● To add user groups, see “Adding User Groups to Databases, Entities, or Entity Groups” onpage 84 for instructions.

6 Optional: To delete users or groups, in sEdit Database Options, select one and click Delete.

7 In Edit Default Access, select a user or group:

Configuring Default Access to Databases, Entities, and Entity Groups 75

● <Owner>

Default for the database owner.

● <Default>

Default for all users.

● Under Users , click + and select a user.

● Under Groups, click +, and select a group.

8 Optional: To edit default access options, click Edit and select options:

● Configure entity access options.

See “Configuring Entities Access Options” on page 76.

● Configure accounts access options.

See “Configuring Accounts Access Options” on page 77.

● Configure time access options.

See “Configuring Time Access Options” on page 78.

● Configure Scenario access options.

See “Configuring Scenario Access Options” on page 80.

● Configure dimension access options.

See “Configuring Dimension Access Options” on page 80.

● Configure Consolidation access options.

See “Configuring Consolidation Access Options” on page 81.

● Configure reference access options.

See “Configuring Reference Access Options” on page 81.

● Configure reports access options.

See “Configuring Reports Access Options” on page 79.

9 Optional: Select New Entities to define access options for new entities.

See “Configuring Default Access for New Entities” on page 82.

10 Click OK.

Configuring Entities Access OptionsYou use the Edit Default Access—Entities tab to secure user access at the entity level.

➤ To configure entity-level access:

1 Access Edit Default Access for <databaseName/entityName/entityGroup>.

See “About Assigning Default Access” on page 75.

2 Select the Entities tab.


3 Select an Access option:

● None

Users cannot check entities out.

● Open As Copy

Users can check entities out.

● Check out Entity

Users can check entities in and out.

4 Optional: Select Read Entity Comments to enable users to read entity check-in comments.

5 Optional: Select Delete Entity to enable users to delete entities.

6 Optional: Select Allow Entity Change Management to enable Entity Change Management.

7 Optional: Select Allow Assumptions Change Management to enable Assumptions Change Management.

8 Optional: Select Allow Batch Export to another Hyperion Application to enable batch exporting.

9 Optional: Select Allow Batch Import from another Hyperion Application to enable batch importing.

10 Optional:Select Change HSF Data Link to enable HSF links.

11 Optional: Select Change Input Status to enable users to change input status.

12 Optional: Select Change Account Groups to enable users to change account group membership.

13 Optional: Select Change Permission Groups to enable users to change account permission groups.

14 Optional: Select Change Funding Options to enable users to modify funding options.

15 Optional: Select Change Required Elements to enable users to assign subaccounts as required elements.

16 Optional: Select Change Template Name to enable users to rename templates.

17 Return to “About Assigning Default Access” on page 75.

Configuring Accounts Access OptionsUse the Edit Default Access—Accounts tab to configure access to accounts.

➤ To configure account access:




3 Select the Permission Groups.

Permission Groups displays account groups classified as Permission Groups in the source entity.

Default contains accounts not belonging to account groups.

● Click Add to add new groups. See “Adding Permissions Groups” on page 78.

● Select a group and click Delete to delete.


Note:

You can add or delete account groups, but you cannot delete the universal Default group.

4 Select Accounts options:

● Add/Delete Subaccounts

Enables modifying subaccount structures.

● Renumber Subaccounts

Enables renumbering subaccounts.

● Edit User-defined Accounts

Enables modifying user-defined accounts: memo, ratio, and covenant.

● Change HSF Data Link

Enables data sharing between entities.

● Allow Input in Actuals

Enables modifying data and time periods in the Actual scenario.

● Allow Input in History

Enables modifying data and historical/forecast boundaries in historical periods.

● Allow Input in Forecast

Enables modifying data and historical/forecast boundaries in forecast periods.

● Change Forecast Method

Enables modifying forecast methods.

● Modify Notes

Enables changing, adding, and deleting notes.

● Rename Accounts

Enables renaming accounts.

Adding Permissions Groups

➤ To add permissions groups:

1 Select a permissions group.

2 Click OK.

Configuring Time Access OptionsYou use the Edit Default Access—Time tab to configure time period access.


➤ To configure time period access:




3 Select time access options:

● Change Time Period Information

Enables general time period modifications not configured in “Configuring Accounts AccessOptions” on page 77.

Configuring Reports Access OptionsYou use the Edit Default Access—Reports tab to define the reporting options. Before you canedit report access, you must access the References tab and select an Entity.

➤ To configure reports access:



2 Select the Reports tab.

3 Select Global Permissions options:

● Default Number Format

Changes the format of numbers on reports.

● Load Default Reports

Restores a standard report to its original layout.

● Add Reports

Enables a user to add freestyle reports to the model.

● Move Reports

Enabled modifying the list order of reports.

4 Under Reports , select reports and permissions:

● Can Edit

Enables editing reports.

● Can Hide/Unhide

Enables hiding and unhiding sections of reports.

● Can Rename

Enables renaming reports.

● Can Lock/Unlock


Enables locking cells in reports.

Configuring Scenario Access OptionsYou use the Edit Default Access—Scenarios tab to configure scenario access.

➤ To configure scenario access:




3 Select Global Permissions applying to all scenarios:

● Add Scenarios

Enables creating scenarios.

● Change output storage rules

Enables modifying output values.

● Allow input in scenario-specific accounts only

Restricts modification to only scenario-specific accounts.

4 Under Access Control Items, select a Data and forecast methods option to determine the primary accesssettings changing data and forecast methods in scenarios:

● Cannot change data or forecast methods

No changes can be made.

● Change data only

Enables change only to financial data.

● Change data and forecast methods

Enables changes to financial data and forecast methods.

5 Optional: Select Add/Delete accounts to enable a user to add or delete accounts within scenario.

Does not apply to the Base and Actual scenarios.

6 Optional: Select Select Delete to enable deleting scenarios.

Does not apply to the Base and Actual Scenarios.

7 Optional: Select Rename to enable renaming scenarios.

8 Optional: SelectChange Scenario Type to enables modifying scenario types of scenarios.

9 Optional: Select Change Actuals Use to enables changing the rules regarding the use of actuals in scenarios.

Configuring Dimension Access OptionsYou use the Edit Default Access—Dimensions tab to configure access to dimensions.


➤ To configure dimension access:



2 Select the Dimensions tab.

3 Select dimensions access options:

● Can Maintain Dimensions

Enables creating and deleting user-defined dimensions.

● Can Assign Dimensions

Enables assigning and removing the user-defined dimensions.

Configuring Consolidation Access OptionsYou use the Edit Default Access—Consolidation tab to configure Consolidator access.

➤ To configure Consolidator access:



2 Select the Consolidation tab.

3 Select Consolidation Structure access options:

● Add to Entity <database name>

Enables adding entities to consolidation structures.

● Remove from Entity <database name>

Enables deleting entities from consolidation structures.

4 Select consolidation access options:

● Change Entity Characteristics

Enables changing entity characteristics in consolidation structures.

Configuring Reference Access OptionsYou use the Edit Default Access—References tab to select the source entity for accounts andreports. This entity applies to the Reports and Entities tabs.

➤ To configure reference access:



2 Select the Reference tab.


3 Select a Get List of Accounts/Reports option to determine the source entity for reports:

● Current Entity

The current entity.

● First Entity in Group

The first entity in an entity group.

● Selected Entity

Click ... to browse and select a database and entity.

Configuring Default Access for New EntitiesYou use the Edit Default Access—New Entities tab to define the default access permissions fornew entities.

➤ To configure default access for new entities:



2 Select the New Entities tab.

3 Select a Newly-created child Entities get an access record by option to define the access permissionssource:

● Making a copy of the access record for this Entity

Uses default access.

● Copying a pre-defined access record

Click Edit Access to open the Edit Default Access dialog box, where you can create accesspermissions.

❍ Optional: Configure entity access.

See “Configuring Entities Access Options” on page 76.

❍ Optional: Configure account access.

See “Configuring Accounts Access Options” on page 77.

❍ Optional: Configure time access.

See “Configuring Time Access Options” on page 78.

❍ Optional: Configure scenario access.

See “Configuring Scenario Access Options” on page 80.

❍ Optional: Configure dimension access.

See “Configuring Dimension Access Options” on page 80.

❍ Optional: Configure Consolidation access.

See “Configuring Consolidation Access Options” on page 81.


❍ Optional: Configure reference access.

See “Configuring Reference Access Options” on page 81.

❍ Optional: Configure reports access.

See “Configuring Reports Access Options” on page 79.

● Assigning the Entity to a Group

Click Select Group to open the Select Group dialog box and select an entity group.

● Letting the creator assign it to a Group

The creator of the entity has access permission to assign the entity to a group.

Adding Users and User Groups to Databases, Entities, or EntityGroups

After creating databases, you must add users. Users are authenticated internally with user IDsfrom external service providers.

● “Adding Users” on page 83

● “Selecting Users from the User Database” on page 84

● “Adding User Groups to Databases, Entities, or Entity Groups” on page 84

Adding UsersYou can add users to databases, entities, or entity groups.

Note:

You can add Users and Groups from the Edit Default Access box. Users or Groups added fromthe Database Options box display in the Edit Default Access box.

➤ To add users or user groups to databases, entities, or entity groups:



3 Optional: To add users or user groups, perform an action:

● To add users to the database, skip this step.

● To add users entities, select the Entities tab and select an entity.

● To add users to entity groups, select the Entity Group tab select an entity group.


● For databases, select Access > Database Options .

● For databases, select Access > Edit Default .

Adding Users and User Groups to Databases, Entities, or Entity Groups 83

● For entities, select Edit > Access .

● For entity groups, select Group > Access .

5 In Edit Database Options or Edit Default Access, click Add User.

6 Click Browse and select a user.

See “Selecting Users from the User Database” on page 84.

7 View information:

● Domain Name/ User ID

Read only

❍ With Standard NTLM Security, the NTLM Directory Server domain is displayed.

❍ With single sign-on, user ID is displayed.

● User Name/User Identity

Read only

❍ With Standard NTLM Security, the name of the user within the domain is displayed..

❍ With single sign-on, the Security Identifier (SID) of the user within the Directory Serveris displayed.

8 In Copy Accesst, select source user for copying access privileges.

9 Click OK.

Selecting Users from the User Database

➤ To select users, in User, select a name and click OK.

Adding User Groups to Databases, Entities, or Entity GroupsYou can add user groups to databases, entities, or entity groups.

Note:

You can add users and groups from the Edit Default Access box. Any Users or Groups added inthe Database Options box appear in the Edit Default Access box.

➤ To add user groups to a databases, entities, or entity groups:

1 Select Databases.


3 Optional: To add a user or user group to an entity or entity group, perform a task:

● For databases, skip this step.

● For an entity, select Entities and select an entity.


● For an entity group, select Entity Group and then an entity group.


● For databases, select Access > Database Options .

● For databases, select Access > Edit Default .

● For entities, select Edit > Access .

● For entity groups, select Group > Access .

5 In Edit Database Options or Edit Default Access, click Add Group.

6 By Name, click Browse to search available groups.

7 In User Groups, select a user group and click OK.

8 On Add Group, select a source user group for copying access and click Copy Access.

9 Click OK.

Adding Users and User Groups to Databases, Entities, or Entity Groups 85

7Activating and Managing Client-

Side Functionality

In This Chapter

Activating and Managing Entity Change Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Activating and Managing Assumptions Change Manager .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Managing Batches, Maps, and Servers for Import and Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

You use Administrator to manage these Strategic Finance client functions:

● Entity Change Management

● Assumptions Change Management

● Importing and exporting maps and batches

Activating and Managing Entity Change ManagementThe ECM (Entity Change Management) tab lists all ECM documents and their owners. ECMdocuments enable bulk-management of multiple target entities through a base entity. ThoughECM documents are create using the client, they are run on the server. See the Hyperion StrategicFinance User Guide.

● “Activating Entity Change Management” on page 87

● “Managing Access to ECM Documents” on page 88

● “Adding Users for ECM Documents” on page 89

● “Adding User Groups for ECM Documents” on page 89

● “Editing Access to ECM Documents” on page 89

● “Changing the Owner of ECM Documents” on page 90

● “Breaking Locks on ECM Documents” on page 90

Activating Entity Change ManagementYou must select three options in the server to activate Entity Change Management:

● General Database Access

● Default Owner Database Access

● Default User Database Access

Activating and Managing Entity Change Management 87

➤ To activate Entity Change Management:

1 On the Databases tab, double-click a database.

2 Select Database > Database Options.

3 In Edit Database Options, select <Default> and click Edit.

4 On Database General, select Allow Entity Change Management and click OK.

5 Click OK.

6 Select Database > Edit Default.

7 From Edit Default Access, select <Owner> and click Edit.

8 Click Entities , select Allow Entity Change Management and click OK.

9 From Edit Default Access, select <Default> and click Edit.

10 Click Entities, select Allow Entity Change Management and click OK.

11 Click OK.

12 You must restart the server for the changes to take effect.

Managing Access to ECM DocumentsYou can define access options for individual ECM documents.

➤ To manage access to ECM documents:

1 In Administrator, select ECM.

2 FromECM Doc, select a name.

3 Select Edit > Access.

4 From Edit Access, perform an action:

● To add usesr, click Add User.

See “Adding Users for ECM Documents” on page 89.

● To add user groups, click Add Group.

See “Adding User Groups for ECM Documents” on page 89.

● To edit access for owners, default users, specific users, or user groups, in Edit Access to<ECM Doc name>, select a name and click Edit.

See “Editing Access to ECM Documents” on page 89.

● To delete user or user groups, in Edit Access to <ECM Doc name>, select a name and clickDelete.

5 Click OK.

88 Activating and Managing Client-Side Functionality

Adding Users for ECM DocumentsAfter selecting an ECM document from the ECM tab of the Administrator utility, you can addusers.

➤ To add users:

1 Access Edit Access.

See “Managing Access to ECM Documents” on page 88.

2 Click Add User.

3 Click Browse.

See “Adding Users” on page 83.

4 In Copy Access, select a source user to copy access settings.

5 Click OK.

Adding User Groups for ECM Documents

➤ To add user groups:



2 Click Add Group.

3 Click Browse.

4 In User Groups, select a user group, and click OK.

5 On Add Group, in Copy Access , select a source group to copy access settings.

6 Click OK.

Editing Access to ECM Documents

➤ To edit ECM document access:



2 Select an Access option:

● None

No access.

● Open As Copy

Enables opening ECM documents as read-only copies.

Activating and Managing Entity Change Management 89

● Check Out

Enables opening entities within ECM documents.

3 Optional: Select Run ECM to enable running Entity Change Management.

4 Optional: Select Delete ECM Doc to enable deleting ECM documents.

5 Click OK.

Changing the Owner of ECM Documents

➤ To change ECM document owners:

1 Click ECM.

2 FromECM Doc, select a name.


4 In Domain Name for New Owner, click Browse to select a user.

See “Selecting Users from the User Database” on page 84.

5 Click OK.

Breaking Locks on ECM Documents

➤ To break locks on ECM documents:

1 Click ECM.

2 On ECM Doc, select an ECM document.


Activating and Managing Assumptions Change ManagerThe ACM (Assumptions Change Manager) tab lists all ACM documents and their owners. ACMdocuments enable bulk-management of multiple target entities through a base entity. ThoughACM documents are create using the client, they are run on the server. See the Hyperion StrategicFinance User Guide.

● “Activating Assumptions Change Manager” on page 91

● “Managing ACM Document Access” on page 91

● “Changing ACM Document Owners” on page 91

● “Breaking ACM Document Locks” on page 91


Activating Assumptions Change ManagerYou activate Assumptions Change Manager through these tasks

● “Configuring General Database SettingsAccess” on page 73.

● “Configuring Default Access to Databases, Entities, and Entity Groups” on page 74.

Managing ACM Document Access

➤ To manage ACM document access:

1 Select ACM.

2 Under ACM Doc, select a name.


4 On Edit Access, perform a task:

● To add users, click Add User.

● To add user groups, click Add Group.

● To edit access for owners, default users, specific users, or user groups, in Edit Access to<ACM Doc name>, select one and click Edit.

● To delete user or user groups, in Edit Access to <ACM Doc name>, select one and clickDelete.

5 Click OK.

Changing ACM Document Owners

➤ To change ACM document owners:

1 Select ACM.



4 In Domain Name for New Owner, select a user.

Click Browse to search. See “Selecting Users from the User Database” on page 84.

5 Click OK.

Breaking ACM Document Locks

➤ To break ACM document locks:

1 Select ACM.


Activating and Managing Assumptions Change Manager 91


Managing Batches, Maps, and Servers for Import and ExportTo import or export data between Strategic Finance and other Hyperion applications, you grantend users access permission to maps and batch imports and exports. You use the Map andBatch tabs to manage maps and batches.

● “Managing Connections to Other Hyperion Product Servers” on page 92

● “Managing Batches” on page 93

● “Managing Maps” on page 94

Managing Connections to Other Hyperion Product ServersBefore users can import or export between a Strategic Finance Server and another Hyperionserver, you create a connection.

● “Managing Connections to Other Hyperion Product Servers” on page 92

● “Creating Connections to Other Hyperion Product Servers” on page 92

Managing Connections to Other Hyperion Product Servers

➤ To manage Hyperion servers:

1 In Administrator, perform a task:

● For Oracle's Hyperion® Planning – System 9 Servers, select Server > Planning Servers.

● For Oracle's Hyperion® Financial Management – System 9 Servers, select Server > FinancialManagement Servers.

2 To create a server, click Add. See “Creating Connections to Other Hyperion Product Servers” on page92.

3 To delete a server, select one and click Delete.

4 Click OK.

Creating Connections to Other Hyperion Product Servers

➤ To create connections to other Hyperion product server:

1 Access Hyperion Servers and click Add. See “Managing Connections to Other Hyperion Product Servers”on page 92.

2 In New Server, enter the server network name and click OK.


Managing BatchesYou use the Batches tab to manage batches.

● “Setting Access to Batches” on page 93

● “Overriding Default Access to Batches” on page 93

● “Changing Owners of Batches” on page 94

Setting Access to BatchesThe default setting determines access to batches that is initially assigned to users or groups.

➤ To create default access control for batches:

1 In Administrator, select the Batches tab.

2 Select a batch .



● Click Add User to add users.


● ClickAdd Group to add groups.


● To edit access for owners, default users, specific users, or user groups, in Edit Access to<batchName>, select one and click Edit.

See “Overriding Default Access to Batches” on page 93.

● To delete users or user groups, in Edit Access to <batchName>, select one andclickDelete.

5 Click OK.

Overriding Default Access to Batches

➤ To override default batch access:

1 In Edit Access, select a user or group and click Edit.

2 In Edit Access for <userName/groupName>, select Access:

● None

No access.

● Check Out/Run Batch

Enables users or user groups to check out and run batches.

3 Optional: Click Delete Batch to enable the user or group to delete the batch.

Managing Batches, Maps, and Servers for Import and Export 93

4 Click OK.

Changing Owners of Batches

➤ To change batch owners:

1 Select Batches.

2 From Batch, select a batch.


4 InChange Owner, enter a user.

See “Changing Entity Owners” on page 67.

5 Click OK.

Managing MapsYou use the Maps tab to manage maps.

● “Managing Access to Maps” on page 94

● “Overriding Default Access to Maps” on page 95

● “Changing Owners of Maps” on page 95

Managing Access to Maps

➤ To manage map access:

1 Select Maps.

2 Select a map.



● To add users, click Add User.


● To add user groups, clickAdd Group.


● To edit access for owners, default users, another user or a user groups, in Edit Access for<mapName>, select one and clickEdit.

See “Overriding Default Access to Maps” on page 95.

● To delete users or user groups, in Edit Access to <mapName>, select one and click Delete.

5 Click OK.


Overriding Default Access to Maps

➤ To override default map access:

1 On Edit Access , select a user or user group and click Edit.

See“Managing Access to Maps” on page 94.

2 On the Edit Access for <userName /groupName>, select access options:

● None

No access.

● Check Out/Run Map

Enables a user or user group to check out and use maps.

3 Optional: Click Delete Map to enable the user or group to be able to delete the map.

4 Click OK.

Changing Owners of Maps

➤ To change map owners:

1 Select Map.

2 From Maps, select the map.


4 On Change Owner , select a user.

See “Changing Entity Owners” on page 67.

5 Click OK.

Managing Batches, Maps, and Servers for Import and Export 95

8Managing Locks, Logs,

Transactions, and Sessions

In This Chapter

Managing Entity Locks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Managing Transactions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Managing Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Managing User Sessions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Managing Event Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

You use Administrator for daily maintenance and troubleshooting such as managing locks, logs,transactions, and user sessions.

Managing Entity LocksWhen users check out entities, Strategic Finance locks the entity to protect the data. You use theLocks tab to view entity locks.

➤ To manage entity locks:

1 From Administrator, select the Locks tab.

2 View locks:

● User ID

The domain and user ID of the user with the lock.

● Entity ID

The name of the locked entity.

● Version Number

The version number of the entity.

● Check Out Date

The date when the entity was checked out.

3 Optional: Break a lock.

See “Breaking Locks on Entities” on page 98.

Managing Entity Locks 97

Breaking Locks on EntitiesWhen you break a lock, the owner of the lock can no longer check the entity into the server andtheir changes are lost.

➤ To break locks:

1 From Administrator, select Locks.

2 Select a lock.

3 Select Lock > Break.

Managing TransactionsYou use the Transactions tab to identify successful transactions and rerun failed transactions.

➤ To manage transactions:

1 From Administrator, select the Transactions tab.

2 View transactions.

The following is displayed for each transaction:

● Transaction Type

Transaction types describe actions:

❍ Convert Entities

Entity conversions during upgrades.

❍ Run Consolidation

Consolidation processes.

❍ Run ECM Changes

Entity Change Management processes.

❍ Database Export

External database exports.

● Transaction State

The current state of the process:

❍ Pending

In the queue

❍ Processing

Being processed

❍ Failure

Terminated by the system

98 Managing Locks, Logs, Transactions, and Sessions

❍ Cancelled

Terminated by a user

❍ Complete

Successful process

● Transaction ID

A unique number assigned to the transaction.

● User ID

The user who requested the transaction.

● Run time

The time when the transaction was requested.

● Duration

The length of time spent processing the transaction.


● To sort by type, in Transaction Type, select a type.

● To sort by state, in Transaction State, select a state.

● To view logs, select a transaction and:

❍ Click Show Log.

❍ Select Transaction > Show.

Logs are available on the Log tab—see “Managing Logs” on page 99.

● To delete a log, select one and click Delete.

● To rerun failed transactions, select one and:

❍ Click Rerun.

❍ Select Transaction > Rerun.

Managing LogsThe Logs tab contains logs, which contain details about transactions and are useful introubleshooting. Strategic Finance logs information about:

● Entity conversions

● Entity change management actions

● Database exports

● Batch import and exports

● Archive repairs and purges

Managing Logs 99

➤ To manage logs:

1 From Administrator, select the Logs tab.

2 View log information:

● User ID

The user who requested the action.

● Entity ID

The target entity of the action.

● Log File Name

The name of the log file.

● Serial String

The time the action was started.

● Time Completed

The time the action completed.

● Transaction Key

A unique number assigned for this action, used for system purposes.

3 Select a log and perform an action:

● To retrieve a log, select Log > Retrieve.

● To retrieve and delete logs, select Log > Retrieve and Delete:

Perform an action:

❍ To delete the log, click Close.

❍ To save the log as a .txt file, click Save As.

Managing User SessionsYou use the Sessions tab to manage user sessions. A session is the time between a user's initialaction until the last action. When users close the client, the session ends and the recorddisappears.

➤ To manage user sessions:

1 From Administrator, select the Sessions tab.

2 View user session information:

● User ID

The user initiating the session.

● Session Key

A unique number identifying the session.


● Creation Time

The time of the initial action.

● Last Accessed Time

The time of the last action.

● Compression Level

The compression level of the session.

3 Optional: To destroy a session, select one and select Session > Destroy:

If a client has ended a session without informing the server, destroying the session removes itfrom the list and frees resources.

Managing Event LogsYou use the Event Logs tab to track daily use of Strategic Finance, and analyze patterns. Eventlogs can be useful in troubleshooting.

➤ To manage event logs:

1 From Administrator, select the Event Logs tab.

2 View event log information:

● Session Date/Time

The time and date that the session was initiated.

● User ID

The domain and name of the user who initiated the session.

● Event Type

The type of event.

● Transaction ID

A unique number identifying the transaction.

● Entity Name

The name of the target entity.

● Entity ID

A number identifying the entity.

● Database

The name of the database containing the entity.

● Success

❍ Y—success

❍ N—failure

Managing Event Logs 101

● Duration

The length of time spent processing the event.

● Parent Transaction ID

For Entity Change Manager and Consolidator events, this number indicates the parent entitydocument or structure.

3 Optional: To retrieve logs, select one and select Event Log > Retrieve.


AServer Registry and Database

Directory Structure

In This Appendix

Server Registry .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Database Directories and Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Server Registry

Caution!

Do not edit registers, unless specified in “Configuring Advanced Server Settings” on page 32.

Hyperion Strategic Finance Service Registry ParametersStrategic Finance service registers are located in:

HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\HSFService

Table 15 Strategic Finance Service Registers

Parameter Type Data

(Default) REG_SZ (value not set)

AdminDirectory REG_SZ C:\HSFData\Admin (default)

ArchiveDirectory REG_SZ Archive

ArchiveWarningLevel REG_SZ Block

CSSConfigFile REG_SZ Absolute filepath to the External Authentication configuration file

DatabaseConnectionString REG_SZ Use to connect to the database

DatabaseConnectivityType REG_SZ ODBC or OLE DB DB Name

DataSourceConnectionString REG_SZ SQLOLEDB

DefaultLogFile REG_SZ C:\HSFData\Admin\Default.log

EntityDirectory REG_SZ ADB

Server Registry 103

Parameter Type Data

EntityFileExtension REG_SZ ALS

HSFDataDir REG_SZ C:\HSFData

LockFileExtension REG_SZ LCK

LogDirectory REG_SZ C:\HSFData

MaxBackgroundWorkers REG_SZ 3

MaximumIntensiveRequests REG_SZ 10

MaximumProcessSize REG_SZ 2048000

MaximumFreeMemory REG_SZ 51200

MinimumFreeDisk REG_SIZ 100

MinumumFreeMemory REG_SIZ 51200

MRUListSize REG_SZ 5

RootDirectory REG_SZ C:\HSFData

RPCPort REG_SZ The port where the Strategic Finance server connects:

7750

SecurityRegime REG_SZ If disabled or showing no value, NTLM is the default.

For External Authentication, set to:

CSS

SocketBufferSize REG_SZ 1024000

SocketPort REG_SZ 7751

StructLockFileExtension REG_SZ LKS

StructureFileExtension REG_SZ CNS

TemplateExtension REG_SZ ALT

TraceLevel REG_SZ Standard

UserFile REG_SZ Users.adm

UserLogDirectory REG_SZ Absolute filepath to the directory containing user logs.

Default:

C:\HSFData\UserLogs

HSF Service Shared Services Registry ParametersStrategic Finance registers for Shared Services are located in:

104 Server Registry and Database Directory Structure

HKEY_LOCAL_MACHINE\Software\Hyperion Solutions\HSFService\Authentication

Table 16 Strategic Finance Registers for Shared Services

Name Type Data


ClassPath REG_EXPAND_SZ The classpath

ConnectionInfo REG_SZ String used to connect to Shared Services

HubInstanceID REG_SZ String storing the name of a Shared Services server

HubURL REG_SZ URL connecting to Oracle's Hyperion® Shared Services

JamPath REG_EXPAND_SZ Locates the Java Virtual Machine

LibPath REG_EXPAND_SZ Locates required libraries

HSF Service License Manager Registry ParametersStrategic Finance registers for License Manager are located in:

HKEY_LOCAL_MACHINE\Software\Hyperion Solutions\HSFService\Licensing

Table 17 Strategic Finance Registers for License Manager

Name Type Data


DeploymentID REG_SZ The deployment for Strategic Finance

LicenseServerPath REG_SZ String connecting to License Manager

HSF Server Registry ParametersStrategic Finance server registers are located in:

HKEY_CURRENT_USER\Software\Hyperion Solutions\Strategic Finance\HSFServer

Table 18 Strategic Finance Server Registers

Name Type Data


network address REG_SZ HSFserver

protocol REG_SZ ncacn_ip_tcp

Server Registry 105

Database Directories and Files

..\HSFDataThe root directory containing Strategic Finance data is ..\HSFData. Subdirectories containStrategic Finance databases, the AdminDoc file, and log files.

Table 19 ..\HSFData

Directory or Subdirectory Description

..\HSFData\ Root directory for all databases.

..\HSFData\ADB Contains databases.

..\HSFData\Admin Contains the AdminDoc file.

..\HSFData\Logs Contains transaction log information.

..\ADBAll native Strategic Finance databases are stored under the ..\HSFData\ADB subdirectory.

Table 20 ..\ADB

Subdirectory Description

..\_delete This subdirectory contains deleted databases.

..\<Database Name> This subdirectory contains an individual, active database

..\ADB\_deleteDeleted databases and their contents are in .\HSFData\ADB\_delete. The date on which thedatabase was deleted is part of the directory name.

..\ADB\<Database Name>Each database is in ..\HSFData\ADB\<Database Name>.

Table 21 ..\HSFData\ABD\<Database Name>

Subdirectory Description

..\delete Contains deleted entities.

..\_ecm Contains Entity Change Management files.

..\<Entity Name> Contains the entity of same name as the folder.


..\ADB\<Database Name>\<Entity Name>Each entity is in ..\HSFData\ADB\<Database Name>.

Table 22 ..\HSFData\ABD\<Database Name>\<Entity Name>

Subdirectory or File Description

..\Archive Contains archived versions of the entity.

..\Drafts Contains working drafts of the entity.

..\<Entity Name>.ALS File named after an entity that contains that entity.

..\<Entity Name>.bld Contains consolidation data for the entity after a consolidation structure was created.

..\<Entity Name>.STR Contains information about structural relationships between entities.

..\<Entity Name>.LCK Indicates if an entity is locked.

..\AdminThe AdminDoc file that contains this information:

● user authorization

● databases and database configurations

● export rule sets

● archive retention rules

● access records

● entity and user groups

● consolidation structure names and configurations

● server logging settings

● server E-mail controls

● backup and restore configuration

in this location:

..\HSFData\ADB\<Database Name>

Table 23 ..\HSFData\Admin

Files Description

..\Default.log Contains logged errors on general server use.

..\ImportExportRestrictions.xml Contains parameter settings that define export rules for RDBMSstaging databases.

..\License.ini Contains license information.

Database Directories and Files 107

Files Description

..\User.adm AdminDoc file.

..\User.tbk AdminDoc file backup

..\LogsTransactions and log files are in:

..\HSFData\Logs

Table 24 ..\HSFData\Logs

Subdirectory or File Description

..\_finished Contains completed transactions.

..\_processing Contains transactions being processed.

..\Event<date>.log Text file that logs transaction activity.

..\TRANS.TRN Transaction file

..\TRANSBAK.TRN Transaction file backup

..\UserLogsEnd user actions are logged in:

..\HSFData\UserLogs

..\Hyperion\StrategicFinance\<release>\Server\DBDatabase scripts are in:

.\Hyperion\StrategicFinance\<release number>\Server\DB

Table 25 ..\Hyperion\StrategicFinance\<release>\Server\DB

Subdirectories and Files Description

..\DB\Oracle\New Scripts for creating export databases in Oracle.

..\DB\Oracle\Upgrade Scripts for upgrading Alcar 6.x export databases in Oracle to Strategic Finance3.x.

..\DB\SQL Server\New Scripts for creating export databases in SQL Server.

..\DB\SQL Server\Upgrade Scripts for upgrading existing Alcar 6.x export databases in SQL Server toStrategic Finance 3.x.


..\DB\Oracle\New

Table 26 ..\DB\Oracle\New Scripts

File Name Description

step1_tables_viewsql Creates the base and ancillary Strategic Finance database schema,including: tables, sequences, indexes, and keys.

step2_defaultspcreate.sql Creates defaults and substitution procedures.

step3_pkgcreate.sql Contains package definitions and bodies for the base StrategicFinance database export and the customer interface table.

step4a_optionalauditcreate.sql Creates an optional audit table for defaults and substitutions.

step4b_optionalaudittrigger.sql Creates an optional trigger for defaults and substitutions.

..\DB\Oracle\Upgrade

..\DB\Oracle\Newcontains the upgrade30.sql script for upgrading an existing Oraclestaging database from 6.x to Strategic Finance 3.x.

..\DB\SQL Server\New

..\DB\SQL Server\New contains these scripts:

Table 27 ..\DB\SQL Server\New Scripts

File Name Description

step1alt_remove_objects.sql Alternative to step 1. Removes objects for reinstallation.

step1_create_alcar_database.sql Creates the Strategic Finance SQL Server database as hsfsvr.

step2_security.sql Sets up logins and permissions. The default are hsfsvr_user,password = null.

step3_tables_grants.sql Contains the base Strategic Finance database schema, including:tables, indexes, and keys with default grants.

step4_procs_funcs.sql Contains stored procedures and functions.

..\DB\SQL Server\Upgrade

..\DB\SQL Server\New contains the upgrade30.sql script to upgrade Oracle stagingdatabases from 6.x to Strategic Finance 3.x.

Database Directories and Files 109

BRDBMS Export Installation and

Setup

In This Appendix

RDBMS Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Setting Up the Export Database for SQL Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Setting Up the Export Database for Oracle .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Configuring the Strategic Finance Server for Database Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

RDBMS ExportExport integrates Strategic Finance data with Relational Database Management (RDBMS)systems, creating transactions in a staging database tables whenever Strategic Finance entitiesare created, updated, or deleted on the Strategic Finance server. Tables link by unique, sequentialtransaction_id. Some additional links are by variable_id or period ID. You create rulesets defining the accounts, time periods, and scenarios exported.

For compatibility, refer to the Hyperion Installation Start Here.

Setting Up the Export Database for SQL ServerTo set up the export database:

● You must be a SQL database administrator with privileges to create:

❍ schema

❍ tables

❍ packages

● You must have access to the Strategic Finance server.

Creating an Instance of SQL ServerIn SQL Server, create an instance of the server in which to create the target database. You needthis information:

Table 28 SQL Server Instance Information

SQL Server Name

RDBMS Export 111

Database User Name

Database Password

Creating the Export DatabaseUsing the user name and password for the SQL server database in Table 28 on page 111, accessthe SQL Server instance and run the Strategic Finance export database scripts to set up thedatabase. The scripts create a database and users with default names. Edit the scripts to configureother names, logins, security, roles, and procedures.

The scripts are in:

[InstallDrive]:\Hyperion\Strategic Finance\Server\DB\SQL Server\New

Run the scripts using Query Analyzer, and install to the SQL Server database. You install thescripts in this order:

Table 29 SQL Server Install Scripts

Script Description

Step1_create_HSF_database Creates the Strategic Finance SQL Server database, with the default name hsfsvr.

Step1alt_remove_objects Alternative step 1 removes objects for reinstall.

Step2_security Sets up logins and permissions.

The default:

● login = hsfdbuser

● password = password

Step3_tables_grants Contains the base Strategic Finance database schema including tables, indexes, andkeys with default grants.

Step4_procs_funcs Contains stored procedures and functions.

Review steps 1 and 2 for conformance to your environment. Step 1 script is used for initialinstallations. To reinstall, use Step1alt.

UpgradingTo upgrade the export database from a previous version, run these scripts in

<InstallDrive>:\Hyperion\StrategicFinance\Server\DB\SQL Server\Upgrade

Table 30 SQL Server Upgrade Scripts

Script Description

upgrade_30 Adds a new column to the Transaction table.

Use to upgrade from 2.9 or prior up to 3.x or 4.0.x.

112 RDBMS Export Installation and Setup

Script Description

upgrade_41 Updates database for unicode.

Use to upgrade from 3.x or 4.0.1 to 4.1, 9.2, or 9.3.

Note: If you are upgrading from 2.9 or earlier, run upgrade_30 before upgrade_41.

Setting Up the Export Database for OracleTo set up the export database:

● You must be an Oracle database administrator with privileges to create:

❍ schema

❍ tables

❍ packages

● You must have access to the Strategic Finance server.

Setting Up Oracle ConnectivityPerform these tasks before setting up Oracle database export:

● Install the Oracle client on the Strategic Finance server.

● In the Oracle server, create the following:

Table 31 Oracle Server Instance Information

Oracle Server Name

Database User Name

Database Password

Note:

See your Oracle documentation for information about installing and configuring serversand creating service names.

Creating the Export DatabaseUsing the user name and password from Table 31 on page 113, access the Oracle Service Nameand create the Oracle schema, or database, used by Strategic Finance to contain the tables andpackages.

The schema name can be any name that best suits your company standards. If there is nostandard, use HSFSvr. Strategic Finance provides SQL scripts in

[InstallDrive]:\Hyperion\StrategicFinance\Server\DB\Oracle\New

Setting Up the Export Database for Oracle 113

To build the database from the scripts, use an appropriate SQL tool (e.g. SQL Plus), and installto the designated schema. Install the scripts in order in Table 32 on page 114.

Note:

Ensure that there are no errors when loading scripts to Oracle. Contact technical support ifrequired.

Note:

There are no “drop object” definitions in the SQL scripts. The first two scripts assume a cleandatabase schema. You cannot load the first two scripts more than once in a schema.

Table 32 Database Scripts for Oracle

Script Description

Pre_installation

Note: With Oracle RAC, do not use this script. See “For OracleReal Application Clusters (RAC)” on page 114.

Creates a new user and the physical tablespaces. Run this, then log in under the username'HSFDBUser' with the password 'password' torun steps 2 though 5.

Note: For security, change the password for'HSFDBUser'.

Step1_tables_views.sql Contains the base and ancillary StrategicFinance database schema including tables,sequences, indexes, and keys.

Step2_defaultspcreate.sql Contains defaults and substitution procedures.

Step3_pkgcreate.sql Contains package definitions and bodies for thebase Strategic Finance database export and thecustomer interface table.

Step4a_optionalauditcreate.sql Optional audit table for defaults andsubstitutions.

Step4a_optionalaudittrigger Optional trigger for defaults and substitutions.

Step5_upgrade Same as update_30.

This sample procedure loads the Strategic Finance SQL scripts using SQLPlus:

1. Type: C:\>sqlplus HSF/password@HSFOraDBSrvName.

2. Replacing scriptname with the real name of the script, type: SQL>scriptname.sql.

3. Load the scripts using the order in the preceding Database Scripts table.

For Oracle Real Application Clusters (RAC)For installing with Oracle Real Application Clusters (RAC), the tasks in thepre_installation.sql file must be performed manually.


➤ To set up export to Oracle using Real Application Clusters:

1 Log into Oracle as the system DBA.

2 Create a tablespace with these attributes:

● size 1024m

● autoextend on

● next 256m

● maxsize 5128m

● extent management local

3 Create a user schema:

● Generate the user schema using the default tablespace you created.

● The schema includes the username and password required by Strategic Finance to accessthe export database.

4 Grant these access privileges to the user schema:

● CREATE PROCEDURE

● CREATE SESSION

● CREATE TABLE

● UNLIMITED TABLESPACE

● CONNECT

● RESOURCE

5 Log in to the user schema and run the scripts in Table 32 on page 114 .

Run Step1_tables_views.sqlfirst.

UpgradingIf you have an existing implementation with export to Oracle, upgrade using the scripts in:

[InstallDrive]:\Hyperion\Strategic Finance\Server\DB\Oracle\Upgrade

Table 33 Oracle Server Upgrade Scripts

Script Description

upgrade_30 Adds a new column to the Transaction table.

Use this script if you are upgrading from releases prior to 2.9 to 4.0.x.

upgrade_41 Updates database for unicode.

Use this script if you are upgrading from 3.x or 4.0.1 to 4.1, 9.2, or 9.3.

Note: If you are upgrading from 2.9 or earlier, run upgrade_30 before running upgrade_41.

Setting Up the Export Database for Oracle 115

Configuring the Strategic Finance Server for Database ExportYou use the Administrator utility to set up the connection between the Strategic Finance serverand the relational database server.

Selecting Database Connectivity

➤ To set up the external connection:

1 Access Administrator.

2 Select Server > Open, select a server, and click OK.

3 Select the Server tab.

4 Select Server > External Connection Settings.

5 In Choose Database Connectivity, select a method:

● SQL Server

● Oracle

Note:

If you change the current setting, restart the Strategic Finance Service. If you are upgradingfrom an existing connection using ODBC, change this parameter to reflect the new databaseconnection.

6 Verify prerequisite software.

See The Hyperion Installation Start Here.

7 Close the Administrator utility.

8 From the desktop, select Start > Settings > Control Panel > Administrative Tools > Services.

9 On the Services box, select Hyperion Strategic Finance Service, right-click, and select Restart.

Creating Rule SetsBefore you can complete “Setting up the External Database Connection in Strategic FinanceServer” on page 116, create a Rule Set.

See the Hyperion Strategic Finance Administrator’s Guide or the online help.

Setting up the External Database Connection in StrategicFinance ServerAfter you install Oracle's Hyperion® Strategic Finance and the HSF Administrator, and set upyour database, configure database connectivity.


➤ To set up the Strategic Finance Server connection to the export database:

1 Access Administrator.

2 Select Server > Open, select a server, then click OK.

3 Select Databases or View > Databases.


5 In External Database, enter or select the following:

6 From HSF Database, select the database for which to set up the external database connection.

7 From Connection Type, select Export.

8 In OLEDB Data source, enter the Data Source Name.

9 In User ID, enter the user ID used to access the relational database.

10 In Password, enter the schema password.

11 In Rule Set Name, enter a rule set name.

For information, see the Hyperion Strategic Finance Administrator’s Guide.

12 Optional: In E-mail Addresses, enter comma-separated E-mail addresses of individuals to notify if exportsfail.

Click Browse to locate E-mail addresses.

13 To export entities to the database, select Database Connectivity Enabled .

14 Click OK to save the connection settings.

HSF Administrator tests the connection and returns to the main window.

Configuring the Strategic Finance Server for Database Export 117

Index

Strategic Financedefinition, 11

AAccess

definition, 73Access Options

Accounts, 77Adding Permissions Groups, 78

Consolidation, 81Dimension, 80Entities, 76Reference, 81Reports, 79Scenarios, 80Time, 78

Access Types, 62Administrator Utility

navigating, 13Architecture, 11

CClient, 12Client-Server, 11Connection String, 43

DDatabase

Access, 73Backup

Backing Up, 39Connecting to External Databases, 43Email Notifications, 42PKZip, 39Restoring, 41

Scheduling Automatic Archives andTransmissions, 41

Transmitting, 40concept, 12creating, 37Creating from Consolidation Labels, 38definition, 37Deleting, 39export, 13Selecting, 38

Database Connectivity, 43Default Access

New Entities, 82task flow, 75

EEntities

accessing, 67Archives, 70, 71, 72Check-In Rules, 70

Setting, 70converting, 68

in bulk, 69Selected, 69

Default Access, 82definition, 67Locks, 68Owners, 67storage, 13templates, 13Upgrade, 68

Entity Change ManagementActivating, 87Adding User Groups, 89Adding Users, 89Breaking Locks, 90Changing the Owner, 90

A C D E F I L M O R S T U

Index 119

Editing Access to, 89Managing, 87Managing Access to ECM Documents, 88

Entity Groupsadding, 69definition, 67, 69deleting, 70editing, 70

Entity Locks, 97Breaking, 98

Event Logs, 101Exporting, 92

BatchesChanging Owners of, 94Overriding Default Access to, 93Setting Access, 93

Creating Connections to Other Hyperion ProductServers, 92

Managing Connections to Other Hyperion ProductServers, 92

MapsChanging Owners of, 95Managing Access to, 94Overriding Default Access to, 95

Extended Analytics, 43Creating Extended Analytics Database Tables, 49Rule Sets, 50

Accounts Options, 51Custom Dimensions, 53General Options, 50Scenarios Options, 52Time Options, 51

Star Schema Database, 47External Analytics, 47

Ffinancial models, 12

IImporting, 92

BatchesChanging Owners of, 94Overriding Default Access to, 93Setting Access, 93

Creating Connections to Other Hyperion ProductServers, 92

gg, 92

MapsChanging Owners of, 95Managing Access to, 94Overriding Default Access to, 95

LLogs, 99

MMaintenance, 97

OODBC Data source, 43

RRelational Database

Exporting, 68Rule Set, 43Rule Sets

Accounts Options, 21Creating, 20Editing, 20General Options, 21Scenario Options, 23Scenario Types, 23Time Options, 22

SScenario Types, 27

creating, 28managing, 28

Security, 16Authentication, 16NTLM, 16Provider, 16

Server, 12Connections, 18

Editing, 18Settings, 29

Configuring, 29General, 29


120 Index

TTransactions, 98

UUser Database, 84User Groups

Adding to Databases, Entities, or Entity Groups,84

Adding Users, 66Creating, 65database access, 73, 74Deleting, 66Deleting Users from, 66

User I.D., 43User Sessions

Viewing Session Information and DestroyingSessions, 100

UsersAccess Types, 62Adding, 83Adding and Editing, 62database access, 73, 74definition, 61Deleting, 65License Information, 65Looking Up Users in Remote Authentication, 63Managing, 61Renaming Users or Changing Network Domains,

64Selecting, 84


Index 121


122 Index