After migrating SAP Adapter from 6.x to 7.x in some cases the data received by the adapter doesn't matches with the data sent by the SAP system or is truncated. Some of the probable reasons for this issue is mentioned below.

1) The encoding of the SAP system is not consistent with the encoding of the RFC destination used by the SAP adapter for communicating to the SAP system.
2) The adapter service is not refreshed to use the latest schema after the migration.
3) The BW adapter activity is not refreshed to refer the latest adapter service schema after the migration.

How to troubleshoot SAP Adapter data mismatch issue after migrating from 6.x to 7.x

All

In order to troubleshoot and resolve this issue perform the below mentioned steps.

a) Check the encoding setting of the RFC destination being used by the SAP adapter and ensure that it is consistent with the encoding of the SAP System/DB i.e if the SAP system is Unicode then the corresponding RFC destination should also be set to use encoding as Unicode and similarly if the SAP system is Non-Unicode then the corresponding RFC destination should also be set to use encoding as Non-Unicode.

To check the encoding of your SAP system log on to your SAP system through the SAP GUI and then click on 'System > Status'.



To check the encoding setting for the RFC destination log on to the SAP System through SAP GUI, once logged in use T-code SM59 and go to the respective RFC destination and click on 'MDMP & Unicode' tab.



b) Using designer refresh the schema for the Adapter service to ensure that the latest schema is used after the migration and while doing so when designer prompts for using existing schema, please select 'No' .


c)  Using designer refresh the adapter service on each of the BW adapter activity using the option 'Refresh Adapter Service' in order to make sure that it is synced up with the latest migrated adapter service schema.