How to disable stop transaction system menu option

[Former Member]

Hi,

We have an issue with one of our programs, this program sends 4 Idocs out of SAP and sometimes the users do a stop transaction by either right clicking on the SAP session in the windows taskbar or by using System Menu icon in the title bar. In such cases less than the required 4 Idocs are sent which leads to inconsistent results. Is there a way to disable the stop transaction option for a specific screen in a program.

Thanks,

Moses

[Former Member]

Hi Moses,

The only reason I can think that a user would want to "stop transaction" is because the program takes a considerable amount of time to execute. Now I am not aware of how to prevent the stop transaction, because other than stop transaction, you might need to "prevent" a lot of other functions on the same lines and this is not feasible.

Rather, how about advising/training users to execute the program in background. Instead of F8 ask them to click F9. This would schedule the program in the background and hence wipe out the possibility of the end user cancelling processing abruptly. Only a BASIS person would be able to by actually cancelling the work process.

Hope this makes sense as an alternative approach.

Regards,

Aditya

[Former Member]

The transaction sequences production orders to send to a shop floor execution system, I have also thought about executing the Idoc send part in the background by creating a job but the user wants online feedback in case one of the order fails the validation checks that are done before creating the Idocs. The user saves the data after sequencing and we create 4 Idocs to send the data out. We have trained users NOT to do the stop transaction but to let the program complete in case they missed something and then go back to the transaction, make changes and then save again so that the changes go out as an Idoc. The execution time depends on the number of orders sequenced and in some cases the users do a stop transaction by mistake (once in 6 weeks) and this throws both the systems out of sync and it takes some manual work to clean the data and bring them in sync. The worst case scenario is that, if not noticed in time this will stop the production line.

The users need an online feedback if the orders had any validation error so that they can go and fix the errors right away. The simplest way to avoid this I thought was to disable the stop transaction on the sequencing screen, after the user saves and they will also get the online feedback. I can also run this in the background and send an email to the user if there were errors.

I am not sure but I read somewhere that the stop transaction needs to be disabled at the OS level. Let me know if there is a quick and easy way to disable the stop transaction for just this screen, if not I will use the background and email solution.

Thanks,

Moses