DRM Manual

ORACLE HYPERION DATA RELATIONSHIP MANAGEMENT, FUSION EDITION
RELEASE 11.1.1.1
N-TIER USERS GUIDE
Data Relationship Management N-tier Users Guide, 11.1.1.1 Copyright 1999, 2008, Oracle and/or its affiliates. All rights reserved. Authors: EPM Information Development Team This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS: Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.
Contents
Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Chapter 1. About Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Hierarchical Data Management Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Data Relationship Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Referential Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Validations and Verifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Imports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Automator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Blender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Property Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Relationship Management Typical Data Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . 20 Chapter 2. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Starting Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Creating Login Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Data Relationship Management Desktop and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Speed Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Main Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Action Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Contents
iii
Hot Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Using the Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Naming Metadata Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Chapter 3. Using Versions, Hierarchies, Nodes, and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Working with Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Version Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Creating As Of Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Using the Version Criteria Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Working with Hierarchies and Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Using Shared Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Opening Hierarchies and Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Hierarchy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Navigating Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Adding and Inserting Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Next ID Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Model After . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Moving Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Using Node Deletion Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Orphan Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Merging Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Finding Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Sorting Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Node Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Working with Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Using the Property Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Version and Hierarchy Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Administrator Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 User Assignment to Property Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 User Assignment to Node Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Chapter 4. Running Imports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Import Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Import Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Starting the Import Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Naming Import Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Configuring Section and Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Configuring Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Specifying File Format Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
iv
Contents
Configuring Duplicate Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Viewing Import Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Chapter 5. Using Automator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Performing Automator Imports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Running Automator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Reviewing Automator Processing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Automator File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Supported Automator Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Required Automator Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Chapter 6. Using Blender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Blender Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Using the Blender Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Configuring Blender Versions and Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring Top Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Viewing Blender Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Chapter 7. Running Exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Export Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Starting the Export Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Top Nodes Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Select Columns Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Column Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Column Widths Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Parameter Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Generation Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Hierarchy Compare Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Hierarchy Difference Report Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Hierarchy Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Lookup Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Property List Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Merge Log Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Transaction Log Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Version Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Ancestor Export Parameters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Verification and Filter Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Exclusion Filter Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Output Formatting Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Output Destination Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Contents
Using Export Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Chapter 8. Using Verifications and Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Verifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Validation or Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Validation Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Validation and Verification Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Running Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Running Verifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Viewing Verification Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Chapter 9. Running Property Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Working with Property Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Property Query Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Performing Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Property Query Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Hot Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Chapter 10. Comparing Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Hierarchy Compare Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Standard Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Property Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Renamed Node Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Comparing Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Chapter 11. Viewing Transaction History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Administrative Actions in Transaction History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Data Actions in Transaction History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Transaction History Range and Filter Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Transaction History Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Chapter 12. Using the Data Relationship Management Batch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Securing the Batch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Setting up Batch Client Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Running the Batch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Saving Versions in the Batch Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Command Line Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Configuration File Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
vi
Contents
Outputs and Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Chapter 13. Using Data Relationship Management Web Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Web Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Using Web Client Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Main Toolbar and Hierarchy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Selecting Versions and Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 How do I display the home page after I install or update Data Relationship Management Web Publishing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 How do I start the Data Relationship Management Web engine? . . . . . . . . . . . . . . . 190 How do I check for error messages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 How do I check for connectivity with the Data Relationship Management application server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Appendix A. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Enabling Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Enabling Keyboard Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Contents
vii
viii
Contents
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
10
Documentation Accessibility
1
In This Chapter
About Data Relationship Management
Features.............................................................................................................................11 System Architecture ...............................................................................................................13 Data Relationship Management Components...................................................................................14 Data Relationship Management Typical Data Life Cycle .......................................................................20
Features
Oracle Hyperion Data Relationship Management, Fusion Edition functions as a hub where reporting structures are maintained, analyzed, and validated before moving throughout the enterprise.
Key Features
Data Relationship Management does the following:

Manages hierarchies, business rules, mappings, and validations Enforces referential integrity across all subscribing systems and hierarchies Enables users to create and manage alternate views Maintains historical versions for comparative reporting and analysis Tracks all hierarchy and attribute changes with a full-featured audit log Manages parallel hierarchies Can serve as the main point-of-entry to update subscribing systems or be used after-thefact for reconciliation and analysis
Ease of Use
Although Data Relationship Management is designed to manage and validate the most complex dimensional structures and their related metadata requirements, the interface provides an intuitive and familiar look and feel. For each system or data set that the tool manages (through import or direct input), there is a graphical representation of the data. To validate this dimensional data, a metadata repository contains user-defined business rules, validation instructions, and relationship information. As
Features
11
the dimensional data changes in each participating system or within Data Relationship Management, data integrity issues are regulated, validated, and reported.
Efficiency
Data Relationship Management is specifically designed to synchronize data across multiple systems. All functionality in the tool is focused on adding efficiency to the hierarchical data management process. The implementation of Data Relationship Management involves a configuration process, as opposed to a custom development process. Configuration mitigates the inherent risks and testing cycles associated with custom programming. After implementation, Data Relationship Management provides several data management features that support large-scale analysis and reconciliation of data.
Table 1
Efficiency Features Benefit Multiple instances of data dimensions can be saved and used for historical reporting, comparisons, reconciliations, and what-if analyses User-defined validations, ranging from simple data verification to organizational policies, can be applied across dimensions in a real-time or batch mode Tools that enable the user to analyze integrity issues across multiple data sets
Feature Versioning
Business rule enforcement
Hierarchy debugging tools
Flexibility
To support the changing needs of a dynamic business environment, Data Relationship Management provides an intuitive, graphical configuration utility. This utility, designed for the non-technical user, enables immediate changes to Data Relationship Management functionality without the need for custom programming.
Security
The security model of Data Relationship Management manages user access at the following levels:
VersionsUser access is restricted based on the version status

A working version is accessible to all users based on their access A submitted version is editable only by system administrators and functional administrators. Finalized and expired versions are read only to all users and administrators.
HierarchyUser access can be restricted to certain areas within a hierarchy. For example, within the chart of accounts, a group of users may only need to maintain the Asset structure. If a user does not have access to a hierarchy, the hierarchy is not displayed. If a user does not have access to any hierarchies in a version, the version is not displayed.
12
Property categoriesUser access can be restricted to certain property categories for a specified node. In most cases, property categories are based on a system basis. For example, a user may be allowed to access the Essbase property category with read/write permission and the Financial Management property category group with read-only permission. If a user does not have access to a property category, the tab does not display. Administrative and user typesUsers can be grouped into four types:

System Administrator has full access including to metadata Functional Administrator has full access to the hierarchy data but does not have ability to change metadata Security Administrator can only create and assign logins Normal user has access to only the information based on the node access groups to which they are assigned and the property categories to which they are granted access
The configuration utility for Data Relationship Management supports user-defined validations that enforce integrity and policy issues. These business rules can be applied during the data entry process or routinely in a batch mode.
Hierarchical Data Management Types

Types of hierarchical data managed by Data Relationship Management are:

Organizational structures Charts of accounts Products Customer relationships
System Architecture
The Data Relationship Management N-tier application is based on an application-server architecture. Use of an application-server architecture enables the bulk of the system processing to be performed on a centralized server and simplifies the client requirements for each end user. The following diagram gives a top-level overview of the Data Relationship Management N-tier architecture. The Data Relationship Management client is a Windows application that runs on the users local computer. The client connects to the Data Relationship Management application server which can support multiple, simultaneous users. The Data Relationship Management database can be hosted on the application server machine or elsewhere.
System Architecture
13
Figure 1
N-tier Architecture
Data Relationship Management Components

The following topics describe the main components and features of Data Relationship Management.
Applications
A Data Relationship Management installation can use multiple back-end databases to support the many business needs for hierarchical data within an organization. Each database is referred to as an application, and each application is independent from any other application. If you are in doubt about which application to use, see your system administrator.
Versions
Data Relationship Management groups sets of hierarchies into versions. A version represents a single, independent set of data arranged into related hierarchies. Versions are usually related to time periods or functions. Examples of versions are March 2001, 3rd Quarter 2000, and Planning. All Data Relationship Management maintenance is performed in versions; users cannot copy or move nodes across versions. The only features that work across versions are compares and some exports. Nodes and properties within a version are shared among the hierarchies within the version. Versions are typically used for the following purposes:
To represent a set of hierarchies used during a particular month (or other business cycle period). Each month a version is created, maintaining an audit trail of hierarchies. To differentiate between real and test data during system testing. To compare different versions to identify changes made to the hierarchies within a time dimension.
14
You can create new versions by copying existing versions, but, after a version is created, it is independent of other versions. Versions can be copied, created, and deleted by a system administrator. Each version has an associated status.
Table 2
Status Descriptions Description Users can edit the hierarchies within the version System administrators are performing final validations on the hierarchies. No further changes by other users are permitted No changes are permitted. From the current version, all exports to other systems are performed. The hierarchies are now out-of-date. Data is maintained for historical purposes and as an audit trail
Status Working Submitted
Finalized Expired
Hierarchies
A hierarchy is a set of nodes that are all descendants of the same node. Thus, a hierarchy is defined by its top node and represents all nodes in the hierarchical relationships below that top node. Hierarchies are contained within a version; and a version can contain multiple hierarchies. Hierarchies provide the main interface for a user when working with Data Relationship Management. Each hierarchy is usually associated with a certain view, external system, or management report. Examples of hierarchies are Line of Business, Geographic, SAP - Legal, and Management Summary.
Nodes
A node is a point within a hierarchy. Every point in a hierarchy is a node. For example, within a hierarchy that represents an organizational structure, a node might represent a department or a cost center. Within a version, a node may be a part of more than one hierarchy. A node can have many userdefined properties that store information about the node and control the use of the node within the information systems of an organization. The following terms are used to define the position of a node and behavior of the node within a hierarchy:
Table 3
Node Terminology Definition A node that cannot have children A node that can have children
Term Leaf Limb
15
Term Child Parent Descendants Ancestors
Definition A node directly below another node (if B is directly below A, B is a child of A) A node directly above another node (in the previous example, A is the parent of B) All nodes below a specified node (including children and all children of children) All nodes between a node and the top of the hierarchy (including the parent, the parent of the parent, and so on) All nodes directly below a node All nodes that share a parent node in a particular hierarchy A node not assigned to any hierarchy
Children Siblings Orphan
Referential Integrity
Referential integrity (RI) is a concept normally associated with relational databases. In Data Relationship Management, RI means that no relational data violates established keys or domain ranges. In this database context, RI refers to two core rules that the Data Relationship Management engine enforces while users are editing hierarchies:
A node must have the same children in all hierarchies. Thus, a node always represents the same rollup structure regardless of context. A node cannot exist more than once in a hierarchy. Thus avoiding any circular reference problems.
By enforcing RI, Data Relationship Management inhibits errors related to structure and redundancy that might occur during the maintenance process.
Properties
Properties are data elements that are similar to fields in a database. Properties can be defined and stored at four levels:

Version Hierarchy Global node - the value for the node is the same no matter what hierarchy it is in or what parent it has Local node - the value for the node can be different for the node in different hierarchies
Most properties in Data Relationship Management are defined at the node level and contain node descriptions. Examples include the name of a node (called Abbrev in Data Relationship Management), the description for a node, and the number of children of a node. Properties at the version and hierarchy level are less common. Examples include properties used for headerlevel information in Data Relationship Management exports.
16
The system administrator can define as many properties as needed. Data Relationship Management is delivered with two categories of standard properties:

System properties that define a node Statistical properties that provide information about a node
Inheritance
Inheritance is a feature that enables high-level nodes to share their property values with lower points in the hierarchy, eliminating the need to store and maintain redundant information. It enables newly entered nodes to automatically obtain their property values from the appropriate ancestors. Proper use of inheritance can greatly reduce data-entry requirements. When defining a property, the system administrator can define the property as inheriting. This definition enables the values for the property to cascade down to its descendants. Inheritance moves through a specific chain of events to determine the value for a property: 1. Data Relationship Management looks for a value entered at the current node. If a user has directly entered a value at the node, the entered value is used. 2. If a value does not exist, Data Relationship Management searches the ancestors of the node for a value. The first entered value that Data Relationship Management finds, moving up the hierarchy is used. Thus, a change to the properties of a node can affect any descendents. 3. If no ancestor has an entered value, the default value is used. A default value is assigned by the system administrator. Global properties that inherit follow a slightly different path. In step 2, as Data Relationship Management moves up the hierarchy in search of an entered value, it encounters the ancestors in the controlling hierarchy. When the system administrator creates a global property, a controlling hierarchy must be designated for the property. A controlling hierarchy tells the system which hierarchy to use to determine the inheriting value for a global property. Many tools are available in Data Relationship Management for maintaining inherited values:

Locking a value so that it cannot be overridden at a descendant Clearing all descendant values for a particular property Removing an overridden value so that the property inherits from a node above
Validations and Verifications

Validations and verifications are tests to ensure that hierarchy rules are observed. They help enforce business rules.
Validationsrun automatically (in real-time) as users edit the structures and properties of hierarchies. Validations are automatically performed for the node being edited and also for its parent. Verificationsrun on-demand (as a batch) after users make a set of changes. Users can choose specific verifications or run a set of verifications defined by the system administrator.
17
Validation and Verification Example

An organization has a business rule that requires that a sales representative assigned more than 20 customers obtain special approval from the marketing department.
A validation using this business rule within Data Relationship Management permits no more than 20 customers to be added to a sales representative node. A verification using this business rule reports only upon sales representatives with more than 20 customers.
Comparing Validations and Verifications
Some business rules call for real-time enforcement and, therefore, should be defined by the system administrator as validations. Other business rules only need to be monitored and should be established as verifications. In the preceding example, a verification is probably more appropriate because, in certain circumstances, it is appropriate for a sales representative to have more than 20 customers. Validations are more appropriate for rules that can never be broken and require immediate enforcement.
Imports
Data Relationship Management can import data from external systems of various formats, including text files, data extracts, and other sources. An import is always performed on a new, empty version that is created as part of the import process. Thus, the user can verify that the import has run correctly before moving the imported data into a production environment. After the data is verified, Blender can be used to incorporate the new data. Imports can be customized and saved by any Data Relationship Management user who is authorized to run imports.
Automator
Automator is an alternative mechanism that enables Data Relationship Management users to make bulk hierarchy changes. The changes are defined in a text file. The functions supported are typical node and property manipulations. When Automator is used, the changes defined in a text file can be performed automatically and easily. Rather than using Automator, you can make corrections to the data as it is processed.
Blender
Blender enables you to combine elements of two versions into a new version or to combine elements into an existing version. The elements to be blended can include various combinations of structural elements such as hierarchies, nodes, and properties.
18
Exports
Exports are tools that are used to transfer hierarchy data to external systems or to a database table. Exports are sometimes referred to as reports or extracts. Exports also serve as the main reporting mechanism for Data Relationship Management. Data Relationship Management provides users a wizard-like export builder that enables them to create and save exports. Exports can create paper reports for distribution or text files to be imported by external systems. If an external system requires a complex export that cannot be generated by the report writer, a new class of export can be created by the programming team and added into the export builder. Each export class has a set of parameters that enable it to be customized for a users specific requirements.
Property Queries
Using Structured Query Language (SQL) to query hierarchically structured data has always been difficult (if not impossible) due to the recursive nature of the required query. Property queries enable you to investigate the hierarchical structure and the property values of sets of nodes without the need for complex recursive SQL programming. Property queries can be used for several purposes:

To find nodes that meet certain criteria In exports and comparisons as a filtering mechanism As a parameter in a generic validation routine (providing queries additional functionality as validations)
Users create a list of criteria, similar to the WHERE clause in a conventional SQL statement, and run it against a set of nodes. The property query returns a list of nodes that meet the defined criteria. Note that:
Property queries can be saved, so Data Relationship Management users can create and share their own toolkit of queries The system administrator can create standard queries that are available to all users
Global property queries are similar to property queries but are run against the list of all nodes in a version instead of against a particular set of nodes within a hierarchy. Because a global property query runs against a set of nodes without reference to a hierarchy, only global properties can be included in the criteria. Property queries can be used as the basis for filters for exports and compares as well as the basis for validations and verifications.
Compare
The Compare feature enables you to compare of the structure and node properties of hierarchies and versions.
19
Three Compare options are available:
The standard Compare option requires that two points, one in each of two hierarchies, be selected. Their structures are then analyzed for differences. The points may be in different versions. The Property Compare option enables two points, one in each of two hierarchies. The representatives of a particular property within the hierarchies are then analyzed for differences. The Renamed Node Compare option duplicates the standard Compare option, except it treats renamed nodes as being the same for comparison purposes. For example, assume that Hierarchy 1 in a compare includes nodes A, B, and C, and Hierarchy 2 includes nodes A, B, and C, but node C has been renamed to CC. The Renamed Node Compare option does not identify differences between the two hierarchies. But the standard Compare option regards nodes C and CC as different.
Note:
The Renamed Node Compare option should only be used between versions that are related (that is, one copied from the other). A Compare process returns two lists:

A list of all nodes that exist in the first hierarchy but not in the second A list of all nodes that exist in the second hierarchy but not in the first
Queries can be used to filter the lists of nodes to be compared.
Data Relationship Management Typical Data Life Cycle

Most organizations use Data Relationship Management on a cyclical basis that matches their management reporting periods (typically every four weeks or every month). Within each reporting period, the use of Data Relationship Management follows a predictable pattern:
Table 4
Data Life Cycle Principal Players System administrator
Task A Data Relationship Management working version is created as a copy of the finalized version for the previous period. The new version may contain multiple hierarchies (for example, for the chart of accounts, the organization structure, and the product structure). Changes are made to the working version by business users who have access to Data Relationship Management. Validations are automatically performed as users enter or amend hierarchy data. If necessary, bulk changes to hierarchy data are performed using Data Relationship Management Automator.
Data Relationship Management users
Data Relationship Management users and/or the system administrator
20
Task As the reporting period deadline looms, the version status is changed to submitted (changes by users are no longer permitted). Validations and verifications are performed to ensure the integrity of the data. Compare options can be used to identify changes. When data integrity is assured, the version status is changed to finalized (no further changes are permitted). Simultaneously, the version status for the previous reporting period is changed from finalized to expired, and the version is stored for possible future use in historical analyses or as an audit record. Exports are performed from the new finalized version to feed hierarchy data to participating systems. After all exports are complete (and have been loaded by the destination systems), all participating systems have consistent hierarchical data as a basis for the period end reporting process. And the cycle repeats for the next reporting period.
Principal Players System administrator
System administrator
System administrator
Existing organizational workflow constraints can be enforced by Data Relationship Management:
Business rules might require that all new cost centers be approved by Corporate Treasury. In this case, a property can be added to indicate approval, and no nodes are exported to other systems until the property is changed to approved. Corporate Treasury can be granted access to Data Relationship Management to update only the indicator property. A property query can also be defined to identify indicator nodes. Business processes might require that all hierarchy updates be redirected to a dedicated group responsible for implementing such updates. Following review and approval, using Automator, changes can be entered into a flat file for bulk loading into Data Relationship Management. This automated approach can significantly reduce potential typing errors.
Other tasks that are performed on an irregular basis:
New hierarchies can be established to support an expansion in scope of the participating systems. Such an action is performed using a process similar to the initial load of Data Relationship Management with hierarchical data. Hierarchies can be restructured to match a change in business needs. Data Relationship Management includes tools, such as Blender, to facilitate this process.
Data Relationship Management Typical Data Life Cycle
21
22
2
In This Chapter
Getting Started
Starting Data Relationship Management ........................................................................................23 Data Relationship Management Desktop and Menus ..........................................................................25 Naming Metadata Objects ........................................................................................................32
Starting Data Relationship Management

To start the Data Relationship Management client:
1 Select Start, then Programs, then Oracle EPM System, then Data Relationship Management, then Data
Relationship Management .
Figure 2
N-tier Login Dialog Box
2 From the Connection drop-down list, select the login connection for the preferred application server.
If no login connections were defined, you are prompted to create a connection. For instructions, see Creating Login Connections on page 24.
3 In the User Name text box, enter a user name or use the default. 4 In the Password text box, enter a password.
Starting Data Relationship Management
23
Note:
User names and passwords are not case-sensitive.
5 Click OK.
Creating Login Connections

The ability to create and save login connections was designed to simplify the login process and avoid inadvertent connections to the wrong environment. If no login connections were defined, the user will is prompted to create a connection.
To create a login connection:

1 In the login dialog box, click the [...] button to the right of the Connection list to display the Login
Connections dialog box.
Figure 3
Login Connections Dialog Box
2 Enter a meaningful name for the connection, such as DevServer or Production, to indicate the environment
being used.
3 Enter the HTTP server URL for the Data Relationship Management application server. 4 Click Test to verify the specified URL. 5 Enter the primary User Name to be used with this connection. 6 Click OK to save and close the dialog box.
Additional connections can be created by clicking the [] button on the Login dialog box. Existing connections can be subsequently edited or deleted.
24
Getting Started
Changing Passwords
To change your password:
1 From the Data Relationship Management main menu, select Tools, then Change Password.
The Change Password dialog box is displayed.
Figure 4
Change Password Dialog Box
2 Enter your old password in the Old Password text box. 3 Enter your new password in the New Password text box. 4 Enter your new password a second time in the Confirm Password text box.
Note:
Your password must contain three of the following elements:
Uppercase letters Lowercase letters Numbers Special characters
5 Click OK.
Data Relationship Management Desktop and Menus

This topic describes the following areas of the Data Relationship Management Desktop:

Speed Buttons on page 26 Main Menu Commands on page 26
25
Action Menus on page 29 Hot Keys on page 29 Using the Options Dialog Box on page 29
Speed Buttons
Speed buttons enable rapid access to frequently used functions within Data Relationship Management. They are displayed just following the menu bar of the Data Relationship Management Desktop and at the top of most other Data Relationship Management windows. To review the function of a speed button, hold the mouse cursor over the button. In a few seconds, a hint will be displayed that explains the function of the button.
Table 5
Speed Buttons Action Open currently selected hierarchy
Speed Button
Send current hierarchy tree view to a printer
Perform Take (copy/move) operation on currently selected node
Perform Put (paste) operation under currently selected node
Open Find Nodes dialog box to search for a node
Expand currently selected node to display it's children
Collapse currently selected hierarchy to only display top node
Open Properties Editor for currently selected version or hierarchy
Main Menu Commands

The Data Relationship Management menu commands and their usage are listed following.
Table 6
File Menu Commands Description Displays the Hierarchy Open dialog, box to select a hierarchy (or set of hierarchies) to open Closes the active Hierarchy window
Menu Item Open Close
26
Getting Started
Menu Item Close All Import Export/Report Blender Automator Printer Setup Print Preview
Description Closes all open Hierarchy windows Opens the Import dialog box, to import data from external files or systems Opens the Export dialog box, to run an existing export or to build a new export Opens the Blender dialog box, to blend data from two versions Opens the Automator dialog box, to process transactions from a flat file Opens the Print setup dialog box From Top Displays the hierarchy from the highest point From Here Displays the hierarchy from the selected node downward
Print
From Top Prints the hierarchy from the highest point From Here Prints the hierarchy from the selected node downward
Exit
Table 7
Closes Data Relationship Management Edit Menu Commands Description Removes the selected node from its position in the hierarchy and places it in the clipboard Pastes the contents of the last Take from the clipboard as a child of the currently selected node Create a new node to insert into the hierarchy Insert an existing node into the hierarchy Opens the Inactivate Nodes dialog box Reactivates an inactive node Removes selected node from the hierarchy Opens the Delete Nodes dialog box Removes the node from the hierarchy, and deletes it if it is an orphan (For example, if a node has the same parent in all hierarchies in which it exists, then an annul will result in the node being deleted) Annuls all nodes following the selected node Opens the Remove Duplicates dialog box (enables property values to be removed) Opens Find Node dialog box to search for node in currently selected hierarchy Opens Find Node dialog box to search for node in all hierarchies of selected version Selects all the nodes in the list view pane of the active hierarchy
Menu Item Take Put Add Node Insert Node Inactivate Reactivate Remove Delete Annul
Annul all below Remove Duplicates Find Global Find Select All
27
Table 8
View Menu Commands Description Displays the Property dialog box populated with the current nodes properties Expands the entire selected hierarchy tree to display all nodes (this may take a few moments for large hierarchies) Collapses the selected hierarchs, so that only the top node is displayed Default View Displays default labels for nodes in the selected hierarchy Description Displays description labels for nodes in the selected hierarchy. Default/Description Displays default and description labels in the selected hierarchies Defined Properties Displays for each node the user-defined properties
Menu Item Properties Expand All
Collapse All Nodes by
List
Ancestors Ancestors of the selected node Siblings Siblings of the selected node Descendants Descendants of the selected node Children Children of the selected node Links All instances of the node in other hierarchies
Refresh Refresh All

Table 9
Refreshes the screen from the database. Refreshes all items in the Version control window
Tools Menu Commands Description Opens the Property Query dialog box to search the selected hierarchy for nodes that meet a defined set of criteria Opens the Global Property Query dialog box to search the version node list for nodes that meet a defined set of criteria Opens the Compare dialog, to identify structural differences between two hierarchies Opens the Property Compare dialog box to identify property differences between two hierarchies Opens the Renamed Node Compare dialog box (similar to a standard Compare, except that renamed nodes are not identified as 'different' between the two hierarchies) Name Search and synchronize based on node name Property Search and synchronize based on property value Primary Node Name Search and synchronize by primary node
Menu Item Property Query
Global Property Query
Compare Property Compare
Renamed Node Compare
Synchronize by
Change Password Transaction History (Session)
Use to change user password. Opens dialog box to view all (or desired subset) of transaction activity performed via Data Relationship Management Opens the dialog box to view request history
Request History
28
Getting Started
Menu Item Options
Description Opens the Options dialog box to customize the local Data Relationship Management installation
Action Menus
The action menu is a set of context-sensitive options that are displayed when the right mouse button is clicked. The action menu items change based on the active object.
Hot Keys
Hot keys allow frequently used functions to be accessed by pressing a certain key or combination of keys. If hot keys are available as a short cut for a function on a menu option, then the appropriate hot key is displayed next to that menu option. For example the <F11> key opens the Property Editor.
Using the Options Dialog Box

To set options:
1 From the Tools menu, select Options to display the Options dialog box.
On the General tab, various options can be configured that affect the way that the user interface looks and behaves.
29
Figure 5
Options - General Tab
2 Select the Properties tab.

The default properties to be displayed in the list view frame and hotlist of the Hierarchy window can be selected.
30
Getting Started
Figure 6
Options Dialog Box - Properties Tab
3 In the Category drop-down list, select All to display all available properties. 4 Optional: In the Available list box, select a property and click the appropriate arrow to add a property. 5 Optional: In the Selected Properties list box, select a property and click the appropriate arrow to remove
a property.
6 Optional: From the Default Category drop-down list, select a category to open when the property editor is
started.
7 Optional: Select Display All Tabs to display an additional property category tab in the property editor that
contains all properties.
8 Optional: Select Multi Line Tabs for the property editor to display all property category tabs stacked on
multiple lines.
9 Select the Exports tab to set default parameters for running exports.
31
Figure 7
Options Dialog Box - Exports Tab
10 From the Default Output Mode text box, select an option from the drop-down list. 11 Optional: Select the User internal viewer option. 12 To use an external viewer, click
notepad.exe.
to browse for the program that you want to use as the viewer, for example
13 Click OK.
Naming Metadata Objects

When you create metadata objects such as exports, queries, compares, imports, and so on, do not use special characters other than the following:

dash ( ) underscore ( _ ) number sign ( # ) ampersand ( & ) dollar sign ( $ ) at sign ( @ ) backslash ( \ ) forward slash ( / ) period ( . )
Caution!
Using special characters other than those listed will cause issues.
32
Getting Started
3
In This Chapter
Using Versions, Hierarchies, Nodes, and Properties
Working with Versions .............................................................................................................33 Working with Hierarchies and Nodes.............................................................................................38 Working with Properties ...........................................................................................................58 Security .............................................................................................................................66
Working with Versions

Data Relationship Management groups hierarchies into versions. A version represents a single, independent set of data that is arranged into related hierarchies. All Data Relationship Management maintenance is performed within a single version. Users cannot copy or move nodes across versions. Compare and export are the only features that work across versions.
Version Control Window

Immediately after logging in, the Data Relationship Management desktop displays the Version control window, which lists a tree view of the available versions, along with the hierarchies contained in each version.
33
Figure 8
Version Control Window
Version Status
The icon to the left of each version in the Version control window indicates the status of the version. The version status is used to control the work flow of hierarchy maintenance and can only be changed by the system administrator using the Data Relationship Management Admin Tool. Table 10 describes each version status icon.
Table 10
Version Status Description Users may edit versions with this status Only system administrators are allowed to make changes to versions with this status (Users are not allowed to make changes) No one can edit this version.
Status Working Submitted
Finalized No one can edit this version. Expired
Memory and Display Status

In addition to version status, the memory status may be displayed as text, to the right of a version or hierarchy name. Table 11 describes memory and display status.
34
Table 11
Memory Status Applies To Versions Hierarchies Versions Description Indicates that the version has been loaded into memory. Indicates that the hierarchy is currently displayed in a hierarchy window. Indicates that the version is not attached to the database and changes are made in memory only. To retain the changes, this version must be manually saved.
Status Open Shown Detached
Note:
The Open and Shown statuses are indicated by a bold version or hierarchy name.
Action Menu
When a version is selected, various options are available on the right-click menu.
Figure 9
Version Control Window - Right-click Menu
Table 12 describes the right-click menu options.
35
Table 12
Version and Hierarchy Right-click Menu Options Description Version Create a new version in a detached state Hierarchy Create a new hierarchy within the current version
Menu Option New
Open Open All Open Selected Open Baseline Close Version Close Baseline Copy to New Save Create As Of
Open the current hierarchy Open all hierarchies in the current version Prompts user to select which hierarchies to open Prompts user to select a hierarchy to open in a baseline version Close the current version Close the baseline version of the current version Copy the current version to a new version in a detached state Save a detached version Create snapshot (in a detached state) of current version as of some past date and time by rolling back transactions that occurred after that time Use Save to save the as of version if a permanent copy is desired.
Delete Properties Assign
Delete the currently selected version or hierarchy Show properties of currently selected version or hierarchy Validation Assign existing validations to be run Verification Assign existing verifications to be run
Verify
Assigned Run the assigned verifications Selected Select verifications to run
Verification Messages Clear Verify Results List
View status messages from verifications Clear the results of the verifications run Global Nodes Display list of global nodes in current version Orphan Nodes Display list of orphan nodes in current version
Controlled Properties Show Status Column
Show list of global properties controlled by current hierarchy Shows the version status column.
Creating As Of Versions
From the right-click menu of the Version control window, the create as of option enables you to create a snapshot of a current version at some past date and time by rolling back transactions that occurred after that time. Whenever a version is created or copied, and the AllowAsOf system preference is set to True, a baseline version is also created. The baseline version is read-only and
36
is not displayed in the Version control window. As changes are made to the version, the transactions are logged. These transactions can be used as a means to roll the baseline version forward to any point in time to generate a snapshot at that point. The desired point in time for the As Of Version can be specified as one of the following:

A date and time A date offset from the current date A specific transaction ID
Note:
When creating an As Of version, there can be a discrepancy when crossing Daylight Savings Time boundaries. For example, if today is February 21 and you request an As Of for the prior September 1 at 3:00 am, the As Of version that gets created is for September 1 at 4:00 am. This is because the current date is in Standard Time but the requested date is in Daylight Savings Time. To adjust for this, you can request the As Of version for 2:00 am to get the 3:00 am data. The opposite occurs when starting in Daylight Savings Time and requesting a date in Standard Time a 3:00 am request returns results for 2:00 am. For clients using Data Relationship Management to create daily delta exports using As Ofs, you can reduce the issue by selecting a time when no transactions are likely such as 3:00 am and verify that there were no transactions the day the export runs. Another approach is to have three versions of the export that differ only in the hour (3:00 am for normal, 2:00 am for one boundary and 4:00 am for the other boundary) and then schedule the normal export for most days and the special exports for the boundary days.
To create an as of version:
1 In the Version control window, right-click a version, and select Create As Of.
37
Figure 10
Create Version As Of Dialog Box
2 Select one of the following time frames for the As Of version:

Transaction Date/Time Transaction Date Offset (Days) Transaction ID For the Transaction ID option, click to open the Transaction History dialog box. The ID of the desired transaction can then be determined. For more information, see Chapter 11, Viewing Transaction History.
3 Click OK.
Using the Version Criteria Dialog Box

In some features of Data Relationship Management, the user may have the option to choose what type of version is desired for the specified operation. After a version is selected, the Version Criteria dialog box enables the user to select one of these options:

Normal Version - The selected version in its current state is used. Use Baseline - The baseline version of the current version is used. Create As Of - A snapshot of the current version at some past date and time is used.
Working with Hierarchies and Nodes

A hierarchy is a logical set of nodes within a version. Each hierarchy is usually associated with a certain view, external system, or management report. The set of nodes that makes up a hierarchy are all descendants from a single top node. In that way, a hierarchy is defined by its top node and represents all the nodes in the hierarchical relationships below that node.
38
Hierarchies are contained within a version, and a single version may contain multiple hierarchies. Hierarchies provide the main interface for a user when working with Data Relationship Management.
Using Shared Nodes

In Data Relationship Management, the concept of shared nodes is defined as multiple instances of a node within the same hierarchy. Explicitly shared nodes created during manual maintenance and import processes share global property values with the primary node. The global properties for shared nodes automatically reference the values of the primary node. Local properties can be specific to each shared node. With shared nodes you can:
Automate the alternate naming of the shared nodes for operations like drag and drop (using the Ctrl key) and Add/Insert Confirm before creating a shared node Create system-level properties that map shared nodes Create system-level referential integrity between shared nodes and primary nodes (for example you cannot delete a primary node that is linked to shared nodes) Display the structure below a shared node Move between shared nodes and the primary node Remove and delete nodes that are the primary shared node Rename the primary shared node (thus renaming all the shared nodes) Display a full member list that can be used for drag and drop-type operations used to create the shared nodes Find and display a shared node list to be used for navigation and analysis purposes
The system preference SharedNodeMaintenanceEnable enables the shared nodes. This preference is disabled by default. In addition, a hierarchy-level property EnableSharedNodes enables shared nodes on a hierarchy by hierarchy basis. This property is disabled by default.
Note:
If shared nodes are enabled, the default shared node system preferences (delimiter, unique string, zero-pad length) should not be changed.
For information on system preferences and properties, see the Oracle Hyperion Data Relationship Management N-tier Administrator's Guide. Additional properties are defined in Data Relationship Management to provide information about and between primary and shared nodes. These read-only properties are automatically created:
39
Primary Node Boolean property indicating if a node has shared nodes that point to it Shared Node Boolean property indicating if the node is a shared node Primary Node Name String property that returns the primary name portion of the shared node name. For non-shared nodes, this property returns the node name in its entirety. Primary Node Has Descendants Boolean property indicating if the primary node has structure below it. This is only populated on shared nodes. Primary Node Descendants Comma-delimited list of the descendants of the primary node. This is only populated on shared nodes where the primary node has structure below it. Primary Node Ancestors Comma-delimited list of the ancestors of the primary node. This is only populated on shared nodes. Shared Map Associated nodes property that maps the shared/primary nodes. This property is populated for shared and primary nodes. Missing Primary Node Boolean property indicating that the shared node resolves to a primary node that does not exist Primary Not in Hierarchy Boolean property that indicates if the primary node is not in the same hierarchy
Adding and Inserting Shared Nodes

Assuming the system has shared nodes enabled, if you try to add a node that already exists, the system asks you if you meant to insert a node. If Yes, then the Insert Node dialog box opens. If No, then an error message displays saying the node already exists in the hierarchy and you must select a different name for the node. In the Insert Node dialog box, select the Create Shared Node option. The Alternate Named shared node is created if needed. The drag and drop operations are enhanced to detect the CTRL key. If you hold CTRL and select a node, the system copies and inserts an Alternate Named shared node. When you drag and drop without the CTRL key, Data Relationship Management does a normal move operation.
Removing and Deleting Primary Shared Nodes

During a Remove, the system checks to see if the node being removed is a primary node. If it is a primary node, you must confirm the Remove operation. Upon confirmation, the system moves the primary node to the location of the first shared member that does not cause a duplicate issue and then removes that shared member. This has the effect of removing the primary member from the original location but does not remove the primary member from the hierarchy. If there is no shared member available or that does not cause a duplicate issue, then the primary node is just removed. During a Delete, the system checks to see if the node being removed is a primary node. If it is a primary node, you must confirm the delete operation. Upon confirmation, the system deletes all the shared nodes and the primary node.
40
Renaming Primary Shared Nodes

When you rename a node, the system checks to see if the node being renamed is a primary node. If it is a primary node, you must confirm the rename operation. Upon confirmation, the system renames the primary node and the shared nodes. Only the primary node can be renamed. The secondary shared nodes cannot be renamed.
Move to Primary Node

Use the Move to Primary Node menu command to jump from the shared node to the primary node.
Converting Shared Nodes to Primary Nodes

You can convert a shared node to a primary node if the primary node does not already exist in the hierarchy. If the primary node already exists, an error message is displayed.
Displaying Shared Nodes

Following are different ways to display shared node information in the system:
Showing Structure Below a Shared Node The Hierarchy viewer displays the structure below a shared node. This structure is read-only and is italicized to indicate that it is controlled from a different location. Drag and drop and maintenance operations are not valid in this section. Full Node List for Drag and Drop Creation A member list that contains all of the nodes in the hierarchy is provided so you can drag and drop into the hierarchy. In the Hierarchy Node list, you can double click to show the node. Find and Display Shared Nodes Select the show shared nodes on a single result option to find all instances of a node. A shared node list is displayed if a single node is returned by the initial search. The shared node list provides detailed information for each shared node and allows for further navigation to any instance of that node in the hierarchy.
Opening Hierarchies and Nodes

A hierarchy may be opened from the Version control window or from the main menu. When the first hierarchy for a particular version is opened, the entire version is loaded into memory.
To open a single hierarchy, do one of the following tasks:

From the Version control window, double-click the hierarchy name. From the Version control window, right-click the hierarchy and select Open.
41
To open all hierarchies within a version, from the Version control window do one of the
following:

Right-click the version name and select Open All. Double-click the version name.
Each hierarchy within the version opens in a separate window.
To open multiple hierarchies:

1 Right-click the version name (or any hierarchy within a version) and select Open Selected. 2 Select a version from the drop down list at the top of the dialog box.
A list of the hierarchies contained within the selected version are listed at the bottom of the dialog box.
3 Select hierarchies to open by using the <Ctrl> key and then click OK.
Hierarchy Window
The hierarchy window title bar shows the name of the hierarchy and version that are currently displayed.
To move a Hierarchy Window, click anywhere in the window title bar. While holding the left mouse key down, move the window to the desired location. To change the size of a Hierarchy Window, slowly move the mouse across a windows border. The cursor changes to a doubled arrow bar. Click and hold the left mouse key down, and then move the mouse up, down, or left and right, to resize the window. Data Relationship Management enables the opening of as many Hierarchy Windows as desired, although no hierarchy may be displayed in more than one window at a time. To select a specific hierarchy, click on any surface area of the desired window. The title bar that you click on changes colors and is displayed in the foreground. The top (or root) node of a specified hierarchy view can be changed. To change the top node of the view, select the desired node then right-click and select View From Here from the action menu. To revert to viewing the hierarchy from its true top node, right-click and select View From Top from the action menu.
42
The Hierarchy Window contains two main panes. The pane on the left is the tree view and presents the structure of the hierarchy. The pane on the right is the list view or child view and contains the children of the selected node. The list view also displays certain properties of the child nodes. The specific properties to be displayed can be configured using the View Nodes By button on the Hierarchy Window toolbar. You may also change the properties that are displayed in the Options dialog box from Tools. The following table describes each Hierarchy Window speed button.
Table 13
Hierarchy Window Speed Buttons Action Removes mark from all nodes in the hierarchy (Refer to section on Marked Nodes for additional information) Expands hierarchy view to display all marked nodes
Speed Button Clear all marked nodes
Expand to marked nodes Changes selected node to next node in the hierarchy that is marked Move to next marked node Enables selected node to be toggled back and forth between 2 nodes Opens or closes the list view pane of the Hierarchy Window Hide/show child panel Changes selected node to the parent of currently selected node if the parent is visible in the current view Determines the properties that are displayed by each node in the hierarchy. Options are: Default View displays default properties Description displays description property for the node Default/Description displays default properties and description Defined Properties user may configure any of the available properties to display Determines the location in which to display the Property Edit window Options are: None window not displayed. Undocked window displayed independent of Hierarchy Window Show at Right window displayed as right-most pane of Hierarchy Window Show at Bottom window displayed as bottom pane of Hierarchy Window
Move to previously selected node
Move to parent node
View nodes by
Dock/undock the Property Edit window
The hierarchy window right-click menu options are described in the following table.
43
Menu Option Properties Synchronize By Name (or Property)
Description Shows the properties for the selected node Searches for nodes in all opened hierarchies based on their name or a common property value Copies the currently selected node Pastes from the clipboard under the currently selected node Adds a new node to the hierarchy Inserts an existing node into the hierarchy Enables you to model a new node after an existing node Enables you to copy properties from a node. Enables you to paste copied properties to a node. Inactivates a node Reactivates a node Removes the node from the current hierarchy and any other hierarchies where it has the same parent (However, the node is not deleted from the version, so that it is available for later re-insertion) Removes the node from all hierarchies and deletes the node from the version. Enables the sort order of limbs and leaves to be set graphically Moves insertion point to the previously selected node. Expands the hierarchy from the selected node. Collapses the hierarchy from the selected node From Here Makes the selected node the top node of the hierarchy. From Top Reverts from a selected node as the top node to the true top node for the hierarchy.
Take Put Add Node Insert Node Model After Copy Properties Paste Properties Inactivate Reactivate Remove
Delete Order Children Move to Previous Node Expand From Here Collapse From Here View
Lists
Ancestors Lists ancestors of the selected node Siblings Lists siblings of the selected node Descendants Lists descendants of the selected node Children Lists children of the selected node Links Lists links of the selected node
Verify
Assigned Runs the assigned verifications for the node Selected Runs the selected verifications for the node
Transaction History (Node)
Displays the transaction history for the node
44
Navigating Hierarchies
To select a node, click a node in the tree view or list view pane.
Note:
To select multiple nodes, the list view pane must be used.
To expand a node, do one of the following:

Double-click on the limb in the tree view or list view pane. Click the plus (+) or minus (-) sign next to a limb. A plus sign (+) next to a limb indicates it is closed. A minus sign (-) indicates it is open.
Adding and Inserting Nodes

A node can be included in a hierarchy in one of two ways:

An existing node, not currently in the hierarchy, can be inserted. A new node can be created.
A new node can also be modeled after an existing node using the Model After function.
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client-created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
To insert a node:
1 Select the point of insertion, which will be the future parent of the new node. 2 Do one of the following:

Right-click to and select Insert Node. From the main menu, select Edit, then Insert Node. Use the keyboard shortcut <Ctrl+I>.
45
3 Select the name of the new node using one of these methods:
Enter the name of the node. If a name is entered that does not correspond to an existing node, you are prompted to locate an existing node. Click and choose a node from an existing hierarchy.
4 Click Insert.
To create and add a new node:

1 Select the point of insertion, which will be the future parent of the new node. 2 Open the Add Node dialog box by performing one of the following:

Right-click to display the action menu and select Add Node. From the main menu select Edit, then Add Node.
46
3 Enter the name and description of the new node. If a name is entered that corresponds to an existing node,
the user will be prompted to use the Insert Node dialog box.
4 Define the new node as Limb or Leaf 5 Use the Copy Properties option to copy some or all properties of an existing node to the new node if desired. 6 Click Add to create and add the new node.
When common prefixes are being used for node names, an option is available to pre-fill the Add Node dialog box with the desired prefix. The hierarchy-level properties PrefillLeafProp and PrefillLimbProp can be set to point to any node-level properties. Then when creating a new node, the name field is pre-filled with the value of the designated property for the parent of the new node.
Next ID Function
The Next ID function enables the automatic generation of node names using sequential numerical IDs and node prefixes. For example, a set of nodes can be created where each of them have a name like Org000xxx, where:

Org is the node prefix and can be any desired character string. 000xxx is the sequential ID and increments by 1 starting at 1.
This feature must be enabled by a Data Relationship Management system administrator for it to be visible to Data Relationship Management users:

The System Preference Allow NextID Generation must be set to True. The System Preference Allow NextID Key Creation Level can be set to Admin, Funct, Any, or None and determines the level of user that is able to create new ID keys.
To use the Next ID function, type the desired prefix into the node name field and click the id button.
If the prefix already exists in the system, then an ID value is returned that is one greater than the last ID previously generated. If the prefix has not been used before, then an ID value of 1 (with the appropriate number of leading zeros) is returned.
The total length of the ID (excluding the prefix and including any leading zeros as necessary) is determined as follows:
The hierarchy properties IDLengthLimbProp and IDLengthLeafProp can be set to point to node-level properties that specify the desired ID length for the specified node. If the IDLengthLimbProp and IDLengthLeafProp properties are not set, then the length of the next sequential ID will be used without any leading zeros.
47
Model After
When a new node is created, it typically shares many common characteristics with existing nodes. The Model After feature enables a new node to be modeled after an existing node and thus improves the efficiency of the node creation process by eliminating redundant steps. To use this feature, open the Hierarchy Window and select the desired node to be modeled after. The Model After dialog box can be opened in one of the following ways:

Right-click to display the action menu and select Model After. From the main menu select Edit, then Model After. Use the keyboard shortcut <Ctrl+M>
Figure 11
Model Nodes Dialog Box
The Node to Model field shows the name of the currently selected node. If another node is to be used to model after, click to open the Select Node dialog box. Any node can then be selected from any hierarchy in the current version. A node name can also be typed directly into the Node to Model field. However, if the name is not found as an existing node, it is displayed with strike through and cannot be used to model after. In the New Node field, enter the name of the new node. If the name already exists, the name is displayed with strike through. The node name can also be created using the Next ID function by clicking the id button. In the New Description field, the description of the new node can be entered.
Copy Properties
The following options can be chosen for copying properties from the original node to the new node:

None - no properties are copied. Defined - only defined properties are copied.
48
Selected - clicking
opens the Select Properties dialog box to select the properties to copy.
All - all properties are copied.
After the desired properties option is selected, clicking the Fetch button populates each of the tabs following with the appropriate data.
Hierarchies Tab
This tab lists each hierarchy in which the node to model after currently exists. The parent of the node in each hierarchy is also listed.
Global Properties Tab

This tab lists each of the global properties of the node to model after based on the copy properties option selected.
Local Properties Tab

This tab lists each of the local properties of the node to model after based on the copy properties option selected.
Figure 12
Model Nodes Dialog Box - Local Properties Tab
The local properties of the node to model after is listed for each hierarchy in which it exists. The various hierarchies can be selected from the Hierarchy drop-down list.
Automator Processing
After each of the desired options for the model operation are set, clicking the Automate button displays the Data Relationship Management Automator dialog box.
49
Figure 13
Automator Dialog Box
This window displays each of the underlying Automator commands that are used to create the new node and copy the desired properties. Clicking the Process button executes each of the commands. The result of each command can be verified by reviewing the Status column. You can save the automator to a flat file that you can edit and reuse. This completes the modeling of the new node. The Automator window and Model Nodes windows can now be closed.
Moving Nodes
Nodes may be moved within a hierarchy or to a different hierarchy:
Moving a node within a single hierarchy removes the node from its original parent and places it under the new parent. Moving a node to a different hierarchy is treated like a copy. The node is left unchanged in its original hierarchy. This function is identical to inserting an existing node.
To move a node, perform one of the following steps:

Drag and drop the node onto its new parent node in the hierarchy Use the Take and Put functions by selecting the node to be moved in one of the following ways:

Right-click and select Take. Use the <Ctrl+T> keyboard shortcut From the main menu, select Edit, then Take.
Select the new parent node for the move and do one of the following:
50
Right-click and select Put. Use the <Ctrl+P> keyboard shortcut From the main menu, select Edit, then Put.
Node Move Problems

A move to a new hierarchy may be unsuccessful for any of the following reasons:

A node with the same name already exists in the destination hierarchy. One of the descendants of the moved nodes already exists in the destination hierarchy. The new relationship fails an assigned validation.
Moving nodes within a hierarchy that has some shared nodes with alternate hierarchies and some non-shared nodes may cause a duplicate to be created in the alternate hierarchy. This fails the Data Relationship Management integrity constraint as described preceding and prevents the move operation. To accomplish the move, the user must first remove the node being moved from the alternate hierarchy before moving it to the main hierarchy. For many users, this causes an issue in the extra maintenance steps needed to perform changes. This can also be a problem when the moves are being done via Automator scripts or through an automated system via the API.
Relaxed Move Option

To facilitate a move that requires a node to be removed from an alternate hierarchy, you can use the Relaxed Move option. If the System Preference AllowRelaxedMove is set to True, the Relaxed Move is allowed. If the system preference is set to False or does not exist, then the normal integrity constraints are enforced. When moving a node, the Relaxed Move enables the new parent in the main hierarchy to take precedence over any conflicting parental relationships for this node in other hierarchies. Consider the four hierarchies in the following example: Hier 1 Hier 2 Hier 3 Hier 4 AXZS +B +X1 +Z1 + C | +C | +X2 +Z2 + 111 | +111 | +111 +111 +D +D The intent is to move node 111 from C to D in Hier 1. When AllowRelaxedMove is false, the move fails due to the insert under D in Hier 2 causing a duplicate node. When AllowRelaxedMove is true, the following occurs: Hier 1 Hier 2 Hier 3 Hier 4 AXZS
51
+B +X1 +Z1 + C | +C | +X2 +Z2 | | +111 +D +D +111 +111 Note that 111 is removed from under X2 in Hier 2 because it now exists under D in that hierarchy.
Using Node Deletion Methods

There are four methods by which a node can be deleted. The subtle differences in the terminology used are significant. The methods are listed in decreasing order of severity in the following table.
Table 14
Node Deletion Methods Result Removes the node from all hierarchies and deletes the node from the version Removes the node from the current hierarchy and any other hierarchies where it has the same parent (However, the node is not deleted from the version, so that it is available for later re-insertion) Performs a Remove on the node in all hierarchies where it has the same parent, and also Deletes the node if it is then an orphan:
Action Delete Remove
Annul
For example, if a node has the same parent in all hierarchies in which it exists, then an Annul will Remove the node from all hierarchies and then Delete it because it is then an orphan If the node does not have the same parent in all hierarchies, the Annul will produce the same result as the Remove
Inactivate
Flags the node as inactive so that it can be easily filtered from an export
Deleting Nodes
Only nodes with no descendents can be deleted.
To delete a node, select a node or set of nodes and do one of the following:

Right-click and select Delete. Use the <Ctrl+D> keyboard shortcut. From the main menu, select Edit, then Delete.
If the option to merge nodes is enabled, the Delete Nodes dialog box opens and presents the selected nodes and their associated merge status. The user can then choose which of the selected nodes to actually delete. It is important to note that when deleting a hierarchy, the nodes within that hierarchy are not deleted. If the nodes do not exist in any other hierarchy within the version, then they become orphans after their resident hierarchy is deleted. If a large group of nodes needs to be deleted from a hierarchy, the Annul All Below command can be used.
52
Removing Nodes
To remove a node, and all of its children, select the node and do one of the following:

Right-click and select Remove. Use the <Ctrl+R> keyboard shortcut. From the main menu, select Edit, then Remove.
Annulling Nodes
When a node is annulled, the node is removed from the hierarchy, and deleted it if it is an orphan. For example, if a node has the same parent in all hierarchies in which it exists, then an annul will result in the node being deleted.
To annul a node:

Use the <Ctrl+N> keyboard shortcut. From the main menu, select Edit, then Annul.
To annul a set of nodes:

Use the <Ctrl+L> keyboard shortcut. From the main menu, select Edit, then Annul All Below.
Inactivating Nodes
Only nodes with no active children can be inactivated.
To inactivate a node, select a node or set of nodes and do one of the following:

Right-click and select Inactivate. Use the <F12> keyboard shortcut. From the main menu, select Edit, then Inactivate.
If the option to merge nodes is enabled, the Inactivate Nodes dialog box opens and displays the selected nodes and their associated merge status. Merge nodes may then be selected in an identical manner as when a node is deleted. Inactivated nodes are displayed with a red slash to indicate their status.
Reactivating Nodes
To reactivate a node, select a node or set of nodes and do one of the following:

Right-click and select Reactivate. Use the <Ctrl+F12> keyboard shortcut.
53
From the main menu, select Edit, then Reactivate.
The node is displayed normally without the red slash.
Orphan Nodes
An orphan node is defined as a node that exists in a version but that is not assigned to any hierarchy within that version. Orphans may exist pending a clean-up to completely remove them, or they may be awaiting re-allocation to one (or more) hierarchies in the version. Orphan nodes within a version may be viewed by right-clicking on a version in the Version control window and selecting List, then Orphan Nodes. A hot list of orphan nodes is displayed.
Figure 14
Orphan Nodes
You can add an orphan node to a hierarchy by doing one of the following:
Insert node and type the name of orphan node For more information, see Adding and Inserting Nodes on page 45.
Drag an orphan from the orphan node hotlist into the hierarchy
It is possible for an orphan node to have descendants that are not orphans. To avoid this, the list of orphan nodes should be reviewed regularly. By right-clicking on each orphan in the hot list and selecting the View Structure option, a list of the orphan node's descendants is displayed.
Deleting Orphan Nodes

You can delete one or more orphan nodes. With the Delete option, the user will be prompted for merge information if the system is configured to require merging. With the Destroy option, the node is deleted immediately regardless of the merge requirements. Nodes with children can be deleted.
54
Merging Nodes
Tracking merge information is a Data Relationship Management option that enables users to specify nodes that should be used in place of deleted or inactivated nodes. External transaction systems supported by Data Relationship Management may still have transactions that refer to the deleted node. By keeping a merge list, Data Relationship Management is able to feed these systems appropriate node mappings that allow them to roll the data to a new valid node. Merging is an option that can be configured by the system administrator in the Data Relationship Management Admin Tool. If the option to merge nodes is enabled within Data Relationship Management, then an appropriate dialog box is displayed when an attempt is made to delete or inactivate a node. This series of forms ensures that valid merge nodes are selected for each deleted or inactivated node.
Figure 15
Inactivate Nodes Dialog Box
To define a merge node from the Delete Nodes or Inactivate Nodes window,
1 Do one of the following tasks:
Enter the name of the merge node in the Merge Node column. Click and select a node name from an existing hierarchy.
The merge node defaults to the parent of the selected node.
2 Click Next to continue the delete or inactivate process.

The results of the delete/inactivate validation process are displayed. Valid transactions are presented in the top portion. Invalid transactions, along with an explanation, are presented in the bottom portion. To fix an invalid transaction, click Back to return to the merge selection form.
3 To complete the operation for approved transactions, click Delete or Inactivate.

If the delete option is disabled or the delete function is unsuccessful, it may be due to one of the following reasons:
A deletion can only be performed by users who are granted authority by the system administrator. A node may not be deleted if it has descendants.
55
The delete may fail an assigned merge validation.
Finding Nodes
There are two different ways to search for nodes. The Find feature searches for nodes within the selected hierarchy while the Global Find searches for nodes in any hierarchy within the selected version.
To use either find feature:

1 Do one of the following:
To use the Global Find feature, select a version in the version and do one of the following:

Use the <Ctrl+G> keyboard shortcut. Use the main menu and select Edit, Global Find.
To use the Find feature, select a hierarchy in the version and do one of the following:

Use the <Ctrl+F> keyboard shortcut. Use the main menu and select Edit, then Find.
Figure 16
Find Node Dialog Box
2 In the Search For text box, enter a string to search 3 From the Search In drop-down list, select one of the following node properties to search:

Name Description DisplayByString (available for Find but not Global Find)
56
4 Select Perform Exact Match to find nodes that match the search string exactly. This option is only available
when searching in Name.
5 In the Display Options section, select one of the following options:

Show in Lists to display a Hotlist of the nodes found Mark Nodes to mark the nodes in the hierarchy window Both to display a Hotlist and mark nodes
6 Select Go to First Node in List to automatically locate the first node in the search results and select it in
the hierarchy window.
7 Click Find to perform the search.
Sorting Nodes
Nodes are sorted in Data Relationship Management according to the following default rules:

Limbs are sorted ahead of leaves. Nodes are then sorted by their name.
This default sort order is similar to how folders and files are sorted by default in the Microsoft Windows Explorer.
Custom Sort Order

Nodes can also be sorted in any explicit custom sort order (although limbs are always sorted ahead of leaves.) The sort order can be defined by any property that has a property data type of SortOrder. (The SortOrder data type is special case of an Integer data type.) By default, any Data Relationship Management installation includes a property called Sort Order (assigned to the Default property category) that can be used for this purpose. To sort a hierarchy according to the value of a node-level sort order property, the hierarchylevel property StandardHierSort must have its value set to point to the appropriate node-level property that contains the sort order. A custom sort order can also be used that applies only to a specific Data Relationship Management user ID, enabling users to customize their display of Data Relationship Management data without impacting other users of the same hierarchy. This is controlled by the hierarchy-level property UserHierSort. If this property has been set to point to a node-level property that has a data type of Sort Order, then this sort order takes precedence over both the StandardHierSort property and the default sort order. If there is no value assigned to the hierarchy-level property StandardHierSort nor to UserHierSort, then the default sort order is applied. The value of a custom sort order property can be set in any of the following ways:
Sort order values can be loaded into a node-level sort order property when data is initially imported into Data Relationship Management (see following for details.) Explicit values can be defined for the sort order property for any node.
57
If a sort order property has been selected for a hierarchys StandardHierSort or UserHierSort properties, then the Order Children menu option is available by right-clicking on any node in a hierarchy. This opens a dialog box that enables the sort order of limbs and leaves to be set graphically. A node-level sort order property might be defined as Derived, and so might be automatically populated with a sort order.
Removing Custom Sort Orders

To disable the use of any sort order, the value of the hierarchy-level property controlling the sort order can be removed by right-clicking on it and selecting Remove Value.
Node Security
Node security settings can only be assigned by a Data Relationship Management user with administrative privileges. Security settings are maintained as property values, just like any other properties of a node. They are maintained in Data Relationship Management (and not in the Data Relationship Management Admin Tool) because Data Relationship Management offers better mechanisms for navigation within the hierarchy. For additional details, refer to the section on Node Access Group security in the Oracle Hyperion Data Relationship Management N-tier Administrator's Guide.
Working with Properties

Properties are data elements that are associated with nodes, similar to fields in a database. Properties enable Data Relationship Management to store extra information about each node. While there are a set of default properties including Name and Description, the system administrator can add as many properties as needed to support the subscribed systems.
Using the Property Editor

The property editor enables users to examine and edit property values for the currently selected node.
To access the editor, select a node and do one of the following:

Right-click and select Properties. Use the <F11> keyboard shortcut. The Property Editor is displayed either docked at the bottom or right, or undocked to the hierarchy window based on the user preference defined under options in the Tools menu.
58
Figure 17
Property Editor
Note that selecting View, then Properties from the main menu or using the Properties speed button on the main tool bar displays the Property Editor for the version or hierarchy selected in the Version Control Window.
Note:
You have edit rights to the property if property name is bold.
Categories
The Property Editor displays lists of properties categorized by a series of tabs which each define a Property Category. Each property category represents a set of logically related properties such as those belonging to a particular external system (for example, SAP or Essbase), or a specific functional area within the company. The system administrator can create as many property categories as needed. Data Relationship Management includes the built-in property categories listed in the following table.
Table 15
Property Categories Description Properties related to a nodes identifying characteristics, such as ID, name and description The only change that can be made to this category is assigning the read-only flag for individual users. Users with read-only access cannot edit values in the category, but can view them. Note: Properties cannot be assigned to thism category.
Category System
Stats
Properties that provide statistical information about the node such as number of children, number or siblings Validations assigned for the node one property for each validation
Validation
59
Category Verification Leaf Access Limb Access
Description Verifications currently assigned for the node one property for each verification Node security groups and their leaf access levels for the node one property for each group Node security groups and their limb access levels for the node one property for each group
Note the following information:
Not all property categories are visible to all users, because the system administrator can restrict user access to specific categories The Validation, Verification, Leaf Access, and Limb Access categories are available to system administrators only
System and Stats properties typically displayed at the node level are listed in the following table.
Table 16
System and Stats Properties Definition Numeric unique identifier for internal use Short, unique name Description of the node Boolean flag to define node as a leaf or limb

System Property Node ID Name (Abbrev) Description Leaf
If True, then node cannot have children If False, then node may have children
Leaf Access Limb Access Node Approved Ancestor List # Children # Descendants # Leaf Children # Leaf Descendants # Leaf Siblings Level # Limb Children # Limb Descendants # Limb Siblings
Indicates level of access to this node for current user (only applies if node is leaf) Indicates level of access to this node for current user (only applies if node is limb) Boolean flag to indicate that node has been in a Finalized version List of ancestor nodes from parent node up Number of nodes, one level beneath Total number of nodes beneath (at all levels) Number of children that cannot have other children Number of descendants that cannot have children Number of siblings that cannot have children Numeric level of node within hierarchy where top node level = 1 Number of children that may have children Number of descendants that may have children Number of siblings that may have children
60
System Property Linked Links # Links References # Siblings
Definition Flag indicating if the node exists in at least one other hierarchy List of all other hierarchies in which the node exists (excluding current) Number of other hierarchies in which the node exists List of all hierarchies in which the node exists (including current) Number of nodes which have the same parent as this node
Property Value Scope and Origin

The property editor displays two icons to the left of each property. The first icon indicates the scope of the property and if it can inherit values.
Table 17
Property Scope Icons Description The value of the property is constant across all hierarchies The value of the property is specific to the hierarchy in which it exists The value of the property is global and inherited The value of the property is local and inherited
Property Icon Global Local Global Inherited Local Inherited
The second icon denotes the origin of the property value.

Table 18
Property Origin Values Description The value of the property is defined by a default value (as set by the system administrator.) Default values are used when:

Property Icon Default
the property is non-inheriting and a user has not entered a value the property is inheriting and no ancestor value was found
Inherited
The value of the property is being supplied by an ancestor node. (The name of the ancestor node and the hierarchy from which the inherited value originates is displayed in the Status column of the Property window.) The value of the property was set by a user at this specific node The value of the property is derived from other values The value of the property has been locked which means that it cannot be changed in any descendant node that inherits this property's value.
Overridden Derived Locked
61
Property Icon
Description If this property value is viewed in a descendant node, its status is indicated with the lightning bolt icon for Static.
Static
The value of the property has been inherited from an ancestor node, whose value has been locked:

As a result, the value cannot be changed in the descendant node The name of the ancestor node and the hierarchy from which the inherited value originates is shown in the Status column of the Property window
Property Status
The Property Status column in the Property Editor provides the name of the ancestor node and the hierarchy in which an inherited value originates. When editing properties, this column also displays status messages that reflect how a value has been edited. The following table describes property statuses.
Table 19
Property Status Definition The value has been modified. The value has been removed - only applicable to Overridden property values. The classification of the property has been changed to Locked (i.e. the value cannot be changed in any descendant node that inherits the property.) The classification of the property has been changed to Unlocked (i.e. the value can be changed in any descendant node that inherits the property.) A request has been made to Clear All Below for the selected property (i.e. clears the value on all descendant nodes which have overridden their inherited values.)
Property status [Modified] [Removed] [Locked]
[Unlocked]
[Cleared]
Updating Property Values

Property names displayed in a bold font may be edited. Property names in regular text are not available for change. The value of a property cannot be edited if any of the following conditions exist:
The property has a derived value. For example, a property indicating the total number of child nodes are derived by Data Relationship Management and cannot be edited. The user does not have appropriate security rights to edit the value. The value of the property has been inherited from an ancestor node, whose value has been Locked.
To find a specific property:

1 Right-click in the property values area and select Find Property. 2 Select a property from the list and click OK.
62
The editor opens to the selected property.
To find a specific property category, right-click in the category tabs area and select Go to Tab. Local Security for Global Properties
You use two system preferences GlobalPropLocalSecurity and GlobalPropLocalOverride to control local security on global properties. In the following example, note that L1 is in both hierarchies. Assume that L1 has global property GP. H1 A B L1 L2 H2 Y Z L1 L3 If a user is given full access from the top of H1 and read-only access from the top of H2, then the user cannot go to L1 under H2 and edit it. However the user can go to L1 under H1 and edit it and the change to the global property can be seen on L1 under H2. This is the normal operation when GlobalPropLocalSecurity is false. When GlobalPropLocalSecurity is true and GlobalPropLocalOverride is blank then the changes to GP for L1 in H1 cannot be saved because it fails the local security check (the user does not have edit access in another hierarchy). However if GlobalPropLocalOverride is set with global property GP, then in the above situation the global property GP is excluded from the local security check and the user is able to save the changes to L1 in H1
Removing Property Values

To remove a value from a property, right-click the property and select Remove Value.
This removes the entered value and enables the inherited or default value to replace it.
Removing Duplicates
For a normal, defined property, Remove Duplicates removes any value equal to the default value in the selected node and any of its children.
63
For an inheriting property, this option removes any value equal to the inherited value in the selected node and in any of its children. For a read/write derived property, this option removes any value equal to the derived value in the selected node and any of its children. Remove Duplicates is also available from the Action Menu of the Version control window, if a hierarchy is selected. In this case, a dialog box enables the user to select the version, hierarchy, and properties to acted upon.
Clearing All Descendant Values

To clear the (overridden) value of a property in all descendant nodes, right-click the property
and select Clear All Below. The value of this property in all descendant nodes is replaced using the inheritance rules. A typical use of this feature is to clear the values of a property in all descendent nodes, in preparation for setting and locking a new value that cannot be subsequently changed in the descendent nodes (for example, the property appears classified as Static in the descendant nodes.)
Locking Property Values

If a property is classified as inheriting a user can lock the value. This action disables any changes to that value in inheriting descendant nodes.
To lock a property value, do the following:

1 Set the value of the property in the selected node. 2 Right-click the property and select Lock.
A padlock icon is displayed to the left of the property name. For all affected descendant nodes, a lighting bolt icon is displayed indicating the property is static. Note that if prior to applying the Lock, a descendant had overridden its inherited value, the Lock does not affect that descendant. To affect all descendants with the Lock command, use the Clear All Below option before applying the Lock.
Saving Changes to a Property Value

To save changes to any property values, click Save at the bottom of the Property Editor. The Save button is not available until a change to a property value has been made. To exit the Property Editor without saving any changes, click Close. When you are prompted to save your changes, click No.
64
Version and Hierarchy Properties

Hierarchy properties are defined at the hierarchy level and are the same for all nodes in the hierarchy. By definition, hierarchy properties are always local, defined properties.
Table 20
Hierarchy Properties Definition Unique, internal identifier for the hierarchy Hierarchy name Hierarchy description Points to the node-level property that is used to determine if a specified node is a certain Node Type Shows property currently used for sorting the hierarchy Integer value to allow sorting the order in which hierarchies appear within the version Indicates the System Category (folder) to which this hierarchy belongs, if any Default for displaying nodes within the hierarchy Default property by which to synchronize nodes for the current hierarchy. Points to the node-level property that is used to pre-fill node name when creating new leaf node Points to the node-level property that is used to pre-fill node name when creating new limb node Points to a node-level property to determine default sort order within the hierarchy Name of the top node for the hierarchy Node ID of the top node Determines how hierarchy nodes display for the current user Property by which to synchronize nodes in the selected hierarchy for the current user Points to a node-level property to determine sort order within the hierarchy for the current user Determines how hierarchy is filtered for the current user
Hierarchy Property Hier ID Hier Name Hier Descr HierarchyNodeType
Hier Sort Hier Sort Order Hier System Category DefaultDisplayBy Default Synchronize By PrefillLeafProp
PrefillLimbProp
StandardHierSort Top Node Top Node ID UserDisplayBy User Synchronize By UserHierSort
UserHierFilter
Version properties are defined at the version level and are the same for all nodes in all hierarchies. By definition, version properties are always global, defined properties. Version properties are rarely used. Examples include the version name, description, and status.
65
User-Defined Version and Hierarchy Properties

User-defined properties can be established at both the hierarchy and version levels. Thus, version and hierarchy properties can have different values for different users for the same property.
Security
Security provides a brief overview of the security mechanisms within Data Relationship Management. For complete details, refer to the Oracle Hyperion Data Relationship Management N-tier Administrator's Guide. All Data Relationship Management users require a username and password. There are four additional factors that affect the security access of a user in Data Relationship Management:
Assignment of a user as a Data Relationship Management administrator (either system, functional, or security administrator). Version status For non-administrator type users, assignment of a user to node access groups For non-administrator type users, assignment of a user to property categories
Users with questions about their access privileges to Data Relationship Management should contact their Data Relationship Management system administrator.
Administrator Types
There are three administrative types in Data Relationship Management:

System Administrator Functional Administrator Security Administrator
System Administrator
If the user is designated as a system administrator, the user can perform all tasks in Data Relationship Management. The privileges of system administrators include the ability to:

Perform exports from any version Edit submitted versions Assign security Assign validations and verifications Edit metadata including property definitions, users, validations, and verifications
66
Functional Administrator
If the user is designated as a Functional Administrator, the user can perform all tasks in Data Relationship Management and edit lookup and lists tables for properties from the Admin menu. The privileges of functional administrators include the ability to:

Perform exports from any version Edit submitted versions Assign security Assign validations and verifications Edit property lookup and list tables from the Admin menu
Security Administrator
If the user is designated as a security administrator, the user can only create users and assign users to node access groups and property categories
User Assignment to Property Categories

Property categories are groupings of properties.
Property categories are visible to Data Relationship Management users as tabs in the property editor. Users can be assigned to multiple property categories to control their access to the hierarchies.
User Assignment to Node Access Groups

Node access groups are used to control user access to hierarchies and nodes. Data Relationship Management users may be assigned to specific groups that have permissions to certain nodes within Data Relationship Management. Security based upon groups is more subtle than the onoff access determined by a user's allocation to a property category, because multiple tiers of access levels may be assigned to a specified group.
Security
67
68
4
In This Chapter
Running Imports
Import Elements....................................................................................................................69 Import Sections ....................................................................................................................70 Starting the Import Wizard ........................................................................................................70 Naming Import Versions ...........................................................................................................71 Configuring Section and Processing Options ....................................................................................72 Configuring Mappings .............................................................................................................74 Specifying File Format Information ...............................................................................................75 Configuring Duplicate Handling...................................................................................................78 Viewing Import Results ............................................................................................................80
Data Relationship Management can import data from external systems of various formats, including text files, data extracts, and other sources. An import is always performed on a new, empty version that is created as part of the import process. Thus, the user can verify that the import ran correctly before moving the imported data into a production environment. After the data is verified, the blender tool can be used to incorporate the new data. Imports can be customized and saved by any Data Relationship Management user authorized to run imports. You use the import wizard to run imports.
Caution!
When running Imports, the regional settings of the server must be used to format date and time information. For example, if the regional setting for the server specifies that date should be formatted as dd.mm.yyyy, then the data given to the import should be in that format. The Import does not do any date/time conversions from one format to another so if the information is not in the correct format then it will not display correctly or at all.
Import Elements
An import consists of the elements in the following table.
Import Elements
69
Table 21
Import Structure Description Attributes of the import, such as version, error-handling settings, and filenames Information about the import, such as hierarchy, node, and relationship (Configuring a section can include designating section headers and delimiters) Data attributes to be imported (An Import Column is mapped to a corresponding non-read-only property in Data Relationship Management, such as name and description. Configuring a column involves selecting a property to populate, ordering the column, and sometimes mapping the column to a particular set of hierarchies. If the input format is a fixed-width text file, the column width should also be configured.)
Import Element Import Sections
Columns
Import Sections
An import can contain any or all of the following sections:
Table 22
Import Sections Description Version property values Required column: version name
Import Section Version
Hierarchy
Structural information about each hierarchy and top node to be imported and, perhaps, hierarchy property values. Required columns: hierarchy name, top node
Node
Structural information about each node to be imported and, perhaps, node property values Required column: node name
Relationship
Parent-child information about each relationship to be imported and, perhaps, node property values for the child in each pair. Required columns: parent node name, child node name
Hierarchy Node
Node values specific to a specified hierarchy Required columns: hierarchy name, node name
Starting the Import Wizard

To start the import wizard:
1 From the Data Relationship Management main menu, click File, then Import.
70
Running Imports
Figure 18
Import Wizard: Import Type
2 Select an import type or a saved import and click Next.

Selecting a parent import type (for example, Flat File Import) from the hierarchy creates an import of the selected type. Selecting a saved import, under an import type, retrieves the settings for the import and enables the user to edit and run the import.
Table 23
Import Wizard Controls Description Save the import to its current name or a new name Delete a saved import Move backward or forward through the import wizard Run the import wizard Close the wizard without saving or running imports
Control Save and Save As Delete Back and Next Run Cancel
Naming Import Versions

To name the import version:
1 For Abbrev, enter a name.
Naming Import Versions
71
Figure 19
Import Wizard: Version and Output Options
2 For Description, enter a description. 3 For Log Output File Name, enter a path and file name for logging error and status messages. 4 Optional: In Max Errors, enter an integer value for the maximum number of errors permitted before the
import process is stopped.
The default value is 20. If a value of zero is entered, the import engine runs to completion regardless of the number of errors encountered. In the event of an unrecoverable error, the import stops processing.
5 Click Next.
Configuring Section and Processing Options

To configure section and processing options:
1 Under Sections, select each section to import.
If a section is not selected, it is not imported, even if it is displayed in the input source.
72
Running Imports
Figure 20
Import WizardSection and Processing Options
2 Optional: Under Skip Blank Values for these Properties, select a property type to skip blank, source-file
values in for the selected property types.
3 Optional: Under Skip Default Values for, select a property type to skip source-file values that equal the
default value for the selected property.
4 Optional: Select Determine Leaf Nodes At End of Import Process to specify that, at the end of the import
process, the import automatically sets the leaf property to True for any node that has no children.
If this option is not selected, the leaf property retains its system default value or any value explicitly included as part of the imported data.
5 Optional: Under Relationship Section Sorting, select Sort Relationships to enable the import to sort the
nodes based on the order in which they are displayed in the relationship section of the source file, and complete both of the following actions:

From Sort Property to Populate, select the node property in which to store the sort order For Hierarchy to be Sorted, enter the hierarchies to which to apply the sort
6 Click Next.
Configuring Section and Processing Options
73
Configuring Mappings
You configure columns on the Mappings page of the import wizard.
To configure mappings:
1 From Section on the Mappings page, select a section.
Figure 21 Import Wizard: Mappings
2 Optional: From Category, select a filter to limit the Available Properties list by type. 3 In Available Properties, double-click an item to add it to the Selected Properties list.
A special column called Ignore Column is available as a placeholder for any column in the input source that should not be processed during the import.
Note:
A column listed in bold is a required column and cannot be removed.
4 Use the up and down arrows to position the column in the Selected Properties list.
The first item in the list is the first column, the second item in the list is the second column, and so on.
74
Running Imports
5 Optional: To map a column to one or more hierarchies, click Hierarchy List.

This feature applies only to hierarchy-specific (or local) properties. To edit the hierarchy list:
In the list box, enter the name of each hierarchy to which the current column applies. The property value is set only in the hierarchies designated in the list. Optional: Select Assign to All if values in that column should be applied to all hierarchies. By default, Assign to All is set to true. Click OK to save the hierarchy list values or Cancel to exit without saving.
6 Click Next.
Specifying File Format Information

When you edit or create a flat file import, a modified Section and Processing Options page is displayed. The primary required entry on this page is the file name for the import file.
To specify file format information:

1 In the File Name text box, enter the file path and file name of the flat file to import.
You can click on the folder button to browse.
75
Figure 22
Import Wizard: Text File Format
2 Under File Format, select a file formats:
Fixed Width Click to display the Fixed Width Configuration dialog box.
a.
76
Running Imports
Figure 23
Fixed Width Configuration Dialog Box
b. c. d.
From Section, select a file section. From Columns, select a column. In Column Width, enter the width for the selected column. Each column name in the list identifies the number of spaces that the column occupies in the input text file.
e. f. g. h.
Repeat steps b, c, and d until you have set the width for each column in each section. Click OK.
Delimited
From the drop-down list, select a delimiter (comma, tab, or other). If you select Other, enter the delimiter character.
3 Optional: Select Strip Quoted Strings to remove quotation marks during data import.
Note:
The string must be enclosed in single quotation marks ( ' ) to be removed. If the string is enclosed in double quotation marks ( ) the quotation marks are not removed.
Selecting this option removes primary quotation marks and converts quotation marks embedded within quotation marks to primary quotation marks before importing the value. For example: 'Mr. Harris's Necktie' is imported as: Mr. Harris's Necktie.
4 Under Section Headings, enter the delimiter prefix.
77
The delimiter prefix is a character that is displayed at the beginning of a section heading, such as /, /**, or [. The delimiter suffix is optional.
5 Enter a heading for each section.

Each section has its own heading text, which, when combined with the delimiter, forms the heading. An example of each heading is displayed on the right. For example: Version Name[version]
6 Click Next.
Configuring Duplicate Handling

The Duplicate Handling page enables the parameters that affect how the import processor handles duplicate nodes. Duplicate is defined as a node that is displayed under multiple parents within the same hierarchy. If a duplicate is identified during the import, the name of the duplicate is replaced with a newly-created unique node name, which is defined according to the guidelines set on the Duplicate Handling page. As you edit the settings for handling duplicates, an example of the resulting value is displayed. Duplicate nodes can be queried to resolve underlying data issues.
To set up duplicate handling:

1 Optional: For Unique String, enter a string.
The string is used to form part of the new unique node name.
78
Running Imports
Figure 24
Import Wizard: Duplicate Handling
2 For Delimiter, enter a character.

The character is used to separate the original node name from the unique portion of the name.
3 For Unique ID Seed, specify a starting point for this ID.

For example, if NodeA occurs three times in a hierarchy and the unique ID seed is 1, the original node is not changed, and the other node names are replaced with NodeA1 and NodeA2. This example ignores the other Duplicate settings in order to illustrate the use of unique ID seed.
4 For Zero-pad Length, enter the minimum number of digits required in the unique ID portion of the duplicate
name.
For example, a value of 3 for zero-pad length produces duplicate nodes named NodeA001, NodeA002, and so on.
5 Optional: Select Append unique text to the end of the Node Abbrev to append the unique portion of the
name to the end of the original node name.
If this option is selected, the unique portion of the name is added to the end of the original node name. If this option is not selected, the unique portion of the name is prefixed to the beginning. For example, 001NodeA, 002NodeA.
Configuring Duplicate Handling
79
6 From Associated Property, select a property to enable duplicate nodes to be grouped so they can be easily
queried after the import is complete.
If an associated property is set, the property is populated with the node name of the original node in all duplicate nodes, and is a global, associated node property.
7 From Duplicate Error Mode, select a mode to determine the severity with which the import processor treats
a duplicate:

Generate Warning A warning message is added to the log for each duplicate. Generate Error The processor adds an error message is added to the log.
Note:
Processing stops if the number of errors exceeds the Max Errors value.
8 Click Run.
Viewing Import Results

After an import is complete, the Import Results dialog box is displayed. This dialog box displays statistical information about the import and a detail of each message generated during the import process. If a log output file name was designated during definition of the import, the information in the Import Results dialog box is contained in the output file. Data is imported to a newly-created version in a detached state. Thus, the data is not yet permanently saved. After the imported data is verified, it can be saved by right-clicking the version in the Version control window.
80
Running Imports
Figure 25
Import Results
Viewing Import Results
81
82
Running Imports
5
In This Chapter
Using Automator
Performing Automator Imports....................................................................................................83 Automator File Format .............................................................................................................86 Supported Automator Actions ....................................................................................................87 Required Automator Parameters .................................................................................................89
Performing Automator Imports

Automator is designed to enable Data Relationship Management users to make bulk hierarchy changes that are defined in a flat file format. The functions supported are typical node and property manipulations. When Automator is used, the changes defined as rows in the flat file can be performed automatically. The Automator functions by reading rows from the specified flat file. Each flat file row defines an action to be taken to modify Data Relationship Management hierarchies. Each row is read and the appropriate actions are performed sequentially. If any errors are encountered, a status message is displayed in the Automator window.
Caution!
When using the Automator, the regional settings of the server must be used to format date and time information. For example, if the regional setting for the server specifies that date should be formatted as dd.mm.yyyy, then the data given to the Automator should be in that format. The Automator does not do any date/time conversions from one format to another so if the information is not in the correct format then it will not display correctly or at all.
The following steps must be followed to perform an Automator batch process:

1 Create a flat file containing the actions to be performed. Detailed definitions of the flat file format are listed
below.
2 Run the Automator from within Data Relationship Management. 3 Check for the failure of any specified actions and the associated error messages.
83
Running Automator
To access Automator from Data Relationship Management:
1 From the Data Relationship Management main menu, select File, then Automator.
2 Under Script File, enter the name and path for the file and configure any file options as necessary.
Click and select a flat file containing the actions to be taken.
3 Click Load to load the flat file contents into the window.
It may take a few seconds to parse and load the flat file. The actions defined in the flat file are now listed in the Automator Window. If any of the actions defined in the flat file do not have the appropriate number of parameters, an error message is displayed in the Return Value column of the window, and any action names that are not recognized by the Automator are ignored, and are not listed.
84
Using Automator
Figure 26
Loaded Automator Window
The list of actions (and their associated parameters) defined in the flat file may now be reviewed. If necessary, the check box adjacent to each Action Name on the list of actions may be clicked to exclude or include defined actions. The Select All, Check, Uncheck and Toggle buttons may be used to define the actions that are included or ignored when the automator list is processed.
4 If necessary, click Versions to map a version name to another existing version.

In the Automator Version Substitution dialog box, the Original list displays versions in the Automator file. The Substitute list displays versions in the system.
Note:
You can type the version name into the Substitute text box.
85
Figure 27
Automator Version Substitution Dialog Box
5 Click the Process button to perform the automator process. The process is performed immediately. 6 Actions are implemented by Data Relationship Management in the order in which they are defined on the
list in the Automator Window.
The status of each action (e.g. Unprocessed, Failure or Success) can be monitored in the Status column, and the progress of large processing lists are displayed in a progress bar.
7 The results of any actions having a returned value are displayed in the Return Value column.
Reviewing Automator Processing Errors

When the processing of the automator is complete, the Automator Window may be reviewed for any errors. The Status column displays Failure for any errors, and a relevant error message is listed in the Return Value column.
If required, the Status and Return Value columns can be added to the original flat file (they become columns G and H of the file) by clicking on the Save button. Alternatively, a new flat file can be created (including these columns) by clicking Save As. In this case, you are prompted to define an appropriate file name. The resulting flat file can be examined and changes can be made to the rows that resulted in error messages. The flat file can then be resubmitted to the Automator for processing of the corrected rows.
Automator File Format

The Data Relationship Management Automator processes data from a flat file whose format can be specified by clicking the Options... button to display the Automator Flat File Script dialog box.
86
Using Automator
Figure 28
Automator Flat File Script
In the Column Order field, the order in which the 6 required columns appear in the flat file can be modified. The type of column Delimiter (comma, tab, or other) can be set. The option to Strip Quoted Strings can also be enabled. Clicking the Defaults button resets all options to the default setting. Clicking OK saves the desired options and closes the dialog box. The data in the flat file must follow a simple, but precise, format.
The first column of the flat file (column A) must contain the name of the Automator action that is to be performed. If this column does not contain a recognized action, then the row is ignored and not loaded. Note that a Remark action is available to allow comments to be added to the flat file. The remaining columns of the flat file contain a list of parameters that define each action. Typically, for most Automator actions, the first three columns of parameters (columns B, C and D) contain the names of the Data Relationship Management version, hierarchy and node upon which the action is to be performed. Columns E and F show other parameters relevant to each action. Columns G and H of the flat file can be populated by Data Relationship Management with the status and any comments resulting from the performance of the specified actions, if the appropriate command is selected in the Automator Window. In such cases, column G reports Success or Failure, and column H reports the reasons for any failures. Your Data Relationship Management system administrator should have an example Automator flat file template that can be examined and copied to clarify the required format. If necessary, this template can be requested directly from your Oracle representative.
Supported Automator Actions

The Automator supports the actions in the following table.
Supported Automator Actions
87
Table 24
Automator Actions Purpose Indicates a remark/comment row in the flat file (Any arbitrary text can be entered on other columns of this row for documentation purposesit is ignored by the Automator process) Adds the specified node to the specified hierarchy (This action can only be used for a node that does not already exist within the specified version) Inserts the specified node into the specified hierarchy (This action can only be used for nodes that already exist in another hierarchy within the specified version) Adds the specified node if it does not already exist in the specified version, otherwise the node is inserted Deletes the specified node from the version, and merges it with the merge node if one is specified Destroys the specified node from the version Activates the specified node in the hierarchy Inactivates the specified node in the hierarchy, and merges it with the merge node if one is specified Removes the specified node from the hierarchy Moves the specified node within the hierarchy Annuls the specified node Annuls all nodes following the specified node Updates the value of the specified property of the specified node Removes (clears) the value of the specified property of the specified node (The property itself is not deleted because many other nodes may be utilizing this property) Removes (clears) duplicate properties for the specified node (Corresponds to the Remove Duplicates command that is available to users within Data Relationship Management) Clears the values of the specified property in all of specified nodes children (Corresponds to the Clear All Below command that is available to users within Data Relationship Management) Locks or unlocks the specified property of the specified node Returns the value of the specified property of the specified node in the Automator result set Returns True if the value of the specified property of the specified node is equal to the value listed in the flat file, otherwise returns False Returns True if the specified node exists in the specified version, otherwise returns False
Action Rem
Add
Insert
AddInsert
Delete
Destroy Activate Inactivate
Remove Move Annul AnnulAllBelow ChangeProp RemoveProp
RemoveDupProps
ClearPropsBelow
LockProp PropQuery
PropCompare
NodeExists
88
Using Automator
Action NodeExistsInHier
Purpose Returns True if the specified node exists in the specified hierarchy, otherwise returns False Returns True if the specified parent node is the parent of the specified node, otherwise returns False Updates the value of a version property Removes (clears) the value of a version property Assigns validations/verifications at the version level Adds an orphan node to a version Adds a hierarchy to a version Deletes a hierarchy from a version Changes the top node for a specified hierarchy Updates the value of a hierarchy property Removes (clears) the value of a hierarchy property Assigns validations/verifications at the hierarchy level Deletes an orphan node
NodeHasAsParent
UpdateVersion PropValue RemoveVersion PropValue AssignVersion Validations AddOrphan AddHier DeleteHier ChangeHierTopNode UpdateHier PropValue RemoveHier PropValue AssignHier Validations DeleteOrphan
Required Automator Parameters

The parameters required by each action in each flat file column are as follows:
Table 25
Automator Parameters Column B Remark Version Column C Remark Hierarchy Column D Remark Node Column E Remark Parent node Column F Remark Is a leaf (0=false, 1=true)
Column A Rem Add
Insert AddInsert
Version Version
Hierarchy Hierarchy
Node Node
Parent node Parent node Is a leaf (0=false, 1=true)
Delete Destroy Activate
Version Version Version
Hierarchy Hierarchy Hierarchy
Node Node Node
(Merge node)
89
Column A Inactivate Remove Move
Column B Version Version Version
Column C Hierarchy Hierarchy Hierarchy
Column D Node Node Node
Column E (Merge node)
Column F
Destination parent node
Annul AnnulAllBelow ChangeProp RemoveProp RemoveDupProps ClearPropsBelow LockProp
Version Version Version Version Version Version Version
Hierarchy Hierarchy Hierarchy Hierarchy Hierarchy Hierarchy Hierarchy
Node Node Node Node Node Node Node Property label Property label Property label Property label Property label Is Locked (0=false, 1=true) Value
PropQuery PropCompare NodeExists NodeExistsInHier NodeHasAsParent UpdateVersion PropValue RemoveVersion PropValue AssignVersion Validations AddOrphan
Version Version Version Version Version Version
Hierarchy Hierarchy Node Hierarchy Hierarchy Property label
Node Node
Property label Property label Value
Node Node Value Parent node
Version
Property label
Version
Validation
Version
Node
Is a leaf (0=false, 1=true) Description Top Node
AddHier DeleteHier ChangeHierTop Node UpdateHier PropValue RemoveHier PropValue AssignHier Validations
Version Version Version Version Version Version
Hierarchy Hierarchy Hierarchy Hierarchy Hierarchy Hierarchy
New Top Node Property label Property label Validation Value
90
Using Automator
Column A Delete Orphan
Column B Version
Column C Node
Column D
Column E
Column F
91
92
Using Automator
6
In This Chapter
Using Blender
Blender Elements ..................................................................................................................93 Using the Blender Wizard .........................................................................................................94 Configuring Blender Versions and Hierarchies ..................................................................................95 Configuring Top Nodes ............................................................................................................98 Viewing Blender Results ......................................................................................................... 102
Blender enables various elements of two versions to be combined, or blended, together. The elements to be blended can include various combinations of structural elements, such as hierarchies and nodes, and properties. Blender provides these options:

To process any combination of adds, moves, or deletes To act upon any combination of hierarchies To map top nodes from a source hierarchy to nodes in a target hierarchy
Blenders can be customized and saved by System Administrators or Functional Administrators.
Blender Elements
A blender consists of the elements described in the following table.
Table 26
Blender Structure Description These are attributes of the Blender itself, such as what versions are being blended, default values, etc. These are the two versions being blended. Blending can occur from the source directly into the target, or into a third new version that is created during the blend process. Also called hierarchy/top-node pairs. These are mappings from the source to the target indicating which hierarchy top nodes in the target are to receive values from the source. Top nodes in the target can either be created on the fly, or mapped directly to existing top nodes, depending on the Blender settings. Lists of properties to be blended. Properties can be blended in one of three ways:
Blender Element Blender
Source/Target Version
Hierarchy Sets
Property Sets
Blender Elements
93
Blender Element
Description

All None Selected
If Selected is chosen, then the selected property set determines which properties are blended.
Using the Blender Wizard

You use the blender wizard to run blenders. The wizard enables you to set the source and target version, set options for hierarchy-level blending behavior, copy blended values to a new version, and so on. Table 27 describes the controls in the Blender wizard.
Table 27
Blender Wizard Controls Description Allow the blender to be saved under its current name, or a new name Delete a previously saved blender Move forwards and backwards through the import blender dialog box Close the dialog box without saving or running any blender
Blender Wizard Controls Save and Save As Delete Back and Next Cancel
To run a blender:
1 From the Data Relationship Management main menu, select File, then Blender.
Figure 29 Blender Dialog BoxChoose Blender
94
Using Blender
2 Select a new or saved a blender.

Selecting [New Blender] from the tree view creates a blender. Selecting a previously saved blender retrieves the settings for that blender and enables you to edit and run the blender.
3 Click Next.
Configuring Blender Versions and Hierarchies

To set the version and hierarchy for a blender:
1 In Source, select the source version.
Figure 30 Blender Dialog Box - Version/Hierarchy Settings
2 In Target, select the target version. 3 Optional: Select Copy to New Version to specify that the blended values be stored in a new version rather
than in the target version.
95
If blending to a new version, an Abbrev is required to name the version. A description for the new version is optional.
4 Selecting Apply to All Hierarchies applies the default settings to all hierarchy/top-node pairs; otherwise
the same settings can be made for each pair.
Default values for hierarchy/top-node settings are required.
5 From the Property Select Options drop-down list, select one of the following ways to blend properties:
All Excl Val/Ver/Access all properties are blended; excludes properties used for nodelevel validation and verification assignments and for node access group leaf and limb-level settings. None no properties are blended Selected the selected properties are blended To select properties, click .
a.
Figure 31
Select Properties Dialog Box
b. c.
Select properties to be included in the blend process. Optional: From the Propagate Mode drop-down list, select one of the following modes to determine how the property is populated in the target:
Force - the property is assigned for every node in the target, whether that property is defined at that node, or is inherited, read/write inherited, and so on. Difference - populates the property for any node where the value is different, regardless of how that property is populated in the target. Defined - the property is blended only when it is specifically defined for the node in the source.
96
Using Blender
d. e.
Select Propagate Property Locks if you want locks in the source to be blended to the target. Click OK.
6 Select from the following options:
Allow Hierarchy Creation to create hierarchies in the target version that exists only in the source version
Note:
If this option is not selected and there are hierarchies that exist in the source but not in the target, then an error occurs.
Allow Leaf Promotion to promote a node in the source that contains children to a limb in the target
Note:
If a node in the source has children, but its corresponding node in the target is a leaf node (an outermost node with no children allowed), then this option enables the Blender to promote the node to limb status. The child nodes from the source are then added to the limb node in the target.
Process Activations to process node activations (inactivate and reactivate) from the target to the source Process Hier Val/Ver Assignment to process the hierarchy level validation and verification assignments from the target to the source Process Moves to move any node which has a different parent in the source to that parent in the target Process Adds to add any nodes existing only in the source to the target Process Removes to remove any nodes existing only in the target according to the setting in the Remove Mode drop-down list and the Remove Indicator drop-down list. If you selected Process Removes, select one of the following Remove Modes:

Remove - node is immediately removed during blending Mark - node is marked for later removal When the Remove Mode is set to Mark, the Remove Indicator field designates which property contains the value showing that the node is flagged to be removed. The remove indicator property must be created as a local, Boolean property. For information on creating properties, see the Oracle Hyperion Data Relationship Management N-tier Administrator's Guide.
7 Click Next.
97
Configuring Top Nodes

From the Hierarchy/Top-Node Settings page of the blender wizard, you can edit settings that are specific to each set of hierarchy/top-node pairs.
To configure top nodes:

1 Optional: Select Blend All Hierarchies to blend all hierarchies using the defaults from the Blender.
If you select the Blend All Hierarchies option, no other options on this tab are enabled.
Figure 32
Blender Dialog BoxHierarchy/Top-Node Settings
2 Select a top-node pair and click one of the following options:

New - to add a new hierarchy set Edit - to edit a hierarchy set Delete - to delete the selected hierarchy set.
3 Click the arrow buttons next to the hierarchy/top-node list to change the position of a hierarchy set within
the list.
98
Using Blender
This controls the order in which sets are processed.
4 Optional: Select Hierarchy/Top Node Settings.
Select Use Blender Defaults if you selected Apply to all Hierarchies on the previous page, and default values from the Version/Hierarchy Settings page are used and the corresponding options in this section are not enabled. Skip step 5. If you deselect Use Blender Defaults, you will need to perform step 5.
5 From the Property Select Options drop-down list, select one of the following ways to blend properties:
All Excl Val/Ver/Access all properties are blended; excludes properties used for nodelevel validation and verification assignments and for node access group leaf and limb-level settings. None no properties are blended Selected the selected properties are blended To select properties, click [...] next to the Property Select Options drop-down list. Select properties to be included in the blend process. Optional: From the Propagate Mode drop-down list, select one of the following modes to determine how the property is populated in the target:
a. b. c.
Force - the property is assigned for every node in the target, whether that property is defined at that node, or is inherited, read/write inherited, and so on. Difference - populates the property for any node where the value is different, regardless of how that property is populated in the target. Defined - the property is blended only when it is specifically defined for the node in the source.
d. e.
Select Propagate Property Locks if you want locks in the source to be blended to the target. Click OK.
6 Optional: Select one or all of the following options:
Process Activations to process node activations (inactivate and reactivate) from the target to the source Process Hier Val/Ver Assignment to process the hierarchy level validation and verification assignments from the target to the source Process Moves causes any node which has a different parent in the source to be moved to that parent in the target. Process Adds causes any nodes existing only in the source to be added to the target. Process Removes causes any nodes existing only in the target to be removed according to the setting in the Remove Mode drop-down list and the Remove Indicator drop-down list. If you selected Process Removes, select one of the following Remove Modes:

Remove - the node is immediately removed during blending. Mark - the node is marked for later removal at the users discretion.
Configuring Top Nodes
99
When the Remove Mode is set to Mark, the Remove Indicator field designates which property contains the value showing that the node is flagged to be removed. The remove indicator property must be created as a local, Boolean property. For information on creating properties, see the Oracle Hyperion Data Relationship Management N-tier Administrator's Guide.
7 If opened from the Hierarchy/Top Node Settings page, the Blender Hierarchy Set dialog box enables the
matching of Hierarchy Sets from the Source to the Target Version.
Figure 33
Blender Hierarchy Set Dialog Box
8 Use
next to the Source Top Node box to browse through the Source version and to select a hierarchy and Top Node.
9 Select a Target option:
If the Target Use Same as Source option is checked, then the target node editors and buttons are disabled and the blender uses the same node in both the Source and Target. Otherwise, click to browse through the target version and select a hierarchy and top node. If the Allow Hierarchy Creation option for the blender is true, then the Target text boxes are enabled and can be used to enter new values for hierarchy and top node.
10 The Blender Options page shows general processing options for the blender.
100 Using Blender
Figure 34
Blender Dialog Box - Blender Options
11 Under Max Iterations, enter a number.

The Max Iterations value determines the maximum number of attempts the Blender performs in reconciling the Source and Target versions. This prevents the Blender from running indefinitely in the case of irresolvable conflicts. The recommended value is 3.
12 Under Max Errors, enter a number.

The Max Errors value sets the maximum number of errors that can occur during processing before the Blender aborts.
13 Select a Propagate Mode.

The default Propagate Mode determines how each property is populated in the Target. The possible values are Force, Difference and Defined.
In Force mode, the property is assigned for every node in the Target, whether that property is defined at that node, or is inherited, read/write inherited, etc. Difference mode populates the property for any node where the value is different, again regardless of how that property is populated in the Target.
Configuring Top Nodes 101
In Defined mode, the property is blended only when it is specifically defined for the node in the Source. The default option to Propagate Property locks determines whether locks in the Source are blended to the Target.
14 Select any of the following options:

Propagate Property Locks to blend property locks from the source to the target Disable Real-Time Validations to turn off the real-time validations on the target version prior to performing the blend operation Process Version Level Val/Ver Assignments to process version-level validation and verification assignments from the target to the source
15 Click [...] to select a file in which to store the output log for the Blender. 16 Select any of these options:

Clear Values to set all Blender Status Property values to False during processing. Populate Values to set each Blender Status Property to True during processing. Select specific Blender Status Property option from the drop-down lists.
Version Blended Property The name of the property that will be set to TRUE if the version has been blended {Version Level Boolean Defined Property} Hierarchy Blended Property The name of the property that will be set to TRUE if the hierarchy has been blended {Hierarchy Level Boolean Defined Property} Node Created Property The name of the property that will be set to TRUE if the node was created by the blend {Global Node Level Boolean Defined Property} Node Inserted Property The name of the property that will be set to TRUE if the node was inserted by the blend {Local Node Level Boolean Defined Property} Node Moved Property The name of the property that will be set to TRUE if the node was moved by the blend {Local Node Level Boolean Defined Property} Global Node Changed Property The name of the property that will be set to TRUE if the node had global properties changed by the blend {Global Node Level Boolean Defined Property} Local Node Changed Property The name of the property that will be set to TRUE if the node had local properties changed by the blend {Local Node Level Boolean Defined Property} Leaf Promoted Property The name of the property that will be set to TRUE if the node was promoted from a leaf to a limb by the blend {Global Node Level Boolean Defined Property}
17 After all settings have been configured, click Run to process the blender.
Viewing Blender Results

After a blender is complete, the Blender Results dialog box is displayed.
102 Using Blender
Figure 35
Blender Results
This dialog box displays an error count and status and a list of each message generated during the Blender process. If the Copy to New Version option was selected, then the newly-created version that contains the blended data is in a Detached state. This means that the data has not yet been permanently saved. After the blended data is verified, it can be saved by right-clicking on the version in the Version Control Window.
Viewing Blender Results 103
104 Using Blender
7
In This Chapter
Running Exports
Export Classes.................................................................................................................... 105 Starting the Export Wizard....................................................................................................... 106 Using Export Books .............................................................................................................. 133
Customized export types may be available for certain clients, for example, XYZ Corporation Essbase Account Export. Such exports may use standard Export/Report dialog box pages and have additional customized dialog box pages, documented separately. Please contact your Oracle representative for details about customized export types for your organization.
Export Classes
Data Relationship Management has many different export classes that can be used in exporting the data in different formats to external systems. Some of these classes are for general use while others are for very specific purposes. The exports are flexible in allowing the user to specify the content, filtering, formatting and output location. Understanding the classes will assist in determining the correct way to get the data out of Data Relationship Management. The following table lists the main export classes for Data Relationship Management.
Note:
Some clients may have more classes since they have custom export classes for their specific implementation.
Class Ancestor Export Generation Export
Description Deprecated - functionality is replaced by the Generation Export class Create a generation-based or level-based export. In addition, it has the ability to balance the hierarchy by different mechanisms. Can be used to send hierarchies out to an external system in a generational or level-based format. Produces comparison results between two hierarchies. They can be the same hierarchy in different versions giving a what has changed type of export. They can be different hierarchies in the same version giving a
Usage Frequency Low - Deprecated Medium
Database Export No No
Compare Export
Medium
Yes
Export Classes 105
Class
Description hierarchy content comparison. This kind of export can be used to send changes only to an external system.
Usage Frequency
Database Export
Difference Report
Produces reports showing differences. The main difference between this and the Compare Export is that its format is in a more readable form rather than the column-based Compare Export. This is the main export class for Data Relationship Management. This export goes through the nodes in the specified hierarchies and exports a record for each node. This is the export to use to create a parent-child type of export for external systems as well as a basic node list type of export. This export is a special use case and it only provides the export of a lookup set for a specified lookup property. This export is used to retrieve the Merge node data that is collected when Merge is used on a Delete or Inactivate. This export is a special use case and it only provides the export of a list for a specified list property. Exports the transaction history information. The version export is similar to the Hierarchy export with the exceptions that it goes through all nodes in the version and cannot retrieve local or hierarchy level property information.
Low
No
Hierarchy Export
High
Yes
Lookup Export
Low
No
Merge Export
Low
No
Property List Export
Low
No
Trans Log Export Version Export
Medium Medium
Yes Yes
Starting the Export Wizard

To run an export:
1 From the Data Relationship Management main menu, select File, then Export/Report.
The Exports dialog box opens and displays the Select Export/Book page. This page is the starting point for all export types.
106 Running Exports
Figure 36
Select Export/Book Page
2 Select the Current Version to be used for the export. For comparison exports, a Previous Version must also
be selected.
Click
to open the Version Criteria dialog box if a Baseline or As of Version is desired.
3 Choose the desired export type.

To create a new export, select the desired type from the tree and click the Next button. To run or edit an existing export, drill down the tree view under the appropriate export type and select the desired export, then click Next. Note that standard exports created by an administrator and available to all users are prefixed with "std:" and displayed in bold. Depending upon the type of export being performed, the Export/Report dialog box presents a varying series of dialog box requesting further criteria for the export. Each dialog box is described in the sections that follow.
Top Nodes Page

The Top Nodes page is used in hierarchy exports to select the top nodes of the hierarchies to be exported.
Starting the Export Wizard 107
Click Add to display the Select Node menu from which a top node may be selected. Select as many top nodes as required. When multiple nodes are added to the list, the data will be exported in the order that the nodes appear. The arrow keys on the right can be used to reorder the current node list. Use Delete to remove a node from the list. For comparison exports, the top node for both the current and previous version must be selected Check the Include Inactive Nodes check box if inactive nodes are to be included in the export.
Figure 37
Export/Report Dialog BoxTop Nodes For Non-Comparative Exports
In the Descendants section, a text file may be defined to list nodes to be included or excluded from the export. To use this feature, check the Use text file to include/exclude descendant Nodes check box and supply the appropriate file name. Select the appropriate option to determine if the text file contains nodes to be included or excluded. The format of the text file is just a listing of nodes with one node per line. For comparison exports, an alternate Join property can be selected if desired. By default, the compare operation maps nodes from each hierarchy that have the same name. It is also possible to join nodes based on other properties. For example, if a property named SortCode was a unique key in the specified hierarchies, then this property is used in the Compare to identify differences/ similarities between nodes having the same SortCode in each hierarchy.
108 Running Exports
Figure 38
ExportHierarchy Compare Export Dialog BoxTop Nodes Page
Select Columns Page

This page is used by nearly all export types to define the columns of data to be included in the export. For most export types, the columns represent property values.
Click the arrow buttons in the center of the dialog box to move values from the Available list to the Selected list. If necessary, use the Category drop down list to make navigation of the Available list easier by restricting it to a single Property Category. Use the up and down buttons to the right of the Selected list to change the display order of the selected columns
Figure 39
Exports Dialog BoxSelect Columns Page
For some export types there are additional options available. For the Generation Hierarchy Export, the Column Set list is displayed to allow selecting columns as:

Pre Columns: properties to export at the beginning of each row Bottom Node Columns: properties for the specified bottom node Ancestor Columns: node properties for the ancestor list of the specified bottom node Post Columns: properties to export at the end of each row
The specialty columns [Node Sequence #] and [Ancestor Sequence #] are also available to number each row in the export. For the Hierarchy Compare Export, properties are duplicated in the Available list and suffixed with [From] or [To] to designate the source hierarchy of each property. The following specialty columns are also available in the list:
[Action Type Code] - exports the type of action (Addition, Merge, Deletion, etc.) for each difference found [Merged Node] - the name of the merge node used during deletion
110 Running Exports
[Property Label] - the name of the property updated [Property Value] - the updated value of the property
For Lookup Export, there are only two columns available because the Lookup Value and the Result Value are the only things being exported.
Figure 40
ExportsLookup Export Dialog BoxSelect Columns Page
For Merge Log Export, the available columns represent information on the merge operations performed.
Figure 41
ExportsMerge Log Export Dialog BoxSelect Columns Page
For the Transaction Log Export, the available columns relate to Transaction History activity.
Figure 42
ExportTrans Log Export Dialog BoxSelect Columns Page
Column Options Page

This page is used by hierarchy export types to configure options for each column in the export.
Check the Skip Defaults check box to place a blank in the export if the field value is equal to the default value. Check the Pivot check box if the field contains a comma delimited value. Then, for each value in the list for that column, a row is exported with all other fields set to the same values. The Pivot option may be selected on just a single column. Check the Primary Key check box to define a field (or fields) as the primary key to be used when determining if duplicates exist. This is also used by the Remove Duplicates option of the Parameters pages.
112 Running Exports
Figure 43
ExportsGeneration Hierarchy Export Dialog BoxColumn Options Page
Column Widths Page

This page appears when fixed width columns are specified for the output. For each column, the following can be configured:

Numerical value for column width - cannot be set to zero Justification Left or Right Pad Character to pad unused character positions. Default is a space.
Figure 44
Hierarchy Export Dialog BoxColumn Widths Page
Parameter Pages
Parameter pages capture the required additional parameters that are unique to each export type. There are many similarities and some subtle differences between these pages.
Generation Export Parameters Page

The Generation Export Parameters page is used to select the appropriate options that define how a Generation Hierarchy Export is generated.
Figure 45
ExportsGeneration Export Dialog BoxParameters Page
The Node Selection Options define whether all nodes are included in the export, or just those that are limbs or leaves. Select Recurse from Top Nodes if the export should include a row for all nodes below the top node selected. If not selected, then only the selected top node is included in the export (which is typically not the desired result.) Select Include Implicitly Shared Nodes to include descendant nodes below shared limb nodes that have been explicitly shared. Implicit shared nodes are only exported if not filtered out by another option such as top node selection or a property query filter. The structure of implicitly shared nodes below a shared parent node is reflected in the ancestor section of the generation export.
If the Limb Nodes Only or Leaf Nodes Only option is used, the Shared Node is included even if it does not match the selected option (leaf or limb). This is done since the
114 Running Exports
implicitly shared node is substituted for the explicitly shared nodes and they are processed against the node selection options.
If a query filter is used in the export, the administrator must explicitly include the shared nodes for this option to work. For example, the filter (#Children=0) would need to be changed to ((#Children=0 OR (Shared Node Flag = True)). For the implicitly shared node, the Parent properties will reflect the values of the actual node, i.e. the primary node. For example, if your export includes the Parent Property for an implicitly shared node, then it will show the parent as the primary node and not the shared node.
Select Root To Node to set the ordering of the export (if not selected, the order is Node to Root.) For example, if node A is a parent to node B and this option is selected, then the output is A,B. Otherwise, with this box unchecked, it is B,A.
The Repeat Level Options are typically used to generate exports for destination systems that require fixed-depth hierarchies (sometimes called a balanced tree.)
Figure 46
ExportsInt Layer Product Gen Report Dialog BoxRepeat Parameters Page
Repeat Num Property defines a property that repeats a node within an export structure. For example, if node B within an A-B-C parent-child hierarchy has a Repeat Num Property with a value of 2, then the export looks like A,B,B,C (node B is repeated twice.) The Bottom Level Property and the Bottom Level Value determine the maximum depth of the export structure. This value can defined as a hierarchy-level property (Bottom Level Property) or as an absolute value (Bottom Level Value.) If a bottom level is defined, the repeat options are enabled to automatically repeat nodes down to the defined level in the export structure. For example, for nodes A-B-C in a parentStarting the Export Wizard 115
child hierarchy, if the Bottom Level Value is defined as 6, node B has a Repeat Num Property value of 2, and the Repeat Bottom Node option is selected, then the export structure is A,B,B,C,C,C (the export structure is six levels deep, the leaf node C is repeated until level 6 is reached, and node B is repeated twice).
The Max Ancestor Levels is used to define the absolute maximum number of ancestor levels in the export structure. If Use inverted level is selected, the Oracle Essbase level methodology is used where the leaves are at 0 and count up. For a node that has multiple branches under it, the node is the largest of the possible values. If Blank repeated levels is not selected, then a node may be repeated in the output to achieve the specified level. Checking this box will prevent the repeated nodes from appearing in the output. If Group repeated columns is selected repeated columns are grouped property in the ancestor columns.
Hierarchy Compare Export Parameters Page

The Hierarchy Compare Export Parameters page is used to select the appropriate options that define how a Hierarchy Compare Export is generated. This page is very similar to the Hierarchy Difference Report Parameters page.
Figure 47
ExportsHierarchy Compare Export Dialog BoxParameters Page
116 Running Exports
The Type Codes define the text that is included in the export columns to identify the results of the compare for each type of result. These codes can be selected as output columns on the Columns page of the export. If checked, Additions includes all nodes in the target (to) hierarchy that are not in the source (from) hierarchy. Conversely, if checked, Deletions includes all nodes in the source (from) hierarchy that are not in the target (to) hierarchy. If checked, Merge includes merge information in the export (if the merge feature is enabled.) If checked, Moves includes all nodes that have different parent nodes in the two hierarchies being compared. If checked, Renames includes all nodes that have different names (the Abbrev property) but the same internal NodeID in the two hierarchies being compared. If checked, Property Updates includes all nodes that have different values in the specified list of properties in the two hierarchies being compared. Use the Add and Remove buttons to add properties to the list of properties to be used. Clicking Edit opens the Select Properties dialog box in which one or more properties may be selected.
Figure 48
Select Properties Dialog Box
Hierarchy Difference Report Parameters Page

The Hierarchy Difference Report Parameters page is used to select the appropriate options that define how a Hierarchy Difference Report is generated.
Figure 49
Export/ReportTest Diff Exp Dialog Box
The functionality of the check boxes on this page is the same as on the Hierarchy Compare Export Parameters page described preceding. The Fixed Width Columns fields are used to define the column width of the Name and Parent Node name in the export. A fixed width cannot be set to zero.
Hierarchy Export Parameters Page

The Hierarchy Export Parameters page is used to select the appropriate options that define how a Hierarchy Export is generated.
118 Running Exports
Figure 50
ExportsHierarchy Export Dialog BoxParameters Page
The Node Selection Options define whether all nodes are included in the export, or just those that are limbs or leaves. Select Recurse from Top Nodes if the export should include a row for all nodes below the top node selected. If not selected, then only the selected top node is included in the export (which is typically not the desired result.) Select Remove Duplicates Based on Keys if the primary key defined on the Column Options page should be used to suppress the export of duplicates. Select Include Implicitly Shared Nodes to include descendant nodes below shared limb nodes that have been explicitly shared. Implicit shared nodes are only exported if not filtered out by another option such as top node selection or a property query filter. The structure of implicitly shared nodes below a shared parent node is reflected in the ancestor section of the hierarchy export.
If the Limb Nodes Only or Leaf Nodes Only option is used, the Shared Node is included even if it does not match the selected option (leaf or limb). This is done since the implicitly shared node is substituted for the explicitly shared nodes and they are processed against the node selection options.
If a query filter is used in the export, the administrator must explicitly include the shared nodes for this option to work. For example, the filter (#Children=0) would need to be changed to ((#Children=0 OR (Shared Node Flag = True)). For the implicitly shared node, the Parent properties will reflect the values of the actual node, i.e. the primary node. For example, if your export includes the Parent Property for an implicitly shared node, then it will show the parent as the primary node and not the shared node.
Select Tabbed Output to insert a tab character every level of the node (so that it resembles a hierarchy when imported into other applications, such as Microsoft Excel.)
Note:
Tabbed output is not available if Include Implicitly Shared Nodes is selected.
Lookup Export Parameters Page

The Lookup Export Parameters page is used to select the appropriate options that define how a Lookup Export is generated. This page is the same as the Property List Export Parameters page.
Figure 51
ExportsLookup Export Dialog BoxParameters Page
To define the lookup export:

1 From the Property drop down box, select a property upon which to base this export. 2 Select any or all of the following options:

Check the Column Headings check box to include column headings in the export. Check the Quoted Strings check box to enclose quotation marks around strings in the export.
120 Running Exports
Check the Fixed Width check box to allow the explicit specification of field widths and separators. Check the Differences Only to filter out lookup pairs where the source and target are the same.
3 Select a field delimiter for the export from the Delimiter drop down box.
Property List Export Parameters Page

The Property List Export Parameters page is used to select the appropriate options that define how a Property List Export is generated. It is the same as the Lookup Export Parameters page.
Merge Log Export Parameters Page

The Merge Log Export Parameters page is used to select the appropriate options that define how a Merge Log Export is generated.
Figure 52
ExportsMerge Log Export Dialog BoxParameters Page
Use Begin and End to select a date range for the merge log export. Clicking the down arrow at the right of these field opens a calendar that can assist in the selection of dates. The Filters fields allow filters for the export to be defined. Enter a Deleted Node to filter by a node name that has been deleted. Enter a Merge Node to filter by a merge node name. Use the Status to define if all nodes, or just deleted or inactivated nodes are to be included in the export.
Enter a User to filter by a user name.
Transaction Log Export Parameters Page

The Transaction Log Export Parameters page is used to select the appropriate options that define how a Transaction Log Export is generated.
Figure 53
ExportsTrans Log Export Dialog BoxParameters Page
Use From and To options to select a date range for the export. Clicking the down arrow at the right of these fields opens a calendar that can assist in the selection of dates. The From ID and To ID options allowing specification of a specified range of IDs. The Action fields can be used to filter the export to include just the specified action types from the transaction log. The Filters are used to filter the export. Most filters are a comma-delimited list of names (e.g. node names) that can be built by clicking the ellipses [...] buttons. The Node field is used to define a list of nodes that acts as a filter for the export. The User field is used to define a list of users that acts as a filter for the export.
122 Running Exports
The Property field is used to define a list of properties that acts as a filter for the export. Other options allow the export to Include Child Nodes, Filter to Current Session, and Run Export for All Versions.
Version Export Parameters Page

The Version Export Parameters page is used to select the appropriate options that define how a Version Export is generated.
The Node Selection Options define whether all nodes are included in the export, or just those that are limbs or leaves.
Figure 54
ExportsVersion Export Dialog BoxParameters Page
Ancestor Export Parameters Page

The Ancestor Export Parameters page is used to configure the following parameters:

Node Direction: determines how the ancestor list is ordered Reporting Style: enables listing ancestors by Name or by Description Include Description: option to include the Description of the bottom node
Figure 55
ExportsAncestor Export Dialog BoxParameters Page
Verification and Filter Page

This page is used to select a verification and define a filter for the export. Any available verification can be selected from the drop-down list to be applied to the export. To define a filter, click the Edit button to open the Property Query Editor. From the editor, a new query can be created or an existing one can be selected from the list. The defined filter query is then displayed in the Property Filter section. Clicking the Clear button, removes the filter query. For most export types, the filter is used to restrict the export output to only those nodes that meet the filter criteria. However, for Hierarchy Compare Exports, it is important to note that the filter determines the set of nodes from each hierarchy that will be compared. For example, when checking for node additions or deletions and a filter is not used, a node that exists in both hierarchies does not show up in the export result. However, if a filter is used and the node meets the filter criteria in one hierarchy but not in the other, that node appears as a difference (either an addition or deletion.)
124 Running Exports
Figure 56
Export/ReportHierarchy Export Dialog BoxVerification and Filter Page
Exclusion Filter Page

This page is used by some export types to define a filter that excludes nodes from the export. The process for creating and editing the filter criteria is similar to that used on the Verification/ Filter page. The exclusion filter is used in two different ways:
For the Generation Hierarchy Export, the filter is used to restrict the nodes that appear as Ancestor Columns. For the Hierarchy Compare Export, the filter is used to exclude nodes that exist in the comparison result from the export output.
Figure 57
ExportsInt Layer Product Gen Export Dialog BoxExclusion Filter Page
Output Formatting Page

This page is used by most export types to specify formatting options for the export results.
Figure 58
ExportsHierarchy Export Dialog BoxOutput Formatting Page
126 Running Exports
In the Format section, select one or more of the following options:

Column Headings - to include column headings in the export. Quoted Strings - to enclose quotation marks around strings in the export. Fixed Width - to allow the explicit specification of field widths and separators. If this option is selected, the next dialog box presented is the Column Widths page.
In the Delimiter section:

From the Field drop-down list, select a field delimiter character. From the Record drop-down list, select a record delimiter character.
In the Header/Footer section: The header and footer options are used to specify text to be printed on the header and footer of the export results. Multiple lines of text can be entered either directly into the text box or click to open the pop-up text editor. Customization tags can also be inserted to further enhance the readability of the export results. The tags use the format <%Tagname(parameters)%> and are replaced with the appropriate value at run time. In the list following, optional parameters are enclosed in [brackets]. The following table describes the customization tags that are available for use.
Table 28
Customization Tags Description Returns current date where format = MM/DD/YYYY Returns current time where format = HH:MM:SS AMPM Returns combination of date and time. Returns current Data Relationship Management user. Returns current Data Relationship Management version for this export. Returns previous Data Relationship Management version for this export. Returns name of export.

Customization Tag <%Date[(format)]%> <%Time[(format)]%> <%Timestamp%> <%CurrentUser%> <%CurrentVersion%>
<%PreviousVersion%>
<%ExportName%> <%FileName%>
Returns output file name if specified Returns default file name if not specified
<%RecordCount%>
Returns count of records exported (only available in footer) Returns the Data Relationship Management product number (for example, 4.6.0.1) Returned value depends on the specified export type as described following:
<%AppVersion%>
<%PropValue()%>
Customization Tag <%PropValue([Previous|Current(Default)], PropName)% > <%PropValue([HierName], PropName)%>
Description For Compare/Difference Exports, returns value of first node in CompareCriteria for Previous/Current version
For Hierarchy Exports, returns value from first node in list If HierName is supplied, return value from the first node that matches HierName
<%PropValue(PropName)%>
For Version Exports, returns only version properties
The Blank line between Header/Footer and Body check box may be used to improve the readability of headers and footers by adding white space. In the Replace section, select up to three characters from the lists on the right to be replaced by the characters selected from the lists on the left. All instances in the export output are replaced as specified. For example, all parentheses can be replaced by braces.
Output Destination Page

This is the final page in the dialog box sequence for all export types and determines the destination of the export output. Select one of the options and click Run to generate the export results:
File results are written to a file. Enter file path or click

Note:
to browse.
If only a file name is specified, the default directory specified in the Tools-Options menu is used to locate the file.

Preview results are displayed in a pop-up window. Table results are exported to a database table.
Export to Table Option

For certain export types, the output can be sent to an external database table. This feature currently supports both MS SQL and Oracle databases. Select the Table option and click the [...] button to open the Export to Table configuration dialog box.
128 Running Exports
Figure 59
Export to Table Options
On the Output Properties tab, configure the following items.

1 From the DAL list, select ADO 2 Define a Connection String for accessing the external database. Either enter an existing connection string
or click the [...] button to build one using the Data Link Properties dialog box. If the connection string is already known, enter it directly and then skip to step 8.
Figure 60
Data Link Properties - Provider Tab
3 On the Provider tab, select the appropriate ODBC driver for the type of external database being used. Then
click the Next button.
130 Running Exports
Figure 61
Data Link Properties - Connection Tab
4 On the Connection tab, specify the server name where the external database resides. 5 Select the desired type of security for accessing the database and enter the appropriate information. Note
that the connection string information, including passwords, is encrypted when saved to the Data Relationship Management database.
6 Select the name of the external database. The Test Connection button can be used to verify a connection
using the specified information.
7 Click OK to close the Data Link Properties dialog box.
Figure 62
Export to Table - Output Properties Tab
8 In the Table field, specify the desired table name in the external database. Note that the table must already
exist before the export can be run.
9 If the User ID and Password are not specified within the connection string, they can be entered in the
appropriate fields.
10 Selecting the Use Transactions option causes the export to be performed within a database transaction and
allows the entire operation to be rolled back if an error occurs during the export.
11 The Use Fast Appends option applies only when using a database-specific DAL. This option can be ignored
when using the ADO DAL.
12 In the Clear Table section, select the desired option:
Do not clear table causes the export to append to any data that already exists in the specified table. Delete based on Version ID(s) deletes any existing data in the table where the specified key field is equal to the current version ID of the data being exported. See additional details below on selecting a Key field. Delete all rows deletes all existing data from the table before writing the export output.
13 On the Column Properties tab, each column being exported must be mapped to a field in the external
database table. Under Field Name, enter the appropriate name of an existing field.
132 Running Exports
Figure 63
Export to Table - Column Properties Tab
14 Select the Field Type of the database field. 15 For fields of type String, specify the Length. For all other field types, the Length is not used. 16 If the Delete based on Version ID(s) option is being used, a Key field must be specified. When the export is
run, all data in the table is first deleted where the Key field is equal to the current version ID of the data being exported. If one of the other options is being used (i.e. Do not clear table or Delete all rows) then the Key field designation is ignored.
17 Once all desired settings have been configured, click OK to close the Export to Table dialog box.
The export is now ready to run. Note that exports configured to output to a table can be run within an export book along with other exports configured for file output.
Using Export Books

Saved exports can be grouped and run together in Export Books. This enables a set of commonly used exports to be executed with one action rather than individually.
Note:
Book exports cannot reference multiple versions. All exports for the book must reference the same version.
Using Export Books 133
To create an export book:

1 Select the Book icon in the Export dialog box. 2 Right-click and select New Book.
Figure 64 Manage Export Books Dialog BoxContent Tab
3 On the Content tab, enter a name and description for the book. 4 Optional: Select Standard Book to make the book available to all users. 5 From the Available list, select the exports that you want to include in the book and use the arrow buttons
to move them to the Selected list.
6 On the Output tab, specify the desired file names if the output is to be combined.
134 Running Exports
Note:
If only a file name is specified, the default directory specified in the Tools-Options menu is used to locate the file. The Pre File and Post File can be used to specify data that is prepended and appended, respectively, to the combined output file.
Note:
When a book contains both exports configured to output to a file and some configured to output to a database table, the Combine option only affects the exports that are writing to files.
Figure 65
Manage Export Books Dialog BoxOutput Tab
Using Export Books 135
136 Running Exports
8
In This Chapter
Using Verifications and Validations
Validations........................................................................................................................ 137 Verifications ...................................................................................................................... 137 Validation or Verification ........................................................................................................ 137 Running Validations ............................................................................................................. 138 Running Verifications ............................................................................................................ 138
Validations
Run automatically (in real-time) as users are editing the structure and properties of hierarchies. Are automatically performed for the node being edited and also for its parent. Have the primary function of denying an attempted update that is invalid. If any validation fails during an update, the update is denied.
Verifications

Run on-demand (batch) after users have made a set of changes. Can be run individually or run in sets defined by the system administrator. Can be inheriting or non-inheriting. If they are inheriting, they run for the node selected or assigned and all descendant nodes. Non-inheriting verifications run on the selected node only. Can be applied to a node and its descendants, a hierarchy, or an entire version. When applied at the version level, the verification is run for all nodes in every hierarchy. Are similar to queries in that they return a set of nodes that fail the business rule.
Validation or Verification
Assume that an organization has a business rule that requires that a sales representative who has been assigned more than twenty customers must obtain special approval from the marketing department.
Validations 137
A Validation that supports this business rule within Data Relationship Management does not allow more than 20 customers to be added to a sales representative node. A Verification supporting the same business rule reports upon all of those sales representatives assigned more than 20 customers.
In summary, some business rules call for real-time enforcement, and such rules should be defined by the system administrator as Validations. Other business rules just need to be monitored, and should be established as Verifications.
Validation Characteristics
In order for a rule to be a candidate for a Validation, it must have the following characteristics:

There are absolutely no exceptions to the rule. There no conceivable timing issues where the rule may temporarily be broken before it can be enforced.
Note that many business rules have exceptions. And for those that do not have exceptions, many still need to be suspended temporarily in order to complete an update. For example, a common rule that Data Relationship Management enforces is called StrandedParent. This rule ensures that all nodes defined as limbs do, in fact, have children. However, the StrandedParent rule must be enforced as a Verification, because all new limbs start out with no children. If this rule were set up as a Validation then no new limb can be added.
Validation and Verification Assignment

Both validations and verifications can be assigned by the system administrator to versions, hierarchies, or specific node chains.
By assigning Validations, the system administrator is establishing a set of hard rules that cannot be broken and which are enforced real-time during hierarchy maintenance. Assigned Verifications are a list of rules that users can run on-demand in order to verify the accuracy of a hierarchy.
Running Validations
Validations are run automatically whenever any changes to a node are saved. If a node fails a validation, the action is cancelled and an error message is displayed.
Running Verifications
Verifications run in a batch mode on request.
138 Using Verifications and Validations
To run a verification, perform the following:

1 Right-click a node and select Verify. 2 Select one of the following options:
Assigned: Runs a list of Verifications (pre-assigned by the system administrator) on the selected node. Selected: Displays the Select Verifications dialog box.
3 If you selected Selected in step 2, each available Verification is listed and can be selected to run by checking
the box.
Click Assigned to select only the verifications assigned by the system administrator.
Figure 66
Select Verifications Dialog BoxVerification Tab
4 Click the Options tab and select to one of the following options to configure the node list returned by the
verifications.

Show in list - all nodes that failed a Verification are displayed in a Hot List Mark Nodes - all nodes that failed a Verification are marked in the Hierarchy Both - nodes are marked and a Hot List is displayed
5 Click OK to run the selected verifications.

Figure 67 Select Verifications Dialog BoxOptions Tab
Running Verifications 139
Viewing Verification Results

To view the results of the verifications:
1 Select the appropriate version in the Version control window. 2 Right-click and select Verification Messages to display the results window.
140 Using Verifications and Validations
9
In This Chapter
Running Property Queries
Working with Property Queries .................................................................................................. 141 Property Query Types ............................................................................................................ 142 Performing Queries............................................................................................................... 142 Property Query Options .......................................................................................................... 146 Hot Lists........................................................................................................................... 148
A property query enables the investigation of the hierarchical structure and the property values of sets of nodes without the need for complex recursive programming. Historically, querying hierarchically structured data through a database using Structured Query Language (SQL) has always been difficult, if not impossible, due to the recursive nature of the required query. Property queries can be used as the basis for filters for exports and compares and as the basis for validations and verifications.
Working with Property Queries

Within Data Relationship Management, the Property Query supports a number of operators such as LIKE, IN, LENGTH, etc. A list of criteria can be created (similar to the WHERE clause in a conventional SQL statement) that can be run against a set of nodes. The Property Query returns a list of nodes that meet the defined criteria. Property Queries can comprise multiple criteria that can be grouped together using AND or OR to form complex queries. Property queries may be saved so different users can develop a tool kit of queries. The system administrator can create standard queries that are available for use by all other users. Typical uses of a Property Query might be:

To locate nodes that meet certain criteria. As a filtering mechanism in exports and comparisons. As a parameter in one of the generic validation routines (this enables queries to have additional functionality as validations.)
Working with Property Queries 141
Property Query Types

Property queries have two distinct flavors:
Normal Property Queries are defined and performed against a node and its children within a hierarchy. They can be run from the top node of a hierarchy or from a node within the hierarchy. The query can reference all properties. Global Property Queries are performed against all nodes in a version. Because the global query runs against a set of nodes without reference to any specific hierarchy, only global properties may be included in the criteria.
Performing Queries
The drop down list at the top of the Property Query dialog box contains all previously saved queries.
To create and perform a new query:

1 From the Tools menu, select one of the following options:

Property Query Global Property Query
142 Running Property Queries
Figure 68
Property Query Dialog Box
2 Select a version. 3 If not a Global Property Query, then select a hierarchy and top node for the list of nodes to be queried by
doing the following:
a. b. c. d.
Click the button to the right of the Hierarchy field to display the Select Node dialog box: Select a hierarchy from the top drop-down box. Navigate the hierarchy to select a top node. Click OK.
Performing Queries 143
Figure 69
Select Node Dialog Box
4 Click Add to build the query criteria.

Query criteria are the building blocks of the query system. Each consists of a property, a comparison operator, and a comparison value. Within the Property Query Item dialog box, select the Property to use, the Query Comparison Operator, and enter a Value to compare against. Add multiple criteria as needed.
Figure 70
Property Query Item Dialog Box
Note that:
Only those query comparison operators relevant to the data type of the selected property is available. The list of properties can be displayed in full or filtered by the property category. By checking the Include Inherited option, the query runs against values that are both overridden and inherited (this is the default behavior.) If this option is not checked, then only overridden values are used in the search. The Defined checkbox is a special criteria that marks a node that has a value saved at that node (i.e. overridden.) It does not do any comparison of the actual value of these nodes. For string properties, the Use String Length checkbox is available to allow comparisons to be done against the property string length instead of the absolute value of the string itself.
The Compare Value is typed into the entry box. This box is unavailable if a value is not required. The query comparison operators that are available for use are described in the following table.
Table 29
Query Comparison Operators Description The value of the property is equal to the compare value The value of the property is not equal to the compare value The value of the property is greater than (but not equal to) the compare value The value of the property is greater than or equal to the compare value The value of the property is less than (but not equal to) the compare value The value of the property is less than or equal to the compare value Strings onlyThe value of the property is in the string in the compare value Strings onlyThe value of the property is not in the string in the compare value Strings onlyThe value of the list property contains the element in the compare value Strings onlyThe value of the list property does not contain the element in the compare value Strings onlyThe value of the property is like (similar to SQL "LIKE" comparison operator) the string in the compare value Strings onlyThe value of the property is not like (similar to SQL "LIKE" comparison operator) the string in the compare value Returns all nodes in the hierarchy that are preceding (i.e. that are antecedents of) the node for which the value of the property is equal to the compare value This is typically used to identify nodes in a hierarchy that are preceding a designated 'end point' (such as a reporting base node, which may be flagged by a Boolean property)
Comparison Operator Equal Not Equal Greater Than Greater Than, Equal Less Than Less Than, Equal In Not In Contains Does Not Contain
Like
Not Like
Above
Not Above
Returns all nodes in the hierarchy that are not preceding (i.e. that are not antecedents of) the node for which the value of the property is equal to the compare value This is typically used to identify nodes in a hierarchy that are not preceding a designated 'end point' (such as a reporting base node, which may be flagged by a Boolean property)
Below
Returns all nodes in the hierarchy that are below (i.e. that are descendants of) the node for which the value of the property is equal to the compare value This is typically used to identify nodes in a hierarchy that are following a designated 'end point' (such as a reporting base node, which may be flagged by a Boolean property)
Not Below
Returns all nodes in the hierarchy that are not following (i.e. that are not antecedents of) the node for which the value of the property is equal to the compare value This is typically used to identify nodes in a hierarchy that are not following a designated 'end point' (such as a reporting base node, which may be flagged by a Boolean property)
Performing Queries 145
Comparison Operator Is Blank Is Numeric Is Not Numeric Is Not Blank
Description The value of the property is blank (the compare value field is unavailable) The value of the property is a numeric value (the compare value field is unavailable) The value of the property is not a numeric value (the compare value field is unavailable) The value of the property is not blank.
5 Go to the Options tab and set the output options.

Figure 71 Property Query Dialog Box
6 Use the speed buttons on the top of the dialog box to save the query. 7 Click OK to perform the query. A Hot List of nodes that match the query criteria are generated and displayed.
Property Query Options

The Options tab of the Property Query dialog box includes the options described in the following table.
Table 30
Property Query Options Description Returns all nodes that meet the criteria, plus their ancestors.
Option Include Match and Parents
Option Include Match and Children Include Match Only Expand List
Description Returns all nodes that meet the criteria, plus their descendants. Returns only nodes that match the criteria (the default behavior.) Available for Include Match and Parents and Include Match and Children. When selected, it allows nodes to be included that are outside of the original scope of the query. For example, in the following hierarchy, if the query starts with Node C and Match and Parents and Inclusive are selected, the result is D and C. If expand list is selected, the result is D, C, B, and A. A B C D * Node matching the criteria E Expand List only includes additional ancestors if the top node specified for the query did not include all ancestors (Include Match and Parents option). Thus, this option has no effect on descendants (include Match and Children option). Note: This option is not applicable for Global Property Query.
Inclusive
Available for Include Match and Parents and Include Match and Children. When selected, it includes the node matching the criteria in the result. This is selected and disabled for Include Match Only. Returns a HotList of nodes that meet the criteria. Marks nodes that meet the criteria in the hierarchy. Note: This option is not applicable for Global Property Query.
Show in list Mark nodes
Both Display Query Criteria
Returns a HotList of nodes and marks them in the hierarchy. Causes extra columns to display in the result set based on the properties being queried. For example, if property query criteria is # Limb Children > 0 and the Display Query Criteria option is selected, then the result set includes a column for # Limb Children that displays the value for each node. If Display Query Criteria is not selected, then this column is not added and only the default columns and properties are displayed in the result list.
Expand to Marked Nodes
This option is available with Mark Nodes and Both. When selected, the hierarchy opens (if it is closed) and expands to the matching nodes and they are marked. Note: This option is not applicable for Global Property Query.
Given the following hierarchy: A B C D *Node matching the criteria E The Inclusive option turns on or off the inclusion of the matching node. The Expand list allows for nodes outside of the original scope of the query to be included So if we started our query at Node C and did a Match and Parents Inclusive we would get (D and C) if we added the expand list we would get D, C, B, and A) Note: Expand List only serves to include additional ancestors if the top node specified for the query did not include
Property Query Options 147
all ancestors. (i.e Include Match and Parents option) Thus, the Expand List option has no effect on descendants (i.e in Include Match and Children option)
Hot Lists
A hot list is a list of nodes returned as a result set from operations such as property queries, compares, and verifications. The hot list enables the user to jump from any node in the list to that node in its hierarchy.
If the list contains nodes from more than one hierarchy, the hot list dialog box displays a tab for each hierarchy. Hot lists can be saved to a file or printed. The Hide node feature enables nodes to be hidden or shown in the list for purposes of saving, printing, and reconciling.
Figure 72
Property QueryHot List Dialog Box
The options on the hot list toolbar are listed in the following table.
Table 31
Hot List Toolbar Buttons Description Run the specified operation again and refreshes the result list
Toolbar Button Refresh list
For query results, open the Property Query dialog box to view the specified query View Parameters Toggle the display of nodes that are set to be hidden Show/Hide Hidden Nodes Print Save to File Find a Node Send the result list to a printer Save the result list to a file Open the Find Node dialog box to search for a node
Toolbar Button
Description Search for the next node meeting the current Find criteria
Find Next
Right-clicking on a node in the Hot List displays the options in the following table.
Table 32
Hot List Right-click Options Description Set the node to be hidden in the list. Set the node not to be hidden in the list. Jump to the node in its hierarchy. Send the result list To Printer or To File. Display another list with the ancestors of this node. Display another list with the siblings of this node. Display another list with the descendants of this node. Display another list with the children of this node. Display another list with all occurrences of this node in all hierarchies. Open the Transaction History dialog box filtered for just this node.
Option Hide Show Go To Print View Ancestors View Siblings View Descendants View Children View Links Transaction History
Hot Lists 149
10
In This Chapter
Comparing Hierarchies
Hierarchy Compare Types ....................................................................................................... 151 Comparing Hierarchies .......................................................................................................... 152
Hierarchy Compare Types

Three hierarchy compare types are available:

Standard Compare on page 151 Property Compare on page 151 Renamed Node Compare on page 152
Standard Compare
The standard compare requires that two points in different hierarchies be selected. Their structures are then analyzed for differences. The points may be in different versions. This is one of the very few features of Data Relationship Management that transcends the boundaries of versions. A standard compare returns two lists:

a list of all the nodes that exist in the first hierarchy but not the second a list of all nodes that exist in the second hierarchy but not in the first
Property Compare
The property compare enables two points in different hierarchies to be selected, and then a particular property is analyzed for any differences. A property compare returns two lists:
a list of all the nodes where the properties are different showing the values of the properties in the first hierarchy a list of all the nodes where the properties are different showing the values of the properties in the second hierarchy
Hierarchy Compare Types 151
Renamed Node Compare

The renamed node compare is the same as the standard compare, but it treats renamed nodes as being the same for comparison purposes. For example, if Hierarchy 1 in a compare includes nodes A, B and C, and hierarchy 2 contains the same nodes but with node C renamed to CC, then the renamed node compare does not identify any differences between the two hierarchies. A standard compare regards nodes C and CC as different if the differences option is selected. A renamed node compare returns two lists:

List of all the nodes that exist in the first hierarchy but not the second List of all nodes that exist in the second hierarchy but not in the first
Property queries may be used to filter the lists of nodes to be compared.
Comparing Hierarchies
To perform an existing or create a compare, perform the following:
1 Select one of the following options from the Tools menu:

Compare Property compare Renamed node compare
152 Comparing Hierarchies
Figure 73
Compare Hierarchies Dialog Box
2 To use an existing definition of a Compare, make a selection from the Compare Name drop down box. You
may then amend any of the saved definitions.
3 To create a new Compare, on the Top Nodes tab select the top node for each of the two hierarchies to be
compared (Hierarchy 1 and Hierarchy 2), by selecting a version and by then clicking node from the hierarchical list of nodes in the Select Node window. and selecting a
4 If a Property Compare was selected in step 1, then the Properties tab is available.
Comparing Hierarchies 153
Figure 74
Property Compare Dialog Box
5 From the list of available properties, select the properties to be compared by clicking the arrow buttons in
the center of the dialog box to move the required properties to the Selected Properties list.
6 On the Options tab select the Comparison Type, Filtering Options, Display Options and Property Filter (if any)
for the comparison.
Figure 75
Compare Hierarchies Dialog Box
7 Select alternate join property if desired.

By default, the compare operation maps nodes from each hierarchy that have the same name. It is also possible to join nodes based on other properties. For example, if a property named SortCode was a unique key in the specified hierarchies, then this property can be used in the Compare to identify differences/similarities between nodes having the same SortCode in each hierarchy.
8 If a Renamed Node Compare has been requested, the Comparison Type options are not available.
If a standard Compare is being performed, then the Treat renamed nodes as similar option is only available if the Comparison Type is Similarities.
9 When all desired options are defined, click OK to perform the comparison. 10 When running a new Compare, the Save As prompt will appear.
To save the new Compare configuration, enter the Name and Description. The Save as Standard option can be checked to make the new Compare available to other users. The results of the compare are displayed in a list and the relevant hierarchy windows are opened.
Comparing Hierarchies 155
11
In This Chapter
Viewing Transaction History
Administrative Actions in Transaction History ................................................................................. 157 Data Actions in Transaction History ............................................................................................ 159 Transaction History Range and Filter Specification ........................................................................... 161 Transaction History Details ...................................................................................................... 163
Administrative Actions in Transaction History

All Data Relationship Management operations are logged in the Transaction History. This data can be viewed by selecting Tools, then Transaction History from the Data Relationship Management main menu. Each operation is recorded with a time stamp, the user name, the type of action performed, and other relevant information. The Transaction History records all changes to metadata such as property definitions, system preferences, and export profiles. The following administrative actions are logged in the transaction history: Node Access Groups

Add Node Access Group Update Node Access Group Update Access Group Members Update Access Group Controlling Hiers Delete Node Access Group Node Types Add Node Type Update Node Type Apply Node Type Props Apply Node Type Validations Delete Node Type
Properties
Add Property Definition
Administrative Actions in Transaction History 157
Update Category List for Prop Def Update Property Definition Update Property Definition Parameters Update Controlling Hierarchy Update Property List Values Add Property Lookup Value Delete Property Lookup Value Delete Property Definition
Property Categories

Add Category Update Category Update Category Users Update Category Properties Delete Category
System Preferences
Update System Preference
System Categories

Add System Category Update System Category Delete System Category
User Management

Add User Set User Password Update User Assign User Node Access Groups Assign User Categories Delete User Update User Lockout
Validations

Add Validation Set Validation Params Update Validation
158 Viewing Transaction History
Delete Validation
Import

Save Import Delete Import
Export

Save Export Delete Export
Book

Save Book Delete Book
Blender

Save Blender Delete Blender
Property Query

Update Criteria List Delete Criteria List
Compare

Save Compare Criteria Update Compare Criteria Delete Compare Criteria
Data Actions in Transaction History

The transaction history provides a record of all the data changes to the system such as version, hierarchy, and node data, as well as logging many basic functions such as user logins, verifications run, and so on. The data transactions are categorized by action types. Following is a list of the action types that are logged: Version Hierarchy and Node Data Changes

Add Hierarchy Add Node Add Orphan Node Add Version
Data Actions in Transaction History 159
Annul Node Annul All Below Node Assign Hierarchy Validations Assign Version Validations Change Top Node Clear All Below Copy Version Delete Hierarchy Delete Node Delete Orphan Delete Version Detach Version Disable Real-Time Validations Inactivate Node Insert Node Lock Node Property Move Node Lost Property Value From Node Order Children Reactivate Node Remove Duplicate Property Values Remove From Orphan Remove Hierarchy Property Value Remove Node Remove Node Property Value Remove Version Property Value Save Version Unlock Node Property Update Hierarchy Property Value Update Node Property Value Update Version Property Value
Logging Actions

Assigned Batch Verifications Run Selected Batch Verifications Run
BCP Run Automator Run Blender Run Close Version Compare Run Export Run Global Query Import Run Log In Log Out Open Version Property Compare Run Query Rebuild Hierarchy Node Table Rename Compare Run
Transaction History Range and Filter Specification

The data displayed can be restricted to a desired range by specifying either:

From Date/Time and To Date/Time From and To transaction ID
After setting the desired range, click the Refresh button to display data within the range.
Transaction History Range and Filter Specification 161
Figure 76
Transaction History
The data can also be filtered on other columns including:

Version Hierarchy Node Action Level User Property
Figure 77
Transaction History
By checking the Filter to Current Session box, the display is limited to only those operations performed because the current user logged in to Data Relationship Management. The Max Records value can be set to limit the number of transactions displayed. Clicking the Automate button opens the Automator Window and enables the user to save the transactions as an Automator file or process them through the Automator.
Transaction History Details

To view the details of a specified transaction, select the record in the grid then right-click and select the Properties option. This opens the Transaction History Detail dialog box.
Transaction History Details 163
Figure 78
Transaction History Details
Figure 79
Administrative Action Detail
12
In This Chapter
Using the Data Relationship Management Batch Client
Overview .......................................................................................................................... 165 Securing the Batch Client ....................................................................................................... 166 Running the Batch Client........................................................................................................ 166 Command Line Syntax........................................................................................................... 167 Configuration File Syntax ........................................................................................................ 172 Outputs and Result Codes ...................................................................................................... 178
Overview
The Data Relationship Management Batch Client is a command-line utility (mdm_connect_ntier.exe) that allows access to various Data Relationship Management operations in batch mode including:

Automator Import Blender Export (individual export and book export) Opening and closing versions
By passing command-line parameters appropriate to the operation, the Batch Client is able to log into the Data Relationship Management engine using supplied credentials, submit a request to perform the given operation, and receive any corresponding results from the server, while logging its activities as it works. If the operation is successful, an error level value of 0 is returned. If the operation fails, a non-zero error level value is returned. For information on error level values, see Table 52 on page 178. The Batch Client accepts options from the command line, a configuration file, or a combination of the two.
Note:
If an option is supplied in both a configuration file and the command line with different values, the value on the command line takes precedence over the value in the configuration file.
Overview 165
Securing the Batch Client

The Batch Client (mdm_connect_ntier.exe) is used to perform batch processes in Data Relationship Management. It requires a username and password to be able to connect to the Data Relationship Management server. The Batch Client can use the Windows Data Protection Application Interface (DPAPI) to allow a more secure method to storing credentials for the Batch Client. The DPAPI protects the information and places it in a location that is only accessible to the user that creates it. Data Relationship Management provides a command line utility (mdm_connect_credentials.exe) that can set the credentials for use by the Batch Client. When the Batch Client runs and no credentials are passed on the command line or in the configuration file, then it uses the credentials stored using the Windows DPAPI.
Setting up Batch Client Credentials

The Credential Utility (mdm_connect_credentials.exe) is used to setup the username and password credentials for the Batch. mdm_connect_credentials.exe associates a Data Relationship Management user to the current Windows account in order to execute the Batch Connect tool securely. The following command line parameters are valid:

Add Stores Data Relationship Management credentials for the current Windows account. Clear Clears the Data Relationship Management credentials for the current Windows account from the secure store. Info Displays the Data Relationship Management username associated with the current Windows account. ? Displays the help file.
If no arguments are passed, the credential utility launches an interactive prompt.
Running the Batch Client

To run the Data Relationship Management Batch Client:
1 Open a command prompt. 2 Navigate to the directory where you downloaded the installation program and to Hyperion\Master
Data Management.
3 Enter mdm_connect_ntier, followed by the parameters as described in this chapter.

The Batch Client can be run from a command prompt or it can be scheduled to run. The Batch Client executes in the following order: 1. Opens the log file. If the log file already exists, the Batch Client appends to it. If the log file does not exist, the Batch Client creates it.
166 Using the Data Relationship Management Batch Client
2. Processes and validates options from the command line or configuration file. 3. Logs into Data Relationship Management using supplied credentials. 4. Runs the appropriate operation. 5. Writes any output file. 6. Logs out of the server, closes the log file, sets the error level and exits.
Dependencies
The Batch Client must run on a computer that meets the requirements for Data Relationship Management client software. The Batch Client requires an HTTP connection to Data Relationship Management. The user login under which it runs must have permissions to use the connection and to read files from directories indicated for input files and to write to directories indicated for log files and export files. For more information on Data Relationship Management N-tier requirements, refer to the Oracle Hyperion Data Relationship Management N-tier Installation Guide.
Note:
The Batch Client is a stand-alone utility program and is not accessible from within the Data Relationship Management client interface.
Saving Versions in the Batch Client

Note:
When using the Batch Client, As Of versions can be specified only as date and time. As Of versions that use date offsets and transaction IDs are not valid. When the Batch Client runs, it logs into an existing Data Relationship Management application server. When new versions are created, they remain detached (not saved to the database) on the application server until they are explicitly saved. When running an Import or Blend via the Batch Client, there is an option to save the version that is created (Autosave=True). The version can be saved or left as detached.
Command Line Syntax

The Batch Client can be used with the command-line parameters described below. Bracketed values ( [ ] ) are optional extensions provided for clarity. Both shorter and longer versions of the value are supported. Commands and parameters are not case sensitive.
Command Line Syntax 167
Caution!
For all parameters, version names containing a space must be enclosed in quotes, for example, APR 2007.
Table 33 describes the command-line parameters for all operations.

Table 33
All Operations Description Specifies the operation to perform. Specify one of the following values:

Parameter
/op=
A[utomate] B[lend] C[lose] E[xport] I[mport] O[pen] R[efresh] D[elete]
This parameter is required

/u= /pw= /url=
Specifies the Data Relationship Management user name for login. Specifies the Data Relationship Management password for login. Specifies the URL (including http:// or https://) for the Web server hosting Data Relationship Management. For example, "http://www.myserver.com/mdm_ntier" Note that this is the same URL used when defining login connections for the N-tier client. Enclosing the value in double quotes is recommended. This parameter is required.
/log=
Specifies the path and file name for the log file. If the file exists, the log is appended to the end of the existing file. Enclosing the value in double quotes is recommended. This parameter is optional. If not specified, the following name is used:
MDMConnectMMDDYYYY.log, where MM = month, DD = day, YYYY = year
/cfgfile=
Specifies the path and file name of the configuration file describing desired options. Enclosing the value in double quotes is recommended. Displays a list of command-line parameters.
/h[elp] | /?
The following tables describe the command-line parameters that can be used with each operation.
Table 34
Automate Parameters Description Specifies the path and file name for the input file. Enclosing the value in double quotes is recommended. This parameter is required. Specifies the delimiter. Specify one of the following values:

Parameter
/infile=
/delim=
Tab Comma
#nnn
where #nnn represents any valid 3-digit ASCII character value (0 255). Tab is the default value.
/cols=
Specifies the column order. If supplied, must contain all column identifiers. A12345 is the default value. Specifies whether to remove quoted strings. Specify one of the following values:

/stripq=
Y[es] N[o] T[rue] F[alse] 1 0
The default value is True.

Table 35
Blend Parameters Description Specifies the name of blender to run. This parameter is required. Specifies the name (or abbrev) for the source version to blend. This parameter is required. Specifies the name (or abbrev) for the target version to blend. This parameter is required. Specifies the name (or abbrev) for the new version to create. Specifies a description for the new version. You must enclose the value in double quotes. Specifies whether to save the blended version or leave it detached. Specify one of the following values:

Parameter
/bl= /sver= /tver= /nvera= /nverd= /save=
Y[es], T[rue], or 1 N[o], F[alse], or 0
The default value is False. For information on saving versions, see Saving Versions in the Batch Client on page 167.
/blendlog=
Specifies the name of the blend log file (not the same as the Batch Client log file). The default value is stored in the blend profile.
Table 36
Close Parameters Description Specifies the name (or abbrev) for the version to close. This parameter is required.
Parameter
/vabbrev=
Table 37
Export Parameters Description Specifies the type of export: individual export or book. Specify one of the following values:

Parameter
/xtype
E[xport] B[ook]
This parameter is required.

/fdate= /tdate= /outfile=
Specifies the From date/time for transaction log exports (Optional) Specifies the To date/time for transaction log exports (Optional) Specifies the path and file name for the output file. If the output file exists, it is overwritten. Enclosing the value in double quotes is recommended. This parameter is required. Specifies the name of the saved export to run. This parameter is required if running a single export. Specifies the name (or abbrev) for the current version. This parameter is required. Specifies the name (or abbrev) for the previous version. This parameter is required. Specifies the version type for the current version. Valid values are:

/xname= /cver= /pver= /cvertype=
A[s Of] N[ormal]
N[ormal] is the default.

/pvertype=
Specifies the version type for the previous version. Valid values are:

A[s Of] N[ormal]
N[ormal] is the default.

/casofdate=
Specifies the As Of Date/Time to use when creating an As Of Version for the current version for the export. Specifies the As Of Date/Time to use when creating an As Of Version for the previous version for the export. Specifies the name of the saved book to run. This parameter is required if exporting a book. Enclosing value in double quotes is recommended. Specifies whether to combine the export output into the file named in /outfile. Specify one of the following values:

/pasofdate=
/bk=
/bkcmb=
Y[es] N[o] T[rue]
Parameter
Description

F[alse] 1 0
If this parameter is False, each export is saved in the file name stored in its export profile. Exports for which the file name in the export profile is invalid or for which Output is set to a value other than File are combined into the file named in /outfile. The default value is stored in book.
/prefile=
Specifies the path and file name to prepend to a combined export book. The default value is stored in book. Specifies the path and file name to append to a combined export book. The default value is stored in book. Specifies the From (Previous) Hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports. Specifies the To (Current) Hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports. Specifies the name (or abbrev) for the top node of the From (Previous) hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports. Specifies the name (or abbrev) for the top node of the To (Current) hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports Specifies the name (or abbrev) for the hierarchy to export. Used for Hierarchy Export and other similar exports, but not used for Hierarchy Compare and Hierarchy Difference exports. Specifies the name (or abbrev) of the top node to export. Used for Hierarchy Export and other similar exports, but not used for Hierarchy Compare and Hierarchy Difference exports.
/pstfile=
/fhier=
/thier= /fabbrev=
/tabbrev=
/hier=
/nabbrev=
Table 38
Import Parameters Description Specifies the path and file name for the input file. Enclosing the value in double quotes is recommended. This parameter is required. Specifies the name (or abbrev) for the import to run. This parameter is required. Specifies the name of the import log file (not the same as the Batch Client log file.) The default value is stored in the import profile. Specifies the version name (or abbrev) to be created by import. The default value is stored in the import profile. Specifies the description of the version to be created by import. The default value is stored in the import profile. Specifies whether to save the imported version or leave it detached. Specify one of the following values:

Parameter
/infile=
/iabbrev= /implog=
/vabbrev=
/vdescr=
/save=
Y[es] N[o] T[rue]
Parameter
Description

F[alse] 1 0
Table 39
Open Parameters Description Specifies the name (or abbrev) of the version to open. This parameter is required.
Parameter
/vabbrev=
Table 40
Refresh Parameters Description Specifies the name (or abbrev) of the version to refresh (close and re-open). This parameter is required.
Parameter
/vabbrev=
Table 41
Delete Parameters Description Specifies the name (or abbrev) for the version to delete. This parameter is required.
Parameter
/vabbrev=
Configuration File Syntax

In addition to using command-line parameters, the Batch Client can be run with a configuration file. Configuration files are formatted like INI files, with sections, keys, and values. There is a General section and an additional section for the specific operation. Section names are enclosed in brackets ( [ ] ) and can be any string value but must match the value specified by the operation key. Lines within each section are formatted in key=value pairs. Below is an example configuration file.
[General] Operation=Export UserName=mylogin Password=mypassword URL=http://localhost/MDM/ LogFileName=C:\Hyperion\Master Data Management\rdsc.log [Export] ExportType=Export ExportName=WeeklyExport OutFile= C:\Hyperion\Master Data Management\export_data.txt CurrentVersionAbbrev=COA Apr 2004 PrevVersionAbbrev=COA Mar 2004
A configuration file can include multiple operations. Each operation is contained in a separate section with a unique label. A special section labeled [Operations] is used to specify the number
of operation sections in the file and the label for each. The operations are performed in the order listed. Below is an example of a configuration file with multiple operations. Note that when using multiple operations, the operation key, for example Operation=Import, must be included in each section rather than just once in the General section.
Note:
Sections, keys, and values are not case sensitive.
[General] Operation=Multiple UserName=mylogin Password=mypassword URL=http://localhost/MDM/ LogFileName=C:\Hyperion\Master Data Management\rdsc.log [Operations] OperationCount=3 Operation1=Weekly_Import Operation2=Update_CostCenters Operation3=Merge_Data [Weekly_Import] Operation=Import InFile="COA_data.txt" ImportAbbrev="RDSC Import" ImportLogFileName="C:\Hyperion\Master Data Management\MDMConnect \import_log.txt" VersionAbbrev="COA Current" VersionDescription="COA for this month" [Update_CostCenters] Operation=Automate InFile=CostCenter_changes.txt StripQuotedStrings=True Delimiter=comma [Merge_Data] Operation=Blend Blendname="COA Blender" SourceVersionAbbrev="COA Current" TargetVersionAbbrev="COA Previous" NewVersionAbbrev="COA Blended" NewVersionDescription="Current and Previous COA"
The following tables describe the keys that can be used in each section of the configuration file.
Table 42
General Section of Configuration File Description Specifies the operation to perform. Specify one of the following values:

Key
Operation
M[ultiple] A[utomate] B[lend]
Configuration File Syntax 173
Key
Description

C[lose] E[xport] I[mport] O[pen] R[efresh] D[elete]
This key is required

UserName Password URL
Specifies the Data Relationship Management user name for login. This key is required. Specifies the Data Relationship Management password for login. This key is required. Specifies the URL (including http:// or https://) for the Web server hosting Data Relationship Management. For example, "http://www.myserver.com/mdm_ntier" Note that this is the same URL used when defining login connections for the N-tier client. Enclosing the value in double quotes is recommended. This key is required.
LogFileName
Specifies the path and file name for the log file. If the file exists, the log is appended to the end of the existing file. Enclosing the value in double quotes is recommended. The default file name is MDMConnectMMDDYYYY.log, where MM = month, DD = day, YYYY = year
Table 43
Multiple Section of Configuration File Description Specifies the number of operation sections in the file. Specify an integer greater than 0. This key is required. Specifies the label for an operation section where N is a number between 1 and the OperationCount value. This key is required.
Key
OperationCount
OperationN
Table 44
Automate Section of Configuration File Description Specifies the path and file name for the input file. Enclosing the value in double quotes is recommended. This key is required. Specifies whether to remove quoted strings. Specify one of the following values:

Key
InFile
StripQuotedStrings
The default value is True.
Key
Delimiter
Description Specifies the delimiter. Specify one of the following values:

Tab Comma
#nnn
where #nnn represents any valid 3-digit ASCII character value (0 255). Tab is the default value.
ColumnOrder
Specifies the column order. If supplied, must contain all column identifiers. A12345 is the default value.
Table 45
Blend Section of Configuration File Description Specifies the name of blender to run. This key is required. Specifies the name of the blend log file (not the same as the Batch Client log file). The default value is stored in the blend profile. Specifies the name (or abbrev) for the source version to blend. This key is required. Specifies the name (or abbrev) for the target version to blend. This key is required. Specifies the name (or abbrev) for the new version to create. Specifies a description for the new version. You must enclose the value in double quotes. Specifies whether to save the blended version or leave it detached. Specify one of the following values:

Key
BlendName BlendLogFileName
SourceVersionAbbrev TargetVersionAbbrev NewVersionAbbrev NewVersionDescription
AutoSave
Table 46
Close Section of Configuration File Description Specifies the name (or abbrev) for the version to close. This key is required.
Key
VersionAbbrev
Table 47
Export Section of Configuration File Description Specifies the type of export: individual export or book. Specify one of the following values:

Key
ExportType
E[xport] B[ook]
This key is required.

OutFile
Specifies the path and file name for the output file. If the output file exists, it is overwritten. Enclosing the value in double quotes is recommended. This key is required. Specifies the name of the saved export to run. This key is required if running a single export. Specifies the name (or abbrev) for the current version. If not specified, the name of the default version is used. Specifies the name (or abbrev) for the previous version. If not specified, the name of the default version is used. Specifies the name of the saved book to run. This key is required if exporting a book. Enclosing value in double quotes is recommended. Specifies whether to combine the export output into the file named in /outfile. Specify one of the following values:

ExportName
CurrentVersionAbbrev
PrevVersionAbbrev
BookName
CombineExportOutput
If this parameter is False, each export is saved in the file name stored in its export profile. Exports for which the file name in the export profile is invalid or for which Output is set to a value other than File are combined into the file named in /outfile. The default value is stored in book.
PreFileName
Specifies the path and file name to prepend to a combined export book. The default value is stored in book. Specifies the path and file name to append to a combined export book. The default value is stored in book. Specifies the From (Previous) Hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports. Specifies the To (Current) Hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports. Specifies the name (or abbrev) of the top node of the From (Previous) hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports.
PostFileName
FromHierarchy
ToHierarchy
FromTopNodeAbbrev
Key
ToTopNodeAbbrev
Description Specifies the name (or abbrev) of the top node of the To (Current) hierarchy. Used for Hierarchy Compare and Hierarchy Difference exports Specifies the number of hierarchy/top node pairs defined. Specifies the Hierarchy to export, where n is a number (1 through HierarchyCount) identifying the current hierarchy/top node pair (for example, Hierarchy1). Used for Hierarchy Export and other similar exports, but not used for Hierarchy Compare and Hierarchy Difference exports. Specifies the name (or abbrev) of the top node to export, where n is a number (1 through HierarchyCount) identifying the current hierarchy/top node pair (for example, TopNodeAbbrev1). Must match Hierarchyn. Used for Hierarchy Export and other similar exports, but not used for Hierarchy Compare and Hierarchy Difference exports. Specifies the From date/time for transaction log exports (Optional) Specifies the To date/time for transaction log exports (Optional) Specifies the version type for the current version. Valid values are:

HierarchyCount Hierarchyn
TopNodeAbbrevn
FromDate ToDate CurrentVersionType
A[s Of] N[ormal]
The default is N[ormal].

CurrentAsOfDate
Specifies the As Of Date/Time to use when creating an As Of Version for the current version for the export. Specifies the version type for the previous version. Valid values are:

PrevVersionType
A[s Of] N[ormal]
The default is N[ormal].

PrevAsOfDate
Specifies the As Of Date/Time to use when creating an As Of Version for the previous version for the export.
Table 48
Import Section for Configuration File Description Specifies the path and file name for the input file. Enclosing the value in double quotes is recommended. This key is required. Specifies the name (or abbrev) for the import to run. This key is required. Specifies the path and file name of the import log file. This is not the same log file as defined by the LogFileName key in the [General] section.) The default file name is MDMConnectImportMMDDYYYY.log, where MM = month, DD = day, YYYY = year Specifies the version name (or abbrev) to be created by import. The default value is stored in the import profile. Specifies the description of the version to be created by import. The default value is stored in the import profile.
Key
InFile
ImportAbbrev ImportLogFileName
VersionAbbrev
VersionDescription
Key
AutoSave
Description Specifies whether to save the imported version or leave it detached. Specify one of the following values:

Table 49
Open Section for Configuration File Description Specifies the name (or abbrev) of the version to open. This key is required.
Key
VersionAbbrev
Table 50
Refresh Section of Configuration File Description Specifies the name (or abbrev) of the version to refresh (close and re-open). This key is required.
Key
VersionAbbrev
Table 51
Delete Section of Configuration File Description Specifies the name (or abbrev) for the version to delete. This parameter is required.
Key
VersionAbbrev
Outputs and Result Codes

All Batch Client operations generate a log file. In addition, exports generate an exported data file and an export log file. The Batch Client logs warnings in the log file for any script items that fail. All errors are also recorded in the log file, including the complete error message. In addition, the Batch Client returns an error level (exit code or result code) indicating its success or failure. Error levels can be tested by a scheduling program or batch file and appropriate action can automatically be taken.
Table 52
Error Level Values Description Successful/normal termination Unknown error
Error Level Value 0 1
Error Level Value 2 3 100 200 210 220 230
Description One or more results from an Automator operation returned a failure Error returned from a Blender operation Error encountered by Data Relationship Management engine and returned to the Batch Client Error occurred during initialization of the Batch Client An invalid parameter value was passed Invalid URL Invalid user name or password
Outputs and Result Codes 179
13
In This Chapter
Using Data Relationship Management Web Publishing
Overview .......................................................................................................................... 181 Web Server Commands ......................................................................................................... 182 Using Web Client Features ...................................................................................................... 183 Main Toolbar and Hierarchy Window ........................................................................................... 184 Frequently Asked Questions .................................................................................................... 189
Overview
The Data Relationship Management Web Publishing module provides an auxiliary means of accessing Data Relationship Management system functionality. This application provides the following capabilities through a Web browser interface:

Viewing hierarchies and node properties Running exports Printing hierarchy trees Searching for nodes in a given hierarchy
Data Relationship Management Web Publishing connects to the Data Relationship Management application server, but operates in a read-only mode. Various requests can be made using HTTP to either retrieve information or execute a command such as running exports or reloading from the database. Figure 80 on page 182 provides a top-level view of Data Relationship Management Web Publishing in relation to the Data Relationship Management architecture. Web Publishing can be run on its own server or hosted on the Data Relationship Management multi-tier Web Server or the primary application server.
Overview 181
Figure 80
Data Relationship Management Web Publishing Architecture
Web Server Commands

You interact with the Data Relationship Management Web Publishing engine by using commands sent via a browser. The available commands are listed in the table below. The commands are entered in a URL format:
http://webservername/mdm_web/mdm_web_pub_gateway.dll/command[? param=value]
where webservername is the Web server name and command is the desired command and param is the parameter and value is the parameter value. Example: http://localhost/mdm_web/mdm_web_pub_gateway.dll/ListHiers?Version=Test% 20Import
Table 53
Web Server Commands Description Returns the versions available for Web Publishing. This list is controlled by the WebVers and WebVersionList system preferences. Returns the hierarchies for a specified version. Returns the full set of properties available for Web Publishing. Returns abbrev, description, label, data type, Categories tab delimited. Parameters {None}
Command
ListVersions
ListHiers ListProperties
Version {None}
182 Using Data Relationship Management Web Publishing
Command
ListNodeProps
Description Returns property values for a specified node. Returns proper abbrev, Value tab delimited Runs a specified export available to Web Publishing. Returns the top node of a hierarchy. Lists the exports available for Web Publishing. Returns the export type, export abbrev, Export Profiles tab delimited Finds a specified Node. Returns Node, Excluded Flag, Inactive Flag Returns the Descendants of the specified node down to the specified level limit. The Return String contains Level, Node Abbrev, Limb/Leaf Indicator, Child Count, Node Description, Node Display Name, Inactive Flag Lists the Export Types Available for Web Publishing Returns the Export text for an export that has been run. The Export contents are streamed. Lists the Standard Exports available for Web Publishing. Returns the Export Type, Export Abbrev and Export Profiles Tab Delimited Returns a set of nodes that matches a search criteria. Returns the Node Abbrev, [Property Value Searched on, If not Abbrev], Excluded Flag, Inactive Flag Returns the Value of the specified system preference Initializes the Engine (Called by the service on startup) Refreshes the Property List. Can be used to have Web Publishing see new properties without restarting Web Publishing
Parameters Version, Hier, Node
RunExport
Export ID, CurrentVersion, PreviousVersion
TopNode ListExports
Version, Hier {None}
FindNode
Version, Hier, Node
ExpandHier
Version, Hier, Node, levellimit
ListExportTypes
{None}
ShowExport
ExportID, CurrentVersion, PreviousVersion
ListStdExports
{None}
SearchForNode
Version, Hier, SearchProp, SearchText
GetSysPrefValue
SystemPrefName
InitEngine
{None}
RefreshProps
{None}
Using Web Client Features

To open a Data Relationship Management Web client, type the following URL into the address
box of your browser:
http://webservername/mdm_web
Using Web Client Features 183
where webservername is the Web server running the Data Relationship Management Web components. The Data Relationship Management Web client home page is displayed.
Main Toolbar and Hierarchy Window

The main toolbar displayed within the client window contains the following items.

Version list - select one of the available Data Relationship Management versions Hierarchy list - select a hierarchy from within the selected version Node name buttons (3) - choose how nodes are labeled in the hierarchy tree Show Inactive - show or hide inactive nodes in the hierarchy tree
Selecting Versions and Hierarchies

The desired Data Relationship Management Version can be selected from the Versions dropdown list at the top left of the window. A Hierarchy from within the selected version can then be chosen from the Hierarchies list. Once a hierarchy is selected, a tree view is displayed in the left frame of the window. The displayed hierarchy tree is navigated as follows:
Clicking the plus sign (+) to the left of a node to expand that node to the next level of the hierarchy Clicking the minus sign (-) to the left of an expanded node to remove the display of any nodes at a lower level in the hierarchy
The display of the node names can be adjusted by selecting one of the node name buttons on the toolbar:
DefaultDisplays the value determined by the hierarchy property (for example, DefaultDisplayBy) if one is set.
DescriptionDisplays the Description for each node. Default and DescriptionDisplays both Default display value and Description for each node.
If none of the three buttons is selected, then the Name for each node is displayed. The Show Inactive option can be used to either include or exclude inactive nodes from the displayed hierarchy tree. The display on the right side of the Web Client is determined by the feature tab currently selected. These four options are available:

PropertiesDisplay properties for the currently selected node. ExportDisplay saved exports available on the Web Client. Print Send image of the current hierarchy tree to a printer. FindSearch for a node in current hierarchy.
Properties
When the Properties tab is selected on the right-hand pane, a read-only view of the properties for the currently selected node is displayed. Clicking each of the available property category tabs display the properties within that category. Each of the properties to which the Web user has access are displayed with the exception of any excluded by way of the WebExcludeNodeProps system preference. Clicking a property in the property viewer causes its Description to be displayed in the status bar below.
Exports
When the Exports tab is selected on the right-hand pane, a list of each available export type, and any saved exports, are displayed in the tree view.
Main Toolbar and Hierarchy Window 185
Figure 81
Exports
The only exports visible in the Web client are those contained in the export book specified by the WebBook system preference. If this system preference is not set or not set correctly, then all exports visible to the Web user are available on the Web client. To run an export, select it in the tree and click the Request Export Run button. The Version Selector window is displayed. Select a version (or select the check box to use the current default version) and then select a previous version if applicable to the desired export type. Click the OK button to send the request. A confirmation message is displayed to confirm that the request for the export has been submitted to the Data Relationship Management Web Server. When the export completes, a new node is displayed in the tree representing the output of the job. This node is labeled with the name of the export and the current and previous versions that were used.
Note:
It may be necessary to click the Refresh Export List button to update the tree and display the latest results.
The result files are stored on the Web server in the directory specified by the WebExDir system preference. To retrieve the export results, select the output node for the export and click the Download Export button. Specify a filename for saving the results and click Save.
Note:
For exports configured to output to a database table, no output is displayed on the Web client nor is anything available for download.
Print
When the Print tab is selected on the right-hand pane, options for printing hierarchy trees are displayed.
Figure 82
Printing Hierarchy Trees
The hierarchy currently shown in the left frame can be printed with the following options:

Full HierarchyPrints the entire hierarchy. From Selected NodePrints the hierarchy from the selected node including all descendant nodes. As Shown In TreePrints the hierarchy with the nodes currently selected and expanded in the left frame tree view. Contents of MemoPrints the contents of the preview window including annotations.
Click the Preview button to display the results of the selected print option in the preview window in the right-hand pane. Additional text can also be typed into the preview window to annotate the hierarchy. Selecting the Contents of Memo option prints the hierarchy data along with any added text. Click the Print It button to send the appropriate text to the default printer for the local machine.
Find
The Find function can be used to locate a node in the selected version and hierarchy using a search string. The WebFindFunction system preference determines which mode will be available: Basic or Enhanced. In the Enhanced mode, the nodes can be searched by:

Name Description OtherAny string property within the hierarchy
Main Toolbar and Hierarchy Window 187
The list of properties available for searching can be restricted if desired. Using the Data Relationship Management client tool, the hierarchy level property WebFindProps can be set to a list of the properties to be used. Then only the properties in that list is displayed in the drop-down list for this option. If the WebFindProps property has no value or does not exist, then all string properties is available in the list.
Tip:
Creating the hierarchy-level property WebFindProps as data type NodeProps makes it easier for users to enter the desired list of properties. The search text can also include wildcard characters. If you include an asterisk (*) before or after the search text, all values that contain the specified substring are returned. Enter the appropriate text in the Search Text box and then click the Find button.
Figure 83
Enhanced Search
The list of nodes matching the search criteria is displayed in Search Results box. Selecting a node from the results and clicking the Go To button highlights the given node in the hierarchy tree. The Clear Results button can be used to erase the contents of the Search Results box.
In the Basic mode, nodes can be searched by name only and the search text must exactly match the name.
Figure 84
Basic Search
Frequently Asked Questions

How do I display the home page after I install or update Data Relationship Management Web Publishing?
If the Data Relationship Management Web Publishing home page is not displayed after you install or upgrade the software, follow this sequence of steps to resolve the problem: 1. Verify that the user name and password entered with the Web Publishing Console are correct. If the Web Publishing login information is invalid, a Catastrophic failure message may be displayed. While this message may sound severe, it simply means that the Engine could not successfully login to the database server. 2. Verify that the URL entered in the browser is correct and has the following format: http:// webservername/mdm_web. 3. Verify network connectivity to the Web server computer as follows: a. Select Start, then Programs, then Accessories, then Command Prompt. b. Enter the following command:
ping Host
where Host is the name of the Web server. 4. Verify that a reply is received from the application server. 5. If no valid reply is received, then check all network connections between the client and server machines. 6. Verify that the Web server is running and IIS is started.
Frequently Asked Questions 189
How do I start the Data Relationship Management Web engine?

The Data Relationship Management Web engine loads automatically when the service is started. You can start and stop the service using the Web Publishing Console or the Microsoft Services screen.
How do I check for error messages?

Any time an unexpected condition arises, an entry is logged into the Windows Event Viewer under Application. The Web Publishing Console can be used to see the filtered set of event log messages pertaining to Web Publishing.
To manually check for error messages:

1 Select Start, then Programs, then Administrative Tools, then Event Viewer. 2 Select the Application Log node or the System Log node. 3 Look for any error messages in the list on the right side of the Event Viewer. 4 If you find errors, double-click the row to view details of which application caused the error and the specific
problem encountered.
How do I check for connectivity with the Data Relationship Management application server?
The Web Publishing Console provides a Web Server tab that displays the versions accessible from the Data Relationship Management application server. If this screen displays versions then there is connectivity to the Data Relationship Management application server. Note you may have to right click and say refresh if you are restarting services so that the cached value shown is refreshed.
A
In This Appendix
Accessibility
Enabling Accessibility............................................................................................................ 191 Enabling Keyboard Equivalents................................................................................................. 191
This appendix describes Data Relationship Management accessibility features.
Enabling Accessibility
Data Relationship Management is always in accessibility mode and does not need to be enabled.
Enabling Keyboard Equivalents

Right-click menus can be accessed by pressing Shift+F10. Use the following keyboard shortcuts to open options in the Data Relationship Management File menu.
Table 54
File Menu Keyboard Shortcuts Keyboard Equivalent Alt+F, A Alt+F, E Alt+F, B Alt+F, I
Menu Option Automator Export Blender Import
The following keyboard shortcuts open options in the Data Relationship Management Admin menu.
Table 55
Admin Menu Keyboard Shortcuts Keyboard Equivalent Alt+A, A
Menu Option Node Access Groups
Enabling Accessibility 191
Menu Option Node Types Node Type Glyphs Properties Property Categories System Categories System Preferences User Management Validations
Keyboard Equivalent Alt+A, N Alt+A, G Alt+A, P Alt+A, C Alt+A, Y Alt+A, S Alt+A, U Alt+A, V
The following keyboard shortcuts open options in the Data Relationship Management Tools menu.
Table 56
Tools Menu Keyboard Shortcuts Keyboard Equivalent Alt+T, P Alt+T, C Alt+T, R Alt+T, N Alt+T, S, R Alt+T, S, N Alt+T, A Alt+T, H Alt+T, O Alt+T, Q
Menu Option Property Query Compare Property Compare Renamed Node Compare Synchronize, By Property Synchronize, ByName Change Password Transaction History Options Request History
The following keyboard shortcuts open options in the Data Relationship Management hierarchy window right-click menu.
Note:
For most of the following menu options, the version must be expanded and selected for the keyboard equivalent to work.
192 Accessibility
Table 57
Hierarchy Window Right-Click Menu Keyboard Shortcuts Keyboard Equivalent Ctrl+O, F11 Ctrl+O, Tab, select node using arrow keys, Ctrl+S Ctrl +O, tab, select node using arrow keys, Shift +F10, T Ctrl +O, tab, select node using arrow keys, Shift +F10, P Ctrl +O, tab, select node using arrow keys, Shift +F10, A Ctrl+O, select a limb node using arrow keys, Ctrl+I Ctrl+M Shift+Ctrl+C Shift+Ctrl+V F12 Ctrl+F12 Ctrl+R Ctrl+D Shift+F10, M Shift+F10, E Ctrl+O, Shift+F10, L, A Ctrl+O, Shift+F10, L, S Ctrl+O, Shift+F10, L, C Ctrl+O, Shift+F10, L, L Ctrl+O, Shift+F10, F, A Ctrl+O, Shift+F10, F, S Ctrl+O, Shift+F10, H
Menu Option Properties Synchronize By Take Put Add Node Insert Node Model After Copy Properties Paste Properties Inactivate Reactivate Remove Delete Move to Previous Node Expand From Here Lists, Ancestors Lists, Siblings Lists, Children Lists, Links Verify, Assigned Verify, Selected Transaction History (Node)
The following keyboard shortcuts open options in the Oracle Hyperion Data Relationship Management, Fusion Edition version and hierarchy right-click menu.
Table 58
Menu Option New, Version New, Hierarchy
Keyboard Equivalent Shift+F10, W, V Shift+F10, W, H
Enabling Keyboard Equivalents 193
Menu Option Open All Open Selected Open Baseline Close Version Close All Close Baseline Copy to New Create As Of Delete Properties Assign, Validation Assign, Verification Verify, Assigned Verify, Selected Verification Messages Clear Verify Results List, Global Nodes List, Orphan Nodes Show Status Column
Keyboard Equivalent Shift+F10, L Shift+F10, S Shift+F10, B Shift+F10, C Alt+F, L Shift+F10, I Shift+F10, P Shift+F10, E Shift+F10, D Shift+F10, R Shift+F10, A, V Shift+F10, A, R Shift+F10, V, A Shift+F10, V, S Shift+F10, M Shift+F10, F Shift+F10, T, G Shift+F10, T, R Shift+F10, H
194 Accessibility
Index
A
accessibility, 191 actions in Automator, 87 Activate, 38 allocating users node access groups, 67 property categories, 67 ancestor export, 123 annulling a node, 53 Automator, 48 defined, 18 flat file format, 86 import errors, 86 required parameters, 89 running imports, 83 supported actions, 87
multiple section, 174 open section, 178 refresh section, 178 dependencies, 167 outputs and result codes, 178 overview, 165 saving versions, 167 Blender defined, 18 elements, 93 setting up top nodes, 98 setting up versions and hierarchies, 95 viewing results, 102 Blender wizard starting, 94
C B
batch client command line syntax all operations, 168 automate parameters, 169 blend parameters, 169 close parameters, 170 delete parameters, 172 export parameters, 170 import parameters, 171 open parameters, 172 refresh parameters, 172 configuration file syntax, 172 automate section, 174 blend section, 175 close section, 175 delete section, 178 export section, 176 general section, 173 import section, 177 compare, 149 defined, 19 property, 20 renamed node, 20 types, 20 controlling hierarchy, 17 creating a new login connection, 24 custom sort order, 57
D
Data Relationship Management changing password, 25 starting, 23 defined, 18 deleting a node, 52 duplicate handling, 78
E
exclusion filter
Index 195
export, 125 export defined, 19 export books, 133 export classes, 105 export to table, 128 export wizard ancestor export, 123 column width, 113 exclusion filter, 125 export books, 133 export to table, 128 generation, 114 hierarchy compare, 116 hierarchy difference report, 117 hierarchy export, 118 lookup export, 120 merge log export, 121 output destination, 128 output formatting, 126 output page, 128 select columns, 109 starting, 106 top nodes, 107 transaction log export, 122 verifications and filters, 124 version export, 123
hierarchy export, 118 hierarchy properties, 65
I
import, 18 elements, 69 sections, 70 import errors, 86 import file format, 75 import mappings, 74 import processing options, 72 import results, 80 import wizard duplicate handling, 78 file format, 75 naming the import version, 71 setting up mappings, 74 setting up sections and processing options, 72 starting, 70 Inactivate, 38 inactivating a node, 53 inheritance defined, 17
K
keyboard equivalents, 191
F
file format import, 75 flat file format in Automator, 86
L
local node, 16 login connection creating new, 24 lookup export, 120
G
generation export, 114 global node, 16
M
memory status, 34 merge log export, 121 Model, 48 Model After, 48 Model Nodes, 48
H
hierarchy defined, 15 working with, 38 hierarchy compare export, 116 hierarchy difference report export, 117
N
naming the import version, 71 node defined, 15 working with, 38
196 Index
node access groups allocating users, 67 nodes annulling, 53 deleting, 52 inactivating, 53 orphan, 54 reactivating, 53 removing, 53
O
orphan node, 54 output destination export, 128 output formatting export, 126 output page export, 128
export, 109 setting column widths export, 113 setting up duplicate handling, 78 setting up import mappings, 74 setting up import sections and processing options, 72 setting up top nodes in Blenders, 98 sort order custom, 57 specifying file format, 75 speed buttons, 26 starting Data Relationship Management, 23 starting export wizard, 106 starting import wizard, 70 system architecture, 13
T
top nodes export, 107 transaction log export, 122
P
parameters in Automator, 89 properties hierarchy, 65 working with, 58 property defined, 16 property categories allocating users, 67 property category, 59 property compare, 20 property editor, 58 property status, 62
V
validations defined, 137 running, 138 verifications defined, 137 running, 138 viewing results, 140 verifications and filters export, 124 version defined, 14 status, 15 version and hierarchies in Blenders, 95 version control window, 33 version export, 123 version status, 34 viewing Blender results, 102 viewing import results, 80 viewing results of verifications, 140
R
reactivating a node, 53 referential integrity defined, 16 removing a node, 53 renamed node compare, 20 running Automator imports, 83 running validations, 138 running verifications, 138
S
selecting columns
Index 197
198 Index

DRM Manual

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

DRM Manual

Enviado por

Direitos autorais:

Formatos disponíveis

ORACLE HYPERION DATA RELATIONSHIP MANAGEMENT, FUSION EDITION

N-TIER USERS GUIDE

TTY Access to Oracle Support Services

About Data Relationship Management

Business rule enforcement

Hierarchy debugging tools

VersionsUser access is restricted based on the version status

About Data Relationship Management

Hierarchical Data Management Types

Organizational structures Charts of accounts Products Customer relationships

Data Relationship Management Components

About Data Relationship Management

Status Working Submitted

Term Leaf Limb

Data Relationship Management Components

Term Child Parent Descendants Ancestors

Children Siblings Orphan

About Data Relationship Management

Validations and Verifications

Data Relationship Management Components

Validation and Verification Example

Comparing Validations and Verifications

About Data Relationship Management

Data Relationship Management Components

Three Compare options are available:

Queries can be used to filter the lists of nodes to be compared.

Data Relationship Management Typical Data Life Cycle

Data Life Cycle Principal Players System administrator

Data Relationship Management users

Data Relationship Management users and/or the system administrator

About Data Relationship Management

Principal Players System administrator

Existing organizational workflow constraints can be enforced by Data Relationship Management:

Other tasks that are performed on an irregular basis:

Data Relationship Management Typical Data Life Cycle

About Data Relationship Management

Starting Data Relationship Management

N-tier Login Dialog Box

Starting Data Relationship Management

User names and passwords are not case-sensitive.

Creating Login Connections

To create a login connection:

Login Connections Dialog Box

Change Password Dialog Box

Your password must contain three of the following elements:

Uppercase letters Lowercase letters Numbers Special characters

Data Relationship Management Desktop and Menus

Speed Buttons on page 26 Main Menu Commands on page 26

Data Relationship Management Desktop and Menus

Speed Buttons Action Open currently selected hierarchy

Send current hierarchy tree view to a printer

Perform Take (copy/move) operation on currently selected node

Perform Put (paste) operation under currently selected node

Open Find Nodes dialog box to search for a node

Expand currently selected node to display it's children

Collapse currently selected hierarchy to only display top node

Open Properties Editor for currently selected version or hierarchy

Main Menu Commands

Menu Item Open Close

Data Relationship Management Desktop and Menus

Menu Item Properties Expand All

Collapse All Nodes by

Refresh Refresh All

Menu Item Property Query