Write-Back Mappings
When you are setting up an integration to pull from an EPM application and write back to Oracle E-Business Suite or PeopleSoft, consider the following:
-
Before you create a data load rule to write back, create the write-back mappings. Write-back mappings occur at the member level. (For example, loading data from an Oracle Hyperion Planning application to your Enterprise Resource Planning (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 is referred to when replacing outgoing dimension members with segment values.
The following interface tables require "write" security privileges for the data load to write-back process:
E-Business Suite
-
GL_INTERFACE
-
GL_INTERFACE_CONTROL
-
GL_BUDGET_INTERFACE
Standard PeopleSoft—PS_HPYPB_ACCT_LN
PeopleSoft Commitment Control
-
PS_HYP_KK_BD_HDR
-
PS_HYP_KK_BD_LN
To create write-back mappings: