Showing results for 
Search instead for 
Did you mean: 

Idoc parsing Error - PI 7.5

Former Member
0 Kudos

Hi All,

We are testing JMS to IDoc interface, getting below error.

Transmitting the message to endpoint <local> using connection AFW failed, due to: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDoc-XML for type <ZELOG>:

state=READING_FIELD_VALUE_TAG, charPosition=739, lineNumber=1, columnNumber=740

It was working fine in PI 7.0 version,but in 7.5 it is throwing error. When we check that character position in input payload it is optional attribute at source.

We faced same problem earlier with other interface, that time we gave 1 in constant field.earlier it was blank constant value. Issue was solved that time and it worked well.

So we followed the same process for this case, It was mapped to target field with blank MapWithDefault node function,So we gave 1 in MapwithDefault ,Issue is not solved this time.. Please let me know if any more details required.

Have anyone faced this kind of issue? and please suggest solution  to solve this issue ..


Jeevitha N

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

please check your target mapping whether it populates 1 for the segment attribute. If not remove the mapwithdefault and use constant (1) value.

Active Contributor
0 Kudos

Hi Jeevitha,

Check the below sap note.

2036878 - IDoc_AAE: Disable field datatype validation during IDoc-XML


The IDoc_AAE adapter uses the SAP Java IDoc Class Library to parse the IDoc-XML to IDoc document/list. The library did not offer the possibility to disable the IDoc document and segment field datatype checks. Based on note 2023782 the IDoc Library is now able to parse the IDoc-XML without checking the fields datatype.

Solution is fix the data type issue or disable the check as mentioned in the note, but take a note below when you disable the check.

If you disable the field datatype check the IDoc_AAE adapter may send IDoc documents with wrong or illegal field contents which may result in an unexpected behavior in the receiver system. Instead of switching off the IDoc field datatype checks it is recommended to correct the data beforehand, ideally already by the original data creator, and only send valid IDoc data according to the IDoc metadata definition.