Skip to Content

IDOC_ERROR_PARSE_FAILURE; state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0

Hello Experts,

I have created the mapping for 1 idoc to N idocs scenario. In the target structure, the occurrences for the iDOC node has been updated as "0..unbounded" to create the multiple idocs.

The Message mapping and Operation mapping are working fine. It creates the multiple idocs based on the conditions.

But, during the testing from PI to ECC using Send Test Message, the below error is appearing,

Kindly help me to fix this issue.

------------------------------------------------------------------------------------------------------------------------------------------------------

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not available. See cause exception for details: state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0

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: The metadata for the parsed IDoc was not available. See cause exception for details: state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0

Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not available. See cause exception for details: state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0

Transmitting the message to endpoint <local> using connection AFW failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not available. See cause exception for details: state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0

Many Thanks

MP

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Jan 07 at 08:00 PM

    Hello Experts,

    Few more details regarding the mapping. As per the below blog, the IDOC occurance has been updated.

    https://blogs.sap.com/2005/12/04/xi-idoc-bundling-the-trick-with-the-occurance-change/

    Please note, this mapping used the custom idoc in the source as well as target.

    Kindly provide your suggetions if any to fix this issue.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 22 at 07:17 PM

    Hello Melchior,

    Please check the following , if they are in place -

    1. In you PI system NWA check the IDOc metadata is loaded for this IDOC type with extension.

    2. In your mapping map all the SEGMENT and BEGIN tags with a constant 1. The Java IDoc adapter requires this to interpret the IDoc XML, blank constant will throw an error.

    Please check the images attached.

    Thanks

    Sugata

    metadata-load.png

    nwa-metadata.png


    metadata-load.png (58.6 kB)
    nwa-metadata.png (76.7 kB)
    Add comment
    10|10000 characters needed characters exceeded