Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-APP-FIN (Application Component) MDG for Financials⤷
USMDZ (Package) Entities
IMG Activity
| ID | FMDM_USMDZ6001 | Define Reassignment |
| Transaction Code | S_SE4_70000047 | (empty) |
| Created on | 20080618 | |
| Customizing Attributes | FMDM_USMDZ6001 | Define Reassignment |
| Customizing Activity | FMDM_USMDZ6001 | Define Reassignment |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FMDM_USMDZ6001 |
Use
In this activity, you specify the entity types and systems for which key mapping is to take place during the outbound processing for distributing master data packages. Afterwards, you make the key mapping settings themselves in the Web Dynpro application USMDZ3_KEYMAPPING.
You use key mapping if individual entity types or attributes in the systems involved in the distribution have different values. This applies to Customizing keys such as account groups in a non-uniform system landscape and also can be relevant for master data such as group charts of accounts that, for example, have a different technical name in a consolidation system than in a system used for general ledger accounting.
Requirements
The following prerequisites must be met:
- You have activated the data model to which the entity types being defined are assigned.
- You have assigned the business systems to the relevant master data packages.
Note
In outbound processing, the SMT mapping is run after the key mapping. You make the settings for SMT mapping under Financial Master Data Management -> Distribution -> Create and Process Maps.
Standard settings
Activities
- Specify the relevant data model.
- Select the entity types for which key mapping is to take place.
- For each entity type, specify the systems for which key mapping is to take place.
Afterwards, the entity types and systems specified in this Customizing activity are available in the Web Dynpro application USMDZ3_KEYMAPPING.
Note
If no key mapping settings can be found for a specific object, even if this should be expected according to the Customizing settings, the methods of key mapping issue an exception and the replication of the master data is terminated.
Example
You use an SAP ECC system for general ledger and an SAP SEM system for consolidation. The group chart of accounts CONS is defined in the ECC system, but has the technical name 20 in the SEM system.
- Specify data model 0F.
- Select entity type CCOA.
- Select for entity type CCOA the business system of the SAP SEM installation. If the consolidation chart of accounts is also called CONS in the master data system, you do not have to select the business system of the SAP ECC installation.
- Run the Web Dynpro application USMDZ3_KEYMAPPING.
- Select entity type CCOA and enter the value CONS.
- Choose Start to enter the value 20 in the key mapping table in the row for the consolidation system.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | FMDM_USMDZ6001 | 0 | SE40000001 | MDG for Financials |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_USMDZ6001 | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20080729 |
| SAP Release Created in | 604 |
