Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

iDoc receiver channel - multimapping error

$
0
0

Hi folks,

 

I have an Edifact to iDoc scenario (PO Java single stack 7.31, AF 7.31). This scenario needs a 1:n multimapping. After the mapping is executed (successfully), I get this error message below in the comm. channel monitoring for the iDoc receiver channel:

 

Message-Verarbeitung fehlgeschlagen. Grund: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge

 

The XML structure is absolutely fine, I tested the mapping plenty of times. If I perform the exact same mapping 1:1, it works just fine.

My research lead me to one relevant note:

http://service.sap.com/sap/support/notes/1843122

 

The only difference is I dont actually use binary payloads and such, just a good ole 1:n message mapping. Nevertheless, we are now asking the Basis team to update the AF to the sps and patch level mentioned in this note.

I searched all the threads with this kind of error (IDOC_ERROR_PARSE_FAILURE), none seems to completely describe my problem.

 

Is there maybe something that I'm missing in the iDoc receiver channel that can solve this? This happens for all EDIFACT to iDoc scenarios that involve multi mappings (never for 1:1 mappings).

 

Please let me know if you have any good to very good ideas.

 

Thanks in advance and best regards,

George

 

 


Viewing all articles
Browse latest Browse all 7030

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>