IDoc xML character issue

Dear expert,
I meet a intractable issue in our SAP system.
The scenario as below:For our product shipping to china,the ship-to of Sales Order should be chinese.
when i give the response to customer using ALE IDoc which is std in sap,the EDI-Subsystem can't parse the xml file! So our customer can't receive the data.
After tracing the issue,i find it is the chinese charater to beget this.
Actually the idoc file is the ANSI coding.
Can anybody help me ?
Thank you very much.

Dear
I find the really reason is that the R/3 System is Non-Unicode System,the ECC 6.0 is Unicode System.
Is my viewpoint right?
Pls give me some advice.
TKS!

Similar Messages

IDoc XML Conversion Issue

Hi Exerts,
When IDoc sent from R/3 got successfully loaded with all segments in WE02 wihtout overlapping,
I find the data gets overlapped in XML only for a deep routed structure in sxi_monitor, while WE02 has no issue for it.
Analysis made:
1. IDoc details had been checked for the field which has 18 digits, but at XML it receives only 5 digits after which it loads to next element of that structure.
2. When i crosschecked with cache, it was fine and i even activated once with the updated metatdata from R/3.
Queries:
1. From R/3 end, everything looks fine by analyzing WE02, i also checked by running IDOC_XML_TRANSFORM, but this XML has generated the proper data as seen in WE02. Where did it get this issue for overlapping in Integration engine? Will R/3 use this standard function module to transform to XML message or any else that creates this unknown error?
2. I activated the complete objects in repository and also checked the cache status, but still it gets me the same overlapping at XML under the Inbound message. Could anyone kindly clarify why this happens?
Helpful answers will be rewarded.

Santhosh,
Thanks for the quick response.
I cross-checked already in IDX2 for the segment reflections as defined in R/3.
But unforgetedly i missed checking the outbound ports which had required this updations....
This works well...
Here is your granted points.
Thanks a lot for remainding me this resolution Santhosh...
Thanks!
Regards,
Dhayanandh .S

Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

Hi,
I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
"Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
Thank you,
Sri

Hi Sri,
To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
E2EDK01005                    0000047110815000000000001.........
E2EDKA1003                    0000047110815000000000002.........
E2EDKA1003                    0000047110815000000000003..........
E2EDKA1003                    0000047110815000000000004........
The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
Thanks
Harish

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

Special character issue/ encoding of characters

Hi All,
My scenario is-
IDoc -> Soap lookup-> soap lookup----> Jdbc
here I am using 3 mappings inside the same operation mapping. I am sending Idoc from ECC and doing a lookup using SOAP twice and updating a table.
now the problem is that when I am sending the Idoc having values some special characters the first mapping executed successfully but the when it is doing the lookup ( first SOAP call) it is failing to return proper and correct values, it is returning the values as "SAX" and when I checked the soap adapter used for lookup it is in error for SAX parsing with the below error text-
Invalid byte 1 of 1-byte UTF-8 sequence.
I have tried to use one java mapping to transform the encoding from ISO-8859-1 to UTF-8 and other way around and also even tried using the standard soap adapter module- XMBWS.XMLEncoding as ISO-8859-1 but did not work.
for e.g - if IDoc contains character Ñ in any field it is not calling the SOAP call properly and returning the values as SAX and adapter is erroring out as mentioned above.
Please advise.
Thanks
Vineet

When you use an UDF and you have programmed a Sax parser, then make sure, that the parser works with the correct encoding. So when the result of the webservice is ISO-8859-1, then assign this to the parser.
In principle the encoding should be part of XML header. Make sure that the encoding of the response is the same as declared in XML header.

Send / Receive Idoc(XML) in SAP ECC 5.0

Hi Experts,
We are using SAP standard idocs to exchanges master data and Sales data between SAP and non SAP system. currently all the idocs are generated and posted as flat file structure.
There is possiblity to use idoc(XML) and HTTP service instead of standard process without XI?
All info related with this is welcome. is it possible? how?
all suggestion n helpful ans will be rewards with points.
regards: gaurave.

Hi Gaurave,
I have comae accross this type of issue once and hope the below link will give you an idea.
http://msdn2.microsoft.com/en-us/library/cc185479.aspx
thanks,
KIRAN

Error: IDoc XML data record

Hi all,
   We have file->XI->idoc scenario and the problem we are facing is like, when the idoc structure is prepared using XSLT mapping, when the idoc is ready to get in thru the idoc adapter we are getting the following error.
<i><b>Error: IDoc XML data record: In segment
Z1UKGAS_HEADR attribute occurred instead of SEGMENT                                </b></i>
Anyone faced the same issue....if so pls do throw some light into this issue....
We r in XI 3.0 SP13...
Thanks & regards,
Jayakrishnan

Hi,
In an IDOC structure segment attribute is requried. From the error you posted, it looks like seqment attribute is missing.
<Z>
   <IDOC BEGIN="">
      <ED SEGMENT="">
      </ED>
   </IDOC>
</Z>
Naveen

Error in moni as invalid XML character (Unicode: 0x16) was found

Hello Experts,
I am facing an issue in Production interface is Proxy - -> JDBC data is passing in ECC successfully in PI moni it is showing error
as Runtime Exception when executing application mapping program com/sap/xi/tf/_MaterialPlantFromSAP_to_MaterialPlantToDYNAMINE_; Details: com.sap.aii.utilxi.misc.api.BaseRuntimeException; An invalid XML character (Unicode: 0x16) was found in the element content of the document.
when i try to open the payload it is showing data is too long when i click on open screen is getting hang showing as not responding.I have checked in the ECC it is also showing data is too long when i click on open after 1 min payload is opening when i try to copy the payload and paste in Message mapping test tab again screen is getting hanging when i try to test with 20 or 30 records in Mapping it going through.
I have downloaded that XML file from ECC moni it is 8.83 MB .
PI can process this huge file ? please suggest me how to pass data in chunks .And also i am not understanding error is due to Payload has not correct data or Payload is huge.
Please throw some light on the issue any help is highly appreciated.
Regards
Praveen Reddy

Hi Praveen,
you need a HEX editor. Please download one from this link
http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
Here in the editor search for the HEX value 0X16 and see the corrosponding charcater in payload.
Try getting rid of the character before it reaches Integrtaion engine possibly with java mapping.
Regards
Anupam
Edited by: anupamsap on Jan 4, 2012 6:43 PM

Sending IDOC-xml to R/3 system

Hi all
I am doing a bypass File to Idoc scenario.we taking the input file as idoc xml and sending it to R/3 system for IDOC generation.Every thing is normal but in SXMB_MONI its showing Obligatory node E1EDP10 missing while that segment was persent in the input file then we just replaced <E1EDP10> by <E1EDP10 SEGMENT="EIEDP10"> elated! it worked I thought the problem was solved "EUREKA"........But now the client is telling we should not hardcode any value in the input file they have provided i.e we shouldn't add the segment attribute.
Its bypass thats why we can't do mapping also......now we r puzzled ........
can we achieve this by changing the XSD of idoc converting the segment attribute required to optional? or what should be do plz tell us as its urgent.........
Regards
saurabh sharma

Pls avoid creating new threads for the same problem when you have a thread already open for the same issue.
Regards,
Jai Shankar

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.

Creating IDoc XML and sending to XI

There is a mechanism to create IDoc XML within SAP ERP through the use of
Change Pointers in concert with a port of type XML File (WE21). This is well
documented in this document.
http://www.erpgenie.com/sap/sapedi/Conversion%20of%20IDOCs%20to%20XML%20format.pdf
My question is whether the IDoc XML can be generated using Change Pointers and
the resulting IDoc XML be sent to XI through a RFC Adapter.
Please don't suggest using an IDoc Adapter. I already know how to do that.
Thanks
Vamsi

Hello Vamsi,
2) You need use Sender File Adapter for this.Not by RFC Adapter
1)yes, you can generate IDOC-XML using Change pointer
for better understanding...
Re: Change pointers trouble
CHANGE POINTER SAPAPO/C5
Re: Change pointer issue!!
If you want to know the basic concepts of Change pointers...Search SDN..you will find lot of info regardin this...
******************Reward points,if found useful

Com.sap.aii.utilxi.misc.api.BaseRuntimeException:An invalid XML character (Unicode: 0x1f) was found in the element content of the document

Hi,
I'm getting the below runtime exception during IDOC- SOAP message mapping in Integration engine.
"Runtime exception occurred during application mapping com/sap/xi/tf/<<<\\Message mapping object name\\>>>; com.sap.aii.utilxi.misc.api.BaseRuntimeException:An invalid XML character (Unicode: 0x1f) was found in the element content of the document"
I have no clue why this exception occurs. Could anyone say the reason of the exception?
Thanks!
Regards,
Gopi

Hi Gopinath
Check this thread
An invalid XML character (Unicode: 0x1d) was found in the element
Kind regards
Javi

Illegal XML character exception in Importing data imprt manager

Did any one of you face Illegal XML character error while importing extracted data from ECC
I googled and found out XML parser does not like to find '<' '&' in the data , is that true? if so what was the work around ?? BTW we are getting DEBMDM customer data and import manager is bombing with these errors with every other file.
I know import server is a route , but any other solution?
-Sudhir

Hi Sudhir,
We had faced a similar situation when using extracted Material Master data from ECC.
We had some special characters in some of the fields like Material description such as (<,^,*,&,#@)etc.But these data were readily imported in MDM without much troubble.However there were some other fields which had error in the Date Formats and were not excepted by MDM
While automatically importing this data in MDM using the Import server the records failed throwing exceptions.
We then analysed the Source file carefully in Excel format by using Fillters and identified these Wrong date charactes which were giving troubble.
We corrected the dates and had no futher issues for the special character text we imported them with Data type Text Normalized and they passed corrrectly even with Data type as TEXT.
So I suggest that you analyses your data correctly in excel if required for better clearance and check for any futher in consisitencies in the dtaa for every field value.
Hope It Helped,
Thanks & Regards
Simona Pinto

Character issue in Excel

Hi All,
For special character issue ..
in Report Builder--> XML Prolong Value: <?xml version="1.0" encoding="iso-8859-1"?>
then issue is vanished,its ok..
but now my issue is for some characters.. the description is printing like CM&U OWI RuÃdorf (1) SDL
instead CM&U OWI Rußdorf (1) SDL. but some description printing properly,:(
Please let me know if I miss any thing ?
THanks
HTH
Edited by: user633508 on Oct 8, 2010 4:52 PM
Edited by: user633508 on Oct 8, 2010 5:10 PM

Hi Kavipriya,
Thanks for quick reply.
This issue after generating output -> Excel..
I am not getting any issue..
but in place of special character , it shows some squar box symbol.. remaining ok..
and remaining special characters are working fine..
the following examples which I got in my excel output..
CM&U Enertrag Randow-HÃ¶he (8) SDL
CM&U PrÃ¼tzke 1-4 SDL I & II
CM&U Kulder Hof TÃ¶nisvorst (4) SDL phase I+II
the output is generating perfect.. but client reports some bad characters are coming in place of Ö. Ü,ß,.....etc
Please let me know how can we correct the above one.
Thanks..

Mapping error: Character reference "&# 00" is an invalid XML character

Hi All,
Iam performing the RFC(R/3) -> PI(7.1) -> SOAP (third party software) ; Synchronous scenario.
The messages are reaching the PI server , but the a mapping errors is occurring due to dummy characters ""& #00" been sent to the XI system.
Is this due to the R/3 sending the invalid characters or these been generated in PI system. Would you suggest any notes,patches to resolve the issue?
"MAPPING">EXCEPTION_DURING_EXECUTE
com.sap.aii.utilxi.misc.api.BaseRuntimeException:
Character reference "& # 00" is an invalid XML character
Many thanks!
guru

Hi,
If you go through this link last page and last para, which says..
"The only solution is to use a Java mapping before the actual mapping to perform the escaping."
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Regards,
Sarvesh

IDoc xML character issue

Similar Messages

Maybe you are looking for