2007 Mar 21 4:03 AM
is there any other method to trace the error in the BDC-CALL TRANSACTION without using BDCMSGCOLL structure.
is there any other method to trace the error in the BDC-CALL TRANSACTION without using BDCMSGCOLL structure.
2007 Mar 21 4:11 AM
Hi Krisna Rao,
U can call the Seesion Method when the call transaction fails,
where u can find which records are not updated successfully by going to sm35.
With Regards
BHASKAR RAO.M
2007 Mar 21 4:12 AM
Hi Krisna Rao,
U can call the Seesion Method when the call transaction fails,
where u can find which records are not updated successfully by going to sm35.
With Regards
BHASKAR RAO.M
2007 Mar 21 6:25 AM
Krishna,
You can do.
After call transaction
Check sy-subrc .
If sy-subrc is not equal to 0 move that record to internal table .
Pls. reward if useful
2007 Mar 21 6:30 AM
Hi Krishna,
Through FORMAT_MESSAGE function module.
OR when ever error will be encountered then session will run. Mkae coding like that.
Hope this helps you. Rply for any queries,
Regards,
Kumar.
2007 Mar 22 6:48 PM
Hi Krishna
As said by Laxman above, just use the function module 'FORMAT_MESSAGE'.
Be sure that you uncomment all the exporting parameters, and declare the imorting parameter as TYPE T100-TEXT.
U will get the message text in the importing parameter.
Reward points if helpful
Regards
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |