Before you create a data write-back rule, you should create the write-back mappings. Write-back mappings occur at the member level and are used for data write-back rules. (Loading data from a Planning application to your ERP source system.) You create write-back mappings to replace outgoing dimension members with source segment members. More specifically, during budget write-back, the write-back mapping will be referred to when replacing outgoing dimension members with segment values.
The following interface tables require “write” security privileges for the data write-back process:
E-Business Suite
GL_INTERFACE
GL_INTERFACE_CONTROL
GL_BUDGET_INTERFACE
PeopleSoft
PS_HPYPB_ACCT_LN
For additional information on database tables access by ERP Integrator, see Source System Tables Used by ERP Integrator.
To create write-back mappings:
Explicit—The source value is matched exactly and replaced with the target value. For example, the source value, “ABC,” is replaced with the target value, “123.” “Explicit” write-back mappings are created the same for data load and data write-back rules. See Creating Mappings Using the Explicit Method.
Between—The range of source values are replaced with one target value. For example, a range from “001” to “010” is replaced as one value: “999.” “Between” write-back mappings are created the same for data load and data write-back rules. See Creating Mappings Using the Between Method.
Like—The string in the source value is matched and replaced with the target value. For example, the source value, “Department” is replaced with the target value, “Cost CenterA.” “Like” write-back mappings are created the same for data load and data write-back rules. See Creating Mappings Using the Like Method.
Tip: | You can click Refresh Values to refresh the list of segment or chartfield values that appear in the drop-down list from the source system. This is especially helpful when creating “Explicit,” “Between,” and “Like” mappings for data write-back data loads. |