First-Time Lifecycle Management Migration for Oracle Hyperion Financial Management 11.1.1 with Hyperion Shared Services Lifecycle Management 11.1.1


Purpose


This tutorial covers a first-time lifecycle management (LCM) migration for Oracle Hyperion Financial Management 11.1.1 classic or Enterprise Performance Management Architect (EPMA)-enabled applications. This lifecycle management migration utilizes Hyperion Shared Services Lifecycle Management 11.1.1.

Time to Complete


Approximately 2 hours.

Topics


This tutorial covers the following topics:

 Overview
 Scenario
 Prerequisites
 Exporting a Financial Management Application to the File System in the Source Environment
 Copying a Financial Management Application Artifacts from the Source Environment to the Destination Environment
 Creating a Financial Management Classic Application Shell in the Destination Environment
t6Importing a Financial Management Application from the File System in the Destination Environment
 Summary

Viewing Screenshots


Click icon to show all screenshots Click icon to show all screenshots

Note: Alternatively, you can click an individual icon (or image) associated with each step to view (or hide) the screenshot associated with that step.

Overview


In this tutorial, you perform a first-time migration with an Oracle Hyperion Financial Management (HFM) 11.1.1 application and Hyperion Shared Services Lifecycle Management 11.1.1 from a source environment to a destination environment.

The Financial Management application consists of artifacts from various products. For example:

  • Shared Services users, groups, provisioning artifacts, and task flows
  • EPMA dimensions, Calculation Manager, data synchronization, and import profile artifacts for EPMA-enabled Financial Management applications
  • Financial Management artifacts
  • Financial reports

Because the Financial Management application artifacts span multiple products, you must migrate the artifacts from each product as it relates to the Financial Management application.

Back to Topic List

Scenario


You are tasked with a first-time migration for an Oracle Hyperion Financial Management 11.1.1 application from a source environment to a destination environment. The 11.1.1 release is installed and configured on the source and destination environments, which utilize separate Shared Services 11.1.1 instances. Consequently, the file system will be utilized for this migration.

Back to Topic List

Prerequisites


Before starting this tutorial:

1.Install and configure Oracle Hyperion Financial Management 11.1.1 and all related 11.1.1 EPM products in the source and destination environments (Hyperion Shared Services, Oracle Hyperion Enterprise Performance Management Architect, Oracle Hyperion Financial Reporting, and so on).
2.The source environment must contain the Financial Management application with all metadata.
3.The source and destination user who is performing the lifecycle management activities is provisioned with the following roles:
  • Shared Services LCM administrator role
  • Financial Management application administrator role

Back to Topic List

Exporting a Financial Management Application to the File System in the Source Environment


1.

In the source environment, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.

 

2.

Navigate to Foundation > Shared Services, and select the native directory provisioning artifacts and the task flows that are applicable to the Financial Management application, as follows:

  • Users – Native Directory users
  • Groups – Native Directory groups
  • Assigned Roles – Roles granted to users and groups through the provisioning process. You should select the roles for the associated product artifacts that pertain to the HFM application.

Note: You should choose the assigned roles for all products that contain artifacts for the Financial Management application.

 

3.

Navigate to the HFM application group, and select the Financial Management application that you want to migrate; for example, Comma.

 

4.

Click Select All to select all Financial Management application artifacts.

 

5.

For EPMA-enabled Financial Management applications, navigate to Foundation > EPM Architect > Application Metadata > Consolidation Applications, and select the EPMA artifacts that reside under the Financial Management application that you are migrating. In the following example, it is Comma.

 

6.

Navigate to Reporting and Analysis to select the financial reports.

 

7.

Expand the Repository Objects folder, and navigate to the folders that contain the financial reports that are associated with the Financial Management application.

 

8.

Select the financial reports; for example, HFM Comma Reports.

 

9.

On the Selected Artifacts tab, review the set of artifacts that you selected for the Financial Management application migration.

 

10.

Click the Define Migration button to define theFinancial Management application migration.

 

11.

Select the first product to migrate (for example, Shared Services), and click Next.

 

12.

On the Source Options page, filter the user, groups, and roles as needed, and click Next.

 

13.

On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be extracted, and click Next.

 

14.

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

You are directed back to the beginning of the migration wizard so that you can define other product migrations.

 

15.

Select the next product to migrate (for example, EPM Architect), and click Next.

 

16.

On the Source Options page, click Next.

 

17.

On the Destination page, enter the name of the file system folder where the EPMA artifacts will be extracted, and click Next.

 

18.

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

 

19.

Select the next product to migrate (for example, Reporting and Analysis), and click Next.

 

20.

On the Source Options page, select Export with job output if you want that information to be migrated, and click Next.

 

21.

On the Destination page, enter the name of the file system folder where the Financial Reports artifacts will be extracted, and click Next.

 

22.

Review the Destination Options page to ensure that the parameters are correct, and click Next.

 

23.

Select the next application to migrate (for example, HFM Comma application), and click Next.

 

24.

Review the source options, and click Next.

 

25.

On the Destination page, enter the name of the file system folder where the Financial Management artifacts will be extracted, and click Next.

 

26.

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

 

27.

Review the Migration Summary to ensure that the defined migrations are correct.

 

28.

Click Save Migration Definition.

 

29.

Select Save as XML, and click OK.

 

30.

Click Save.

 

31.

Enter the location and name for the migration definition file, and click Save.

 

32.

In the Download Complete dialog box, click Close.

 

33.

Click Close.

 

34.

Click Execute Migration.

The Financial Management application migration is executed.

 

35.

Click Launch Migration Status Report.

 

36.

On the Migration Status Report page, review the status of the migration.

When the report status changes to Success, the migration is completed successfully, and the Financial Management application artifacts are extracted to the file system.

 

37.

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

 

Back to Topic List

Copying Financial Management Application Artifacts from the Source Environment to the Destination Environment


The source environment application artifacts that exist on the file system must be moved to the destination environment file system. You can accomplish this task by copying and pasting the artifacts, sending them through FTP, or burning them to a DVD.

Note that the default file system location for the life cycle management artifacts is on the Shared Services Web application server at <%hyperion_home%>\common\import_export.

The artifacts must also be copied into the user directory within this file system location.

In this example, you copy and paste the artifacts within Windows Explorer.

1.

In the source environment, navigate to Windows Explorer on the file system.

 

2.

Select Tools > Map Network Drive.

 

3.

Enter the parameters for the destination environment file system location.

 

4.

Click Finish.

 

5.

Navigate to the location of the source environment application artifacts.

 

6.

Select the folders, right-click, and select Copy.

 

7.

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

The database artifact folders now reside on the destination server file system location.

Back to Topic

Creating a Financial Management Classic Application Shell in the Destination Environment


Before migrating a Financial Management classic application, you must create the Financial Management classic shell application in the destination environment.

Before following these steps to create a classic application in the destination environment, you must have Oracle Hyperion Financial Management installed and configured in the destination environment.

Note: For Financial Management EPMA-enabled applications, you can skip this section.

1.

Log on to Oracle Enterprise Performance Management Workspace in the destination environment.

 

2.

Select Navigate > Administer > Classic Application Administration > Consolidation Administration > Create Application.

 

3.

Enter the application properties to create a Financial Management classic application shell.

 

4.

Click Create.

You have successfully created a Financial Management classic application shell.

Back to Topic List

Importing a Financial Management Application from the File System in the Destination Environment


You have exported the Financial Management application artifacts from the source environment to the file system and copied the artifacts to the destination environment file system.

1.

In the destination, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.


 

2.

Perform one of the following actions:

  • For Financial Management applications that are EPMA-enabled, proceed to step 3.
  • For Financial Management classic applications, skip to step 18.

 

3.

If the Financial Management application is EPMA-enabled, navigate to Application Groups > File System.

 

4.

Select the EPMA file system artifacts that are applicable to the Financial Management application.

 

5.

Click Define Migration.

 

6.

View the Source Options page, and click Next.

 

7.

Select the destination (in this case, EPM Architect), and click Next.

 

8.

Select the Dimension Import Mode of Merge or Replace, select Deploy after Import, enter the remaining parameters to deploy the application view to a physical Financial Management application, and click Next.

 

9.

Review the Migration Summary, and click Save Migration Definition.

 

10.

Click OK.

 

11.

In the File Download dialog box, click Save.

 

12.

Enter the location and migration definition file name and click Save.

 

13.

In the Download Complete dialog box, click Close.

 

14.

Click Close again.

 

15.

Select Execute Migration.

The migration is executed.

 

16.

Click Launch Migration Status Report to view the status of the migration

Notice that the migration is completed.

 

17.

Click Cancel to close the Migration Status Report.

 

18.

Navigate to Application Groups > File System, and select the Financial Management application artifacts, the Financial Management Shared Services artifacts, and the Financial Management application financial reports.

 

19.

Review the Selected Artifacts tab to view the artifacts that you selected for the migration.

 

20.

Click Define Migration.

21.

Select the Financial Reports artifacts, and click Next.

 

22.

Review the source options, and click Next.

 

23.

On the Destination page, select the Reporting and Analysis repository, and click Next.

 

24.

On the Destination Options page, select Exclude Job Output on Import (optional), and click Next.

 

25.

Select the Financial Management artifacts, and click Next.

 

26.

Review the source options, and click Next.

 

27.

Select the destination Financial Management application that you want to import the artifacts to, and click Next.

 

28.

For Import Dimension Mode and Import Phased Submission Assignment mode, select merge or replace, and click Next.

Note: If dimensions or phased submission assignments are not being imported, these options will not be considered.

 

29.

On the Source page, select Shared Services, and click Next.

 

30.

Review the Source Options page, and click Next.

 

31.

On the Destination page, select the Shared Services destination, and click Next.

 

32.

On the Destination Options page, select the import operation type and the number of maximum errors before stopping the import, and click Next.

 

33.

Review the Migration Summary, and click Save Migration Definition.

 

34.

Click OK.

 

35.

In the File Download dialog box, click Save.

 

36.

Enter the location and migration definition file name, and click Save.

 

37.

In the Download Complete dialog box, click Close.

 

 

38.

Click Close again.

 

39.

Click Execute Migration.

 

40.

Click Launch Migration Status Report.

The migration is completed.

 

Back to Topic List

Summary


Congratulations! You have completed your first migration using Shared Services Lifecycle Management release 11.1.1.

In this tutorial, you have learned how to:

 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.
 For Financial Management classic applications, create a Financial Management classic application shell in the destination environment.

Import the application artifacts from the destination environment file system to the application.

Note: For Financial Management EPMA-enabled applications, you must first migrate and deploy the EPMA dimensions.

Back to Topic List

Related Information


To learn more about Financial Management, refer to additional OBEs.

Back to Topic List

Left Curve
Popular Downloads
Right Curve
Untitled Document
Left Curve
More Middleware Downloads
Right Curve