1. Administrator's Guide
  2. Integrating Data
  3. Data Load, Synchronization and Write Back
  4. Synchronizing and Writing Back Data
  5. Write-Back
  6. Defining Data Load Rules for Write-Back Scenarios (Data from EPM Cloud / Essbase Applications to Oracle Enterprise Resource Planning (ERP) Sources)

Defining Data Load Rules for Write-Back Scenarios (Data from EPM Cloud / Essbase Applications to Oracle Enterprise Resource Planning (ERP) Sources)

You create a data load rules to write back to extract budget data from application to a general ledger instance and ledger source.

You can create data load rules to write-back in these ways:

  • Choose the Oracle Enterprise Performance Management Cloud application.

  • Choose the Oracle Essbase aggregate storage (ASO) or Essbase block storage application (BSO).

The process at a high level:

  1. Oracle Hyperion Financial Data Quality Management, Enterprise Edition imports data from EPM Cloud and writes it to a FDMEE staging table.

  2. FDMEE applies the necessary transformation in the staging table.

  3. Data is exported from the FDMEE staging table to a file-based application.

  4. After a successful execution of the data load rule to write back, view the results of the balances transfer from the EPM Cloud application to the file using the Data Load Workbench.

To define data load rules to write back:

  1. On the Workflow tab, under Data Load, select Data Load Rule.
  2. Select the Location Name or click Search button to select the location name.
  3. Click Add to add a data load to write-back rule.
  4. Enter the Name.
  5. For EPM Cloud applications: Select the Plan Type.

    FDMEE supports data loads for up to six plan types (including custom and EPM Cloud applications.)

  6. Optional: Enter a description.
  7. Click Save.
  8. Define the source and target options.