Hyperion PLANNING RELEASE 11.1.1
Creating Planning User Groups
Prerequisites
Before starting this tutorial, you should:
1. Have Provisioning Manager access to Planning applications.
2. Have access to Oracle® Hyperion Shared Services Console.
Creating Groups and Associating Existing Users
Shared Services Console enables you to manage user security and application groups in a central location. It is installed with the Shared Services server. To create native directory groups in Shared Services Console, perform the following steps:
1. Log on to Shared Services.
2. In Shared Services Console, expand Shared Services, User Directories, and Native Directory nodes.
3. Right-click Groups and select New to display the Create Group pane.
4. Enter Consultant_Admin for the name and Implementation Consultant Group for the description, and click Next to display the Groups Members tab.
6. Select Planners_NA and click Add.
7. Click Next to display the User Members tab.
8. Click Go to display all users in Shared Services.
9. Select users and click Add.
Assigning Planning Roles to Groups
To complete the process of creating the user group, you must provision it with access privileges to provide all users in the group with the same level of security. In this case, the security level is administrative access to Planning. To provision user groups, perform the following steps:
1. In Shared Services Console, expand Shared Services, User Directories, Native Directory nodes and click Groups to display the Group Search pane.
2. Click Search to display all user groups in Shared Services.
3. Right-click Consultant_Admin and select Provision to display the Provisioning pane.
5. Select Interactive User and click Add.
The Interactive User role is now displayed in the Selected Roles area.
6. Click Save.
The Provision Summary pane displays the successful provisioning message.
Summary
In this tutorial, you learned how to:
Create groups and associate existing users Assign Planning roles to groups
Setting Up an Audit Trail in Planning
Prerequisites
Before starting this tutorial, you should:
1. Have administrator access to Planning applications.
2. Have access to Workspace and Planning.
3. Have access to query Planning relational database tables. In this case, you use Oracle SQL Developer.
Enabling Auditing
To enable Planning audit reports, perform the following steps:
1. Log on to Workspace.
2. Select Navigate > Applications > Planning > [Planning application].
3. Select Administration > Reporting.
4. Select the Auditing tab.
6. In the view pane, expand the Forms node. Under Forms, click a folder name to display its content, and click a data form.
7. Click an unlocked cell, enter data, and click Save.
Viewing and Clearing Audit Reports in SQL Developer
To use Oracle SQL Developer to view and clear audit reports, perform the following steps:
1. From your desktop, select Start > Programs > Oracle - OraDb11g > Application Development > SQL Developer.
3. Select the HSP_AUDIT_RECORDS table and click the Data tab to display audit history.
In this example, data changes applied to all affected cells are posted to the table.
4. From the Data tab, click the first cell in row 1 and press Ctrl + A to select all rows.
6. Click Commit Changes.
7. All records are deleted.
Summary
In this tutorial, you learned how to: Enable auditing
Using Interface Tables to Import Metadata into Planning
Prerequisites
Before starting this tutorial, you should:
1. Have access to the Configuration Utility.
2. Have administrative access to Performance Management Architect.
3. Have access to data sources that contain dimension metadata
Configuring Interface Data Sources
You must configure data sources in order to use interface tables in Performance Management Architect. Interface tables provide you with a database interface to import metadata and data from external systems to Dimension Library. To configure interface data sources, perform the following steps:
1. Launch the EPM System Configurator to display the Welcome pane and click Next.
2. In the product selection panel, expand the Hyperion Foundation and Performance Management Architect nodes. Select Interface Datasource Configuration and
click Next.
4. Select a database type (Oracle, SQL or DB2), and click Next.
5. Enter the details for the interface data source, and click Next.
7. Click Finish.
Creating Interface Table Definitions
To create interface table definitions, perform the following steps:2. Select File > New > Data Interface Table Definition to display the Data Interface Area Mapping Wizard.
3. On the Interface Area page, select the interface table data source you created. Next, select the table and column that contain the values to import, and click Next.
4. On the Dimensions page, select a column, enter a dimension name, and click Next.
5. On the Properties page, enter a name and description for the interface area definition, and click Finish.
Importing Dimensions from Interface Tables
Before importing dimensions into the Dimension Library, you must create and run a data synchronization or an import profile. Data synchronization enables you to synchronize and map data between Hyperion applications, interface tables, and external files. Profiles include important information about the dimensions to be imported such as new dimensions, whether to merge or replace existing dimensions, and dimension properties. You execute the profile to import dimensions into Dimension Library. To import dimensions from interface tables, perform the following steps:
1. In the Performance Management Architect Data Synchronization module, select File > New > Synchronization to display the New Synchronization pane.
3. Select a source data interface definition, and click Next.
4. Select an available destination application, and click Next.
5. Select plan types for source and destination and click Finish.
7. Select File > Import > Create Profile to create an import profile in Dimension Library.
8. Enter profile details and click OK.
9. Select mapping options and click Next.
10. Review mapping options and click Finish.
12. Click Close.
Summary
In this tutorial, you learned how to: Configure interface data sources Create interface table definitions Import dimensions for interface tables
Creating Planning Classic Applications
Prerequisites
Before starting this tutorial, you should:
1. Have access to or have installed Oracle® Hyperion Planning, Fusion Edition 11.1.1.0.0
2. Have access to or have installed a Planning application.
3. Create a Shared Services application group called Planning Training Applications.
Creating Data Sources
Data sources link the relational database to the Essbase server. You must create a data source when you create an application. Each data source must be associated with an instance. When you create or update applications using the Classic Application Wizard, you select a data source for the application. To create a data source, perform the following steps:
1. Log on to Workspace.
2. In Workspace, select Navigate > Administer > Classic Application Administration > Planning Administration.
3. In Classic Administration Wizard, click Manage Data Source.
4. Click Create Data Source.
6. From the Select Database Platform drop-down list, select a database type such as SQL or Oracle.
7. In the Application Database area, enter Planning application details and click Validate Database Connection.
Creating Sample Applications
For classic Planning applications, use the Classic Application Wizard to create and delete applications. When using the Classic Application Wizard to create a classic sample application, select the Sample Application check box. To create the Planning Classic application, perform the following steps:
1. From Workspace, Classic Application Administration, in the bottom left pane, click Create Application.
2. On the Select tab, specify details for the new sample application, select the Sample Application check box, and click Next to display the Finish tab.
3. Click Finish.
4. In the Application Creation Confirmation pane, click the link to refresh the Planning applications menu.
You have created a Planning application with a predefined structure.
Initializing Sample Applications
After creating the classic sample application, you must initialize it. To initialize the Planning Classic application, perform the following steps:
1. From Workspace, select Navigate > Administer > Planning > [Planning application].
2. Select Edit > Sample Planning Application > Initialize Sample Application.
3. In the successful initialization dialog box, click OK.
5. Select Database and click Create.
6. In the Manage Database dialog box, click Create.
The Cube Refresh status is displayed.
7. When the status displays Create Complete, click Finish.
8. Verify that the application was initalized by expanding Forms, clicking a folder, and opening a data form.
Loading Sample Data
You load sample application data directly through Administration Services Console. You must rename the sample application text file with up to eight characters. To load sample data, perform the following steps:
1. In the \Hyperion\products\Planning\bin\ directory, locate the sample data file.
2. Extract the sample data zip file to a location on your drive, such as c:\TEMP and rename it to be eight characters or less.
In this example, SampleAp.txt file contains the sample data that you are loading to the sample application.
3. Log on to Administration Services Console, expand Enterprise View > Essbase Servers > [localhost] > Applications > [Planning application], and select [Planning
outline].
5. Click Find Data File to display the Open dialog box.
6. On the File System tab, locate and select the sample data file, and click OK.
7. Select the Abort on Error option and click OK.
8. After the status “Success” is displayed, click Close.
9. In the Planning sample application, open a data form to verify that the data was loaded.
Summary
In this tutorial, you learned how to: Create data sources
Create sample applications Initialize sample applications Load sample data
Migrating Planning Classic Applications to Performance Management Architect
Prerequisites
Before starting this tutorial, you should:
1. Have administrator access to a Planning Classic application (budplan is used for this tutorial).
2. Have administrative access to Performance Management Architect.
3. Have administrative access to Essbase.
Preparing the Environment
You should back up your applications and application databases on a daily basis, and before migrating classic applications to Performance Management Architect. To prepare the environment for application migration, and be able to restore to a previous state, back up the following items:
Planning database
Essbase outline files for all applications Essbase security file
Essbase configuration file Full export of Essbase data
Migrating Applications
To move a Planning Classic application to Performance Management Architect, perform the following steps:
1. Log on to Workspace.
2. Select Navigate > Administer > Application Upgrade to display the Application Upgrade Wizard.
3. On the Application Upgrade Wizard Welcome page, click Next.
4. Select the application you want to migrate and click Next.
5. On the Application Selection page, select the application you want to migrate , click Add to move it to the Application to Upgrade list, and click Next.
6. Review the Upgrade Summary and click Finish to execute the upgrade.
8. When job status displays as Completed 100%, select Navigate > Administer > Application Library, and confirm that the Planning application is in Performance
Management Architect.
10. Review the application dimensions in Dimension Library.
Summary
In this tutorial, you learned how to:
Prepare the environment for application migration Migrate applications
Automating Planning Administrative Processes Using Batch Client
Prerequisites
Before starting this tutorial, you should:
1. Install Performance Management Architect.
2. Have administrative access to Planning.
3. Have administrative access to Performance Management Architect.
Preparing to Use Batch Client
To prepare to create applications, perform the following steps:
1. View the script that you want to use to create test Planning applications. You must verify that the script is complete and uses the correct syntax.
2. Log on to Workspace.
3. Select Administer > Application Library to display Application Library.
Creating Applications
To create applications, perform the following steps:
1. Open a command prompt, and change the directory to C:\Hyperion\products\Foundation\BPMA\EPMABatchClient. This is the default directory for Batch Client.
For more information on how to create Batch Client scripts, refer to the Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition 11.1.1, Batch Client User's Guide.
2 Enter the create application creation command and execute the application creation script. In this case, the script was validated and the application was
successfully created.
3. Check the EPMABatchClientResults log file to verify that the application was successfully created. The file is located in the default directory,
C:\Hyperion\products\Foundation\BPMA\EPMABatchClient\output.
Deploying Applications
To deploy applications, perform the following steps:
1 View the script that you want to use to deploy applications. You must verify that the script is complete and uses the correct syntax. In this case, you will deploy the
PLAN3 Planning application.
For more information on how to create Batch Client scripts, refer to the Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition 11.1.1, Batch Client User's Guide.
2 Open a command prompt, enter the deploy application command, and execute the deploy application script. In this case, the script was validated and the
application was successfully deployed.
3. Check the EPMABatchClientResults log file to verify that the application was successfully deployed. The file is located in the default directory,
C:\Hyperion\products\Foundation\BPMA\EPMABatchClient\output.
5. In Library Job Console, verify that the application was successfully deployed.
7. Select Applications > Planning > [Planning Application] to verify that the Planning application is now available for testing.
Summary
In this tutorial, you learned how to: Prepare to use Batch Client Create applications Deploy applications
Loading Metadata into Planning Using Data Integration Management
Prerequisites
Before starting this tutorial, you should:
1. Have administrator rights to Planning.
2. Have access to Workspace, Planning, and Data Integration Management.
3. Have a load file containing Planning metadata to use in Data Integration Management.
Reviewing Load Files
To review load files, perform the following steps:
1. Open the metadata load file and review its contents. In this case, we are using a csv file.
In this example, you have one member, 5800, that you will load into Planning. Columns represent member properties.
2. Add additional rows to the load file to load other accounts.
In this example, add account 5900 (Discount Expense). Now there are two accounts to add to Planning.
Logging On to Data Integration Management
To log on to Data Integration Management, complete the following steps:1. Select Start > Programs > Informatica PowerCenter 8.1.1 > Client > PowerCenter Workflow Manager.
2. In the Welcome to PowerCenter Workflow Manager window, click OK.
The Informatica PowerCenter Workflow Manager is displayed.
Connecting to Repositories
To connect to a repository, complete the following steps:
1. In the Repository Navigator pane, right click a repository and select Connect.
2. In the Connect to Repository dialog box, enter security credentials and click Connect.
3. Select Connections > Application to set the Planning application connection.
The Application Connection Browser is displayed.
5. Click New .
6. Enter the application name, user name, and password, and click OK .
7. Click Close .
Creating Flat File Sources
You create a flat file source in Designer. You set up both source and target definitions. To create flat file source definitions, perform the following steps:
2. Right-click the Planning folder, and select Open .
3. Select Tools > Source Analyzer .
4. Select Sources > Import from File .
5. Select the flat file you are using to import metadata and click OK . In this example, the flat file is LoadAccounts_DIM.csv.
The Flat File Import Wizard is displayed.
6. If your load file contains names in the first row, select Import field names from first line, and click Next .
8. Select column data types for the text file, and click Finish .
9. If the table exists, click Replace to replace the source details.
The flat file is displayed in Source Analyzer.
10. Expand the flat file source to view all ports that can be mapped from this flat file to the Planning application target. In this example, the target is the Account
dimension in Planning.
11. Right-click the flat file source and select Edit .
12. Select the Columns tab, and set all data type values to string .
13. Click OK to close the dialog box.
14. Press Ctrl+S to save your changes and verify that the file was saved.
Creating Planning Targets
You use Target Designer to set up a Planning target for the metadata load. You select a target and create a data source. After setting up a connection to a Planning data source, you test the connection. To create Planning application target definitions, perform the following steps:
1. From Designer, select Tools > Target Designer .
3. Click the ellipsis button to create a data source name before you define your targets.
The DSN represents a set of information that is used to connect to an application such as Planning.
4. Enter the DSN and server details and click Get applications to refresh the list of servers that you can connect to.
6. Click Test connectivity .
7. Click OK to close the Define DSN dialog box.
9. Select Account , and click OK to import account metadata into Planning.
Next, you create a mapping from the source flat file to the target Planning application.
Creating Mappings
You use Mapping Designer to create a mapping between source file and the Planning target.
1. From Target Designer, select Tools > Mapping Designer .
The Mapping Designer window is displayed.
2. Select Mappings > Create .
3. In the Mapping Name dialog box, enter a mapping name and click OK .
4. Select the source for the data load. In this example, it is the LoadAccounts_DIM flat file.
The source definition and source qualifier are displayed in the mapping dimension editor.
6. Expand the source qualifier to view all mapping ports .
7. Select a target for the mapping, and adjust the Mapping Designer windows to see all targets and source definition details.
8. Drag the Planning account target to the Mapping Dimension Editor and place the target to the right of the source.
10. Right-click anywhere in Mapping Designer, and select Autolink .
11. Select the target (From Transformation) and source (To Transformations) to link, click Apply Now , and then click OK .
13. View the Mapping output window to confirm that the mapping was saved .
Creating Data Load Workflows
You use Workflow Manager to create a data load workflow. Next, you execute the data load workflow to load the metadata to the Planning target. To create data load workflows, perform the following steps:
1. From PowerCenter Designer, select Tools > Workflow Manager .
2. In Workflow Manager, right-click the Hyperion folder, and select Open to ensure that the Hyperion repository is connected
3. The Workflow Designer window is displayed.
The last workflow that you were working on is displayed.
4. Select Workflows > Create .
6. Enter the workflow name, server, and any other details, and click OK .
7. Select Tasks > Create to create a session task.
Session tasks specify how workflows are executed.
8. In the Create Task dialog box, enter the task name, and click Create .
9. Select the mapping that you created, and click OK .
Executing Data Load Workflows
You use Workflow Manager to execute a data load workflow in order to load the metadata to the Planning target. First, you verify the source and target properties for the task and the mapping and save the workflow. Next, you link and validate the task flow. Finally, you execute the workflow.
Verifying Source and Target Properties Linking and Validating Task Flows Executing Workflows
Verifying Source and Target Properties
To verify source and target properties, perform the following steps:1. Right-click the session task and select Edit to verify that source and target properties are correct.
2. Select the Mapping tab to verify source and target properties.
4. Verify that the correct reader, (File Reader) for the flat file is selected.
6. Click OK to close the Edit Tasks window.
Linking and Validating Task Flows
To link and validate task flows, perform the following steps:1. Select Tasks > Link Task to link the tasks in the workflow.
2. Link to tasks.
3. Select Tasks > Validate to validate the task flow.
4. In the Output window, verify that the workflow is valid.
If your workflow is not valid, verify the session task properties again.
Executing Workflows
To execute workflows, perform the following steps:
1. Select Workflows > Start Workflow.
2. Right-click the session task and select Properties to verify that the workflow was executed properly.
3. Verify that two rows were successfully created in the target Planning applications.
Verifying Results in Planning
In this topic, you log on to Planning and verify that the two accounts were added to the Account dimension.
1. Log on to Workspace and access your Planning application.
2. In the Administration menu, select Dimensions to display Dimension Editor.
3. In the Dimensions list, select Account and search for account 5800.
4. Verify that accounts 5800 and 5900 were added to the Account dimension.
Summary
In this tutorial, you learned how to: Review load files
Log on to Data Integration Management Connect to the Repository
Create flat file sources Create Planning targets Create mappings
Create data load workflows Execute data load work flows Verify results in Planning
First-Time Lifecycle Management Migration for Oracle Hyperion Planning 11.1.1 with Hyperion Shared
Services Lifecycle Management 11.1.1
Prerequisites
Before starting this tutorial:1. Install and configure Planning 11.1.1 and all related 11.1.1 EPM products in the source and destination environments (Hyperion Shared Services, Essbase, Financial Reporting, and so on).
2. The source environment must contain the Planning application with all metadata loaded.
3. The source environment user who is performing the lifecycle management activities is provisioned with the following roles:
Shared Services LCM administrator role
Planning application administrator role4. The destination environment user who is performing the lifecycle management activities is provisioned with the following roles:
Shared Services LCM administrator role
Planning application administrator role
Planning application creator roleExporting a Planning Application to the File System in the Source Environment
1. In the source environment, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.
2. Navigate to Foundation > Shared Services, and select the native directory provisioning artifacts and task flows that are applicable to the Planning application, as
follows:
Users – Native Directory users
Groups – Native Directory groups
Assigned Roles – Roles granted to users and groups through the provisioning process. You should select the roles for the associated product artifacts that pertain to the Planning application.Note: You should choose the assigned roles for all products that contain artifacts for the Planning application.
3. Navigate to the Planning application group, and select the Planning application that you want to migrate; for example, HPSamp. 4. Select the application artifacts that you want to migrate.
that reside under the Planning application that you are migrating. In the following example, it is HPSamp.
6. Navigate to Reporting and Analysis to select the financial reports.
7. Select the Repository Objects folder, and navigate to the folders that contain the financial reports that are associated with the Planning application. 8. Select the financial reports; for example, Planning HPSamp Reports.
9. On the Selected Artifacts tab, review the set of artifacts that you selected for the Planning application migration.
10 Click the Define Migration button to define the Planning application migration. 11 Select the first product to migrate (for example, Shared Services), and click Next.
13 On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be extracted, and click Next.
14 Review the destination options to ensure that the parameters are correct, and click Next.
You are directed back to the beginning of the migration wizard so that you can define other product migrations.
15 Select the next product to migrate (for example, EPM Architect), and click Next.
16. On the Source Options page, click Next.
17 On the Destination page, enter the name of the file system folder where the EPMA artifacts will be extracted, and click Next.
19 Select the next application to migrate (for example, Planning), and click Next.
20 On the Source Options page, and click Next.
21 On the Destination page, enter the name of the file system folder where the Planning artifacts will be extracted, and click Next.
22 Review the Destination Options page, and click Next.
23 Select the next application to migrate (for example, Reporting and Analysis), and click Next.
25 On the Destination page, enter the name of the file system folder where the Financial Reporting artifacts will be extracted, and click Next.
26 Review the destination options to ensure that the parameters are correct, and click Next.
27 Review the Migration Summary to ensure that the defined migrations are correct.
28 Click Save Migration Definition. 29 Select Save as XML, and click OK.
31 Enter the location and name for the migration definition file, and click Save.
32 In the Download Complete dialog box, click Close.
33 Click Close.
The Planning application migration is executed.
35 Click Launch Migration Status Report.
36 On the Migration Status Report page, review the status of the migration. When the report status changes to Success, the migration is completed successfully, and
the Planning application artifacts are extracted to the file system.
Copying Planning Application Artifacts from the Source Environment to the Destination Environment
The source environment application artifacts that exist on the file system must be moved to the destination environment file system. You can accomplish this task by copying and pasting the artifacts, sending them through FTP, or burning them to a DVD. Note that the default file system location for the life cycle management artifacts is on the Shared Services Web application server at <%hyperion_home%>\common\import_export. In this example, you copy and paste the artifacts within Windows Explorer.1 In the source environment, navigate to Windows Explorer on the file system. 2 Select Tools > Map Network Drive.
3 Enter the parameters for the destination environment file system location.
4 Click Finish.
5 Navigate to the location of the source environment application artifacts. 6 Select the folders, right-click, and select Copy.
The application artifact folders now reside on the destination server file system location.
Creating the Planning Application in the Destination Environment for Planning Classic Applications
Before migrating a Planning classic application, you must first create the Planning application in destination environment. Prior to beginning this section, ensure that you have created a new relational database for this new application.
Note:
If the Planning application is already created in the destination environment or if the Planning application is EPMA-enabled, skip this section.
The following dimension-level properties must match in both the source and the destination applications: Start yearBase time period (for example, 12 months, Quarters, and Custom) Start month
If the source has a “Single Currency” application type, then the destination application should be of the same type
Source and destination plan types must match (for example, if the source application has a plan type called Plan1, a Plan1 plan type must exist in the destination application).
1 Log on to Workspace.
2 Navigate to Administer > Classic Application Administration > Planning Administration.
4 Click Create Data Source.
5 Enter the parameters, and select Finish.
7 Enter the application name, description, Shared Services project, and instance, select Sample Application, and click Next.
8 Click Finish.
9 Select File > Open > Applications > Planning > HPSamp
You successfully created the destination application.
Importing a Planning Application from the File System in the Destination Environment
You have exported the Planning application artifacts from the source environment to the file system, copied the artifacts to the destination environment file system, and created a Planning application in the destination environment. You now import the artifacts into the destination Planning application.
Note:
Shared Services artifacts must be imported before you import Planning artifacts.
Because Lifecycle Management does not support Planning access permissions migrations, use the following Planning command-line utilities (ImportSecurity and ExportSecurity) to export and import Planning security:HYPERION_HOME\products\Planning\bin\ExportSecurity.cmd HYPERION_HOME\products\Planning\bin\ImportSecurity.cmd
2. Navigate to the File System node, select the Shared Services artifacts, and click Define Migration.
3. Review the source options, and click Next.
4. In the destination, choose the Shared Services destination, and click Next.
5. On the Destination Options page, select the import operation type and the number of maximum errors before stopping the import, and click Next.
6. Click Execute Migration.
The migration is executed.
7. Click Launch Migration Status Report to view the status of the migration.
8. Perform one of the following actions:
For Planning applications that are EPMA-enabled, proceed to step 9.Note: EPMA artifacts must be imported and deployed before non-dimensional Planning artifacts are imported.
For Planning classic applications, skip to step 24.9. If the Planning application is EPMA-enabled, navigate to Application Groups > File System.
Note: The EPMA artifacts must be imported and deployed before you migrate non-dimensional artifacts for Planning application. 10 Select the EPMA file system artifacts that are applicable to the Planning application.
11 Click Define Migration.
12 View the Source Options page, and click Next.
13 Select the destination (in this case, EPM Architect), and click Next.
14 Select the Dimension Import Mode ( Merge or Replace), select Deploy after Import, enter the remaining parameters to deploy the application view to a physical
15 Review the Migration Summary, and click Save Migration Definition.
16 Click OK.
17 In the File Download dialog box, click Save.
19 In the Download Complete dialog box, click Close.
20 Click Close again.
21 Click Execute Migration.
The migration is executed.
22 Click Launch Migration Status Report to view the status of the migration.
Notice that the migration is completed.
23 Click Cancel to close the Migration Status Report.
25 Review the Selected Artifacts tab to view the artifacts that you selected for the migration.
26 Click Define Migration.
27 Select the Financial Report artifacts (FR artifacts), and click Next.
28 Review the Source Options page, and click Next.
29 On the Destination page, select the Reporting and Analysis repository, and click Next.
30 Optional: On the Destination Options page, select Exclude job output on import, and click Next.
32 Review the Source Options page, and click Next.
33 Select the destination Planning application that you want the application to import to, and click Next.
34 Review the Destination Options page, and click Next.
35 Review the Migration Summary page, and click Save Migration Definition.
36 Click OK.
38 Enter the location and migration definition file name, and click Save.
39 In the Download Complete dialog box, click Close. 40 Click Close again.
41 Click Execute Migration.
42. Click Launch Migration Status Report.
The migration is completed.
Summary
Congratulations! You have completed your first migration by using Shared Services Lifecycle Management 11.1.1. To review the steps that you completed: Export the application artifacts from your source environment to the file system.
Copy the application artifacts from your source environment file system to the destination environment file system. Create a Planning classic application in the destination environment.
Creating and Initializing Oracle Hyperion Capital Asset Planning Applications
Prerequisites
Before starting this tutorial, you should understand:
1. Planning functionality.
2. Capital Asset Planning business model. The following are also required:
1. Oracle Hyperion Planning 11.1.1 (installed and configured)
2. Capital Asset Planning 11.1.1 (This product option must be enabled in the System Configurator.) 3. Two empty relational databases
This tutorial uses Oracle 11g as the relational storage. For a list of supported relational databases, as well as information about the required components for Planning, consult the following documentation:
Oracle Enterprise Performance Management System - Installation Start Here
Oracle Enterprise Performance Management System - Installation and Configuration GuideYou can download Oracle Enterprise Performance Management System documentation from the Oracle Software Delivery Cloud website.
Using Performance Management Architect
When you create and initialize Capital Asset Planning in Performance Management Architect, you must complete the following tasks: Create a Capital Asset Planning application
Verify the Capital Asset Planning application initialization
To create a Capital Asset Planning application:
1. Log on to Workspace, and select Navigate > Administer > Application Library.
3. In the Application Information area, enter an application name, and select Planning as the type. Optional: Select Auto Create Local Dimensions.
4. In the Planning area, clear all plan types, and select Capital Asset. Optional: Select a default currency and Use Multiple Currencies.
5. In the Calendar area, make your selections, and click Next.
6. Review the Dimension Selection page, make the necessary modifications to the list of dimensions, and click Next.
7. Click OK.
9. Review the messages. If errors are found, make the necessary modifications to the dimension members .
10. Click Finish.
11. In the Deploy dialog box, select the appropriate values for the following:
Instance Name
Application Server
Shared Services Project13. On the New Data Source page, enter a data source name and click Next.
14. Enter the database connection details, and click Test Connection. When the connection displays as successful, click Next.
15. Enter the Essbase server details, test the connection, and click Next.
17. Select Create Outline, and click Deploy.
18. Click the Click here to navigate to jobs link.
To verify the Capital Asset Planning application initialization:
1. Select Navigate > Applications > Planning > [Application Name].
If the application name does not display, select Navigate > Applications > Planning > Refresh and repeat step 1.
2. In the left pane, expand Forms > Capital to display the predefined data forms.
Using Classic Administration
When you create a classic Capital Asset Planning application, you must complete the following tasks: Create a Capital Asset Planning application
Initialize Capital Asset Planning
To create a Capital Asset Planning application:
1. In Workspace, select Navigate > Administer > Classic Application Administration > Planning Administration.
3. In the content pane, click Create Data Source.
4. Enter a data source name, and perform the following actions:
Select a database platform and, in the Application Database area, enter the relational database connection information.
Click Validate Database Connection.
In the Essbase Server area, enter the Essbase connection details.
Click Validate Essbase Connection.
Click Finish.5. In the left pane, click Create Application.
6. Enter an application name, make the following selections, and click Next.
Data Source
Shared Services Project7. Make your selections for the calendar period settings, and click Next.
8. Accept the default application currency and multiple currency settings, and click Next.
9. Select Capital Expense as the type, enter a name for the plan, and click Next.
11. Click the here first to refresh workspace Navigate > Applications menu link.
To initialize Capital Asset Planning:
1. Select Navigate > Applications > Planning > CAP02.
2. In Planning, select Edit > Initialize Capital Asset Planning.
4. When a dialog box displays a message that Capex has been successfully initialized, click OK.
5. In the left pane, expand form, and select Capital to display the predefined data forms.
6. Select Administration > Manage Database.
7. Select Database, and click Create.
8. Click Create.
9. Click Finish.
Summary
Loading Employees and Employee Data in Oracle Hyperion Workforce Planning 11.1.1
Prerequisites
Before starting this tutorial, you should understand:
1. Oracle® Hyperion Planning, Fusion Edition functionality.
2. The Workforce Planning business model.
3. Performance Management Architect functionality. The following are also required:
1. Workforce Planning must be installed and configured.
2. Workforce Planning application
3. ADS file containing employee data.
Contact your consultant for more information about creating a customized ADS file.
You can download Oracle Enterprise Performance Management System documentation from the Oracle E-Delivery website.
Importing Employee Data
1. In the Dimension Library, select File > Import > Create Profile.
2. Enter the following information and click Browse:
Profile name
FlatFile as the import Type
Application that contains the Workforce Planning plan type3. Click Browse.
5. Click Upload.
6. Click OK.
7. Select the column delimiter used in your ADS file, and click Next.
8. Select the following options and click Next:
Create dimensions for the non-mapped dimensions with the source dimension name9. Click Finish.
10. Click Yes.
11. Click Click here to navigate to jobs.
13. In Workspace, select Navigate > Administer > Application Library.
14. Right-click [Workforce Application] and select Validate > Application.
16. In the Job Console, refresh the page until the status displays as Completed.
17. Return to the Application Library, right-click [Workforce Application] and select Deploy > Application.
19. Click Click here to navigate to jobs.
20. In the Job Console, refresh the page until the status displays as Completed.
Adding Headcount (To-Be-Hired)
1. In Workspace, select Navigate > Applications > Planning > [Workforce Planning Application].
2. From the left pane, expand Forms.
3. Click Workforce.
5. Select Operations and click Go.
6. In the content area, right-click and select Add To-be-hired > Salary.
7. Enter the to-be-hired information and click Validate.
8. When all entries are validated with no errors, click Add.
9. Save your data form.
Reconciling Existing Employees
1 Right-click TBH1 and click Reconcile To-be-hired.
2. In the From Employee text box, enter the employee to be reconciled and click Validate.
3. Click Reconcile.
4. In the left pane, click Manage Existing Employees.
The imported and reconciled employees are displayed in the Manage Existing Employees form.
5. Make the necessary changes and click Save.
Summary
Creating and Initializing Workforce Planning Applications
Prerequisites
Before starting this tutorial, you should understand:
1. Oracle Hyperion Planning functionality.
2. The Workforce Planning business model. The following are also required:
1. Oracle Hyperion Planning 11.1.1 must be installed and configured.
2. The Workforce Planning 11.1.1 product option must be enabled in the System Configurator.
3. Two empty relational databases.
This tutorial uses Oracle 11g as the relational storage. For a list of supported relational databases, please consult the installation documentations (below) You can find more information on the required components for Oracle Hyperion Planning 11.1.1 in the following documentation:
Oracle Enterprise Performance Management System - Installation Start Here
Oracle Enterprise Performance Management System - Installation and Configuration GuideYou can download Oracle Enterprise Performance Management System documentation from the Oracle Software Delivery Cloud website.
Using Performance Management Architect
When you create and initialize Workforce Planning in Performance Management Architect, you must complete the following tasks: Create a Workforce Planning application
Verify the Workforce Planning application initialization
To create a Workforce Planning application:
1. Logon to Workspace and select Navigate > Administer > Application Library.
3. In the Application Information area, enter an application name and select Planning as the type. Optional: Select Auto Create Local Dimensions.
4. In the Planning area, deselect all plan types and select Workforce. Optional: Select a default currency and Use Multiple Currencies.
5. In the Calendar area, make your selections and click Next.
6. Review the Dimension Selection page, make the necessary modifications to the list of dimensions, and click Next.
7. Click OK.
9. Review the messages section. If errors are found, make the necessary modifications to the dimension members .
10 Click Finish.
11 In the Deploy dialog box, select the appropriate values for the following:
Instance Name
Application Server
Shared Services Project12 Click the Data Source icon.
14 Enter the database connection details and click Test Connection.
When the connection displays as successful, click Next.
15 Enter the Essbase server details, test the connection, and click Next.
16 Click Finish.
17 Select Create Outline and click Deploy.
19. Review the job console and click Refresh until the status displays as Completed.
To verify the Workforce Planning application initialization:
1. Select Navigate > Applications > Planning > [Application Name].
If the application name does not display, select Navigate > Applications > Planning > Refresh and repeat step 1.
Using Classic Administration
When you create a classic Workforce Planning application, you must complete the following tasks: Create a Workforce Planning application
Initialize Workforce Planning
To create a Workforce Planning application:
1. In Workspace, select Navigate > Administer > Classic Application Administration > Planning Administration.
2. From the left pane, click Manage Data Source .
3. From the content pane, click Create Data Source.
4. Enter a data source name and perform the following actions:
Select a database platform and enter the relational database connection information in the Application Database area.
Click Validate Database Connection.
Enter the Essbase connection details in the Essbase Server area.
Click Validate Essbase Connection.5. From the left pane, click Create Application.
6. Enter an application name, make the following selections, and click Next.
Data Source
Shared Services Project
Instance7. Make your selections for the calendar period settings and click Next.
9. Select Workforce Planning as the type and enter a name for the plan. Click Next.
10. Verify the application settings you chose and click Finish.
To initialize Workforce Planning:
1. Select Navigate > Applications > Planning > WFP02.
2. In Planning, select Edit > Initialize Workforce.
3. When prompted if you want to proceed with the initialization, click OK.
4. When finished, a dialog box displays that Workforce has been successfully initialized. Click OK.
5. From the left pane, expand forms and select Workforce to display the pre-defined data forms.
7. Select Database and click Create.
8. Click Create.
9. Click Finish.
Summary
Hyperion PLANNING RELEASE 11.1.2.2.
Automating Planning Administrative Processes Using the Oracle® Hyperion Enterprise Performance
Management Architect, Fusion Edition Batch Client 11.1.2
Prerequisites
Before starting this tutorial, you should:
1 . Have administrator access to a working installation of Planning 11.1.2.
2 . Have administrator access to a working installation of Hyperion® Shared Services 11.1.2.
3 . Have administrator access to a working installation of Enterprise Performance Management Architect 11.1.2.
Preparing to Use Batch Client
To prepare using Batch Client:
Downloading Documentation
To download documentation:
1 . Launch your browser.
2 . Navigate to the Oracle Enterprise Performance Management System, Fusion Edition Release 11.1.2 Documentation Library by using the
following URL:
http://download.oracle.com/docs/cd/E17236_01/index.htm
3 . In the left menu, click Foundation Services.
4 . Under Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition, for Batch Client User's Guide, right-click PDF and select
Save Link As....
Accessing Batch Client
To access Batch Client:
1 . Select Start, Programs, then Oracle Enterprise Performance Management System, then Foundation Services, then Performance Management Architect,and then Start EPMA Batch Client.
The Batch Client command window is displayed:
Logging On to Performance Management Architect
To log on to Performance Management Architect:
1 . Set the server URLs by using the following commands, and press Enter after each line item:
set bpmaserverurl=http://localhost/hyperion-bpma-server; set workspaceurl=http://localhost:19000/workspace;
Note: Contact your administrator for your company's server URLs.
2 . Enter your Performance Management Architect username and password with the following syntax, and press Enter: login username,password;
Creating Planning Applications
Performance Management Architect Batch Client enables you to create a new, empty Planning application with the specified name. Empty applications are oftentimes referred to as shell applications. After creating shell applications, you can create, import, or copy dimensions and members in Shared Library and within Planning applications.
Creating Shell Applications
To create shells for Planning applications:
1 . Create the shell application with the following syntax, and press Enter:
Create Application Properties(ApplicationName, ApplicationDescription, ApplicationType) Values('PlanBud', 'Planning Budget Application', 'Planning');
Application Name—A string containing a valid name for the application. In this example, 'PlanBud' is used.
ApplicationDescription—A string containing a valid description for the application. In this example, 'Planning Budget Application' is used.
ApplicationType—Enter 'Planning' for Planning applications.The following message is displayed: The application "PlanBud" has been created with objectid "1_4".
Adding Dimensions and Members
You can create dimensions and members in Shared Library or within an application. You can add dimensions and members to the Shared Library, or you can copy them from the Shared Library to an application. You can add dimensions as shared dimensions or you can copy them to the application as local dimensions. You can insert a copy of a member as a shared member in an application. However, you can use the Insert Member command only on local dimensions and Shared Library dimensions. You cannot insert members in a shared dimension in an application. You can also import dimensions and members to an application or Shared Library using an ADS file. This section covers the different methods of adding dimensions and members by using Batch Client:
1 . Create dimensions with the following syntax and press Enter:
Create Dimension Properties(ApplicationName, DimensionName, DimensionDescription, DimensionType) Values(#Shared,'Entity','Entity Dimension','Entity');
ApplicationName—The name of an existing application. Use #Shared to create a dimension in the Shared Library.
DimensionName—A valid name for the dimension. In this example, 'Entity' is used.
Dimension Description—A string containing a valid description for the dimension. In this example, 'Entity Dimension' is used.
DimensionType—Dimension Type can be any one of the following: Account, Alias, AllocationType, Attribute, ConsolidationMethod, Country, Currency, Entity, Generic, ICP, Measure, Scenario, SecurityClass, SmartList, Time, UDA, Value, Version, View, Year.Note: Planning requires six dimensions. If these six dimensions are already created in Dimension Library, you can add them to the application
instead.
2 . Create members with the following syntax and press Enter:
Create Member Properties(ApplicationName, DimensionName, ParentName, MemberName, MemberDescription) Values('PlanBud','Account', '#root', 'Income Statement', 'Income Statement Accounts');
ApplicationName—The name of an existing application. Use #Shared to create a dimension in the Shared Library. In this example, 'PlanBud' is used.
DimensionName—The name of an existing dimension. In this example, 'Account' is used.
ParentName—The name of the parent under which to insert the newly created member. Use #Root to add a new member at the top level of the tree.
MemberName—A valid name for the new member. In this example, 'Income Statement' is used.
MemberDescription—A description for the new member. In this example, 'Income Statement Accounts' is used.
3 . Import dimensions and members by using an ADS file with the following syntax, and press Enter:
Execute Import Parameters(importtype, profilename, filename, waitforcompletion)Values('flatfile', 'PlanApp', '.\AppFiles\PlanApp.ads', 'true');
ImportType—The type of import to perform. Allowed values are: FlatFile and InterfaceTables.
ProfileName—The name of an existing import profile. In this example, 'PlanApp' is used.
FileName—The name of the flat file to import, if performing a flat file type import. In this example, the 'PlanApp.ads' flat file in the AppFiles directory is used.Allowed values are: True or False.
The following figure displays a sample ADS file:
4 . Use the following syntax to copy dimensions within Shared Library, within an application, or between Shared Library and an application, and
press Enter:
Copy Dimension Properties(ApplicationName, DimensionName, TargetDimensionName, TargetDimensionDescription, destApplicationName) Values('#Shared', 'Scenario','Scenario', 'Scenario Dimension', 'PlanBud');
ApplicationName—The name of an existing application. Use #Shared to copy a dimension from the Shared Library.
DimensionName—The name of an existing dimension. In this example, 'Scenario' is used.
TargetDimensionName—The name of the target dimension. In this example, 'Scenario' is used.
TargetDimensionDescription—The description of the target dimension. In this example, 'Scenario Dimension' is used.
destApplicationName—The name of the destination application. In this example, 'PlanBud' is used.Note: You cannot copy a dimension directly from one application to another.
5 . Use the following syntax to add an existing dimension from the Shared Library to the specified application, and press Enter after each line item: SET APPLICATION = 'PlanBud';
Include Dimension Properties(DimensionName, IncludeAsShared) Values('C_Alias', 'true');
DimensionName—The name of an existing dimension in the Shared Library. In this example, 'C_Alias' is used.
IncludeAsShared—Use a value of true to include the dimension as a shared dimension. Use a value of false to include a local copy of the dimension within the application.The dimension can be added as a shared dimension or copied to the application as a local dimension.
Note: You must set the application name before the Include Dimension command. By setting the application name, command lines use it if the
application is not explicitly defined within a command.
6 . Use the following syntax to insert a copy of a member as a shared member within an application, and press Enter after each line item: SET APPLICATION = 'PlanBud';
Insert Member Properties(DimensionName, ParentName, InsertMemberName, MemberToInsertName) Values('Account', 'Par1', ‘Mem1’, ‘Mem2’);
DimensionName—The name of an existing dimension. In this example, 'Account' is used.
ParentName—Name of the parent to insert the member under. In this example, 'Par' is used.
InsertMemberName—Name of the member to insert the member under. In this example, 'Mem1' is used.
MemberToInsertName—Name of the shared member to be inserted. In this example, 'Mem2' is used.You can use the Insert Member command only on local dimensions and Shared Library dimensions. You cannot insert members in a shared dimension within an application.
Note: You must set the application name before the In command. By setting the application name, command lines use it if the application is
not explicitly defined within a command. Alternatively, you can set the application name to #Shared if you are copying a member from Shared Library.
Deploying Planning Applications
After creating the shell and adding dimensions and members, you deploy the application to make it accessible in Workspace. To deploy Planning applications, you must be provisioned with the Application Creator or Planning Administrator role.
1 . Deploy a Planning application with the following syntax, and press Enter:
Execute Deploy Parameters(ApplicationName, InstanceName, ApplicationServer, HubProject, waitforcompletion, dataSourceName, CreateOutline) Values('PlanBud', 'PLANNING', 'PLANNING', 'Default Application Group', 'true', 'ST01PLN3', 'true');
ApplicationName—The name of an existing application. In this example, 'PlanBud' is used.
InstanceName—The name of the instance to deploy to. In this example, 'PLANNING' is used.
ApplicationServer—The name of the application server to deploy to. In this example, 'PLANNING' is used.
HubProject—The Shared Services project to add the deployed application to. In this example, 'Default Application Group' is used.
WaitForCompletion—If set to true, Batch Client waits for the job to finish. If set to false, Batch Client submits the job and continues. Allowed values are: True or False
datasourceName—Creates a data source with the specified name. In this example, 'ST01PLN3' is used.
CreateOutline—Creates the Essbase outline if you are deploying the application for the first time. Allowed values are True or False.For additional Planning parameters, see the Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition 11.1.2 Batch
Client's User Guide. When the deployment is completed, the following message is displayed:
Accessing the Deployed Application in Application Library
You must log on to Workspace with an administrator account. To access the deployed application in Application Library:
1 . Log on to Workspace.
2 . Select Navigate, then Administer, and then Application Library.
