You create a data load rules to write back to extract budget data from an application to a general ledger instance and ledger source.
You can create data load rules to write-back in these ways:
Choose the Planning application.
Choose the Essbase aggregate storage (ASO) or Essbase block storage application (BSO).
For Public Sector Planning and Budgeting applications where you have consolidated personnel (HR) and non-personnel expenses in the aggregate storage cube, you pull information from the aggregate storage application. For nonpersonnel-related expenses you see only the total number (combination) in the aggregate storage application.
Note:
Public Sector Planning and Budgeting require that you combine the regular planning results from an Essbase block storage cube, with the personnel position budget information in an Essbase aggregate storage cube to a new aggregate storage cube.
When performing the data load rule to write back for a Public Sector Planning and Budgeting application, you select the aggregate storage cube that you created in Public Sector Planning and Budgeting. You can also select a Planning application as the source for the write-back.
The process at a high level:
FDMEE imports data from Planning and writes it to a FDMEE staging table.
FDMEE applies the necessary transformation in the staging table.
Data is exported from the FDMEE staging table to a general ledger interface table.
The mapping is used to format the data in the journal import tables.
After a successful execution of the data load rule to write back log in to the general ledger source system and run the budget import process in the general ledger.
To define data load rules to write back:
to select the location name.