IDOC_ERROR_PARSE_FAILURE

[former_member346123]

Hi Gurus,

  We are on PI 7.4 single stack. while using IDOC adapter having exception in receiver channel 

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDoc-XML for type <MBGMCR02>:
state=READING_FIELD_VALUE_TAG, charPosition=438, lineNumber=1, columnNumber=439

IDoc_AAE adapter seems to be working fine for some of the other messages. Its only for some of the messages that I am getting this error. surprisingly when i processed the message with empty data it was positive also BEGIN and SEGMENT mapped with 1.

Most answers suggested to apply note : 1688780 , however it supported till 7.31 which was mentioned under the note

Validated with all suggested solutions by SCN still no luck. Please clarify why the receiver channel throws this error ? how to fix this?

Receiver IDOC payload from message monitoring :

<?xml version="1.0" encoding="UTF-8"?>

<MBGMCR02><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABNAM></TABNAM><DIRECT>2</DIRECT><IDOCTYP>MBGMCR02</IDOCTYP><MESTYP>MBGMCR</MESTYP><MESCOD>MBI</MESCOD><SNDPOR>A000000002</SNDPOR><SNDPRT>LS</SNDPRT><SNDPFC>LS</SNDPFC><SNDPRN>MBLOCK</SNDPRN><RCVPOR>SAPDE1</RCVPOR><RCVPRT>LS</RCVPRT><RCVPFC>LS</RCVPFC><RCVPRN>DE1CLNT200</RCVPRN></EDI_DC40><E1BP2017_GM_HEAD_01 SEGMENT="1"><PSTNG_DATE>150526</PSTNG_DATE><DOC_DATE>20151129</DOC_DATE><HEADER_TXT>130572047</HEADER_TXT></E1BP2017_GM_HEAD_01><E1BP2017_GM_CODE SEGMENT="1"><GM_CODE>06</GM_CODE></E1BP2017_GM_CODE><E1BP2017_GM_ITEM_CREATE SEGMENT="1"><MATERIAL>119056 </MATERIAL><PLANT>K0016</PLANT><STGE_LOC>06</STGE_LOC><BATCH>1000000000</BATCH><MOVE_TYPE>IM</MOVE_TYPE><ENTRY_QNT>672</ENTRY_QNT><PO_NUMBER>Material C</PO_NUMBER><PO_ITEM>ha</PO_ITEM></E1BP2017_GM_ITEM_CREATE></IDOC></MBGMCR02>

Thanks,

aman

[engswee · Accepted solution]

Hi Aman

The error is because the PSTNG_DATE field is in incorrect format. It has value 150526 but should be in SAP format YYYYMMDD. This is mentioned in the SAP note in the answer to the following thread.

Rgds

Eng Swee

[former_member346123 · Accepted solution]

Thanks Eng for quick reply. I go through scn links and some one suggest to send date in yymmdd format for this issue. However even with YYYYMMDD also having the same issue.

[engswee · Accepted solution]

Your IDoc mapping may have more than one issue caused by validation. Can you post screenshot of the latest error as well as latest payload?

My guess is that it is the same error for a different field, i.e. your PO_ITEM should be numeric with leading zeroes (similar to the thread I mentioned above) but it is having String value "ha".

[former_member346123 · Accepted solution]

PO_ITEM and PO_NUMBER mapped with substring of description field .description coming as some string data(eg: material number).

still getting same idoc parser error

MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDoc-XML for type <MBGMCR02>:
state=READING_FIELD_VALUE_TAG, charPosition=836, lineNumber=1, columnNumber=837

payload:

<?xml version="1.0" encoding="UTF-8"?>

<MBGMCR02><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABNAM></TABNAM><DIRECT>2</DIRECT><IDOCTYP>MBGMCR02</IDOCTYP><MESTYP>MBGMCR</MESTYP><MESCOD>MBI</MESCOD><SNDPOR>A000000002</SNDPOR><SNDPRT>LS</SNDPRT><SNDPFC>LS</SNDPFC><SNDPRN>MBLOCK</SNDPRN><RCVPOR>SAPDE1</RCVPOR><RCVPRT>LS</RCVPRT><RCVPFC>LS</RCVPFC><RCVPRN>DE1CLNT200</RCVPRN></EDI_DC40><E1BP2017_GM_HEAD_01 SEGMENT="1"><PSTNG_DATE>20150526</PSTNG_DATE><DOC_DATE>20151129</DOC_DATE><HEADER_TXT>130572047</HEADER_TXT></E1BP2017_GM_HEAD_01><E1BP2017_GM_CODE SEGMENT="1"><GM_CODE>06</GM_CODE></E1BP2017_GM_CODE><E1BP2017_GM_ITEM_CREATE SEGMENT="1"><MATERIAL>119056 </MATERIAL><PLANT>K0016</PLANT><STGE_LOC>06</STGE_LOC><BATCH>1000000000</BATCH><MOVE_TYPE>IM</MOVE_TYPE><ENTRY_QNT>672</ENTRY_QNT><PO_NUMBER>Material C</PO_NUMBER><PO_ITEM>ha</PO_ITEM></E1BP2017_GM_ITEM_CREATE></IDOC></MBGMCR02>

[engswee · Accepted solution]

My guess is correct, position 836 is related to PO_ITEM field. This needs to be a numeric field with leading zeroes.

Obviously your mapping is wrong, you will need to clarify on the technical spec for the correct mapping. This is something no one on SCN can advise you.

[former_member346123 · Accepted solution]

Functional team has changed the data . They have the logic at DB end to convert char to numeric, however its not sending as numeric value from DB leads failure in PI. Issue resolved with correct data. Thanks.