Anda di halaman 1dari 189

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.

5.

Click Go to display all user groups in Shared Services.

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.

10. Click Finish, and click OK to return to the Provisioning pane.

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.

4.

From Available Roles, expand Planning Training Applications and hyplan nodes.

5.

Select Interactive User and click Add.

6.

The Interactive User role is now displayed in the Selected Roles area. 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.

5. Click Close.

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.

2. Expand nodes to locate Planning relational database tables.

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.

5. Click Delete Selected Row(s).

6. Click Commit Changes.

7. All records are deleted.

Summary
In this tutorial, you learned how to: Enable auditing View and clear audit reports in SQL Developer

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.

3. Select Create a new datasource link 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.

6. Review the configuration summary, and click Next.

7. Click Finish.

Creating Interface Table Definitions


To create interface table definitions, perform the following steps: 1. From Workspace, select Navigate > Administer > Data Synchronization.

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.

2.

Select Hyperion Data Interface Area as the source type, and click Next.

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.

6.

Drag a source dimension to a destination dimension to manually assign or change mappings.

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.

11. When prompted to execute the profile, click Yes.

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. 2. Log on to Workspace. In Workspace, select Navigate > Administer > Classic Application Administration > Planning Administration.

3.

In Classic Administration Wizard, click Manage Data Source.

4.

Click Create Data Source.

5.

In Data Source Name, enter a data source name.

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.

8.

In the Essbase Server area, enter Essbase server details and click Validate Essbase Connection.

9.

Validate both connections and click Finish.

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.

4.

Select Administration > Manage Database.

5.

Select Database and click Create.

6.

In the Manage Database dialog box, click Create.

7.

The Cube Refresh status is displayed. 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.

The data form is displayed. Note that there is no data loaded into the application.

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

4.

Right-click your outline, and select Load data to display the Data Load pane.

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.

The Application Summary page displays the applications available for upgrade. This information is provided from the Shared Services application.

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.

7. In Job Console, click Refresh to view the status of 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.

9. Double-click your application to display Dimension Library.

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

Log on to Workspace. Select Administer > Application Library to display Application Library.

4.

In Application Library, view existing Performance Management Architect applications. In this case, only one Planning application is displayed.

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.

4. Verify that the application appears in Application Library. In this case, the PLAN3 Planning application is now displayed.

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.

4. In Workspace, select Navigate > Administer > Library Job Console.

5. In Library Job Console, verify that the application was successfully deployed.

6. In Application Library, verify that the application is now 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. You are logged on to Data Integration Manager. Next, you need to connect to the PowerCenter Repository.

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.

4.

The Application Connection Browser is displayed. From the Select Type drop-down list, select the Planning application connection.

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: 1. From Workflow Manager, select Tools > Designer .

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 .

7.

Select the delimiters and text qualifiers for the text file, 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 .

The Edit Tables dialog box is displayed.

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 .

2.

Select Targets > Import from Hyperion Planning .

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.

5.

Select the application and login details to connect to Planning.

6.

Click Test connectivity .

7.

Click OK to close the Define DSN dialog box.

8.

Click Connect to view Planning application targets.

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 .

2.

The Mapping Designer window is displayed. 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.

5.

Drag the source to the Mapping Dimension Editor.

6.

The source definition and source qualifier are displayed in the mapping dimension editor. 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.

9.

Expand the target definition to view all of its ports.

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 .

12. Press Ctrl+S to save your changes.

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 .

5.

If a workflow is open in Workflow Designer, click Yes at the prompt to close the open workflow.

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 .

10. Click Done .

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.

3.

Select the flat file source.

4.

Verify that the correct reader, (File Reader) for the flat file is selected.

5.

Verify that target properties are correct.

6.

Click OK to close the Edit Tasks window.

7.

Press Ctrl+S to save the workflow.

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.

5.

If your workflow is not valid, verify the session task properties again. Press Ctrl+S to save the workflow.

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.

4.

Verify that two source rows were successfully read from the flat file source.

5.

Click OK, and minimize open windows.

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: Planning application administrator role The destination environment user who is performing the lifecycle management activities is provisioned with the following roles:

Shared Services LCM administrator role

4.

Shared Services LCM administrator role Planning application administrator role Planning application creator role

Exporting 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:

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.

Users Native Directory users Groups Native Directory groups

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.

5. For EPMA-enabled Planning applications, navigate to Foundation > EPM Architect > Application Metadata > Planning Applications, and select the EPMA artifacts

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.

12 On the Source Options page, filter the user, groups, and roles as needed, 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.

18 Review the destination options to ensure that the parameters are correct, 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.

24 On the Source Options page, select Export with Job Output if you want that information to be migrated, 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.

30 Click Save.

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.

34 Click Execute Migration.

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.

37 Refresh the Migration Status Report to see that the migration is completed.

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.

7 Navigate to the newly mapped destination location, right-click, and select Paste.

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: The following dimension-level properties must match in both the source and the destination applications: Start year Base 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.

If the Planning application is already created in the destination environment or if the Planning application is EPMA-enabled, skip this section.

3 Select Manage Data Source.

4 Click Create Data Source.

5 Enter the parameters, and select Finish.

6 Click Create Application.

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: 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 1. In the destination, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.

Shared Services artifacts must be imported before you import Planning artifacts.

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.

Notice that the migration is executed.

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 Planning application, and click Next.

15 Review the Migration Summary, and click Save Migration Definition.

16 Click OK.

17 In the File Download dialog box, click Save.

18 Enter the location and migration definition file name, and 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.

24 Navigate to Application Groups > File System, and select the Planning application artifacts and the Planning financial reports.

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.

31 Select Planning artifacts, 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.

37 In the File Download dialog box, click Save.

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. Import the application artifacts from the destination environment file system to the application.

Creating and Initializing Oracle Hyperion Capital Asset Planning Applications Prerequisites
Before starting this tutorial, you should understand: 1. 2. Planning functionality. Capital Asset Planning business model.

The following are also required: 1. 2. 3. Oracle Hyperion Planning 11.1.1 (installed and configured) Capital Asset Planning 11.1.1 (This product option must be enabled in the System Configurator.) 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 Guide

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

2.

In the Application Library, select File > New > Application(s) .

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.

8.

In the Member area, click the plus signs (+) to display the dimensions, and click Validate.

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 Project

12.

Click the Data Source icon.

13.

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.

16.

Click Finish.

17.

Select Create Outline, and click Deploy.

18.

Click the Click here to navigate to jobs link.

19.

Review the job console, and click Refresh until the status displays a Completed message.

To verify the Capital Asset Planning application initialization:


1. Select Navigate > Applications > Planning > [Application Name].

2.

If the application name does not display, select Navigate > Applications > Planning > Refresh and repeat step 1. 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.

2. In the left pane, click Manage Data Source.

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 Project Instance

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

10. Verify the application settings, and click Finish.

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.

3.

When prompted if you want to proceed with the initialization, click OK.

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
In this tutorial, you learned how to create and initialize Capital Asset Planning applications.

Loading Employees and Employee Data in Oracle Hyperion Workforce Planning 11.1.1 Prerequisites
Before starting this tutorial, you should understand: 1. 2. 3. Oracle Hyperion Planning, Fusion Edition functionality. The Workforce Planning business model. Performance Management Architect functionality.

The following are also required: 1. 2. 3. Workforce Planning must be installed and configured. Workforce Planning application 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 type

3.

Click Browse.

4.

Locate your employee ADS file and click Open.

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 name Select All - Merge As Shared

9.

Click Finish.

10.

Click Yes.

11.

Click Click here to navigate to jobs.

12.

Click Refresh until the job status displays as Completed.

13.

In Workspace, select Navigate > Administer > Application Library.

14.

Right-click [Workforce Application] and select Validate > Application.

15.

Click Click here to navigate to jobs.

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.

18.

Select Refresh Outline and click Deploy.

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.

4.

Select New Hires.

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.

10.

Repeat steps 5 through 9 to add more headcount.

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
In this tutorial, you learned how to use Performance Management Architect to load employees and employee data into Workforce Planning applications.

Creating and Initializing Workforce Planning Applications Prerequisites


Before starting this tutorial, you should understand: 1. 2. Oracle Hyperion Planning functionality. The Workforce Planning business model.

The following are also required: 1. 2. 3. Oracle Hyperion Planning 11.1.1 must be installed and configured. The Workforce Planning 11.1.1 product option must be enabled in the System Configurator. 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 Guide

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

2. In the Application Library, select File > New > Application(s) .

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.

8. In the Member area, click + to display the dimensions and click Validate.

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 Project

12 Click the Data Source icon.

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

16 Click Finish.

17 Select Create Outline and click Deploy.

18 Click Click here to navigate to jobs.

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

2.

If the application name does not display, select Navigate > Applications > Planning > Refresh and repeat step 1. From the left pane, expand Forms > Workforce to display the pre-defined data forms.

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. Click Finish.

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 Instance

7. Make your selections for the calendar period settings and click Next.

8. Select the default application currency and multiple currency settings. 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.

11. Click here first to refresh workspace Navigate > Applications menu.

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.

6.

Select Administration > Manage Database.

7.

Select Database and click Create.

8.

Click Create.

9.

Click Finish.

Summary
In this tutorial, you learned how to create and initialize Workforce Planning applications.

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

In the left menu, click Foundation Services. Under Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition, for Batch Client User's Guide, right-click PDF and select Save Link As....

5.

Navigate to the location where you want to save the file, and click Save.

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 NameA string containing a valid name for the application. In this example, 'PlanBud' is used. ApplicationDescriptionA string containing a valid description for the application. In this example, 'Planning Budget Application' is used. ApplicationTypeEnter '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');

ApplicationNameThe name of an existing application. Use #Shared to create a dimension in the Shared Library. DimensionNameA valid name for the dimension. In this example, 'Entity' is used. Dimension DescriptionA string containing a valid description for the dimension. In this example, 'Entity Dimension' is used. DimensionTypeDimension 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');


3.

ApplicationNameThe name of an existing application. Use #Shared to create a dimension in the Shared Library. In this example, 'PlanBud' is used. DimensionNameThe name of an existing dimension. In this example, 'Account' is used. ParentNameThe 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. MemberNameA valid name for the new member. In this example, 'Income Statement' is used. MemberDescriptionA description for the new member. In this example, 'Income Statement Accounts' is used. 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');

ImportTypeThe type of import to perform. Allowed values are: FlatFile and InterfaceTables. ProfileNameThe name of an existing import profile. In this example, 'PlanApp' is used. FileNameThe 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. WaitForCompletionIf set to true, Batch Client waits for the job to finish. If set to false, the Batch Client submits the job and continues.

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');

ApplicationNameThe name of an existing application. Use #Shared to copy a dimension from the Shared Library. DimensionNameThe name of an existing dimension. In this example, 'Scenario' is used. TargetDimensionNameThe name of the target dimension. In this example, 'Scenario' is used. TargetDimensionDescriptionThe description of the target dimension. In this example, 'Scenario Dimension' is used. destApplicationNameThe 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');

DimensionNameThe name of an existing dimension in the Shared Library. In this example, 'C_Alias' is used. IncludeAsSharedUse 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);

DimensionNameThe name of an existing dimension. In this example, 'Account' is used. ParentNameName of the parent to insert the member under. In this example, 'Par' is used. InsertMemberNameName of the member to insert the member under. In this example, 'Mem1' is used. MemberToInsertNameName 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');

ApplicationNameThe name of an existing application. In this example, 'PlanBud' is used. InstanceNameThe name of the instance to deploy to. In this example, 'PLANNING' is used. ApplicationServerThe name of the application server to deploy to. In this example, 'PLANNING' is used. HubProjectThe Shared Services project to add the deployed application to. In this example, 'Default Application Group' is used. WaitForCompletionIf 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 datasourceNameCreates a data source with the specified name. In this example, 'ST01PLN3' is used. CreateOutlineCreates 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.

3.

Click the Planning application that you deployed in Batch Client. In this example, 'PlanBud' is selected.

When you select an application, the following information is displayed in the lower pane:

SummaryContains the name, type, date created, date last deployed, and the associated data synchronizations. DescriptionContains the information that you provided in the Description field when you created the application. DimensionsLists the dimensions available in the application. PropertiesDisplays the status, default currency, and specific properties set for the application. SynchronizationsLists the data synchronizations for this application. Rules / Rule SetEnumerates the rules and rule sets defined in Calculation Manager for this application.

Summary
In this tutorial, you have learned how to: Download documentation and access Batch Client Create Planning applications using Batch Client Deploy Planning applications using Batch Client Access the deployed Planning application in Application Library

Resources Oracle Hyperion Enterprise Performance Management Architect Batch Client User's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/epma_batch_user.pdf) Oracle Hyperion Shared Services User and Role Security Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/hss_admin.pdf) Oracle Enterprise Performance Management Workspace, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/bpmui_admin.pdf)

Creating and Initializing Oracle Hyperion Capital Asset Planning, Fusion Edition 11.1.2 Applications Prerequisites
Before starting this tutorial, you should: 1 . Have administrator access to a working installation of Planning 11.1.2 with Capital Asset Planning enabled. 2 . Have administrator access to a working installation of Hyperion Shared Services 11.1.2. 3 . Have administrator access to a working installation of Performance Management Architect 11.1.2. 4 . Have created Planning datasources. This tutorial requires: 1. One datasource for the Capital Asset Planning application created in Performance Management Architect. 2. One data source for the Capital Asset Planning application created in Classic Application Administration. 5 . Have a working Planning application that was created in Performance Management Architect. Before you initialize Capital Asset Planning:

Download the Creating and Initializing Oracle Hyperion Capital Asset Planning, Fusion Edition 11.1.2 Administrator's Guide and read Appendix A, Capital Asset Planning Structure. Review the predefined elements, identifying which elements you can use and which elements you need to customize. Update dimension outlines to resolve differences between Capital Asset Planning member names and member names of other applications. Plan the structure of the Entity dimension if you intend to use both Capital Asset Planning and Oracle Hyperion Workforce Planning, Fusion Edition. Initializing Workforce Planning produces one No Entity member, whereas initializing Capital Asset Planning produces a few Entity members. You can change the Entity members after you initialize the applications.

Creating Capital Asset Planning Applications in Performance Management Architect


You perform the following tasks in this topic:

Create a Capital Asset Planning application using the Application Creation Wizard Access the Capital Asset Planning application

Creating a Capital Asset Planning Application Using Application Creation Wizard


In this example, you create a Capital Asset Planning application with no additional plan types. To create Capital Asset Planning applications in Performance Management Architect by using Application Creation Wizard: 1. Log on to Workspace. 2. Select Navigate, then Administer, and then Application Library.

Application Library is displayed. Sample applications were created in the tutorial environment. Note that these Planning applications are not included with the software.

3.

In Application Library, select File, then New, and then Application (Z).

The Application Creation Wizard is displayed.

4.

In the Application Information area, perform the following actions:

Enter an application name. Select Planning as the type. Enter a description. Select Auto Create Local Dimensions.

5.

In the Planning area, perform the following actions:

Select General as the application type. Clear all plan type selections. Select Capital Asset Name and enter a plan type name. Accept USD as the default currency. Select Use Multiple Currencies.

6.

In the Calendar area, select a base time period, fiscal start month, and weekly distribution.

7.

For Period and Year, perform the following actions:

Select Create New Local Period Dimension. Enter Period as the period name. Select Create New Local Year Dimension. Enter Year as the year name. Select the first fiscal year. Select the number of fiscal years for the application.

8. 9.

Click Next. Review the Dimension Selection page, make the necessary modifications, and click Next.

10.

The following message is displayed: Dimensions for Capital Asset have been seeded. Click OK.

The Application Settings page is displayed.

11.

In the Member Area, expand CapEx.

The dimensions created for the application are displayed.

12.

13.

Click Validate. The validation process checks for missing dimensions and other required information. If anything is missing in the application, the deployment is aborted. If another deployment for the application is in progress, the request is cancelled. Review the listed messages. If errors are found, make the necessary modifications to the dimension members.

14.

Tip: Period and Year dimension errors usually appear when you do not select Create New Local Period Dimension and Create New Local Year Dimension during application creation. Click Validate to ensure that no error messages are displayed.

15. 16.

Click Finish. The deployment process involves the following steps: Validate the applicationThe validation process is run upon application deployment. Selecting the environment information for deploymentSelect the server and instance to which you are deploying the application. Export and deploy the applicationWhen you deploy an application, the deployment job begins and the application is exported from Performance Management Architect to Planning. Create the product applicationIn new deployments, Planning creates the application and the product server attempts to load the metadata. After deployment is completed, the status and deployment timestamp is updated in Application Library, and the deployment job is marked completed and free of errors, the deployed Planning application becomes accessible in Oracle Enterprise Performance Management Workspace, Fusion Edition (Workspace). On the Deploy page, enter the required information and click Deploy.

Select a Planning instance. In this example, PLANNING is selected. Select a Planning application server. In this example, PLANNING is selected. Select a Shared Services project (application group). In this example, Default Application Group is selected. Select a Planning datasource. In this example, ST01PLN6 is selected. Select Create Outline. Optional: Select Create Security Filters. Optional: Select Shared Members Security Filters. The application name and description are entered when you first create the application in Performance Management Architect and are not editable. In the Job Task dialog box, click the Click here to navigate to jobs link.

17.

After the deployment action is initiated, you can check Job Console for results. For Capital Asset Planning applications, the deploy process creates the following:


18.

Tables and values in the Planning database. An application and outline in Essbase without the need to refresh the cube from the Planning Web user interface. HSP_Rates, for multi-currency applications, upon deployment (it is not a dimension that you create manually). Capital Asset Planning-specific dimensions, members, data forms, smart lists, member formulas, business rules, and menus. On the Job Console toolbar, click Refresh to update the job results. Job Console:

A job ID is associated with each task in Job Console, which displays the following information:

o o o o o o o o

SummaryInformation about the job: Started Timestart time for small jobs. Submitted Timestart time for large jobs. Last Updated Timelast time the job was updated. User Nameuser name that submitted the job. Process Nameprocess name in which the job is running Threadthread ID of the current job. Serverserver name where the job is running. Detailjob summary, including errors and warnings. Attachmentsfile attachments associated with the job. Statusstatus and progress of the job. Each job can have the following status: Invalid, Scheduled Start, Queued, Scheduled Stop (cancelled by the user), Starting, Running, Stopping, Stopped (aborted by the user), Aborted (aborted due to an error), Completed, Completed With Errors, and Not Responding.

Accessing the Capital Asset Planning Application


After deploying the application, you refresh the application list and access it through Workspace. To access the Capital Asset Planning application after deployment: 1 . In Workspace, select Navigate, then Applications, and then Refresh.

2.

The application list is refreshed. Select Navigate, then Applications, then Planning, and then <Application Name>. In this example, the CapEx application is selected.

The application is displayed. 3. In the Select Data Form area, expand Forms and select Capital.

The predefined Capital Asset Planning data forms are displayed in the content area.

Adding the Capital Asset Planning Plan Type to an Existing Planning Application
If you have an existing Planning application, you can add the Capital Asset Planning plan type to it in Performance Management Architect by selecting the Initialize menu command.

Initializing the Capital Asset Planning Plan Type


To initialize the Capital Asset Planning plan type: 1. In Workspace, select Navigate, then Administer, and then Application Library.

2.

In Application Library, select the Planning application in which you want to add the Capital Asset Planning plan type. In this example, the Capital Asset Planning plan type is added to PlanBud.

3.

Right-click the application and select Initialize, and then Capital Asset.

Note: Select Workforce and Capital Asset if the application will use both plan types. 4. In the Confirm Initialization dialog box, click Yes.

The validation process runs before the deployment. The following message is displayed: Validating Application for Deploy.

5.

On the Deploy page, enter the required information and click Deploy.

The following message is displayed while dimensions are created in the application: Seeding dimensions for Capex.

For more information on the deployment process, click here. 6. In the Job Task dialog box, click the Click here to navigate to jobs link.

7.

On the Job Console toolbar, click Refresh to update the job results. Job Console:

The application deployment displays a progress of 100% when it is completed. For more information on Job Console, click here.

Accessing the Updated Application in Workspace


After the deployment is completed, you access the updated application in Workspace. To access the updated application in Workspace: 1 . In Workspace, select Navigate, then Applications, then Planning, and then <Application Name>. In this example, the PlanBud. application is selected.

The application is displayed. 2. In the Select Data Form area, expand Forms and select Capital.

The predefined Capital Asset Planning data forms are displayed in the content area.

Creating Capital Asset Planning Applications in Classic Application Administration Creating Classic Capital Asset Planning Applications
To create Classic Capital Asset Planning applications: 1. Log on to Workspace. 2. Select Navigate, then Administer, then Classic Application Administration, and then Planning Administration.

3.

In Classic Application Wizard, click Create.

4.

On the Select tab, perform the following actions:

Select a data source. In this example, ST01PLN4 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, ClCapEx is entered. Enter a description of the application. In this example, Classic Capital Asset Planning application is entered. Select a Shared Services project (application group). In this example, Default Application Group is selected. Select an instance (cluster) to use for the application. In this example, PLANNING is selected. For Calculation Module, select Business Rules or Calculation Manager. In this example, Calculation Manager is selected.

5. 6.

Select the Calendar tab. Select the base time period, fiscal start year, fiscal start month, weekly distribution, and total years.

7. 8.

Select the Currencies tab. Select the default application currency. If the application supports multiple currencies, select Yes.

9. 10.

In this example, USD is selected as the default application currency, and multiple currencies are supported. Select the Plan Types tab. Perform the following actions: Clear all plan type selections. Select Capital Asset Planning under Planning Specialized Modules. Enter CapEx as the name for the Capital Asset Planning plan.

11. 12.

Select the Finish tab. Review your selections and click Finish to create the application.

When the application creation is successfully completed, the following message is displayed:

Accessing and Initializing the Application


To access and initialize the Capital Asset Planning application: 1 . Next to Go to the new application:, click the application name. In this example, ClCapEx is clicked.

The application is displayed.

2.

Select Administration, then Initialization, and then Capital Asset.

3.

When prompted to proceed with the initialization, click OK.

4.

At the confirmation message confirms that initialization is successful, click OK.

5.

The application is displayed. In the Select Data Form area, expand Forms and select Capital.

The predefined Capital Asset Planning data forms are displayed in the content area.

Summary
In this tutorial, you learned how to:

Create Capital Asset Planning applications in Performance Management Architect Add the Capital Asset Planning plan type to an existing Planning application Create Capital Asset Planning applications in Classic Application Administration

Resources

Oracle Hyperion Planning, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin.pdf) Oracle Hyperion Capital Asset Planning, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/cpx_admin.pdf) Oracle Enterprise Performance Management Workspace, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/bpmui_admin.pdf)

Creating Classic Planning Applications in Oracle Hyperion Planning, Fusion Edition 11.1.2 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. 4.

Select the Calendar tab. Select the base time period, fiscal start year, fiscal start month, weekly distribution, and total years.

5. 6.

Select the Currencies tab. Select the default application currency. If the application supports multiple currencies, select Yes.

7. 8.

Select the Plan Types tab. 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.

9. 10.

Note: The name and number of plan types depend on your business requirements. Select the Finish tab. 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.

2.

The Refresh menu option updates the navigation menu with new applications. 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.

6.

You manage data forms and folders, and ad hoc grids in the Data Form Management page. 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, then Planbud, and then [Plan Type]. In this example, the PlanBud application is accessed from the UPKPS1RC4:1423 Essbase Server view. The Incstmt 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. Resources Oracle Hyperion Planning, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin.pdf) Oracle Essbase Database Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag.pdf) Integrating Oracle Internet Directory and Hyperion Shared Services 11.1.2 Prerequisites Before starting this tutorial, you should: 1 . Have administrator access to a working installation of Shared Services. 2 . Have administrator access to a working installation of Oracle Internet Directory. Configuring Oracle Internet Directory in Shared Services Adding New User Directories You must log on to Shared Services using an administrator account to perform the following steps. To add new user directories: 1 . Log on to Shared Services. 2 . Select Administration, and then Configure User Directories.

The Defined User Directories page is displayed. 3. Click New.

4.

Under Directory Type, select Lightweight Directory Access Protocol (LDAP).

5.

Click Next.

Setting the Connection Information The Connection Information page contains the information used to connect to the directory server. To set the connection information: 1 . In the Directory Server drop-down list, select Oracle Internet Directory.

2.

Enter a name for the connection.

3.

The connection name is used to identify a specific user directory if multiple user directories are configured. Enter a host name.

4.

Enter the OID port number.

5.

The default port number for Oracle Internet Directory is 389. In this example, a custom port is used. Optional: Select SSL Enabled if the user directory is configured for secure communication.

6.

In this example, SSL is not enabled. Click Fetch DNs.

7.

You can also enter the Base Distinguished Name (DN). Accept the default value for the ID attribute.

8.

In the Maximum Size text box, enter the maximum number of results that a search can return.

9.

Select Trusted if this provider is a trusted single sign-on (SSO) source.

SSO tokens from trusted sources do not contain the user's password. 10 . Ensure that Anonymous Bind is not selected.

11 . Enter the User DN and password.

12 . Optional: Select Append Base DN if you want to append the Base DN to the User DN.

13 . Click Next. Setting Properties for the User URL Shared Services uses the properties set on the User Configuration page to create a user URL for determining the starting node for user searches. The URL speeds the search. Note: The user URL should not point to an alias. Enterprise Performance Management System security requires that the user URL points to an actual user. With OID, you cannot automatically configure the user filter, because the root Directory System Agent Specific-Entry (DSE) of OID does not contain entries in the Naming Contexts attribute. To set the properties for the user URL: 1 . Optional: Enter a unique user identifier and click Auto Configure.

2.

If you choose to auto configure, the values for the succeeding text boxes will be filled in for you. Enter a user RDN.

3.

Each DN component is called a relative distinguished name (RDN) and represents a branch in the directory tree. The RDN of a user is generally the equivalent of the user ID (uID) or common name (cn). Enter a login attribute.

4.

The login attribute stores the user's login name. You use the login attribute as the user name when you log on to EPM System products. Note: If you are configuring OID as an external user directory for EPM System products deployed on Oracle Application Server in a Kerberos environment, you must set this property to userPrincipalName. Enter a first name attribute.

5.

This attribute stores the user's first name. Enter a last name attribute.

6.

This attribute stores the user's last name. Optional: Enter an email attribute.

7.

This attribute stores the user's e-mail address. Enter an object class name, and click Add.

8.

Shared Services uses the object classes (the mandatory and optional attributes associated with the user) listed on this page to locate users who should be provisioned. Click Next.

Setting Group Properties Shared Services uses the properties set on the Group Configuration page to create the group URL for determining the starting node for group searches. The URL speeds the search. Note: The Group URL should not point to an alias. EPM System security requires that the group URL point to an actual group. Data entry on the Group Configuration page is optional. If you do not enter the group URL settings, Shared Services searches within the Base DN to locate groups. The search can negatively affect performance, especially if the user directory contains many groups. With OID, you cannot use the autoconfigure feature, because the root DSE of OID does not contain entries in the Naming Contexts attribute. To set group properties: 1 . If you do not plan to provision groups or if users are not categorized into groups on the user directory, clear Support Groups and skip to step 5. Otherwise, proceed to step 2.

2.

Clearing this option disables the fields on this page. Optional: Enter a unique group identifier and click Auto Configure.

3.

f you choose to auto configure, the values for the succeeding text boxes will be filled in for you. Enter a group RDN.

4.

The Group RDN has a significant impact on login and search performance. Because it is the starting point for all group searches, you must identify the lowest possible node in which all groups for EPM System products are available. For optimum performance, ensure that the number of groups present within the group RDN do not exceed 10,000. If more groups are present, use a group filter to retrieve only the groups that you want to provision. Enter a name attribute.

5.

This attribute stores the name of the group. Enter an object class name, and click Add.

6. 7.

Shared Services uses the object classes (the mandatory and optional attributes) listed on this page to locate groups that should be provisioned. Click Save. When the following status message is displayed, click OK.

The Oracle Internet Directory that you added is displayed on the Provider Configuration tab on the Defined User Directories page.

8.

Select File, and then Logout.

9 . Restart services. Testing the OID Connection You must log on Shared Services using an administrator account to perform the following steps. To test the OID connection in Shared Services: 1 . Log on to Shared Services. 2 . Select Administration, and then Configure User Directories.

The Defined User Directories page is displayed.

3.

Ensure that the OID directory is selected, and click Test.

When the connection test is successful, the following status message is displayed:

4.

If the connection test failed, proceed to the next topic to edit directory settings. When the following message is displayed, click Save.

5 . Click OK. Editing Directory Settings You must log on to Shared Services using an administrator account to perform the following steps. To edit directory settings in Shared Services: 1 . In Shared Services, select Administration, and then Configure User Directories.

2.

The Defined User Directories page is displayed. Select the Oracle Internet Directory that you want to modify and click Edit.

3.

Modify the configuration settings as needed.

4. 5.

Note: You cannot modify the configuration name. Click Save. When the following message is displayed, click OK.

6.

Select File, and then Logout.

7 . Restart services. 8 . Optional: Log on to Shared Services and test your connection. Deleting Configured Directories You must log on Shared Services using an administrator account to perform the following steps.

To delete configured directories in Shared Services: 1 . In Shared Services, select Administration, and then Configure User Directories.

2.

The Defined User Directories page is displayed. Select the Oracle Internet Directory that you want to delete and click Delete.

3.

When you are prompted to delete the external directory, click OK.

4.

When the following message is displayed, click OK.

5.

Select File, and then Logout.

6 . Restart services. Summary In this tutorial, you have learned how to:

Configure an Oracle Internet Directory in Shared Services Edit directory settings Delete configured directories Resources Oracle Hyperion Enterprise Performance Management System Security Administration Guide

User and Role Security Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/hss_admin.pdf) Oracle Internet Directory Administrator's Guide (http://docs.oracle.com/cd/E12839_01/oid.1111/e10029.pdf) First-Time Oracle Hyperion Enterprise Performance Management System Lifecycle Management Migration for Oracle Hyperion Planning, Fusion Edition 11.1.2 with Hyperion Shared Services 11.1.2 Prerequisites Before starting this tutorial, you should: 1 . Have Planning Administrator and Application Creator access to a working installation of Oracle Hyperion Planning 11.1.2, in both source and destination environments. The source and destination environments must use the same release number. 2 . Have administrator access to Shared Services 11.1.2, in both source and destination environments. 3 . Have Lifecycle Management Administrator access to Lifecycle Management 11.1.2, in both source and destination environments. 4 . Have defined a Planning data source in the destination environments. 5 . Have a working source Planning application with all required metadata loaded. Note: Lifecycle Management does not migrate data. Exporting Planning Applications You must migrate EPM System artifacts, as they relate to Planning. Exporting Shared Services Users, Groups, and Roles Before migrating a Planning application, you must migrate the Shared Services Native Directory artifacts (users, groups, and roles). To migrate Shared Services users, groups, and roles: 1. Log on to Workspace. 2. Select Navigate, then Administer, and then Shared Services Console.

3.

In the left pane, expand Application Groups, then Foundation, and then Shared Services.

4.

The content pane opens the Artifact List tab, which contains artifacts that you can export from Shared Services. Expand Native Directory, and make the following selections:

Groups Roles

Users

5.

At the bottom of the page, click Define Migration.

6.

Enter filters for the source users, groups, and roles and click Next. In this example, the default (asterisk wildcard) is accepted.

7.

On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be exported, and click Next. In this example, the file system folder is named hss_ugr.

8.

Review the destination options to ensure that the parameters are correct, and click Next.

9.

Review the migration summary and click Execute Migration.

10.

Click Launch Migration Status Report.

11.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully. In the left pane, the exported artifacts are displayed under File System.

Exporting Assigned Roles Each EPM System product provides several default roles tailored to various business needs. Each application belonging to an EPM System product inherits these roles. Predefined roles from the applications registered with Shared Services are displayed in Shared Services Console. When you assign a predefined product role to a user, you must migrate the Assigned Roles directory to ensure the same access between source and destination environments. To export assigned roles: 1. In the left pane, expand Application Groups, then Foundation, and then Shared Services.

2.

In the content pane, select the assigned roles for products that contain artifacts for the Planning application and click Define Migration. In this example, assigned roles for the Hyplan Planning application and Foundation Services are selected.

3.

Enter filters for the roles and click Next. In this example, the default (asterisk wildcard) is accepted.

4.

On the Destination page, enter the name of the file system folder where the Shared Services role artifacts will be exported, and click Next. In this example, the file system folder is named hss_roles.

5.

Review the destination options to ensure that the parameters are correct, and click Next.

6.

Review the migration summary, and click Execute Migration.

7.

Click Launch Migration Status Report.

8.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully. In the left pane, the exported artifacts are displayed under File System.

Exporting Shared Library In this tutorial, the Performance Management artifacts are split into two sets: Shared Dimensions and Application. The Shared Dimensions directory contains shared dimensions artifacts, such as entity, account, and year. To export Shared Library dimensions: 1. In the left pane, expand Application Groups, then Foundation, and then EPM Architect..

2.

In the content pane, expand Shared Library Dimensions, select the dimensions that you want to export, and click Define Migration. In this example, all dimensions in the source's Shared Library are selected.

3.

Review the source options and click Next.

4.

On the Destination page, enter the name of the file system folder where the Shared Library artifacts will be exported, and click Next. In this example, the file system folder is named epma_shared.

5.

Review the destination options to ensure that the parameters are correct, and click Next.

6.

Review the migration summary and click Execute Migration.

7.

Click Launch Migration Status Report.

8.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.

Exporting Performance Management Applications Planning applications require a shell application: either a Classic shell application or Performance Management shell application. In this tutorial, the Planning application was created in Performance Management Architect, which requires you to export its application metadata. To export Performance Management Architect application metadata: 1. In the left pane, expand Application Groups, then Foundation, and then EPM Architect.

2. 3.

In the content pane, expand Application Metadata, then Planning Applications, and then [Your Planning Application. Select Local Dimensions and Planning Settings and click Define Migration. In this example, local dimensions and planning settings for the Hyplan Planning application are selected.

4.

Review the source options and click Next.

5.

On the Destination page, enter the name of the file system folder where the Performance Management Architect application artifacts will be exported, and click Next. In this example, the file system folder is named epma_hyplan.

6.

Review the destination options to ensure that the parameters are correct, and click Next.

7.

Review the migration summary and click Execute Migration.

8.

Click Launch Migration Status Report.

9.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.

Exporting Calculation Manager Artifacts You can migrate the following Calculation Manager artifacts: rules, rule sets, formulas, scripts, and templates. To export Calculation Manager artifacts: 1. In the left pane, expand Application Groups, then Foundation, and then Calculation Manager.

2.

In the content pane, expand Planning, select [Your Planning Application], and click Define Migration. In this example, the Hyplan Planning application is selected. You can also select specific artifacts under your Planning application if you do not want to export all Calculation Manager artifacts.

3.

Review the source options, and click Next.

4.

On the Destination page, enter the name of the file system folder where the Calculation Manager artifacts will be exported, and click Next. In this example, the file system folder is named calc_hyplan.

5.

Review the destination options to ensure that the parameters are correct, and click Next.

6.

Review the migration summary and click Execute Migration.

7.

Click Launch Migration Status Report.

8.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration is successfully completed . In the left pane, the exported artifacts are displayed under File System.

Exporting Planning Application Artifacts You use Lifecycle Management to migrate the following types of Planning artifacts:

Configurationuser preferences, user variables, and application settings Relational dataplanning units, cell text, text values, account annotations, and supporting details Global artifactssubstitution variables, business rules, task lists, spread patterns, and so on Plan types Securityaccess permissions To export Planning application artifacts: 1. In the left pane, expand Application Groups, then Default Application Group, and then [Your Planning Application]. Note: If you associated your Planning application with a different application group, you must navigate to that application group and select your Planning application.

2.

In the content pane, expand select the artifacts you want to export and click Define Migration. In this example, Configuration, Global Artifacts, Plan Type, and Relational Data are selected. You can also select a subset of artifacts. It is highly recommended that you split the artifact migration. For instance, you can export a separate file system for Security (access permissions).

3.

Review the source options and click Next.

4.

On the Destination page, select File System, enter the name of the file system folder where the Planning artifacts will be exported, and click Next. In this example, the file system folder is named pln_hyplan.

5.

Review the destination options to ensure that the parameters are correct, and click Next.

6.

Review the migration summary and click Execute Migration.

7.

Click Launch Migration Status Report.

8.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.

Exporting Repository Objects You can export repository objects such as financial reports, books, and other attached files. To export repository objects: 1. In the left pane, expand Application Groups, then Reporting and Analysis, and then Reporting and Analysis.

2.

In the content pane, expand Repository Objects, select the artifacts that you want to export, and click Define Migration. In this example, the following objects are selected: financial reports in the root folder, the Hyplan folder and its contents, and the InsFiles folder and its contents.

3.

Review the source options and click Next.

4.

On the Destination page, select File System, enter the name of the file system folder where the repository objects will be exported, and click Next. In this example, the file system folder is named repobj.

5.

Review the destination options to ensure that the parameters are correct, and click Next.

6.

Review the migration summary and click Execute Migration.

7.

Click Launch Migration Status Report.

8.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.

Copying Source Artifacts 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. The default file system location for the exported artifacts is: [Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory In this topic, you compress the source artifact directory, copy it to the destination environment, and extract the file system folders. To copy source artifacts to the destination environment: 1. Navigate to the following directory: [Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory In this example, you navigate to C:\oracle\Middleware\user_projects\epmsystem1\import_export\admin@Native Directory.

2.

The exported file system folders are displayed. Navigate two levels up, and copy or compress the import_export directory.

In this example, the import_export directory is compressed with 7-zip.

3.

Typically, in new environments, the import_export directories do not exist until you run a migration. In the destination environment, navigate to [Middleware Home]\user_projects\epmsystem1.

4.

Notice that the import_export directory does not exist. Copy and extract the compressed file.

5.

Open the import_export and [admin_user]@Native Directory folders.

6.

Verify that the exported file system folders were extracted in the Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory directory of the destination environment.

[Middleware

Importing Planning Applications from the File System into the Destination Environment You exported the Planning application artifacts from the source environment to the file system and you copied the artifacts to the destination environment file system. In this topic, you run the Lifecycle Management migration in the destination environment. Importing Guidelines:

Shared Services artifacts must be imported before you import any other artifact. Performance Management Architect application metadata artifacts must be imported before you import Planning artifacts. To import Planning applications from the file system into the destination environment: 1. Log on to Workspace and open Shared Services Console. 2. In the left pane, expand File System.

3.

In the left pane, select the file system folder that contains the Shared Services users, groups, and roles. In this example, hss_ugr is selected.

4.

On the Artifact List tab, click Select All, verify that the artifacts were selected, and click Define Migration.

5.

Review the source options and click Next.

6.

On the Destination page, verify that Foundation:Shared Services is selected, and click Next.

7.

On the Destination Options page, accept the defaults, and click Next.

8.

Review the migration summary, and click Execute Migration.

9.

Click Launch Migration Status Report.

10.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration is successfully completed. 11. In the left pane, under File System, select the file system folder that contains the Performance Management Architect Shared Library dimensions and members. In this example, epma_shared is selected.

It is recommended that you import Shared Library dimensions and members before importing Planning applications. Some Planning applications require Shared Members, which will cause your migration to fail if they have not been imported to the Shared Library. 12. On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.

13.

Review the source options and click Next.

14.

On the Destination page, verify that Foundation:Performance Management Architect is selected and click Next.

15.

On the Destination Options page, accept the defaults and click Next.

16.

Review the migration summary and click Execute Migration.

17.

Click Launch Migration Status Report.

18.

On the Migration Status Report page, review the status of the migration. The report status displays Completed when the migration completed successfully. Click Refresh to display the updated job status.

19.

In the left pane, under File System, select the file system folder that contains the Performance Management Architect application metadata. In this example, epma_hyplan is selected.

20.

On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.

21.

Review the source options, and click Next.

22.

On the Destination page, verify that Foundation:Performance Management Architect is selected, and click Next.

23.

On the Destination Options page, select Deploy after Import and Create Outline, enter the remaining required parameters, and click Next. In this example, the following information is entered: Deploy after Import: Selected Instance Name: Default Shared Services Project: Default Application Group Data Source: ST01PLN1 Create Outline: Selected Note: You must have an existing Planning data source ready before you run the import.

24.

Review the migration summary, and click Execute Migration.

25.

Click Launch Migration Status Report.

26.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully. 27. In the left pane, under File System, select the file system folder that contains the Calculation Manager artifacts for your Planning application. In this example, calc_hyplan is selected.

28.

On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.

29.

Review the source options, and click Next.

30.

On the Destination page, verify that Foundation:Calculation Manager is selected, and click Next.

31.

Review the destination options, and click Next.

32.

Review the migration summary, and click Execute Migration.

33.

Click Launch Migration Status Report.

34.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully. 35. In the left pane, under File System, select the file system folder that contains the Shared Services assigned roles. In this example, hss_roles is selected.

36.

On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.

37.

Review the source options, and click Next.

38.

On the Destination page, verify that Foundation:Shared Services is selected, and click Next.

39.

Review the destination options, and click Next.

40.

Review the migration summary, and click Execute Migration.

41.

Click Launch Migration Status Report.

42.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully.

43.

In the left pane, under File System, select the file system folder that contains the Planning application artifacts. In this example, pln_hyplan is selected.

44.

On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.

45.

Review the source options, and click Next.

46.

On the Destination page, verify that Default Application Group: Hyplan is selected, and click Next.

47.

Review the destination options, and click Next.

48.

Review the migration summary, and click Execute Migration.

49.

Click Launch Migration Status Report.

50.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully. 51. In the left pane, under File System, select the file system folder that contains the repository objects. In this example, repobj is selected.

52.

On the Artifact List tab, click Select All, verify that the artifacts were selected, and click Define Migration.

53.

Review the source options, and click Next.

54.

On the Destination page, verify that Reporting and Analysis:Reporting and Analysis is selected, and click Next.

55.

On the Destination Options page, accept the defaults, and click Next.

56.

Review the migration summary, and click Execute Migration.

57.

Click Launch Migration Status Report.

58.

On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.

The report status displays Completed when the migration completed successfully. The migration for all artifacts is completed. 59. Next, verify that your artifacts imported completely. In the left pane, expand User Directories, then Native Directory, and then Users.

On the Browse tab, click Search, and review the user list.

60. 61.

Repeat the same steps for Groups and Roles. It is also recommended that you review the assigned roles. Next, open Calculation Manager, and verify that the rules and rule sets for your Planning application are available. In Workspace, select Navigate, then Administer, and then Calculation Manager.

Expand Planning, then [Planning Application], then [Plan Type], and then Rules.

62.

Ensure that the rules associated with your Planning application are listed. Repeat the same steps to verify all nodes under all plan types in the Planning application. Next, open your Planning application. In Workspace, select Navigate, then Applications, then Planning, and then [Planning Application].

Verify that data forms, menus, smart lists, and other Planning objects have migrated successfully.

Summary In this tutorial, you have learned how to:

Export Planning applications Copy source artifacts to the destination environment Import Planning applications from the file system into the destination environment Resources Oracle Hyperion Planning, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin.pdf) Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/epma_admin.pdf)

Oracle Hyperion Enterprise Performance Management (http://docs.oracle.com/cd/E17236_01/epm.1112/epm_lifecycle_management.pdf)

System

Lifecycle

Management

Guide

Creating and Initializing Oracle Hyperion Workforce Planning, Fusion Edition 11.1.2 Applications Prerequisites Before starting this tutorial, you should: 1 . Have administrator access to a working installation of Planning 11.1.2 with Workforce Planning enabled. 2 . Have administrator access to a working installation of Hyperion Shared Services 11.1.2. 3 . Have administrator access to a working installation of Oracle Hyperion Performance Management Architect 11.1.2. 4 . Have created Planning datasources. This tutorial requires: 1. One datasource for the Workforce Planning application created in Performance Management Architect. 2. One data source for the Workforce Planning application created in Classic Administration. 5 . Have a working Planning application that was created in Performance Management Architect. Before you initialize Workforce Planning:

Download the Oracle Hyperion Workforce Planning, Fusion Edition 11.1.2 Administrator's Guide and read Appendix A, Workforce Planning Structure. Review the predefined elements, identifying which elements you can use and which elements you need to customize. Update dimension outlines to resolve differences between Workforce Planning member names and member names of other applications. Plan the structure of the Entity dimension if you intend to use both Workforce Planning and Oracle Hyperion Capital Asset Planning, Fusion Edition. You can change the Entity members after you initialize the applications. Creating Workforce Planning Applications in Performance Management Architect To create and initialize Workforce Planning applications in Performance Management Architect: Creating a Workforce Planning Application Using Application Creation Wizard In this example, you create a Workforce Planning application with no additional plan types. To create Workforce Planning applications in Performance Management Architect using Application Creation Wizard: 1. Log on to Workspace. 2. Select Navigate, then Administer, and then Application Library.

Application Library is displayed. Sample applications were created in the tutorial environment. These Planning applications are not included with the software.

3.

In Application Library, select File, then New, and then Application (Z).

Application Creation Wizard is displayed.

4.

In the Application Information area, perform the following actions:

Enter an application name. In this example, Wkfc1 is entered. Select Planning as the type. Enter a description. In this example, Workforce Planning application is entered. Select Auto Create Local Dimensions.

5.

In the Planning area, perform the following actions:

Select General as the application type. Clear all plan type selections. Select Workforce Name and enter a plan type name. Accept USD as the default currency. Select Use Multiple Currencies.

6.

In the Calendar area, select a base time period, fiscal start month, and weekly distribution.

7.

For Period and Year, perform the following actions:

Select Create New Local Period Dimension. Enter Period as the period name. Select Create New Local Year Dimension. Enter Year as the year name. Select the first fiscal year. Select the number of fiscal years for the application.

8. 9.

Click Next. Review the Dimension Selection page, make the necessary modifications, and click Next.

The following message is displayed: Creating application Wkfc1.

10.

The following message is displayed: Dimensions for Workforce have been seeded. Click OK.

The Application Settings page is displayed.

11.

In the Member Area, expand Wkfc1.

The dimensions created for the application are displayed.

12.

13.

Click Validate. The validation process checks for missing dimensions and other required information. If anything is missing in the application, the deployment is aborted. If another deployment for the application is in progress, the request is cancelled. Review the listed messages. If errors are found, make the necessary modifications to the dimension members.

14.

Tip: Period and Year dimension errors usually appear when Create New Local Period Dimension and Create New Local Year Dimension were not selected during application creation. Click Validate to ensure that no error messages are displayed.

15. 16.

Click Finish. The deployment process involves the following steps: Validate the applicationThe validation process is run upon application deployment. Select the environment information for deploymentSelect the server and instance to which you are deploying the application. Export and deploy the applicationWhen you deploy an application, the deployment job begins and the application is exported from Performance Management Architect to Planning. Create the product applicationIn new deployments, Planning creates the application and the product server attempts to load the metadata. After deployment is completed, the status and deployment timestamp is updated in Application Library, and the deployment job is marked Completed. After the job is marked "Completed" and free of errors, the deployed Planning application becomes accessible in Workspace. On the Deploy page, enter the required information and click Deploy.

Select a Planning instance. In this example, PLANNING is selected. Select a Planning application server. In this example, PLANNING is selected. Select a Shared Services project (application group). In this example, Default Application Group is selected. Select a Planning datasource. In this example, ST01PLN7 is selected. Select Create Outline. Optional: Select Create Security Filters. Optional: Select Shared Members Security Filters. The application name and description are entered when you first create the application in Performance Management Architect and are not editable. In the Job Task dialog box, click the Click here to navigate to jobs link.

17.

18.

After the deployment action is initiated, you can check Job Console for results. After you create a Workforce Planning application, it is validated and deployed to Planning immediately. The deployment process creates a Planning application automatically. On the Job Console toolbar, click Refresh to update the job results.

Job Console:

A job ID is associated with each task in Job Console. Job Console displays the following information:

o o o o o o o o

SummaryInformation about the job: Started Timestart time for small jobs. Submitted Timestart time for large jobs. Last Updated Timelast time the job was updated. User Nameuser name that submitted the job. Process Nameprocess name in which the job is running Threadthread ID of the current job. Serverserver name where the job is running. Detail job summary, including errors and warnings. Attachmentsfile attachments associated with the job. Statusstatus and progress of the job. Each job can have the following status: Invalid, Scheduled Start, Queued, Scheduled Stop (cancelled by the user), Starting, Running, Stopping, Stopped (aborted by the user), Aborted (aborted due to an error), Completed, Completed With Errors, and Not Responding.

Accessing the Workforce Planning Application After deploying the application, you refresh the application list and access it through Workspace. To access the Workforce Planning application after deployment: 1 . In Workspace, select Navigate, then Applications, and then Refresh.

2.

The application list is refreshed. Select Navigate, then Applications, then Planning, and then <Application Name>. In this example, the Wkfc1 application is selected.

The application is displayed. 3. From the Select Data Form area, expand Forms and select Workforce.

The predefined Workforce Planning data forms are displayed in the content area. Adding the Workforce Planning Plan Type to an Existing Planning Application If you have an existing Planning application, you can add the Workforce Planning plan type to it in Performance Management Architect. You do that by selecting the Initialize menu command. Initializing the Workforce Planning Plan Type To initialize the Workforce Planning plan type: 1. In Workspace, select Navigate, then Administer, and then Application Library.

2.

In Application Library, select the Planning application in which you want to add the Workforce Planning plan type. In this example, the Workforce Planning plan type is added to PlanBud.

3.

Right-click the application, select Initialize, and then Workforce.

4.

Note: Select Workforce and Capital Asset if the application will use both plan types. In the Confirm Initialization dialog box, click Yes.

The validation process runs before the deployment. The following message is displayed: Validating Application for Deploy.

5.

On the Deploy page, enter the required information and click Deploy.

The following message is displayed while dimensions are created in the application: Seeding dimensions for Workforce.

6.

For more information on the deployment process, click here. In the Job Task dialog box, click the Click here to navigate to jobs link.

7.

On the Job Console toolbar, click Refresh to update the job results.

Job Console:

The application deployment displays a progress of 100% when it is completed. For more information on the Job Console, click here. Accessing the Updated Application in Workspace After the deployment is completed, you access the updated application in Workspace. To access the updated application in Workspace: 1 . In Workspace, select Navigate, then Applications, then Planning, and then <Application Name>. In this example, the PlanBud. application is selected.

2.

The application is displayed. In the Select Data Form area, expand Forms, and select Workforce.

The predefined Workforce Planning data forms are displayed in the content area.

Creating Workforce Planning Applications in Classic Application Administration Creating Classic Workforce Planning applications To create Classic Workforce Planning applications: 1. Log on to Workspace. 2. Select Navigate, then Administer, then Classic Application Administration, and then Planning Administration.

3.

In Classic Application Wizard, click Create.

4.

On the Select tab, perform the following actions: Select a data source. In this example, ST01PLN10 is selected. Enter the name of the application. The name can contain up to eight characters. It must not be the same as an existing Essbase application. In this example, Wkfc2 is entered. Enter a description of the application. In this example, Classic Workforce Planning application is entered. Select a Shared Services project (application group). In this example, Default Application Group is selected. Select an instance (cluster) to use for the application. In this example, PLANNING is selected. For Calculation Module, select Business Rules or Calculation Manager. In this example, Calculation Manager is selected.

5. 6.

Select the Calendar tab. Select the base time period, fiscal start year, fiscal start month, weekly distribution, and total years.

7. 8.

Select the Currencies tab. Select the default application currency. If the application supports multiple currencies, select Yes.

In this example, USD is selected as the default application currency, and multiple currencies are supported. 9. Select the Plan Types tab. 10. Perform the following actions:

Clear all plan type selections. Select Workforce Planning under Planning Specialized Modules. Enter Wrkforce as the name for the Workforce Planning plan.

11. Select the Finish tab. 12. Review your selections and click Finish to create the application.

When the application creation is successfully completed, the following message is displayed:

Accessing and Initializing the Application To access and initialize the Workforce Planning application: 1 . Next to Go to the new application:, click the application name. In this example, Wkfc2 is clicked.

The application is displayed.

2.

Select Administration, then Initialization, and then Workforce.

3.

When prompted to proceed with the initialization, click OK.

4.

At the confirmation message that initialization is successful, click OK.

5.

The application is displayed. In the Select Data Form area, expand Forms and select Workforce.

The predefined Workforce Planning data forms are displayed in the content area. Summary In this tutorial, you have learned how to:

Create Workforce Planning applications in Performance Management Architect Add the Workforce Planning plan type to an Existing Planning Application Create Workforce Planning applications in Classic Application Administration Resources Oracle Hyperion Planning, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin.pdf) Oracle Hyperion Workforce Planning, Fusion Edition Administrator's Guide (http://docs.oracle.com/cd/E17236_01/epm.1112/wfp_admin.pdf) Oracle Enterprise Performance Management (http://docs.oracle.com/cd/E17236_01/epm.1112/bpmui_admin.pdf) Workspace, Fusion Edition Administrator's Guide