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. Write-Back
  6. Available Source to Target Write-Backs

Available Source to Target Write-Backs

You define data load rules to write back for Planning source systems.

The target system for a write back must be a file-based application that uses dimensions that match the General Ledger Chart of Accounts. You can create the file-based application using the Custom Target Application feature (see Creating a Custom Target Application). When creating the application, ensure that the Export to File option is "Yes".

Other Considerations:

  • Data load to write back is supported only for Planning applications, and Planning applications created from Oracle Essbase ASO cubes.

  • Data load rules to write back are not supported for EPMA deployed aggregate storage Essbase cubes.

  • Only monetary and statistical amounts can be written back.

  • Allocation from a source amount to multiple target amounts is not provided.

  • When specifying a period range, make sure the start and ending periods are within a single fiscal year. When data ranges cross fiscal years, duplicate data results.