Skip to Content
avatar image
Former Member

Why is the RFC Adapter so unstable

Hi all,

I have a scenario where an IDOC is sent from the sender system and an RFC enabled Function Module is called on the target system. Sometimes I get an error in the Adapter for no aparent reason. I check the RFC adapter trace file but none of the exceptions was raised and I am not able to see what was the problem.

But, if I restart the RFC Adapter and send the IDOC again, everything's allright. Why? Is there any other trace avilable somewhere? Is there any way to restart the RFC Adapter periodically and automatically?

Thanks and regards,

Nuno

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 14, 2004 at 01:08 AM

    This sounds like a bizarre scenario. Why would a Idoc (asynchronous) be calling an RFC (synchronous)?

    Unless the RFC is doing update? Then you have more problems. You are mixing your QoS from EO to BE. The delivery is no longer guaranteed. The posting to the RFC could work but XI may not get the acknowledgement - RFC adapter does not do commit so you must have a commit in the remote function. If no acknowledgement is received, do you resend and risk duplicate updates? How do you guarantee EO delivery? The sender system is right in expecting EO for it's outbound Idoc.

    In all the training material RFC is intended for data retrieval, not data posting. This is consistently done with Idoc (EO, or EOIO).

    I would consider changing the scenario to Idoc->xi->Idoc.

    Add comment
    10|10000 characters needed characters exceeded