At one point or the other, you have experienced that the employee master data replication aborts or does not work as expected. For example, it
- fails with an error message which is not sufficient to solve the underlying problem,
- is successful but the data in the SAP ERP system is incorrect,
- is incomplete and expected data is missing in the SAP ERP system.
Due to the complexity of the replication process and the extensive customization possibilities, these problems are often difficult to analyze. In some cases, you must debug in order to find the root cause of such issues.
To tackle this challenge, development and support collected debugging tips & tricks in SAP Knowledge Base Article 3006964. Among other things, the following questions are answered in this article.
How can I monitor the data passed from SAP SuccessFactors?
The first step in an analysis is to check the data which comes from SAP SuccessFactors that will be stored in the SAP ERP system. We show you where to find this information.
How do I even start debugging?
Since the replication runs on a regular basis and you do not want your debugging analysis to interfere with it, you cannot simply set breakpoints for the replication user. We explain possibilities about how to overcome this in order to start a debugging session.
If the replication aborts with an error message, how do I quickly find the place where this error is raised?
Although you see error messages of aborted replications in SAP transaction SLG1, sometimes it is not clear why exactly this error was raised. But once you know the coding place where this happens, you will understand the underlying reason much better. We present you with a few clicks which immediately take you to the right place.
How to set breakpoints in a smart way?
The replication coding itself consists of thousands of lines. But depending on the problem, you can narrow down where in the coding it is worth to take a closer look. For example, we point out the classes and methods where the replication customizing is handled. Or if an error happens during the validation of the info type or during the update process, we will give you hints how to find the responsible coding.
So long story short: Check out SAP Knowledge Base Article 3006964 and empower yourself with its enclosed troubleshooting skills!”