Show TOC

Function documentationMapping in Central Finance

 

When accounting documents are posted in Central Finance, business mapping is used to harmonize the master data in the documents. Identifiers and codes in the documents must be mapped, that is, the relationship between an identifier or code used in the source system and one used in Central Finance must have been defined. This is necessary because sometimes different identifier or codes are used for the same entity. For example, in the source system, a customer may have the ID 28900 whereas in the Central Finance system, the same customer has the ID 13700. Codes and identifiers may also be different across the various systems of your existing system landscape.

Mapping must be defined for the following categories:

  • Mapping for business object identifiers (for example, customer ID, vendor ID, or material ID).

    This is done using MDG key mapping functions.

  • Mapping for codes (for example, company code, business area, or country code).

    This is done using MDG value mapping functions.

    Note Note

    Central Finance business mapping uses MDG mapping functions and its data repository. This does not mean that MDG master data governance processes have to be set up. It is sufficient to maintain the relevant mapping data in the Central Finance system. An extra license for MDG is not required if you only want to use the mapping functions and not the master data distribution functions.

    End of the note.
  • Mapping for short-living cost objects (for example, production order or internal order).

    This is done in Customizing of Central Finance.

Central Finance also offers Business Add-Ins (BAdIs) for mapping.

Features

Mapping with SAP Master Data Governance (SAP MDG)

The mapping of object identifiers and codes within Central Finance is based on SAP Master Data Governance (SAP MDG) value and key mapping. Value mapping in SAP MDG corresponds to code mapping in Central Finance and key mapping corresponds to object identifier mapping. This requires additional configuration.

You make these settings in Customizing for SAP MDG under Start of the navigation path Cross-Application Components Next navigation step Processes and Tools for Enterprise Applications Next navigation step Master Data Governance Next navigation step General Settings Next navigation step Value Mapping End of the navigation path and Start of the navigation path Cross-Application Components Next navigation step Processes and Tools for Enterprise Applications Next navigation step Master Data Governance Next navigation step General Settings Next navigation step Key Mapping End of the navigation path.

For more information, see the Customizing documentation for SAP MDG under Start of the navigation path Cross-Application Components Next navigation step Processes and Tools for Enterprise Applications Next navigation step Master Data Governance Next navigation step General Settings End of the navigation path.

Defining Mapping

Code mapping (value mapping in SAP MDG) is defined in Customizing for SAP MDG under Start of the navigation path Master Data Governance Next navigation step General Settings Next navigation step Value Mapping Next navigation step Maintain Value Mapping End of the navigation path.

Object identifier mapping (key mapping in SAP MDG) is either generated automatically as part of master data replication in SAP MDG or can be maintained manually in the transaction MDG_KM_MAINTAIN.

Note Note

If you have installed SAP MDG, in addition to the SAP MDG functions that are available with SAP Simple Finance, on-premise edition, the distribution of master data is also supported. For more information about SAP MDG, see the SAP HELP Portal at Start of the navigation path http://help.sap.comInformation published on SAP site Next navigation step SAP Business Suite Next navigation step SAP ERP Add-Ons Next navigation step SAP Master Data Governance End of the navigation path.

End of the note.
Mapping Entities and Mapping Actions

Central Finance uses mapping entities (the ID of a business object or code) and mapping actions to control how master data is mapped. All fields that belong to the same mapping entity are mapped in the same way. For each mapping entity, you can choose a mapping action to define how the system handles field values. The following mapping actions are available:

  • Keep Data: Field values of this kind are not mapped at all. The data from the sending system is retained.

  • Mapping Obligatory: The field values for all filled fields must be mapped. If no mapping data exists, an error is raised which can be corrected via error handling.

  • Map if Possible: The system tries to map any filled field. If no mapping data exists, no error is raised but the original data from the sending system is retained.

  • Clear Data: Fields of this kind are always cleared.

Additionally, you can implement the BAdI: Determine Mapping Action, if you want to make the mapping action dependent on the field value or on context information. For more information, see the documentation of the BAdI: Determine Mapping Action under Start of the navigation path Central Finance Next navigation step BAdIs: Central Finance End of the navigation path.

Activities

Define Mapping Entities (Enhanced Configuration)

If necessary you can enhance and change the existing set of mapping entities and dependent fields. Note that definitions that you make here override definitions delivered by SAP. For more information, see the documentation of the activity Define Mapping Entities (Enhanced Configuration) under Start of the navigation path Central Finance Next navigation step Mapping End of the navigation path.

BAdI: Enhance Standard Processing of Posting Data

You can use this BAdI to control the processing logic used to post accounting document data in Central Finance. For more information, see the documentation of the BAdI: Enhance Standard Processing of Posting Data under Start of the navigation path Central Finance Next navigation step BAdIs: Central Finance End of the navigation path.