cancel
Showing results for 
Search instead for 
Did you mean: 

Idoc with crazy content: "&" -> Entity Reference must end on ;

Former Member
0 Kudos

Hello,

this is our issue:

An R/3 sends per Idoc INVOIC containing this:

.....

After eliminating the "&" the message could be successfully processed starting in test mode from RWB.

But as we mentioned a few idocs containing the & passed the XI successfully too!

So, how can this be explained?

Any help is appreciated!

Best regards

Dirk

Accepted Solutions (0)

Answers (3)

Answers (3)

bhavesh_kantilal
Active Contributor
0 Kudos

Dirk,

Adding to stefan, as you are testing the call from the RWB 's test tool, you would need to manually change the & to & amp ; ( without the spaces ) .

In a real time case, if it is a valid XML internally & will be escaped as above. But from RWB you need to do this manually in the payload.

Regards

Bhavesh

bhavesh_kantilal
Active Contributor
0 Kudos

Dirk,

Adding to stefan, as you are testing the call from the RWB 's test tool, you would need to manually change the & to & amp ; ( without the spaces ) .

In a real time case, if it is a valid XML internally & will be escaped as above. But from RWB you need to do this manually in the payload.

Regards

Bhavesh

stefan_grube
Active Contributor
0 Kudos

& is not allowed in XML besides starting an escape sequence which end with ;

There seems to be an issue with the IDOC adapter, as the & should be escaped.

What SP version do you use?

Regards

Stefan

Former Member
0 Kudos

Hello Stefan,

thank you for this hint!

We are on SP19 of XI 3.0.

And unfortunately we have this issue with the "&" in the regular communication with an R/3 system for Idocs sent to our XI !

Best regards

Dirk

Former Member
0 Kudos

Hello again,

today we have sent a message which was running on error before without any "&".

Looks like we were wrong with our idea.

Same message runs on error again!

And we are on this error message from ABAP Mapping now:

Error in mapping program Y_X02_IDOC_TO_FLAT (Type SAP-ABAP, Kernel Error Id UNCAUGHT_EXCEPTION) An Exception of type CX_SY_CREATE_DATA_ERROR has been triggered, but was not considered locally or declared by a RAISING-clause. The data object of type C could not be generated: Not permitted values for LENGTH.

Looks like there is something wrong with the Mapping program.

So we have to check on our own now!

Thank you for your help!

Regards

Dirk

stefan_grube
Active Contributor
0 Kudos

Hi Dirk,

There is one note concerning unallowed characters in IDoc XML: Note 1004368.

The note deals with non-printable signs, maybe this happens in your IDos as well.

Regards

Stefan