topic Re: Call transaction in Application Development and Automation Discussions

Call transaction

Former Member — Fri, 06 Jan 2006 09:13:46 GMT

Hi,

I used the command below:

Call transaction tcode USING i_bdc_tab MODE 'N' MESSAGES INTO MESSTAB.

and it returned an sy-subrc = 1001. What does it(sy-subrc = 1001) mean?

Re: Call transaction

Former Member — Fri, 06 Jan 2006 09:16:54 GMT

If the MODE addition is omitted, then the processing mode is 'A'.

If a screen is displayed in processing mode 'E' because the system reached the end of the BDC data, the system automatically switches to processing mode 'A'.

If breakpoints are set in a transaction tcod called using the CALL TRANSACTION tcod USING itab variant, these are not actually reached in 'N' mode. The system tries to insert data in the Debugger screen; the call ends with SY-SUBRC = 1001 and the message "Batch input data is not available for screen SAPMSSY3 0131" (S 00 344).

Message was edited by: chandrasekhar jagarlamudi

Re: Call transaction

Former Member — Fri, 06 Jan 2006 09:20:16 GMT

Hi Joseph,

1. First try with just :

Call transaction tcode

2. If that works fine, then try with :

transaction tcode USING i_bdc_tab

3. If there is error here,

then, the BDC data must be problematic.

4. 1001 - never encountered such sy-subrc,

hence difficult to say the exact error.

regards,

amit m.

Re: Call transaction

suresh_datti — Fri, 06 Jan 2006 09:22:41 GMT

Hi Joseph,

It is a Batch Input error.What Transaction are you using? Change the MODE to 'E' and look for the contents of the error messsage in your MESSTAB. BTW are you in de-bug mode?

Regards,

Suresh Datti

Re: Call transaction

Former Member — Fri, 06 Jan 2006 09:25:18 GMT

hi,

I have observed the same when i was working with MM01 transaction.

Sy-subrc = 1001 when i got a message of type 'S' which says Material No. is automatically generated". But this is not an error message ( type E).

Regards,

Sailaja.

Re: Call transaction

Former Member — Fri, 06 Jan 2006 09:26:44 GMT

Hi Joseph,

There might be some popup screen which is being called in between. Since you have not handled that screen in your recording that transaction is giving return code as '1001'. When you process this in A or E mode that screen gets suppressed so everything goes fine.

Also,m see this link..it might prove handy

<a href="http://www.sapfans.com/forums/viewtopic.php?t=53781&highlight=1001">sy-subrc = 1001</a>

Regards,

Raj

Message was edited by: Rajasekhar Dinavahi

Re: Call transaction

Former Member — Fri, 06 Jan 2006 09:30:15 GMT

Hi,

In background some times it will give, but nothing is wrong with your code.

check the below thread

thanks

vijay

Message was edited by: Vijay Babu Dudla

Re: Call transaction

Former Member — Fri, 06 Jan 2006 10:00:10 GMT

Hi,

Instead of checking for if sy-subrc = 0 or not

better go for

read table msgcol with key msgty = E'.

If sy-subrc <> 0 .

If it is not error message, anywayz we can proceed.

Regards,

Sailaja.

Re: Call transaction

Former Member — Fri, 06 Jan 2006 10:07:55 GMT

Hi,

Is there any difference on Im in debug mode and not?

Thanks!!!

Re: Call transaction

suresh_datti — Fri, 06 Jan 2006 10:11:57 GMT

Yes, you might get this message in De-bug even if the code is OK and the program runs fine when not in de-bug mode. This is normal and have seen it happen.

Suresh

Re: Call transaction

Former Member — Fri, 06 Jan 2006 10:14:37 GMT

Hi,

Did you checked in debug mode what is happening.

there is no problem at all with the logic developed by you. you can proceed.

check this thread..

thanks

vijay

Message was edited by: Vijay Babu Dudla

Re: Call transaction

Former Member — Fri, 06 Jan 2006 10:57:22 GMT

if you get the sy-subrc 1001. it means the call transaction was not successfull and i am sure it the problem with ur ur bdctab it is not populated according to the recording or there must b a problem in the recording itself.

regards,

Lakshmikanth