You create a write-back rule for extracting budget data from an application to a general ledger instance and ledger source.
When you create a data write-back rule, you can 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 non-personnel related expenses you see only the total number (combination) in the aggregate storage application.
Note:
Public Sector Planning and Budgeting requires 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 new aggregate storage cube.
When performing the data 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 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 what you use to format the data in the journal import tables.
After a successful execution of the write-back rule, log in to the general ledger source system and run the budget import process in the general ledger.
To define data write-back rules:
From the Workflow tab, and then under Write Back Rule, select Write-Back Rule.
Enter the Location Name or click
to select the location name.Define the source filters. See Defining the Source Filter Options.