on 03-28-2007 5:35 PM
This issue is about my previous thread which has been resolved:
"Missing segment in invoice idoc" https://www.sdn.sap.com/irj/sdn/collaboration
Can we debug this in production system?
please vote to NO or YES then give your wildest comments...
Thank you all
Hi,
Normally debugging in production is not advised/allowed because it will have an impact on the system performance. What we normally do is replicating the same issue in the staging/integration system. If it can be reproduced the staging system, we can debug in the staging system. There is no need to debug in production system. More than 80% scenarios, we should be able to replicate the issue in staging system since it is a production copy (Staging system should be refreshed by copying from Production system periodically, atleast once in a month). If it can not be replicated in the staging system, as a last resort we can debug in the production system , probably in the non-peak hours. Commit to database or document posting may not be an issue. We can stop proceeding the debug session by just quitting. Since IDOC is in error stage, it may not get posted. Even if it is posted, we can cancel the document.
Normally for production debugging, special user id is issued by Basis/Security team.
Regards
Anil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, Incase of error / problem, it is required to debug in production server also.
Regards,
Rajesh Banka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Sure you can debug the idoc in the production system also.
But every body wants testing data not to post in the data base.
So for this first you find out COMMITWORK statement in the idoc.
If you dont find this you will try to find MODIFY or UPDATE or INSRET statement in the program and put breakpoint in these points and you can debug upto before above these statements when you encounter these statements you can RESTART the begug screen.In this way you can do this.
As my understanding this is only the way to debug.
Thanks,
shyla
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pablito,
Yes we can debug the issue in producion if have the access.but if the programm is linked with other things, it may leads to many coplications.
But sincerly not advisabel.
Reward if really helpful.
Regards,
Sateesh.Kandula
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.