‎2008 Feb 11 7:11 AM
‎2008 Feb 11 7:27 AM
Error handling in call transaction.
The BDCMSGCOLL does not have the messages text. It has only the message type, number and message parameters.
You have to read the message text. (recall that the database table T100 stores all the messages.)
To handle error in bdc call transaction method...without using structure BDCMSGCOLL,
Use Std Function module 'FORMAT_MESSAGE'
If you are using BDC session method and an error occurs, a a session is created in SM35. You can rerun the session in foreground from transaction SM35 after correcting the error.
‎2008 Feb 11 7:27 AM
Error handling in call transaction.
The BDCMSGCOLL does not have the messages text. It has only the message type, number and message parameters.
You have to read the message text. (recall that the database table T100 stores all the messages.)
To handle error in bdc call transaction method...without using structure BDCMSGCOLL,
Use Std Function module 'FORMAT_MESSAGE'
If you are using BDC session method and an error occurs, a a session is created in SM35. You can rerun the session in foreground from transaction SM35 after correcting the error.
‎2008 Feb 11 10:29 AM
hi.
LSMW uses session method and to handle errors occured, a session is created in SM35. You can go thru the error log file to handle the errors and rerun the program.
LSMW dont support call transcation method bezc, it dos not handle errors by implicitly.
Regards,
kavitha.
‎2008 Mar 15 8:31 AM
Thank u very much kavitha madam .
for this answer iam waiting for very long time .
ie.LSMW dont support call transcation method bezc, it dos not handle errors by implicitly.
if u possible can u explain briefly plzzzzzzz ?