Error in parsing an XML-urgent

hi all,
iam receving the following error message
"ORA-29540 class oracle/xml/parser/plsql/xmlparsercover does not exists"
while executing one of my procedures.
please let me know what could be the problem?...
Regards,
vimal.

You cannot import and export the XDB schema. You must install it. The XDB Schema is not required for XMLDOM, XMLPARSER, XSLPROCESSOR, only for the DBMS_XMLDOM, DBMS_XSLPROCESS and DBMS_XMLPARSER pacakage. You may have totally corrupted your instance. Ideally you should restore the entire database from backup at this point. If you do not have a backup from before the point you tried to import XDB (which wouldn't suprise me) you should try to drop the XDB user immediately. You should then upgrade to at least 9.2.0.3.0 and then add the XDB user following the instructions in the XDB Developers guide. Basically run the script catnoqm followed by the script catqm. Note you should take a full backup before running catnoqm.

Similar Messages

"Error while parsing SOAP XML payload: no element found" received when invoking Web Service

Running PB 12.1 Build 7000. Using Easysoap. Error ""Error while parsing SOAP XML payload: no element found" received when invoking Web Service". This error does not appear to be coming from the application code. Noticed that there were some erroneous characters showing up within the header portion of the XML ("&Quot;"). Not sure where these are coming from. When I do a find within the PB code for """" it gets located within two objects, whereas they both reference a "temp_xml_letter". Not sure where or what temp_xml_letter resides??? The developer of this is no longer with us and my exposure to WSDL and Web Services is rather limited. Need to get this resolved...please.
This is the result of the search. Notice the extraneous characters ("""):
dar1main.pbl(d_as400_mq_xml)
darlettr.pbl(d_email_xml)
---------- Search: Searching Target darwin for 'temp_xml' (9:52:41 AM)
---------- 2 Matches Found On "temp_xml":
dar1main.pbl(d_as400_mq_xml).d_as400_mq_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> number </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
darlettr.pbl(d_email_xml).d_email_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> imcnumber </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
---------- Done 2 Matches Found On "temp_xml":
---------- Finished Searching Target darwin for 'temp_xml' (9:52:41 AM)

Maybe "extraneous" is an incorrect term. Apparantly, based upon the writeup within Wiki, the parser I am using does not interpret the """? How do I find which parser is being utilized and how to control it?
<<<
If the document is read by an XML parser that does not or cannot read external entities, then only the five built-in XML character entities (see above) can safely be used, although other entities may be used if they are declared in the internal DTD subset.
If the document is read by an XML parser that does read external entities, then the five built-in XML character entities can safely be used. The other 248 HTML character entities can be used as long as the XHTML DTD is accessible to the parser at the time the document is read. Other entities may also be used if they are declared in the internal DTD subset.
>>>

Unable to display tree view; Error when parsing an XML document (Premature end of file.)

Hi folks,
I am using a cascaded mapping in my OM. I have a graphical mapping followed by the Java mapping. It is a flat file to IDOC mapping. Everything works fine in Dev but when I transport the same objects to QA, the Operation mapping though it doesn't fail in ESR testing tool, gives the following message and there is no output generated for the same payload which is successfully tested in DEV. Please advise on what could be the possible reasons.
Unable to display tree view; Error when parsing an XML document (Premature end of file.)

kalyan,
There seems to be an invalid xml payload which causes this error in ESR not generating the tree view. Please find the similar error screenshot and rectify the payload.
Mutti

Error when parsing the XML document

hi all.
i have the next problem.
the sender sistem send to XI an XML. some tags send a '#' caracter.
Sender Service send:
Torre B1 - B#Unimev
when Im traying to test XML inbound, XI show the next error:
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x14(:main:, row:1, col:992))
XML:
<?xml version="1.0" encoding="UTF-8" ?>
- <ZDEBMAS6>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>300</MANDT>
 <DOCNUM>0000000000339708</DOCNUM>
 <DOCREL>640</DOCREL>
 <STATUS>30</STATUS>
 <DIRECT>1</DIRECT>
 <OUTMOD>2</OUTMOD>
 </EDI_DC40>
- <E1KNA1M SEGMENT="1">
 <MSGFN>009</MSGFN>
 <REGIO>07</REGIO>
 <STCD1>20147972750</STCD1>
 <FITYP>01</FITYP>
 <STCDT>80</STCDT>
 <STCD3>0</STCD3>
- <Z1KNA1M SEGMENT="1">
 <MSGFN>009</MSGFN>
 <KUNNR>0001000563</KUNNR>
 <ZZSOCRCV>3100</ZZSOCRCV>
 <ZZGBDAT>00000000</ZZGBDAT>
 <ZZAD_STREET_CO>Torre B1 - B Unimev</ZZAD_STREET_CO>
 <ZZAD_ROOMNUM_CO>PB</ZZAD_ROOMNUM_CO>
 <ZZAD_FLOOR_CO>E</ZZAD_FLOOR_CO>
 <ZZAD_PSTCD1_CO>M5521AAR</ZZAD_PSTCD1_CO>
 <ZZAD_CITY1_CO>Mendoza</ZZAD_CITY1_CO>
 <ZZAD_REGIO_CO>07</ZZAD_REGIO_CO>
 </Z1KNA1M>
 <Z1ADRCM SEGMENT="1">
 <MSGFN>009</MSGFN>
 <KUNNR>0001000563</KUNNR>
 <STREET>Torre B1 - B Unimev</STREET>
 <FLOOR>PB</FLOOR>
 <HOUSE_NUM2>E</HOUSE_NUM2>
 <CITY1>Mendoza</CITY1>
 <POST_CODE1>5521</POST_CODE1>
 <COUNTRY>AR</COUNTRY>
 <REGION>07</REGION>
 <LANGU>S</LANGU>
 </Z1ADRCM>
 </E1KNA1M>
 </IDOC>
</ZDEBMAS6>
Message was edited by: Rodrigo Pertierra
Message was edited by: Rodrigo Pertierra

Hi Rodrigo,
Do you use a specific "encoding" like UTF-8 or ISO-8859-1 in your Sender CC.
Try changing the Transfer mode to Binary instead of Text.
Also go through these links:-
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
Invalid char in XML from inbound IDoc
Hope this provides a solution.
Regards.
Praveen

Failed upgrade from WLS8.1 sp5 to sp6 Got an error in parsing template.xml

Hi All
have an issue when applying SP6 on WLS81, and web directory has 50G avail..
error msg: 2009-08-19 17:57:38,368 FATAL [readSilentXML] com.bea.plateng.wizard.installer.c
ommon.parsers.TemplateParser - Got an error in parsing template.xml!
2009-08-19 17:57:38,381 FATAL [readSilentXML] com.bea.plateng.wizard.installer.s
ilent.tasks.ReadSilentXMLTask - java.lang.NullPointerException
2009-08-19 17:57:38,387 INFO [WizardController] com.bea.plateng.wizard.WizardCo
ntroller - Terminating.
Any thoughts...
Thanks

Hi All
have an issue when applying SP6 on WLS81, and web directory has 50G avail..
error msg: 2009-08-19 17:57:38,368 FATAL [readSilentXML] com.bea.plateng.wizard.installer.c
ommon.parsers.TemplateParser - Got an error in parsing template.xml!
2009-08-19 17:57:38,381 FATAL [readSilentXML] com.bea.plateng.wizard.installer.s
ilent.tasks.ReadSilentXMLTask - java.lang.NullPointerException
2009-08-19 17:57:38,387 INFO [WizardController] com.bea.plateng.wizard.WizardCo
ntroller - Terminating.
Any thoughts...
Thanks

Error "Cannot parse appinfo xml file."

Periodically my users are getting the error below when trying to launch BPC for Excel:
"Cannot parse appinfo xml file."
Seems this file is getting corrupted somehow. If I remove the file from their citrix profile and they relogin, the file is recreated and then they can launch BPC for Excel. Until then though, they get this error and sometimes it says the Web App server is unavailable, when it indeed is available.
Anyone experience this, or have any ideas as to the problem?
Thanks,
Greg

Please notice that inquiries related to BPC topics should now be posted to dedicated forums.
Business Planning and Consolidations, version for SAP NetWeaver
<a class="jive_macro jive_macro_community" href="" __jive_macro_name="community" modifiedtitle="true" __default_attr="2065"></a>
Business Planning and Consolidations, version for the Microsoft Platform
<a class="jive_macro jive_macro_community" href="" __jive_macro_name="community" modifiedtitle="true" __default_attr="2066"></a>
Please adjust any bookmarks or shortcuts you may have set previously to point to this forum.
Best regards,
[Jeffrey Holdeman|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/jeffrey+holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

Error reading application-client.xml,Urgent

Hi ,
I am getting this error,can anyone suggest something for this ?
found error javax.naming.NamingException: Error reading application-client descriptor: No location specified and no suitable instance of the type 'com.crm.Dao.Customer.CustomerData' found for the ejb-ref CustomerData
Waiting for reply,
Regards,
Mandar

In the client deployment under META-INF you should have the application-client.xml.
Can you CustomerData - home,remote etc. be seen from the clientside classpath?
Have they been deployed to OC4J?
Looks like it is not being found either on the server or on the client.
Cheers,
Ashok

Javax.resource.ResourceException: : Error in parsing XML

Hi
Iam developing a connector application.
Iam using OC4J 9.0.4 version(standalone) for deployment of RAR file. We are parsing the below xml in our application using SAX parser.
<?xml version="1.0" encoding="utf-8"?>
<DocAnnoList xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" LibName="IMGSERV" DocID="1698353" SystemType="1">
<AnnoDefPermission>
<security>
<securityobject libraryid="IMGSERV" systemtype="idmis" objectid="" objecttype="annotation" clientpermission="change">
<permission id="1" name="Test1G" type="group" level="read" />
<permission id="2" name="Test1G" type="group" level="write" />
<permission id="3" name="Test1G" type="group" level="append" />
</securityobject>
</security>
</AnnoDefPermission>
</DocAnnoList>
But iam getting the below error while parsing this xml with OC4J running on Win2k/HPUX/Solaris.
Error in parsing XML Stream. The element "DocAnnoList" is not as per the XSD.
04/03/26 14:11:06 org.xml.sax.SAXException: : Error in parsing XML Stream. The element "DocAnnoList" is not as per the
XSD.
04/03/26 14:11:06 at com.abc.is.ra.util.AB_IS_XMLObjectHandler.startElement(Unknown Source)
04/03/26 14:11:06 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1181)
04/03/26 14:11:06 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:300)
04/03/26 14:11:06 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:267)
04/03/26 14:11:06 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
04/03/26 14:11:06 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:286)
04/03/26 14:11:06 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:224)
I put the xSchema.jar,xml.jar & xmlparserv2.jar in java CLASSPATH as described at below URL.
http://otn.oracle.com/pub/articles/vohra_xmlschema.html
But problem is still there.
Can anyone tell me what is the problem. Iam sure, there is nothing wrong with our code as it is running well on Websphere 5, Weblogic 8.1, JBoss 3.2.3, SUN ONE 7.

will come if there are any tab spaces in the file..
delete the tab spaces from the file..

Parsing of xml file in oracle stored procedure on linux server

We have an XML file in the "/database/stats/dev/xml1/" path and tried to parse the file using the below code :
p := xmlparser.newParser;
xmlparser.setValidationMode(p, FALSE);
-- xmlparser.setErrorLog(p, errfile);
xmlparser.setBaseDir(p, dir);
xmlparser.parse(p, inpfile);
doc := xmlparser.getDocument(p);
xmlparser.freeParser(p);
The above procedure is throwing below mentioned exception at "xmlparser.parse(p, inpfile);".
SQLCODE: ORA-31001
SQLERRM: ORA-31001: Invalid resource handle or path name "/xml1.dtd"
The xml file contains the following line, which is giving an error, while parsing the xml file.
<!DOCTYPE CCIOrder SYSTEM "xml1.dtd">
Directory Structure:
OWNER DIRECTORY_NAME DIRECTORY_PATH
SYS XML1 /database/stats/dev/xml1

you'll need to use server-side code to check the xml file names in that folder, return that list to flash and display the list to the user.
or, if you can get by presenting a hard-coded list of xml files, you won't need any server-side coding.

JavaMapping in PI 7.1 Error:Unable to display tree view; Error when parsing

hi,
i get by testing in PI 7.1 (operation mapping) this ERROR:
"Unable to display tree view; Error when parsing an XML document (Content is not allowed in prolog.)"
this is my java-programm-code:
import java.io.FileInputStream;
import java.io.FileOutputStream;
import com.sap.aii.mapping.api.StreamTransformation;
import java.io.*;
import java.util.Map;
import javax.xml.parsers.*;
import org.xml.sax.*;
import org.xml.sax.helpers.*;
/*IMPORT statement imports the specified classes and its methods into the program */
/Every Java mapping program must implement the interface StreamTransformation and its methods execute() and setParameter() and extend the class DefaultHandler./
public class Mapping extends DefaultHandler implements StreamTransformation {
Below is the declaration for all the variables we are going to use in the
subsequent methods.
     private Map map;
     private OutputStream out;
     private boolean input1 = false;
     private boolean input2 = false;
     private int number1;
     private int number2;
     private int addvalue;
     private int mulvalue;
     private int subvalue;
     String lineEnd = System.getProperty("line.separator");
setParamater() method is used to store the mapping object in the variable
"map"
     public void setParameter(Map param) {
          map = param;
     public void execute(InputStream in, OutputStream out)
               throws com.sap.aii.mapping.api.StreamTransformationException {
          DefaultHandler handler = this;
          SAXParserFactory factory = SAXParserFactory.newInstance();
          try {
               SAXParser saxParser = factory.newSAXParser();
               this.out = out;
               saxParser.parse(in, handler);
          } catch (Throwable t) {
               t.printStackTrace();
As seen above execute() method has two parameters "in" of type
InputStream and "out" of type OutputStream. First we get a new instance
of SAXParserFactory and from this one we create a new Instance of
SAXParser. To the Parse Method of SaxParser, we pass two parameters,
inputstream "in" and the class variable "handler".
Method "write" is a user defined method, which is used to write the
string "s" to the outpurstream "out".
     private void write(String s) throws SAXException {
          try {
               out.write(s.getBytes());
               out.flush();
          } catch (IOException e) {
               throw new SAXException("I/O error", e);
     public void startDocument() throws SAXException {
          write("");
          write(lineEnd);
          write("");
          write(lineEnd);
     public void endDocument() throws SAXException {
          write("");
          try {
               out.flush();
          } catch (IOException e) {
               throw new SAXException("I/O error", e);
     public void startElement(String namespaceURI, String sName, String qName,
               Attributes attrs) throws SAXException {
          String eName = sName;
          if ("".equals(eName))
               eName = qName;
          if (eName.equals("NUMBER1"))
               input1 = true;
          if (eName.equals("NUMBER2"))
               input2 = true;
     public void endElement(String namespaceURI, String sName, String qName)
               throws SAXException {
          String eName = sName;
          if ("".equals(eName))
               eName = qName;
          if (eName.equals("NUMBER1"))
               input1 = false;
          if (eName.equals("NUMBER2"))
               input2 = false;
     public void characters(char[] chars, int startIndex, int endIndex)
               throws SAXException {
          String dataString = new String(chars, startIndex, endIndex).trim();
          if (input1) {
               try {
                    number1 = Integer.parseInt(dataString);
               } catch (NumberFormatException nfe) {
          if (input2) {
               number2 = Integer.parseInt(dataString);
          if (input2 == true) {
               addvalue = number1 + number2;
               mulvalue = number1 * number2;
               subvalue = number1 - number2;
               write("" + addvalue + "");
               write(lineEnd);
               write("" + mulvalue + "");
               write(lineEnd);
               write("" + subvalue + "");
               write(lineEnd);
in developer studio 7.1 i dont get error.
this happens by testing the mapping-programm in ESR.
can somebody help me please?

Make sure that the xml created out after the java mapping is a valid xml with only one root node.
Regards,
Prateek

Getting the following error while parsing the values usng xml parser

Hi
I am getting the following error while parsing the values using the code in r12 instance on linux
declare
XML_PARSER XMLPARSER.PARSER;
DOC XMLDOM.DOMDOCUMENT;
DOCELEMENT DBMS_XMLDOM.DOMELEMENT;
BEGIN
-- NEW PARSER
XML_PARSER := XMLPARSER.NEWPARSER;
-- SET SOME CHARACTERISTICS
XMLPARSER.SETVALIDATIONMODE(XML_PARSER, FALSE);
     IF P_DIR IS NOT NULL AND P_FILENAME IS NOT NULL
     THEN
     FND_FILE.PUT_LINE(FND_FILE.LOG,'DIRECTORY FOUND'||'-'||P_DIR);
     XMLPARSER.SETBASEDIR(XML_PARSER, P_DIR);
     -- PARSE INPUT FILE
     FND_FILE.PUT_LINE(FND_FILE.LOG,'FILE FOUND'||'-'||P_FILENAME);
     XMLPARSER.PARSE(XML_PARSER, P_DIR || '/' || P_FILENAME);
     -- GET DOCUMENT
     DOC := XMLPARSER.GETDOCUMENT(XML_PARSER);
     LOAD_SUPP(doc);
     ELSE
     DBMS_OUTPUT.PUT_LINE('DIRACTORY/FILENAME CANNOT BE NULL');
     END IF;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('DATA NOTINSERTED'||sqlerrm);
     ROLLBACK;
END
I am getting the following error
DIRACTORYL-/home/appldevORA-0000: normal, successful completion
FILE NAME-suppliersample_data.xmlORA-0000: normal, successful completion
DATA NOTINSERTEDORA-31001: Invalid resource handle or path name "/home/appldev/suppliersample_data.xml"
ORA-06512: at "SYS.XDBURITYPE", line 11
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 142
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-29280: invalid directory path
It could be great if some one could give a suggestion/solution.
Thanks
Ajesh

Besides this is not the correct forum try to google the error message first before posting:
http://ora-29280.ora-code.com/
cheers

XML - 0112 Error on parsing using SAX and xml file in InputSource object.

I need to parse a XML string and extract some information. I have to use SAX parser. I'm converting hte string to InputSource and then trying to parese.
i'm getting XML-0112 error, my guess is that it is not able to locate DTD file but i tried hardcoding the whole path in DOCTYPE tag.
i tried doing setSystemId also but no luck.
null

Can you post a simple test case to look at?

Error while parsing or executing XML-SQL document

friends,
my scenario is based on file to jdbc.i am facing an error in receiver CC in RWB.
The error states that '
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'MATMAS' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated.'
My SOAP xml message is
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:TimeSent>2008-02-06T22:30:21Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>ECC</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>BS_JDBC</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://file_to_jdbc">MI_JDBC_RECEIVER</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">
sapecc50\sapmnt\trans</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileEncoding">UTF-8</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">txt</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">matmas1.txt</sap:Record>
</sap:DynamicConfiguration>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info />
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="IS">is.01.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:22Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
</sap:Hop>
</sap:HopList>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
and payload message is
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
- <STATEMENT>
- <ROW action="INSERT">
<TABLE>MATMAS</TABLE>
- <access>
<MATNR>38</MATNR>
<MTART>HALB</MTART>
<MATKL>00107</MATKL>
<MEINS>pc</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>10</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>88</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>13</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>89</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.03.02</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>14</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>98</MATNR>
<MTART>HALB</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.09.01</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>170</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2005.03.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>178</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.03.06</ERSDA>
<BRGEW>3</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>188</MATNR>
<MTART>NLAG</MTART>
<MATKL>5</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.05.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>288</MATNR>
<MTART>HALB</MTART>
<MATKL>101</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.02.11</ERSDA>
<BRGEW>5</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>358</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.09.09</ERSDA>
<BRGEW>500</BRGEW>
<NTGEW>500</NTGEW>
<GEWEI>G</GEWEI>
</access>
- <access>
<MATNR>359</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.08.01</ERSDA>
<BRGEW>20</BRGEW>
<NTGEW>10</NTGEW>
<GEWEI>G</GEWEI>
</access>
</ROW>
</STATEMENT>
</ns0:MT_JDBC_RECEIVER>
Could anybody help me in sorting out this issue.My advance thanks

hi,
ypur structure is bad defined.
if you want to do an insert, the DT should be
<ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
___<StatementName>
______<dbTableName action=INSERT>
_____<table>MATMAS</table>
_______ <access>
___________<MATNR>38</MATNR>
___________<MTART>HALB</MTART>
___________<MATKL>00107</MATKL>
___________<MEINS>pc</MEINS>
___________<ERSDA>2008.04.05</ERSDA>
___________<BRGEW>10</BRGEW>
___________<NTGEW>12</NTGEW>
___________<GEWEI>KG</GEWEI>
______</access>
_____</dbTableName>
__ </StatementName>
</ns0:MT_JDBC_RECEIVER>
the ROW field is used when you wait receive data from DB for example you execute and SQL Query from Sender communication channel "SELECT name FROM TABLE Names"
so, the result of this query would be, for example:
<row>
____<name>joge</name>
</row>
<row>
____<name>pepe</name>
</row>
<row>
____<name>nicola</name>
</row>
See this link
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:40 AM
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:42 AM

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

Error while parsing or executing XML-SQL document attribute "action" missin

Hi All,
I am doing a scenario for IDOC to JDBC, When I push IDOC from R/3 , IDOC sent to XI System successfully,
I have also checked in SXMB_MONI it is showing the successful staus without any errors, and I have also copied the xml structure from main document of payloads and tested the mapping in Integration Designer, and it is showing successfull message.
here is the xml structure from payloads of Request Message Mapping ........
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">1000001</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">1</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">1</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">1</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">1</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">2</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">2</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">2</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">6</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">6</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">4</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">6</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">3</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">3</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">3</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">5</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">5</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">5</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">9</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">7</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">7</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">7</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">12</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">8</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">8</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">8</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</ns0:RTACOGRP_RECEIVER_MT>
When I checked for component monitoring in runtime workbench....
these are the messages........
Error while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Here are the messages from message monitoring ......
2007-06-07 12:42:17 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2007-06-07 12:42:17 Success JDBC adapter receiver channel RTACOGRP_COM_Chan: processing started; party , service WSORTABS
2007-06-07 12:42:17 Error No "action" attribute found in XML document ("action" attribute missing or wrong XML structure)
2007-06-07 12:42:17 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure).
2007-06-07 12:42:17 Error The message status set to NDLV.
Can any body please resolve the problem.....
Thanks in Advance
Murthy

Bhavesh,
Now I have changed the data structure , and the resultant structure is like this...
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <Statement>
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">100002223</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">H</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">H</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">H</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">H</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">T</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">V</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">V</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">S</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">R</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">R</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">R</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">8</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">S</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">S</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">S</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">10</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">T</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">11</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">E</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">E</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">E</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</Statement>
</ns0:RTACOGRP_RECEIVER_MT>
Now in message monitoring error is showing like this...
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error
Now in Component Monitoring error is showing like this....
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error
I have tested the stored procedure in sql by giving the same values , it was successfully executed..
Can you please tell me where is the error still in structure ...
Thanks in Advance,
Murthy.

Error in parsing an XML-urgent

Similar Messages

Maybe you are looking for