cancel
Showing results for 
Search instead for 
Did you mean: 

RFC lookup in mapping in error because of "Ampersand" (&)

Robert_d_Hoedt
Explorer
0 Kudos

Hi.

In PI we do a mapping with an RFC Lookup. The RFC we call is BAPI_PO_GET_DETAIL.

In some cases the PO contains a product where the short text contains an &. (like M & M, or Cheese & Onion)

I am not using the short text at all. It is not even visible in the mapping test (if i do display queue for the RFC lookup), but the & gets pulled in to PI and therefore the mapping is incomplete.

The error message is like: "....The entity name must immediately follow the '&' in the entity reference.

See error logs for details...."

How can i avoid the Ampersand?

Is it possible to do something in the RFC communication channel maybe?

Regards

Robert

Accepted Solutions (0)

Answers (2)

Answers (2)

Robert_d_Hoedt
Explorer
0 Kudos

Hi Jens,

Thx. This will almost certainly solve my issue, as we are indeed since 1 week on SP 24+.

I'll ask our Basisteam to apply the fix and will let you know the result.

Regards

Robert

JaySchwendemann
Active Contributor
0 Kudos

I would have said it is not an issue by RFC but by SOAP as Ampersand is of course a reserved character in XML, but then I read https://launchpad.support.sap.com/#/notes/3226758.

Do you happen to be on SP24+?