Ansicht
Dokumentation
RMDG_ADJUST_KEY_MAPPING - Adjust Key Mapping after Client Copy
PERFORM Short Reference ABAP Short ReferenceThis documentation is copyright by SAP AG.
Purpose
The report enables you to replace an old business system ID with a new business system ID for a particular main context.
Integration
After a client-copy in a new system, some of the identifiers of the mapped objects still have the business system ID of the old system. These IDs are not correct. They must instead use the business system of the new system. You use this report to replace the business system ID.
Prerequisites
- You have defined an existing main context IDand an existing business system ID.
- You have the necessary authorization to execute this report. The authorization check determines whether you are authorized to change a specific business system ID. This check is controlled by the MDG_IDM authorization check.
Features
Choose 'Adjust key mapping on local registry' (default) when you only want to get the old business system beeing updated with the new one.
Choose 'Adjust key mapping on central registry' when you want to enhance the existing key mapping data with newly created entries for the new business system. Therefore the programm processes the following steps:
- Selection of all existing objects for the entered 'old business system'.
- Copying these objects by changing the 'old' into the 'new' business system.
- Enhancing all mapping groups, the old objects are belonging to with the newly created objects.
You can run a simulation to check what will be reorganized. To do this, select the Test Run checkbox.
If you run the report in this mode, the system returns the number of identifiers in the mappings that would be changed for the specified main context ID.
Selection
Standard Variants
Output
The report creates two different output texts:
- Short Log
- Gives the number of identifiers in the various mappings that were changed.
- Detailed Log
- Gives a list of all identifiers and their elements, such as Object ID, ID Value, Object Identifier Type, and so on, that were changed
Activities
- Specify an existing main context ID and the old business system ID.
- Enter a name for the new business system ID.
- Choose either a short results log or a detailed results log.
Example
In the system the following mapping group exists for the entered data:
Object1 | Object2 | |
---|---|---|
Object Type | 194 (Material) | 194 (Material) |
Object ID Type | 20 (Material ID) | 20 (Material ID) |
ID Value | 123 | 456 |
Business System | SYS_001 | SYS_003 |
In dependency if you start the report with 'update local registry' or 'update central registry', the result looks like as described in the following:
- Report is started with the following parameters:
- Object Type: 194 (Material)
- Old Business System: SYS_001
- New Business System: SYS_002
- Local Registry: X
- The result is:
Object1 (changed) | Object Type | |
---|---|---|
Object Type | 194 (Material) | 194 (Material) |
Object ID Type | 20 (Material ID) | 20 (Material ID) |
ID Value | 123 | 456 |
Business System | SYS_002 | SYS_003 |
- Report is started with the following parameters:
- Object Type: 194 (Material)
- Old Business System: SYS_001
- New Business System: SYS_002
- Central Registry: X
- The result is:
Object1 | Object2 | Object3 (new) | |
---|---|---|---|
Object Type | 194 (Material) | 194 (Material) | 194 (Material) |
Object ID Type | 20 (Material ID) | 20 (Material ID) | 20 (Material ID) |
ID Value | 123 | 456 | 123 |
Business System | SYS_001 | SYS_003 | SYS_002 |
Fill RESBD Structure from EBP Component Structure Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 6988 Date: 20240520 Time: 083246 sap01-206 ( 75 ms )