Hyperion: LCM Best Practices

If you are migrating an entire Planning application at once, Lifecycle Management handles most migration dependencies automatically. However, if you are migrating artifacts individually, Oracle recommends that you migrate Planning artifacts in this order:

1. Shared Services Native Directory (Security)
2. Application Settings under Configuration Properties
3. Global Artifacts:
   
   • Spread Patterns
   • Smart Lists
   • Common Dimensions
   • Exchange Rates
4. All Standard and Attribute Dimensions under Plan Type
5. Configuration:
   
   • User Variables
   • User Preferences
6. Substitution Variables under Global Artifacts
7. Plan Type:
   
   • Substitution Variables
   • Calc Scripts
   • Rules files
   • Calculation Manager Rules
8. Global Artifacts:
   
   • Business Rules
   • Custom Menus
   • Calculation Manager Rule sets
9. Data Forms under Plan Type
10. Global Artifacts:
    
    • Composite Forms
    • Task Lists
11. Relational Data
12. Access Permissions under Security
13. Reporting and Analysis (Financial Reporting and Web Analysis)

Hyperion: Setting Up an Audit Trail in Planning

This tutorial covers how to set up audit trails in Planning.
As an Administrator, you can select aspects of the application for change tracking. You can track changes to metadata, data forms, business rules, workflow, users, and access permissions.
To view audits, you create and run reports by using RDBMS report writers.

Scenario

As Administrator, you have been asked to turn on data and offline change tracking for your Planning application. After setting up change tracking, you need to verify data changes in the HSP_AUDIT_RECORDS table in SQL Server.

Prerequisites

Before starting this tutorial, you should:

1.	Have Administrator rights to Planning applications.
2.	Have access to Workspace and Planning.
3.	Have Administrator access to Microsoft SQL Server Enterprise Manager.

Setting Up Change Tracking

You can enable auditing for dimension administration, alias table administration, data modification, launching business rules, data form definition, data form folder administration, workflow, copy versions, security, user administration, group administration, and offline access.
In this topic, you set up change tracking for data modification and offline access.

To set up change tracking:

1.	Launch Workspace and log on as Administrator.
2.	Select Navigate > Applications > Planning > <Planning Application>.
3.	In Planning, select Administration > Reporting.
4.	Select the Auditing tab.
5.	Select the Data and Offline check boxes, and click Save Selections.
6.	Click Close .
7.	In the view pane, expand Forms. Under Forms, click a folder name to display its content, and click a data form.
8.	Click an unlocked cell, enter data, and click Save .

Viewing and Clearing Audit Reports in SQL Server

Depending on selected audit options, application changes are recorded in a HSP_AUDIT_RECORDS table, stored in the relational database. When using SQL Server, you can view and clear audit reports in Enterprise Manager.

To view and clear audit reports in SQL Server:

1.	Open Microsoft SQL Server - Enterprise Manager. From the Console Root, expand Microsoft SQL Servers > SQL Server Group > < SQL Server e.g. local> > Databases > < Planning application database > > Tables.
2.	Select the HSP_AUDIT_RECORDS table.
3.	Right-click HSP_AUDIT_RECORDS and select Open Table > Return all rows.
4.	Review the latest records, and click Close . In this example, data changes applied to all affected cells were posted to the table.
5.	Right-click HSP_AUDIT_RECORDS and select Open Table > Query.
6.	Right-click SELECT, and select Change Type > Delete.
7.	Click Run.
8.	When prompted that the query was executed successfully, click OK.
9.	Click Close .
10.	Right-click HSP_AUDIT_RECORDS and select Open Table > Return all rows.
11.	Verify that all records were deleted .

Hyperion: Creating Classic Planning Applications in Oracle Hyperion Planning, Fusion Edition 11.1.2

Overview

You can create Planning applications using Classic Application Administration. To use Classic Application Administration, you must be assigned the appropriate roles, as described in the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.

For Classic Planning applications, you use Classic Application Wizard to create and delete applications, and register with Hyperion® Shared Services. When you create Classic applications, you can set them up to calculate business rules by using Business Rules or Calculation Manager.

Software and Hardware Requirements

The following is a list of software requirements:

• Oracle Hyperion Planning Plus 11.1.2

Oracle Hyperion Planning Plus 11.1.2 includes the following components:

• Oracle Hyperion Enterprise Performance Management System Release 11.1.2 - Start Here: Installation Documents and Readmes
• Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.2
• Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2
• Oracle Hyperion Enterprise Performance Management System Additional Content Release 11.1.2
• Oracle Hyperion Calculation Manager Release 11.1.2
• Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition Release 11.1.2
• Oracle Essbase Release 11.1.2
• Oracle Essbase Clients Release 11.1.2
• Oracle Essbase Spreadsheet Add-in Release 11.1.2
• Oracle Hyperion Financial Reporting, Fusion Edition Release 11.1.2
• Oracle Hyperion Enterprise Performance Management Reporting and Analysis Core Components Release 11.1.2
• Hyperion Web Analysis Release 11.1.2
• Oracle Hyperion Planning, Fusion Edition Release 11.1.2
• Optional: Hyperion Data Integration Management Adapters Release 11.1.1.1.0
• Optional: Oracle Hyperion Smart View for Office, Fusion Edition Release 11.1.2
• Optional: Oracle Data Integrator, Oracle Data Profiling, and Oracle Data Quality for Data Integrator 10g (10.1.3.5.0)
• Optional: Oracle Identity Management 11g (11.1.1.1.0)

Relational storage databases are required in the installation and configuration of Oracle Hyperion Planning Plus 11.1.2. This tutorial requires a relational storage for the Classic Planning application. See the Oracle Hyperion EPM System Release 11.1.2 - Start Here: Installation Documents and Readmes.

Prerequisites

Before starting this tutorial, you should:

1 .	Have administrator access to a working installation of Oracle Hyperion Planning 11.1.2.
2 .	Have access to relational storage used to create a Planning data source.
3 .	Have administrator access to Administration Services Console.
4 .	Have defined an Essbase Server view in Administration Services Console.

Managing Planning Data Sources

Dimensions and members are stored in the Essbase databases and in the Planning repository (Planning relational database). Each Planning application requires a Planning repository.

To create Planning data sources:

1.	Log on to Workspace.
2.	Select Navigate, then Administer, then Classic Application Administration, and then Planning Administration.
3.	In the left pane, click Manage Data Source. You can also click the Manage Data Source button in the content pane.
4.	Click Create Data Source.
5.	Perform the following actions for the application database: Select a database platform. In this example, Oracle is selected. Enter the server that hosts your database. In this example, localhost is entered. Enter the database port number. The default port for the Oracle database is 1521. Enter the Oracle service name or system identifier (SID). In this example, the Oracle SID is ORCL. Enter the user associated with the database schema. In this example, ST01PLN2 is used. Enter the schema password. Click Validate Database Connection. The following message confirms that the connection was successful:
6.	Enter the connection information to your Essbase Server, and click Validate Essbase Connection. The following message confirms that the connection was successful:
7.	Click Finish.

Creating a Classic Planning Application

To create a classic Planning application in Classic Application Administration: 

1.	In the left pane, click Create Application. You can also click Create from Classic Application Wizard to start the application creation process.
2.	On the Select tab, perform the following actions: Select a datasource. In this example, the ST01PLN2 datasource created in the previous topic is selected. Enter the name of the application. The name can contain up to eight characters. It must be different than an existing Essbase application. In this example, we name the application PlanBud. Enter an application description. In this example, Planning and Budgeting application is entered. Select a Shared Services Project (application group). In this example, the PlanBud application will be grouped under the Default Application Group. Select an instance (cluster) to use for the application. In this example, Default is selected. Select an application type. In this example, General is selected. For Calculation Module, select Business Rules or Calculation Manager. In this example, Calculation Manager is selected.
3.	Select the Calendar tab.
4.	Select the base time period, fiscal start year, fiscal start month, weekly distribution, and total years.
5.	Select the Currencies tab.
6.	Select the default application currency. If the application supports multiple currencies, select Yes.
7.	Select the Plan Types tab.
8.	Perform the following actions: Select Plan Type 1 and Plan Type 2, and clear all other plan type selections. Enter a name for both plan types. In this example, Incstmt and Balsheet are entered. Note: The name and number of plan types depend on your business requirements.
9.	Select the Finish tab.
10.	Review your selections and click Finish to create the application. When the application creation is successfully completed, the following message is displayed:

Opening the Planning Application

To open the Planning application in Workspace after creating it in Classic Application Administration:

1.	In Workspace, select Navigate, then Applications, and then Refresh. The Refresh menu option updates the navigation menu with new applications.
2.	Select Navigate, then Applications, then Planning, and then [Application Name]. In this example, you open the PlanBud application.
3.	The PlanBud application is displayed. After creating Classic Planning applications, you can add dimension members, data forms, menus, business rules, and task lists.
4.	Select Administration, then Manage, and then Dimensions. You can manage dimensions, set performance settings, and change the evaluation order in Dimension Editor.
5.	Select Administration, the Manage, and then Data Forms and Ad Hoc Grids. The Data Form Management page is displayed. You manage data forms and folders, and ad hoc grids in the Data Form Management page.
6.	After making changes to your application, you must refresh the Essbase database outline. Select Administration, then Application, and then Refresh Database.
7.	Make your selections and click Refresh. The following example displays a Planning application with defined dimensions, members, data forms, and other Planning objects.

Loading Data Into the Application

Prior to loading data to the application, ensure that you:

• Have a Planning application with the required metadata.
• Have a data file that maps to the metadata defined in the application.
• Have administrator access to Planning and Administration Services Console.
• Have defined an Essbase Server view in Administration Services Console.

This tutorial shows you how to load data into the Incstmt plan type in the PlanBud application. To load data into the application:

1.	Log on to Administration Services Console.
2.	In the left pane, expand Enterprise View, then Essbase Servers, then [Server View], then Applications, thenPlanbud, and then [Plan Type]. In this example, the PlanBud application is accessed from the UPKPS1RC4:1423 Essbase Server view. TheIncstmt plan type is selected. Essbase refers to plan types as databases.
3.	Select Actions, and then Load data for "[Plan Type / Database]".
4.	In the Data Load dialog box, click Find Data File.
5.	Select the File System tab, locate your data file, and click OK.
6.	Click OK to execute the data load process. You can also select the Abort on Error option in the Data Load dialog box to stop the loading process when an error occurs. The following progress box is displayed during the data load process:
7.	When the data load process is completed, the Data Load Results dialog box displays a status of Success.
8.	Open a data form in your Planning application to verify that data was loaded successfully.

Summary

In this tutorial, you have learned how to:

• Manage Planning datasources.
• Create a Classic Planning application.
• Open the Classic Planning application that you created.
• Load data into Planning applications.