Defining the Write-Back Mappings (EBS and PeopleSoft only)

When you define an import format, you can also define the import format mappings from the EPM application for the data write-back rule. In the case where you have imported data from your source system and want to write-back, the auto create option identifies the original data load mapping and creates the reversal of the mapping.

When you create the write-back mapping definition, map one dimension to one segment mapping where no data load mapping is available. If a data load mapping is available, then that is the basis for the transformation. Inbound import formats are defined using the Data Load Mapping tab, and write-backs are defined using the Write-back Mapping tab.

  To define the write-back import format mappings:

  1. In Import Format, select the Import Name.

  2. Select the Write-back Mapping tab.

  3. Optional: Click Autocreate to automatically create import mappings from the EPM application dimension (source) to the target ERP source system segment or chartfield. Then, click OK.

    In scenarios where data load mappings are available (metadata or data was sourced from the ERP source system using FDMEE) the same mappings can be reverse-engineered to identify the EPM target application to ERP source system mappings.

    Example 1: Single Segment Mappings

    Table 11. Mappings Set for the ERP Source System to EPM Target Application

    Segment 1Segment 2Segment 3Segment 4Segment 5Dimension
    Company     Entity
    Cost Center    Department
    Account    Account
    Product    Product
    Location    Location

    When you click the Auto Create button, FDMEE automatically identifies the inward mappings and populates the EPM-to-ERP mapping as shown in the following example. In the case, FDMEE splits out the department back into the related cost center and location that was mapped in the forward mapping.

    Table 12. Automatic Creation of the EPM Target Application Mapping

    Source Dimension Target Segment or Chartfield
    EntityCompany
    DepartmentCost Center
    AccountAccount
    ProductProduct
    LocationLocation

    Note:

    When EPM Target Application mappings are automatically created, they extract the appropriate segment from a concatenated dimension and split it back when writing back the data.

    Example 2: Concatenated Segment Mappings

    Table 13. Mappings Set for the ERP Source System to EPM Target Application

    Segment 1Segment 2Segment 3Segment 4Segment 5Dimension
    Company     Entity
    LocationCost Center   Department
    Account    Account
    Product    Product

    When you click the Auto Create button, FDMEE automatically identifies the inward mappings and populates the EPM-to-ERP mapping as shown in the following example:

    Table 14. Automatic Creation of the EPM Target Application Mapping

    Source Dimension Target Segment or Chartfield
    EntityCompany
    DepartmentCost Center
    DepartmentLocation
    AccountAccount
    ProductProduct

  4. If you are not using the “Auto Create” option:

    1. Select each source dimension.

    2. For each dimension, enter the target segment or chartfield name.

    Tip:

    For E-Business Suite, you can use the same import format for multiple locations when you have multiple source accounting entities that use the same chart of accounts and are mapped to the same target applications. For PeopleSoft, you can reuse the same import format for multiple locations when you have source business units that share the same SETID for all chartfields and are mapped to the same target applications.

  5. Click Save.