Hyperion Master Data Management 9.0 Administration Student Guide

Hyperion Master Data Management 9.0 Administration Student Guide D50739GC10 Edition 1.0 June 2007 D50924

Copyright 2006, 2007, Oracle. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Table of Contents 0 Preface Course Objectives......................................................xi Course Structure...................................................... xii Course Materials...................................................... xii Student Guide..................................................... xii Student Workbook.................................................. xii Conventions.......................................................... xiii Additional Resources................................................... xiii Module 1: Getting Started Lesson 1: Master Data Management Overview Describing Master Data................................................ 1-2 Master Data Versus Transactional Data and Metadata..................... 1-3 Defining Master Data............................................... 1-4 Master Data Management Objectives.................................. 1-5 Master Data Change Management Challenges........................... 1-6 Hyperion Master Data Management Solution............................ 1-7 Hyperion System 9.................................................... 1-8 Hyperion System 9 Components...................................... 1-9 Hyperion Master Data Management Integrated Environment................1-11 Key Benefits of Hyperion Master Data Management......................... 1-12 Centralized Master Data Store....................................... 1-12 Secured Master Data Store......................................... 1-13 Combined Business Rules.......................................... 1-13 Master Data Audit................................................ 1-13 Historical Information.............................................. 1-13 Reporting on Hierarchies........................................... 1-13 Master Data Key Terms and Concepts................................... 1-14 Applications..................................................... 1-15 Versions........................................................ 1-16 Master Data Life Cycle............................................. 1-18 Version Status................................................... 1-19 Hierarchies...................................................... 1-20 Nodes.......................................................... 1-21 Orphan Nodes................................................... 1-22

Table of Contents Other Hierarchy and Node Terms.................................... 1-23 Properties and Property Categories................................... 1-24 Validations and Verifications........................................ 1-26 Lesson 2: Navigating Hyperion MDM User Interface Connecting to Hyperion MDM Applications................................. 2-2 Launching the MDM NTier Client...................................... 2-3 Creating Login Connections.......................................... 2-5 MDM NTier Client Desktop............................................. 2-7 Working with Hierarchies............................................... 2-8 System Categories................................................. 2-8 Opening Hierarchies............................................... 2-9 Closing Hierarchies................................................ 2-9 Hierarchy Window................................................ 2-10 Configuring the Hierarchy Window....................................2-11 Viewing Node Properties.............................................. 2-12 Property Editor................................................... 2-12 Property Categories............................................... 2-13 Displaying Property Tabs........................................... 2-14 Lesson 3: Working with Master Data Working with Hierarchies............................................... 3-2 Adding and Inserting Nodes.......................................... 3-3 Moving Nodes.................................................... 3-5 Deleting Nodes................................................... 3-6 Merging Nodes.................................................... 3-7 Searching for Nodes.................................................. 3-8 Finding Nodes in a Hierarchy......................................... 3-9 Finding Nodes in a Version..........................................3-11 Navigating Hot Lists............................................... 3-12 Listing Orphan Nodes............................................. 3-14 Analysis Tools...................................................... 3-15 Running Property Queries.......................................... 3-17 Comparing Hierarchies............................................ 3-19 Comparing Properties............................................. 3-20 iv Hyperion System 9 Master Data Management Administration

Table of Contents Module 2: Managing Hyperion MDM Applications Lesson 4: Hyperion MDM Architecture Hyperion MDM NTier Architecture........................................ 4-2 Client Tier........................................................ 4-3 Middle Tier....................................................... 4-3 Database Tier..................................................... 4-3 Users.............................................................. 4-4 Administrators.................................................... 4-4 Business Users................................................... 4-5 User Authentication Modes.......................................... 4-6 Hyperion MDM Web Architecture........................................ 4-8 Configuring Web Access........................................... 4-10 Launching Hyperion MDM Web Client................................. 4-12 Lesson 5: Creating and Configuring Hyperion MDM Applications Creating Hyperion MDM Applications..................................... 5-2 Creating Hyperion MDM Applications on Microsoft SQL Server.............. 5-3 Configuring Hyperion MDM Applications................................... 5-5 Navigating Hyperion MDM Services Console............................ 5-6 Starting and Stopping the Hyperion MDM Services and Processes........... 5-7 Adding Database Connections....................................... 5-8 Setting the Default Database Connection............................... 5-9 Configuring Hyperion MDM Authentication............................. 5-10 Configuring Authentication Methods.................................. 5-12 Configuring Internal Authentication Policies............................ 5-14 Configuring Common Security Services............................... 5-16 Enabling Common Security Services.................................. 5-17 Configuring System Preferences........................................ 5-18 Available System Preferences....................................... 5-19 Lesson 6: Building the Master Data Structure Working with Versions................................................. 6-2 Creating Versions.................................................. 6-3 Saving Versions................................................... 6-4 Applying Life-Cycle Management to Versions............................ 6-5 Copying to a New Version........................................... 6-6 Hyperion System 9 Master Data Management Administration v

Table of Contents Deleting Versions.................................................. 6-8 Managing Hierarchies................................................. 6-9 Adding Hierarchies................................................ 6-10 Creating System Categories........................................ 6-12 Assigning Hierarchies to System Categories............................ 6-13 Editing Hierarchy Properties........................................ 6-15 Saving Hierarchies................................................ 6-17 Deleting Hierarchies............................................... 6-17 Lesson 7: Managing Properties Hyperion MDM Properties Overview...................................... 7-2 Property Definition Levels.............................................. 7-3 Local Versus Global Properties....................................... 7-4 Inheritance.......................................................... 7-5 Global Properties and Inheritance..................................... 7-6 Property Categories................................................... 7-7 Creating Property Categories........................................ 7-8 Built-In Property Categories............................................. 7-9 User-Defined Properties...............................................7-11 Data Types...................................................... 7-12 Property Types................................................... 7-14 Creating and Configuring Properties..................................... 7-15 Setting Up Lookup Properties....................................... 7-17 Setting Up Lists of Values.......................................... 7-19 Specifying a Controlling Hierarchy.................................... 7-20 Setting Up Derived Properties....................................... 7-21 Specifying Default Values.......................................... 7-23 Specifying Maximum and Minimum Values............................. 7-24 Working with Formulas............................................... 7-25 Formula Deriver Class............................................. 7-25 Creating and Editing Formulas...................................... 7-26 Formula Syntax.................................................. 7-28 Testing Formulas................................................. 7-30 Formula Evaluation............................................... 7-31 Functions....................................................... 7-32 Logical Operators................................................. 7-37 vi Hyperion System 9 Master Data Management Administration

Table of Contents Lesson 8: Setting Up Node Types Node Types Overview................................................. 8-2 Node Types Versus Property Categories................................ 8-2 Node Types Benefits............................................... 8-3 Configuring HierarchyNodeType......................................... 8-4 Creating Node Types.................................................. 8-6 Assigning Properties to Node Types................................... 8-7 Assigning a Node Type to Nodes...................................... 8-8 Assigning Node Types to Nodes by Using Derived Properties............... 8-9 Disabling Node Types................................................ 8-10 Adding, Modifying, and Deleting Node Glyphs..............................8-11 Troubleshooting Common Errors........................................ 8-13 Too Few Properties Are Displayed.................................... 8-13 Too Many Properties Are Displayed................................... 8-14 Validations or Verifications Do Not Run................................ 8-14 Lesson 9: Implementing Business Rules Validations and Verifications Overview.................................... 9-2 Considerations for Validations and Verifications.......................... 9-4 Validation Levels.................................................. 9-5 Validation Classes................................................. 9-7 Creating Validations and Verifications..................................... 9-9 Editing Validation Parameters........................................9-11 Create Validations and Verifications by Using Property Queries............. 9-12 Assigning Validations and Verifications................................... 9-13 Assigning Validations and Verifications to Node Types.................... 9-15 Running Verifications.............................................. 9-17 Module 3: Administering Master Data Lesson 10: Loading Master Data Importing Master Data Overview........................................ 10-2 Import Elements.................................................. 10-3 Import Sections.................................................. 10-4 Importing Data to New Versions........................................ 10-5 Selecting Section and Processing Options............................. 10-7 Hyperion System 9 Master Data Management Administration vii

Table of Contents Mapping Properties to Columns...................................... 10-9 Specifying File Format Information...................................10-11 Setting Up Duplicate Handlings..................................... 10-12 Running Imports and Viewing Results................................ 10-14 Saving and Deleting Imports....................................... 10-15 Blending Versions.................................................. 10-16 Blender Elements................................................ 10-18 Configuring Blender Versions and Hierarchies......................... 10-20 Setting Up Top Nodes............................................ 10-23 Selecting Blender Options......................................... 10-25 Running Blenders and Viewing Results............................... 10-27 Importing Data to Existing Versions..................................... 10-28 Automator File Format............................................ 10-29 Performing Imports by Using Automator.............................. 10-32 Reviewing Automator Processing Results............................. 10-34 Lesson 11: Exporting Master Data Exporting Data Overview...............................................11-2 Creating Exports..................................................11-3 Export Classes....................................................11-3 Exporting Hierarchies..................................................11-5 Specifying Top Nodes..............................................11-6 Selecting Export Columns...........................................11-8 Specifying Column Options..........................................11-9 Setting Export Parameters..........................................11-10 Defining Filters and Verifications.....................................11-11 Configuring Output Formats.........................................11-12 Specifying the Output Destination....................................11-14 Saving and Deleting Exports........................................11-15 Creating Generation Exports...........................................11-17 Selecting Columns................................................11-17 Configuring Repeat Parameters.....................................11-18 Defining Exclusion Filters...........................................11-18 Creating Hierarchy Compare Exports....................................11-19 Exporting to a Database Table..........................................11-21 Setting Up Table Fields............................................11-22 Creating and Exporting Books..........................................11-24 viii Hyperion System 9 Master Data Management Administration

Table of Contents Lesson 12: Managing Security Levels of Security.................................................... 12-2 Node Access....................................................... 12-3 Node Access Groups.............................................. 12-5 Global Node Access Groups........................................ 12-6 Managing Node Access Groups..................................... 12-7 Assigning Node Access Groups to Users.............................. 12-8 Defining Controlling Hierarchies..................................... 12-9 Assigning Node Access Groups to Hierarchies......................... 12-10 Property Access.....................................................12-11 Assigning Property Categories to Users.............................. 12-12 Managing Users.................................................... 12-13 Creating Users.................................................. 12-14 Assigning User Permissions....................................... 12-16 Locking and Unlocking Users...................................... 12-18 Changing User Passwords........................................ 12-20 System Preferences and Security................................... 12-21 Lesson 13: Auditing Master Data Tracking Master Data Changes......................................... 13-2 Viewing Baseline Versions.......................................... 13-3 Viewing the Transaction History...................................... 13-4 Viewing Transaction History Details................................... 13-5 Exporting the Transaction History.................................... 13-6 Analyzing Master Data Changes........................................ 13-7 Creating As Of Versions............................................ 13-8 Exporting Hierarchy Differences..................................... 13-9 Appendix A: Hyperion MDM Implementation Guidelines Implementation Process Overview....................................... A-2 Discovering the Environment......................................... A-3 Identifying Business Requirements.................................... A-4 Designing Application Structure....................................... A-6 Loading and Analyzing Master Data................................... A-8 Preparing for Rollout.............................................. A-10 Going Live...................................................... A-11 Hyperion System 9 Master Data Management Administration ix

Table of Contents x Hyperion System 9 Master Data Management Administration

Preface 0 Welcome to Hyperion System 9 Master Data Management Administration! Before you begin, please take a moment to review this section. The preface presents an overview of the following information: Course objectives Structure of the course Course materials used in the class Conventions used in the book Additional resources to enhance your learning Relevant follow-up courses that you might want to attend in the future Course Objectives After completing this course, you should be able to: Describe Hyperion MDM concepts and terminology Navigate the Hyperion MDM user interface Edit versions and hierarchies Describe the Hyperion MDM architecture Create Hyperion MDM applications Manage and organize properties Enforce business rules Load and export master data Manage security Track master data changes

Preface Course Structure Hyperion System 9 Master Data Management Administration is a 3-day, instructor-led training course consisting of lectures, demonstrations, and hands-on exercises. In this course, the instructor presents a topic conceptually by explaining its purpose, demonstrating how it works, and then guiding the students through the exercises. Demonstrations and hands-on exercises reinforce the concepts and skills introduced during lectures. Course Materials You use two books in class the student guide and the student workbook. The instructor may also give you handouts. Student Guide The student guide is designed to be used by students and the instructor during lecture time. It has 3 modules: Module 1 describes Hyperion MDM concepts and terms, the Hyperion MDM components and architecture. You also become familiar with Hyperion MDM user interface. Module 2 describes how to create a new Hyperion MDM application and how to build its structure including versions, hierarchies, properties, node types, and business rules. Module 3 describes administrative tasks to manage and maintain the application structure. Each module contains lessons. Each lesson begins with a list of objectives followed by the presentation of slides and accompanying text. The lesson ends with a summary of the topics covered in the lesson. Student Workbook The student workbook has two sections exercises and exercise solutions. Exercises A critical part of the learning process is the challenge of completing real tasks associated with each lesson. Each exercise is an opportunity to apply your new knowledge. Solutions The solutions present the detailed steps to successfully complete the exercises. xii Hyperion System 9 Master Data Management Administration

Preface Conventions The following text conventions are used in this course book: Text to be typed, options to be selected, names of files and modules, and menu selections are displayed in bold type. Examples: - Select Clear Profile. - Click YES to clear the profile. When available, figures are used to identify an object or task. Example: Click Edit. Keyboard shortcuts are displayed as follows: Ctrl+Enter Alerts are used to direct your attention to different types of information. NOTE A note provides related information, common mistakes, or cautions about the current topic. TIP A tip provides information that helps you work more efficiently. Additional Resources Use the following resources to enhance your learning: Hyperion System 9 Master Data Management Services NTier Administrator s Guide. Hyperion System 9 Master Data Management Services NTier User s Guide. Hyperion System 9 Master Data Management Administration xiii

Preface xiv Hyperion System 9 Master Data Management Administration

M O D U L E 1 Getting Started 0 Overview The Hyperion MDM solution provides a centralized, transparent process for managing critical BPM master data that drive enterprise reporting. The lessons in this unit introduce you to Hyperion MDM concepts and terms, the Hyperion MDM components and architecture. You also become familiar with Hyperion MDM user interface. Lessons in this module include: Master Data Management Overview Navigating Hyperion MDM User Interface Working with Master Data

L E S S O N 1 Master Data Management Overview 1 Objectives At the end of this lesson, you should be able to: Describe master data and master data management (MDM) challenges Describe the benefits of the Hyperion System 9 Master Data Management solution Describe Hyperion MDM concepts and terminology

Lesson 1 Master Data Management Overview Module 1 Getting Started Describing Master Data Master data is data that is shared across systems (such as lists or hierarchies of customers, suppliers, accounts, or organizational units) and is used to classify and define transactional data. IDC A company may record the transaction of selling Product A to Customer X on 1/1/06 for $100. Taken as a whole, this is a single transactional data record. However, embedded in the transaction are various elements of master data (i.e. Product A and Customer X) that help define the transaction and can be used to "slice and dice" the data for reporting purposes. Key Point: Master data is a requirement for transactional and analytical systems. Describing Master Data The slide shows a quote from a white paper titled Managing Master Data for Business Performance Management: The Issues and Hyperion s Solutions, written by Harry D Morris and Dan Vasset of IDC, in April of 2005. Master data drives the execution of both enterprise back office systems such as enterprise resource planning (ERP), Business Intelligence (BI), and business performance management (BPM) solutions. According to John Kopcke, CTO of Hyperion Compliance and performance management both require consistent master data across an enterprise. Managing master data is one of the most difficult, time consuming and expensive challenges facing IT professionals in enterprises today. 1-2 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Master Data Versus Transactional Data and Metadata Transactional Data Company Hyperion Entity FL Account 100000 Sub-Account 500 Date 8/12/05 Amount $70,000 Sales Person Ralph Collins Metadata Company Text Char (25) Entity Text Char(2) Account Integer Int (6 ) Sub-Account Integer Int (3) Date Datetype MM/DD/YY Amount Float Decimal Sales Person Text Char (25) Master Data Product Organization Accounts Software Central Sales (+) BI Essbase (sku #) MN FL Direct (+) Partner (+) Training East Cost of Sales (-) Master Data Versus Transactional Data and Metadata Master data is not transaction data. Transaction data is information that is generated and captured by operational systems and describes the activities, or transactions, of the business. For example, a single transaction might be Ralph Collins sold $70,000 worth of software and services on August 12, 2005. Master data is not metadata. Metadata is data that describes transactional data for the systems that store it. Master data represents core elements of the business that are applied to multiple transactions and are used to categorize, aggregate, and evaluate the transaction data. Master data enables IT systems and users to understand the meaning of each piece of data in a transaction. Hyperion System 9 Master Data Management Administration 1-3

Lesson 1 Master Data Management Overview Module 1 Getting Started Defining Master Data Master data Is a vocabulary that includes: Hierarchies (business dimensions) Reporting structures Attributes Business rules Defines enterprise standards for key performance management processes: Financial reporting Planning Analysis Business modeling Key performance indicators (KPIs) Defining Master Data Master data for business performance management (BPM) is the vocabulary of business users. From a reporting or dimensional modeling perspective, it refers to the hierarchies around which metrics are organized. It consists of dimensions, reporting structures, attributes, and business rules. Unlike enterprise resource planning (ERP) reference data, BPM master data does not involve the process of recording transactions. It focuses on defining enterprise standards for key performance management processes, including financial reporting, planning, analysis, business modeling, and key performance indicators (KPIs). 1-4 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Master Data Management Objectives Balance enterprise needs Synchronize systems Enforce policies Create consistency Manage change control process Empower business users Master Data Management Objectives The goal of centralized master data management is to synchronize business performance management master data changes across the enterprise. Its objectives are to eliminate master data inconsistencies by enforcing business rules and manage the master data change control process. Business users own and maintain the hierarchies (master data) that pertain to their specific line of business. The IT group is responsible for implementing and maintaining the MDM infrastructure, including managing security and ensuring data integrity. As an end result, centralized master data management balances enterprise needs and empowers business users. Hyperion System 9 Master Data Management Administration 1-5

Lesson 1 Master Data Management Overview Module 1 Getting Started Master Data Change Management Challenges Despite its importance, master data is often inconsistent across a company. Data that should be unique is often different in different information systems. According to IDC, Master data management is currently handled independently in many separate analytic and transactional systems. The lack of coordination limits the ability for organizations to accurately track, analyze, and manage information about their customers, products, and suppliers. Without a centralized master data management system, the process of managing master data changes is an error-prone manual process that involves many people across the enterprise. It does not provides an audit trail and it is almost impossible to roll back changes. The process is time and resource consuming. 1-6 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Hyperion Master Data Management Solution The Hyperion master data management solution provides a centralized, transparent process for managing critical business performance management master data that drive enterprise reporting. With Hyperion MDM, you can create customized master data views and configure security in a way that enables business users to work independently within their area of responsibility to manage master data changes that are specific to their functional areas. By eliminating the complexity that surrounds change management processes, Hyperion MDM enables a collaborative relationship between business users and IT. Business users can manage their own master data in an environment that is designed to represent master data in a format that they can easily understand. Hyperion System 9 Master Data Management Administration 1-7

Lesson 1 Master Data Management Overview Module 1 Getting Started Hyperion System 9 Hyperion delivers the most comprehensive and flexible business performance management (BPM) system in the marketplace today. It integrates a modular suite of financial management applications with the most comprehensive business intelligence (BI) capabilities for reporting and analysis. It increases user productivity, lowers cost of ownership, and reduces business risk. Hyperion System 9 is the first business performance management system in the market. It represents the convergence of disparate technologies and is a major milestone in the business performance management category. System 9 provides an enterprise-class deployment foundation and a pervasive and personalized user experience. System 9 enables companies to understand the past, monitor the present, and plan for future performance across the enterprise. 1-8 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Hyperion System 9 Components Hyperion System 9 BI+ Workspace Hyperion System 9 Applications+ Financial Management Planning Strategic Finance Performance Scorecard Hyperion System 9 BI+ Interactive Reporting Enterprise Analytics Essbase Analytics Web Analysis Financial Reporting Production Reporting Enterprise Metrics Hyperion System 9 Foundation Services Master Data Management Services Application Link Advanced Shared Services Hyperion System 9 Components System 9 consists of four main components: Hyperion System 9 Applications+ Hyperion System 9 BI+ Hyperion System 9 Foundation Services Hyperion System 9 BI+ Workspace Applications+ provides comprehensive support for the performance management cycle, delivering performance scorecarding, modeling, budgeting, planning, forecasting, financial consolidation, and reporting in an integrated, modular suite. Hyperion System 9 Master Data Management Administration 1-9

Lesson 1 Master Data Management Overview Module 1 Getting Started BI+ stores, protects, and delivers information for a company s extended enterprise (employees, customers, suppliers, and partners). It enables you to analyze, transform, and report data; search for, retrieve, and use documents; run queries, execute and schedule jobs; and distribute logs. Foundation Services supports functions that are common to all components. Application+ and BI+ communicate and share data through Foundation Services. System 9 components can connect to a variety of data sources and are accessed through a common interface called Workspace. Workspace allows you to access and interact with Hyperion authored content using BI+ tools as well as third-party documents such as Microsoft Word and Excel files. 1-10 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Hyperion Master Data Management Integrated Environment Hyperion System 9 Shared Services Essbase Cube Other Tools ODS Hyperion MDM Data Warehouse ETL Business Process SAP Oracle PeopleSoft Legacy Hyperion Master Data Management Integrated Environment The diagram on the slide displays the Hyperion MDM conceptual architecture. Hyperion MDM is not only a central repository for synchronizing BPM master data, but it also provides a choice for making changes either at Hyperion MDM or at peripheral systems. In addition, it includes a comprehensive simple object access protocol (SOAP) and component object model (COM+) API for integrating via Web Services with other applications, regardless of data models. Hyperion System 9 Master Data Management Administration 1-11

Lesson 1 Master Data Management Overview Module 1 Getting Started Key Benefits of Hyperion Master Data Management The store of business dimensions (hierarchies): Is centralized and secured Stores business rules Can be audited Provides historical information Enables reporting on hierarchies Key Benefits of Hyperion Master Data Management Master Data Management is a tool that helps you manage complex hierarchies business dimensions that are used in operational (transactional) systems, data warehouses, and analytic databases. Centralized Master Data Store Thousands of changes in hierarchies may occur every month. A number of different systems use master data. For example, Essbase analytic cubes, downstream reporting systems, general ledger systems, and legacy systems must use the same set of master data. A centralized data store keeps all dependent systems synchronized. 1-12 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Secured Master Data Store Typically only a few people are responsible for making changes in the master data in a corporation. These people may not be experts in managing all master data, which may result in inaccurate data. Distributing management of the master data to corporate lines of business (LOBs) helps solve this problem. Corporate LOBs should be able to make changes to their sections of the hierarchies. Combined Business Rules Business rules are different for different systems. For example, Essbase, Hyperion Financial Management, SAP, and legacy systems have different means to specify their business rules. The master data store combines the entire set of business rules. Master Data Audit Many legacy systems do not provide answers to the following questions: Who added this cost center? When was this description changed and who changed it? What is the difference between last month s accounts structure and this week s? What nodes have been added, deleted, moved, or renamed in the hierarchy? The master data store keeps track of all these changes and enables you to audit the master data. Historical Information Master data management enables you to go back in a business cycle and retrieve historical information to answer questions like this: Show me my business dimension structure as of the beginning of this year (or close of business last year, or close of business last quarter). The ability to retrieve historical information supports analysis reports to display exactly what the master data were when you created these quarterly reports. Reporting on Hierarchies Master data management enables you to distribute information to downstream reporting systems as well as to other people who might need to create reports on changes, reports that display their sections of hierarchy, and so on. Hyperion System 9 Master Data Management Administration 1-13

Lesson 1 Master Data Management Overview Module 1 Getting Started Master Data Key Terms and Concepts Applications Versions Hierarchies Nodes Properties and property categories Validations and verifications Master Data Key Terms and Concepts Hyperion MDM uses the following key terms to define and manage master data: applications, versions, hierarchies, nodes, properties, property categories, validations, and verifications. 1-14 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Applications MDM applications are independent repositories of master data. Versions MS SQL DB MDM Application 1 Versions Oracle DB MDM Application 2 Applications A Hyperion MDM application is a store of master data and the information that is needed to manage master data in a relational database. As part of the Hyperion MDM installation, you can create an MDM application in either a Microsoft SQL Server or an Oracle relational database. You can use multiple MDM applications to support the many business needs for hierarchical data in an organization. Each application is independent of all other applications. Hyperion System 9 Master Data Management Administration 1-15

Lesson 1 Master Data Management Overview Module 1 Getting Started Versions Represent independent sets of master data Encapsulate hierarchies Are typically related to business time periods Support what if scenarios Markets Accounts March 2006 Products Versions Hyperion MDM groups sets of hierarchies into versions. A version represents a single, independent set of master data that is arranged into related hierarchies. Versions are usually related to time periods or functions. Examples of versions are March 2005, 3rd Quarter 2004, and Planning. Versions are typically used for the following purposes: To represent a set of hierarchies used during a particular month (or other business cycle period). For example, a new version is created each month, allowing the master data historical records to be stored. To plan changes in the current version for the next main business cycle period; for example, for the next fiscal year. To support what if scenarios during reorganizations, restructures, and merges. 1-16 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview To differentiate between real data and test data during system testing. To compare different versions to identify changes that are being made to the hierarchies across time. New versions can be created by copying existing versions. However, once a version is created, it is independent of other versions. Hyperion System 9 Master Data Management Administration 1-17

Lesson 1 Master Data Management Overview Module 1 Getting Started Master Data Life Cycle Most organizations use master data on a cyclical basis that matches their management reporting periods (typically every month). Within each reporting period, the use of master data follows a predictable pattern that includes the following phases: 1. An administrator creates a new working version as a copy of the finalized version for the previous period. 2. Business users make changes to the working version. Validations are automatically performed as users enter or amend master data. 3. As the reporting period deadline looms, the version status is changed to Submitted. The administrator runs compares to identify changes and performs validations and verifications to ensure the integrity of the data. 1-18 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview 4. When data integrity is assured, the administrator changes the version status for the current reporting period to Finalized and the version status for the previous reporting period from Finalized to Expired. The expired version is stored for possible future use in historical analyses or as an audit record. 5. The administrator performs exports 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. Version Status The version status controls the workflow of hierarchy maintenance. There are four version statuses: Version Status Working Submitted Finalized Expired Description Business users can manage and change the master data within the version within the limitations of configured constraints and validations. Business users are limited by security. The version is submitted for administrator review. Only administrators can change the master data. Business users are not allowed to make changes, but they can view the master data. This status is used towards the end of a master data cycle to allow for verification, corrections, and synchronized publishing of all changes. No one can change the master data within the version. This status is used to create a "gold copy" of all master data structures and properties as they are at the close of a life cycle period. Administrators and business users can view the master data within the version. This status is preserved for comparison and historical purposes. An attempt to publish (export) from an expired versions generates a warning that the data may be out of date. Hyperion System 9 Master Data Management Administration 1-19

Lesson 1 Master Data Management Overview Module 1 Getting Started Hierarchies Define structural relationships among master data (organization structure, accounts, geographic) Store alternate rollups Are uniquely defined by their top node Product Hierarchy All Segments Top Node Electronics Limb Audio Systems Leaf Services Installation Repair Limb Leaf Leaf Hierarchies A hierarchy is a logical set of nodes that are all descendants of a single top node. Thus a hierarchy is defined by its top node and represents all the nodes in the hierarchical relationships below that node. 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 Hyperion MDM. Each hierarchy is usually associated with a certain view, external system, or management report. Example of hierarchies are Line of Business, Markets, and Management Summary. 1-20 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Nodes Are the hierarchy building blocks Use familial relationship terms Sibling of East Markets West Ancestors of CA CA Parent East Child Child CT NY Descendants of East New York Nodes A node is a point in a hierarchy. Every point in a hierarchy is a node. For example, in a hierarchy representing an organizational structure, a node may represent a department or a cost center within the organization. Familial relationship terms are used to define the position of nodes in the hierarchy. For example, a node is a child if it is directly below another node; a node is a parent if it is directly above another node. Similarly, descendants are all of the nodes below a given node, and ancestors are all of the nodes between a given node and the top of a hierarchy. Hyperion System 9 Master Data Management Administration 1-21

Lesson 1 Master Data Management Overview Module 1 Getting Started Nodes (continued) Always have the same children in all hierarchies May not be assigned to a hierarchy (orphan nodes) Markets West Stores CA Orphan nodes CA CA LATAM East East EMEA CT NY CT NY UK France APAC Nodes (continued) A node may be a part of more than one hierarchy in the same version. To ensure structure integrity, nodes always have the same children in all hierarchies, and a node may not exist more than once in any hierarchy. 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. Orphan nodes are created as the result of removing nodes from hierarchies. Orphans may exist pending a cleanup to completely remove them, or they may be awaiting reallocation to one or more hierarchies in the version. 1-22 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Other Hierarchy and Node Terms Markets Root node West CA Branch Tree East Limb CT NY Leaf Limb Mixed kids New York Leaf APAC Limb (stranded parent) Other Hierarchy and Node Terms Hyperion MDM uses additional terms that define hierarchy structure elements. For example, the hierarchy is also called a tree; the top node is also called the root node of the hierarchy; and a tree structure that starts from a parent node and includes all of its descendants is called a branch. Every node is classified as a limb or a leaf. A limb is a node that can have children; a leaf is a node that cannot have children. In addition, a limb without leaves is called a stranded parent and a mix of limbs and leaves with the same parent is called mixed kids. Hyperion System 9 Master Data Management Administration 1-23

Module 1 Getting Started Lesson 1 Master Data Management Overview Properties and Property Categories Properties Define the node attributes Are created by the administrator West Property categories Group properties into manageable subsets Are assigned to users to ensure basic security and interface simplification Node ID Name Description Leaf Consolidation Expense Tag Account Type Data Type System Essbase Planning Properties Property Categories Properties and Property Categories Properties are main components of a Hyperion MDM application. They are created by the system administrator and can be grouped into property categories. Properties Properties can be defined and stored at three levels: version, hierarchy, and node. Most properties in Hyperion MDM are defined at the node level and contain information that describes a node. Examples include the name of the node, the description of the node, and the number of children of the node. Properties at the version and hierarchy level are less common. 1-24 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Property Categories Property categories enable you to group properties and to control the allocation of security privileges to sets of properties. For example, properties can be grouped by source or by destination system. The same property can be in one or many property categories. You can assign users to property categories to enforce basic security and simplify interface. As an administrator, you can always see all property categories. Hyperion MDM is delivered with the following property categories. Property Category System Stats Validation Verification Leaf Access Limb Access Description Properties related to a node s identifying characteristics, such as ID, Name, and Description. Properties that provide statistical information about the node, such as number of children and number of siblings. Validations currently assigned for the node one property for each validation. 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. Hyperion System 9 Master Data Management Administration 1-25

Lesson 1 Master Data Management Overview Module 1 Getting Started Validations and Verifications Ensure data quality and enforce business rules: Real-time (validation) Batch mode (verification) Run on demand Scheduled exports Are defined by the administrator Validations and Verifications Validations and verifications ensure master data quality and enforce business rules. Validations are performed in real time. For example, account numbers must have 8 numeric characters. When the user enters a new account number, Hyperion MDM validates the entered data and notifies the user if it is not valid. Verifications are performed in batch mode on demand by the administrator or as scheduled exports. For example, a hierarchy should not allow stranded parents or mixed kids. 1-26 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 1 Master Data Management Overview Summary In this lesson, you should have learned to: Describe master data and master data management (MDM) challenges Describe the benefits of the Hyperion System 9 Master Data Management solution Describe Hyperion MDM concepts and terminology Hyperion System 9 Master Data Management Administration 1-27

Lesson 1 Master Data Management Overview Module 1 Getting Started 1-28 Hyperion System 9 Master Data Management Administration

L E S S O N 2 Navigating Hyperion MDM User Interface2 Objectives At the end of this lesson, you should be able to: Launch the MDM NTier client and connect to Hyperion MDM applications Manage login connections Navigate hierarchies View node properties

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started Connecting to Hyperion MDM Applications You can specify multiple connections in MDM NTier client, but you can connect to only one application at a time. Connection A http://host_a/mdm_ntier Host A Application A MDM NTier Client Connection B http://host_b/mdm_ntier Host B Application B Connecting to Hyperion MDM Applications You use the MDM NTier client, a Windows application that runs on the local computer, to connect to Hyperion MDM server that supports multiple, simultaneous users and provides access to the corresponding MDM application. The MDM system administrator defines which application is served by the Hyperion MDM server. From MDM NTier client, you can connect to only one Hyperion MDM application. To simplify the login process and avoid inadvertent connections to the wrong environment, you can create and manage many login connections. If no login connections are defined, you are prompted to create a new login connection. 2-2 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface Launching the MDM NTier Client To start the MDM NTier client: 1. Launch the client: C:\Hyperion\Master Data Management Services\ mdm_ntier_client_http.exe 2. Log on to the client: Launching the MDM NTier Client Hyperion MDM NTier client provides user interface for all users who work with master data. To launch the MDM NTier client: 1. Run the C:\Hyperion\Master Data Management Services\ mdm_ntier_client_http.exe file. NOTE You can also start the MDM NTier client from the Start menu by selecting Start > Programs > Hyperion System BI+ > Master Data Management Services > MDM Client Software. The MDM NTier Login dialog box is displayed. Hyperion System 9 Master Data Management Administration 2-3

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started 2. Log on to the client: a. From the Connection drop-down list, select the connection. b. In the User Name text box, enter your username. c. in the Password text box, enter your password. d. Click OK. The MDM NTier client desktop is displayed. 2-4 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface Creating Login Connections Named login connections simplify the login process by storing: The URL to the Hyperion MDM application The user name Creating Login Connections Login connections store the URL to Hyperion MDM applications and the user name. To create a login connection: 1. In the MDM NTier Login dialog box, click the ellipsis button, [...], to the right of the Connection list. The Login Connections dialog box is displayed. 2. Perform the following steps: a. In the Name text box, enter a name for the connection to indicate the environment being used. b. In the HTTP Server URL text box, enter the URL to the Hyperion MDM application provided by the MDM administrator. Hyperion System 9 Master Data Management Administration 2-5

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started c. Click Test to verify the login connection d. In the User Name text box, enter the primary username to be used with this login connection. 3. Click OK to save the login connection and close the dialog box. 2-6 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface MDM NTier Client Desktop Menu bar Speed buttons Desktop Version Control window MDM NTier Client Desktop When you log on to the MDM NTier client, its desktop is displayed. The desktop contains a menu bar, speed buttons, and the Version Control window. Menu commands enable you to perform actions on master data such as opening versions and hierarchies, viewing properties, and editing nodes. The speed buttons allow quick access to frequently used functions within the client. To review the function of a speed button, hold the cursor over the button. A tooltip that explains the function of the button is displayed as a balloon. The Version Control window lists a tree view of the available versions, along with the hierarchies contained in each version. The icon to the left of each version in the Version Control window indicates the status of the version. Hyperion System 9 Master Data Management Administration 2-7

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started Working with Hierarchies Hierarchies provide the main interface for business users. A version can have one or more hierarchies. Hierarchies can be grouped into system categories. System category Hierarchies Hierarchy window Working with Hierarchies Hierarchies are contained within a version, and a single version may contain multiple hierarchies. Each hierarchy is usually associated with a certain view, external system, or management report. A hierarchy is a logical set of nodes within a version. The nodes that make up a hierarchy are all descendants of a single top node. In this way, a hierarchy is defined by its top node and represents all the nodes in the hierarchical relationships below that node. System Categories Hierarchies can be grouped into system categories within a version. System categories are displayed in the Version Control window as folders. As an administrator, you can manage system categories as well as the order of hierarchies within the given system category. 2-8 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface Opening Hierarchies You can open a hierarchy from the Version Control window or from the menu. When you open the first hierarchy for a particular version, the entire version is loaded into memory. To open a single hierarchy from the Version Control window, double-click the hierarchy name. Each hierarchy within the version is opened in a separate window. NOTE If you double-click the system category, all grouped hierarchies are opened, which results in multiple windows being open. Closing Hierarchies When you open a hierarchy, its status is indicated by a bold hierarchy name in the Version Control window. To close the hierarchy, you close the hierarchy window or close the hierarchy version. Hyperion System 9 Master Data Management Administration 2-9

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface Hierarchy Window A hierarchy can be displayed in only one hierarchy window. You can change the top node of the hierarchy to limit the tree view. Hierarchy Version View Nodes by button Hide/Show child panel button Selected node description Tree view Children of the selected node Child panel Hierarchy Window When you open a hierarchy, it is displayed in the hierarchy window in which the title bar shows the name of the hierarchy and version. You can open as many hierarchy windows as desired, although you cannot open the same hierarchy in more than one window at a time. The hierarchy window contains two panes: The pane on the left is the tree view; it displays the structure of the hierarchy. To expand a node in the hierarchy, click the plus sign (+) next to the node or double-click the node itself. To hide expanded nodes, click the minus sign (-) next to the node or double-click the node. The pane on the right is the child panel; it displays the children of the selected node. The child panel also displays certain properties of the child nodes. You can open and close the child panel by clicking the Hide/Show child panel button. 2-10 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface Configuring the Hierarchy Window By default, the hierarchy window displays the Name, Description, and Links properties in the child panel. You can configure it to display specific properties by using the View Nodes by button on the hierarchy window toolbar or by selecting View > Nodes By > Defined Properties from the client menu. You can also change the top node of the hierarchy view by selecting View From Here from the shortcut menu for the desired node. To revert to viewing the hierarchy from its true top node, right-click anywhere in the tree view and select View From Top. Hyperion System 9 Master Data Management Administration 2-11

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started Viewing Node Properties You view properties for the selected node in the Property Editor. The Property Editor can be displayed Docked at the right Docked at the bottom Undocked You can open only one Property Editor for each hierarchy. Properties are grouped by property categories that are displayed as tabs. Property categories Viewing Node Properties Properties are data elements that are associated with nodes; they enable Hyperion MDM to store extra information about each node. In addition to the set of default properties, which includes Name and Description, you can add as many properties as needed to support the subscribed systems. Property Editor The Property Editor enables you to examine and edit property values for the currently selected node. To access the editor, select a node and take one of the following actions Right-click and select Properties. Use the F11 keyboard shortcut. 2-12 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface The Property Editor is displayed either docked at the bottom, docked at the right, or undocked to the hierarchy window, based on the user preference defined under Tools > Options. When you change the current node in the hierarchy window, the corresponding node properties are automatically refreshed in the Property Editor. Only one Property Editor can be opened for each hierarchy window. Property Categories The Property Editor displays lists of properties categorized by a number of tabs, each of which each defines a property category. Each category represents a set of logically related properties that belong to a particular external system (for example, SAP or Essbase), or to a specific functional area within the company. Hyperion MDM provides the built-in property categories that are automatically available for nodes. For example, the System Property category groups properties related to a node s identifying characteristics, such as Node ID, Name, and Description. You can create as many property categories as needed. If the property name is bold, you have edit rights to the property. Hyperion System 9 Master Data Management Administration 2-13

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started Displaying Property Categories You can customize the display of property categories. Navigation buttons One line Multiple lines Access/Verification properties All properties Displaying Property Tabs By default the Property Editor displays property categories as tabs in one line. If the width of the Property Editor window cannot fit all property categories, then the editor displays arrow buttons that enable you to scroll the tabs right and left. You can configure the editor so that it displays tabs in multiple lines, which allows you select a tab with one click. As administrator, you can also configure the editor to display access/verification properties or all properties. 2-14 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 2 Navigating Hyperion MDM User Interface Summary In this lesson, you should have learned to: Launch the MDM NTier client and connect to Hyperion Master Data Management applications Manage login connections Navigate hierarchies View node properties Hyperion System 9 Master Data Management Administration 2-15

Lesson 2 Navigating Hyperion MDM User Interface Module 1 Getting Started 2-16 Hyperion System 9 Master Data Management Administration

L E S S O N 3 Working with Master Data 3 Objectives At the end of this lesson, you should be able to: Edit hierarchies and node properties Search for nodes Run property queries Perform hierarchy compares

Lesson 3 Working with Master Data Module 1 Getting Started Working with Hierarchies Node operations Insert Add Delete Copy Move Merge Node management tools Shortcut menu commands Drag-and-drop feature Working with Hierarchies Nodes are the building blocks of hierarchies. You maintain the structure of a hierarchy by inserting, adding, deleting, and moving nodes in the hierarchy window. You manage nodes by using menu commands or by using the drag-and-drop feature, which simplifies master data restructuring. 3-2 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Adding and Inserting Nodes Node names must be unique within a hierarchy. Geography Markets NA East CT NA West APAC Add NY Insert NA East CT NY Adding and Inserting Nodes Every node is uniquely identified by its name. Even though a node may be part of more than one hierarchy in the same version, the node cannot exist more than once in the same hierarchy. You add a node (limb or leaf) to the hierarchy in one of the following two ways: You can insert an existing node that is a part of the same hierarchy or another hierarchy. If you insert a node from the same hierarchy, then you must change its name so that it is unique in the hierarchy. You can create a new node. Hyperion System 9 Master Data Management Administration 3-3

Lesson 3 Working with Master Data Module 1 Getting Started To add a new node to a hierarchy: 1. Open the hierarchy to which you want to add a new node. 2. In the tree view, right-click the parent node for the new node and select Add Node. The Add Node dialog box is displayed. 3. Perform the following actions: In the Name text box, enter a name for the new node. If the node name exists in the version, then you are prompted to use the Insert Node dialog box. Optional: In the Description text box, enter a description for the new node. In the Add Node As area, select Limb or Leaf. Optional: In the Copy Properties area, select the node from which you want to copy properties. You can also select the properties that you want to copy from the selected node. Click Add. The new node is added to the hierarchy and is displayed in the tree view. To insert a new node in a hierarchy: 1. Open the hierarchy in which you want to insert a new node. 2. In the tree view, right-click the parent node for the new node and select Insert Node. The Insert Node dialog box is displayed. 3. Select the name of the new node by using one of the following methods: In the Name text box, enter the name of the node. If the node name does not exist in the version, then you are prompted to use the Add Node dialog box. Click [...] and select a node from an existing hierarchy. 4. Click Insert. The new node is added to the hierarchy and is displayed in the tree view. 3-4 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Moving Nodes Nodes can be moved only under valid limb nodes; they cannot be moved under leaf nodes. Geography NA East Take Markets NA West CT PA NY Put NA East CT NY PA Drag and drop Moving Nodes You can move nodes within the same hierarchy or to a new hierarchy. Moving a node within a hierarchy removes the node from its original parent and places it under the new parent. Moving a node to a different hierarchy is identical to inserting an existing node. To move a node, you can drag it onto its new parent node or use the Take and Put commands on the shortcut menu. 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 Hyperion System 9 Master Data Management Administration 3-5

Module 1 Getting Started Lesson 3 Working with Master Data Deleting Nodes Only nodes with no descendents can be deleted. Markets Orphan nodes Geography NA West Remove NA West NA East CA CA CT NA East NY CT Delete NA West NY Inactivate Insert CA Other APAC Japan Annul Japan Deleting Nodes There are four methods by which a node can be deleted. Delete Remove Annul Inactivate Removes the node from all hierarchies and deletes the node from the version. Removes the node from the current hierarchy and any other hierarchies in which it has the same parent. However, the node is not deleted from the version, so that it is available for later reinsertion. Removes the node from all hierarchies in which it has the same parent and then deletes the node if the node becomes an orphan. Flags the node as inactive so that it can be filtered from an export. The inactive node can be reactivated. 3-6 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Merging Nodes Merging nodes are used in place of deleted or inactivated nodes. Markets NA West CA NA East CT NY Merging Nodes Tracking merge information is a Hyperion MDM option that allows users to specify nodes that should be used in place of deleted or inactivated nodes. External transaction systems supported by Hyperion MDM may still have transactions that refer to the deleted node. By keeping a merge list, Hyperion MDM is able to feed these systems appropriate node mappings that allow them to move the data to a new valid node. As an administrator, you can configure the Use Merge methodology by setting the UseMerge system preference to TRUE. If the Use Merge methodology is enabled, then a wizard is displayed when the user deletes or inactivates a node. This series of forms ensures that valid merge nodes are selected for each deleted or inactivated node. Hyperion System 9 Master Data Management Administration 3-7

Lesson 3 Working with Master Data Module 1 Getting Started Searching for Nodes Find a node In the hierarchy In the version List orphan nodes Searching for Nodes Hierarchies can consist of hundreds of nodes, which makes it difficult to navigate to a particular branch or node by using the hierarchy window interface. Hyperion MDM provides powerful searching tools that enable you to quickly find desired nodes in the hierarchy or the entire version and then navigate to the nodes in the tree view. The simplest method of searching for nodes is to use the Find command. You can search for nodes in the selected hierarchy or perform a global search for nodes in any hierarchy within the selected version. 3-8 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Finding Nodes in a Hierarchy 1. Open a hierarchy 2. Select Edit > Find 3. Define the search criteria 4. Click Find Speed buttons for marked nodes Hotlist Marked nodes Finding Nodes in a Hierarchy The simplest method of searching for nodes in the hierarchy is to use the Find command. To find nodes in a hierarchy: 1. Open a hierarchy in which you want to find nodes. 2. Press Ctrl+F or select Edit > Find. 3. Perform the following actions: In the Search For text box, enter the string to be used as the search criterion. From the Search In drop-down list, select the search criterion property. Optional: Select the Perform Exact Match check box to restrict the search to exact matches to the value entered in the Search For text box. Hyperion System 9 Master Data Management Administration 3-9

Lesson 3 Working with Master Data Module 1 Getting Started In the Display Options section, select one of the following options: Show in Lists Mark Nodes Both Displays results in the form of a hot list Marks the nodes found in the hierarchy window Displays a hot list and marks the nodes Optional: Select the Select Go to First Node in List check box to automatically locate the first node in the search results and select it in the hierarchy window. 4. Click Find. Hyperion MDM performs the node search. If the search is successful, then the first node that matches the search criterion is selected in the tree view. You can find the next node that matches the search criterion by selecting Find > Next or pressing F3. If no node is found, then a notification message is displayed. 3-10 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Finding Nodes in a Version 1. Select a version 2. Select Edit > Global Find 3. Define the search criteria 4. Click Find Hierarchies Finding Nodes in a Version When you want to search for nodes across hierarchies, you use the Global Find command. To find nodes in a version: 1. In the Version Control window, select a version in which you want to find nodes. 2. Press Ctrl-G or select Edit > Global Find. 3. Perform the following actions: In the Search For text box, enter the string to be used as the search criterion. From the Search In drop-down list, select the search criterion property. 4. Click Find. Hyperion MDM performs the node search across all hierarchies in the version. If the search is successful, then the results are displayed in a hot list. The nodes are grouped in tabs, with one tab for each hierarchy in which the nodes are found. Hyperion System 9 Master Data Management Administration 3-11

Lesson 3 Working with Master Data Module 1 Getting Started Navigating Hot Lists The hot list enables you to jump from any node in the list to that node in its hierarchy. Save to File Hot list Hierarchy window Navigating Hot Lists A hot list is a list of nodes returned as a result of a node search. The hot list enables quick navigation 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 window displays a tab for each hierarchy. Hot lists can be saved to a file or printed. For the example shown in the slide, the saved hot list looks like the following sample: 1) Find - 'Statistics' (9) ------------------------ Name Description Links Capital Expenditures CapExBuildings 3-12 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data CapExCompEquip CapExCompSftwr CapExLand CapExLsholdImprov CapExMfgMach CapExOffFurn CapExVehicles ------------------------ 2) Find - 'Category' (2) ------------------------ Name Description Links Capability Capacity ------------------------ Hyperion System 9 Master Data Management Administration 3-13

Lesson 3 Working with Master Data Module 1 Getting Started Listing Orphan Nodes To list orphan nodes: 1. Select a version 2. Select List > Orphan Nodes To list orphan node s descendants: 1. Select an orphan node 2. Right-click and select View Structure Descendants of Scenarios are not orphan nodes. Listing Orphan Nodes Orphan nodes within a version can be viewed by right-clicking a version in the Version Control window and selecting List > Orphan Nodes. A hot list of orphan nodes is displayed. You can add an orphan node to a hierarchy by doing one of the following: Insert a node and type the name of orphan node Drag an orphan from the orphan node hot list into the hierarchy It is possible for an orphan node to have descendants that are not orphans. To avoid this, you should review the list of orphan nodes regularly. Right-click each orphan in the hot list and select View Structure to display a list of the orphan node's descendants. 3-14 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Analysis Tools Property Query Tools Property Query Global Property Query Comparison Tools Compare Property Compare Renamed Node Compare Analysis Tools Hyperion MDM NTier client includes powerful analysis tools that enable you to investigate hierarchy structures and the property values of sets of nodes without the need for complex recursive programming. Property Query Tools Property query tools support a number of operators such as LIKE, IN, and LENGTH. You can create a query criteria similar to the WHERE clause in a conventional SQL statement and run the query against a set of nodes. Property query tools return 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. Hyperion System 9 Master Data Management Administration 3-15

Lesson 3 Working with Master Data Module 1 Getting Started MDM NTier client offers two property query tools: Property Query This tool enables you to define and run queries against a node and its descendants within a hierarchy. You can run a property query from the top node of a hierarchy or from a node within the hierarchy. The query can reference all properties. Global Property Query This tool enables you to define and run queries 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. You can save the property query and develop a tool kit of queries so that other users can use it. An administrator can create standard queries and make them available for use by all users. NOTE You can also use property queries as a filtering mechanism in exports and comparisons. Comparison Tools Comparison tools enable you to analyze the structure and node properties of different hierarchies and versions. A typical business scenario is an organization that has structured cost centers by both functional business area and by geographic location. In this case, the organization wants to ensure that all cost centers are mapped into both structures. MDM NTier client offers three comparison tools: Compare This tool compares structures of two hierarchies for similarities or differences. Property Compare This tool looks for similarities (or differences) of a property in two hierarchies. Renamed Node Compare Similar to the Compare tool, this tool compares structures of two hierarchies, but it treats renamed nodes as being the same for comparison purposes. 3-16 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Running Property Queries Running Property Queries Property queries return a list of nodes that meet certain criteria. You define the criteria interactively by using the Property Query tool. You can save the property query and develop a tool kit of queries that you can share with other users. And you can create standard queries and make them available to all users. NOTE You can also use property queries as a filtering mechanism in exports and comparisons. To run a new property query: 1. Select Tools > Property Query. The Property Query dialog box is displayed. Hyperion System 9 Master Data Management Administration 3-17

Lesson 3 Working with Master Data Module 1 Getting Started 2. In the Query Origin area, select the version and hierarchy. 3. In the Criteria area, click Add to create a search criterion. The Property Query Item dialog box is displayed. 4. Define the search criteria by setting the controls and then click OK. For example, select # Children from the Query Attribute list and type 2 as the value. 5. Optional. Select the Options tab and define property query options. The Options tab of the Property Query dialog box contains the following options: Option Include Match and Parents Include Match and Children Include Match Only Show in list Mark nodes Both Function Returns all nodes that meet the search criterion and their ancestors Returns all nodes that meet the search criterion and their descendants Returns only nodes that match the search criterion (the default behavior) Returns a hot list of nodes that meet the search criterion Marks nodes that meet the search criterion in the hierarchy Returns a hot list of nodes and marks them in the 6. Optional. Click Save or Save As to save the property query. 7. Click OK. The hot list displays nodes that meet the search criterion. 3-18 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Comparing Hierarchies The Compare and Renamed Node Compare tools analyze two hierarchies for structural differences. Version: February 2006 Markets Version: March 2006 Markets Differences EMEA Europe Compare tool NA Central NA West APAC Renamed Node Compare tool NA East CT NY NA East CT NY Similarities Comparing Hierarchies You identify structural changes that have been made in hierarchies by running the Compare and Renamed Node Compare tools. For example, you want to compare the same Market hierarchy from two versions: February 2006 and March 2006. If you run the Renamed Node Compare tool, it returns a hot list of nodes that are different in each hierarchy (NA Central for Markets in February 2006; NA West and APAC for Markets in March 2006) excluding those nodes that have been renamed (EMEA was renamed to Europe). If you run the Compare tool, it returns a hot list of all nodes that are different in the two hierarchies. Hyperion System 9 Master Data Management Administration 3-19

Module 1 Getting Started Lesson 3 Working with Master Data Comparing Properties The Property Compare tool analyze nodes for property value differences. Version: February 2006 Markets Version: March 2006 Markets EMEA Europe Resulting node list Property Node ID Name Value 238 EMEA Property Node ID Name Value 238 Europe Join property Selected property Comparing Properties You identify changes to specific properties that occurred in nodes by running the Property Compare tool. To analyze particular properties, you select them in the Properties tab. You also need to define a join property that selects nodes whose properties you want to analyze. For example, if you want to retrieve a list of nodes that were renamed, you select Node Id for Join property and Name as Selected property. The resulting node list is displayed in the form of a hot list. 3-20 Hyperion System 9 Master Data Management Administration

Module 1 Getting Started Lesson 3 Working with Master Data Summary In this lesson, you should have learned to: Edit hierarchies and node properties Search for nodes Run property queries Perform hierarchy compares Hyperion System 9 Master Data Management Administration 3-21

Lesson 3 Working with Master Data Module 1 Getting Started 3-22 Hyperion System 9 Master Data Management Administration

M O D U L E 2 Managing Hyperion MDM Applications 3 Overview Multiple applications are required in a typical Hyperion MDM implementation. The lessons in this unit introduce you to how to create a new Hyperion MDM application and define its structure. Lessons in this module include: Hyperion MDM Architecture Creating and Configuring Hyperion MDM Applications Building the Master Data Structure Managing Properties Setting Up Node Types Implementing Business Rules

L E S S O N 4 Hyperion MDM Architecture 4 Objectives At the end of this lesson, you should be able to: Describe Hyperion System 9 Master Data Management NTier architecture Identify Hyperion MDM components Describe Hyperion MDM users and authentication modes Describe Hyperion MDM Web architecture

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications Hyperion MDM NTier Architecture Hyperion MDM incorporates a powerful NTier architecture to manage master data across enterprise applications. The NTier architecture enables the bulk of data processing to be performed on a centralized application server, which simplifies requirements for client applications. The diagram in the slide provides a high-level view of the information flow between the master data and the product components. Client applications connect to an MDM application server that receives and executes client requests through MDM engines. NTier architecture enables you to distribute the work load by separating Web server and application server on different computers. For maximum scalability, you can also distribute the MDM engines across multiple application servers. A database that stores master data can be hosted on the application server or elsewhere on the network. 4-2 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 4 Hyperion MDM Architecture Client Tier Client applications enable you to connect to the MDM application server and perform administrative and management tasks on the master data. These clients include: MDM NTier Client: The business user and administrator interface to Hyperion MDM MDM Connect: A command line utility to run processes in batch mode MDM API: Application programming interface to Hyperion MDM that enables developers to create customized applications by using the C++ programming language Middle Tier Hyperion MDM middle-tier components include Web server, application server, and data access layer. Web Server MDM clients connect to the MDM application server through the Web server by using Simple Object Access Protocol (SOAP) over HTTP or HTTPS. The Web server is implemented as Internet Information Services (IIS), providing scalable, secure, and manageable Web server capabilities. The Web server requires: Windows 2000 (Service Pack 3 or later), Windows XP, or Windows 2003 Server Internet Information Services version 5 or later Microsoft Data Access Components (MDAC) 2.7 or later Application Server The Hyperion MDM application server is built on component technology that uses Component Object Model to support communication among objects on different computers. Data Access Layer The data access layer (DAL) stores information that is necessary for connecting to multiple MDM databases. The DAL is configured and managed implicitly from the Hyperion MDM Console. Database Tier The Hyperion MDM database requires a processor of 500 Mhz or faster (dual processors are recommended) and at least 512 MB of RAM. The database can be created using one of the following RDBMS servers: Microsoft SQL Server 7.0 or later or Oracle 8i or later. Hyperion System 9 Master Data Management Administration 4-3

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications Users Administrators Can have three levels: System Admin Functional Admin Security Admin Perform administrative functions Business users Must be granted access to master data Perform nonadministrative functions Users The control of access and functional privileges in Hyperion MDM is implemented with multiple levels of users. Administrators Hyperion MDM provides three administrative levels that enable targeted allocation of MDM privileges across the organization: System Admin: Has access to all administrative functions in Hyperion MDM, including access to all versions, all hierarchies, and all nodes within hierarchies, limited only by the version status of Finalized and Expired. System Admins are not limited by node access groups or property categories. 4-4 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 4 Hyperion MDM Architecture Functional Admin: Does not have access to any of the administrative functions in Hyperion MDM except for properties. Has read-only access to all property information except for lists and lookup tables. Functional Admins have access to all versions, all hierarchies, and all nodes within hierarchies, limited only by the version status of Finalized and Expired. Security Admin: Does not have access to any of the administrative functions in Hyperion MDM except for user management. Security Admins have read-only access to all versions, all hierarchies, and all nodes within hierarchies. Business Users Business users have access to nonadministrative functions. They must be granted access to nodes and properties. All users are assigned access to the Hyperion MDM database. The username used for this access is also used to control security within Hyperion MDM. Hyperion System 9 Master Data Management Administration 4-5

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications User Authentication Modes Hyperion MDM security supports three user authentication modes: Internal: Hyperion MDM External: Hyperion Shared Services NTLM LDAP MSAD Mixed: Based on individual user settings User Authentication Modes Hyperion MDM users can be authenticated internally (within Hyperion MDM) or externally (via an authentication repository). It is also possible to configure user authentication externally or internally based on individual user settings. Internal authentication is the default authentication mode; it includes enhanced password and user controls. This mode is used in earlier Hyperion MDM releases. External authentication means that the user login information needed by Hyperion applications is stored outside the applications. The information is maintained in a central authentication directory, such as Lightweight Directory Access Protocol (LDAP) Directory, Microsoft Active Directory (MSAD), or Windows NT LAN Manager (NTLM). 4-6 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 4 Hyperion MDM Architecture An authentication directory is a centralized store of user information such as login names and passwords, and perhaps other corporate information. The repository functions like a telephone directory. The authentication directory usually contains more than user names and passwords; for example, it may include e-mail addresses, employee IDs, job titles, access rights, and telephone numbers. It may also contain objects other than users; for example, it may contain information about corporate locations or other entities. In order to use external authentication for Hyperion applications, your organization must have an authentication directory that contains corporate user information. Additionally, you must modify the XML-based security configuration file that is associated with your product to specify correct information pertaining to your corporate authentication directory. The following types of authentication repositories are supported: Windows NT LAN Manager on NT 4.0 or later, Windows 2000, and Windows 2003 Lightweight Directory Access Protocol version 3 or later Microsoft Active Directory server, Windows 2000 sp3 or later Hyperion System 9 Master Data Management Administration 4-7

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications Hyperion MDM Web Architecture The Hyperion MDM Web Publishing module provides additional means of accessing Hyperion MDM functionality. The module 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 The Hyperion MDM Web Publishing module operates in read-only mode. Requests can be made by using HTTP either to retrieve information or to execute a command such as running exports or reloading from the database. 4-8 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 4 Hyperion MDM Architecture The Hyperion MDM Web Publishing module employs a Web-based user interface and runs on a Web server. The module uses an ActiveX control that can run only on Windows operating systems. NOTE Although Microsoft Internet Explorer can be run on a Macintosh computer, it cannot run ActiveX controls. Although some versions of Netscape (on Windows) have ActiveX support, use of Hyperion MDM Web Publishing in a Netscape configuration is not supported at this time. Hyperion System 9 Master Data Management Administration 4-9

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications Configuring Web Access Hyperion MDM Web Client communicates with the RDBMS of the MDM application using Hyperion Master Data Management Server Data Access Layer (DAL). The user profile that the Hyperion MDM Web engine uses to communicate with the MDM aplication to publish master data to the Web, must be defined in both the RDBMS hosting the MDM application and Hyperion NTier Client. To configure DAL: 1. Select Start > All Programs > Hyperion Solutions > Hyperion Master Data Management > Data Access Layer Configuration. The Hyperion MDM DAL Conficguration window is displayed. 2. Select Local Machine. 4-10 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 4 Hyperion MDM Architecture 3. Select the default DAL connection created by the installation utility that is specific to the RDBMS of the host machine (MDM_Web_MSSQL or MDM_Web_Oracle). 4. Right-click and select Clone Connection. 5. Edit the connection details as necessary by entering values for the following connection parameters: DatabaseName Password ServerName UserName 6. Select File > Save Registry. 7. Select File > Exit. Hyperion System 9 Master Data Management Administration 4-11

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications Launching Hyperion MDM Web Client Launching Hyperion MDM Web Client After you install and configure Hyperion MDM Web Client, end users can access master data in read-only mode by entering the following URL into a supported browser: http://webserver_hostname/mdm_web All end users can view the same master data when they launch the Hyperion MDM Web client. The master data that end users can access is determined by the access privileges that you grant to the Hyperion MDM Web user and the system preferences settings that apply to Hyperion MDM Web Server. NOTE For more information on installing and configuring Hyperion MDM Web Server refer to Hyperion Master Data Management Server Web Publishing Module. 4-12 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 4 Hyperion MDM Architecture Summary In this lesson, you should have learned to: Describe Hyperion MDM NTier architecture Identify Hyperion MDM components Describe Hyperion MDM users and authentication modes Describe Hyperion MDM Web architecture Hyperion System 9 Master Data Management Administration 4-13

Lesson 4 Module 2 Hyperion MDM Architecture Managing Hyperion MDM Applications 4-14 Hyperion System 9 Master Data Management Administration

L E S S O N 5 Creating and Configuring Hyperion MDM Applications 5 Objectives At the end of this lesson, you should be able to: Create Hyperion MDM applications Configure Hyperion MDM applications Configure system preferences

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Creating Hyperion MDM Applications Hyperion MDM stores master data, including the information that it needs to manage master data, in a relational database that is referred to as the MDM application. As part of the Hyperion MDM installation, the installer creates the initial Hyperion MDM application in either a Microsoft SQL Server or an Oracle relational database. The first time you run the installer on a Microsoft Windows computer and perform a complete installation, the following components are installed and configured: Web Server MDM Application Server Initial Hyperion MDM application To start the installer, you run mdm_server_setup.exe. The installer creates the initial Hyperion MDM application by installing and executing SQL scripts. these scripts are saved in the C:\Hyperion\Master Data Management Services\Database directory: 5-2 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications Creating Hyperion MDM Applications on Microsoft SQL Server Automatically: 1. Stop the Hyperion MDM service and processes 2. Modify SQL Server Create Database.sql 3. Run mdm_server_setup.exe Manually: 1. Create a MS SQL Server database 2. Execute database scripts Creating Hyperion MDM Applications on Microsoft SQL Server When you select to create the initial Hyperion MDM application in Microsoft SQL Server, the installer prompts you to specify the name of the database. The default name is MDM. You also specify the names of the database file and log file. The default names of these files are: mdm_data.mdf mdm_log.ldf The installer creates the initial MDM application by executing several Microsoft SQL Server scripts in the following order: 1. SQL Server Create Database.sql 2. SQL Server Build.sql 3. SQL Server Build Stored Procs.sql Hyperion System 9 Master Data Management Administration 5-3

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications 4. SQL Server MDM Role Setup.sql 5. SQL Server Import Table Section Init.sql 6. SQL Server Init.sql 7. SQL Server MDM Init.sql 8. SQL Server Set AuthMethod.sql It is possible to have multiple Hyperion MDM applications to support the different needs for master data in an organization. You can create additional Hyperion MDM applications by using one of the following methods: Automatically by repeatedly running the installer program Manually by running the SQL scripts that are installed during the Hyperion MDM installation To create a Hyperion MDM application automatically: 1. Stop the Hyperion MDM service and processes. 2. Modify the SQL Server Create Database.sql script by changing the database name, database file name, and log file name. 3. Run mdm_server_setup.exe. To create a Hyperion MDM application manually: 1. Launch SQL Query Analyzer. 2. Log in as system administrator. 3. Open the SQL Server Create Database.sql script and modify it by changing the database name, database file name, and log file name. 4. Run the script against the master database. 5. Open and run the remaining scripts, in the order in which they are listed in the previous section, against the database that was created in step 4. 5-4 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications Configuring Hyperion MDM Applications Connection A (default) MDM Application A Connection B MDM Client MDM Application Server MDM Application B MDM Services Console Configuring Hyperion MDM Applications You use Hyperion MDM Services Console a component of Hyperion MDM Application Server to configure and manage Hyperion MDM applications. From the console, you can perform the following tasks: Monitor servers Configure database connections Configure Common Security Services (CSS) Configure server setup Start and stop Hyperion MDM services and processes Import registry settings (available only for upgrades to version 9.0) Hyperion System 9 Master Data Management Administration 5-5

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Navigating Hyperion MDM Services Console Navigation controls: Server Monitor Configuration Navigating Hyperion MDM Services Console Hyperion MDM Services Console includes a navigation control panel located on the left side of the user interface. This panel contains two areas: Server Monitor Configuration From the Server Monitor area, you can perform the following actions: Start, stop, and view the status of Hyperion MDM Services View server information, including operating system, COM+ components, and out-ofprocess application information View engine status, including user sessions, versions, and event queues View the event log for Hyperion MDM Services events From the Configuration section, you can perform the following actions: Configure database connections Manage system preferences Enable Common Security Services 5-6 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications Starting and Stopping the Hyperion MDM Service and Processes Starting and Stopping the Hyperion MDM Services and Processes You use the Local Machine page in Hyperion MDM Services Console to start and stop the Hyperion MDM service and processes. The following table shows the shortcut buttons and describes the task that is performed when you click each button. Starts the MDM service Stops the MDM service Stops and restarts the MDM service Stops the MDM service and forces all processes to shut down Hyperion System 9 Master Data Management Administration 5-7

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Adding Database Connections Adding Database Connections You use Hyperion MDM Services Console to manage Hyperion MDM applications. For each application you define a different database connection. To add a database connection: 1. Click the Database Settings link. The Connections tab is displayed. 2. Click New Item. 3. In the Connection Name text box, enter a name for the connection. 4. In the Database Type area, select SQL Server or Oracle. 5. In the Connection Parameter area, enter the server and database names. 6. In the Engine Login area, enter the username mdm_system and the password razza. 7. In the Database Login area, enter the username mdm_db and the password razza. 8. Click Save Changes. 5-8 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications Setting the Default Database Connection Setting the Default Database Connection The default connection determines the Hyperion MDM application that users connect to when they log in to Hyperion MDM NTier Client. To set the default database connection: 1. On the Connections tab of the Database Settings page, select the database connection name. 2. Select the Default Connection check box. 3. Click Save Changes. 4. Click the Local Machine link. 5. Stop and restart the Hyperion MDM service and processes. Hyperion System 9 Master Data Management Administration 5-9

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Configuring Hyperion MDM Authentication Authentication methods Internal authentication policies Configuring Hyperion MDM Authentication You configure authentication at the application level from the System Preferences tab of Hyperion MDM Services Console. From this tab, you can switch between different authentication methods and you can select settings for internal authentication policies. Before you can access the System Preferences tab, you need to connect to a Hyperion MDM application. To connect to an MDM application: 1. In the navigation panel, click the Database Settings link. The Connection tab is displayed. 2. Select the database connection for the application that you want to configure. 5-10 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications 3. Click Connect. The Verify Database Password dialog box is displayed. 4. Enter the password for the database user mdm_db (the default password is razza). 5. Click OK. A confirmation message window is displayed. 6. Click OK. Hyperion System 9 Master Data Management Administration 5-11

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Configuring Authentication Methods Internal Common Security Services Mixed Configuring Authentication Methods The Hyperion MDM Services security model includes three methods for authenticating users: Internal: User authentication is managed internally by Hyperion MDM. Common Security Services: User authentication is managed by Hyperion Shared Services and user login information is maintained in a central authentication directory, such as Lightweight Directory Access Protocol (LDAP), Microsoft Active Directory (MSAD), or Windows NT LAN Manager (NTLM). Mixed: System and security administrators can assign either of the previous authentication methods to Hyperion MDM users. You can use the System Preferences tab on the Database Settings page to configure the authentication method at the application level. 5-12 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications To set the authentication method for an application: 1. From the Connections tab of the Database Settings page, select a connection and connect to the application. 2. Select the System Preferences tab. 3. From the Authentication area, select an authentication method. 4. Click Save Changes. 5. Stop and restart the Hyperion MDM service and processes. Hyperion System 9 Master Data Management Administration 5-13

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Configuring Internal Authentication Policies Password Settings Lockout Settings Configuring Internal Authentication Policies When you select the internal authentication method, you also configure internal authentication policies by specifying password settings and lockout settings. You can specify values for the following parameters in the Password Settings area: Expiration Period: Number of days before user passwords expire Maximum Length: Maximum length for user passwords (zero indicates no maximum) Minimum Length: Minimum length for user passwords (zero indicates no minimum) Warning Period: Number of days before (negative value) or after (positive value) passwords expire, when users are warned to change their password In the Lockout Settings area, you can exclude specific users from automatic login lockouts. 5-14 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications Exclude Functional Admin: Excludes users with Functional Admin privileges Exclude Security Admin: Excludes users with Security Admin privileges Exclude System Admin: Excludes users with System Admin privileges Excluded User List: Excludes the users specified in the list Inactivity Threshold: Maximum number of inactive days before users are locked out (zero indicates no maximum) Invalid Logins Allowed: Maximum number of invalid login attempts before users are locked out (zero indicates no maximum) Hyperion System 9 Master Data Management Administration 5-15

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Configuring Common Security Services Configuring Common Security Services You configure Common Security Services (CSS) from the Common Security Services page of Hyperion MDM Services Console. There are two main parameters that you need to configure on this page, host name and port number. They are the name of the machine where Hyperion Shared Services is installed and the port number assigned to Hyperion Shared Services on that machine. Two additional parameters are Alternate URL and the Use Alternate option, which you can use to point to a backup CSS server. TIP Do not modify the Classpath Root parameter or the contents of the System Path and Class Path areas unless you fully understand the impact of the changes that you make. 5-16 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications Enabling Common Security Services To complete the Hyperion MDM installation, you need to configure external authentication and enable Common Security Services. To enable Common Security Services: 1. On the Common Security Services page of Hyperion MDM Services Console, click Enable CSS. 2. Click OK. A confirmation message is displayed. 3. Stop and restart the Hyperion MDM service and processes. Hyperion System 9 Master Data Management Administration 5-17

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Configuring System Preferences Configuring System Preferences In the System Preferences dialog box, you can edit settings that control the behavior of Hyperion MDM. To access this dialog box, you need to log in to Hyperion MDM NTier Client with administrative privileges. To edit system preferences parameters: 1. From the main menu of the Hyperion MDM NTier Client window, select Admin > System Preferences. 2. From the Current drop-down list, select a system preference. The parameters of the system preference that you selected are displayed. 3. Edit the parameter values. 5-18 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 5 Creating and Configuring Hyperion MDM Applications To search for system preferences: 1. In the System Preferences dialog box, click Search. The Find System Preference dialog box is displayed. 2. In the Search For text box, type a search string. 3. From the Search In drop-down list, select a system preference item: - Name - Label - Value - Description 4. Click Find. Available System Preferences For the available system preferences and their descriptions, see the NTier Administrator s Guide, Chapter 2, Getting Started. Hyperion System 9 Master Data Management Administration 5-19

Lesson 5 Module 2 Managing Hyperion MDM Applications Creating and Configuring Hyperion MDM Applications Summary In this lesson, you should have learned to: Create Hyperion MDM applications Configure Hyperion MDM applications Configure system preferences 5-20 Hyperion System 9 Master Data Management Administration

L E S S O N 6 Building the Master Data Structure 6 Objectives At the end of this lesson, you should be able to: Work with versions Manage hierarchies

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Working with Versions Create and save versions Manage version life cycles Copy to a new version Delete versions Working with Versions A version represents a single, independent set of data that is arranged into related hierarchies. All master data management maintenance is performed within a single version. Managing hierarchies in Hyperion Master Data Management includes the following tasks: Create and save versions Manage version life cycles Copy to a new version Delete versions 6-2 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure Creating Versions Creating Versions When you create a new application, an empty version named Initial Version is created by default with its status set to Submitted. To set up the initial environment in a Hyperion MDM application, you create a new empty version. To create a new version: 1. In the Version Control window, right-click Initial Version and select New > Version. The Add Version dialog box is displayed. 2. In the Abbrev text box, type a name for the new version. 3. Optional: In the Description text box, type a description. 4. Click OK. The new version is added to the Version Control window. Hyperion System 9 Master Data Management Administration 6-3

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Saving Versions Saving Versions When you create a new version, Hyperion MDM creates a detached working version. Detached versions are not saved to the MDM application and are displayed with red text in the Version Control window. To save a version: 1. In the Version Control window, right-click the version name and select Save. The Confirm Action dialog box is displayed. 2. Select the Check here to confirm this action check box, and then click OK. The version is saved to the database. 6-4 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure Applying Life-Cycle Management to Versions Applying Life-Cycle Management to Versions To control the workflow of hierarchy maintenance, you can change the version status. To change the version status: 1. In the Version Control window, right-click the version name and select Properties. The version s properties dialog box is displayed. 2. On the System tab, select a value for the Version Status property. [Modified] is displayed in the status column. 3. Click Save. Hyperion System 9 Master Data Management Administration 6-5

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Copying to a New Version Copying to a New Version New versions are typically created from existing versions to support two business scenarios: To create a new working version when the current working version is finalized as part of the master data life cycle To create a separate version for "what if" scenarios, future reorganizations, or future planning To create a new version as a copy: 1. In the Version Control window, right-click the source version and select Copy to New. The Copy Version dialog box is displayed. 2. Perform the following actions: 6-6 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure In the Abbrev text box, enter a name for the new version. Optional: In the Description text box, enter a description of the new version. 3. Click OK. The new version is added to the Version Control window. 4. Right-click the version name and select Save. The Confirm Action dialog box is displayed. 5. Select the Check here to confirm this action check box and then click OK. The version is saved to the database Hyperion System 9 Master Data Management Administration 6-7

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Deleting Versions Deleting Versions The database that stores master data is very sparse in its storage, but if it contains numerous versions, large master data structures, or both, you may want to completely remove older versions that are no longer needed to free up database storage space. To delete a version: 1. In the Version Control window, right-click the version and select Delete. The Confirm Action dialog box is displayed. 2. Select the Check here to confirm this action check box and then click OK. The version is deleted from the database. 6-8 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure Managing Hierarchies Adding hierarchies Creating system categories Assigning hierarchies to system categories Editing hierarchy properties Deleting hierarchies Managing Hierarchies Hierarchies are contained in a version, and a single version may contain multiple hierarchies. Each hierarchy is usually associated with a certain view, external system, or management report. The slide list includes the tasks that you need to perform to manage hierarchies. Hyperion System 9 Master Data Management Administration 6-9

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Adding Hierarchies Adding Hierarchies A hierarchy is a logical set of nodes within a version. The nodes that make up a hierarchy are all descendants of a single top node. Therefore a hierarchy is defined by its top node and represents all the nodes in the hierarchical relationships below that node. To add a hierarchy: 1. In the Version Control window, right-click the version in which you want to create a new hierarchy and select New > Hierarchy. The Add Hierarchy dialog box is displayed. 2. In the Hierarchy area, perform the following actions: In the Hierarchy Name text box, type a name for the new hierarchy. In the Hierarchy Description text box, type a description of the new hierarchy. 6-10 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure 3. In the Top Node area, perform the following tasks: Select the Create New Top Node check box. In the Name text box, type the name of the top node for the new hierarchy. Optional: In the Description text box, enter a description of the top node of the new hierarchy. 4. Click OK. The new hierarchy is added to the version tree in the Version Control window. Hyperion System 9 Master Data Management Administration 6-11

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Creating System Categories Creating System Categories You can group hierarchies into system categories within a version. Non-empty system categories are displayed in the Version Control window as folders. You create system categories by using the System Categories dialog box. To create a system category: 1. From the main menu, select Admin > System Categories. The System Categories dialog box is displayed. 2. On the dialog box toolbar, click (Create New System Category). The New System Category dialog box is displayed. 3. In the Category Name text box, type a name for the new system category and then click OK. 4. Optional: To close the System Categories dialog box, click OK. 6-12 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure Assigning Hierarchies to System Categories 1 2 3 4 Assigning Hierarchies to System Categories When you create a system category, it does not initially contain any hierarchies. Therefore, if you close the System Categories dialog box, the system category folder is not added to the version tree in the Version Control window. To assign hierarchies to a system category: 1. In the System Categories dialog box, select a version name from the Version dropdown list. The hierarchies included in the version are displayed in the Available area. 2. Press the Ctrl key and then select the hierarchy names that you want to assign to a system category. Hyperion System 9 Master Data Management Administration 6-13

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications 3. Click the add button. The hierarchies that you selected are added to the Selected area. NOTE Hierarchies that are members of another system category, have their system category value displayed in braces ([ ]) next to the hierarchy name. Because a hierarchy can belong to only one system category, assigning a hierarchy to the current system category removes its previous assignment. 4. Click OK. 5. Optional: From the main menu, select View > Refresh All. NOTE When you assign hierarchies to system categories, the results are not automatically displayed in the version tree in the Version Control window. 6-14 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure Editing Hierarchy Properties Editing Hierarchy Properties Hierarchy properties are defined at the hierarchy level and are the same for all nodes in the hierarchy. You can also assign a hierarchy to a system category by setting the Hier System Category system property for the specified hierarchy in the Property Editor. The following table describes the predefined hierarchy properties: Hierarchy Property Hier ID Hier Name Hier Descr HierarchyNodetype Description 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 of a certain node type Hyperion System 9 Master Data Management Administration 6-15

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Hierarchy Property Hier Sort Hier Sort Order Hier System Category DefaultDisplayBy PrifillLeafProp PrefillLimbProp StandardHierSort Top Node Top Node ID UserDisplayBy UserHierSort UserHierFilter Description Shows the 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 Points to the node-level property that is used to prefill the node name when creating new leaf node Points to the node-level property that is used to prefill the node name when creating new limb node Points to a node-level property that is used 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 are displayed for the current user Points to a node-level property to determine sort order within the hierarchy for the current user Determines how the hierarchy is filtered for the current user 6-16 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 6 Building the Master Data Structure Saving and Deleting Hierarchies Saving Hierarchies You do not need to explicitly save changes that you make in the hierarchy structure. Changes are automatically saved to the database. Deleting Hierarchies When you delete a hierarchy, only its structure is deleted from the database. The hierarchy nodes that are not a part of another hierarchy become orphan nodes at the version level. The orphan nodes can be either reassigned to another hierarchy within the version or completely removed from the version. To delete a hierarchy: 1. In the Version Control window, right-click the hierarchy and select Delete. The Confirm Action dialog box is displayed. 2. Select the Check here to confirm this action check box and then click OK. The hierarchy structure is deleted from the database. Hyperion System 9 Master Data Management Administration 6-17

Lesson 6 Module 2 Building the Master Data Structure Managing Hyperion MDM Applications Summary In this lesson, you should have learned to: Work with versions Manage hierarchies 6-18 Hyperion System 9 Master Data Management Administration

L E S S O N 7 Managing Properties 7 Objectives At the end of this lesson, you should be able to: Describe Hyperion Master Data Management properties Create property categories Create properties Define formulas

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Hyperion MDM Properties Overview Property definition levels Inheritance Property categories Built-in properties and property categories User-defined properties Hyperion MDM Properties Overview Master data properties are data elements. They are the main components of a Hyperion MDM application, and they are similar to database fields. Properties are used to describe hierarchy nodes based on specific characteristics of the external systems in which they belong; to categorize nodes within hierarchies according to business functions; and to define security rules. Properties are grouped into categories. The system administrator creates properties, groups them into categories, and assigns security rules to them. 7-2 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Property Definition Levels The property level defines the scope of the property. A property can be defined at each of the following levels: Version Hierarchy Global Node Local Node Property Definition Levels In Hyperion MDM, properties can be defined and stored at four levels. Most properties are defined at the node level and contain information that describes the node; for example, name, description, and number of children. You can create properties at the version and hierarchy levels to meet organization or process needs. For example, you might create a property for hierarchies that identifies the external systems for which the hierarchies are valid. Properties at the version and hierarchy level are less common than properties at the node level. Hyperion System 9 Master Data Management Administration 7-3

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Local Versus Global Properties Local properties can have different values in different hierarchies. Global properties have the same value in all hierarchies. Income Expenses Net Income Total Expenses Sales Salaries Cost of Sales Operator: Subtract Account Type: Expense Cost of Sales Operator: Add Account Type: Expense Operator is a Local property. Account Type is a Global property. Local Versus Global Properties A local property for a node can have different values in different hierarchies in which the node occurs. A global property for a node has the same value in all hierarchies in which the node occurs. Updating the value for a global property for a node in one hierarchy updates that property value in all the other hierarchies in which the node occurs. For the example in the slide, Operator is a local property and Account Type is a global property. The Operator property value for the Cost of Sales node is Subtract in the Income hierarchy and Add in the Expenses hierarchy. The Account Type property value for the Cost of Sales node is Expense in both the Income hierarchy and the Expenses hierarchy. 7-4 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Inheritance Descendant nodes inherit values for a property from an ancestor. Locking a property at a parent node prevents its descendant nodes from modifying the inherited value for that property. Currency property set to Euro Descendants of Europe inherit Euro as value for Currency property Currency property set to GBP, overriding inherited value Descendants of United Kingdom inherit GBP for Currency property Inheritance Inheritance is a feature that allows high-level nodes to share property values with lower points in the hierarchy. This eliminates the need to store and maintain redundant information. When you define a property as inheriting, the values of the property cascade down to its descendants. Proper use of inheritance enhances the referential integrity of your application and reduces maintenance requirements. When determining the value of inheritable properties, the following rules apply: 1. If you directly enter a value at the current node, the entered value is used. 2. If you do not enter a value at the current node, the property value of the first ancestor node (moving up the hierarchy) is used. 3. If no ancestor has an entered value, the default value is used. Hyperion System 9 Master Data Management Administration 7-5

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Global Properties and Inheritance You must select a controlling hierarchy for properties defined as both global and inheriting. Controlling hierarchy Revenue Accounts Taxable Accounts Total Revenue Account Type: Income Services Account Type: Income Total Taxable Services Account Type: Expense Account Type: Income Account Type is a global and inheriting property that can take different values in different hierarchies. Global Properties and Inheritance Because a node can have different ancestors in different hierarchies, determining the value of global and inherited properties requires additional considerations. When you configure a property that is defined as both global and inheriting, you must specify a controlling hierarchy for the property. If a node exists in multiple hierarchies, the value inherited from the node s ancestor (or ancestors) in the controlling hierarchy determines the value for that property in all hierarchies in which the node occurs. For the example in the slide, the Account Type property is defined as both global and inheriting. Revenue Accounts is specified as the controlling hierarchy for the Account Type property. In the Revenue Accounts hierarchy, the Services node inherits the value Income for the Account Type property from its ancestor, Total Revenue. Because Revenue Accounts is specified as the controlling hierarchy, the Services node in the Taxable Accounts hierarchy also inherits Income as the Account Type property value. 7-6 Hyperion System 9 Master Data Management Administration

Essbase Planning Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Property Categories Are created by the system administrator Enable grouping of properties Are used to control security privileges Property Categories Property categories are used to group related properties such as properties that belong to a particular external system (for example, Essbase, Planning, Oracle, or SAP), or a specific functional area within a company. Property categories are created by the system administrator according to the specific master data needs of an organization. Property categories are also used to control security privileges. The system administrator can restrict user access to specific property categories. Hyperion System 9 Master Data Management Administration 7-7

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Creating Property Categories Creating Property Categories You create property categories from the Property Categories window. To create a property category: 1. From the menu bar, select Admin > Property Categories. The Property Categories window is displayed. 2. On the toolbar, click the (Create New Property Category) button. The New Property Category dialog box is displayed. 3. In the Property Category Name text box, type a name for the new property category and then click OK. 4. Optional: To close the Property Categories window, click OK. 7-8 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Built-In Property Categories System Default Stats Validation Verification Leaf Access Limb Access Built-In Property Categories In addition to the properties and property categories that system administrators define, there are several built-in property categories that organize the system properties. The following table describes the system-defined property categories. Property Category System Stats Validation Verification Description Properties related to a node s identifying characteristics, such as ID, Name, and Description Properties that provide statistical information about the node, such as number of children and number of siblings Validations currently assigned for the node one property for each validation Verifications currently assigned for the node one property for each verification Hyperion System 9 Master Data Management Administration 7-9

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Leaf Access Limb Access 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 The Validation, Verification, Leaf Access, and Limb Access categories are available to administrators only. NOTE For a list of the node-level System and Stats properties and their descriptions, see the NTier User s Guide, Chapter 3, Working with Properties. 7-10 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties User-Defined Properties Properties are mostly defined at the node level and contain information that describes the node. User-Defined Properties System administrators can define as many properties as necessary to meet an organization s master data requirements. User-defined properties must be assigned to at least one property category. In the Property Editor window, property categories are displayed as tabs. When you select a property category tab, the properties that are assigned to it are displayed in the Property column. You can edit the values of the properties that are displayed in bold type. The values of properties whose names are displayed in regular type cannot be changed. Hyperion System 9 Master Data Management Administration 7-11

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Data Types Data types define the data type of the values for the property, such as date, integer, or string. Data Types Data types define the data type of the values for a property. The most commonly used data types are string, boolean, and integer. Some data types store information about the hierarchy structure. For example, properties with the AscNodes data type store a list of nodes related to the current node. The following table describes the property data types. Property Data Type AscGroup AscNode AscNodes Description Associated Node Group. A property of this type can point to multiple nodes. Those nodes automatically point back to this node and automatically point to each other as well. Associated Node. A property of this type can point to a single other node. That node automatically points back to this node. Associated Nodes. A property of this type can point to multiple nodes. Those nodes automatically point back to this node but not to each other. 7-12 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Property Data Type Boolean Date Float FormatMemo (FrmtMemo) Group Hier Integer LeafNode LimbNode ListGroup Memo MultiNode (MultiNod) Node NodeProps (NodePrps) Property (Prop) Query RangeList (RangeLst) Sort SortProp StdQuery String Time ValType Version Description True or false Date and time Floating-point value Formatted memo Check box list of items Points to a hierarchy Integer value Points to a leaf node Points to a limb node List of items Memo field Points to multiple nodes Points to a node Points to a node's properties Points to a property Points to a query Defines a range of values Used for sorting Points to a sort property Points to a standard query String value Time Points to a validation type Points to a version Hyperion System 9 Master Data Management Administration 7-13

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Property Types Property types determine how the property gets its values. There are four property types: Lookup Defined Derived RWDerived Property Types When you create a property, you select a property type. Property types define how values are assigned to the property. The following table describes the four available property types. Property Type Defined Lookup Derived RW Derived How Property Values Are Derived Users enter values manually or select them from a list that system administrators define when they set up the property. Property values are assigned to the property automatically based on the values of another property. For example, the Country property might be filled in automatically based on the value for the City property. Property values are derived by using a function or a formula. Functions for derived properties are referred to as deriver classes. Derived properties are read-only; users cannot change their values. Property values for RWDerived properties are derived the same way as Derived property types. Users can manually override automatically derived values. 7-14 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Creating and Configuring Properties Creating and Configuring Properties You create and configure properties from the Properties window. To create a property: 1. From the menu bar, select Admin > Properties. The Properties window is displayed. 2. On the toolbar, click (Create New Property). The New Property dialog box is displayed. 3. In the Property Name text box, type a name for the new property. 4. Optional: In the Description text box, type a description. Hyperion System 9 Master Data Management Administration 7-15

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications 5. Optional: In the Label text box, type a label for the property. TIP The property label is displayed in the Property column of the Property Editor window. The default property label is the property name. 6. From the Data Type drop-down list, select a data type. 7. From the Property Level drop-down list, select a property level. 8. From the Property Type drop-down list, select a property type. 9. From the Category drop-down list, select a property category. 10. Depending on the property type that you selected in step 8, perform one of the following tasks. If you selected Defined as the property type, click OK to close the New Property dialog box. If you selected Lookup as the property type, the Lookup Property drop-down list is enabled. Select a lookup property from the drop-down list and then click OK to close the New Property dialog box. If you selected Derived or RWDerived as the property type, the Class Name dropdown list is enabled. Select a deriver class from the drop-down list and then click OK to close the New Property dialog box. 7-16 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Setting Up Lookup Properties The value of a lookup property is determined by the value of another property and a lookup table. 3 1 2 4 Setting Up Lookup Properties The values of a property with the Lookup property type are determined by the values of another property and a lookup table. For example, suppose that you define a property named Region and define its values as EUROPE, US, and ASIA. Next, you define a Lookup property type named Currency and select Region as its lookup property. You then set up the following lookup table to automatically derive the Currency property values. Lookup Value EUROPE US ASIA Result value EUR USD YEN Hyperion System 9 Master Data Management Administration 7-17

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications To set up a lookup property: 1. In the New Property dialog box, perform the following actions: a. From the Property Type drop-down list, select Lookup. b. From the Lookup Property drop-down list, select a lookup property. 2. Click OK. 3. In the Properties window, select the Lookup Table tab. 4. To set up the lookup table, perform the following actions: a. In the Lookup Key text box, type a valid value of the lookup property you selected in step 1. b. In the Result Value text box, type the result value that you want to assign to the lookup value that you entered. c. Click Add. d. Repeat steps a through c to complete the lookup table. 7-18 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Setting Up Lists of Values A list of values defines a set of valid values for the property. End users can select a value from the list to assign it to the property. 2 1 3 Setting Up Lists of Values When you create a Defined or RWDerived property, end users can enter values for the property manually from the Property Editor window. For efficiency, and to prevent users from entering incorrect values, you can set up a list of valid values for the property. To set up a list of values: 1. On the Property Definition tab of the Properties window, select the List check box. The List Values tab is added to the Properties window. 2. Select the List Values tab. 3. In the Add text box, type a value and click Add. The value is added to the list. 4. Repeat step 3 to complete the list of values. Hyperion System 9 Master Data Management Administration 7-19

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Specifying a Controlling Hierarchy A controlling hierarchy determines the value for global and inherited properties. 2 1 3 Specifying a Controlling Hierarchy For nodes that occur in more than one hierarchy, the controlling hierarchy determines the ancestor from which a global and inherited property derives its values. To define the controlling hierarchy: 1. On the Property Definition tab of the Properties window, select the Inheritable check box. The Controlling Hierarchy tab is added to the Properties window. 2. Select the Controlling Hierarchy tab. 3. To select a controlling hierarchy, perform the following actions: a. From the Version area, select a version. The hierarchies included in the version are displayed in the Controlling Hierarchy area on the right. b. Select a hierarchy from the list and then click Apply. 4. Optional: Repeat step 3 for other versions. 7-20 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Setting Up Derived Properties Setting Up Derived Properties The values of derived properties are calculated based on the values of one or more other properties. If the property type is Derived, the derived values for the property cannot be manually overridden by users. If the property type is RW Derived, the derived values can be manually overridden. When you create a derived property, you assign it a deriver class. Deriver classes are built-in functions that return values based on parameters that you provide. The deriver class assigned to a property cannot be changed after the property is created. Properties with the property type Derived or RWDerived display a Property Params tab in the Properties window. The parameters displayed on the Property Params tab depend on the deriver class that you selected. A separate row is displayed for each parameter. Hyperion System 9 Master Data Management Administration 7-21

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications The following table describes the most commonly used deriver classes. Deriver Class AncestorProp AscNodeProp DualAncestorProp ExternalLookup Formula InvertedLevel Description Moves up the local or controlling hierarchy (based on the Global flag) until it reaches a node for which the specified property equals the given value and then returns the specified return property. Although this property is not literally inheriting, the Inheritable flag must be set to allow the specification of the controlling hierarchy. Goes to the node pointed to by the specified node property and returns the specified property. Moves up the local or controlling hierarchy (based on the Global flag) until it reaches a node for which the specified properties equal the given values and then returns the specified return property. Although this property is not literally inheriting, the Inheritable flag must be set to allow the specification of the controlling hierarchy. Returns a property value based on an external database table. The parameters specify the Where clause and the fields to be returned as well as the field and record delimiter for building up the value from the returned row. Returns a value based on a specified formula. Provides an Essbase Type Level that starts at 0 for the leaf and increases up the ancestor chain. For nodes that have multiple branches underneath them, it is the maximum of the values from each branch. To enter or edit a value for a parameter: 1. Click in the value field for the parameter that you want to edit. An ellipsis button is displayed at the right end of the value field that corresponds to the parameter. 2. Click the ellipsis button. 3. The Text Edit - [ParamN] dialog box is displayed. 4. Type the value for the parameter and click OK. 7-22 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Specifying Default Values Default values are used in the following situations: For non-inheriting properties without a user-defined value For inheriting properties without a defined ancestor value Specifying Default Values You can define a default value for a property by typing a value in the Default Value text box of the Property Definition tab in the Properties window. The default value is used if an end user does not enter a value for a property. For inheriting properties, the default value is used if a value is not defined for the node s ancestor. TIP The default value can also represent a constant prefix to all of the property values. Hyperion System 9 Master Data Management Administration 7-23

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Specifying Maximum and Minimum Values Specifying Maximum and Minimum Values You enter values in the Minimum Value and Maximum Value text boxes on the Property Definition tab of the Properties window to specify numeric, date, or string length boundaries for the property values. 7-24 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Working with Formulas Most commonly used deriver class Used to create custom formulas Built using the Formula Tester dialog box Working with Formulas You use formulas to create custom properties to address specific business needs. Formula Deriver Class The most commonly used deriver class is Formula. When you create a Derived or RWDerived type property, you must also define the formula to be used to derive the property values. Formulas are composed of string literals, functions, or both, and their parameters. The parameters can consist of further string literals and other functions. You use the Formula Tester dialog box to create formulas. Hyperion System 9 Master Data Management Administration 7-25

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Creating and Editing Formulas Double-click an item in a list to insert it at the cursor location in the Formula box. Creating and Editing Formulas You can enter a formula by typing directly into the Formula text box or by selecting from the lists. By default, the Remove Spaces check box is selected. If you want to include spaces for formatting (for example, between the label and description in a concatenated string), you should clear this check box. The Function area lists all existing functions and their required parameters and result type. The Property area lists all currently defined properties, including system properties, and their labels. 7-26 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties To insert a function into a formula: 1. From the Function area, select a function. 2. Click the Insert button. 3. Replace each required parameter with the appropriate value. To insert a property into a formula: 1. In the Property area, select a property. 2. Click the Insert button. Hyperion System 9 Master Data Management Administration 7-27

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Formula Syntax Function names are case-insensitive and are followed by parentheses. Parameters can be nested functions, property labels, or literals. UpperCase(PropValue(PropertyLongName)) Nested function Property Label Literals can be string, numeric, or Boolean and do not need to be enclosed in quotation marks. Equals(String,PropValue(ParentDescr),UnitedKingdom) Property Label String literal Formula Syntax Formulas are automatically checked for syntax before being saved. The following items are verified: Whether function names are correct Whether property names are correct Whether an equal number of opening and closing parentheses are present Whether the correct number of parameters are present Function Names Function names are case-insensitive and should be immediately followed by parentheses, regardless of whether any parameters are required. 7-28 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Function Parameters Parameters must be of the expected type and number. Use commas to separate parameters. Parameter values can be nested functions, property names, or literals. The following considerations apply for literals: Literals can be string, integer, floating-point, or Boolean. In a string literal, spaces are treated like any other character. Therefore you should not use extra spaces in formulas. Quotation marks are not needed around literals, including string literals. Valid Boolean literals are 1, 0, T, F, True, and False. If parameters are of incorrect type, an error is reported. In the case of too few parameters, a List index out of bounds error is reported. In the case of too many parameters, the additional parameters are ignored. In certain functions where parameter values may need to contain special characters (for example, comma, space, and tab), a special [keyword] notation can be used. For example, FlipList(NodeList,[comma])is used to perform the FlipList function on the comma-delimited list NodeList. The following functions can take [comma], [space], or [tab] as the Delimiter parameter: ArrayCount, ArrayIndex, ArrayItem, FlipList, Intersection, ListContains, PadList, RangeListContains, RangeListSubset. The ReplaceStr function, which requires parameters for the old and new pattern, can take [comma], [space], [tab], [crlf], [cr], [lf], [openparen], or [closeparen] in addition to normal text strings. Literals Any value that is not a valid function name followed by parentheses is considered a literal. It can be a string, integer, floating-point, or Boolean literal. In a string literal, spaces are treated like any other character. Therefore you should not use extra spaces in formulas. Hyperion System 9 Master Data Management Administration 7-29

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Testing Formulas Testing Formulas Formulas can be tested for specific nodes by entering test data in the scratch pad area and then clicking the Evaluate button. This process may find logic or implementation errors in the formula that a simple syntax check may miss. The formula result and any formula error or status messages are displayed. 7-30 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Alternatively, you can select the Evaluate Using Node option, and then select a specific node from a hierarchy to test the formula. Formula Evaluation Formulas are evaluated from left to right, with functions and string literals being evaluated when they are encountered. By this method, nested functions are evaluated before additional parameters that appear to the right of the nested function. Functions can be nested explicitly in a formula, or they can be nested implicitly by being set to retrieve the value of another formula property. Implicit circular reference checking is not performed by the Formula Deriver; therefore a circular reference causes a stack overflow and abnormally terminates the application. Hyperion System 9 Master Data Management Administration 7-31

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Functions PropValue(PropAbbrev) PropValue(Description) Concat(Item1, Item2,... ItemN) Concat(Country Code:,PropValue(Code)) NodeIsLeaf () NodeIsLeaf() StrToInt(AString; Default) StrToInt(PropValue(Children)) Functions The slide shows examples of some commonly used functions. PropValue returns the value of the specified property for the current node as a string. Concat concatenates two or more given strings into one and returns the result. NodeIsLeaf returns TRUE if the current node is a leaf; otherwise, it returns FALSE. StrToInt converts the data type from string to integer. You can optionally provide a default value to use in case the string value does not contain a valid integer. 7-32 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties List of Functions The following list describes commonly used functions. Abbrev Returns the Abbrev (Name) of the current node. Syntax: Abbrev(): String Add Adds two given integer values and returns the result. Syntax: Add(Int1, Int2: Integer): Integer BoolToStr the result. Converts a given Boolean value to the string True or False and returns Syntax: BoolToStr(Expression: Boolean): String ConcatWithDelimiter the result. Concatenates two or more delimited strings into one and returns Syntax: ConcatWithDelimiter(Delimiter: String; SkipBlanks: Boolean; Item1, Item2,... ItemN: String): String Descr Returns the Descr (Description) of the current node. Syntax: Descr(): String FloatToStr Returns a string representing the given floating-point value. Syntax: FloatToStr(AFloat: Float): String GreaterThanOrEqual Returns TRUE if the first of two given integer values is greater than or equal to the second. Syntax: GreaterThanOrEqual(Int1, Int2: Integer): Boolean HasChildWith Returns TRUE if the given expression is true for any child. Syntax: HasChildWith(Expression1: Boolean): Boolean HasParentNode Returns TRUE if the given local node has a parent node. Syntax: HasParentNode(ALocalNodeAbbrev: String): Boolean HasSiblingWith Returns TRUE if the given expression is true for any sibling. Formulas that use this function must be in a local property. Syntax: HasSiblingWith(Expression1: Boolean): Boolean Hyperion System 9 Master Data Management Administration 7-33

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications HierNodePropValue given hierarchy. Returns the value of the given property of the given node in the Syntax: HierNodePropValue(HierAbbrev,NodeAbbrev,PropAbbrev: String): String ID Returns the integer ID of the current node. Syntax: ID(): Integer Intersection Returns the set of items common to two lists. The ordering of the results is based on how the items appear in the first list. Syntax: Intersection(List1: String; List2: String; Delimiter: String): String IntToStr Converts the given integer to a string value and returns the result. Syntax: IntToStr(Int: Integer): String IsAlpha Returns TRUE if the given string contains only the letters A to Z (caseinsensitive). Syntax: IsAlpha(AString: String): Boolean IsNumeric Returns TRUE if the given string contains only numbers 0 to 9. Syntax: IsNumeric(AString: String): String Length Returns the number of characters in the given string. Syntax: Length(AString: String): Integer ListAncestors Returns a comma-delimited list of the current node s ancestors. The current node must be a local node for this function to work. To ensure that the node is local, any formula containing this function must be part of a local derived formula property. Syntax: ListAncestors(): String ListChildren Returns a comma-delimited list of the current node s immediate children. Syntax: ListChildren(): String ListContains a delimited list. Returns a Boolean value indicating whether or not a value is contained in Syntax: ListContains(List, Item, Delimiter: String): String 7-34 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties ListDescendents descendents. Returns a comma-delimited list of all of the current node s Syntax: ListDescendents(): String LowerCase Converts the given string to lowercase and returns the result. Syntax: LowerCase(AString: String): String NodeExists Returns TRUE if the given node exists. Syntax: NodeExists(NodeAbbrev: String): Boolean NodeInHier Returns TRUE if the given node exists in the given hierarchy. Syntax: NodeInHier(NodeAbbrev, HierAbbrev: String): Boolean NodePropValue Returns the value of the given property of the given node in the current hierarchy for a local node, or in the current version for a global node. Syntax: NodePropValue(NodeAbbrev, PropAbbrev: String) : String NumChildWith Returns the number of children for which the given expression is true. Syntax: NumChildWith(Expression: Boolean): Integer NumDescendentsWith expression is true. Returns the number of descendents for which the given Syntax: NumDescendentsWith(Expression: Boolean): Integer ParentPropValue Returns the value of the given property of the current node s parent node. The current node must be a local node for this function to work. To ensure that the node is local, any formula containing this function must be part of a local derived formula property. Syntax: ParentPropValue(PropAbbrev: String): String PropControllingHier Returns the name of the controlling hierarchy of the given property in the current version. Syntax: PropControllingHier(PropAbbrev: String): String PropDefaultValue Returns the default value of the given property. Syntax: PropDefaultValue(PropAbbrev: String): String RTrim Returns the given string with all spaces trimmed from the right end. Hyperion System 9 Master Data Management Administration 7-35

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Syntax: RTrim(AString: String): String StrToFloat Returns the floating-point value of the given string. If the string does not represent a valid floating-point value, the default value is returned. Syntax: StrToFloat(AString: String; Default: Float): Float SubString Returns a portion of the given string, starting at the given index and containing the given number of characters. Syntax: SubString(AString: String; Index, Count: Integer): Integer UpperCase Converts the given string to uppercase and returns the result. Syntax: UpperCase(AString: String): String 7-36 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 7 Managing Properties Logical Operators Equals(ParamType, String1, String2) Equals(String,PropValue(NodeType),Account) Equals(Integer,StrToInt(PropValue(Children)),1) Or(Expression1, Expression2) OR(NodeIsLeaf(),Equals(String,PropValue(NodeType),AccLeaf)) And(Expression1, Expression2) AND(NodeIsLeaf(), Equals(String,PropValue(NodeType),Account)) If(Expression; ResultIfTrue, ResultIfFalse) IF(NodeIsLeaf(), AccountLeaf,AccountLimb)) Logical Operators Logical operators allow you to test for different conditions. The slide shows examples of some of the most commonly used logical operators. Equals returns TRUE if two values of a specified data type match exactly. Or returns TRUE if either of two expressions evaluates to TRUE. And returns TRUE if both of two expressions evaluate to TRUE. If returns the first of two values if the test expression evaluates to TRUE; otherwise, it returns the second value. Hyperion System 9 Master Data Management Administration 7-37

Lesson 7 Managing Properties Module 2 Managing Hyperion MDM Applications Summary In this lesson, you should have learned to: Describe Hyperion Master Data Management properties Create property categories Create properties Define formulas 7-38 Hyperion System 9 Master Data Management Administration

L E S S O N 8 Setting Up Node Types 8 Objectives At the end of this lesson, you should be able to: Describe node types Configure the node type property Create node types Troubleshoot common errors

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications Node Types Overview Group nodes based on common characteristics Filter properties for nodes Determine validations and verifications for nodes Determine the node icon (glyph) Node Types Overview Node types enable you to logically group nodes that share the same basic characteristics. The nodes within a specified node type share the following elements: Properties Validations Glyphs Node Types Versus Property Categories Node types should not be confused with property categories. The node type assigned to a node determines which properties and validations are valid for the node. Property categories organize the properties into groups. 8-2 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types Node Types Benefits Node types offer the following benefits: They are used to filter the list of properties assigned to nodes. They are used to assign validations and verifications to nodes. For example, suppose that the properties in your application include Alias, Account Type, and Country Code, with the following requirements. Nodes used in the Account dimension in your target systems do not need a Country Code property. Nodes used in the Entity dimension in your target systems do not need an Account Type property. Nodes for both Account and Entity dimensions in your target systems need an Alias property. To meet these requirements, you create node types named Account and Entity. The Account node type includes the Account Type and Alias property but not the Country Code property. The Entity node type includes the Country Code and Alias property, but not the Account Type property. Often, more complex node types that combine several groupings are required. For example, suppose that you have a requirement that the IsCalculated property for all account leaf nodes should be set to FALSE. You create node types named Account- Limb and Account-Leaf. You then create a verification rule that verifies that the IsCalculated property is set to FALSE, and you assign the rule to the Account-Leaf node type. Hyperion System 9 Master Data Management Administration 8-3

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications Configuring HierarchyNodeType 1. Create a property for node types. 2. Set the HierarchyNodeType property at the hierarchy level to identify the node type property. Configuring HierarchyNodeType Node types are assigned to nodes. End users select a node type value and assign it to the node from a list of node types that you define. HierarchyNodeType is a systemdefined property at the hierarchy level that stores the node type property name, which stores the different node-type categories that you define for a given hierarchy. To configure the HierarchyNodeType property, perform the following tasks: Identify an existing node-level property or create a new one (typically Local and Inheriting) that can be used for each node to indicate its node type. For example, you could use a property named TypeOfNode. 8-4 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types At the hierarchy level, set the HierarchyNodeType property to the node-level property that indicates node type. In the example in the slide, the HierarchyNodeType property points to the TypeOfNode property for the CashFlow hierarchy. After this property is set, the node types are enforced for this hierarchy. TIP Because property and validation assignments to nodes that belong to different hierarchies are based on varying business requirements, you can define several node type properties to meet the master data needs of an organization. Hyperion System 9 Master Data Management Administration 8-5

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications Creating Node Types Creating Node Types You create and set up node types from the Node Types dialog box. To create node types: 1. From the menu bar, select Admin > Node Types. The Node Types window is displayed. 2. On the toolbar, click (Create New Node Type). The New Node Type dialog box is displayed. 3. In the Name text box, type a name for the new node type. 4. Optional: In the Description text box, type a description. 5. From the Glyph drop-down list, select a glyph (icon) for the node type. 6. Click OK. 8-6 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types Assigning Properties to Node Types Assigning Properties to Node Types You set up node types by assigning specific properties and validations to them. To assign properties to node types: 1. In the Node Types window, select a node type from the Current drop-down list. 2. Select the Properties tab. 3. From the Category drop-down list, select a property category. 4. Press and hold the Ctrl key and select the properties that you want to assign to the node type. 5. Click the add button. The properties that you selected are added to the Selected Properties area. Hyperion System 9 Master Data Management Administration 8-7

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications Assigning a Node Type to Nodes Assigning a Node Type to Nodes By assigning a specific node type to a node, you automatically assign all the properties and validations that are assigned to the node type to it. End users can use the Property Editor window to assign a node type to a node, or you can create a derived property to automatically assign nodes to node types. The following guidelines apply to assigning a node type to nodes: When end users view properties for a node, only the properties assigned to the given node type are shown. Leaving the node type property value blank indicates that no node type is assigned to the node, and all available properties are shown when end users view properties for the node. Because the node type property is typically defined as inheriting, it is not necessary to assign a node type for the children of each node unless a child node must be assigned to a node type that is different from the node type of its parent. 8-8 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types Assigning Node Types to Nodes by Using Derived Properties Using a derived property enables you to assign node types to imported or entered nodes automatically. The following are some typical properties from which node types are derived: A prefix on the node name, such as cc_ for cost center nodes and acc_ for account nodes A structure property, such as being a leaf or a limb node A hierarchy-level property, such as belonging to a hierarchy for a specific dimension Concat(PropValue(Dimension),-,If(NodeIsLeaf(),Leaf,Limb)) Assigning Node Types to Nodes by Using Derived Properties Because you might be importing thousands of nodes into your application, you need an efficient way to assign node types to nodes. If all the nodes in a hierarchy share a node type, you can assign the node type to the top node; its descendants inherit the node type. Another strategy is to make the node type property a derived property. You can then use a formula or a deriver class to automatically derive the node type for the node based on other node or hierarchy properties. For the example in the slide, the node type is derived from the value of two properties: the Dimension property, which is a hierarchy-level property that stores the dimension type for the current hierarchy, and the IsLeaf system property, which is a node-level property that returns TRUE if the current node is a leaf. In the formula, if IsLeaf returns TRUE, the dimension type is concatenated with the text Leaf ; otherwise, the dimension type is concatenated with the text Limb. Hyperion System 9 Master Data Management Administration 8-9

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications Disabling Node Types Disabling Node Types You disable a node type for a specified hierarchy by removing its value. To disable the use of node type for a specified hierarchy: 1. In the hierarchy Property Editor window, right-click the HierarchyNodeType property and select Remove Value. 2. Click Save. [Removed] is displayed in the status column. 8-10 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types Adding, Modifying, and Deleting Node Glyphs Adding, Modifying, and Deleting Node Glyphs You can create new glyphs (icons) and delete glyphs that you no longer use. You can also modify existing glyphs. To create a glyph: 1. Select Admin > Node Type Glyphs. 2. Click (Create New Glyph). The New Node Glyph dialog box is displayed. 3. In the Name text box, type a name for the new glyph. 4. Click Browse and select the bitmap that you want to use for the new glyph. 5. Click OK. Hyperion System 9 Master Data Management Administration 8-11

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications To modify a node glyph: 1. Select Admin > Node Type Glyph. 2. Double-click a glyph. The Edit Node Glyph dialog box is displayed. 3. Perform any of the following actions: Edit the name of the glyph. Click Browse and select a different bitmap. To delete a glyph that is no longer in use: 1. Select Admin > Node Type Glyph. 2. Select a glyph and then click (Delete Current Glyph). A deletion confirmation message is displayed. 3. Click Yes. 8-12 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types Troubleshooting Common Errors These are some common problems related to node types: Too few properties are displayed for nodes Too many properties are displayed for nodes Validations or verifications do not run Troubleshooting Common Errors Improper assignment of node types can result in the following problems. Too Few Properties Are Displayed One or more property categories for a node may display fewer properties than were assigned to the property category. Because properties must be assigned to node types as well as to property categories to be displayed, you should verify that the Properties tab for the node type includes the correct properties. Hyperion System 9 Master Data Management Administration 8-13

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications Too Many Properties Are Displayed If the node type property is blank for a node, properties are not filtered. If nodes display too many properties, make sure that the node type property for the node has a value. If the node type is assigned from a derived property, verify that the formula or deriver class for the property returns valid values for all nodes. Validations or Verifications Do Not Run Verifications and validations run only for node types to which they have been assigned. If a validation or verification fails to run for a node, verify that the node is assigned the correct node type and that the correct validations and verifications are included on the Validations tab for the node type. 8-14 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 8 Setting Up Node Types Summary In this lesson, you should have learned to: Describe node types Configure the node type property Create node types Troubleshoot common errors Hyperion System 9 Master Data Management Administration 8-15

Lesson 8 Setting Up Node Types Module 2 Managing Hyperion MDM Applications 8-16 Hyperion System 9 Master Data Management Administration

L E S S O N 9 Implementing Business Rules 9 Objectives At the end of this lesson, you should be able to: Describe validations and verifications Create validations and verifications Run verifications

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications Validations and Verifications Overview Benefits Ensure that hierarchy rules are observed Enforce business rules Validations versus verifications Validations are enforced during data entry. Verifications execute in batch mode. Validations and Verifications Overview Validation rules ensure that the hierarchy rules and business rules used by the external systems that Hyperion Master Data Management feeds are observed. These are some typical requirements for which validation rules could be created: Adherence to standards for account numbers and account codes; for example, all accounts starting with 100 are expense accounts. Maximum depth of hierarchies; for example, account hierarchies cannot exceed four levels. Adherence to limb and leaf requirements; for example, limb members must be readonly. 9-2 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Validation rules are implemented as either validations or verifications. The differences between validations and verifications are: Validations - Run automatically (in real time) as users edit 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 in sets defined by the system administrator. - Can be inheriting or noninheriting. If they are inheriting, they run for the node selected or assigned and all descendant nodes. Noninheriting 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 validation rule. Hyperion System 9 Master Data Management Administration 9-3

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications Considerations for Validations and Verifications Validations should be used instead of verifications only when the following conditions are met: There are absolutely no exceptions to the rule. There are no possible timing issues where the rule may temporarily be broken before it can be enforced. Considerations for Validations and Verifications When is it appropriate to implement a validation rule, and when is a verification more appropriate? Many business rules have exceptions. For those that do not have exceptions, many still need to be suspended temporarily in order to complete an update. For rules that have exceptions or that need to be temporarily suspended for reasons of timing, verifications should be used instead of validations. Consider the following examples. Assume that an organization has a business rule that states that a sales representative can have no more than 20 customers. If exceptions are allowed with management approval, a verification is appropriate. A verification would report on all those sales representatives who have been assigned more than 20 customers. Management could then verify that these exceptions had approval. If exceptions to this rule are never allowed, a validation is more appropriate. A validation would make it impossible to add a 21st customer. Sometimes, rules need to be suspended temporarily for timing reasons. For example, a common rule that Hyperion Master Data Management Server 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 could ever be added. 9-4 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Validation Levels The validation level determines when and at what level validations and verifications run. The following levels are available: Node Hierarchy Version Remove Move Global node Merge Validation Levels The validation level defines the circumstances and the level (node, hierarchy, or version) at which the validation (or verification) runs. The following table lists available validation levels: Validation Level Meaning Example Node Hierarchy Version The most commonly used level. Can be a validation or a verification. Can be assigned and run at the node, hierarchy, or version level. Verification only. Intended to check properties in a hierarchy to ensure that certain criteria are met. Can be assigned and run at the hierarchy or version level (in the Version Control window). Verification only. Checks the properties of a version. Check that a text string has a valid length. Ensure that a hierarchy has no more than 10,000 nodes. Ensure that a version contains no more than 100,000 nodes. Hyperion System 9 Master Data Management Administration 9-5

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications Remove Global node Merge Validation only. Activated when an attempt is made to remove or delete a node from a hierarchy. Can be used to prevent certain types of nodes from being deleted. Can be assigned and run at the hierarchy or version level (in the Version Control window). Validation or verification, assigned at a version level. Validates every node in the version regardless of hierarchy, including orphans. Only properties defined as global are checked. Validation only. Similar to the Global node validation, but activated when an operation requiring a merge (for example, a deletion or an inactivation) is performed. Assigned at the version level. Prevent the deletion of cost center nodes from a hierarchy. Ensure that all nodes have a name with more than 8 characters. Ensure that a leaf node is merged only with another leaf node. 9-6 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Validation Classes Validation Classes When you create a validation or verification, you select a validation class to specify the criteria. Validation classes are similar to deriver classes for derived properties. Each validation class has one or more parameters. Validation classes return a value of TRUE or FALSE for a node based on whether the node s property values match the criteria defined in the validation class parameters. If a node returns a value of FALSE, it passes the validation or verification. For example, you can create a verification with the MaxChildren validation class set at 10. Nodes that have 10 or fewer children return a value of FALSE and pass the verification. Hyperion System 9 Master Data Management Administration 9-7

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications The following table describes the most commonly used validation classes. Validation Class Level Description Parameters BoolNodeInHier Node Verifies that the specified Boolean property has no TRUE values in the given hierarchy. CustPropQuery Node Verifies by using a predefined standard query and the expected result. GlobalPropQuery Global Verifies by using a predefined standard query and the expected result. MergeEquiv Merge Verifies that the affected node and the merge node have the same value for the specified property. NoPropBranch Node Verifies that the specified property is set at least once on a given branch. PropLength Node Verifies that the specified property has a value that is at least of minimum length and no more than maximum length. RequiredField Node Verifies that for all nodes for which a specified property has a given value, each property in the required list has a value. If the Reject Default Records flag is TRUE, then each property in the required list must have a value other than the default. If the Reject Default Records flag is FALSE, then the default values are acceptable. SingleBoolBranch Node Verifies that the specified Boolean property is set to TRUE only once per branch. SinglePropBranch Node Verifies that the specified property is set only once per branch. StrPropEqual Node Fails for all nodes for which the specified property equals the given value. UniquePropBranch Node Verifies that the specified property has a unique value within a branch. UniqueProp Node Verifies that the specified property has no duplicate values within a hierarchy. If the Include Defaults flag is FALSE, then nodes with default value are not included. VersionUniqueProp Global Verifies that the specified property has no duplicate values within a version. If the Include Defaults flag is FALSE, then nodes with the default value are not included. Property, Hierarchy Property query name, Failure value Property query name, Failure value Property Property Property, Minimum Length, Maximum Length Property, Value, Reject Default Records, Required Properties Property Property Property, Value Property Property, Include Defaults Property, Include Defaults 9-8 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Creating Validations and Verifications 2 1 3 4 Creating Validations and Verifications You create and set up validations and verifications from the Validations window. For validations and verifications, Description is a required field. The text in the Description field is included in the error message that is displayed when nodes fail validation. To create a validation: 1. Select Admin > Validations. The Validation window is displayed. 2. Click the create new validation button. The New Validation dialog box is displayed. 3. Perform the following actions: From the Validation Type section, select Validation or Verification. From the Class drop-down list, select a validation class. Hyperion System 9 Master Data Management Administration 9-9

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications From the Level drop-down list, select a validation level. In the Name text box, type a name for the new validation. In the Label text box, type a label for the validation. In the Description text box, type a short description. 4. Click OK. 9-10 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Editing Validation Parameters 1 2 3 4 Editing Validation Parameters After you create a validation, you need to edit the parameter values of the validation class to complete its setup. To edit validation class parameters: 1. In the Validations window, select the Parameters tab. 2. In the Value field for the parameter, click the ellipsis button. The Text Edit dialog box is displayed. 3. Type a value for the parameter. 4. Click OK. Hyperion System 9 Master Data Management Administration 9-11

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications Creating Validations and Verifications by Using Property Queries 1. Define a property query. 2. Use either the CustPropQuery or the GlobalPropQuery validation class to create a validation or a verification. 3. Specify the name and the failure value of the property query for the validation parameter values. Create Validations and Verifications by Using Property Queries With the CustPropQuery and GlobalPropQuery validation classes, you can use property queries to define the criteria for validations and verifications. This enables you to build powerful validations and verifications with complex criteria. To use property queries, you first create the property query to be used in the validation or verification. You then create a validation or verification with the CustPropQuery validation class for standard queries or the GlobalPropQuery validation class for global queries. You reference the property query name in the Parameters tab. You also specify whether a value of TRUE or FALSE should be returned when nodes meet the criteria defined in the query. 9-12 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Assigning Validations and Verifications Assigning Validations and Verifications After you create validations and verifications, you can assign them to versions, hierarchies, and nodes. Validations and verifications that you assign at the version level are inherited by all hierarchies and nodes within the version. Validations and verifications that you assign at the node level are inherited by all levels under the node. To assign validations and verifications to versions or hierarchies: 1. Right-click the version or hierarchy and select Assign > Verifications or Assign > Validations from the shortcut menu. The Assign Validations or Assign Verifications dialog box is displayed. Hyperion System 9 Master Data Management Administration 9-13

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications 2. In the Selected column, select the check boxes for the validations or verifications that you want to assign to the version or hierarchy. 3. Click OK. To assign validations and verifications to a node: 1. Right-click the node and select Properties. The node Property Editor window is displayed. 2. Select the Validation or Verification tab. 3. In the Value column, select the check boxes for the validations or verifications that you want to assign to the node. 4. Click Save. 9-14 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Assigning Validations and Verifications to Node Types Assigning Validations and Verifications to Node Types You assign validations and verification to one or more node types. A validation or verification runs only for nodes that belong to a node type to which it is assigned. For example, you could create a validation named ExpenseTest that verifies that all nodes with an account type of expense have a prefix of 100. Because only account nodes have an account type, you assign the ExpenseTest validation to the Account node type, but not to the Entity node type. To assign validations to node types: 1. Select Admin > Node Types. The Node Types window is displayed. 2. From the Current drop-down list, select a node type. Hyperion System 9 Master Data Management Administration 9-15

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications 3. Select the Validations tab. 4. Press and hold the Ctrl key and select the validations that you want to assign to the node type from the Available Validations area. 5. Click the add button. 6. Click OK. 9-16 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Running Verifications Running Verifications Verifications run in batch mode on request. Failed verifications are listed in a separate window. If you select to mark nodes, nodes that fail verification are marked in the hierarchy. To run a verification: 1. Right-click a node and select Verify. 2. Select one of the following options: Assigned Runs all verifications that are assigned to the node type. Selected Displays the Select Verifications dialog box. 3. If you chose Selected in step 2, each available verification is listed. To select a verification to run, select its check box. Hyperion System 9 Master Data Management Administration 9-17

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications 4. Click Assigned to select only the verifications that have been assigned by the administrator. 5. Click the Options tab and select one of the following options to configure the node list returned by the verifications. Show in list All nodes that fail a verification are displayed in a list. Mark nodes All nodes that fail a verification are marked in the hierarchy. Both Nodes are marked and a list is displayed. 6. Click OK to run the selected verifications. 9-18 Hyperion System 9 Master Data Management Administration

Module 2 Managing Hyperion MDM Applications Lesson 9 Implementing Business Rules Summary In this lesson, you should have learned to: Describe validations and verifications Create validations and verifications Run verifications Hyperion System 9 Master Data Management Administration 9-19

Lesson 9 Module 2 Implementing Business Rules Managing Hyperion MDM Applications 9-20 Hyperion System 9 Master Data Management Administration

M O D U L E 3 Administering Master Data 9 Overview The Hyperion MDM application structure is the container where master data from source systems is stored and managed. Lessons of this unit cover the steps of managing and maintaining the application structure. Lessons in this module include: Loading Master Data Exporting Master Data Managing Security Auditing Master Data

L E S S O N 1 0 Loading Master Data 10 Objectives At the end of this lesson, you should be able to: Describe importing data features Import master data to new versions Combine versions Import master data to existing versions

Lesson 10 Loading Master Data Module 3 Administering Master Data Importing Master Data Overview [Hier] TotalActivity,Activity TotalGeography,Geographical [Relation] Europe,Geographical,Europe,EUR France,Europe,France HQ,EUR, Import from flat file to test version. Blend test version into production version. Importing Master Data Overview You can import master data from external systems to Hyperion Master Data Management applications in various formats, including text files, data extracts, and other sources. When you import data to Hyperion MDM, always create a new version. This allows you to verify that the import was run correctly. After verifying the data, you use the Blender tool to incorporate the imported data into a production environment. In the example shown in the slide, the Entity dimension was imported from a flat file into a new version named TestVersion. After you review the data, you incorporate it into the existing production version by using the Blender tool. 10-2 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Import Elements Section heading Hierarchy name Top node Node name [Hier] TotalActivity,Activity TotalGeography,Geographical [Relation] Europe,Geographical,European Operations,EUR France,Europe,France HQ,EUR, Admin,France,Administration France,EUR Plant1,France,Plant Number 1,EUR Parent Node property values Import Elements An import file includes sections and columns. Sections designate the type of data being imported. An import can contain several sections for importing hierarchy, node, relationship, and other types of information. The sections can appear in any order and must be identified by section headers. The data in each section is organized into columns. An import column is mapped to a corresponding property in Hyperion MDM, such as Name, Description, or any other nonread-only property. Columns can be either fixed width or separated by a delimiter, such as a comma or a colon. Columns can be in any order and do not require labels. Mapping the columns to corresponding properties in Hyperion MDM takes place in the Import Wizard. You can include multiple sections of the same type in a single file; for example, several entity sections from different Hyperion Essbase databases. The import process combines the sections before importing them. Hyperion System 9 Master Data Management Administration 10-3

Lesson 10 Loading Master Data Module 3 Administering Master Data Import Sections Version [version] Hierarchy [hier] Node [node] Relationship [relation] Hierarchy node [hiernode] Import Sections The following table describes the valid sections and the required columns for each section: Import Sections Required Columns Description Version Version Name Contains version property values. Hierarchy Hierarchy Name, Top Node Contains structural information about each hierarchy and top node to be imported. Can also contain columns for hierarchy property values. Node Node Name Contains structural information about each node to be imported. Can also contain columns for node property values. Relationship Hierarchy Node Parent Node Name, Child Node Name Hierarchy Name, Node Name Contains parent-child information about each relationship to be imported. Can also contain columns for node property values for the child in each pair. Contains node values that are specific to a given hierarchy. 10-4 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Importing Data to New Versions 1 2 4 3 Importing Data to New Versions You use the Import Wizard to create imports. You can also open imports that you saved previously. When you open a saved import, you can edit the import settings before running the import. To launch the Import Wizard: 1. From the menu bar, select File > Import. The Import Type page of the wizard is displayed. 2. Perform one of the following tasks: Select Flat File Import from the list to start a new import. Select a saved import from the list to use a previously saved import. Hyperion System 9 Master Data Management Administration 10-5

Lesson 10 Loading Master Data Module 3 Administering Master Data 3. Click Next. The Import page of the wizard is displayed. 4. Enter a name and description for the new version and specify error-handling options. The following table describes the available fields: Field Abbrev Description Log Output File Name Max Errors Description A name of up to 20 characters for the version in which to import data. A description of up to 40 characters. A path and file name for logging error and status messages. An integer value for the maximum number of errors permitted before the import process is stopped. The default value is 20. If you enter a value of 0, the import engine runs to completion regardless of the number of errors encountered. If an unrecoverable error occurs, the import process is stopped. 10-6 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Selecting Section and Processing Options Selecting Section and Processing Options You must identify each section in the import file that you want to import. You must also specify processing options for the imported data. The following table describes the available options. Option Description Sections Skip Blank Values for These Properties Skip Default Values for Select each section to import. If a section is not selected, it is not imported, even if it appears in the input source. Configure the import to skip blank values in the source file for the property types selected. Skip property values in the source file if they are equal to the default value for the property. Hyperion System 9 Master Data Management Administration 10-7

Lesson 10 Loading Master Data Module 3 Administering Master Data Option Description Determine Leaf Nodes at End of Import Process Relationship Section Sorting Sort Property to Populate Hierarchies to Be Sorted Determine whether the import automatically makes any node with no children at the end of the import into a leaf node. If selected, the import automatically sets the leaf property to True for any node that has no children at the end of the import process. If not selected, the leaf property retains either its system default value or any value explicitly included as part of the imported data. Enable the import to sort the nodes based on the order in which they appear in the relationship section of the source file. Select the node property in which to store the sort order. This option is available only if the Sort Relationships check box is selected. Enter the hierarchies to which the sort applies. This option is available only if the Sort Relationships check box is selected. 10-8 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Mapping Properties to Columns 1 2 3 4 [Relation] Europe,Geographical,Europe HQ,EUR, France,Europe,France HQ,EUR, Admin,France,Administration France,EUR, Plant1,France,Plant Number 1,EUR, UK,Europe,United Kingdom,GBP,Development... Mapping Properties to Columns You must map columns in the import file to Hyperion MDM properties. You create separate mappings for each section of the import file. Each property maps to a column in the import file: The number of properties in the Selected Properties list must match the number of columns in the import file. The order of the properties in the Selected Properties list must correspond to the order of the columns in the file. For example, if data for the Description property is in the third column of the import file, the Description property must be displayed as the third item in the Selected Properties list. A special property called Ignore Column is available as a placeholder for any column in the input source that should not be processed during the import. Hyperion System 9 Master Data Management Administration 10-9

Lesson 10 Loading Master Data Module 3 Administering Master Data For hierarchy-specific (or local) properties, you can use the Hierarchy List text box to specify the hierarchies for which the mapping is valid. For example, you could have a Currency property and you want to populate the property only for nodes in the Geographical hierarchy, not the Functional hierarchy. By default, all hierarchies are selected. This feature applies to local properties only. 10-10 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Specifying File Format Information Specifying File Format Information You must specify the following file format information: Import file name and location Column delimiter for the file or, if it is a fixed-width file, the width for each column Whether to strip quote marks Prefix character used in the file to designate lines that contain section headings. (Optional: You can include a suffix character.) Section heading labels used in the file (for example, hier for hierarchy section) For fixed-width files, the columns width values default to the field lengths of the properties to which they are mapped. You can modify the column widths as needed. Select the Strip Quoted Strings check box to allow the import of data that encloses string values in quotation marks (double or single). By selecting this option, you remove surrounding quotes and separate embedded quotes before importing the value. For example: Mr. Harris s Necktie would be imported as Mr. Harris's Necktie. Hyperion System 9 Master Data Management Administration 10-11

Lesson 10 Loading Master Data Module 3 Administering Master Data Setting Up Duplicate Handlings Setting Up Duplicate Handlings You can edit the parameters that affect how the import processor handles duplicate nodes. A duplicate is any node that appears under multiple parents within the same hierarchy. If a duplicate is identified during the import, it is replaced with a unique node that is named according to the defined guidelines. As the settings are edited, an example displays the resulting value. You can query duplicate nodes to resolve underlying data issues. The following table describes the available options: Option Unique String Delimiter Description Enter an optional string that is used to form part of the new unique node name. Enter a character that is used to separate the original node name from the unique portion of the name. 10-12 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Option Unique ID Seed Zero-Pad Length Append Unique Text to the End of the Node Abbrev Associated Property Duplicate Error Mode Description Specify the starting point for this ID. For example, if NodeA occurs three times in the same hierarchy, and the unique ID seed is 1, then the original node is unchanged, and the other nodes are replaced with NodeA1 and NodeA2. (This example ignores the other Duplicate settings to illustrate the unique ID seed.) Enter the minimum number of digits in the Unique ID portion of the duplicate string. For example, a value of 3 for the zero-pad length means that duplicate nodes are named NodeA001, NodeA002, and so on. Select to determine whether the unique string is to be added to the beginning or the end of the original node name. If this check box is selected, the string is added to the end. If it is not selected, the string is added to the beginning. For example, if it is not selected, the duplicate nodes are named 001NodeA, 002NodeA, and so on. Select a property to allow duplicate nodes to be grouped so that they can be easily queried after the import is completed. The selected property is populated with the node name of the original node in all duplicate nodes. Select an option 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: An error message is added to the log for each duplicate. Hyperion System 9 Master Data Management Administration 10-13

Lesson 10 Loading Master Data Module 3 Administering Master Data Running Imports and Viewing Results Running Imports and Viewing Results After setting the duplication handling options, you can click Run to run the import. When the import is completed, the Import Results dialog box displays statistical information about the import as well as a detailed list of each message generated during the import process. If you designated a log output file name when you defined the import version, the information in the Import Results dialog box is displayed in the output file. Data is imported to the new version in a detached state; that is, the data is not yet permanently saved. After verifying the imported data, you can save it by right-clicking the version in the Version Control window. 10-14 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Saving and Deleting Imports Saving and Deleting Imports You can save imports that you run regularly by clicking the (Save) or (Save As) button in the Import Dialog window toolbar. To save an import: 1. In the Save As dialog box, type a name in the Name text box. 2. Optional: In the Description text box, type a short description. 3. Click OK. To delete an import: 1. Select the name of the import that you want to delete. 2. On the toolbar, click the (Delete) button. Hyperion System 9 Master Data Management Administration 10-15

Lesson 10 Loading Master Data Module 3 Administering Master Data Blending Versions Source Target after blend Target before blend Moved node Inserted nodes Blending Versions You use the Blender feature to combine (or blend) elements of two versions together. The elements can include various combinations of structural elements, such as hierarchies, nodes, and properties. The following options are available: Process any combination of adds, moves, or deletes Modify any combination of hierarchies Map top nodes in a source hierarchy to a different node in the target hierarchy. 10-16 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data For the example in the slide, the following differences exist between the source and target versions before the blend: The EastAdmin and EastMarketing nodes exist as children of Connecticut in the source version, but they do not exist in the target version. EastSales is a child of the Massachusetts node in the source version and of the Connecticut node in the target version. After the source is blended into the target version, EastAdmin and EastMarketing are added to Connecticut in the target version and EastSales is moved from Connecticut to Massachusetts. Hyperion System 9 Master Data Management Administration 10-17

Lesson 10 Loading Master Data Module 3 Administering Master Data Blender Elements Blenders consist of the following major elements: Blender attributes Source and target versions Hierarchy sets Property sets Blender Elements You use the Blender Wizard to run blenders. You can set up the source and target version, set options for hierarchy-level blending behavior, copy the blended values to a new version, and so on. To start the Blender Wizard: 1. In Hyperion MDM Client, select File > Import. 2. Perform one of the following tasks: Select New Blender from the list to start a new blender. Select a saved blender from the list to use a previously saved blender. 3. Click Next to continue setting up the blender. 10-18 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data A Blender consists of these major elements: Blender Element Blender attributes Source and target versions Hierarchy sets Property sets Description Attributes of the Blender itself; for example, versions being blended, default values, and so on. The two versions being blended. Blending can occur from the source into the target, or you can create a new version during the blend process. Mappings from the source to the target that indicate 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 they can be mapped directly to existing top nodes, depending on the Blender settings. Also called hierarchy/top-node pairs. Lists of properties to be blended. Properties can be blended in one of three ways: All None Selected If you choose Selected, the selected property set determines which properties are blended. Hyperion System 9 Master Data Management Administration 10-19

Lesson 10 Loading Master Data Module 3 Administering Master Data Configuring Blender Versions and Hierarchies Configuring Blender Versions and Hierarchies You must select the source version that you want to blend and the target version into which to blend the source version. Instead of blending the target into the source, you can merge the source and target versions into a new version. The following table describes the available options: Option Version Copy to New Version Apply to All Hierarchies Description Specify the source and target versions. Specify that the blended values are stored in a new version rather than in the target version. If selected, you must enter an abbreviation to name the version. The description is optional. Apply 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. 10-20 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Option Property Select Options Allow Hierarchy Creation Allow Leaf Promotion Process Moves Description Specify the properties to be included in the blend process: All: All properties are blended. None: No properties are blended. Selected: A selected subset of properties are blended. If you choose Selected, click the browse button to select properties in the Select Properties dialog box. In the Propagate Mode dropdown list, select one of the following modes to determine how the property is populated in the target: Difference: Populates the property for any node where the value is different, regardless of how that property is populated in the target. This is the most commonly used mode. Defined: The property is blended only when it is specifically defined for the node in the source. Force: The property is assigned for every node in the target, whether that property is defined at that node, is inherited, is read/ read and write inherited, and so on. This option should be used with caution. Select Propagate Property Locks if you want locks in the source to be blended into the target. Create hierarchies in the target version that exist only in the source version. If not selected, and hierarchies are being blended that exist only in the source and not in the target, an error occurs. Promote nodes in the source that contain children to limbs in the target. 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), this option allows 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. Select to cause any node that has a different parent in the source to be moved to that parent in the target. Hyperion System 9 Master Data Management Administration 10-21

Lesson 10 Loading Master Data Module 3 Administering Master Data Option Process Inserts Process Removes Description Select to cause nodes that exist only in the source to be added to the target. Select to cause nodes that exist 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 user s discretion. When you set the remove mode to Mark, the Remove Indicator field designates which property contains the value showing that the node is flagged to be removed. 10-22 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Setting Up Top Nodes Setting Up Top Nodes You can map hierarchy structures in the source version to hierarchy structures in the target version by defining blender hierarchy sets. Each blender hierarchy set maps a hierarchy and node in the source version to a hierarchy and node in the target version. The descendants of the node in the source version are blended into the descendants of the target node. You can select any node in the source or target hierarchy as the top node for the blend, including leaf nodes. The default is Blend all Hierarchies. NOTE If you accept the default selection, no other options are available. Hyperion System 9 Master Data Management Administration 10-23

Lesson 10 Loading Master Data Module 3 Administering Master Data To set up top nodes: 1. Click New to add a new hierarchy set. The Blender Hierarchy Set dialog box is displayed. 2. Click the select node button to browse through the source version and select a hierarchy and a top node. 3. Perform one of the following tasks to select target version hierarchy and nodes: To use the same hierarchy and nodes in the target version as in the source version, select the Use Same as Source check box. To use a different hierarchy and nodes for the target version than for the source, proceed to step 4. 4. Perform one of the following tasks to use a different hierarchy and nodes for the target version: To create a new hierarchy and top node in the target, enter names in the Hierarchy and Top Node text boxes. These text boxes are available only if the Allow Hierarchy Creation option for the Blender is selected. Otherwise, you must select an existing hierarchy and node. To select an existing hierarchy and top node, click the select node button, browse through the target version, and then select a hierarchy and top node for the blend. The same hierarchy/top-node settings options are available on this page as on the Version/Hierarchy Settings page. If you selected Apply to All Hierarchies on the previous page, then the Use Blender Defaults check box is selected on this page; the default values from the Version/Hierarchy Settings page are used, and the corresponding options in this section are not available. Otherwise, you can configure the settings individually for each hierarchy set. 10-24 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Selecting Blender Options Selecting Blender Options The following table describes the general processing options that you can select for the Blender: Option Max Iterations Max Errors Description Set the maximum number of Blender attempts to reconcile source and target versions. This option prevents the Blender from running indefinitely in case of irresolvable conflicts. It is recommended that you set this option to 3. Set the maximum number of allowable processing errors before the Blender aborts. Hyperion System 9 Master Data Management Administration 10-25

Lesson 10 Loading Master Data Module 3 Administering Master Data Option Property Propagate Mode Propagate Property Locks Blender Status Properties Description Select a mode to determine how each property is populated in the target: Difference: The property is populated for any node where the value is different, regardless of how that property is populated in the target. This is the most commonly used mode. Defined: The property is blended only when it is specifically defined for the node in the source. Force: The property is assigned for every node in the target, whether that property is defined at that node, is inherited, is read and write inherited, and so on. This option should be used with caution. Select to blend locks in the source with the target. Blender status properties are special values that are set during Blender processing to indicate the actions taken on a particular version, hierarchy, or node. They allow auditing of Blender activity to determine which elements were affected. Select the Clear Values check box to set all blender status property values to False during processing. Select the Populate Values check box to set each blender status property to True during processing. You can then select each property from the drop-down lists. 10-26 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Running Blenders and Viewing Results Running Blenders and Viewing Results After configuring the settings, you can initiate Blender processing by clicking the Run button. When the Blender is finished, the Blender Results dialog box displays the error count, the status, and a list of messages generated during the process. If you selected Copy to New Version on the Version/Hierarchy Settings page, the new version is in a disconnected state; that is, the data is not yet permanently saved. After verifying the blended data, you can save it by right-clicking the version in the Version Control window. Hyperion System 9 Master Data Management Administration 10-27

Lesson 10 Loading Master Data Module 3 Administering Master Data Importing Data to Existing Versions You use Automator to import data to existing versions. Importing Data to Existing Versions You can use the Automator feature to update existing versions in a Hyperion MDM application. Automators enable you to make bulk changes to MDM versions and hierarchies by performing node and property manipulations that are defined in a flat file format. Each flat file row defines an action; for example, adding or inserting nodes to modify existing hierarchies. Each row in the flat file is read and the appropriate actions are performed sequentially. If any errors are encountered, a status message is displayed in the Automator window. Using automators, you can maintain data in an external system and feed it into Hyperion MDM applications on a periodic basis. For example, you may have a chart of accounts in a legacy system that does not permit you to import data from external systems. In this case, you can maintain the data in the legacy system and update the Hyperion MDM application with changes extracted from the legacy system. 10-28 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Automator File Format Action Param1 Param2 Param3 Param4 Param5 Param6 AddHier Ver Hier Desc TopNode Desc ResultDesc DeleteHier Ver Hier ResultDesc Add Ver Hier Abbrev Parent Leaf ResultDesc Insert Ver Hier Abbrev Parent ResultDesc AddInsert Ver Hier Abbrev Parent Leaf ResultDesc ChangeProp Ver Hier Abbrev PropLabel Value ResultDesc RemoveProp Ver Hier Abbrev PropLabel ResultDesc LockProp Ver Hier Abbrev PropLabel Lock ResultDesc PropCompare Ver Hier Abbrev PropLabel Value ResultDesc Ver Hier Version name Hierarchy name Abbrev Leaf Node name 0 = Limb, 1 = Leaf Automator File Format Automators import data from delimited text files. The columns in the flat file must adhere to the following format. The first column 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 is 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, columns 2 through 4 contain the names of the version, hierarchy, and node upon which the action is to be performed. Columns 5 and 6 show other parameters that are relevant to each action. Hyperion System 9 Master Data Management Administration 10-29

Lesson 10 Loading Master Data Module 3 Administering Master Data The following table describes the most commonly used automator actions. Action Rem Add Insert AddInsert Delete Destroy Activate Inactivate Remove Move Annul AnnulAllBelow ChangeProp RemoveProp RemoveDupProps ClearPropsBelow LockProp Purpose Indicates a remark or comment row in the spreadsheet. Any arbitrary text can be entered in other columns of this row for documentation purposes it is ignored by the automator process. Adds the specified node to the specified hierarchy. This action can be used only for a node that does not already exist in the specified version. Inserts the specified node into the specified hierarchy. This action can be used only for nodes that already exist in another hierarchy in 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 given. 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 given. Removes the specified node from the hierarchy. Moves the specified node within the hierarchy. Annuls the specified node. Annuls all nodes below the specified node. Updates the value of the given property of the specified node. Removes (clears) the value of the given property of the specified node. The property itself is not deleted because many other nodes may be using this property. Removes (clears) duplicate properties for the specified node. Corresponds to the Remove Duplicates command that is available to users in Hyperion MDM. Clears the values of the given property in all of the specified node s children. Corresponds to the Clear All Below command that is available to users in Hyperion MDM. Locks or unlocks the given property of the specified node. 10-30 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data PropCompare NodeHasAsParent UpdateVersion PropValue RemoveVersion PropValue AddOrphan AddHier DeleteHier ChangeHierTopNode UpdateHier PropValue RemoveHier PropValue Returns True if the value of the given property of the specified node is equal to the value listed in the spreadsheet; 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. 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 given hierarchy. Updates the value of a hierarchy property. Removes (clears) the value of a hierarchy property. Hyperion System 9 Master Data Management Administration 10-31

Lesson 10 Loading Master Data Module 3 Administering Master Data Performing Imports by Using Automator 1. Create a flat file. 2. Run Automator. 3. Review the results. Performing Imports by Using Automator To import data in batch mode by using the automator process, you perform the following tasks: 1. Create a flat file based on the file format template to define each action to be performed. 2. Run Automator from within the Hyperion MDM client. 3. Check for the failure of any specified actions and review the associated error messages. To run the automator process: 1. From the menu bar, select File > Automator. The Automator window is displayed. 10-32 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data 2. In the Script File text box, type the full path to the flat file. 3. Optional: Click the Options button to configure any file options as necessary. 4. Click Load. The content of the flat file is loaded into the Automator window. 5. Select the actions that you want to process. By default, all actions are selected. 6. Click the Process button. The selected actions are processed in the order in which they are defined in the Automator window. You can monitor the status of each action (for example, Unprocessed, Failure, Success) in the Status column. Hyperion System 9 Master Data Management Administration 10-33

Lesson 10 Loading Master Data Module 3 Administering Master Data Reviewing Automator Processing Results Reviewing Automator Processing Results When the processing is complete, the status of each action and any processing errors is displayed in the Automator window. You can review the results in one of the following ways: Review the content of the Status and Return Value columns in the Automator window. Click the Save or Save As button to save the results in the Status and Return Value columns to the original or a new file, and then open the file to examine its content. 10-34 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 10 Loading Master Data Summary In this lesson, you should have learned to: Describe importing data features Import master data to new versions Combine versions Import master data to existing versions Hyperion System 9 Master Data Management Administration 10-35

Lesson 10 Loading Master Data Module 3 Administering Master Data 10-36 Hyperion System 9 Master Data Management Administration

L E S S O N 1 1 Exporting Master Data 11 Objectives At the end of this lesson, you should be able to: Describe exporting features Create data exports Create export books

Lesson 11 Exporting Master Data Module 3 Administering Master Data Exporting Data Overview Purpose: To create delimited text files for transfer to external systems To create reports for review and audit Exporting Data Overview Hyperion Master Data Management provides a centralized master data repository that you can use to import hierarchies from different external systems and to merge them into one version. By maintaining master data in one centralized repository, you can synchronize changes across all enterprise applications and reduce maintenance costs. Exports are tools that you use to transfer hierarchy data to external systems. They are used to extract master data from Hyperion MDM applications and import that data to external systems. Exports are sometimes referred to as reports or extracts. Exports also serve as the main reporting mechanism for reviewing and auditing master data changes across the enterprise. Exports offer the following advantages: You can use queries to filter the nodes that are selected based on properties that are created to support the specific needs of the target systems. You can preview, print, and save the results in a file or a database table. 11-2 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data You can group exports into books and run them in batches. You can send book output to separate files or combine it in a single file. You can create and save exports for repeated use. Creating Exports You use the Export wizard to create exports. To launch the Export wizard: 1. From the menu bar, select File > Export/Report. The Select Export/Book window is displayed. 2. From the list of predefined export classes, select an export type. 3. From the corresponding drop-down lists, select a current version (and if necessary a previous version) and then click Next. Export Classes Several basic export types are built in to Hyperion MDM and can be customized based on user needs. The following table describes the export types. Export type Generation Hierarchy export Hierarchy Compare export Hierarchy Difference report Hierarchy export Lookup export Description Used to produce generation builds. Supports fixed levels and node repeating to transform a natural hierarchy (that is, one with mixed levels) into a fixed-level hierarchy (that is, a balanced tree ). Used as a delta (difference) export to generate only the differences between hierarchies. A column-based export that is easy for external systems to access. Used as a delta (difference) export to generate differences. A sectioned report that is designed for analysis by people rather than by external systems. Fundamental building block that is used as the basis for the majority of exports from Hyperion MDM to external systems. Lists lookup pairs for a single, designated lookup property. Useful for properties with a large list (hundreds or more) of lookup pairs that require review through a readable text file. Hyperion System 9 Master Data Management Administration 11-3

Lesson 11 Exporting Master Data Module 3 Administering Master Data Export type Merge Log export Property List export Transaction Log export Version export Ancestor export Description Exports information defining the transformations required to move data allocated to previously deleted (or inactivated) nodes. Reports on allowed values for a designated list property. Similar to Lookup export, it is used only for properties with large lists of values that require review through a readable text file. Exports the transaction logs with the ability to filter the export on multiple columns. Exports all nodes regardless of hierarchy, including orphan nodes (nodes that are not allocated to any hierarchy in a version). Used to export a basic list of nodes without any local properties or structural information. Exports an ancestor list for each node in the hierarchy. The Generation export type is generally used instead of Ancestor. 11-4 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Exporting Hierarchies Exporting Hierarchies Hierarchy exports are used as the basis for the majority of exports from Hyperion MDM to external systems. To perform a hierarchy export: 1. From the Exports tree, select Hierarchy Export. 2. From the Current drop-down list, select a version. 3. Optional: Click the ellipsis button to specify additional version criteria. 4. Click Next. The Top Nodes page of the wizard is displayed. Hyperion System 9 Master Data Management Administration 11-5

Lesson 11 Exporting Master Data Module 3 Administering Master Data Specifying Top Nodes Specifying Top Nodes You use the Top Nodes page in Hierarchy exports to select the top nodes of the hierarchies to be exported. Data for the selected node and its descendants is exported. You can select as many top nodes from each hierarchy as required. When multiple nodes are added to the list, the data is exported in the order in which the nodes appear. You can optionally use a list of nodes in a text file as a filter. You can choose either to include in the export only the nodes listed in the text file or to exclude from the report the nodes listed in the text file. To select top nodes for the export: 1. Click Add. The Select Node dialog box is displayed. 2. Perform the following actions: 11-6 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data a. From the Hierarchy drop-down list, select a hierarchy. b. Expand the hierarchy tree and select a top node. c. Click OK. 3. Optional: Repeat steps 1 and 2 to select additional top nodes. 4. Click Next. The Select Columns page of the wizard is displayed. Hyperion System 9 Master Data Management Administration 11-7

Lesson 11 Exporting Master Data Module 3 Administering Master Data Selecting Export Columns Selecting Export Columns The Select Columns 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. To select which columns to include in an export, perform the following tasks: Move the properties that you want to include in the export from the Available list to the Selected list. Use the arrow buttons to the right of the Selected list to change the display order of the selected columns. TIP The order in which the properties are displayed in the Selected list determines the order of the columns in the export output file. Optional: Use the Category drop-down list to make navigation of the Available list easier by restricting it to properties for a single property category. 11-8 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Specifying Column Options Specifying Column Options You use the Column Options page of the wizard to configure options for each column in a hierarchy export. If the field value is equal to the default value, select the Skip Defaults check box to place a blank in the export. If the field contains multiple comma-delimited values, select the Pivot check box. 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 can be selected on just a single column. Select the Primary Key check box to define a column (or columns) as the primary key to be used to determine whether duplicates exist. Hyperion System 9 Master Data Management Administration 11-9

Lesson 11 Exporting Master Data Module 3 Administering Master Data Setting Export Parameters Setting Export Parameters You use the Parameters page to specify additional required export options. The options on this page vary depending on the type of export. The following table describes the options for hierarchy exports. Option Node Selection Options Hierarchy Options (Recurse from Top Nodes) Duplicate Options (Remove Duplicates Based on Key) Format Options (Tabbed Output) Description Defines whether all nodes are included in the export, or just those that are limbs or leaves. Specifies whether the export should include a row for all descendants of the top node selected. If not selected, only the selected top node is included in the export (this is usually not the desired result). Specifies whether the primary key defined on the Column Options page should be used to suppress the export of duplicates. Specifies whether a tab character should be inserted for every level of the node (so that it resembles a hierarchy when imported into other applications, such as Excel). 11-10 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Defining Filters and Verifications Defining Filters and Verifications You use the Verification/Filter page to select a verification and to filter export results. Applying Verifications You can select any available verification from the drop-down list and apply it to the export. When you select a verification, only nodes that pass the verification are included in the export. Applying Filters To filter export results, you select a property filter. Property filters restrict export results based on criteria that are defined in a property query. You can select an existing property query from the Property Filter drop-down list, or you can create a new property query. When you select a property filter, only nodes that meet the property query criteria are included in the export. Hyperion System 9 Master Data Management Administration 11-11

Lesson 11 Exporting Master Data Module 3 Administering Master Data Configuring Output Formats Configuring Output Formats You use the Output Formatting page to specify formatting options for export results. The following table describe the formatting options. Option Column Headings Quoted Strings Fixed Width Field Delimiter Record Delimiter Description Specifies whether to include column headings in the export. Encloses strings in quotation marks. Allows the explicit specification of column widths and separators. If this option is selected, the next page presented is the Column Widths page. This option can be combined with the Field Delimiter option. Specifies the character to be used as a field delimiter for columns. This option can be combined with the Fixed Width option. Specifies the record delimiter character. 11-12 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Option Header and Footer options Blank Line Between Header/Footer and Body Replace options Description Specifies the text to be printed on the header and footer of the export results. You can enter multiple lines of text either directly into the text box or in the pop-up text editor accessed by clicking the ellipsis button. You can use customization tags to include additional information. Improves the readability of headers and footers by adding white space. Replaces up to three characters from the lists on the left with the characters selected from the lists on the right. All instances in the export output are replaced as specified. For example, all parentheses can be replaced with braces. You can also insert customization tags in the headers and footers to enhance the readability of the export results. The tags use the format <%Tagname(parameters)%> and are replaced with the appropriate value at runtime. In the following list, optional parameters are enclosed in brackets ([]). The following customization tags are available. Customization Tag <%Date[(format)]%> <%Time[(format)]%> <%Timestamp%> <%CurrentUser%> <%CurrentVersion%> <%PreviousVersion%> <%ExportName%> <%FileName%> <%RecordCount%> <%AppVersion%> <%PropValue([Previous Curre nt(default)], PropName)%> <%PropValue([HierName], PropName)%> <%PropValue(PropName)%> Description Returns the current date in the format MM/DD/YYYY. Returns the current time in the format HH:MM:SS AMPM. Returns a combination of date and time. Returns the user ID of the current Hyperion MDM user. Returns the current Hyperion MDM version for this export. Returns the previous Hyperion MDM version for this export. Returns the name of the export. Returns the output file name if specified. Otherwise, returns the default file name. Returns the count of records exported (available only in the footer). Returns the Hyperion MDM product number (for example, 9.0.4.12) For Compare/Difference Exports, returns the value of the first node in CompareCriteria for the Previous/Current version. For Hierarchy Exports, returns the value from the first node in the list. If HierName is supplied, returns the value from the first node that matches HierName. For Version Exports, returns only version properties. Hyperion System 9 Master Data Management Administration 11-13

Lesson 11 Exporting Master Data Module 3 Administering Master Data Specifying the Output Destination Specifying the Output Destination The Output Destination page is the final page in the sequence for all export types; it determines the destination of the export output. Select one of the following options and click Run to generate the export results. File: Results are written to a file. Enter a file path or browse to the location where the file is stored. Preview: Results are displayed in a pop-up window. Table: Results are written to a database table. Click the ellipsis button to configure this option. 11-14 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Saving and Deleting Exports Saving and Deleting Exports You can save exports for repeated use. You can save exports as either standard exports or private exports. A standard export is a public export that can be run by any user. A private export can be run only by the user who created it. Any user can create and save a private export. Only administrators can create standard exports. End users can modify standard exports according to their needs and save them as private exports. To save an export: 1. Click the save button or the save as button on the Export window toolbar. The Save As dialog box is displayed. 2. In the Name text box, type a name. 3. Optional: In the Description text box, type a short description. Hyperion System 9 Master Data Management Administration 11-15

Lesson 11 Exporting Master Data Module 3 Administering Master Data 4. Optional: Select the Standard check box to save the export as a standard export. 5. Click OK. To delete an export: 1. Click the name of the export that you want to delete. 2. On the toolbar, click the delete button. A warning message is displayed. 3. Click Yes to confirm the deletion. 11-16 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Creating Generation Exports Creating Generation Exports Generation exports output hierarchies in a generation-based or level-based format. You use the Select Columns, Repeat Parameter, and Exclusion Filter wizard pages to configure additional options for generation exports. Selecting Columns For exports that are based on the Generation Export class, when you select node properties, you can assign them to one or more of the following column sets: 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 Hyperion System 9 Master Data Management Administration 11-17

Lesson 11 Exporting Master Data Module 3 Administering Master Data Configuring Repeat Parameters You select options on the Repeat Parameter page to generate exports for destination systems that require fixed-depth hierarchies (also called balanced hierarchies). The following table describes the options on the Repeat Parameter page. Option Repeat Num Property Bottom Level Property & Bottom Level Value Repeat Nodes to Enforce Bottom Level Max Ancestor Levels Use Inverted Level Blank Repeated Levels Description Defines a property that repeats a node in an export structure. For example, if node B in an A-B-C parent-child hierarchy has a Repeat Num Property value of 2, then the export looks like A,B,B,C (node B is repeated once). Defines the maximum depth of the export structure. This value can be defined as a hierarchy-level property (Bottom Level Property) or as an absolute value (Bottom Level Value). These options are enabled if a bottom level value is defined. Select one of these options to automatically repeat nodes down to the defined level in the export structure. For example, for nodes A-B-C in a parent-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 (node B is repeated once and the leaf node C is repeated until level 6 is reached). Defines the absolute maximum number of ancestor levels in the export structure. Assigns level values to nodes according to the Essbase level methodology. Typically used to create level-based format exports most suitable for Essbase. Select this box to hide repeated nodes in the output file. Defining Exclusion Filters You use the Exclusion Filter page to define a filter that excludes nodes from the export. For a Generation export, this page is used to define a property filter to restrict the nodes that appear as ancestor columns. Nodes that meet the property filter criteria are excluded from the export. 11-18 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Creating Hierarchy Compare Exports Creating Hierarchy Compare Exports The Hierarchy Compare export outputs the differences between hierarchies. A typical use of this type of export is to send changes only to an external system. You can export the differences between the same hierarchies in two different versions (for example, a previous and the current version), or content differences between hierarchies in the same version. The following list includes tasks that are specific to the Hierarchy Compare Export class: On the Select Export/Book page of the wizard, you must select a version from both the Previous and Current drop-down lists. On the Top Nodes page of the wizard, you must select the top node for both the current and the previous version. Hyperion System 9 Master Data Management Administration 11-19

Lesson 11 Exporting Master Data Module 3 Administering Master Data On the Parameters page, you must select appropriate options to define how the Hierarchy Compare Export output file is generated. The following table describes the options on the Parameters page. Option Additions Deletions Merges Moves Renames Property Updates Description Includes all nodes in the target hierarchy that are not in the source hierarchy. Includes all nodes in the source hierarchy that are not in the target hierarchy. Includes merge information in the export file (if the merge feature is enabled). Includes all nodes that have different parent nodes in the two hierarchies being compared. Includes all nodes that have different names (Abbrev values) with the same internal NodeID in the two compared hierarchies. Includes all nodes that have different values in the specified list of properties in the two hierarchies being compared. On the Verification/Filter page, you can select a property filter to determine the set of nodes from each hierarchy that are compared. For example, when you check for node additions or deletions and do not use a filter, a node that exists in both hierarchies does not show up in the export result. However, if you use a filter and the node meets the filter criteria in one hierarchy but not in the other, then that node appears as a difference (either an addition or a deletion). 11-20 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data Exporting to a Database Table Exporting to a Database Table For certain export types, you can send the output to an external database table. This feature currently supports both Microsoft SQL and Oracle databases. To export data to a database table: 1. On the Output Destination page, select the Table option and click the ellipsis button. The Export to Table dialog box is displayed 2. Select the Output Properties tab. 3. Define a connection string to access the external database. Either enter an existing connection string or click the ellipsis button to build one by using the Data Link Properties dialog box. Hyperion System 9 Master Data Management Administration 11-21

Lesson 11 Exporting Master Data Module 3 Administering Master Data 4. In the Table text box, enter the table name in the external database. TIP The table must exist before the export can run. 5. Enter the user ID and password, if they are not specified in the connection string. 6. Select the Use Transactions check box to cause the export to be performed within a database transaction and to allow the entire operation to be rolled back if an error occurs during the export. 7. Clear the Use Fast Appends check box. Select this check box only when you use a database-specific DAL. 8. In the Clear Table area, select one of the following options: Do not clear table: Causes the export to be appended 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. Delete all rows: Deletes all existing data from the table before writing the export output. Setting Up Table Fields You use the Column Properties tab of the Export to Table dialog box to map each column that is being exported to a field in the external database table. In the Field Name text box, enter the name of an existing field. For fields of type String, specify the length. For all other field types, the length is not used. 11-22 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data If you select the Delete based on Version ID(s) check box on the Output Properties tab of the Export to Table dialog box, you must specify a Key field in the Column Properties tab. When you run the export, 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 you select one of the other options ( Do not clear table or Delete all rows ), the Key field designation is ignored. Hyperion System 9 Master Data Management Administration 11-23

Lesson 11 Exporting Master Data Module 3 Administering Master Data Creating and Exporting Books Creating and Exporting Books You can group saved exports together to create export books. This enables you to run a set of commonly used exports in batch mode. To create an export book: 1. Launch the Export wizard. 2. On the Export page, right-click Books and select New Book from the shortcut menu. The Manage Export Books window is displayed with the Content tab selected by default. 3. In the Name text box, type a name for the new book. 4. Optional: In the Description text box, type a short description. 11-24 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 11 Exporting Master Data 5. Optional: Select the Standard Book check box to make the book available to all users. 6. In 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. 7. Optional: Select the Output tab to configure output options. You can combine the book export into a single file, and you can specify file names and storage locations for the results of the book exports. 8. Click OK. To run an export book: 1. Launch the Export wizard. 2. On the Export page, right-click the name of the book and select Run from the shortcut menu. Hyperion System 9 Master Data Management Administration 11-25

Lesson 11 Exporting Master Data Module 3 Administering Master Data Summary In this lesson, you should have learned to: Describe exporting features Create data exports Create export books 11-26 Hyperion System 9 Master Data Management Administration

L E S S O N 1 2 Managing Security 12 Objectives At the end of this lesson, you should be able to: Describe Hyperion Master Data Management security levels Create and manage node access groups Create and manage users and their privileges Define security by using system preferences

Lesson 12 Managing Security Module 3 Administering Master Data Levels of Security Version Status Determines whether the version can be modified. User Type Determines ability to perform administrative functions. Read Node Access Determines the type of access to each node. Read Edit Edit Property Access Determines the type of access to properties. Levels of Security Hyperion MDM provides security at four levels. Version status: Determines whether a version is open for modification. Even administrators cannot make changes to a version that has Finalized status. User type: Classifies the user as an administrator or a business user. System and functional administrators have full access to all versions, all hierarchies, and all nodes within hierarchies. Security administrators and business users must be granted access to nodes and properties. Node access: Determines which nodes the user can view or edit. Node access is assigned by using node access groups. Property access: Provides an additional level of security below node access. For nodes to which users have been granted access, property access determines which node properties they can view or edit. Property access is assigned by using property categories. 12-2 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Node Access Node access levels are defined through inheritance of property values. Limb Access Leaf Access Default values Read Edit Markets NA West Overridden values Limb Access Leaf Access Insert Edit CA NA East Limb Access Leaf Access Insert Add Limbs inherit Read APAC CT NY Leafs inherit Edit Node Access To simplify security maintenance, node access is designed to support assignment of access levels to nodes through inheritance of property values. The following two local, inheriting system properties are responsible for node access: Limb Access: Determines access level for the node and its limb descendants. Leaf Access: Determines access level for the node and its leaf descendants. By default, the node descendents inherit the values of the Limb Access and Leaf Access properties. You can override these values for a specific node, in which case the corresponding property values for all of its dependants default to the overridden value. In the diagram shown in the slide, the value of Limb Access for West was overridden to Insert; it was inherited by CA. The value of Leaf Access for CA was overridden to Add. The rest of the nodes inherited values from the top node Market. Hyperion System 9 Master Data Management Administration 12-3

Lesson 12 Managing Security Module 3 Administering Master Data The following table describes node access levels. Status Description Example Usage Read Provides read-only access no changes are permitted Viewing and reporting Limited Insert Allows insertion of a node for which the user has (at least) global insert privilege Insert Edit Allows editing of property values Edit Insert Allows insertion, copying, moving, and removing of nodes Edit Insert Copy Move Remove Inactivate Allows inactivation and reactivation of nodes Edit Insert Copy Move Remove Inactivate Reactivate Add Allows addition and deletion of nodes Edit Insert Copy Move Remove Inactivate Reactivate Add Delete 12-4 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Node Access Groups Node access groups control user access to nodes. Node Access Group Limb Access Level Leaf Access Level Limb Access Leaf Access Insert Edit Markets NA West CA US East US West EMEA APAC Insert Add Read None Edit Add Edit None Limb Access Leaf Access Limb Access Leaf Access Add Add Read Edit No access to West Node Access Groups To set access levels for both the Limb Access and Leaf Access properties for each node, you use node access groups. Node access groups are defined only by a system administrator and typically represent functional areas of an organization. When you assign a user to a node access group, the user is granted access to nodes according to the access levels assigned to nodes for the group. You can assign users to multiple node access groups. If there is a conflict in access levels because a user is a member of multiple node access groups, then the highest security level is used. Node Access Groups and Hierarchies If a node access group has access to any node in a hierarchy, then the entire hierarchy is visible to all users who are members of that node access group. This allows users to navigate to the nodes to which they have access. Conversely, if a node access group has no access to any node in a hierarchy, users who are members of that node access group cannot open the hierarchy. Hyperion System 9 Master Data Management Administration 12-5

Module 3 Administering Master Data Lesson 12 Managing Security Global Node Access Groups Global node access groups control user access to nodes across hierarchies. Limb Access Level Add Leaf Access Level Add Limb Access Level Read Leaf Access Level Read US West global node access group Markets Geography NA West Americas CA NA East NA West CA Limb Access Leaf Access Add Add Controlling hierarchy Global Node Access Groups Because Leaf Access and Limb Access are local properties, if a node occurs in more than one hierarchy, you must assign node access groups in each hierarchy to ensure the same access level to the same nodes. Alternatively, you can use global node access groups. When you create a global node access group, you specify a controlling hierarchy for the group. For global groups, the leaf and limb access levels to nodes in the controlling hierarchy are used for all hierarchies in which the nodes occur. For example, suppose that your organization has a Markets and a Geography hierarchy. You determine node access on a market basis, and markets are geographically dispersed. You create global access groups for each market region and assign them to nodes in the Markets hierarchy. 12-6 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Managing Node Access Groups Delete Current Node Access Group Create New Node Access Group Managing Node Access Groups In the Node Access Groups dialog box, you create, edit, and delete node access groups. You create and manage node access groups in the Node Access Groups dialog box. To create a node access group: 1. Select Admin > Node Access Groups. The Node Access Groups dialog box is displayed. 2. Click the create new node access group button. The New Node Access Group dialog box is displayed. 3. Perform the following steps: a. In the Name text box, type a name for the node access group. Hyperion System 9 Master Data Management Administration 12-7

Lesson 12 Managing Security Module 3 Administering Master Data b. In the Description text box, type a description for the node access group. c. Optional: If you want to make the group global, select the Global check box. d. Click OK. The new group is displayed in the Node Access Groups dialog box. To edit a node access group: 1. From the Current drop-down list, select a node group to edit. The definition of the selected node access group is displayed in the Node Access Groups dialog box. 2. Modify the required information and then click OK. 3. Click OK. The Information message box is displayed. To delete a node access group: 1. From the Current drop-down list, select a node group to delete. 2. Click the delete current node access group button. The Warning message box is displayed. 3. Click Yes. Assigning Node Access Groups to Users You use the two lists at the bottom of the Node Access Groups dialog box to assign users to a node access group. The Selected Users list shows users that are currently members of the group. The Available Users list shows users that are not currently members. To include a user in or exclude a user from a group, select the user and then click the appropriate arrow. 12-8 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Defining Controlling Hierarchies Global Node Access group Version Controlling hierarchy Defining Controlling Hierarchies For global node access groups, you define controlling hierarchies on the Controlling Hierarchies tab. The tab displays versions and their hierarchies in the form of two related lists. You can define only one controlling hierarchy per version. To define a controlling hierarchy, you first select a version from the list and then select the desired hierarchy on the right. Hyperion System 9 Master Data Management Administration 12-9

Lesson 12 Managing Security Module 3 Administering Master Data Assigning Node Access Groups to Hierarchies Node Access tabs Right-click menu Selected node Node access groups Access levels Assigning Node Access Groups to Hierarchies You assign node access by using the Leaf Access and Limb Access tabs in the Property Editor. Each of these tabs displays a list of the node access groups that are defined in the application. You select an access level for each node access group. If the selected node is a parent, the access level is inherited by its descendants. NOTE If the Leaf Access and Limb Access tabs are not visible in the Property Editor, right-click and select Show Access/Verification Properties from the shortcut menu. Alternatively, you can select Show All Properties from the shortcut menu. For users who are not system administrators, the Leaf Access and Limb Access tabs are not displayed. Instead, the System tab page displays Leaf Access and Limb Access properties. These properties are read-only; they display the access level assigned to the node for the node access group to which the user belongs. If the user belongs to multiple node access groups with different access levels, the Leaf Access and Limb Access properties display the highest access level. 12-10 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Property Access Property access is controlled through property categories. Read Edit Property Access Property categories provide an additional layer of security beneath node access. All user-defined properties are assigned to one or more property categories. Users are assigned read, write, or no access to each property category. If the user has no access to a property category, the tab for that property category is not displayed in the Property window. To modify the value of a property for a node, users must have at least Edit access to the node and Edit access to the property category to which the property belongs. Hyperion System 9 Master Data Management Administration 12-11

Lesson 12 Managing Security Module 3 Administering Master Data Assigning Property Categories to Users 1. Select Admin > Property Categories. 2. Select a property category. 3. Select users. 4. Define read/write access. Assigning Property Categories to Users Determining whether users need full access or read-only access to property categories may help you to determine how properties should be categorized. To assign a property category to users, select Admin > Property Categories. On the Users tab, you assign a property category to users. The list on the right shows users to which the property category is assigned. The list on the left shows users to which the property category can be assigned. To change a property s assignment, select a user and click the appropriate arrow. The Read Only check box indicates whether the user has read-only or read and write access to the property category. 12-12 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Managing Users 1. Select Admin > User Management. 2. Define user credentials: Username Password User type Personal data 3. Specify authentication method: Internal External 4. Assign user permissions: Node access Property access 5. Monitor login status. Managing Users System administrators and security administrators manage Hyperion MDM users by using the User Management dialog box. To open this dialog box, from the Master Data Management Services main menu, select Admin > User Management. For each Hyperion MDM user, you define user credentials, specify the preferred authentication method, and assign node access and property access. The User Management tool also enables you to monitor user login status. You cannot rename users. When you delete a user, all exports that have been saved by the user are also deleted. Hyperion System 9 Master Data Management Administration 12-13

Lesson 12 Managing Security Module 3 Administering Master Data Creating Users Create personal logins. Determine which users require administrative access. Creating Users It is recommended that you assign every Hyperion MDM user a personal login. Avoid using generic or department-wide logins. To create a new user: 1. In the User Management dialog box, click Create New User. The New User dialog box is displayed. 2. Optional: Select the Clone User check box and then select a user from the drop-down list. When creating a user account, you can use the Clone User option to copy information (Department, Phone, User Type, Node Access Groups, and Property Categories assignments) from an existing user to the new user. Otherwise, you can enter the information for the new user in each field. 12-14 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security 3. In the User Name text box, enter a user name of up to 20 characters. 4. In the Full Name text box, enter the user full name of up to 40 characters. 5. Optional: Enter the phone number and department of the user. 6. From the User Type drop-down list, select the user type. 7. If the user authentication mode was defined as Mixed during installation, then in the Authentication section select one of the following: Manage User within MDM Service: This mode enables password information in the New User dialog box. Manage User in Active Directory, LDAP or NTLM: This mode disables password information in the New User dialog box. 8. If you selected the Manage User within MDM Service authentication mode in the previous step, perform the following steps: a. In the Password text box, enter the user password. b. In the Confirm Password text box, retype the user password. c. Optional: Select one of the following options: - User must change password at next logon: The user must change the password at the next login attempt. The expiration period starts after the change is made. - Select Password never expires: The user can use the password indefinitely. 9. Click OK. The user is created. You can now assign node access and property access to the new user. Hyperion System 9 Master Data Management Administration 12-15

Lesson 12 Managing Security Module 3 Administering Master Data Assigning User Permissions Node Access Groups Property Categories Assigning User Permissions You manage user permissions to nodes and properties in the User Management dialog box. NOTE You can also assign user permission through dialog boxes for managing node access groups and property categories. Assigning Node Access Groups You use the Node Access Groups tab to assign node access groups to a user. The Selected Node Access Groups list on the right shows groups to which the user is assigned. The Available Node Access Groups list on the left shows groups to which the user can be assigned. 12-16 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security To include a user in a group or exclude a user from a group, select the group and click the appropriate arrow. Assigning Property Categories You use the Property Categories tab to assign property categories to a user. The Selected Categories list on the right shows categories to which the user is assigned. The Available Categories list on the left shows categories to which the user can be assigned. To change a user s assignment, select a category and click the appropriate arrow. The Read Only check box indicates whether the user has read-only or read and write access to the selected category. Hyperion System 9 Master Data Management Administration 12-17

Lesson 12 Managing Security Module 3 Administering Master Data Locking Out and Unlocking Users Users can be locked out automatically or manually. Security administrators unlock individual users. System administrators configure lockout-related system preferences. Lockout/Unlock User button Lockout message Lockout information Locking and Unlocking Users You can lock out users and provide a lockout reason by clicking the Lockout/Unlock User button in the User Management dialog box. The lockout information becomes visible on the Login Status tab. When a locked out user attempts to log in, a standard lockout message is displayed in the Error message box. To unlock a user, you click the Lockout/Unlock User button again and confirm the change. As a system administrator, you can set system preferences to define lockout policy in your company. The following system preferences relate to user lockout: System Preference LockoutExcludeFuncAdmin LockoutExcludeSecAdmin Description Excludes functional administrators from automatic login lockouts. Set to True to enable; otherwise set to False. Excludes security administrators from automatic login lockouts. Set to True to enable; otherwise set to False. 12-18 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security LockoutExcludeSysAdmin LockoutExcludeUsers LockoutInactivity LockoutInvalidLogins Excludes system administrators from automatic login lockouts. Set to True to enable; otherwise set to False. Comma-separated list of users to exclude from automatic login lockouts. Maximum number of inactive days before a user is locked out. Zero value indicates no maximum. Maximum number of invalid logins before a user is locked out. Zero value indicates no maximum. Hyperion System 9 Master Data Management Administration 12-19

Lesson 12 Managing Security Module 3 Administering Master Data Changing User Passwords Users change their passwords by selecting Tools > Change Password. Security administrators reset user passwords in the User Management dialog box. System administrators configure password-related system preferences. Changing User Passwords Users can change their passwords in the Change Password dialog box. Security administrators can reset user passwords in the Set Password dialog box. To access the Set Password dialog box, click the Change Password toolbar button in the User Management dialog box. As a system administrator, you can set system preferences to define password policy in your company. The following system preferences relate to user passwords: System Preference PasswordDuration Description Number of days that a user's password is valid. PasswordWarningPeriod Positive or negative number to indicate how many days before (-) or after (+) the password expiration date to warn users to change their password. PasswordMaxLength PasswordMinLength Maximum length for user passwords. Zero indicates no maximum. Minimum length for user passwords. Zero indicates no minimum. 12-20 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security System Preferences and Security You can use the security options in the System Preferences dialog box to further define access to tasks based on user type. System Preferences and Security There are system preferences that specify the type of user allowed to perform certain actions. The possible values for these system preferences are Admin, Any, and None. A value of Admin indicates that only administrators have access to the feature. A value of Any indicates access for any user level. A value of None indicates no access. The following table describes the system preferences that relate to security. System Preference AllowNextIDKeyCreation AllowPropCopyOnAdd EnablePropCopyOptions Inactivate InactiveChanges Description Allow Next ID key creation level Allow copying of properties when adding new node Enable property copy options Level required to allow node inactivation Allow changes to inactive node Hyperion System 9 Master Data Management Administration 12-21

Lesson 12 Managing Security Module 3 Administering Master Data LeafEdit NdTpDAll RenameLeaf RenameLimb Allow leaf property to be edited Allow Show All Properties to override node type Level required to rename Leaf Level required to rename Limb 12-22 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 12 Managing Security Summary In this lesson, you should have learned to: Describe Hyperion MDM security levels Create and manage node access groups Create and manage users and their privileges Define security by using system preferences Hyperion System 9 Master Data Management Administration 12-23

Lesson 12 Managing Security Module 3 Administering Master Data 12-24 Hyperion System 9 Master Data Management Administration

L E S S O N 1 3 Auditing Master Data 13 Objectives At the end of this lesson, you should be able to: Describe tracking master data View baseline versions and transaction history Create transaction history reports Create As Of versions Analyze hierarchy differences

Lesson 13 Auditing Master Data Module 3 Administering Master Data Tracking Master Data Changes Initial version created Timeline Changes made Baseline version Current version Transaction history Tracking Master Data Changes When you create a new version or copy a version, Hyperion System 9 Master Data Management creates two versions: Baseline version: An initial snapshot of the version from where you start the master data management cycle. Changes that you make to the master data do not apply to the baseline version. Normal version: A working version in which you make changes to master data. All operations that you perform in Hyperion MDM are logged in the transaction history. Each operation is recorded with a time stamp, the username, the type of action performed, and other relevant information. NOTE The AllowAsOf system preference must be set to True to enable baseline versioning. 13-2 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 13 Auditing Master Data Viewing Baseline Versions Viewing Baseline Versions The baseline version is read-only and is not displayed in the Version Control window. You view a baseline version by opening its hierarchies. To open a hierarchy of a baseline version: 1. In the Version Control window, select a version, right-click, and then select Open Baseline from the shortcut menu. The Open Hierarchy dialog box is displayed. 2. Select the hierarchies that you want to open for the baseline version and then click OK. The selected hierarchies are displayed in the corresponding hierarchy windows. Hyperion System 9 Master Data Management Administration 13-3

Lesson 13 Auditing Master Data Module 3 Administering Master Data Viewing the Transaction History The transaction history records all user actions and data changes. Select Tools > Transaction History to view transaction records. Viewing the Transaction History The transaction history records all changes to Hyperion MDM application master data, such as property definitions, system preferences, and export profiles. It also records all user actions, including user management and logging actions. To view transaction records, select Tools > Transaction History. In the Transaction History dialog box, you can restrict displayed records to a desired date/time range or transaction ID range. After setting the desired range, click the Refresh button to display data within the range. You can also filter records on other columns, including version, hierarchy, node, action, level, user, and property. Select the Filter to Current Session check box to limit the display to only those operations performed by the current user logged in to Hyperion MDM. Set the Max Records value to limit the number of transactions displayed. Use the Automate button to save the transactions as an automator file or to process them through the Automator. 13-4 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 13 Auditing Master Data Viewing Transaction History Details Viewing Transaction History Details To view the details of a specified transaction, select the record in the grid and then press F11. This opens the Transaction History Detail dialog box, in which you can view the transaction details such as version ID, hierarchy ID, and node ID. If the transaction updated a property value, then you can also view the value that the property had before and after the transaction. Hyperion System 9 Master Data Management Administration 13-5

Lesson 13 Auditing Master Data Module 3 Administering Master Data Exporting the Transaction History 1. Select File > Export/Report. 2. Select Trans Log Export. 3. Select transaction details. 4. Define transaction: Range Action Filter 5. Specify: Export formatting Output destination Exporting the Transaction History You use the Hyperion MDM Export Wizard to export the transaction history. The wizard walks you through the steps for defining transaction history details to be exported as well as report parameters. 13-6 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 13 Auditing Master Data Analyzing Master Data Changes 3 days ago Baseline version As Of version (correct) Current version (incorrect) Run compares Transaction history Analyzing Master Data Changes Transaction history and baseline versions enable you to analyze changes made to hierarchies during a certain period of time in the master data management cycle. It is possible to roll the baseline version forward to any point in time to generate a snapshot at that point. That snapshot is called an As Of version. As Of versions are created in memory with the status Expired/Detached. You cannot modify the hierarchies or node properties of As Of versions, but you can display their hierarchies, run compares, or export master data. For example, if you discover that the current version contains incorrect information and you want to investigate what changes to the master data caused the problem, you can create an As Of version as of some past date and time when the version contained correct information, and then run compare tools to analyze the differences between the As Of version and the current version. This is usually less difficult than analyzing the transaction history for the same period of time. Hyperion System 9 Master Data Management Administration 13-7

Lesson 13 Auditing Master Data Module 3 Administering Master Data Creating As Of Versions Access to Transaction History As Of version created Creating As Of Versions To create an As Of version: 1. In the Version Control window, select a version, right-click, and select Create As Of from the shortcut menu. The Create Version As Of dialog box is displayed. 2. Select one of the following: Transaction Date/Time: Specify a date and time as of which you want to create the version. Transaction Date Offset: Specify a date and time offset from the current date. Transaction ID: Specify the ID of the desired transaction. To look up the transaction ID, click the Transaction History button next to the field. 13-8 Hyperion System 9 Master Data Management Administration

Module 3 Administering Master Data Lesson 13 Auditing Master Data Exporting Hierarchy Differences 1. Select File > Export/Report. 2. Select Hierarchy Difference Report. 3. Provide specific report parameters. Exporting Hierarchy Differences After you have created an As Of version, you can create a report that lists the differences between the As Of version and the current version. For that purpose you use the Hierarchy Difference report available in the Exports dialog box. The Hierarchy Difference report is similar to the Compare export, but its format is more readable than that of the column-based Compare export. The Hierarchy Difference report parameters are the same as on the Hierarchy Compare Export Parameters page, except for the Fixed Width Columns fields that 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. Hyperion System 9 Master Data Management Administration 13-9

Lesson 13 Auditing Master Data Module 3 Administering Master Data Summary In this lesson, you should have learned to: Describe tracking master data View baseline versions and transaction history Create transaction history reports Create As Of versions Analyze hierarchy differences 13-10 Hyperion System 9 Master Data Management Administration

A P P E N D I X A Hyperion MDM Implementation Guidelines A Objectives After completing this lesson, you should be able to: Describe the process of implementing a Hyperion Master Data Management application Describe the implementation tasks

Appendix A Hyperion MDM Implementation Guidelines Implementation Process Overview 1. Discovering the environment 2. Identifying business requirements 3. Designing Master Data Management application structure 4. Loading and analyzing master data 5. Preparing for rollout 6. Going live Implementation Process Overview Implementing Hyperion Master Data Management applications is a large discovery process that can be broken down to the following main tasks: 1. Discovering the environment 2. Identifying business requirements 3. Designing Master Data Management application structure 4. Loading and analyzing master data 5. Preparing for rollout 6. Going live A-2 Hyperion System 9 Master Data Management Administration

Hyperion MDM Implementation Guidelines Appendix A Discovering the Environment During the discovery phase you analyze and identify Data systems Functional differences General ledger Human resources Planning Interfaces Hyperion System 9 BI+ Analytic Services (Essbase) Hyperion Financial Management Oracle Financial SAP BW Workflow and business processes Metadata flow Discovering the Environment Implementation process starts with the discovery phase during which you identify data systems that are planned to manage their dimensions in a Hyperion Master Data Management application. These systems can have different functional features and use different interfaces, workflow, business processes, and metadata flows. Typical questions that you need to find answers are: How frequently are hierarchies changed in the data systems? Timeline information helps define master data versions. Where is data entered? Are there multiple data entry points, peer-to-peer systems, or ETL processes in place? Hyperion System 9 Master Data Management Administration A-3

Hyperion MDM Implementation Guidelines Appendix A Identifying Business Requirements During this phase you define Interfaces with the data systems Method Style Content Business rules System business rules Enterprise operational business rules Identifying Business Requirements After you identified the data systems, you can define business requirements that includes interfaces with the data systems and business rules. Interfaces To define interfaces, you need to decide how the application should communicate with the data systems. For example, to update dimensions in an Analytic Services cube you can use load rules or you can push master data to the staging database and use Hyperion System 9 BI+ Analytic Integration Services. You also need to identify what information is needed and what type of master data update should be performed - full update or changes only. The interface style helps define data format and exports. A-4 Hyperion System 9 Master Data Management Administration

Hyperion MDM Implementation Guidelines Appendix A Business Rules Business rules help you define validations and verifications in the system as well as additional properties to support business rules. There are two main types of business rules: System business rules. For example, unique aliases in Analytic Services across the nodes. Enterprise operational business rules that are not enforced by the data systems, but rules that are defined by operational business. Hyperion System 9 Master Data Management Administration A-5

Hyperion MDM Implementation Guidelines Appendix A Designing Application Structure During this phase you design and build Versions Properties Property categories Validations Verifications Exports Designing Application Structure During the design phase, your main task is to define properties. Cross-system properties. Different data systems can have properties that can be related to each other. For example, system A has Expense Flag that is Boolean (TRUE or FALSE) and the System B has Expense Flag that is "E" or blank, and system C has Expense Flag that is "No Expense" or "Expense". You can resolve these differences based on the workflow where you defined the primary data system and then determine what can be derived and how. Derived properties. Data systems can have business rules to define their data. For example, a cost center that starts with 999 may define an allocation. In Hyperion Master Data Management application this can be enforced by a derived property instead of a business rule. A-6 Hyperion System 9 Master Data Management Administration

Hyperion MDM Implementation Guidelines Appendix A Inherited properties. Basic information can be inherited. For example, there are a number of times when the same person controls cost centers of the whole branch. Other examples are LOB codes, company codes, legal information, geographic structure (country and location information), managerial structure. Property defaults. Defining default values for properties reduces maintenance and data storage. For example, if you create a property that defines consolidation in Analytic Services, addition (+) can be the default value because most of the consolidations in an Analytic Services cube are additions. Hyperion System 9 Master Data Management Administration A-7

Hyperion MDM Implementation Guidelines Appendix A Loading and Analyzing Master Data During this phase you perform the following tasks: Load master data by the data system into separate versions Analyze loaded data to identify Structural differences Structural incompatibilities Design filters to resolve structural differences Merge data into one common version Loading and Analyzing Master Data After you identified properties, exports, and workflow, you are ready load and analyze the master data. Loading Data First step is to load master data by data system identified during the discovery phase. You load data for each of the data systems into separate versions and then you can use Master Data Management tools to compare these versions and analyze their structural differences. Valid structural differences. Some structural differences are valid. For example, a hierarchy in System A has more nodes than in System B, but the familial relationships of the nodes remain the same. These differences can be determined by filters. Structural incompatibilities. Structural incompatibilities in hierarchies are difficult to resolve. If there is no common solution, these hierarchies have to be maintained separately. A-8 Hyperion System 9 Master Data Management Administration

Hyperion MDM Implementation Guidelines Appendix A Merge Data After loading data from the data systems and making all comparisons, you can merge data in a common single version. Hyperion System 9 Master Data Management Administration A-9

Hyperion MDM Implementation Guidelines Appendix A Preparing for Rollout During this phase you perform the following tasks: Test exports and filters Test validations and verifications Setup security in the application Preparing for Rollout After you created the application structure, developed exports, filters, and properties, you can start producing the exports to the data systems. At this phase the application goes under typical post-development cycle including QA testing of all data flow and workflow processes. It may be that feeding the data systems is performed in parallel through the normal process and through the Master Data Management process. You also define levels of security in the application by creating users and groups in the application and define their privileges. A-10 Hyperion System 9 Master Data Management Administration

Hyperion MDM Implementation Guidelines Appendix A Going Live During this phase you perform the following tasks: Reload the master data Provide access to the application to business users Monitor and maintain the application Going Live After you complete the test phase, you test data may not be the most current. Usually it is a fair amount of time between the initial data load and the time the application goes live and, therefore, you need to reload the master data in the application. Further steps of the implementation process include providing access to the application to business users, monitoring, and maintaining the working status of the application. Hyperion System 9 Master Data Management Administration A-11

Appendix A Hyperion MDM Implementation Guidelines Summary In this lesson, you should have learned to: Describe the process of implementing a Hyperion Master Data Management application Describe the implementation tasks A-12 Hyperion System 9 Master Data Management Administration