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.

Click Save. The Provision Summary pane displays the successful provisioning message. you learned how to: Create groups and associate existing users Assign Planning roles to groups . Select Interactive User and click Add. Summary In this tutorial.5. 6. The Interactive User role is now displayed in the Selected Roles area.

perform the following steps: 1. . 5. Select Administration > Reporting. Log on to Workspace. In this case. Click Close. Select Navigate > Applications > Planning > [Planning application]. 4. Have access to query Planning relational database tables. Have administrator access to Planning applications. 3. 3.Setting Up an Audit Trail in Planning Prerequisites Before starting this tutorial. you should: 1. 2. 2. you use Oracle SQL Developer. Have access to Workspace and Planning. Enabling Auditing To enable Planning audit reports. Select the Auditing tab.

click a folder name to display its content.OraDb11g > Application Development > SQL Developer. 7. In the view pane. perform the following steps: 1. enter data. From your desktop. expand the Forms node. and click Save. and click a data form. Under Forms. Expand nodes to locate Planning relational database tables. Viewing and Clearing Audit Reports in SQL Developer To use Oracle SQL Developer to view and clear audit reports. Click an unlocked cell. select Start > Programs > Oracle . .6. 2.

. Click Delete Selected Row(s). click the first cell in row 1 and press Ctrl + A to select all rows. In this example. 4. data changes applied to all affected cells are posted to the table.3. 5. From the Data tab. Select the HSP_AUDIT_RECORDS table and click the Data tab to display audit history.

you learned how to: Enable auditing View and clear audit reports in SQL Developer . Summary In this tutorial. 7.6. Click Commit Changes. All records are deleted.

you should: 1. 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. In the product selection panel. Select Create a new datasource link and click Next. 2. Have administrative access to Performance Management Architect. 2. 3. expand the Hyperion Foundation and Performance Management Architect nodes. perform the following steps: 1. . Select Interface Datasource Configuration and click Next. To configure interface data sources. 3.Using Interface Tables to Import Metadata into Planning Prerequisites Before starting this tutorial. Interface tables provide you with a database interface to import metadata and data from external systems to Dimension Library. Launch the EPM System Configurator to display the Welcome pane and click Next. Have access to the Configuration Utility.

and click Next. Review the configuration summary. 6. and click Next. SQL or DB2). . and click Next.4. Select a database type (Oracle. 5. Enter the details for the interface data source.

select Navigate > Administer > Data Synchronization. Click Finish. Creating Interface Table Definitions To create interface table definitions. . perform the following steps: 1.7. From Workspace.

2. enter a dimension name. and click Next. On the Properties page. you must create and run a data synchronization or an import profile. whether to merge or replace existing dimensions. On the Dimensions page. . select File > New > Synchronization to display the New Synchronization pane. perform the following steps: 1. 4. and external files. and click Finish. You execute the profile to import dimensions into Dimension Library. On the Interface Area page. select the interface table data source you created. and dimension properties. select a column. Next. select the table and column that contain the values to import. and click Next. interface tables. Importing Dimensions from Interface Tables Before importing dimensions into the Dimension Library. enter a name and description for the interface area definition. 3. Select File > New > Data Interface Table Definition to display the Data Interface Area Mapping Wizard. Data synchronization enables you to synchronize and map data between Hyperion applications. Profiles include important information about the dimensions to be imported such as new dimensions. 5. and click Next. To import dimensions from interface tables.2. In the Performance Management Architect Data Synchronization module. Select Hyperion Data Interface Area as the source type.

and click Next. . Select an available destination application. Select plan types for source and destination and click Finish. and click Next. Drag a source dimension to a destination dimension to manually assign or change mappings. 5. Select a source data interface definition. 6. 4.3.

click Yes. When prompted to execute the profile.7. 9. Review mapping options and click Finish. Enter profile details and click OK. Select File > Import > Create Profile to create an import profile in Dimension Library. Select mapping options and click Next. 11. 8. 10. .

Summary In this tutorial. Click Close.12. you learned how to: Configure interface data sources Create interface table definitions Import dimensions for interface tables .

you should: 1.1. You must create a data source when you create an application.0 2. When you create or update applications using the Classic Application Wizard. Create a Shared Services application group called Planning Training Applications.Creating Planning Classic Applications Prerequisites Before starting this tutorial. 4. In Workspace. you select a data source for the application. Have access to or have installed a Planning application. Click Create Data Source.0. . click Manage Data Source. 3. 5. In Classic Administration Wizard. To create a data source. enter a data source name. In Data Source Name. 2. perform the following steps: 1. Creating Data Sources Data sources link the relational database to the Essbase server. Fusion Edition 11. Log on to Workspace.1. select Navigate > Administer > Classic Application Administration > Planning Administration. 3. Have access to or have installed Oracle® Hyperion Planning. Each data source must be associated with an instance.

8. In the Essbase Server area. enter Planning application details and click Validate Database Connection. In the Application Database area.6. 7. From the Select Database Platform drop-down list. select a database type such as SQL or Oracle. enter Essbase server details and click Validate Essbase Connection. .

in the bottom left pane.9. When using the Classic Application Wizard to create a classic sample application. Creating Sample Applications For classic Planning applications. 2. . Validate both connections and click Finish. select the Sample Application check box. specify details for the new sample application. Classic Application Administration. and click Next to display the Finish tab. perform the following steps: 1. To create the Planning Classic application. use the Classic Application Wizard to create and delete applications. 3. click Create Application. On the Select tab. select the Sample Application check box. Click Finish. From Workspace.

3. You have created a Planning application with a predefined structure. 2. From Workspace. click OK. Initializing Sample Applications After creating the classic sample application. In the successful initialization dialog box. . Select Edit > Sample Planning Application > Initialize Sample Application. To initialize the Planning Classic application. select Navigate > Administer > Planning > [Planning application].4. Select Administration > Manage Database. In the Application Creation Confirmation pane. perform the following steps: 1. 4. you must initialize it. click the link to refresh the Planning applications menu.

8. The Cube Refresh status is displayed. Note that there is no data loaded into the application. click Create. 7. When the status displays Create Complete. and opening a data form.5. click Finish. . In the Manage Database dialog box. clicking a folder. 6. Select Database and click Create. The data form is displayed. Verify that the application was initalized by expanding Forms.

locate the sample data file. 4. such as c:\TEMP and rename it to be eight characters or less. 2. Extract the sample data zip file to a location on your drive. and select Load data to display the Data Load pane. SampleAp.Loading Sample Data You load sample application data directly through Administration Services Console. Right-click your outline. perform the following steps: 1. Log on to Administration Services Console. and select [Planning outline]. 3.txt file contains the sample data that you are loading to the sample application. In this example. You must rename the sample application text file with up to eight characters. expand Enterprise View > Essbase Servers > [localhost] > Applications > [Planning application]. In the \Hyperion\products\Planning\bin\ directory. To load sample data. .

5. Select the Abort on Error option and click OK. Click Find Data File to display the Open dialog box. 7. locate and select the sample data file. 9. On the File System tab. click Close. 6. open a data form to verify that the data was loaded. 8. and click OK. In the Planning sample application. After the status “Success” is displayed. Summary In this tutorial. you learned how to: Create data sources Create sample applications Initialize sample applications Load sample data .

To prepare the environment for application migration. This information is provided from the Shared Services application. . Select Navigate > Administer > Application Upgrade to display the Application Upgrade Wizard. you should: 1. and be able to restore to a previous state. Have administrative access to Performance Management Architect. click Next. and before migrating classic applications to Performance Management Architect. Have administrator access to a Planning Classic application (budplan is used for this tutorial). 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. Log on to Workspace. The Application Summary page displays the applications available for upgrade.Migrating Planning Classic Applications to Performance Management Architect Prerequisites Before starting this tutorial. 2. 3. Preparing the Environment You should back up your applications and application databases on a daily basis. 3. On the Application Upgrade Wizard Welcome page. perform the following steps: 1. Have administrative access to Essbase. 2.

7.4. . Select the application you want to migrate and click Next. 6. On the Application Selection page. 5. In Job Console. click Add to move it to the Application to Upgrade list. click Refresh to view the status of the upgrade. Review the Upgrade Summary and click Finish to execute the upgrade. and click Next. select the application you want to migrate .

8. 9. When job status displays as Completed 100%. and confirm that the Planning application is in Performance Management Architect. . Double-click your application to display Dimension Library. select Navigate > Administer > Application Library.

you learned how to: Prepare the environment for application migration Migrate applications .10. Review the application dimensions in Dimension Library. Summary In this tutorial.

. only one Planning application is displayed. 4. Have administrative access to Planning. you should: 1. View the script that you want to use to create test Planning applications. 3. Log on to Workspace. 2. view existing Performance Management Architect applications. In this case.Automating Planning Administrative Processes Using Batch Client Prerequisites Before starting this tutorial. Select Administer > Application Library to display Application Library. 3. 2. Preparing to Use Batch Client To prepare to create applications. In Application Library. perform the following steps: 1. You must verify that the script is complete and uses the correct syntax. Install Performance Management Architect. Have administrative access to Performance Management Architect.

The file is located in the default directory. Fusion Edition 11. the PLAN3 Planning application is now displayed.1. refer to the Oracle Hyperion Enterprise Performance Management Architect. In this case. For more information on how to create Batch Client scripts. and change the directory to C:\Hyperion\products\Foundation\BPMA\EPMABatchClient. perform the following steps: 1. 2 Enter the create application creation command and execute the application creation script. Verify that the application appears in Application Library.Creating Applications To create applications. the script was validated and the application was successfully created. . In this case. 4. Open a command prompt. Batch Client User's Guide. C:\Hyperion\products\Foundation\BPMA\EPMABatchClient\output. This is the default directory for Batch Client. 3. Check the EPMABatchClientResults log file to verify that the application was successfully created.1.

select Navigate > Administer > Library Job Console. and execute the deploy application script.1. . you will deploy the PLAN3 Planning application. the script was validated and the application was successfully deployed.Deploying Applications To deploy applications. Fusion Edition 11. In this case. In this case. refer to the Oracle Hyperion Enterprise Performance Management Architect. Check the EPMABatchClientResults log file to verify that the application was successfully deployed. Batch Client User's Guide. C:\Hyperion\products\Foundation\BPMA\EPMABatchClient\output. 4. The file is located in the default directory.1. 3. You must verify that the script is complete and uses the correct syntax. 2 Open a command prompt. In Workspace. perform the following steps: 1 View the script that you want to use to deploy applications. enter the deploy application command. For more information on how to create Batch Client scripts.

.5. verify that the application is now deployed. In Application Library. In Library Job Console. verify that the application was successfully deployed. 6.

Summary In this tutorial. Select Applications > Planning > [Planning Application] to verify that the Planning application is now available for testing.7. you learned how to: Prepare to use Batch Client Create applications Deploy applications .

Columns represent member properties. and Data Integration Management. You are logged on to Data Integration Manager. complete the following steps: 1. Have a load file containing Planning metadata to use in Data Integration Management. you have one member. Logging On to Data Integration Management To log on to Data Integration Management. Open the metadata load file and review its contents. 2. click OK. Have access to Workspace. Reviewing Load Files To review load files. In this example. In this example. add account 5900 (Discount Expense). Now there are two accounts to add to Planning. that you will load into Planning. Planning. perform the following steps: 1. .1. 2. Select Start > Programs > Informatica PowerCenter 8. you should: 1. In this case. The Informatica PowerCenter Workflow Manager is displayed. we are using a csv file. Add additional rows to the load file to load other accounts. you need to connect to the PowerCenter Repository. Next. 2. 5800.1 > Client > PowerCenter Workflow Manager. In the Welcome to PowerCenter Workflow Manager window. 3. Have administrator rights to Planning.Loading Metadata into Planning Using Data Integration Management Prerequisites Before starting this tutorial.

Connecting to Repositories To connect to a repository. The Application Connection Browser is displayed. . select the Planning application connection. enter security credentials and click Connect. In the Connect to Repository dialog box. In the Repository Navigator pane. 4. Select Connections > Application to set the Planning application connection. complete the following steps: 1. From the Select Type drop-down list. 3. 2. right click a repository and select Connect.

5. Enter the application name. Click Close . To create flat file source definitions. and password. Creating Flat File Sources You create a flat file source in Designer. Click New . You set up both source and target definitions. . From Workflow Manager. 7. perform the following steps: 1. 6. select Tools > Designer . user name. and click OK .

6. the flat file is LoadAccounts_DIM. Select the delimiters and text qualifiers for the text file. Select the flat file you are using to import metadata and click OK . . 3.csv.2. 5. Right-click the Planning folder. The Flat File Import Wizard is displayed. If your load file contains names in the first row. and click Next . In this example. select Import field names from first line. Select Tools > Source Analyzer . and click Next . Select Sources > Import from File . and select Open . 7. 4.

The flat file is displayed in Source Analyzer. Select column data types for the text file. Expand the flat file source to view all ports that can be mapped from this flat file to the Planning application target. If the table exists. the target is the Account dimension in Planning. click Replace to replace the source details.8. and click Finish . 9. Right-click the flat file source and select Edit . 10. The Edit Tables dialog box is displayed. . 11. In this example.

13. you test the connection. select Tools > Target Designer . Select Targets > Import from Hyperion Planning . . After setting up a connection to a Planning data source. From Designer. 2. Creating Planning Targets You use Target Designer to set up a Planning target for the metadata load. Click OK to close the dialog box. You select a target and create a data source. To create Planning application target definitions. and set all data type values to string .12. perform the following steps: 1. Press Ctrl+S to save your changes and verify that the file was saved. Select the Columns tab. 14.

. Enter the DSN and server details and click Get applications to refresh the list of servers that you can connect to. 4.3. Click the ellipsis button to create a data source name before you define your targets. 5. Select the application and login details to connect to Planning. The DSN represents a set of information that is used to connect to an application such as Planning.

Click Test connectivity .6. 8. Click Connect to view Planning application targets. . Click OK to close the Define DSN dialog box. 7.

select Tools > Mapping Designer .9. Next. 1. 4. it is the LoadAccounts_DIM flat file. 2. Select Account . 5. In the Mapping Name dialog box. In this example. enter a mapping name and click OK . Drag the source to the Mapping Dimension Editor. Select Mappings > Create . . The Mapping Designer window is displayed. From Target Designer. Creating Mappings You use Mapping Designer to create a mapping between source file and the Planning target. Select the source for the data load. and click OK to import account metadata into Planning. you create a mapping from the source flat file to the target Planning application. 3.

Expand the source qualifier to view all mapping ports . Expand the target definition to view all of its ports. . Select a target for the mapping. 9. The source definition and source qualifier are displayed in the mapping dimension editor. Drag the Planning account target to the Mapping Dimension Editor and place the target to the right of the source. 7. and adjust the Mapping Designer windows to see all targets and source definition details. 8.6.

10. and select Autolink . Select the target (From Transformation) and source (To Transformations) to link. Right-click anywhere in Mapping Designer. 12. click Apply Now . 11. and then click OK . . Press Ctrl+S to save your changes.

To create data load workflows. Select Workflows > Create . The Workflow Designer window is displayed. 2. If a workflow is open in Workflow Designer. right-click the Hyperion folder. View the Mapping output window to confirm that the mapping was saved .13. The last workflow that you were working on is displayed. and select Open to ensure that the Hyperion repository is connected 3. select Tools > Workflow Manager . In Workflow Manager. Next. Creating Data Load Workflows You use Workflow Manager to create a data load workflow. perform the following steps: 1. 4. 5. click Yes at the prompt to close the open workflow. From PowerCenter Designer. you execute the data load workflow to load the metadata to the Planning target. .

6. server. and any other details. Session tasks specify how workflows are executed. enter the task name. Select the mapping that you created. and click Create . and click OK . In the Create Task dialog box. 9. Enter the workflow name. . 7. Select Tasks > Create to create a session task. 10. 8. and click OK . 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. 2. perform the following steps: 1. Right-click the session task and select Edit to verify that source and target properties are correct. you link and validate the task flow. you verify the source and target properties for the task and the mapping and save 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. First. Select the Mapping tab to verify source and target properties. Finally. 3. you execute the workflow. . Next. Select the flat file source.

5. Verify that the correct reader.4. (File Reader) for the flat file is selected. . Verify that target properties are correct.

. 7. Press Ctrl+S to save the workflow.6. Click OK to close the Edit Tasks window.

In the Output window. 3. verify that the workflow is valid. 5. verify the session task properties again. . Select Tasks > Validate to validate the task flow.Linking and Validating Task Flows To link and validate task flows. 4. 2. Link to tasks. If your workflow is not valid. Press Ctrl+S to save the workflow. perform the following steps: 1. Select Tasks > Link Task to link the tasks in the workflow.

Verify that two rows were successfully created in the target Planning applications. perform the following steps: 1. 3. 2. 4. Verify that two source rows were successfully read from the flat file source. Right-click the session task and select Properties to verify that the workflow was executed properly. Select Workflows > Start Workflow.Executing Workflows To execute workflows. .

Verify that accounts 5800 and 5900 were added to the Account dimension. and minimize open windows. Log on to Workspace and access your Planning application. In the Dimensions list. 2. select Account and search for account 5800. 1. 4. In the Administration menu. Verifying Results in Planning In this topic. Click OK. .5. you log on to Planning and verify that the two accounts were added to the Account dimension. 3. select Dimensions to display Dimension Editor.

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 .

Financial Reporting. Select the application artifacts that you want to migrate. log on to Shared Services as the user who is provisioned with the appropriate LCM roles.1.1 with Hyperion Shared Services Lifecycle Management 11.1 EPM products in the source and destination environments (Hyperion Shared Services. and select the Planning application that you want to migrate. Essbase.1. Navigate to Foundation > Shared Services.1. HPSamp. Install and configure Planning 11. 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. Navigate to the Planning application group. 4.1 and all related 11. 2. For EPMA-enabled Planning applications. 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. 5. and so on).1 Prerequisites Before starting this tutorial: 1. 3. as follows: Assigned Roles – Roles granted to users and groups through the provisioning process. and select the EPMA artifacts .1. In the source environment. navigate to Foundation > EPM Architect > Application Metadata > Planning Applications.    Users – Native Directory users Groups – Native Directory groups 3. The source environment must contain the Planning application with all metadata loaded. and select the native directory provisioning artifacts and task flows that are applicable to the Planning application. 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. 2.First-Time Lifecycle Management Migration for Oracle Hyperion Planning 11. for example.

and click Next. and click Next. and roles as needed. it is HPSamp. Select the Repository Objects folder. Planning HPSamp Reports. review the set of artifacts that you selected for the Planning application migration. In the following example. 11 Select the first product to migrate (for example. Shared Services).that reside under the Planning application that you are migrating. . Navigate to Reporting and Analysis to select the financial reports. Select the financial reports. 8. for example. groups. filter the user. 7. 12 On the Source Options page. 10 Click the Define Migration button to define the Planning application migration. and navigate to the folders that contain the financial reports that are associated with the Planning application. On the Selected Artifacts tab. 9. 6.

18 Review the destination options to ensure that the parameters are correct. 17 On the Destination page. . 15 Select the next product to migrate (for example. EPM Architect). You are directed back to the beginning of the migration wizard so that you can define other product migrations. 16. and click Next. click Next. 14 Review the destination options to ensure that the parameters are correct. On the Source Options page. enter the name of the file system folder where the EPMA artifacts will be extracted. and click Next. and click Next. and click Next. enter the name of the file system folder where the Shared Services artifacts will be extracted. and click Next.13 On the Destination page.

19 Select the next application to migrate (for example. enter the name of the file system folder where the Planning artifacts will be extracted. 24 On the Source Options page. and click Next. Planning). . 21 On the Destination page. select Export with Job Output if you want that information to be migrated. 23 Select the next application to migrate (for example. 22 Review the Destination Options page. and click Next. and click Next. and click Next. Reporting and Analysis). and click Next. 20 On the Source Options page. and click Next.

27 Review the Migration Summary to ensure that the defined migrations are correct. enter the name of the file system folder where the Financial Reporting artifacts will be extracted. and click Next. and click OK. 28 Click Save Migration Definition. 30 Click Save. 29 Select Save as XML. and click Next. 26 Review the destination options to ensure that the parameters are correct.25 On the Destination page. .

31 Enter the location and name for the migration definition file. 33 Click Close. 32 In the Download Complete dialog box. . click Close. 34 Click Execute Migration. and click Save.

the migration is completed successfully.The Planning application migration is executed. and the Planning application artifacts are extracted to the file system. review the status of the migration. 37 Refresh the Migration Status Report to see that the migration is completed. 35 Click Launch Migration Status Report. . When the report status changes to Success. 36 On the Migration Status Report page.

you copy and paste the artifacts within Windows Explorer. 5 Navigate to the location of the source environment application artifacts. 2 Select Tools > Map Network Drive. 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. sending them through FTP. . In this example. right-click. right-click. 6 Select the folders. navigate to Windows Explorer on the file system. 7 Navigate to the newly mapped destination location.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. 1 In the source environment. 3 Enter the parameters for the destination environment file system location. and select Copy. 4 Click Finish. and select Paste. or burning them to a DVD. You can accomplish this task by copying and pasting the artifacts.

Note: The following dimension-level properties must match in both the source and the destination applications: Start year Base time period (for example. if the source application has a plan type called Plan1. 3 Select Manage Data Source.   If the Planning application is already created in the destination environment or if the Planning application is EPMA-enabled. skip this section. Quarters. 2 Navigate to Administer > Classic Application Administration > Planning Administration. Creating the Planning Application in the Destination Environment for Planning Classic Applications Before migrating a Planning classic application. then the destination application should be of the same type Source and destination plan types must match (for example. . and Custom) Start month If the source has a “Single Currency” application type. you must first create the Planning application in destination environment. ensure that you have created a new relational database for this new application.The application artifact folders now reside on the destination server file system location. 1 Log on to Workspace. a Plan1 plan type must exist in the destination application). Prior to beginning this section. 12 months.

. and select Finish. 6 Click Create Application. 5 Enter the parameters.4 Click Create Data Source.

Shared Services project. 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.   Shared Services artifacts must be imported before you import Planning artifacts. 8 Click Finish. copied the artifacts to the destination environment file system. You now import the artifacts into the destination Planning application. .cmd 1. description.7 Enter the application name. Note: Because Lifecycle Management does not support Planning access permissions migrations.cmd HYPERION_HOME\products\Planning\bin\ImportSecurity. and created a Planning application in the destination environment. In the destination. use the following Planning command-line utilities (ImportSecurity and ExportSecurity) to export and import Planning security: HYPERION_HOME\products\Planning\bin\ExportSecurity. and click Next. select Sample Application. and instance. log on to Shared Services as the user who is provisioned with the appropriate LCM roles.

Click Launch Migration Status Report to view the status of the migration. Navigate to the File System node. select the Shared Services artifacts.2. Notice that the migration is executed. 4. 3. Click Execute Migration. . Review the source options. select the import operation type and the number of maximum errors before stopping the import. and click Next. 7. 6. choose the Shared Services destination. 5. The migration is executed. and click Next. and click Next. On the Destination Options page. and click Define Migration. In the destination.

select Deploy after Import. If the Planning application is EPMA-enabled. 9. and click Next. 10 Select the EPMA file system artifacts that are applicable to the Planning application. EPM Architect). Perform one of the following actions:  For Planning applications that are EPMA-enabled. 12 View the Source Options page. 13 Select the destination (in this case. Note: The EPMA artifacts must be imported and deployed before you migrate non-dimensional artifacts for Planning application.  For Planning classic applications. Note: EPMA artifacts must be imported and deployed before non-dimensional Planning artifacts are imported. . 14 Select the Dimension Import Mode ( Merge or Replace). enter the remaining parameters to deploy the application view to a physical Planning application.8. proceed to step 9. navigate to Application Groups > File System. skip to step 24. 11 Click Define Migration. and click Next. and click Next.

17 In the File Download dialog box. 18 Enter the location and migration definition file name. and click Save. . and click Save Migration Definition. click Save. 16 Click OK.15 Review the Migration Summary.

. click Close. 20 Click Close again.19 In the Download Complete dialog box. 22 Click Launch Migration Status Report to view the status of the migration. 23 Click Cancel to close the Migration Status Report. and select the Planning application artifacts and the Planning financial reports. 24 Navigate to Application Groups > File System. 21 Click Execute Migration. The migration is executed. Notice that the migration is completed.

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

Review the Dimension Selection page. 7. Optional: Select a default currency and Use Multiple Currencies. In the Planning area. clear all plan types. . and click Next. and click Validate. and select Capital Asset. 6. 5. In the Calendar area. In the Application Information area. Optional: Select Auto Create Local Dimensions. 8. enter an application name. and click Next. click the plus signs (+) to display the dimensions. and select Planning as the type. make the necessary modifications to the list of dimensions. In the Member area. 4.3. make your selections. Click OK.

Click Finish.9. . Review the messages. 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. If errors are found. 10. make the necessary modifications to the dimension members .

and click Test Connection. click Next. Enter the Essbase server details. Click Finish. 16. Enter the database connection details. test the connection. 14. and click Next. On the New Data Source page. . When the connection displays as successful. 15.13. enter a data source name and click Next.

17. Select Create Outline. Click the Click here to navigate to jobs link. 18. . 19. Review the job console. and click Deploy. and click Refresh until the status displays a Completed message.

Using Classic Administration When you create a classic Capital Asset Planning application. In Workspace. Select Navigate > Applications > Planning > [Application Name]. In the left pane. expand Forms > Capital to display the predefined data forms. select Navigate > Applications > Planning > Refresh and repeat step 1. you must complete the following tasks: Create a Capital Asset Planning application Initialize Capital Asset Planning To create a Capital Asset Planning application: 1. If the application name does not display. In the left pane. 2. click Manage Data Source. 2. select Navigate > Administer > Classic Application Administration > Planning Administration. .To verify the Capital Asset Planning application initialization: 1.

enter the relational database connection information.    Data Source Shared Services Project Instance . In the Essbase Server area. In the content pane. Click Finish. and perform the following actions:      Select a database platform and. enter the Essbase connection details. and click Next. Enter an application name. In the left pane. make the following selections. Enter a data source name. click Create Data Source. 4. Click Validate Essbase Connection. 5. click Create Application. in the Application Database area. 6.3. Click Validate Database Connection.

. and click Next. enter a name for the plan.7. Accept the default application currency and multiple currency settings. 10. 8. and click Next. and click Next. 9. Select Capital Expense as the type. and click Finish. Make your selections for the calendar period settings. Verify the application settings.

Click the here first to refresh workspace Navigate > Applications menu link. . In Planning. When prompted if you want to proceed with the initialization.11. 2. 3. select Edit > Initialize Capital Asset Planning. To initialize Capital Asset Planning: 1. Select Navigate > Applications > Planning > CAP02. click OK.

and click Create. Click Finish. 7. 9. When a dialog box displays a message that Capex has been successfully initialized. you learned how to create and initialize Capital Asset Planning applications. . 8. Summary In this tutorial. Click Create. In the left pane. expand form. Select Database.4. 5. 6. and select Capital to display the predefined data forms. Select Administration > Manage Database. click OK.

Loading Employees and Employee Data in Oracle Hyperion Workforce Planning 11. Click Browse. 2. In the Dimension Library. You can download Oracle Enterprise Performance Management System documentation from the Oracle E-Delivery website. Locate your employee ADS file and click Open. Performance Management Architect functionality. Fusion Edition functionality. . select File > Import > Create Profile. 2. The Workforce Planning business model. you should understand: 1. 3.1 Prerequisites Before starting this tutorial. 4. Enter the following information and click Browse:    Profile name FlatFile as the import Type Application that contains the Workforce Planning plan type 3. The following are also required: 1. 3.1. Oracle® Hyperion Planning. 2. Workforce Planning must be installed and configured. Workforce Planning application ADS file containing employee data. Importing Employee Data 1. Contact your consultant for more information about creating a customized ADS file.

Click Upload. 7. 8. Select the column delimiter used in your ADS file. Select the following options and click Next:   Create dimensions for the non-mapped dimensions with the source dimension name Select All . 6.Merge As Shared . and click Next.5. Click OK.

9. . Click Yes. Click Refresh until the job status displays as Completed. Click Finish. 10. 11. Click Click here to navigate to jobs. 12.

In Workspace. . Right-click [Workforce Application] and select Validate > Application. Click Click here to navigate to jobs. 15.13. 14. select Navigate > Administer > Application Library.

16. right-click [Workforce Application] and select Deploy > Application. 18. . Return to the Application Library. Select Refresh Outline and click Deploy. In the Job Console. 17. refresh the page until the status displays as Completed.

Click Workforce. 3.19. In Workspace. expand Forms. 4. Select New Hires. From the left pane. select Navigate > Applications > Planning > [Workforce Planning Application]. Click Click here to navigate to jobs. 20. . refresh the page until the status displays as Completed. Adding Headcount (To-Be-Hired) 1. 2. In the Job Console.

Select Operations and click Go. click Add. Repeat steps 5 through 9 to add more headcount. 7. 8. In the content area. 6. 9.5. right-click and select Add To-be-hired > Salary. . 10. Save your data form. When all entries are validated with no errors. Enter the to-be-hired information and click Validate.

Reconciling Existing Employees 1 Right-click TBH1 and click Reconcile To-be-hired. Summary In this tutorial. In the left pane. Click Reconcile. . you learned how to use Performance Management Architect to load employees and employee data into Workforce Planning applications. click Manage Existing Employees. The imported and reconciled employees are displayed in the Manage Existing Employees form. enter the employee to be reconciled and click Validate. 2. 3. Make the necessary changes and click Save. In the From Employee text box. 4. 5.

1. 2. Logon to Workspace and select Navigate > Administer > Application Library. you should understand: 1.1. Oracle Hyperion Planning 11.1 product option must be enabled in the System Configurator. The following are also required: 1. The Workforce Planning business model. Using Performance Management Architect When you create and initialize Workforce Planning in Performance Management Architect.1 must be installed and configured. please consult the installation documentations (below) You can find more information on the required components for Oracle Hyperion Planning 11. 2. The Workforce Planning 11. select File > New > Application(s) .Installation Start Here Oracle Enterprise Performance Management System . Oracle Hyperion Planning functionality. . In the Application Library. Two empty relational databases. 2. 3. you must complete the following tasks: Create a Workforce Planning application Verify the Workforce Planning application initialization To create a Workforce Planning application: 1.1. This tutorial uses Oracle 11g as the relational storage.1 in the following documentation:   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. For a list of supported relational databases.Creating and Initializing Workforce Planning Applications Prerequisites Before starting this tutorial.

In the Application Information area.3. Optional: Select a default currency and Use Multiple Currencies. . click + to display the dimensions and click Validate. 7. Optional: Select Auto Create Local Dimensions. 8. make the necessary modifications to the list of dimensions. Click OK. and click Next. In the Member area. 6. In the Calendar area. Review the Dimension Selection page. deselect all plan types and select Workforce. 5. 4. make your selections and click Next. enter an application name and select Planning as the type. In the Planning area.

13 On the New Data Source page. . enter a data source name and click Next. Review the messages section. make the necessary modifications to the dimension members .9. If errors are found. 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.

18 Click Click here to navigate to jobs. test the connection. When the connection displays as successful. 17 Select Create Outline and click Deploy. click Next. and click Next. 16 Click Finish. .14 Enter the database connection details and click Test Connection. 15 Enter the Essbase server details.

Review the job console and click Refresh until the status displays as Completed.19. From the left pane. If the application name does not display. To verify the Workforce Planning application initialization: 1. 2. Select Navigate > Applications > Planning > [Application Name]. select Navigate > Applications > Planning > Refresh and repeat step 1. . expand Forms > Workforce to display the pre-defined data forms.

click Create Data Source. 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 Manage Data Source . Click Validate Essbase Connection. 3. From the content pane. In Workspace.Using Classic Administration When you create a classic Workforce Planning application. 2. 4. select Navigate > Administer > Classic Application Administration > Planning Administration. Enter the Essbase connection details in the Essbase Server area. Click Finish. Click Validate Database Connection. . From the left pane. you must complete the following tasks: Create a Workforce Planning application Initialize Workforce Planning To create a Workforce Planning application: 1.

8. 6.5. From the left pane. Click Next. click Create Application. Make your selections for the calendar period settings and click Next. . Enter an application name.    Data Source Shared Services Project Instance 7. make the following selections. and click Next. Select the default application currency and multiple currency settings.

10. Click here first to refresh workspace Navigate > Applications menu. Verify the application settings you chose and click Finish. Select Workforce Planning as the type and enter a name for the plan.9. 11. . Click Next.

click OK. When prompted if you want to proceed with the initialization. 2.To initialize Workforce Planning: 1. Click OK. Select Administration > Manage Database. In Planning. . expand forms and select Workforce to display the pre-defined data forms. 6. select Edit > Initialize Workforce. 3. When finished. 5. From the left pane. Select Navigate > Applications > Planning > WFP02. 4. a dialog box displays that Workforce has been successfully initialized.

Click Finish. you learned how to create and initialize Workforce Planning applications.7. 9. Summary In this tutorial. 8. Click Create. Select Database and click Create. .

you should: 1 .oracle. 3 . Have administrator access to a working installation of Enterprise Performance Management Architect 11. Have administrator access to a working installation of Hyperion® Shared Services 11.1. and click Save. Fusion Edition Batch Client 11. right-click PDF and select Save Link As. In the left menu. for Batch Client User's Guide. Fusion Edition Release 11. click Foundation Services.2 Documentation Library by using the following URL: http://download.1.2.Hyperion PLANNING RELEASE 11. Launch your browser.2 Prerequisites Before starting this tutorial. Preparing to Use Batch Client To prepare using Batch Client: Downloading Documentation To download documentation: 1 .2.1..com/docs/cd/E17236_01/index.htm 3. .2..1. Automating Planning Administrative Processes Using the Oracle® Hyperion Enterprise Performance Management Architect.1. Navigate to the Oracle Enterprise Performance Management System.2. 4.2. Have administrator access to a working installation of Planning 11. 2 . 2 . Under Oracle Hyperion Enterprise Performance Management Architect. Navigate to the location where you want to save the file. Fusion Edition. 5..1.

2. then Foundation Services. and press Enter after each line item: set bpmaserverurl=http://localhost/hyperion-bpma-server. and press Enter: login username. set workspaceurl=http://localhost:19000/workspace. ApplicationDescription. Note: Contact your administrator for your company's server URLs. ApplicationType) Values('PlanBud'.password. Enter your Performance Management Architect username and password with the following syntax.and then Start EPMA Batch Client. then Performance Management Architect. Creating Planning Applications Performance Management Architect Batch Client enables you to create a new. import. or copy dimensions and members in Shared Library and within Planning applications. . 'Planning Budget Application'. Empty applications are oftentimes referred to as shell applications. 'Planning'). you can create. empty Planning application with the specified name.Accessing Batch Client To access Batch Client: 1 . The Batch Client command window is displayed: Logging On to Performance Management Architect To log on to Performance Management Architect: 1 . Creating Shell Applications To create shells for Planning applications: 1 . Select Start. Programs. Create the shell application with the following syntax. After creating shell applications. and press Enter: Create Application Properties(ApplicationName. then Oracle Enterprise Performance Management System. Set the server URLs by using the following commands.

the Batch Client submits the job and continues. Entity. DimensionName. 'PlanBud' is used. 'Income Statement'. FileName—The name of the flat file to import.'Entity Dimension'. Create members with the following syntax and press Enter: Create Member Properties(ApplicationName. filename. Time. the 'PlanApp. MemberDescription—A description for the new member. In this example. ProfileName—The name of an existing import profile. Measure. Import dimensions and members by using an ADS file with the following syntax. MemberDescription) Values('PlanBud'. Adding Dimensions and Members You can create dimensions and members in Shared Library or within an application. Create dimensions with the following syntax and press Enter: Create Dimension Properties(ApplicationName. 'Income Statement' is used. ParentName.   Application Name—A string containing a valid name for the application. You can add dimensions as shared dimensions or you can copy them to the application as local dimensions.'Entity'). Year. WaitForCompletion—If set to true. ApplicationDescription—A string containing a valid description for the application. In this example. DimensionName—A valid name for the dimension. 'true'). This section covers the different methods of adding dimensions and members by using Batch Client: 1. In this example. DimensionName—The name of an existing dimension. you can add them to the application instead. Generic. ApplicationType—Enter 'Planning' for Planning applications. If these six dimensions are already created in Dimension Library.       3.ads'. Currency. 2. 'Entity' is used. 'Account' is used. Alias. ICP. In this example. profilename. You can insert a copy of a member as a shared member in an application. In this example. Note: Planning requires six dimensions. Country.     ImportType—The type of import to perform. if performing a flat file type import. In this example. In this example. SmartList. DimensionType—Dimension Type can be any one of the following: Account.'Account'. Scenario. AllocationType.'Entity'. You cannot insert members in a shared dimension in an application. If set to false. You can also import dimensions and members to an application or Shared Library using an ADS file. Attribute.     ApplicationName—The name of an existing application. and press Enter: Execute Import Parameters(importtype. 'Income Statement Accounts'). 'Entity Dimension' is used.ads' flat file in the AppFiles directory is used. ConsolidationMethod. MemberName—A valid name for the new member. '#root'. However. View. You can add dimensions and members to the Shared Library. 'PlanBud' is used. In this example. 'Income Statement Accounts' is used. MemberName. Batch Client waits for the job to finish.\AppFiles\PlanApp. UDA. In this example. Dimension Description—A string containing a valid description for the dimension. ApplicationName—The name of an existing application. 'PlanApp'. The following message is displayed: The application "PlanBud" has been created with objectid "1_4". SecurityClass. 'PlanApp' is used. DimensionDescription. you can use the Insert Member command only on local dimensions and Shared Library dimensions. Allowed values are: FlatFile and InterfaceTables. waitforcompletion)Values('flatfile'. Use #Shared to create a dimension in the Shared Library. Version. Use #Shared to create a dimension in the Shared Library. In this example. 'Planning Budget Application' is used. DimensionName. or you can copy them from the Shared Library to an application. Use #Root to add a new member at the top level of the tree. '. Value. DimensionType) Values(#Shared. . ParentName—The name of the parent under which to insert the newly created member.

MemberToInsertName) Values('Account'. IncludeAsShared—Use a value of true to include the dimension as a shared dimension. and press Enter: Copy Dimension Properties(ApplicationName. 'Par' is used. 'C_Alias' is used. ParentName. 'Scenario Dimension'. TargetDimensionDescription. ‘Mem2’). In this example. By setting the application name. InsertMemberName.Allowed values are: True or False. TargetDimensionDescription—The description of the target dimension. 'Scenario'. DimensionName. In this example. 'PlanBud'). 'Mem2' is used. By setting the application name. Include Dimension Properties(DimensionName. and press Enter after each line item: SET APPLICATION = 'PlanBud'. or between Shared Library and an application. In this example.      ApplicationName—The name of an existing application. TargetDimensionName—The name of the target dimension. TargetDimensionName.'Scenario'. ParentName—Name of the parent to insert the member under. destApplicationName—The name of the destination application. 'true'). Note: You must set the application name before the In command. In this example. destApplicationName) Values('#Shared'. 'PlanBud' is used. MemberToInsertName—Name of the shared member to be inserted. You cannot insert members in a shared dimension within an application. command lines use it if the application is not explicitly defined within a command. In this example. 'Scenario Dimension' is used. DimensionName—The name of an existing dimension. Use the following syntax to copy dimensions within Shared Library. In this example. Note: You cannot copy a dimension directly from one application to another. and press Enter after each line item: SET APPLICATION = 'PlanBud'. Use a value of false to include a local copy of the dimension within the application. within an application. In this example. Use the following syntax to add an existing dimension from the Shared Library to the specified application. Use #Shared to copy a dimension from the Shared Library. In this example. IncludeAsShared) Values('C_Alias'.   DimensionName—The name of an existing dimension in the Shared Library. 'Scenario' is used. The following figure displays a sample ADS file: 4. 'Account' is used. ‘Mem1’. Use the following syntax to insert a copy of a member as a shared member within an application. Insert Member Properties(DimensionName. InsertMemberName—Name of the member to insert the member under. 'Par1'. you can set the application name to #Shared if you are copying a member from Shared Library. 6.     DimensionName—The name of an existing dimension. 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. command lines use it if the application is not explicitly defined within a command. 'Scenario' is used. . You can use the Insert Member command only on local dimensions and Shared Library dimensions. 5. 'Mem1' is used. Alternatively. In this example.

'PlanBud' is selected. HubProject—The Shared Services project to add the deployed application to. In this example. Click the Planning application that you deployed in Batch Client. waitforcompletion. If set to false. you must be provisioned with the Application Creator or Planning Administrator role. 'Default Application Group' is used.        ApplicationName—The name of an existing application. In this example.Deploying Planning Applications After creating the shell and adding dimensions and members. In this example. dataSourceName. 2 . Deploy a Planning application with the following syntax. Log on to Workspace. WaitForCompletion—If set to true. Select Navigate. 'PLANNING' is used. see the Oracle Hyperion Enterprise Performance Management Architect.2 Batch Client's User Guide. ApplicationServer—The name of the application server to deploy to. 'true'). HubProject. For additional Planning parameters. In this example. InstanceName. and press Enter: Execute Deploy Parameters(ApplicationName. In this example. . Fusion Edition 11. 'PLANNING'. Allowed values are True or False. To deploy Planning applications. 'true'. CreateOutline) Values('PlanBud'. 'Default Application Group'. When the deployment is completed. InstanceName—The name of the instance to deploy to. ApplicationServer. CreateOutline—Creates the Essbase outline if you are deploying the application for the first time. then Administer. Batch Client waits for the job to finish. 1. you deploy the application to make it accessible in Workspace. 'PLANNING' is used. 3. 'ST01PLN3' is used. Batch Client submits the job and continues. In this example. 'PlanBud' is used.1. the following message is displayed: Accessing the Deployed Application in Application Library You must log on to Workspace with an administrator account. 'ST01PLN3'. 'PLANNING'. and then Application Library. Allowed values are: True or False datasourceName—Creates a data source with the specified name. To access the deployed application in Application Library: 1 .

pdf)  Oracle Hyperion Shared Services User and Role Security Guide (http://docs. Properties—Displays the status. Dimensions—Lists the dimensions available in the application. date last deployed. Synchronizations—Lists the data synchronizations for this application.pdf) . Description—Contains the information that you provided in the Description field when you created the application.com/cd/E17236_01/epm.1112/hss_admin. and specific properties set for the application.1112/bpmui_admin. the following information is displayed in the lower pane:       Summary—Contains the name. and the associated data synchronizations.oracle.When you select an application. 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. Fusion Edition Administrator's Guide (http://docs.oracle. Summary In this tutorial. default currency.pdf)  Oracle Enterprise Performance Management Workspace. date created.com/cd/E17236_01/epm. Rules / Rule Set—Enumerates the rules and rule sets defined in Calculation Manager for this application. type.oracle.com/cd/E17236_01/epm.1112/epma_batch_user.

1.1. 2.1. Initializing Workforce Planning produces one No Entity member. Update dimension outlines to resolve differences between Capital Asset Planning member names and member names of other applications. Select Navigate. and then Application Library. Application Library is displayed. . Have administrator access to a working installation of Hyperion® Shared Services 11. Fusion Edition 11.2.2 Administrator's Guide and read Appendix A.2. then Administer. Have administrator access to a working installation of Performance Management Architect 11. One data source for the Capital Asset Planning application created in Classic Application Administration. This tutorial requires: 1. whereas initializing Capital Asset Planning produces a few Entity members. Capital Asset Planning Structure. Have a working Planning application that was created in Performance Management Architect. You can change the Entity members after you initialize the applications. 3.1. Sample applications were created in the tutorial environment. 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.Creating and Initializing Oracle® Hyperion Capital Asset Planning. Note that these Planning applications are not included with the software. select File. you should: 1 . 4 .1. Log on to Workspace. Before you initialize Capital Asset Planning:    Download the Creating and Initializing Oracle® Hyperion Capital Asset Planning. Review the predefined elements. 5 . 2 . Have administrator access to a working installation of Planning 11. identifying which elements you can use and which elements you need to customize. Plan the structure of the Entity dimension if you intend to use both Capital Asset Planning and Oracle Hyperion Workforce Planning. Have created Planning datasources. In Application Library. Fusion Edition.2 Applications Prerequisites Before starting this tutorial. Fusion Edition 11. then New. 3 . you create a Capital Asset Planning application with no additional plan types.2 with Capital Asset Planning enabled. To create Capital Asset Planning applications in Performance Management Architect by using Application Creation Wizard: 1. 2. One datasource for the Capital Asset Planning application created in Performance Management Architect. and then Application (Z). The Application Creation Wizard is displayed.

In the Calendar area. fiscal start month. In the Application Information area. Accept USD as the default currency. Select Create New Local Year Dimension. Select Use Multiple Currencies. 7. 8. 5. Select Capital Asset Name and enter a plan type name. 6. Enter Period as the period name. In the Planning area.4. Select Auto Create Local Dimensions. and click Next. Select the number of fiscal years for the application. perform the following actions:      Select General as the application type. . For Period and Year. perform the following actions:     Enter an application name. select a base time period. Select Planning as the type. make the necessary modifications. Clear all plan type selections. Enter Year as the year name. Click Next. perform the following actions:       Select Create New Local Period Dimension. Select the first fiscal year. Review the Dimension Selection page. Enter a description. 9. and weekly distribution.

11. The Application Settings page is displayed. The dimensions created for the application are displayed. Click Validate. Click OK. In the Member Area. The validation process checks for missing dimensions and other required information.10. expand CapEx. . 12. If errors are found. If another deployment for the application is in progress. If anything is missing in the application. the deployment is aborted. The following message is displayed: Dimensions for Capital Asset have been seeded. the request is cancelled. Review the listed messages. make the necessary modifications to the dimension members. 13.

Selecting the environment information for deployment—Select the server and instance to which you are deploying the application. the deployed Planning application becomes accessible in Oracle® Enterprise Performance Management Workspace. In this example. Optional: Select Create Security Filters. Select a Planning datasource. 15. Click Finish. The application name and description are entered when you first create the application in Performance Management Architect and are not editable. 16. In this example.14. In the Job Task dialog box. In this example. Create the product application—In new deployments. . Fusion Edition (Workspace). 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. the deployment job begins and the application is exported from Performance Management Architect to Planning. click the Click here to navigate to jobs link. The deployment process involves the following steps: Validate the application—The validation process is run upon application deployment. Planning creates the application and the product server attempts to load the metadata. Select a Planning application server. On the Deploy page. Optional: Select Shared Members Security Filters. PLANNING is selected. Export and deploy the application—When you deploy an application. Default Application Group is selected. 17.            Select a Planning instance. the status and deployment timestamp is updated in Application Library. Click Validate to ensure that no error messages are displayed. enter the required information and click Deploy. In this example. After deployment is completed. Select Create Outline. PLANNING is selected. and the deployment job is marked completed and free of errors. ST01PLN6 is selected. Select a Shared Services project (application group).

member formulas. Completed. and menus. Capital Asset Planning-specific dimensions. Completed With Errors. Submitted Time—start time for large jobs. members. . On the Job Console toolbar. Running. Stopping. for multi-currency applications.After the deployment action is initiated. Status—status and progress of the job. the deploy process creates the following:      18. click Refresh to update the job results. smart lists. User Name—user name that submitted the job. An application and outline in Essbase without the need to refresh the cube from the Planning Web user interface. which displays the following information:  o o o o o o o o   Summary—Information about the job: Started Time—start time for small jobs. For Capital Asset Planning applications. and Not Responding. Server—server name where the job is running. HSP_Rates. Aborted (aborted due to an error). Process Name—process name in which the job is running Thread—thread ID of the current job. Job Console: A job ID is associated with each task in Job Console. Last Updated Time—last time the job was updated. Stopped (aborted by the user). data forms. upon deployment (it is not a dimension that you create manually). Scheduled Start. Each job can have the following status: Invalid. business rules. Tables and values in the Planning database. Attachments—file attachments associated with the job. Queued. Detail—job summary. Starting. Scheduled Stop (cancelled by the user). you can check Job Console for results. including errors and warnings.

Initializing the Capital Asset Planning Plan Type To initialize the Capital Asset Planning plan type: 1. The application is displayed.Accessing the Capital Asset Planning Application After deploying the application. The predefined Capital Asset Planning data forms are displayed in the content area. then Applications. 2. the Capital Asset Planning plan type is added to PlanBud. select Navigate. In Application Library. In Workspace. In this example. expand Forms and select Capital. you can add the Capital Asset Planning plan type to it in Performance Management Architect by selecting the Initialize menu command. the CapEx application is selected. you refresh the application list and access it through Workspace. and then <Application Name>. then Administer. In Workspace. Adding the Capital Asset Planning Plan Type to an Existing Planning Application If you have an existing Planning application. and then Application Library. select the Planning application in which you want to add the Capital Asset Planning plan type. 2. Select Navigate. select Navigate. . 3. then Planning. and then Refresh. The application list is refreshed. In this example. In the Select Data Form area. To access the Capital Asset Planning application after deployment: 1 . then Applications.

5. 6. For more information on the deployment process. click here. Note: Select Workforce and Capital Asset if the application will use both plan types. The following message is displayed while dimensions are created in the application: Seeding dimensions for Capex. On the Deploy page. and then Capital Asset. . click Yes.3. The following message is displayed: Validating Application for Deploy. click the Click here to navigate to jobs link. The validation process runs before the deployment. In the Job Task dialog box. In the Confirm Initialization dialog box. enter the required information and click Deploy. 4. Right-click the application and select Initialize.

To access the updated application in Workspace: 1 . Job Console: The application deployment displays a progress of 100% when it is completed. then Planning. click Refresh to update the job results. you access the updated application in Workspace. select Navigate. In this example. The predefined Capital Asset Planning data forms are displayed in the content area. Accessing the Updated Application in Workspace After the deployment is completed. click here. the PlanBud. The application is displayed. and then <Application Name>. application is selected. . On the Job Console toolbar. 2. expand Forms and select Capital.7. In Workspace. For more information on Job Console. then Applications. In the Select Data Form area.

Select an instance (cluster) to use for the application. PLANNING is selected. It must be different than an existing Essbase application. select Business Rules or Calculation Manager. click Create. In this example. On the Select tab. Log on to Workspace. fiscal start month. In this example. The name can contain up to eight characters. Select a Shared Services project (application group). then Classic Application Administration. Select Navigate. In Classic Application Wizard. 5. In this example. For Calculation Module. 3. Select the base time period. Enter a description of the application. In this example. . weekly distribution. and total years. then Administer.Creating Capital Asset Planning Applications in Classic Application Administration Creating Classic Capital Asset Planning Applications To create Classic Capital Asset Planning applications: 1. In this example. 4. ST01PLN4 is selected. ClCapEx is entered. 6. Calculation Manager is selected. 2. fiscal start year. Classic Capital Asset Planning application is entered. and then Planning Administration. Default Application Group is selected. In this example. Select the Calendar tab. Enter the name of the application. perform the following actions:       Select a data source.

If the application supports multiple currencies. In this example.    11. 12. Select the Plan Types tab. Select the Finish tab. Select the Currencies tab. Enter CapEx as the name for the Capital Asset Planning plan. Select the default application currency.7. select Yes. Review your selections and click Finish to create the application. and multiple currencies are supported. the following message is displayed: . Perform the following actions: Clear all plan type selections. 8. 10. 9. USD is selected as the default application currency. When the application creation is successfully completed. Select Capital Asset Planning under Planning Specialized Modules.

The application is displayed. . expand Forms and select Capital. then Initialization. Next to Go to the new application:. and then Capital Asset. When prompted to proceed with the initialization.Accessing and Initializing the Application To access and initialize the Capital Asset Planning application: 1 . ClCapEx is clicked. The application is displayed. 3. click OK. Select Administration. At the confirmation message confirms that initialization is successful. 5. In this example. 4. In the Select Data Form area. 2. click the application name. click OK.

1112/hp_admin.oracle.com/cd/E17236_01/epm.1112/cpx_admin. Summary In this tutorial.The predefined Capital Asset Planning data forms are displayed in the content area. Fusion Edition Administrator's Guide (http://docs. Fusion Edition Administrator's Guide (http://docs. 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.pdf) . Fusion Edition Administrator's Guide (http://docs.pdf) Oracle Enterprise Performance Management Workspace.oracle.oracle.com/cd/E17236_01/epm.pdf) Oracle Hyperion Capital Asset Planning.com/cd/E17236_01/epm.1112/bpmui_admin.

then Classic Application Administration. 4. click Manage Data Source. . 2. 2. In the left pane.1. Have defined an Essbase Server view in Administration Services Console.2 Prerequisites Before starting this tutorial. Select Navigate. and then Planning Administration. 3. To create Planning data sources: 1. then Administer. Have administrator access to Administration Services Console. you should: 1. 3.Creating Classic Planning Applications in Oracle® Hyperion Planning. Each Planning application requires a Planning repository. Fusion Edition 11.1. You can also click the Manage Data Source button in the content pane. Managing Planning Data Sources Dimensions and members are stored in the Essbase databases and in the Planning repository (Planning relational database).2. Have administrator access to a working installation of Oracle Hyperion Planning 11. Log on to Workspace. Have access to relational storage used to create a Planning data source.

Enter the server that hosts your database.4. In this example. localhost is entered. Click Validate Database Connection. ST01PLN2 is used.        The following message confirms that the connection was successful: . The default port for the Oracle database is 1521. Perform the following actions for the application database: Select a database platform. In this example. Enter the schema password. Enter the database port number. Enter the user associated with the database schema. In this example. Oracle is selected. the Oracle SID is ORCL. In this example. Enter the Oracle service name or system identifier (SID). Click Create Data Source. 5.

You can also click Create from Classic Application Wizard to start the application creation process. Click Finish. and click Validate Essbase Connection. . click Create Application. Enter the connection information to your Essbase Server.6. The following message confirms that the connection was successful: 7. Creating a Classic Planning Application To create a classic Planning application in Classic Application Administration: 1. In the left pane.

In this example. On the Select tab. Enter the name of the application. In this example. Calculation Manager is selected. and total years. In this example. Select the base time period. fiscal start month. Enter an application description. Select an instance (cluster) to use for the application. For Calculation Module. Default is selected. Select a Shared Services Project (application group). Select an application type. select Business Rules or Calculation Manager.2. the PlanBud application will be grouped under the Default Application Group. . the ST01PLN2 datasource created in the previous topic is selected. In this example. Select the Calendar tab. In this example. The name can contain up to eight characters. In this example. It must be different than an existing Essbase application. General is selected. weekly distribution. In this example. perform the following actions:        Select a datasource. we name the application PlanBud. 4. fiscal start year. 3. Planning and Budgeting application is entered.

Note: The name and number of plan types depend on your business requirements. the following message is displayed: . 6. 9. Select the Currencies tab. Incstmt and Balsheet are entered. Enter a name for both plan types. If the application supports multiple currencies. 8. and clear all other plan type selections. Perform the following actions:   Select Plan Type 1 and Plan Type 2. Select the default application currency. In this example. Select the Finish tab. Review your selections and click Finish to create the application. When the application creation is successfully completed. select Yes. 7.5. Select the Plan Types tab. 10.

you can add dimension members. In Workspace. In this example. then Applications. then Applications. and then [Application Name]. menus. and task lists. The Refresh menu option updates the navigation menu with new applications. After creating Classic Planning applications.Opening the Planning Application To open the Planning application in Workspace after creating it in Classic Application Administration: 1. 2. then Planning. data forms. select Navigate. 3. business rules. you open the PlanBud application. Select Navigate. and then Refresh. The PlanBud application is displayed. .

set performance settings. and then Dimensions. then Manage. Select Administration. .4. and change the evaluation order in Dimension Editor. You can manage dimensions.

then Application. Select Administration. You manage data forms and folders. After making changes to your application. and ad hoc grids in the Data Form Management page.5. 6. and then Data Forms and Ad Hoc Grids. Select Administration. you must refresh the Essbase database outline. . The Data Form Management page is displayed. the Manage. and then Refresh Database.

ensure that you:     Have a Planning application with the required metadata. Essbase refers to plan types as databases. This tutorial shows you how to load data into the Incstmt plan type in the PlanBud application. and then [Plan Type]. and other Planning objects. data forms. . In this example. The Incstmt plan type is selected. then [Server View]. then Essbase Servers. Log on to Administration Services Console. Loading Data Into the Application Prior to loading data to the application.7. then Planbud. Have defined an Essbase Server view in Administration Services Console. The following example displays a Planning application with defined dimensions. Make your selections and click Refresh. expand Enterprise View. 2. Have a data file that maps to the metadata defined in the application. the PlanBud application is accessed from the UPKPS1RC4:1423 Essbase Server view. members. Have administrator access to Planning and Administration Services Console. To load data into the application: 1. then Applications. In the left pane.

4.3. click Find Data File. Select Actions. and then Load data for "[Plan Type / Database]". In the Data Load dialog box. .

.5. and click OK. Select the File System tab. 6. locate your data file. Click OK to execute the data load process.

When the data load process is completed. . The following progress box is displayed during the data load process: 7. Open a data form in your Planning application to verify that data was loaded successfully. the Data Load Results dialog box displays a status of Success.You can also select the Abort on Error option in the Data Load dialog box to stop the loading process when an error occurs. 8.

1112/esb_dbag. Click New. 2 . 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. 3.oracle. Log on to Shared Services. 2 . .Summary In this tutorial.com/cd/E17236_01/epm.1112/hp_admin. you have learned how to:       Manage Planning datasources. Select Administration.pdf) Oracle Essbase Database Administrator's Guide (http://docs. Fusion Edition Administrator's Guide (http://docs. Have administrator access to a working installation of Oracle Internet Directory.2 Prerequisites Before starting this tutorial. Resources Oracle Hyperion Planning.1. Open the Classic Planning application that you created. The Defined User Directories page is displayed. Create a Classic Planning application.com/cd/E17236_01/epm. Have administrator access to a working installation of Shared Services.pdf) Integrating Oracle® Internet Directory and Hyperion® Shared Services 11. you should: 1 . Load data into Planning applications. To add new user directories: 1 .oracle. and then Configure User Directories.

Enter the OID port number. To set the connection information: 1 . Click Next. Enter a name for the connection. 2. 5. Under Directory Type. Enter a host name. 4. select Oracle Internet Directory. select Lightweight Directory Access Protocol (LDAP). The connection name is used to identify a specific user directory if multiple user directories are configured. Setting the Connection Information The Connection Information page contains the information used to connect to the directory server. . In the Directory Server drop-down list. 3.4.

9. Click Fetch DNs. 7. You can also enter the Base Distinguished Name (DN). . 6. In this example. enter the maximum number of results that a search can return. a custom port is used.5. In the Maximum Size text box. Accept the default value for the ID attribute. Optional: Select SSL Enabled if the user directory is configured for secure communication. 8. The default port number for Oracle Internet Directory is 389. Select Trusted if this provider is a trusted single sign-on (SSO) source. SSL is not enabled. In this example.

Ensure that Anonymous Bind is not selected. Enter the User DN and password.SSO tokens from trusted sources do not contain the user's password. 12 . 11 . 10 . Optional: Enter a unique user identifier and click Auto Configure. Note: The user URL should not point to an alias. . Click Next. To set the properties for the user URL: 1 . 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. 13 . Enterprise Performance Management System security requires that the user URL points to an actual user. Optional: Select Append Base DN if you want to append the Base DN to the User DN. The URL speeds the search. 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. With OID.

Note: If you are configuring OID as an external user directory for EPM System products deployed on Oracle Application Server in a Kerberos environment. Enter a last name attribute. Enter a first name attribute. 5. 6. you must set this property to userPrincipalName. . This attribute stores the user's last name. This attribute stores the user's first name. Enter a login attribute. the values for the succeeding text boxes will be filled in for you. Enter a user RDN. 3. If you choose to auto configure. 4. Each DN component is called a relative distinguished name (RDN) and represents a branch in the directory tree. Optional: Enter an email attribute. You use the login attribute as the user name when you log on to EPM System products. Enter an object class name.2. The login attribute stores the user's login name. 7. This attribute stores the user's e-mail address. and click Add. The RDN of a user is generally the equivalent of the user ID (uID) or common name (cn).

Enter an object class name.000. you cannot use the autoconfigure feature. f you choose to auto configure. The Group RDN has a significant impact on login and search performance. Otherwise. If you do not plan to provision groups or if users are not categorized into groups on the user directory. For optimum performance.8. Enter a name attribute. The search can negatively affect performance. 5. Note: The Group URL should not point to an alias. clear Support Groups and skip to step 5. To set group properties: 1 . ensure that the number of groups present within the group RDN do not exceed 10. Clearing this option disables the fields on this page. 2. Enter a group RDN. 4. because the root DSE of OID does not contain entries in the Naming Contexts attribute. Optional: Enter a unique group identifier and click Auto Configure. proceed to step 2. EPM System security requires that the group URL point to an actual group. 3. Because it is the starting point for all group searches. Shared Services searches within the Base DN to locate groups. and click Add. The URL speeds the search. . With OID. If you do not enter the group URL settings. Click Next. the values for the succeeding text boxes will be filled in for you. This attribute stores the name of the group. Data entry on the Group Configuration page is optional. 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. especially if the user directory contains many groups. you must identify the lowest possible node in which all groups for EPM System products are available. 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. use a group filter to retrieve only the groups that you want to provision. If more groups are present.

Select Administration. The Oracle Internet Directory that you added is displayed on the Provider Configuration tab on the Defined User Directories page. When the following status message is displayed. Log on to Shared Services. Click Save. click OK. Testing the OID Connection You must log on Shared Services using an administrator account to perform the following steps.6. Restart services. 2 . . The Defined User Directories page is displayed. and then Logout. 8. Shared Services uses the object classes (the mandatory and optional attributes) listed on this page to locate groups that should be provisioned. 9 . To test the OID connection in Shared Services: 1 . 7. Select File. and then Configure User Directories.

3. and click Test. and then Configure User Directories. Editing Directory Settings You must log on to Shared Services using an administrator account to perform the following steps. If the connection test failed. . When the connection test is successful. 5 . select Administration. To edit directory settings in Shared Services: 1 . Click OK. When the following message is displayed. click Save. the following status message is displayed: 4. Ensure that the OID directory is selected. proceed to the next topic to edit directory settings. In Shared Services.

and then Logout. When the following message is displayed. 5. 4. The Defined User Directories page is displayed. 8 . 7 . Restart services. click OK. 6. Modify the configuration settings as needed. Click Save. Select the Oracle Internet Directory that you want to modify and click Edit. Note: You cannot modify the configuration name.2. Select File. . Deleting Configured Directories You must log on Shared Services using an administrator account to perform the following steps. Optional: Log on to Shared Services and test your connection. 3.

and then Logout. 6 . Select the Oracle Internet Directory that you want to delete and click Delete. click OK. Restart services. and then Configure User Directories. 5.To delete configured directories in Shared Services: 1 . The Defined User Directories page is displayed. Summary In this tutorial. In Shared Services. select Administration. 4. When the following message is displayed. Select File. 3. 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 . When you are prompted to delete the external directory. 2. click OK.

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

At the bottom of the page. . 6. groups. the file system folder is named hss_ugr. 9. and roles and click Next. In this example. On the Destination page. and click Next. In this example. the default (asterisk wildcard) is accepted. Review the migration summary and click Execute Migration. and click Next. click Define Migration. Users 5. enter the name of the file system folder where the Shared Services artifacts will be exported. Review the destination options to ensure that the parameters are correct. 8. 7. Enter filters for the source users.

then Foundation. 11. In the left pane. Exporting Assigned Roles Each EPM System product provides several default roles tailored to various business needs. expand Application Groups. the exported artifacts are displayed under File System. On the Migration Status Report page. Click Launch Migration Status Report. Each application belonging to an EPM System product inherits these roles. When you assign a predefined product role to a user. review the status of the migration. The report status displays Completed when the migration completed successfully. .10. To export assigned roles: 1. you must migrate the Assigned Roles directory to ensure the same access between source and destination environments. Predefined roles from the applications registered with Shared Services are displayed in Shared Services Console. In the left pane. and then Shared Services. and click Refresh to display the updated job status.

5. In this example. the file system folder is named hss_roles. Enter filters for the roles and click Next. assigned roles for the Hyplan Planning application and Foundation Services are selected. the default (asterisk wildcard) is accepted. and click Next.2. . and click Next. 3. 4. In the content pane. In this example. Review the destination options to ensure that the parameters are correct. enter the name of the file system folder where the Shared Services role artifacts will be exported. select the assigned roles for products that contain artifacts for the Planning application and click Define Migration. In this example. On the Destination page.

In the left pane.6. The report status displays Completed when the migration completed successfully. . Review the migration summary. the exported artifacts are displayed under File System. 7. review the status of the migration. and click Execute Migration. On the Migration Status Report page. 8. Click Launch Migration Status Report. and click Refresh to display the updated job status.

and then EPM Architect. 3. select the dimensions that you want to export. expand Shared Library Dimensions. then Foundation. In the content pane. 4.. To export Shared Library dimensions: 1. and click Define Migration. and year. The Shared Dimensions directory contains shared dimensions artifacts. 2. enter the name of the file system folder where the Shared Library artifacts will be exported.Exporting Shared Library In this tutorial. On the Destination page. . account. the Performance Management artifacts are split into two sets: Shared Dimensions and Application. In this example. In the left pane. and click Next. such as entity. In this example. all dimensions in the source's Shared Library are selected. the file system folder is named epma_shared. expand Application Groups. Review the source options and click Next.

In the left pane. review the status of the migration. 7. The report status displays Completed when the migration is successfully completed. the exported artifacts are displayed under File System. .5. Review the destination options to ensure that the parameters are correct. Click Launch Migration Status Report. Review the migration summary and click Execute Migration. On the Migration Status Report page. and click Next. 6. 8. and click Refresh to display the updated job status.

which requires you to export its application metadata. and then [Your Planning Application. the Planning application was created in Performance Management Architect. 3. then Planning Applications. local dimensions and planning settings for the Hyplan Planning application are selected.Exporting Performance Management Applications Planning applications require a shell application: either a Classic shell application or Performance Management shell application. . and then EPM Architect. In this example. In the left pane. In the content pane. In this tutorial. 2. To export Performance Management Architect application metadata: 1. expand Application Metadata. Select Local Dimensions and Planning Settings and click Define Migration. then Foundation. expand Application Groups.

7. Review the source options and click Next. review the status of the migration. 8. 9. 6. 5. 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. and click Refresh to display the updated job status. . Click Launch Migration Status Report. On the Migration Status Report page. Review the migration summary and click Execute Migration. and click Next. On the Destination page.4. Review the destination options to ensure that the parameters are correct.

In the left pane. the exported artifacts are displayed under File System. then Foundation. and then Calculation Manager. expand Application Groups. rule sets. In the left pane.The report status displays Completed when the migration is successfully completed. and templates. . formulas. Exporting Calculation Manager Artifacts You can migrate the following Calculation Manager artifacts: rules. scripts. To export Calculation Manager artifacts: 1.

Review the destination options to ensure that the parameters are correct. You can also select specific artifacts under your Planning application if you do not want to export all Calculation Manager artifacts. and click Next. . In this example. and click Next. In this example. On the Destination page. the Hyplan Planning application is selected. enter the name of the file system folder where the Calculation Manager artifacts will be exported. 3. and click Next. expand Planning. select [Your Planning Application].2. In the content pane. 4. and click Define Migration. the file system folder is named calc_hyplan. 5. Review the source options.

Review the migration summary and click Execute Migration. and click Refresh to display the updated job status. review the status of the migration. 8. Click Launch Migration Status Report. The report status displays Completed when the migration is successfully completed . 7. the exported artifacts are displayed under File System. . On the Migration Status Report page. In the left pane.6.

. Note: If you associated your Planning application with a different application group. user variables. cell text. spread patterns. and so on Plan types Security—access permissions To export Planning application artifacts: 1. In the left pane. you must navigate to that application group and select your Planning application. account annotations. task lists. and supporting details Global artifacts—substitution variables. and then [Your Planning Application]. then Default Application Group.Exporting Planning Application Artifacts You use Lifecycle Management to migrate the following types of Planning artifacts:      Configuration—user preferences. and application settings Relational data—planning units. text values. expand Application Groups. business rules.

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.

select File System. In this example. 4. On the Destination page. . enter the name of the file system folder where the repository objects will be exported. Review the source options and click Next. the file system folder is named repobj. 5. Review the destination options to ensure that the parameters are correct. and click Next. and click Next.3.

Click Launch Migration Status Report. In the left pane.6. and click Refresh to display the updated job status. The report status displays Completed when the migration is successfully completed. review the status of the migration. . On the Migration Status Report page. the exported artifacts are displayed under File System. 7. Review the migration summary and click Execute Migration. 8.

Navigate to the following directory: [Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory In this example. and extract the file system folders. . or burning them to a DVD. you navigate to C:\oracle\Middleware\user_projects\epmsystem1\import_export\admin@Native Directory. The default file system location for the exported artifacts is: [Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory In this topic. copy it to the destination environment. The exported file system folders are displayed.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. 2. and copy or compress the import_export directory. sending them through FTP. You can accomplish this task by copying and pasting the artifacts. To copy source artifacts to the destination environment: 1. Navigate two levels up. you compress the source artifact directory.

In the destination environment. Typically. 3. in new environments. the import_export directories do not exist until you run a migration. navigate to [Middleware Home]\user_projects\epmsystem1.In this example. . the import_export directory is compressed with 7-zip.

. Open the import_export and [admin_user]@Native Directory folders. Copy and extract the compressed file.4. 5. Notice that the import_export directory does not exist.

Importing Guidelines:   Shared Services artifacts must be imported before you import any other artifact. 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. In this topic. 2. In the left pane. To import Planning applications from the file system into the destination environment: 1. In this example.6. hss_ugr is selected. Performance Management Architect application metadata artifacts must be imported before you import Planning artifacts. 3. you run the Lifecycle Management migration in 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. . Log on to Workspace and open Shared Services Console. and roles. select the file system folder that contains the Shared Services users. In the left pane. expand File System. groups.

verify that the artifacts were selected. and click Define Migration. verify that Foundation:Shared Services is selected. On the Artifact List tab. Review the source options and click Next. and click Next. and click Execute Migration. On the Destination page. .4. and click Next. 5. click Select All. 8. On the Destination Options page. 6. 7. accept the defaults. Review the migration summary.

The report status displays Completed when the migration is successfully completed. 13. verify that all artifacts are selected. Click Launch Migration Status Report. 11. and click Refresh to display the updated job status. Review the source options and click Next.9. . select the file system folder that contains the Performance Management Architect Shared Library dimensions and members. which will cause your migration to fail if they have not been imported to the Shared Library. In this example. 12. epma_shared is selected. Some Planning applications require Shared Members. review the status of the migration. It is recommended that you import Shared Library dimensions and members before importing Planning applications. 10. and click Define Migration. under File System. On the Artifacts tab. On the Migration Status Report page. In the left pane. click Select All.

under File System. 19. In this example. On the Migration Status Report page. select the file system folder that contains the Performance Management Architect application metadata. . Click Launch Migration Status Report. 17. verify that Foundation:Performance Management Architect is selected and click Next. 18. 16. 15. Click Refresh to display the updated job status. On the Destination Options page. review the status of the migration. accept the defaults and click Next. epma_hyplan is selected.14. On the Destination page. In the left pane. The report status displays Completed when the migration completed successfully. Review the migration summary and click Execute Migration.

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. enter the remaining required parameters. On the Destination Options page. and click Next. 22. On the Artifacts tab. select Deploy after Import and Create Outline. click Select All. and click Define Migration.      . 23.20. On the Destination page. and click Next. In this example. verify that all artifacts are selected. verify that Foundation:Performance Management Architect is selected. and click Next. 21. Review the source options.

Review the migration summary. 25. review the status of the migration. and click Refresh to display the updated job status. and click Execute Migration. Click Launch Migration Status Report. On the Migration Status Report page. The report status displays Completed when the migration completed successfully. . calc_hyplan is selected. In this example. In the left pane. under File System. select the file system folder that contains the Calculation Manager artifacts for your Planning application. 27. 26.24.

31. verify that Foundation:Calculation Manager is selected. 30. Review the source options. Review the destination options. Review the migration summary. and click Define Migration. 32. verify that all artifacts are selected. and click Execute Migration. and click Next. On the Destination page. click Select All.28. 29. and click Next. . and click Next. On the Artifacts tab.

select the file system folder that contains the Shared Services assigned roles. 36.33. In the left pane. Click Launch Migration Status Report. 35. and click Define Migration. On the Artifacts tab. review the status of the migration. On the Migration Status Report page. and click Next. and click Refresh to display the updated job status. hss_roles is selected. 34. verify that all artifacts are selected. . under File System. click Select All. The report status displays Completed when the migration completed successfully. In this example. Review the source options. 37.

On the Migration Status Report page. 39. review the status of the migration.38. . Review the migration summary. The report status displays Completed when the migration completed successfully. and click Next. 40. Click Launch Migration Status Report. and click Refresh to display the updated job status. verify that Foundation:Shared Services is selected. On the Destination page. Review the destination options. and click Execute Migration. 42. and click Next. 41.

click Select All. In the left pane. Review the source options. 46. select the file system folder that contains the Planning application artifacts. and click Next. On the Destination page. 44. On the Artifacts tab. and click Define Migration. In this example. under File System. and click Next. pln_hyplan is selected. 47. 45. and click Next. verify that all artifacts are selected.43. Review the migration summary. . verify that Default Application Group: Hyplan is selected. Review the destination options. 48. and click Execute Migration.

The report status displays Completed when the migration completed successfully. and click Refresh to display the updated job status. select the file system folder that contains the repository objects. repobj is selected. On the Migration Status Report page. . 51. On the Artifact List tab. In this example. and click Next. verify that the artifacts were selected. and click Define Migration. Click Launch Migration Status Report. under File System. In the left pane. 52. review the status of the migration. Review the source options. click Select All.49. 50. 53.

expand User Directories.54. The migration for all artifacts is completed. In the left pane. and click Next. On the Destination page. On the Migration Status Report page. The report status displays Completed when the migration completed successfully. and click Execute Migration. 57. 55. Click Launch Migration Status Report. 59. and click Refresh to display the updated job status. . Review the migration summary. verify that your artifacts imported completely. and then Users. On the Destination Options page. accept the defaults. verify that Reporting and Analysis:Reporting and Analysis is selected. Next. 58. review the status of the migration. 56. then Native Directory. and click Next.

. In Workspace.On the Browse tab. then [Planning Application]. click Search. Repeat the same steps for Groups and Roles. Expand Planning. 60. and then Rules. then Administer. and then Calculation Manager. and verify that the rules and rule sets for your Planning application are available. Next. It is also recommended that you review the assigned roles. open Calculation Manager. 61. select Navigate. then [Plan Type]. and review the user list.

oracle.1112/hp_admin. Verify that data forms.pdf) Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide (http://docs. Repeat the same steps to verify all nodes under all plan types in the Planning application. Summary In this tutorial. open your Planning application.62. menus.com/cd/E17236_01/epm.com/cd/E17236_01/epm. 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. and other Planning objects have migrated successfully. In Workspace. and then [Planning Application].pdf) . then Planning. Fusion Edition Administrator's Guide (http://docs. select Navigate.oracle. then Applications. smart lists.1112/epma_admin. Ensure that the rules associated with your Planning application are listed. Next.

 Oracle Hyperion Enterprise Performance Management (http://docs. Select Navigate. select File. In Application Library.2 Applications Prerequisites Before starting this tutorial. Have created Planning datasources. Sample applications were created in the tutorial environment. One data source for the Workforce Planning application created in Classic Administration. . you create a Workforce Planning application with no additional plan types. 2 .1.1. These Planning applications are not included with the software.1. Fusion Edition 11.1. 5 . and then Application Library. 3 . Have administrator access to a working installation of Planning 11.� Review the predefined elements. �Workforce Planning Structure. Have administrator access to a working installation of Hyperion® Shared Services 11. 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.2 Administrator's Guide and read Appendix A.2. 2.1112/epm_lifecycle_management. Plan the structure of the Entity dimension if you intend to use both Workforce Planning and Oracle Hyperion Capital Asset Planning. You can change the Entity members after you initialize the applications. To create Workforce Planning applications in Performance Management Architect using Application Creation Wizard: 1. Fusion Edition. One datasource for the Workforce Planning application created in Performance Management Architect.pdf) System Lifecycle Management Guide Creating and Initializing Oracle® Hyperion Workforce Planning. Fusion Edition 11. then New.oracle. Have administrator access to a working installation of Oracle Hyperion Performance Management Architect 11.2. 3. Have a working Planning application that was created in Performance Management Architect. and then Application (Z). 2. you should: 1 . 4 . Application Library is displayed. Log on to Workspace.2 with Workforce Planning enabled.1. Update dimension outlines to resolve differences between Workforce Planning member names and member names of other applications. This tutorial requires: 1. identifying which elements you can use and which elements you need to customize.com/cd/E17236_01/epm. Before you initialize Workforce Planning:    Download the Oracle® Hyperion Workforce Planning. then Administer.

4. In this example. Wkfc1 is entered. Select Auto Create Local Dimensions. Select Planning as the type. Workforce Planning application is entered. Select Workforce Name and enter a plan type name. In this example. In the Application Information area.Application Creation Wizard is displayed. 5. perform the following actions:     Enter an application name. . Enter a description. In the Planning area. perform the following actions:      Select General as the application type. Select Use Multiple Currencies. Accept USD as the default currency. Clear all plan type selections.

select a base time period. Select the first fiscal year. The following message is displayed: Creating application Wkfc1. Enter Year as the year name. make the necessary modifications. and weekly distribution. For Period and Year.6. Click Next. Select the number of fiscal years for the application. Select Create New Local Year Dimension. fiscal start month. perform the following actions:       Select Create New Local Period Dimension. Enter Period as the period name. 7. 9. In the Calendar area. . 8. Review the Dimension Selection page. and click Next.

10. . The following message is displayed: Dimensions for Workforce have been seeded. 11. The Application Settings page is displayed. expand Wkfc1. In the Member Area. Click OK. The dimensions created for the application are displayed.

The deployment process involves the following steps: Validate the application—The validation process is run upon application deployment. 16.12. If another deployment for the application is in progress. the status and deployment timestamp is updated in Application Library. If anything is missing in the application. make the necessary modifications to the dimension members. Select the environment information for deployment—Select the server and instance to which you are deploying the application.” After the job is marked "Completed" and free of errors. Export and deploy the application—When you deploy an application. the request is cancelled. If errors are found.     . the deployment is aborted. 14. the deployment job begins and the application is exported from Performance Management Architect to Planning. 13. Click Validate to ensure that no error messages are displayed. Click Validate. and the deployment job is marked “Completed. Planning creates the application and the product server attempts to load the metadata. The validation process checks for missing dimensions and other required information. enter the required information and click Deploy. Review the listed messages. the deployed Planning application becomes accessible in Workspace. 15. On the Deploy page. Create the product application—In new deployments. After deployment is completed. 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 Finish.

The deployment process creates a Planning application automatically. click Refresh to update the job results. In the Job Task dialog box. it is validated and deployed to Planning immediately. Select a Planning application server. Select Create Outline. Select a Shared Services project (application group). In this example. PLANNING is selected. Select a Planning datasource. PLANNING is selected. Default Application Group is selected. In this example. On the Job Console toolbar. Optional: Select Create Security Filters. After the deployment action is initiated. . In this example. 18.       Select a Planning instance. In this example. 17. The application name and description are entered when you first create the application in Performance Management Architect and are not editable. you can check Job Console for results. After you create a Workforce Planning application. ST01PLN7 is selected. click the Click here to navigate to jobs link. Optional: Select Shared Members Security Filters.

Queued. and Not Responding. Starting. User Name—user name that submitted the job. Scheduled Start. Last Updated Time—last time the job was updated. Each job can have the following status: Invalid. Submitted Time—start time for large jobs. including errors and warnings. Completed With Errors. Stopping. Stopped (aborted by the user). Status—status and progress of the job. Completed. Job Console displays the following information:  o o o o o o o o   Summary—Information about the job: Started Time—start time for small jobs.Job Console: A job ID is associated with each task in Job Console. Attachments—file attachments associated with the job. Detail— job summary. Running. Aborted (aborted due to an error). Scheduled Stop (cancelled by the user). . Server—server name where the job is running. Process Name—process name in which the job is running Thread—thread ID of the current job.

. Adding the Workforce Planning Plan Type to an Existing Planning Application If you have an existing Planning application. the Wkfc1 application is selected. select Navigate. and then Application Library. Select Navigate. To access the Workforce Planning application after deployment: 1 . and then <Application Name>. and then Refresh. then Administer. 2. 3. In Workspace. From the Select Data Form area. The application list is refreshed. select Navigate. In this example. then Applications. In Workspace. expand Forms and select Workforce. You do that by selecting the Initialize menu command. then Applications. you can add the Workforce Planning plan type to it in Performance Management Architect. The predefined Workforce Planning data forms are displayed in the content area.Accessing the Workforce Planning Application After deploying the application. Initializing the Workforce Planning Plan Type To initialize the Workforce Planning plan type: 1. you refresh the application list and access it through Workspace. The application is displayed. then Planning.

select the Planning application in which you want to add the Workforce Planning plan type. The following message is displayed: Validating Application for Deploy. In Application Library. and then Workforce. select Initialize. In the Confirm Initialization dialog box. 4. In this example. 3. the Workforce Planning plan type is added to PlanBud. The validation process runs before the deployment. Right-click the application. . Note: Select Workforce and Capital Asset if the application will use both plan types.2. click Yes.

On the Deploy page. 6. For more information on the deployment process. The following message is displayed while dimensions are created in the application: Seeding dimensions for Workforce. enter the required information and click Deploy. click here. . click the Click here to navigate to jobs link.5. In the Job Task dialog box.

and select Workforce. In the Select Data Form area. select Navigate. For more information on the Job Console. click here. In this example. On the Job Console toolbar. The application is displayed. To access the updated application in Workspace: 1 .7. click Refresh to update the job results. then Applications. Accessing the Updated Application in Workspace After the deployment is completed. . and then <Application Name>. expand Forms. 2. you access the updated application in Workspace. Job Console: The application deployment displays a progress of 100% when it is completed. then Planning. the PlanBud. In Workspace. application is selected.

Select Navigate. then Classic Application Administration. 3. and then Planning Administration. Log on to Workspace. Creating Workforce Planning Applications in Classic Application Administration Creating Classic Workforce Planning applications To create Classic Workforce Planning applications: 1. click Create. 2. then Administer.The predefined Workforce Planning data forms are displayed in the content area. . In Classic Application Wizard.

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:

then Initialization. Wkfc2 is clicked. At the confirmation message that initialization is successful. When prompted to proceed with the initialization. Next to Go to the new application:. . 2. Select Administration. The application is displayed. click the application name. 3. click OK. click OK. In this example. 4. and then Workforce.Accessing and Initializing the Application To access and initialize the Workforce Planning application: 1 .

expand Forms and select Workforce.oracle.com/cd/E17236_01/epm. 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.1112/bpmui_admin.1112/hp_admin.oracle. In the Select Data Form area. Summary In this tutorial.com/cd/E17236_01/epm. The predefined Workforce Planning data forms are displayed in the content area.5. Fusion Edition Administrator's Guide (http://docs. Fusion Edition Administrator's Guide .com/cd/E17236_01/epm. Fusion Edition Administrator's Guide (http://docs.1112/wfp_admin.pdf) Workspace.pdf) Oracle Enterprise Performance Management (http://docs.oracle. The application is displayed.pdf) Oracle Hyperion Workforce Planning.

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.