In This Section:
Financial budgeting in formation often must be compared with and controlled with actuals and stored in the general ledger system. You define data write-back rules to determine how you want to extract the budget data from Planning and write it back to the ERP system. For example, you may want to write-back budget data.
You can define write back rules for Planning, 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
Considerations:
Data Write-back is supported 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, FDMEE requires that the Period dimension be designated as “Dense”. Other dimension can also be Dense but Period is required to be dense for write back to work.
Data Write-back is not supported for EPMA deployed aggregate storage Essbase cubes,
For E-Business Suite source systems, you can post to budgets with or without budget journals.
Only monetary and statistical amounts are eligible to be written back to the general ledger.
You cannot create data write-back rules for 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.
You must have the GL Write-back security role to create data write-back rules.
Write-back can be performed without first loading data from a GL source to an EPM target.