Migrating Data and Adjustments from an Ownership to Non-Ownership Application

Considerations

  • If Consolidation Journals Workflow is enabled for the application, Posted journals cannot be imported.

  • Consolidated data cannot be imported. FCCS_Proportion data, which is Dynamic Calc in non-Ownership applications, and FCCS_Elimination data must be recalculated.

  • You do not need to export Configurable Consolidation Rules, as they are not used in non-Ownership applications.

Steps to be Done in Ownership Application

Data Export

  • Export Base Data Local Currency (non-Adjustments)

    • Data Sources – "FCCS_Data Input", "FCCS_Managed Data", "FCCS_Other Data" (if enabled) and any other custom Data Sources

    • Currency (In the case of Multiple Currency Applications) - "Entity Currency"

    • Consolidation – "FCCS_Entity Input"

    • Cube - Consol

  • Export Adjustment Data (Journals)

    Use Consolidation Journals module to export Journals to a JLF file.

  • Export Override Rates Data (Multiple Currency Applications)

    • Currency – ILvl0Descendants ("Input Currencies")

    • Consolidation – Children (FCCS_Overrides)

    • Accounts – ILvl0Descendants ("FCCS_Historical Accounts")

    • Cube - Consol

  • Export System Exchange Rates Data (Multiple Currency Applications)

    • Currency - ILvl0Descendants ("Input Currencies")

    • From_Currency – Children ("From Currency")

    • Entity – "FCCS_Global Assumptions

    • Account – ILvl0Descendants ("Entered Exchange Rates")

    • Cube – Rates

Metadata Export

  1. Export Custom Dimensions.

  2. Export Movement and Data Source Dimensions in case Custom members are created.

  3. Export Account, Entity, Currency, and Scenario core Dimensions.

Security Export

Refer to this topic:

EPM Automate Export App Security: How to export artifact-level assignments (ACLs) to a file

Steps to be Done in Target Non-Ownership Application

Create Application

  1. Create a non-Ownership application by enabling all the required features as the Source application, except for features associated with Ownership Management.

  2. Maintain the same application currency, start period and number of years.

  3. If there were posted journal in the source system, create the target application without Journal Workflow enabled to import Posted journals. If Journal Workflow is to be used, remember to Post the journals manually after importing the JLF file.

Import Metadata

  1. Create a job to import dimension extracts.

  2. Upload dimension extracts to target.

  3. Import Metadata into target environment.

  4. Refresh the Database after successful metadata import.

Refer to this topic:

EPM Automate Import Metadata: How to import metadata into application

Import Security

Refer to this topic:

EPM Automate Import App Security: How to import access permissions from a file

Approvals Setup

If the source application used Process Management (Approvals), then set up Approvals in the target application.

Import Data

  1. Create Import Data Jobs to import data into the respective Cubes.

  2. Upload data extracts to target.

Refer to this topic:

EPM Automate Import Data; How to import data into an application

Import Journals

  1. Create Import Journals job to import JLF file.

  2. Upload JLF to target.

Refer to this topic:

Import Consolidation Journals into Financial Consolidation and Close Applications Using EPM Automate

Consolidate Data

Data must be consolidated to generate calculated data. If the application is multiple-currency enabled, you must run the Translate business rule for the respective reporting currencies.