Reading Log

[Former Member]

Is it possible to identify my BDC inputs (key fields that I provide on screen) during failed BDC transaction (bdc Session) from the Session Log programmatically? I can use the std. FMs RSTS* to get the error messages, but how do I link this error messages to the specific input I had provided?

Thanks

[Former Member]

I don't think that is possible.

[Former Member]

Thanks Srini!!! Thatz what I thought so too

I have to use BDC session and I have to track errors by my inputs, Is there any possible way to do this?

[RichHeilman]

maybe you could use BDC call transaction in a custom program, the use the MESSAGES into itab extension of CALL TRANSACTION, after execution, write the parameters and the messages to a message itab. At the end of processing show the message itab in ALV grid for the user.

Regards,

Rich Heilman

[Former Member]

I will be invoking bdc using update task and can't do call transaction

[RichHeilman]

Then, I would say that there is <b>no easy way</b> to accomplish what you want. Notice that I didn't say that it was impossible.

Regards,

Rich Heilman

[Former Member]

Look at program RSBDCCTU. Basically this is what is used in SM35. The logic is, you get all the APQI-GROUPID and QID for the errored transactions. Then with each GROUPID, QID combination, you will open that particular transaction using BDC_RECORD_OPEN. This will give you an internal table called TRANSACTIONS. Loop through this table, and call BDC_RECORD_GET using the transaction index. That will give you the BDC screen data that you originally passed. Now you need to parse through that information to find out which field has which value for a failed transaction.

Hope this helps,

Srinivas

[Former Member]

Thanks Srini/ Rich.. Exactly the answer i was afraid of.. And logically I don't think we can expect any thing more ...