Skip to Content
avatar image
Former Member

RFC Communication Channel error in SM58


I have a scenario where we have RFC -> XI (BPM) -> SOAP. Currently, this links our SAP QAS system to a non-SAP internal system's QAS environment. However, we now have a new requirement whereby the non-SAP system will have a Training environment set up to run in parallel with its QAS. Any ideas on how I could do this?

I have set up a second Configuration Scenario more or less identical to the original only it points to the Training system. However, when the RFC is triggered I get an exception in SM58 saying 'Commit fault:'.

Searching the forum I see that this is often because there are 2 or more CCs with the same ProgramID. This is not the case for me. I have created 2 distinct RFC Destinations (RFCQAS and RFCTRN) with equally distinct Program IDs (zrfcqas and zrfctrn). The 2 CCs I have set up use the corresponding Program IDs so although I have two RFC Communication Channels they use different ProgIDs. However, the same RFC is used but the Destination parameter is dynamically assigned by the calling ABAP.

Is my only option to create another FM that calls the training system? I hope not because then I'll have to re-create all the mapping objects!



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 23, 2008 at 04:53 PM


    Since only your NON SAP system connectivity needs to be changed, Copy the configuration scenario in ID and create a new scenario. No update the receiver SOAP channels details as per the new end point..!!


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Resolved this by creating copies of the RFC in the QAS system. This uses the same RFC Destination, Program Id and CC as the original. I then had to create the additional IR and ID objects.