1. Administering Data Management for Oracle Enterprise Performance Management Cloud
  2. Integration Tasks
  3. Data Load, Synchronization and Write Back
  4. Synchronizing and Writing Back Data
  5. Data Synchronization

Data Synchronization

Data synchronization enables you to synchronize and map data between Oracle Enterprise Performance Management Cloud source to target applications irrespective of the dimensionality of the application simply by selecting the source and target EPM Cloud application, and then mapping the data. Given the powerful mapping features already available, the data can be easily transformed from one application to another application.

For example, use data synchromization to move data from:

  • Planning input cubes to reporting cubes,

  • Actuals from Financial Consolidation and Close to Planning reporting cube for variance reporting.

Tasks enabled by the data synchronization:

  • Create and modify synchronizations.

  • Select source and target applications.

  • Define mappings between sources and targets.

  • Push data from Planning to Oracle Essbase ASO cubes created by Planning.

  • Copy consolidated data from Essbase ASO cubes to Planning for future planning.

  • Execute synchronizations.

  • View logs of synchronization activities.

At a high level, the steps to synchronize data in Data Management include:

Note:

Make sure the EPM applications to be synchronized are registered as target applications.

  1. Import Format—Select the source and target Oracle Enterprise Performance Management System applications.

    The dimensional mapping is also defined in the import format. You map the dimensions that comprise each source and target application so that the synchronization can recognize all relevant elements.

    Note:

    To make certain that Data Management loads periodic instead of year-to-date (YTD data), you might have to hard code the "Periodic" Value dimension in the import format.
  2. Location—Create a new location and associate it with the import format.

  3. Data Load Rule—Define the source filter parameters.

  4. Data Load Mapping—Define the source to target application mappings.

  5. Execute—When the data rule is executed, data from the source EPM System is extracted to a file. The data can be imported and processed using the data load workflow process.

  6. Export—Synchronizes the data.