Today, External Debugging of an Application of another SAP User in other Location in another Machine/System. we would investigate an extremely helpful hint in ABAP which I didn’t be aware in that frame of mind than a very long term SAP profession. As we continue to say, nobody can know it all in ABAP. On the off chance that somebody claims s/he knows nearly everything in ABAP either s/he is lying or s/he is GOD! Reverve her/him.
A day or two ago, one of our end client detailed an issue in one of our application program in our pre-creation framework. Everything worked appropriately and as need might arise being developed and quality framework. In any case, something turned out badly in pre-creation. I didn’t have the approval to execute the t-code/program in my pre-creation framework (as it was the duplicate of genuine creation framework). Being an engineer, I had investigate access and needed to investigate and see what was turning out badly yet I couldn’t as I didn’t have the approval to execute the t-code/program. The other issue was, the client being an end client, didn’t have approval to Troubleshoot. External Debugging of an Application of another SAP User in other Location in another Machine/System.
This was a conundrum circumstance. The client can execute yet can’t investigate. I can troubleshoot yet can’t execute. Also, the client was on the west shore of the nation and around then I was at the eastern piece of our country.
The most straightforward option would have been to raise a help solicitation to get approval for me to execute the t-code in pre-push. Yet, it would have required an investment to get the endorsements from all divisions.
Fortunately one of my companions let me know he read something about/hext client = username some place. This gives the individual who executes this order to permit the other client referenced in the order line to assume control over his/her meeting and troubleshoot.
Confounded?? Allow us to take a genuine model with genuine names.
Say Business end client’s name is Karyn (sap client id 00217) and Engineer’s name is Sergio (sap client id 00951).
Since Karyn has the approval to execute the t-code, she will put the order as/hext client = 00951 in her framework in SAP sitting far away on the west coast. Essential to see here is, she put the client id of Sergio, not herself. This implies she would like Sergio to do the Troubleshooting. She would simply empower the debugger and execute the meeting.
PS: There ought to be a space between/hext and client and = and username.
Since Sergio needs to troubleshoot he really wants to put an outer break point in his framework.
Since Sergio needs to troubleshoot a meeting of Karyn, he really wants to keep up with Karyn’s id in the Outer Debugger username as displayed underneath.
Assuming you receive the message “You are not approved for the outside investigating of client 00217” while attempting to save the other client’s id, then, at that point, go to the lower part of this post for another stunt. Reward Stunt.
Presently ask Karyn (end client) to execute the t-code and enter the order/hext client = 00951.
In the above screen shot check at the base right, it has Karyn’s client id (00217) and in the order, we composed Sergio’s client id (00951).
She will receive an underneath spring up message. Essentially, it is an admonition to the client that his/her meeting would be repaired by another person.
Request that she press alright and execute the program. The second she raises a ruckus around town button.. abracadabra…
You would see a troubleshooting meeting on your screen far away on the east coast as displayed beneath.
Check at the base right of the underneath screen capture, it has Sergio’s client id (00951).
Presently, you are a cheerful ABAPer. Troubleshoot, get the main driver and give the arrangement. No need of screen share, not have to get unique endorsement to execute the program and don’t bother being on a similar machine/framework and don’t bother being in a similar area. How advantageous. Isn’t it?
The end client, Karyn shouldn’t drop the meeting in her machine when Sergio is troubleshooting. In the event that she drops or exits from it, the troubleshooting meeting will end at Sergio’s end. On the off chance that, Karyn truly needs to strongly leave, she can put the order/hx and the two of them would exit.
Presently the reward tip for now which we guaranteed previously. Assuming you at any point get the blunder message “You are not approved for the outer troubleshooting of client XXXXX”, go to se37 and open FM “SUSR_CHECK_DEBUG_ABILITY”. Put a debugger as displayed underneath.
Rehash your action, i.e dole out another client and hit alright.
It will stop at the breakpoint in the FM. Simply change the SY-SUBRC to 0. You are finished.
Of all the power provide for ABAPers, I think, Troubleshoot with Supplant is the most grounded one. This is vital to any shut entryways for the ABAPers.
Yet, as Spiderman said, “to whom much is given, much will be expected”. So it is our obligation to not abuse it but rather use it capably.
Viva os ABAPers (May the ABAPers in Portuguese live forever)!!
We put a great deal of exertion in conceptualizing, testing and composing every single article. In the event that you could pass this connect to something like 5 partners/companions who you think would profit from our post, it would be an extraordinary blessing to our group. We believe our articles should reach to whatever number crowds as could be allowed with the goal that everybody would benefit and our group would stay propelled and our work doesn’t lose all sense of direction in this colossal expanse of the web.
YOU MAY LIKE THIS
Conquering the Full Stack Developer Interview: Essential Questions and Expert Tips
SAP HANA Cloud Tools: Empowering Development
BlackBox AI: Unveiling the Mystery Behind Machine Learning’s Magic
WhatsApp us