Data Mapping: Previous Next
Data Mapping: Previous Next
Send feedback
Before you start any of the replication scenarios in Central Finance you typically perform mappings.
PreviousNext
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 identifiers 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 for business object identifiers (for example, customer ID, vendor ID, or material ID).
• Mapping for codes (for example, company code, business area, or country code).
NoteCentral 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.
• Mapping for short-living cost objects (for example, production order or internal order).
CautionIf it is necessary to change values or key mappings after you have carried out an initial load and
started ongoing replication you must be aware that this may lead to serious inconsistencies in follow-on
processes. For example, if you change the mapping of a business partner (customer or vendor), and you
have already transferred invoices involving this business partner to the Central Finance system, follow-on
documents, such as clearing documents, would be posted to a different business partner. Another example
is the company code mapping: let’s assume that source company code 1000 is mapped to target company
code C100 and later on, during the fiscal year, the mapping is changed and the source company
code 1000 is mapped to C200. In this case, replicated documents are posted partly in the company
code C100 and partly in the company code C200 leading to inconsistent data.
PreviousNext