Call Transaction Issue

[Former Member]

Hii

I am using 'Call Transaction' statement in my Program ,I want the user to be directly navigated to a screen (Which is not the second screen ,so i can't use 'Skip first screen') in the transaction.

I do not want to Run 'Call Transaction' in fore ground as the user will have to press 'Enter' on each screen in between.I want to directly navigate the user to that screen & back to the my calling Program.

Regards

Ajitabh Pradhan

[Former Member]

Hii

I am using 'Call Transaction' statement in my Program ,I want the user to be directly navigated to a screen (Which is not the second screen ,so i can't use 'Skip first screen') in the transaction.

I do not want to Run 'Call Transaction' in fore ground as the user will have to press 'Enter' on each screen in between.I want to directly navigate the user to that screen & back to the my calling Program.

Regards

Ajitabh Pradhan

[Former Member]

Hi Ajitab,

I have tried this <b>MBST</b> transation.

You can do it in this way..

Record the screen sequences using <b>SHDB</b> till you want the user input screen. Use CALL TRANSACTION and pass BDCDATA only till this step.. After the user input ( if its the last screen or step of that transaction ), you can come out of the transaction and back to the calling program..

You need to do some R&D if the user input screen is no the last screen.

<b>AS</b>

[Former Member]

Hi

I don't know if it's possible because it depends on the trx.

U can try to create a little BDC working in ERROR mode, so you force an error when the BDC is in that screen. In this way the BDC'll stop as soon as the first error occurs so at your dynpro.

The problem is when the user press BACK to go back, you can't be sure he backs directly to calling program, but perhasp the user has to press BACK several times.

Max