topic Re: CALL TRANSACTION error during the initial run in Application Development and Automation Discussions

CALL TRANSACTION error during the initial run

Former Member — Tue, 19 Dec 2006 04:00:14 GMT

Hi,

I have a custom program that calls the transaction FOIO (Change Contract) inside. Here's my sample code:

...

CALL TRANSACTION 'FOIO'.

IF sy-subrc = 0.

ENDIF.

...

The problem is, after the CALL TRANSACTION, it no longer goes back to the custom program to perform the other lines of code. It stays on the last screen of FOIO. I am not sure why this is happening. Maybe the transaction has to be initialized first because the succeeding runs are ok. Does anyone have an idea on how to do this?

Re: CALL TRANSACTION error during the initial run

Former Member — Tue, 19 Dec 2006 04:05:09 GMT

there may not be any Processing codes after you call the Transaction . Hence Program Ends Once it calls the transaction

Re: CALL TRANSACTION error during the initial run

Former Member — Tue, 19 Dec 2006 04:26:31 GMT

good

check out the recording and see wheather all the screens come properly in your recordding,

debug the bdc and check wheather the end OK CODE is firing properly or not,if not than assign the appropriate OK COD for that.

thanks

mrutyun^

Re: CALL TRANSACTION error during the initial run

jayanthi_jayaraman — Tue, 19 Dec 2006 04:26:33 GMT

Hi,

One option is to use Submit command with return.

Otherwise,Try runing the BDC to achieve it.

call transaction 'FOIO' using itab mode 'N' update 'S' messages into i_msg.

Here itab is the internal table you are using to pass entries to BDC.

Mode 'N' means it won't display you screen.

i_msg is the error message internal table.

Kindly reward points by clicking the star on the left of reply,if it helps.

Message was edited by:

Jayanthi Jayaraman