/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
If you are unsure if there is PDI code involved in an issue/dump that you are receiving on the UI, you can use the Tracing tool in the SDK to find out.
Environment
SAP Cloud for Customer
SAP Business ByDesign
SAP Cloud Application Studio
Resolution
Please note, to use the Tracing tool in the SDK, you do not need to know the Solution name, and you do not need to open any Solution before you Start Tracing.
- Log in to the Front End System first (i.e C4C or ByD etc.)
- Make sure you have the Cloud Application Studio SDK downloaded. If you do not, please refer to this Case Document 1937930 - How to Download the Cloud Application Studio from Support Portal
- Open the Cloud Application Studio SDK
- Once it has loaded, select the Start Tracing icon.
- If you cannot see this icon, you can also find it here:
- Go to the frontend, and reproduce the issue.
- When you are finished reproducing the issue, select the Stop Tracing icon.
- If you cannot see this icon, you can also find it here:
- Now select the Trace Explorer icon
- If you cannot see this icon, you can also find it here:
- The Trace Explorer window will appear, and you can highlight the trace you took, and select Get Trace Details. (If you cannot see the trace you have taken, select the refresh icon)
- If there is PDI involvement, you can see PDI solution name along with the path from SDK.
- If there is no PDI involvement, you cannot see PDI solution name in trace details.
Once you get PDI solution name and path, you can put the breakpoints and debug further your code to understand the exact cause for the error/dump.
For more details about debugging and tracing please refer PDI Help Document article '5.5.8 Trace Explorer' and '8.17 Debugging '.
See Also
You can also check the blog Performance ABSL Trace – New functionality in 2005 Release which will help you to identify the exact time take to execute your custom script.
Keywords
SDK trace, Dump error, Frontend error, Debugging , KBA , sdk trace , performace trace , AP-RC-BDS-SCR , ByDesign Studio Scripting (ABSL) , How To