topic Re: about screen in Application Development and Automation Discussions

about screen

as_dr — Fri, 13 Apr 2012 06:48:06 GMT

Hi Experts,

My problem is regarding with screen after creating the document (in any t-code) want to exit the current screen fe.if the user create the order in VA01 and save the document system should shutting the existing screen how can I solve the problem what I need?

Thanks so much for any help

Re: about screen

Former Member — Fri, 13 Apr 2012 06:50:28 GMT

Try to use 'LEAVE PROGRAM'.

Re: about screen

matt — Fri, 13 Apr 2012 07:15:24 GMT

Please use a meaningful subject in future

What you want is for every transaction to leave the existing screen when save is pressed? That's not how SAP is designed. You would have to change nearly every transaction.

Given the question as stated, how Gaurav's answer is correct is beyond me.

Re: about screen

as_dr — Fri, 13 Apr 2012 09:52:53 GMT

Dear Matthew,

Gaurav 's answer is correct ,when the document save screen doesn't leave we have to use back buton for leaving current screen.İf you have any suggestion please share wtih me .

Re: about screen

matt — Fri, 13 Apr 2012 10:05:35 GMT

No. Gaurav isn't telling you to press the back button, he's telling you the ABAP command that if added to a transaction will leave the screen entirely. it's usually the command implemented by the back button.

Your requirement, if I understand it, is for ALL transactions to leave the screen when save is pressed. If that is your requirement, then I'm afraid SAP doesn't work like that, and there is no practical, general solution.

Re: about screen

as_dr — Fri, 13 Apr 2012 10:30:43 GMT

Dear Matthew,

Ok.I understand you. But if I don't want to use back buton for leaving the screen LEAVE programme is solution or not?

Re: about screen

matt — Fri, 13 Apr 2012 13:37:11 GMT

To use LEAVE PROGRAM, you'll have to modify the program behind VA01 (for example), and add the command at the right place for it to take effect. I.e. it's non-trivial and the solution for each transaction may well be different.

I'm pretty sure whoever came up with this requirement doesn't want the expense of modifying all standard transactions in your system. It's probably cheaper to train your staff...

Maybe though, there is another solution - but we can only determinet at if you can explain why this requirement exists? What is it that the users are doing that you don't want them to do?