Varad
Before going for Background job not listed in transaction SM50. Here and there you might have a foundation work dynamic in your work sign in SM37 which you need to troubleshoot or do some examination at run time. However, shockingly, you probably won’t have the option to see it in Cycle Outline t-code SM50. Let’s get started on background job not listed in transaction SM50.
The above work/report isn’t in the SM50 list underneath.
Solution 1:
Your scene should have more than one application servers. So you want to investigate different servers other than the server where SM50 is running. Check the above screen shot. The SM50 was running in server 05. The rundown of servers should be visible from t-code SM51.
How to Debug any Work Item in SAP Workflow?
Solution 2: You can likewise see your work in the Worldwide Work Cycle Outline t-code SM66.
Check in the underneath screen, there are occupations from various servers(20/02/04/05/07 and so forth). You can see the positions which was absent in SM50 list.
Tip to debug active job:
You can investigate the completed foundation occupations planned by your own client id by utilizing order JDBG.
You can investigate the dynamic foundation occupations booked by any client id utilizing t-code SM50/SM51.
Select the work, Program/Meeting >Program->Debugging.
Much thanks for your time!!
YOU MAY LIKE THIS
Automatically Fill Test Data in FM & BAPIs for SE37 – The Lazy Way
