on 09-16-2013 2:28 PM
Hi Gurus,
I'm face a problem with IDoc_AAE for sending IDoc Extension.
From all symptom I'm sure, that this is the error descripted in the SAP-Note 180511.
But my basis team told me they cannot import it because the current PI is already PI7.31 SP 7 Patch 4.
Here is the screenshot:
But, after longtime reserching, I cannot find other reasons.
Please help me to check whether this note is really not importable?
Thank you for your prompt reply!
Regards
Rene
It is the error of IDoc self.
Just change the root element, then ok.
thank you for your reply!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
my problem was the xml format is not correct.
My colleague developed a Z-IDoc with Name ZDELVRY3 based on standard Idoc DELVRY03. I have not noticed, the xml file contain the root element still is DELVRY03.
For such error, i think the following steps could be helpful:
1. check whether the root element names are same as the imported Idoc in PI.
2. check the format of every element. try to book the same idoc in WE19.
3. still error? then check sap-notes.
Hope my suggestion can help you!
Regards
Rene
Hello Dong,
Note 1801511 IDOC_ERROR_PARSE_FAILURE while sending IDoc Extension, contains a fix for the Java PI component - XI ADAPTER FRAMEWORK 7.31.
For 7.31 SP07 the fix is available in the Patch Level (PL) 01.
Your screenshot shows that the MESSAGING component is on SP07 PL04. However, this component is not related to the fix in the note. Please check with your Basis team if the XI Adapter Framework component is on a higher PL than 01.
Check the notes below for further info:
1381878 How/where to check the patch levels of your XI/PI system
1746599 The difference between a PI Support Pack and a Patch
1335523 FAQ: Deployment PI Patches in Release 7.1 and higher
P.S. A Java patch cannot be imported via SNOTE (only ABAP fixes). Either JSPM or SUM must be used to import a Java patch.
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dong
One way to check and confirm is to run transaction SNOTE in system where the note needs to be
applied-> Click on download SAP Note Icon (7th icon from L to R). After downloading come back on SNOTE initial screen and click on SAP Note Browser ICON(10th icon), Enter the note # , it will show you if the note can be implemented or not.
As the note details "Wrong french translation of table entries in table T163Y" i am not sure if the note has to be applied in XI , but anyways ..give a try.
Regards
Srinivas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dong
Have you already checked the below discussion about similar error
Note 1736292 - Idoc_error_parse_failure Java IDoc_AAE
usually if you see that note can be implemented than Basis team should be able to apply the patch or notes except few exception where manual changes need to be carried out.
Regards
Srinivas
Hi Dong
Please see the below discussion , similar issues was marked as resolved with two note implementations 736292 ,1688780.
http://scn.sap.com/thread/3200077
Regards
Srinivas
Hi,
Can you please share the error details you are facing with regards to the IDoc_AAE, based on that suggestions can be provided...
HTH
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
the scenario is very simple: File --> IDoc.
The IDoc type is DELVRY03 with extension ZDELVRY3.
The standard IDoc DELVRY03 works well, but the extension has the following error:
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: IDoc type extension ZDELVRY3 within the EDI_DC40 control record segment does not match the IDocXML root tag : state=READING_ENDTAG, charPosition=717, lineNumber=27, columnNumber=12
Please help me out!
Thanks
Rene
User | Count |
---|---|
79 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.