Special character in receiver xml

Dear All,
I have a file being moved from SAP to Market end point server. The receiver side is in xml format (no FCC)
Code page conversion is used - UTF8 TO UTF16LE
A special character is occurring in the receiver side: [] It is actually new line character and I suupose due to incompatibility it is coming.
How do we get rid of this character?
Thanks

Hi,
What Kind of mapping do you use? I have explored this behaviour in a XSLT Mapping and i resolved it by using <xsl:strip-space element = "*" />
Maybe this help?
Regards,
Björn

Similar Messages

Need to prevent special character in generated XML file

Hello,
I am using E-business Suite 12.1.3 and XML version 5.6.3.
My XML file is ending up with a special character (a Latin capital letter U with circumflex) at the end, after the final closing tag.
Due to this the concurrent program that needs to output the XML is ending with warning.
My XML file is produced using a PL/SQL procedure, as follows (I've simplified it):
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<?xml version="1.0" encoding="UTF-8" ?>');
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<DOCS>');
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<LETTER>');
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<EMP_NAME>Michaela Hart</EMP_NAME>');
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'</LETTER>');
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'</DOCS>');
But when I run the concurrent request that creates the output then try to view the output in Internet Explorer I get the following error:
Invalid at the top level of the document. Error processing resource 'http://servername.domain...
</DOCS>
If I view the source of the page in Internet Explorer it shows a square after </DOCS> indicating the special character that has been added.
I checked this by looking at the output file in unix (cat -v o7766582.req) and it showed up the Latin U character.
I realise it could be to do with the character set I am using. I checked what we had on the server:
> echo $NLS_LANG
American_America.UTF8
I would have thought that corresponded with the XML declaration character set but I'm not sure.
Does anyone have any other ideas about why I have this special character, and how it could be removed?
Thanks in advance,
Hazel

Hi AlexAnd,
thanks very much for your reply.
I'm now unable to recreate the problem since dbms_xmlgen worked. If I switch back to my previous method it works fine!
I'm not sure your suggestion would help, as there were no special characters in the data, the special character was added after the last tag I output. I hard coded the data (as in my example) for testing purposes so there was no SQL in use and the special character was still added at the end of the XML output. But I will definitely give it a try if I get the problem again.
I had the idea that maybe I should have been using FND_FILE.PUT rather than FND_FILE.PUT_LINE but now the error is gone I can't tell if that would have solved the problem either.
I appreciate your input.
Regards
Hazel

Special character in receiving file

hi everyone.
i have implemented file to file scenario. I am getting file at my receiving end.
IN my receiver CC i have mentioned endSeparator as 'nl' , but when file gets created it shows special charater (box shaped) separating each record.
any idea where m going wrong ?
thanks,
gaurav

hi,
when i opened that txt file in notepad , m getting that special rectangle character but when i opened it in wordpad, its coming perfectly.
what does this rectangle char is ??? when we specify endSeparator as 'nl' then do we need to open it in wordpad only ????
thanks,
pooja

Special character printing in xml reports

Hello,
When i am trying to print euro symbol in xml report, i am getting some '?' symbol instead of euro symbol.
Need your suggestion here what extra tags we need to use for the same.
I have designed rtf file and inserted euro symbol using word doc.
Thanks,
Amar

In Report properties at XML prolog Value field change to below code:
<?xml version="1.0" encoding="windows-1252"?>
or try like below
copy contents to BI Publisher Desktop\Template Builder for Word\fonts in your <oracle_home>\lib\fonts
Regards,
Ajay Reddy
Edited by: user13259014 on Feb 23, 2011 12:06 PM

Xml publisher reprot - special character problem

I invoice report through xml publisher. I have '&' special character in vendor list. I am getting below error
A semi colon character was expected. Error processing resource.
Below is the code
CREATE OR REPLACE PACKAGE BODY XML_RPT AS
    FUNCTION XML_TAG (p_tag IN VARCHAR2, p_data IN VARCHAR2) RETURN VARCHAR2 IS
    l_ret_str VARCHAR2(5000);
    BEGIN
        l_ret_str := '<'||p_tag||'>'||p_data||'</'||p_tag||'>';
        RETURN l_ret_str;
    END XML_TAG;
     PROCEDURE VENDOR(errbuf          OUT VARCHAR2,
                     retcode         OUT NUMBER) IS
    CURSOR inv_Cur IS
        select pv.vendor_name
        from po_vendors pv;
     xmldata            varchar2(1000);
     l_sqlstr           varchar2(1000);
     l_seqnum           varchar2(3);
     l_vendor_name      varchar2(100);
    BEGIN
      xmldata := '<?xml version="1.0" encoding="UTF-8"?>';
      xmldata :=xmldata|| '<VENDOR>';
      xmldata := xmldata||' <LIST_VENDOR>';
      fnd_file.put_line(fnd_file.output,xmldata);
      FOR rpt_rec IN inv_Cur LOOP
          xmldata := '<VENDOR_REC>';
          l_vendor_name := replace(rpt_rec.VENDOR_NAME,'&','&amp');
          xmldata := xmldata || XXMCG_XML_TAG('VENDOR_NAME',L_VENDOR_NAME);
          xmldata :=xmldata|| '</VENDOR_REC>';
          fnd_file.put_line(fnd_file.output,xmldata);
      END LOOP;
      xmldata := '</LIST_VENDOR>';
      xmldata := xmldata||'</VENDOR>';
     fnd_file.put_line(fnd_file.output,xmldata);
    EXCEPTION
    WHEN OTHERS THEN
         fnd_file.put_line(fnd_file.log,substr(SQLERRM,1,500));
    END VENDOR;
END XML_RPT;can any one advice.

Duplicate post ? xml publisher report problem
Srini

Special character in XML causing the file to hit worng folder.

I am facing program, while sending a data to a repository using SOAP XML. The file path which is needed has a special character and this is not getting identified at the target.
here is the brief descriptio.
1) We generate the PDF using the XML report in ERP.
2) Using the same data, we generate SOAP XML file and send to a respoitory.
3) Here using this SOAP XML, the PDF is generated and stored in a location which is sent in the file.
we are sending the target path as "PO's from Customer" as below:
'<target_folder_path>'||'/Documents/'||TO_CHAR(SYSDATE,'YYYY')||'/PO's from Customer'||'</target_folder_path>';
The path needed is '/Documents/2012/PO's from Customer' , but due the apostrophe, the file is hit /adadmin path.
I have tried replcaing the special character by ' , but still no luck. If i remove the special characters, then the file is hitting correct path.
But the requirement is to have '/Documents/2012/PO's from Customer' .
Is there is a way this can be achived. Please advice.

Is it as simple as using two single quotes between PO and s?
'/PO''s from Customer'I can't tell from what you wrote how you are generating the value in the first place so if not correct provide more details related to whatever builds the path.

Special Character Restrictions for Native XML Driver

Hi,
I have found the following special character restrictions in the documentation:
"Because they are handled specially by the Native XML driver, do not use the following special characters to define element types and attributes in your XML schema:u201C.u201D, u201C/u201D, u201C\u201D, u201C:u201D u201C@u201D."
After checking the createad XML-Files in our projects that we will use for CR4E there is often a u201C.u201D in the definition. Because this is delivered from third-party, we wish that the u201C.u201D will be enabled.
In the moment we create the XSD-Files from the XML-File with XML2XSD.
It is possible in the future?
Best Regards
Arnold Meier

The changes aren't in XI Release 2, but in 2008.
Do you still have Nha's XML data? I edited Document_Policy, Policy_AllCoverages, Policy_Beneficiary to Document.Policy, Policy.AllCoverages, Policy.Beneficiary, then use the following code in CR4E 2.0:
reportClientDocument reportClientDocument;
ConnectionInfo connectionInfo;
PropertyBag propertyBag;
* Connect to the Java Print Engine and create a new document.
reportClientDocument = new ReportClientDocument();
reportClientDocument.setReportAppServer(ReportClientDocument.inprocConnectionString);
reportClientDocument.newDocument();
* Define connection to the XML and XSD files.
propertyBag = new PropertyBag();
propertyBag.put("Local XML File", "C:\\Documents and Settings\\tueda\\Desktop\\nha.xml");
propertyBag.put("Local Schema File", "C:\\Documents and Settings\\tueda\\Desktop\\nha.xsd");
propertyBag.put("Convert Multivalue to Table", Boolean.FALSE);
propertyBag.put("Database DLL", "crdb_xml.dll");
connectionInfo = new ConnectionInfo();
connectionInfo.setAttributes(propertyBag);
* Specify the dataset in the XML as a Table, and add to the report.
Table table = new Table();
table.setConnectionInfo(connectionInfo);
table.setName("Document.Policy/Policy.Beneficiary");
table.setAlias("Document_Policy/Policy_Beneficiary");
reportClientDocument.getDatabaseController().addTable(table, null);
* Save report to file C:\local_xml.rpt
reportClientDocument.saveAs("nha_local_xml.rpt", "C:\\", ReportSaveAsOptions._overwriteExisting);
reportClientDocument.close();
Sincerely,
Ted Ueda

Parsing xml that contains special character

this is my xml file.
<?xml version="1.0" encoding="ISO-8859-1" ?>
<grid_assessment>
     <chart>
          <range>5</range>
          <sharing_charging>
               <score>3</score>
               <label><![CDATA[SHARING & CHARGING POLICIES]]></label>
this is my java code.
          SAXParser parser = new SAXParser();
          parser.setContentHandler(this);
          parser.setErrorHandler(this);
          try
               fis = new FileInputStream(xmlFile);
          catch(IOException ioe)
               System.out.println( ioe.getMessage() );
          InputSource inputSource = new InputSource((InputStream)fis);
          try
               parser.parse(inputSource);
          catch(SAXException saxe)
               System.out.println( saxe.getMessage() );
          catch(IOException ioe)
               System.out.println(ioe.getMessage());
when i parse the xml file, i got an error message like this.
org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.Stopping after fatal error: The entity name must immediately follow the '&' in the entity reference.
is there anybody who knows how to parse the xml file that contais special character?
i tried "&" instead of "&". but it didn't work...
please help...
thanks in advance...

this is my java code.
          SAXParser parser = new SAXParser();If that is javax.xml.parsers.SAXParser then your code won't compile; i suspect you might be using some non-standard parser?
          parser.setContentHandler(this);
          parser.setErrorHandler(this);These methods are deprecated.
when i parse the xml file, i got an error message like this.
org.xml.sax.SAXParseException: The entity name must
immediately follow the '&' in the entity
reference.Stopping after fatal error: The entity name
must immediately follow the '&' in the entity
reference.I don't; maybe it's your parser. What parser are you using, and what version?
is there anybody who knows how to parse the xml file
that contais special character?There is nothing more you need to do; the codeimport javax.xml.parsers.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
import java.io.*;
public class CeasarKim1Parser extends DefaultHandler {
public static void main (String[] args) {
    try {
      SAXParser parser = SAXParserFactory.newInstance().newSAXParser();
      FileInputStream fis = null;
      fis = new FileInputStream(args[0]);
      InputSource inputSource = new InputSource((InputStream)fis);
      parser.parse(inputSource, new CeasarKim1Parser () );
    } catch(SAXException saxe) {
      saxe.printStackTrace();
    } catch(IOException ioe) {
      ioe.printStackTrace();
    } catch (ParserConfigurationException pce) {
      pce.printStackTrace();
public void characters(char[] ch, int start, int length) {
    System.out.println(new String(ch, start, length));
// similar implementations of the other content handler methods
}which is basically a compilable and non-deprecated version of yours, with the file<?xml version="1.0" encoding="ISO-8859-1" ?>
<grid_assessment>
<chart>
    <range>5</range>
    <sharing_charging>
      <score>3</score>
      <label><![CDATA[SHARING & CHARGING POLICIES]]></label>
    </sharing_charging>
</chart>
</grid_assessment>does not generate any exceptions and parses the CDATA section correctly. That is using 1.4.1 and the default org.apache.crimson.jaxp.SAXParserImpl parser.
Pete

XML special character/encoding problem

Hi
I would like to store XML in a MSSQL database into a column with the datatype xml.
It seems like the xml datatype in an xMII transaction allways is stored with encoding type UTF-8
and the MSSQL xml datatype is UTF-16. This gives me some problem with special characters when inserting into the MSSQL database (in the example below is the MSSQL datatype xml):
INSERT INTO
VALUES
The error returned is this:
"com.microsoft.sqlserver.jdbc.SQLServerException: XML parsing: line 1, character 62, illegal xml character"
If I replace the 'ä' with a normal 'a' the command executes ok.
I am currently using a workaround that looks like this, when setting the parameter in my transaction:
stringreplace(Local.test, " encoding=" & doublequote & "UTF-8" & doublequote, "")
But I was hoping I could get rid of the stringreplace.
Is there a solution / recommended way of doing this?
Best Regards
Simon Bruun
Edited by: Simon Bruun on Mar 4, 2011 10:43 AM

I solved this. I convert to Unicode UTF-8

Biztalk error if "&" special character is used from Oracle Database

There is an error when system was received data form Oracle database. The data format is including "&"....etc special character. Becuase of the error appear between Oracle database and receive port. I can't do anything in Biztalk program to
encode the message. Does any way to do encoding when biztalk receive data?
xlang/s engine event log entry: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'ECT.TOSToEDB.orcWorkingTable(7e2c77ec-adb6-5790-29ad-835ec8374c1d)'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 8eb4cb36-82b2-4d34-9b45-64b8aba23758
Shape name:
ShapeId: 09bc980e-3040-4238-a838-f3606294effe
Exception thrown from: segment 1, progress 84 Inner exception: An error occurred while parsing EntityName. Line 4, position 112.
Exception type: XmlException
Source: System.Xml
Target Site: Void Throw(System.Exception) The following is a stack trace that identifies the location where the exception occured
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   at System.Xml.XmlTextReaderImpl.ParseEntityName()
   at System.Xml.XmlTextReaderImpl.ParseEntityReference()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
   at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.LoadXml(String xml)
   at ECT.TOSToEDB.orcWokingTableCheck.segment1(StopConditions stopOn)
   at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

There are 5 special characters which in xml & < > " ' if the Oracle fields contain any of those characters it will cause invaild xml.
This can be solved at the oracle side be replacing the special characters by it's html encode equivalent, so & becomes & , I think the best way to solve it
is to make a custom pipeline component and translate the special characters there.
There is my Send Port Properties. Do you mean the default biztalk pipeline component ("XML Receive") cannot translate any special characters?

How to insert special character in sgm file and interprete it without isoents while opening in FM9.0

I have an sgm file which contains special characters in different languages.
<!DOCTYPE MANUAL PUBLIC "-//SWE-XXX//DTD XXX MANUAL-DTD 2.0//EN">
<MANUAL LANG="CS">
<TITEL>
Polish characters: óê¿ñæÑÆÊ¥Ó£
Czech characters: éìóïáøèíùòú&Og rave;ÌÉÓÚÙÈØÍÁÏ aacute: á</TITEL>
</MANUAL>
Is there any way to insert special character directly in sgm file, so that it won't have to be interpreted by isoents mapping rules?
isoent.rwr interpretes oacute as:
entity "oacute" is fm char 0x00F3;
But I would like to use 0x00F3 directly in fm file, so that if any additional character is needed - I won't have to update isoent files
I've tested already:
ó
&x00F3;
&0x00F3;
but with no luck
Is there anyone who could help me with it?
I will really appreciate your help
/Joanna

Hi Michael. Thank you for your reply.
There is no declaration within sgm file itself - but while opening the file I use sgml application definition with the following settings:
Default API client: FmTranslator
SGML character encoding: ISO Latin1
XML character encoding: UTF-8
Namespace: Enable
CSS2 Preferences:
Generate CSS2: Disable
Add Fm CSS Attribute To XML: Disable
Retain Stylesheet Information: Disable
Entity locations
Entity search paths
C:\Program Files\Adobe\FrameMaker9\Structure\sgml\isoents
So as you can see, character encoding is set to ISO Latin1 (there is no way to use UTF-8 encoding in sgml files)
Typing ź or ć in sgm document and opening it with framemaker sgml application - I receive: ¿æ and message: "Non-SGML character found; should have been character reference"
Everything works fine when I type f.ex.: &x016B; and insert appropriate reference lines into isolat1.rw and isolat1.ent files
But what I would like to avoid is editing those isoent files each time new character is be needed.

Special Character Handling (&) in the payload content in PI 7.1

Hello All,
My Scenario is Idoc to File. I need to handle some special characters like "&" in XML payload content in PI 7.1. I am receiving & character in the text field.
eg:
<RECORD>
   <BEGDA>20100901</BEGDA>
   <STAT1>A</STAT1>
   <NAME1>Grandview&MO CLMR</NAME1>
<PERL_SUB_AREA>0005</PERL_SUB_AREA>
</RECORD>
I created java mapping by using the blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9420. [original link is broken] [original link is broken] [original link is broken]
"The code used in java mapping is converting & into &amp"
Mapping is working fine in the test tab of Operation mapping and the message is successfully handling the record with & character(message with Chequered Flag).In the result tree view,it is showing
<PERL_TEXT>Grandview&MO CLMR</PERL_TEXT
and in the source XML view
<PERL_TEXT>"Grandview&ampMO CLMR"</PERL_TEXT>
Issue:
Now the record is written as
<RECORD>
<CUST_STATUS>A</CUST_STATUS>
<COMPANY>1050</COMPANY>
<PERL_AREA>1MOB</PERL_AREA>
<PERL_TEXT>"Grandview&ampMO CLMR"</PERL_TEXT>
<PERL_SUB_AREA>0005</PERL_SUB_AREA>
</RECORD>
Since & is coming as part of text, "it is converting & -> &amp" in the text field and the record is written in the file as
"A|1050|1MOB|Grandview&ampMO CLMR|0005 ....."
While it should come as:
A|1050|1MOB|Grandview&MO CLMR|0005 .....
Java mapping code used is as:
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import com.sap.aii.mapping.api.StreamTransformation;
public class HandleAmpersand implements StreamTransformation {
     public void setParameter (Map param) { }
     public void execute (InputStream in, OutputStream out) {
          try {
               int read_data;
                    while ((read_data = in.read() ) != -1) {
                         if (read_data != '&') {
                              out.write(read_data);
                         } else {
                         out.write("&".getBytes());
                    out.flush();
     } catch (Exception e) { }
Also, i am using message mapping after java mapping in operation mapping
Please guide me where it is going wrong.
Thanks
Shikha Jain
Edited by: Jain Shikha on Jan 5, 2011 4:42 AM

Hi Jain Shikha,
I have faced similar issue in our production system.
Our issue:-
Sender system is sending :- DEKOR " OBS!
Other middleware is converting it and sending to SAP PI as :- DEKOR &amp ;quot; OBS!
Because of this, there is increase in size from 12 characters to 21 characters. We were getting error as the target side ABAP table has column width 15.
Our solution:- Wrote a java mapping to convert &quot; to u201C
if (strContent.contains("&")) {
                    getTrace().addInfo("& is present");
                    strContent = strContent.replaceAll("&amp ;", "&");
                    strContent = strContent.replaceAll("&quot ;", "\"");
                    strContent = strContent.replaceAll("&apos ;", "\'");
                    strContent = strContent.replaceAll("&amp ;", "&");
                    strContent = strContent.replaceAll("&lt ;", "<");
                    strContent = strContent.replaceAll("&gt ;", ">");
Note: - quote ("), apostrophe ('), ampersand (&), less than (<), greater than (>) are special characters in XML. They should not be present in data. http://www.w3.org/TR/REC-xml/
Not Well formed XML:
<Name>Raghuu2019s</Name>   <Name> Raghu & Vamsee </Name>
Well formed XML:
<Name>Raghu's</Name>   <Name>Raghu & Vamsee</Name>
Graphical mapping, XSLT, DOM, SAX need well formed XML as input, otherwise they give parser exception.
Your solution:-
I understand you are using a graphical mapping. Follow below steps
Step 1: Convert u201CNot Well formed XMLu201D to u201CWell formed XMLu201D, using java mapping (which your doing already).
Step 2: Use Graphical mapping for your transformation logic.
Step 3: Again convert back u201CWell formed XMLu201D to u201CNot Well formed XMLu201D (As this what target system is expecting. Use below java mapping.
Regards ,
Raghu
Edited by: Raghu Vamsee on Jan 6, 2011 1:45 PM
Edited by: Raghu Vamsee on Jan 6, 2011 1:59 PM

Special Character Issue in Country Name Côte d'Ivoire encoding ISO-88509-1

soa suite 10.1.3.4
I am reading an xml file using file adapter. The file has encoding type ISO-88509-1 and the country name is coming as <country_name>Côte d'Ivoire</country_name>.
When I see the BPEL instance, this character is converted to "C\234te d'Ivoire" jumbled character. The target endpoints receives the country name in jumbled format only. I can't change the incoming file format. Is there a way I can read it properly and keep the special character as it is during SOA process.
Any idea how can I progress in this issue?

Any idea on this ? My soa suite server is on Solaris and the folder where I am reading the file from is on Windows.

SOAP Adapter - Error because of special character (u00FC - Umlaut) in payload

Hello,
We have a SOAP sync scenario.
SAP -> PI 7.0 -> 3rd Party system
We have a special character (ü - Umlaut) as part of the payload.
When the message enters message pipeline in PI, I can see the payload XML till message branching step.
From Message mapping step, i get the message - "The XML page cannot be displayed. An invalid character was found in text content" in SXMB_MONI.
In communication channel monitoring, I see the following error:
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)(:main:, row=2, col=2106) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106): java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)(:main:, row=2, col=2106) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2106)
But, when I pass the same message(with special character) to the 3rd party system using SOAP UI, i get a valid response back.
So, what is going wrong in PI?
Thanks,
Chandra

Hi Gouri,
you are right. My message is successful in SXMB_MONI, and the error is coming from comm channel monitoring with deliverin to target.
My sender is a proxy, and we can not specify any encoding in proxy sender.
I did not specify any encoding in SOAP Receiver aswell.
This is the sequence in comm channel monitoring:
Success: Delivering to channel: CI_SOAP_Receiver_Sync
Success: MP: Entering module processor
Success: MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success: SOAP: request message entering the adapter with user J2EE_GUEST
Error: SOAP: call failed: java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)
Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046): java.io.IOException: Parsing Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)(:main:, row=2, col=2046) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 72(:main:, row:2, col:2046)
So, what can i do to fix this?
Thanks,
Chandra
Edited by: Chandra Sekhar H on Mar 3, 2011 12:25 PM

Error while releasing transport request - Special character "_" in generic

Hi all,
we're receiving the error Special character "_" in generic key when releasing a best practice transport.
Note 1304725 describes my error, but the solution cannot be implemented. The reason for this is that we do not have an individual entry for eacht yb_PS,..,
but we have only one entry where field BWERT has a wildcard '*' as entry.
Does anyone has some idea how to solve this ?
kind regards !

Hello Bjorn,
How did you get this solved?
I'm having nearly the same issue:
A custom-table with a total key lenght of about 365 characters. As soon as I enter a special character (_) in the key field just before the position 120, the message tk287 rejects the entry. Entering the special character in a key field at about key position
60, there's no message rejecting the entry.
Regards

Special character in receiver xml

Similar Messages

Maybe you are looking for