Receiver RFC adapter Encoding Issue

[former_member187563]

Hello,

I have a SOAP to RFC synchronous scenario in PI 7.1.

At the receiver end a RFC is called and response is sent back to PI using the RFC adapter.

The interface was working fine, but the message started failing in QA and Prod with the below error from some time:

Received XI System Error. ErrorCode: EXCEPTION_DURING_EXECUTE ErrorText: null ErrorStack: Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ECC_ZBAPI_FLASH_SLSDETLS_INTERF~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Character reference "&#00" is an invalid XML character.

On analyzing it was found, there are some special characters in the RFC response XML and it is failing in PI response mapping. This issue gets resolved if a java mapping is used for cleansing the data.

But can you guys help in understanding how this issue might have occurred all of a sudden. Is there any unicode - non unicode setting which can be updated in PI or ECC to avoid this error. The encoding in RFC response seems to be UTF-16, while PI expects UTF-8.

Is there any setting we can do in the RFC.

Please give your suggestions, it will be really helpful.

Regards,

Ujjwal Kumar

[former_member229310]

Hello Ujjwal,

This could be the content of the response that is being sent from SAP.  Would be easier if you could reach abaper and get to know what kind of values are being sent on the response parameters.

Hope is useful.

[former_member186851]

Hello Ujjawal,

Firstly find out what exactly in the data(which special character) which is causing the issue?

[JaySchwendemann]

Please check the following:

1. Go to your PI System SM59 and check the Destination to your receiver ABAP system.

2. Do a unicode test

3. If its unicode, adjust MDMP & Unicode Tab accordingly

4. In the receiver RFC Channel in PI there's AFAIK no setting to specify unicode. That's specific to sender RFC channel, so no need to adjust (stand me corected, if I'm wrong)

5. How could that happen all of a sudden: Your sender is a third party, right? You basically have no control of the data being sent, so this sort of things, while unlikely could happen to you if the sender changes something in the payload. Probably you will be safest off, using the  already said Java mapping to eleminate the special characters

<update to 5.>

If the error only occurs on the response of the RFC then your third party sender is not the problem.

Cheers

Jens

[former_member187563]

Thanks for the reply.

But since its a receiver RFC adapter. It does not use any RFC destination. Do we have some standard RFC destination from PI to ECC system or SAP JCo is used for this connectivity.

If any RFC destination exists then - "3. If its unicode, adjust MDMP & Unicode Tab accordingly" - It should be set to Unicode right ?

You are correct in Receiver RFC channel, there is no Unicode settings available.

Regards,

Ujjwal Kumar

[former_member182412]

Hi Ujwal,

Check these sap notes

1764915 - Non-Unicode Support for RFC Adapter

1849382 - Codepage mismatch between the PI RFC channel and the registered RFC server program

1775434 - invalid XML character received by RFC Sender Adapter

Check also question 27 in this sap note 730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter

Regards,

Praveen.