01-13-2009 10:14 AM
Hi All,
I have written a BDC for F-37, which is working fine in all screen mode
but not working in "N" mode..
P.S. I have BDC as the only option.
Thanks in advance,
Kalyan Venigalla.
01-13-2009 10:58 AM
If you look at the documentation of CALL TRANSACTION you can pass BDC options which is of type CTU_PARAMS. In this assign 'X' to field 'RACOMMIT' and try to run the BDC in 'N' mode.
DATA: OPT TYPE CTU_PARAMS.
OPT-DISMODE = 'N'.
OPT-UPMODE = 'L'.
OPT-RACOMMIT = 'X'.
CALL TRANSACTION 'F-37' USING BDC_TAB OPTIONS FROM OPT MESSAGES INTO MESSTAB.
Thanks and regards,
S. Chandramouli.
01-13-2009 10:31 AM
What are the messages you get back in your bdc_message_table?
(PS: you don't have a hard/soft breakpoint set? so the bdc in background (mode N )is waiting for input at that stage?
01-13-2009 10:34 AM
HI ,
Do one thing use Mode 'P', insted of 'N'.
u want no screen display
01-13-2009 10:41 AM
HI,
Can you tell me the error thrown by bdc....
Also try using the E mode....
Regards,
Rohan.
01-13-2009 10:58 AM
If you look at the documentation of CALL TRANSACTION you can pass BDC options which is of type CTU_PARAMS. In this assign 'X' to field 'RACOMMIT' and try to run the BDC in 'N' mode.
DATA: OPT TYPE CTU_PARAMS.
OPT-DISMODE = 'N'.
OPT-UPMODE = 'L'.
OPT-RACOMMIT = 'X'.
CALL TRANSACTION 'F-37' USING BDC_TAB OPTIONS FROM OPT MESSAGES INTO MESSTAB.
Thanks and regards,
S. Chandramouli.
01-13-2009 11:01 AM
01-13-2009 11:10 AM
No, this option does not suppress the 'NO SCREEN-FIELD' messages.
The option which I mentioned will be typically useful while doing BDC with transactions VL01N(Delivery), F-58(Check payment) transactions. BDC in these transactions run successfully in All screens mode even without using this option, but fail if it is run in 'N' mode. It does not return the document number generated. In such scenario we can use this option.
Thanks and regards,
S. Chandramouli.
01-13-2009 11:12 AM
01-13-2009 11:00 AM
Thanks for all the responses.
There were no error messages collected in message tab after call transaction.
but there were messages like no screen field, which I thought are just warning messages.
when I cleared those its working fine now.