Hyperion Master Data Management 9.0 Administration Student Guide

Transcription

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

2 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 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.

3 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 Master Data Versus Transactional Data and Metadata Defining Master Data Master Data Management Objectives Master Data Change Management Challenges Hyperion Master Data Management Solution Hyperion System Hyperion System 9 Components Hyperion Master Data Management Integrated Environment Key Benefits of Hyperion Master Data Management Centralized Master Data Store Secured Master Data Store Combined Business Rules Master Data Audit Historical Information Reporting on Hierarchies Master Data Key Terms and Concepts Applications Versions Master Data Life Cycle Version Status Hierarchies Nodes Orphan Nodes

4 Table of Contents Other Hierarchy and Node Terms Properties and Property Categories Validations and Verifications Lesson 2: Navigating Hyperion MDM User Interface Connecting to Hyperion MDM Applications Launching the MDM NTier Client Creating Login Connections MDM NTier Client Desktop Working with Hierarchies System Categories Opening Hierarchies Closing Hierarchies Hierarchy Window Configuring the Hierarchy Window Viewing Node Properties Property Editor Property Categories Displaying Property Tabs Lesson 3: Working with Master Data Working with Hierarchies Adding and Inserting Nodes Moving Nodes Deleting Nodes Merging Nodes Searching for Nodes Finding Nodes in a Hierarchy Finding Nodes in a Version Navigating Hot Lists Listing Orphan Nodes Analysis Tools Running Property Queries Comparing Hierarchies Comparing Properties iv Hyperion System 9 Master Data Management Administration

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

6 Table of Contents Deleting Versions Managing Hierarchies Adding Hierarchies Creating System Categories Assigning Hierarchies to System Categories Editing Hierarchy Properties Saving Hierarchies Deleting Hierarchies Lesson 7: Managing Properties Hyperion MDM Properties Overview Property Definition Levels Local Versus Global Properties Inheritance Global Properties and Inheritance Property Categories Creating Property Categories Built-In Property Categories User-Defined Properties Data Types Property Types Creating and Configuring Properties Setting Up Lookup Properties Setting Up Lists of Values Specifying a Controlling Hierarchy Setting Up Derived Properties Specifying Default Values Specifying Maximum and Minimum Values Working with Formulas Formula Deriver Class Creating and Editing Formulas Formula Syntax Testing Formulas Formula Evaluation Functions Logical Operators vi Hyperion System 9 Master Data Management Administration

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

8 Table of Contents Mapping Properties to Columns Specifying File Format Information Setting Up Duplicate Handlings Running Imports and Viewing Results Saving and Deleting Imports Blending Versions Blender Elements Configuring Blender Versions and Hierarchies Setting Up Top Nodes Selecting Blender Options Running Blenders and Viewing Results Importing Data to Existing Versions Automator File Format Performing Imports by Using Automator Reviewing Automator Processing Results Lesson 11: Exporting Master Data Exporting Data Overview Creating Exports Export Classes Exporting Hierarchies Specifying Top Nodes Selecting Export Columns Specifying Column Options Setting Export Parameters Defining Filters and Verifications Configuring Output Formats Specifying the Output Destination Saving and Deleting Exports Creating Generation Exports Selecting Columns Configuring Repeat Parameters Defining Exclusion Filters Creating Hierarchy Compare Exports Exporting to a Database Table Setting Up Table Fields Creating and Exporting Books viii Hyperion System 9 Master Data Management Administration

9 Table of Contents Lesson 12: Managing Security Levels of Security Node Access Node Access Groups Global Node Access Groups Managing Node Access Groups Assigning Node Access Groups to Users Defining Controlling Hierarchies Assigning Node Access Groups to Hierarchies Property Access Assigning Property Categories to Users Managing Users Creating Users Assigning User Permissions Locking and Unlocking Users Changing User Passwords System Preferences and Security Lesson 13: Auditing Master Data Tracking Master Data Changes Viewing Baseline Versions Viewing the Transaction History Viewing Transaction History Details Exporting the Transaction History Analyzing Master Data Changes Creating As Of Versions Exporting Hierarchy Differences 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

10 Table of Contents x Hyperion System 9 Master Data Management Administration

11 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

12 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

13 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

14 Preface xiv Hyperion System 9 Master Data Management Administration

15 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

16

17 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

18 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 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

19 Module 1 Getting Started Lesson 1 Master Data Management Overview Master Data Versus Transactional Data and Metadata Transactional Data Company Hyperion Entity FL Account 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, 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

20 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

21 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

22 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

23 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

24 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

25 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

26 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 Hyperion System 9 Master Data Management Administration

27 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

28 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 Hyperion System 9 Master Data Management Administration

29 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

30 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 Hyperion System 9 Master Data Management Administration

31 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

32 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 Hyperion System 9 Master Data Management Administration

33 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

34 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 Hyperion System 9 Master Data Management Administration

35 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

36 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 Hyperion System 9 Master Data Management Administration

37 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

38 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 Hyperion System 9 Master Data Management Administration

39 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

40 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 Hyperion System 9 Master Data Management Administration

41 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

42 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 Hyperion System 9 Master Data Management Administration

43 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

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

45 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

46 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 Host A Application A MDM NTier Client Connection B 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