Tracking jco called rfc message

[Former Member]

Hi,

is it possible tracking when it called rfc (with jco) if it succesfull or not using with message monitor?

Thanks

[jamie_cawley · Accepted solution]

You could, but you would be adding a bunch of unnecessary layers. Why not just use the logs or create you own logging mechanism?

Jamie

[Former Member · Accepted solution]

jamie,

I ask this subject because we are on doing some workshop for a customer.

They asked me this question. I told them to study.

How can it be done? Thanks.

[Former Member · Accepted solution]

It is possible but its a fire and forget scenario. You can submit a message via http post and map the message with a rule to run a blt to call your bapi. If the bapi fails you can use the terminate action to set the message status to failed.

[jamie_cawley · Accepted solution]

The message monitor is only used for the listeners, idoc or rfc, not jco calls. The listeners are connected to an rfc destintation within ecc and the monitor will display any message sent via this connection to MII. To answer your question, you could setup a wrapper bapi that would send the success/failed message back to mii using an rfc destination, but this would be pointless and a waste of effort. As the others have mentioned, when you call a function with jco you should check the success and then the return table for errors. Go to the downloads section and download the modules libraries for examples.

Jamie

[Former Member]

There is a sucess flag when u call RFC using jCO from a transaction...i guess you can use that.

[agentry_src]

Remember that the success flag can mean the RFC performed its function correctly or it can simply mean that a good connection was made to the ERP system. You need to characterize the behavior of each BAPI, or if you know ABAP read the code to determine which case applies.

Mike