IDOC_ERROR_PARSE_FAILURE

Hello Team,
   I am doing IDoc - SFTP Flat file scenario using standard module SAP_XI_IDOC/IDOCXmlToFlatConvertor.
   Whenver an Idoc is triggering, I am getting the error in receiver channel :
"MP: exception caught with cause com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: IDoc type within the EDI_DC40 control record segment does not match the IDocXML root tag <SHPMNT05>: state=READING_ENDTAG, charPosition=252, lineNumber=2, columnNumber=214"
   Kindly suggest your valuable inputs.
Thanks
Ravi

Hi Ravi,
Which version you are using if it is SAP PI 7.3
please check below note :#1791798
Once check your input payload message is any wrong data is there in control record.
Thanks,
Sreenivas

Similar Messages

IDOC AAE error:IDOC_ERROR_PARSE_FAILURE

Hello Gurus,
I am facing following error in IDOC AAE channel scenario is SOAP to IDOC we are using Integrated configuration.I have mapped all the attributes in the IDOC to 1 and date formats are fine.On Analsys i found for the IDOC Field MENGE is not accepting Decimal values when the value 868.000 is passed IDOC AAE is failing with following error.
When i pass with out decimal like 868 Idoc is posting successfully.
using connection
File_http://sap.com/xi/XI/System failed, due to:
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 IDocXML for type :state=READING_FIELD_VALUE_TAG,
charPosition=441, lineNumber=1, columnNumber=442" tabIndex=0
ti="0" lsdata="{0:'Transmitting the message to endpoint using
connection File_http://sap.com/xi/XI/System failed, due to: 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 IDocXML for type
:\nstate=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1,
columnNumber=442',7:true}" ct="TV"
bMarkedAsFocussed="true" bResetTabIndex="true"Transmitting
the message to endpoint <local> using connection
File_http://sap.com/xi/XI/System failed, due to: 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 IDocXML for type
<Z2MAK075IDOC>:
state=READING_FIELD_VALUE_TAG, charPosition=441, lineNumber=1, columnNumber=442
I have explored through forum but i didnt find exact solution how decimal values can be handled in IDOC AAE .Please through some light on the issue any help is higly apprecaited.
Regards
Praveen Maareddy

Hi Praveen
Looks like it will not allow dot(.) or comma(,) .
Check this
A numc field will not allow you to post values like '.' or ',' to it. You need to get rid of the decimal point/comma. You can do that by multiplying the value by 100 or 1000... depending on your decimal places. Then it is possible to post that values to a numc field. A numc does allow only the numeric characters from 0 to 9. If this is not what you want (because you are dealing with an characteristic) you need to use a char infoobject or you need to use a keyfigure.
Problem with conversion char to numc in transference rules
You can change the data type of MENGE like below
result TYPE p LENGTH 8 DECIMALS 3.

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
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 IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: 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 IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDocXML:state=READING_SEGMENT_STARTTAG

Hello Experts,
We are getting a strange issue while trying to post IDOC into ECC through PO 7.31 Single Stack.
We are having a custom segment in IDOC with a single field.If we don't create that segment in PO,i.e. if we don't map this segment the IDOC is getting posted.But if we map the custom segment(setting SEGMENT=1),we are getting error "com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDocXML for type <*IDOC_NAME*>:
state=READING_SEGMENT_STARTTAG, charPosition=834, lineNumber=1, columnNumber=835".
I have gone through other discussion in scn related to this exception,but they are not similar to our problem.
Please suggest.
Regards,
Suman

Hi Sunil,
I have re-imported Idoc as many as 10 times,even created separate message and operation mapping,new Idoc receiver channel.But still no luck.
Regards,
Suman

IDOC_ERROR_PARSE_FAILURE READING_FIELD_STARTTAG

Hi all,
I'm having an error in SAP_XI_IDOC/IDOCXmlToFlatConvertor.
Here's the scenario:
1. We have a new IDOC extension. I have imported it in XI and the test was okay. An IDOC text file was generated.
2. Some of the fields of the IDOC extension were changed. I have reimported it in XI. Test is not okay. I'm getting an error message in RWB for the comm channel.
I have seen in the previous posts that their errors are, READING_FIELD_VALUE.. I have no errors in the value of the field. My problem is in the segment name since it was changed recently.
Any ideas?
Thanks!
Regards,
SAPenthusiast

Hi Grzegorz,
I have already done this. It's working in the mapping already. I can view the corrected segments in sxi_monitor already.
Hi Udo,
I have already tried this before. I deleted it also then passed a new test data. The idoc metadata was generated in idx2. i checked the structure of the idoc and it is correct. It has the correct segments. but I'm still having the same error in parsing.

Error in CC while using SAP_XI_IDOC/IDOCXmlToFlatConvertor module

Hi,
We are getting an error in CC monitoring while using SAP_XI_IDOC/IDOCXmlToFlatConvertor module for converting IDoc XML to flat file. Below is the error text:
"Message processing failed. Cause: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZDELVRY3>: state=READING_FIELD_VALUE_TAG, charPosition=7404, lineNumber=2, columnNumber=7366"
Any suggestion how to resolve it.
Regards
Pravesh

Please check the OSS note below and install the mentioned patch accordingly:
[Note 1278687 - Exception in the IDocXMLProcessor (IDOC_ERROR_PARSE_FAILURE)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278687]
If it persists, check if are there any mapping errors on the Audit Logs for the failed message.

Flat Idoc to Idoc XML conversion error.

Hi All,
We are using PI 7.1 EHP1, Where in we would like to see the capabilty of User-Module for Conversion of IDoc Messages Between Flat and XML Formats. Gone thru the below blog and maintained the necessary NWA configurations:
How to Use User-Module for Conversion of IDoc Messages Between Flat and XML Formats
While testing phase, The file is not been picked by the Sender File Adapter and the below error is been displayed in RWB:
"MP: exception caught with cause com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: Invalid character encountered in XML input data source: state=INITIAL, charPosition=0, lineNumber=1, columnNumber=1, invalidChar=U+0045, sourceSnippet=...EDI_DC40 510000000002889077846C 3012 SHPMNT05 ZSHPMNT9 S... ^"
Any Clues?
Thnx

Hi Stefan,
You are right i have maintained the mandatory parameters (SAPRelease, SourceJRA, TargetDestination) within the sender File adapter module key parameters.
Now getting another error within Comm Channel Monitoring:
MP: exception caught with cause java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Any Clues?
Thnx

Issue with IDOC_AAE in PI 7.31

Hi,
i have a file - IDOC_AAE(Receiver) Scenario.We are using PI 7.31.
When we are posting the file we are getting the below error:
IDoc: Error before sending : IDocException com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: Invalid character encountered within IDocXML for type <ORDERS05>: state=READING_ATTRIBUTE_VALUE, charPosition=77, lineNumber=1, columnNumber=78, invalidChar=U+0022, sourceSnippet=...UTF-8" standalone="no"?><ORDERS05><IDOC BEGIN=""><EDI_DC40 SEGMENT=" "><TABNAM>EDI_DC40</TABNAM><DIR... ^
Can anyone help on this issue??

Hi,
Try refreshing the cache in ID. Also, check that you have completed all the steps for the receiver Idoc adapter.
Refer this link for the steps :
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21717
Also, you can try creating a new receiver channel and checking if the problem still persists.
Regards

Error in portlets while using Basic Authentication

We have the Portal on the web.Whenever anyone types the URL for the Portal welcome page he is prompted for a
username and a password(facilitated by the Apache Server security by adding the relevant tag in the httpd.conf file).The following is the tag added in the httpd.conf file:-
<Location /servlet>
AuthName "XXX"
AuthType Basic
AuthUserFile "F:/Oracle9iAS/Apache/Apache/bin/users"
require user kiran
</Location>
For a particular user we have added the Exchange portlet on his home page under a tab.Clicking on this particular tab gives the following error when the security is present.
The following error occurred when attempting to call the
initSession of the Web Provider: exchangeprovider_XXX
ORA-29532: Java call terminated by uncaught Java exception:
java.lang.UnsatisfiedLinkError: no oraawt in
java.library.path
However on removal of the security the same Exchange portlets is displayed without any errors.
Any help on the above would be welcome.
Thanks in advance.
Regds.
Kiran.

Please check the OSS note below and install the mentioned patch accordingly:
[Note 1278687 - Exception in the IDocXMLProcessor (IDOC_ERROR_PARSE_FAILURE)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278687]
If it persists, check if are there any mapping errors on the Audit Logs for the failed message.

Message split on adapter engine for the java based IDoc adapter

Hi Guys,
Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
I'm getting such exception when I try to post 3 IDocs
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: 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"><ns0:Message1><...
^
Mapping is one to many.
Each IDoc content has been compared manually against the xsd schema and it was fine.
I know that old way of modifying xsd is still possible.
Best regards,
Wojciech

Did you find a solution to this? Having a similar error right now.
Thanks and kind regards
Jens

IDOC XML Parsing

Hi Everyone.
I've got some lovely XML IDocs. I'd like to read them into the IDOC Class Library and send them to SAP with JCo..........
But I can't get some simple code to parse the XML. I've been sending XMLs to SAP for a long time and they were always valid in SAP. They are also valid XML.
I also borrowed the code directly out of the JCo documentation, so you'd think it would work.
I'm using Java 6, IDoc Class lib 3.01. I've also tried Java 5. If I could parse the XML I would be using SAP 4.7 and JCo 3.01....
I've used JDOM for creating my XML. I've tried UTF-8 and ISO-8859-1 encoding. The error doesn't change
The error message i get is IDOC_ERROR_PARSE_FAILURE: Invalid charachter encountered in XML input data sourcee: state=EXPECTING_IMMEDIATE_TAG_END, charPosition=48, lineNumber=1, columnNumber=49, invalidChar=U+0053, sourceSnippet=...<?xml version "1.0" encoding="UTF-8"?>....
Heres my function I'm using.
(getRfcConnection is my own helper function to create a RFC Destination)
The rest of it is really just copied + pasted from the documentation.
public static void submitXml(Sap_Pruefziffer sap_pruefziffer, String language,String iDocXML)
    throws JCoException, CS_Rfc_Exception, AbapException, IDocParseException
        JCoDestination destination = getRfcConnection(sap_pruefziffer,language);
        IDocRepository iDocRepository = JCoIDoc.getIDocRepository(destination);
        String tid = destination.createTID();
        IDocFactory iDocFactory = JCoIDoc.getIDocFactory();
        //this would be great for re-implementing the OrderDataFactory
        //although that works just fine
        // a) create new idoc
        /*IDocDocument doc = iDocFactory.createIDocDocument(iDocRepository,"MATMAS02");
        IDocSegment segment = doc.getRootSegment();
        segment = segment.addChild("E1MARAM");
        // and so on. See IDoc Specification .....
        JCoIDoc.send(doc, IDocFactory.IDOC_VERSION_DEFAULT, destination, tid);*/
        // b) use existent xml file
        //get IDOC XML/IDOC Parser
        IDocXMLProcessor processor=iDocFactory.getIDocXMLProcessor();
        //parse the XML/IDOC
        IDocDocumentList iDocList=processor.parse(iDocRepository, iDocXML);//, IDocXMLFormat.SAP_RELEASE_610, IDocXMLProcessor.PARSE_WITH_FIELD_VALUE_CHECKING
        //send the XML/IDOC per RFC (our destination)
        JCoIDoc.send(iDocList, IDocFactory.IDOC_VERSION_DEFAULT, destination, tid);
        //not really sure what this does
        destination.confirmTID(tid);
Thanks for your help in advance
Martin

Hi Martin,
For the XML file processing we have to use XML Parsers, these are bit difficult.
We got the same issue in our project, we written normal java code to parse the xml file.
Do one thing, if the xml file is not big one then take the xml data into a string. parse the string based on characters < and >.
Suppose we have xml data as below
String str = "<emp>employee1</emp>"
You have to get the string between >,<.
Regards,
Lakshmi Prasad.

XML-comments not allowed in IDOC_AAE-Adapter?

Hi,
we have a File to IDOC scenario and are using the IDOC_AAE adapter for sending IDOCs to the SAP system.
In our mapping we have added some comments into the XML-IDOC-structure.
By sending the document to the SAP-system we are getting the following 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: Invalid XML 1.0 character
encountered within IDocXML for type <INVOIC01>:
state=READING_FIELD_STARTTAG, charPosition=872, lineNumber=23, columnNumber=14,
invalidChar=U+0021,
sourceSnippet=...RCY>^~~~<KUNDEUINR>DEXXXXXXX</KUNDEUINR>^~~~<BSART>INVO</BSART>^~~~^~~... ^
The problem seems to be the <!-- - Tag in the structure.
But the ! (U+0021) is a correct XML 1.0 character. I don't know why the IDOC-XML parser throws this exception.
Does anybody have an idea what the problem is?
When we remove the comments the IDOC could be sent successfully to the SAP system.
Are only IDOC-specific characters allowed here, no comments and no other XML-specific characters and structures?
This would be very strange.
Thanks for your answer.
Regards
Thorsten

Hi Anoop / Ilayarajan,
Could you please post the solution for this error. When I provision a user to PeopleSoft, I am getting similar error: com.waveset.util.WavesetException: An error occurred adding user "userID' to resource 'PeopleSoft Component Interface'. com.waveset.util.XmlParseException: XML Error: 1:1: Content is not allowed in prolog.
Thanks
User_idm

1120 Error in CC 2014

I am using the exact same fla and as in Flash 6, CC, and CC 2014 to run an Away3D-based program. It works without a hitch in 6 and CC. But in CC 2014, all of my embedded resources get the error: 1120 Access of undefined property.
Any insight is greatly appreciated.
Below is not my code but the sample code that is included with Away3D. This also generates the 1120 Error in CC 2014 (but works fine in 6 and CC) for the embedded assets: FloorDiffuse, TrinketDiffuse, etc.
package
import away3d.containers.*;
import away3d.core.pick.*;
import away3d.entities.*;
import away3d.events.*;
import away3d.materials.*;
import away3d.primitives.*;
import away3d.utils.*;
import caurina.transitions.Tweener;
import caurina.transitions.properties.CurveModifiers;
import flash.display.*;
import flash.events.*;
import flash.geom.Vector3D;
[SWF(backgroundColor="#000000", frameRate="60", quality="LOW")]
public class Basic_Tweening3D extends Sprite
//plane texture
[Embed(source="/../embeds/floor_diffuse.jpg")]
public static var FloorDiffuse:Class;
//cube texture jpg
[Embed(source="/../embeds/trinket_diffuse.jpg")]
public static var TrinketDiffuse:Class;
//engine variables
private var _view:View3D;
//scene objects
private var _plane:Mesh;
private var _cube:Mesh;
* Constructor
public function Basic_Tweening3D()
stage.scaleMode = StageScaleMode.NO_SCALE;
stage.align = StageAlign.TOP_LEFT;
//setup the view
_view = new View3D();
addChild(_view);
//setup the camera
_view.camera.z = -600;
_view.camera.y = 500;
_view.camera.lookAt(new Vector3D());
//setup the scene
_cube = new Mesh(new CubeGeometry(100, 100, 100, 1, 1, 1, false), new TextureMaterial(Cast.bitmapTexture(TrinketDiffuse)));
_cube.y = 50;
_view.scene.addChild(_cube);
_plane = new Mesh(new PlaneGeometry(700, 700), new TextureMaterial(Cast.bitmapTexture(FloorDiffuse)));
_plane.pickingCollider = PickingColliderType.AS3_FIRST_ENCOUNTERED;
_plane.mouseEnabled = true;
_view.scene.addChild(_plane);
//add mouse listener
_plane.addEventListener(MouseEvent3D.MOUSE_UP, _onMouseUp);
//initialize Tweener curve modifiers
CurveModifiers.init();
//setup the render loop
addEventListener(Event.ENTER_FRAME, _onEnterFrame);
stage.addEventListener(Event.RESIZE, onResize);
onResize();
* render loop
private function _onEnterFrame(e:Event):void
_view.render();
* mesh listener for mouse up interaction
private function _onMouseUp(ev:MouseEvent3D) : void
Tweener.addTween(_cube, { time:.5, x:ev.scenePosition.x, z:ev.scenePosition.z, _bezier:{x:_cube.x, z:ev.scenePosition.z} });
* stage listener for resize events
private function onResize(event:Event = null):void
_view.width = stage.stageWidth;
_view.height = stage.stageHeight;

Please check the OSS note below and install the mentioned patch accordingly:
[Note 1278687 - Exception in the IDocXMLProcessor (IDOC_ERROR_PARSE_FAILURE)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278687]
If it persists, check if are there any mapping errors on the Audit Logs for the failed message.

IDOCXMLtoFileConvertor Exception

Hi,
Can someone please let me know the reason for below exception for IDOC XML converter.
Message processing failed. Cause: com.sap.conn.idoc.IDocParseException: (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
Thanks
-Kulwant

Hi Kulwant Bhatia,
I understand you are getting error message in IDOC sender channel (using IDOCFlatToXmlConvertor) in PI7.11. Hope you have followed steps mentioned in SAP Help [Link1|http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm]
It seems, error is due to wrong IDOC format triggered from sender SAP system (R/3). You may take out IDOCFlatToXmlConvertor module from communication channel and test interface again, to see how messages looks (in SXI_MONITOR or RWB).
Regards,
Raghu_Vamsee

IDOC_ERROR_PARSE_FAILURE

Similar Messages

Maybe you are looking for