CALL TRANSACTION

[Former Member]

HI experts, im lost with something, in this code:

CALL TRANSACTION 'ML81N'

USING i_bdcdata

options from tran_opts.

"Commit para el workflow

wf_id = v_work.

CALL FUNCTION 'ZFMADENDUM_COMMIT'

EXPORTING

wi_id = wf_i

After the call transaction is called, the next "call function" statement is not executed, ¿Do I have to change something in the bdc_opstions to make it return? or it's just automatic, I found that the "call transaction" statement returns the control to the calling program, but it seems that is not doing it, it may be something in the function, but I'd like to check this doubt with you first.

Thank you. I will return the points...

[former_member188685]

wf_id = v_work.

CALL FUNCTION 'ZFMADENDUM_COMMIT'

EXPORTING

wi_id = wf_i

what is the use of above function module. what is happening inside..?

[Former Member]

1. Is your service entry a loop process?

2. What is the mode you use in BDC?

3. pass on the message tabe to you CALL TRANSACTION? to get the error?

4. Do you have any release statergy for this and you have authorization?

5. If you want to update you custom table with Server number after the call transaction, you can update using commit work.

If the hint is usefulu2026 Say thanks by rewardu2026.

Regards,

Prabhu Rajesh

[Former Member]

Hello Euclides Lopez,

use the CALL TRANSACTION with mode A and check if it is executed properly.

do check the sy-subrc value

if :

0 : Successful

<=1000 : Error in dialog program

if sy-subrc > 1000 : Batch input error

Regards

Indu.

[former_member182371]

Hi,

maybe it has something to do with tran_opts-RACOMMIT.

Try with tran_opts-RACOMMIT = ' '

(RACOMMIT: Do not end transaction at COMMIT WORK ).

Best regards.

Edited by: pablo casamayor on Aug 3, 2008 8:53 PM