09-01-2006 10:43 AM
Hi all,
I'm using a BDC call transaction to perform a remote call on a custom transaction. My BDC table is populated properly and I'm able to get past the initial selection screen.
Unfortunately, once I get into the main screen of the program, the process just stops and I am left in the main screen of the program I called. This happens no matter what mode I use for my call transaction parameter.
Funny thing is, there isnt even an error message. I'm just taken to the main screen and left there. Any ideas why?
09-01-2006 10:47 AM
it seems that yo don't have correct ok_code for second screen implemented in your bdc. Please check that.
BR, JAcek
09-01-2006 10:50 AM
I think you have not used correct OK_CODE for that screen.
I suggest U do recording and then try.
recording is the best Option to such problems .
regards
Atul
09-01-2006 10:52 AM
Hi,
Check your recording you might have missed the screen sequence, by the way which transaction were you rying to write call transaction for?
09-01-2006 10:59 AM
Hi,
Is the custom transaction working fine online?
Are the OK_Codes properly set for the screen?
Regards
09-02-2006 7:19 AM
The OK_CODE is correct since I have used a BDC Recording to find out the neccessary values in the first place. The custom transaction works fine online.
It's a standard screen from IW51 with a completely different interface and an action box attached. I know how to trigger the action box once the user hits save... the problem is, i can't get the transaction to go into 'Save' mode. It just enters the main screen an stops there.