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.”
You can define data load rules to write back for Oracle Hyperion Planning, Oracle Essbase aggregate storage (ASO), and Essbase block storage (BSO) 11.1.2.x applications only as the source and for these target source systems:
PeopleSoft Enterprise Financial Management
Oracle E-Business Suite
Fusion General Ledger
Oracle Hyperion Financial Management to Oracle E-Business Suite
Budget & Actuals may be exported to Peoplesoft interface table: PS_HPYPB_ACCT_LN. Peoplesoft provides a Generate Journal Process only for Budget data. There is no process pre-defined to Generate Journal for Actual data. You must write a custom Journal template for the actual data.
Other Considerations:
Data load to write back is supported only for Planning, Essbase aggregate storage, and Essbase block storage 11.1.2.x applications only. Applications created in earlier releases are not supported.
For BSO Essbase applications, Oracle Hyperion Financial Data Quality Management, Enterprise Edition requires that the Period dimension be designated as "Dense." Other dimensions can be Dense, but Period must be designated as dense to write back.
For E-Business Suite source systems, you can post to budgets with or without budget journals.
Only monetary amounts may be written back to the source ERP’s that provide a source adapter. If statistical amounts, or other data needs to be written back, then use scripting.
You cannot create data load rules to write back to PeopleSoft Human Capital Management source systems.
FDMEE loads data into the specific data interface table. You must then run the budget load routines provided by Oracle Fusion, E-Business Suite, or PeopleSoft Enterprise Financial Management.
Allocation from a source amount to multiple target amounts is not provided.
Data Load rules to write-back can be performed without first loading data from a General Ledger source to an EPM target.
The category assigned to upgraded and write back rules is randomly assigned and plays no role in the function of the rule. To view an upgraded rule, select Show All Categories, which may reveal "hidden" rules.
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.
This table shows available source-to-target write-back combination:
Table 3-22 Available Source to Target Write Backs
| Source | E-Business Suite Budget | E-Business Suite Actual | PeopleSoft Budget | PeopleSoft Commitment Control | PeopleSoft Actual | SAP | JD Edwards |
|---|---|---|---|---|---|---|---|
| Planning | Out of Box | Out of Box | Out of Box | Out of Box | Custom | Use custom application. | Use custom application. |
| Essbase | Out of Box | Out of Box | Out of Box | Not supported | Custom | Use custom application. | Use custom application. |
| Financial Management | Out of Box | Out of Box | Out of Box | Not supported | Custom | Use custom application. | Use custom application. |
| Oracle Hyperion Profitability and Cost Management | Out of Box | Out of Box | Out of Box | Not supported | Custom | Use custom application. | Use custom application. |
| ARM | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |