com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchExcept

[Former Member]

Hi experts,

I Sent a interface RFC->Third Party.

In SM58 transaction the status error is

com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchExcept

Thanks for any information.

Diego Bortolucci

[Former Member · Accepted solution]

Hi Diego Bortolucci ,

Please let me know the scenario and the parameter you maintained in SM58.

Thanks

Gopal

[Former Member · Accepted solution]

Hi Gopal krishnan,

My message Interface is Inbound - Asynchronous.

I sent the message by SE37 transaction using the RFC.

RFC -> Third Party (Legacy System).

Parameters in SM58: Period and User name.

Thanks,

Diego Bortolucci

[moorthy · Accepted solution]

HI,

SO your scenario is RFC->XI->ThirdParty right ?

Did you configure RFC sender Adapter in XI ?

Check out all the configurations like SM58 entries etc in the SAP R/3 or any SAP application System.

To know about Sender RFC adapter configuration-/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

Regards,

Moorthy

[Former Member · Accepted solution]

HI,

SO your scenario is RFC->XI->ThirdParty right ?

Yes RFC -> XI -> ThirdParty

Did you configure RFC sender Adapter in XI ?

This problem occurs in QAS environment, in DEV environment is OK.

Check out all the configurations like SM58 entries etc in the SAP R/3 or any SAP application System.

My SM59 is configured equal this blog

Thanks,

Diego Bortolucci

[moorthy · Accepted solution]

Is QA Business System is pointing to correct R/3 system ?

And all logon parameters for RFC sender adapter is correct ?

Did you get this error in SM58 of R/3 system ?

Make CPA Cache Refresh.

Or try out restarting the RFC Adpater from j2EE engine.

Regards,

Moorthy

[Former Member · Accepted solution]

Moorthy,

Thanks, You solved my problem.

1 - I Restarted the RFC Adapter.

2 - I had two Communication Channel for Interface, I Deleted one.

3 - I Stoped and Started the service.

[Former Member · Accepted solution]

Moorthy,

We have the same problem as Diego had. In our case, we have an scenario with BPM, FILE --> XI --> IDOC.

In the BPM before calling an IDOC, we must check the data in SAP ECC through an RFC call to a BAPI. If the BAPI (which validates data in a business way) returns OK then the IDOC is sent. To invoke the BAPI, we applied a Wrapper approach to avoid time up errors. Here we use correlation.

So we invoke an RFC (ZFI_0044), that invokes the validating BAPI, and at the end the RFC (ZFI_0044) invokes another function module (ZFI_0045) to tell the BPM step in XI that the validation was ok or not.

The problem with had is that RFC calls (ZFI_0045) from SAP ECC to XI seems not to be received by XI, or not understand by the BPM instance. The symptoms are:

the BPM keeps waiting and SM58 in SAP ECC shows the error:

Commit fault: com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchExcept

Any ideas or suggestions?

Thanks in advance.

XIRookie.

[henrique_pinto · Accepted solution]

xi rookie, please create a new thread with ur question.

Regards,

Henrique.

[Former Member · Accepted solution]

Patricio,

You cannot use one same Program Id for some Communication Channels active.

Saludos,

[Former Member · Accepted solution]

What error appears in Runtime Workbench - Communication Channel Monitoring?

The complete error appears in this tool.

Thanks,

Diego Bortolucci