Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

CALL Transaction Problem

Former Member
0 Likes
859

Hi Guys,

I would like to ask if anyone could help me with my problem with CALL Transaction if I am correct that it's causing this problem. My problem is if I call a transaction and after I process my data in that transaction when I click save it doesnt return to the transactions main screen ( The screen displayed after the CALL transaction in my code ) it returns to my program... How can I fix this? your help will be much appreciated. Thanks!

Regards,

Michael Nacionales

7 REPLIES 7
Read only

Former Member
0 Likes
828

use leave to transaction instead of call transaction

Read only

0 Likes
828

i am passing some data through bdc. I think it wont work

Read only

0 Likes
828

after the call transaction of your BDC.. write Exit or leave program statement to avoid control getting back to the calling program screen...

Read only

0 Likes
828

does it going to return it to the transaction I called?

Read only

0 Likes
828

call transaction will return the control to the calling program once the BDC processing is done...

so when control comes back from the BDC session.. just give EXIT command or Leave Program command so the control will exit from the report as well... and this will avoid displaying the calling program screen after the BDC processing.

Read only

ThomasZloch
Active Contributor
0 Likes
828

Hi,

there is no fix because this is not an error. Processing "Save" (or "Back", "Exit" etc.) at the end of a CALL TRANSACTION will always return to the caller, which can then prepare and call the next transaction, if so desired.

Not sure what you are trying to do, so I cannot recommend a workaround.

Cheers

Thomas

Read only

0 Likes
828

I see, I think this would be my last option if theres no other way... I would just call it again after call transaction.. the problem would just be after that second call transaction if it saves the process again it wont call the transaction again.