topic Re: error in call transaction in Application Development and Automation Discussions

error in call transaction

Former Member — Thu, 27 Apr 2006 07:15:27 GMT

hi guyz!

hope this post finds u all at a gr8 mood. ok, in my BDC program, i am using call transaction method with mode as 'N'- no display and UPDATE -'S' i.e, synchronous. so my question is, lets say in my internal table, there are 10 records. if there is a error record at index 5, then will call transaction, this time will skip that record and continue processing from 6th record. looking forward for some honest answer.

best regards

Manas

Re: error in call transaction

Former Member — Thu, 27 Apr 2006 07:21:14 GMT

HI Manas,

if the mode is 'N' then it skips the fifth record(error Record) and process the next record irrespective whether update is 'S'(synchronous) or 'A'. But if the Mode is 'E' then it stops at the fifth record at the place where the error exists.

Regards,

Santosh

Re: error in call transaction

Former Member — Thu, 27 Apr 2006 07:22:59 GMT

call transaction will fail for the 5th one and continue with next record.

Regards

vijay

Re: error in call transaction

Former Member — Thu, 27 Apr 2006 07:23:38 GMT

Hi manas,

1. In this case, it will skip 5th,

and continue further.

2. thats the reason there are different modes

made available.

E = Display of screens only if an error occurs

A = Processing with display of screens

N =

Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-msgid contains "00", sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".

P =

Processing without display of the screens. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger

Others = Like A

regards,

amit m.

Re: error in call transaction

vinod_gunaware2 — Thu, 27 Apr 2006 07:23:49 GMT

Change mode 'A' Or trap error messaage.

and check it out.

regards

vinod

Re: error in call transaction

Former Member — Thu, 27 Apr 2006 07:24:17 GMT

Yes,

You are correct. When you in Background Mode the call transaction skips the current errorenous record and continue processing. The Error messages along with any kind of message during execution, are captured in BDCMSGCOLL internal table and you have to create the table to capture those along with MODE & UPDATE. Syntax is .

DATA : i_messtab LIKE bdcmsgcoll occurs 0 with header line.

CALL TRANSACTION TCODE USING i_bdcdata

MODE p_mode

UPDATE p_upd

MESSAGES INTO i_messtab.

While executing BDC in MODE = E. The BDC execution stops when an Error is encounter during execution. When you press ENTER the execution continues till the loop ends.

In MODE = A, All screens of that transaction are visible and yu have to proceed manually with the OKCODE window appearing.

Reagrds

Rohit

PS: Please Mark points

Re: error in call transaction

Former Member — Thu, 27 Apr 2006 07:25:00 GMT

Hi,

Call transaction will continue with 6th record.

Regards,

Tanveer.

Mark helpful answers

Re: error in call transaction

Former Member — Thu, 27 Apr 2006 07:29:04 GMT

hey guyz!

thnx a lot for ur effective and earliest reply. solved my purpose.

thnx

manas