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 situations 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, you can 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.
Note: | It is not necessary to define import format mappings for an import format using a PeopleSoft Human Capital Management source system. |
To define the write-back import format mappings:
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 ERP Integrator) the same mappings can be reverse engineered to identify the EPM target application to ERP source system mappings.
Example 1: Single Segment Mappings
Table 2. Mappings Set for the ERP Source System to EPM Target Application
Segment 1 | Segment 2 | Segment 3 | Segment 4 | Segment 5 | Dimension |
---|---|---|---|---|---|
Company | Entity | ||||
Cost Center | Department | ||||
Account | Account | ||||
Product | Product | ||||
Location | Location |
When you click the Auto Create button, ERP Integrator automatically identifies the inward mappings and populates the EPM to ERP mapping as shown in the following example.
Table 3. Automatic Creation of the EPM Target Application Mapping
Source Dimension | Target Segment or Chartfield |
---|---|
Entity | Company |
Department | Cost Center |
Account | Account |
Product | Product |
Location | Location |
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 4. Mappings Set for the ERP Source System to EPM Target Application
Segment 1 | Segment 2 | Segment 3 | Segment 4 | Segment 5 | Dimension |
---|---|---|---|---|---|
Company | Entity | ||||
Location | Cost Center | Department | |||
Account | Account | ||||
Product | Product |
When you click the Auto Create button, ERP Integrator automatically identifies the inward mappings and populates the EPM to ERP mapping as shown in the following example.
If you are not using the “Auto Create” option:
Tip: | For E-Business Suite, you can use the same import format for multiple locations if 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 if you have source business units that share the same SETID for all chartfields and are mapped to the same target applications. |