Defining Data Write-back Rules

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 ASO or Essbase BSO application.

For Public Sector Planning and Budgeting applications where you have consolidated personnel (HR) and nonpersonnel expenses in the ASO cube, you pull information from the ASO application. For nonpersonnel related expenses you see only the total number (combination) in the ASO application.

Note:

Public Sector Planning and Budgeting requires that you combine the regular planning results from an Essbase BSO cube, with the personnel position budget information in an Essbase ASO cube to new ASO cube.

When performing the data write-back for a Public Sector Planning and Budgeting application, you select the ASO 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:

ERP Integrator imports data from Planning and writes it to ERP Integrator staging table.
ERP Integrator applies the necessary transformation in the staging table.
Data is exported from the ERP Integrator 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:

In the Tasks pane, select Data Write-Back.
Enter the Location Name or click to select the location name.
Click Add to add a data write-back rule.
Enter the Name.
For Planning applications: Select the Plan Type.
Optional: Enter a description.
Click Save.
Define the source filters. See Defining the Source Filter Options.