06-18-2007 7:01 AM
Hi,
can we see the errors in call transaction in session method?
regards,
phani.
06-18-2007 7:02 AM
06-18-2007 7:02 AM
06-18-2007 7:03 AM
06-18-2007 7:05 AM
Yes u can see,
in call transcation u have to use BDCMSGCOLL check in call transcation syntax.
in Session u will get the errors in SM35 it self.
regards
prabhu
reward if it is helpful.
06-18-2007 7:17 AM
hi,
in both cases we can see.
<b>sesion method.</b>
in session method system defaultly provide log for handling error records, for that one.
goto SM35-->select your SESSION NAME-> and choose LOG file tab and click--->then it displays log file with error records.
<b>in Call transaction</b>
in Call transaction we can explicitly provide logic for handling error records, for that one we create internal table of type <b>BDCMSGCOLL</b>.
this table holds error records.
call transaction <transaction-name> using <bdcdata>
mode <E/A/N>
update <S/A/L>
MESSAGES INTO <bdcmsgcoll>.
<b>another way of handling error records in call transaction method.</b>
while working with call transaction if sy-subrc = 0( if any error records are found) then create session for handling error records. for that one we use session method function modules.
and follow these steps to see the error records.
goto SM35-->select your SESSION NAME-> and choose LOG file tab and click--->then it displays log file with error records.
regards,
Ashokreddy.
06-18-2007 7:32 AM
Hi Phani,
In call transaction, you can handle error messages using FM : FORMAT_MESSAGE to display message text.
In BDC, you can handle the same using BDC_MSGCOLL.
Reward Points if it is helpful
Thanks.
hari krishna.