topic Re: Call transaction error(?) in Application Development and Automation Discussions

Call transaction error(?)

Former Member — Tue, 10 Feb 2009 08:43:02 GMT

Hi all,

I have used call transaction in batch program as follows:

CALL TRANSACTION 'VA02' USING bdcdata MODE mod
                        MESSAGES INTO messtab           .

My problem is that when this is run in debugging mode, it works, no problem, but when

i have run it directly it does not update some of the orders data.

What could be the problem?

Note: I have tried to use; commit work and also commit work and wait commands after call transaciton but it did not work properly; updated some and did not update other some.

Under debug everything is ok.

Thanks.

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 08:46:46 GMT

Hi,

try using update 'S' ( synchronous update ).

CALL TRANSACTION 'VA02' USING bdcdata MODE mod

MESSAGES INTO messtab update 'S'.

thanks.

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 08:48:56 GMT

Hi ,

One reason can be the entries in the table BDCDATA , may not be sufficient , what might be happening is that during debugging you might be pressing the Enter key or some other key which result in the record to be created , but in the direct execution the step is missing and hence the record is not created .

So what i would suggets is please check the recording again.

Regards

Arun

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 08:50:07 GMT

Add UPDATE 'S' to your CALL TRANSACTION command.

Regards

Sathar

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 09:00:28 GMT

Hi,

Try this way..

opt-dismode = 'N'. 
opt-defsize = 'X'. 
opt-racommit = 'X'.
opt-updmode ='S'.
CALL TRANSACTION 'VA02' USING bdcdata OPTIONS FROM opt
MESSAGES INTO itab

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 09:13:58 GMT

Hi,

from you are call transaction syntax update A/S/L is missing

like call transaction 'tcode' using bdcdata mode A/E/N update A/S/L messages into bdcmsgcoll.

Choose the update mode:

A : Asynchronous update

S : Synchronous update

L : Local update

add the update mode check once in debugg mode and mode a/e/n

Regards,

Madhu

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 11:27:42 GMT

You want to mention update type in this statement.

CALL TRANSACTION 'VA02'

USING bdcdata

MODE mod

update c_s " (Synchronous Update Type)

MESSAGES INTO messtab.

Regards,

Joan

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 12:06:03 GMT

Hi,

Check the below syntax ,

Call Transaction u2018Transaction Nameu2019 using BDCDATA

MODE u2018Nu2019 or u2018Au2019 or u2018Eu2019

UPDATE u2018Su2019 or u2018Au2019 or u2018Lu2019

MESSAGES into ITAB.

Regards,

Anki Reddy

Re: Call transaction error(?)

Former Member — Tue, 10 Feb 2009 12:17:34 GMT

Hi Deniz,

Try using below syntax for clling transaction:

CALL TRANSACTION 'VA02' USING bdcdata MODE mod UPDATE upd
                        MESSAGES INTO messtab

Mode should be 'N' [run in background i.e. without screens] and Update should be 'A' i.e. Asynchronous, so if in mid of transaction you exit then nothing will be updated.

I don't think so you need to call commit transaction BAPI after BDC as through BDC you are directly saving the data as per your recording. If still you are facing the same problem then please check your recording and process it in background [Click 'Process' button]. Check if still if gives you same issue i.e. data not saved for few orders. If still same prb persists then there is no fault in your program, just that do the recording again.

Regards,

Saba