Step Three : SAP Unicode Conversion Completion Activities

 

SAP Unicode Conversion Completion Activities.

After Import the System Copy as unicode system Only MDMP system we need to do after conversion activity. you need to run transaction SUMG after the System Copy is finished.

MDMP Systems only after the conversion of an MDMP or an Ambiguous Blended Code Page System, it is required to perform a couple of completion Steps in a different transaction named SUMG. 

Step 1:

 Upload the R3load log XML files. These files contain all tables and data records that have to be processed in Tcode .SUMG. After upload the SUMG work list is filled and the data records that must be post processed for all the tables in this work list are classified.

Step 2: 

The Automatically Repair uses the Reprocess Log created and maintained in Tcode SPUMG before. This step is necessary because R3load cannot access the Reprocess Log for performance reasons. However, if R3load detects the same problem as the Reprocess scan, it stores this information in an XML file. The Automatically Repair will use this information from the Reprocess Log then to convert the data once again in the Unicode system.

Step 3

Use the Manual Repair Methods to process table content which is still not correctly converted; data records, which had been created in SPUMG after the Reprocess scan or which had not been maintained in the Reprocess Log. You can also manually repair table rows later when the Conversion Completion is finished.

This Just an overview only before do the Unicode conversion go through the Unicode conversion guide.