topic Re: Error with call transaction in Application Development and Automation Discussions

Error with call transaction

Former Member — Thu, 29 Nov 2007 15:47:23 GMT

Hi,

I developed the FM for idoc Z over the transaction deliveries VL01. At the first, in the FM read the data segments of the idoc, then it make a "call transaction" over the transaction.

CALL TRANSACTION 'VL01' USING bdcdata

MODE v_mode

UPDATE 'S'

MESSAGES INTO messtab.

the FM takes 2 years of operation ok. During the last week, in the system have appeared Idoc with status wrong, because after running the "call transaction" the table "messtab" is empty and the value of sy-subrc is 0, therefore the idoc status is 51.

Does anyone because it happens with the call transaction?

Thanks in advantage

Re: Error with call transaction

Former Member — Thu, 29 Nov 2007 15:52:13 GMT

Hi!

Set the MODE to 'A' to step-by-step, or 'E' to stop-at-error mode processing. With this you will be able to find the error.

Regards

Tamá

Re: Error with call transaction

former_member194669 — Thu, 29 Nov 2007 15:53:32 GMT

Hi,

Instead of check for sy-subrc = 0 please check


read table messtab with key msgty = 'E'.
if sy-subrc eq 0.
  move '51' to idoc_status-status.
endif.

a®

Re: Error with call transaction

Former Member — Thu, 29 Nov 2007 16:41:36 GMT

Hi,

The error only happen in sometimes, in fact, when I made a debbuging over the call transaction the result was ok.

The problem is that the table messtab is empty, without message the errors neither message of confirmation; like if the call transaction not executed the operation.

Regards,

ARF