Message processing failed in XML parser

This is IDoc to file integration. When I test (WE19), I did not put any value in the 'Quantity' field (which is 6 characters long).In the message mapping I put a condition to see if the value is empty then put zero, and it did not give any error. I have given all the fixed field lengths in the file adapter but still getting the following error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'TABLERO DE CONTROL' too long (>6 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'TABLERO DE CONTROL' too long (>6 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'

When I enter value in the 'Quantity' field, the integration works fine. The value 'tablero de control' is the 'Description' which is the next field. My Content Conversion is like;
Field1, Field2, Quantity, Description
(where Field1 and Field2 are mandatory and Quantity and Description are optional)
When I provide all 4 values, the integration work just fine, when I do not provide 'Quantity' it fails.

Similar Messages

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableExcep

Hi,
I am generating IDoc for infotype 2006 through creating Change pointers using the Function Module 'CHANGE_POINTERS_CREATE_DIRECT'.
The problem is the Idoc is not reaching the receiver system. It is showing the below error message when i checked it in RWB Communication Channel Monitoring,
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'XXXXX' (structure 'callperson'): com.microsoft.sqlserver.jdbc.SQLServerException: Warning: Fatal error 7987 occurred at Dec 17 2009 1:43PM( $ . Note the error and time, and contact your system administrator.
The scenario is Sender: Idoc and Receiver : JDBC adapters.
Please let me know how to solve this issue.
Thanks,
Sri

Hi,
From the error message: "Error processing request in sax parser: Error when executing statement for table/stored proc. 'XXXXX' (structure 'callperson'): ". I think:
(a) If there is any data type mismatch like a character field from PI is trying to post into a date or numeric field in the stored procedure. You need to check if the data type of the fields in PI and the stored procedure are same?
(b) If there is any structure mismatch when the XML is created by BADI like any mandatory fields are missing.
Thanks,
Manohar Dubbaka

Message processing failed if we receive attachments via E-Mail

Dear ladies and gentlemen,
we have follow proccess:
We get some e-mails with an attachment. The E-Mail pick up the messages and send it to an RFC Channel.
I changed the payload via the localejbs/AF_Modules/PayloadSwapBean :
localejbs/AF_Modules/PayloadSwapBean Local Enterprise Bean TRANSFORM
and the module configuration looks follow:
TRANSFORM swap.keyName payload-name
TRANSOFRM swap.keyValue MailAttachment-1
it looks good and the payload would be swapped okay, and the mapping is also okay.
But if we push the message to the RFC Adapter I get follow error message back:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
So now my question: If is possible, that the adapter try to send also the Body of this E-Mail to the target system ? Because the
Message ID is the ID from the payload of the E-Mail Body.
It is possible to keep away the E-Mail Body from the payload?
Because we need only the attachment. Or if I I have to setup via Bean anything in the RFC Adapter ?
Thanks
Kind reagards
Stephan Kohler
P.S. The PI System is an PI 7.1, the target system would be an R/3 4.6. I haven't any success with the RFC Adatper version 7.10 or 6.40

> Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
>
Is your attachment an XML? Is this XML structure is same as what you mapping source is? If that is the case, it should be okay. Is this interface working for non-mail sender? You might want to re-import the RFC structure in to PI again.
VJ

Message processing failed: Invalid http response: 220

Hi Experts,
I am working on FILE to SOAP scenerio. File is coming in XI properly. But in the SOAP CC its showing this error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid http response: 220 (Name of the Interanet of the Company) Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Thu, 23 Oct 2008 12:02:22 +0530 : java.io.IOException: invalid http response: 220 (Name of the Interanet of the Company) Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Thu, 23 Oct 2008 12:02:22 +0530
Any ideas ?
-=Soniy

Hi Sonia,
Please go throgh the following links for use ofr XML SPY
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75
Re: Stand alone testing using XML Spy
WSDL frm Altova xml spy
Invoke Webservices using SAPXI
Testing XI exposed Web-Services
Regards
Sridhar Goli

Message processing failed, FTP Receiver Adapter error...

Hello all,
We have a Idoc to File(FTP) scenario using PI.
When PI try to send the file out to the FTP site, we get the following message in the communication channel monitoring and the file never reach the FTP site:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: ConnectException: Connection timed out: connect
When we look at the detail display, we can see that the connection as been establish with the FTP site but the adapter is unable to deliver the file...
Any Idea why?
Thanks in advance.

Hi ,
There are two things that you can do
1- check the connection of FTP from command prompt. If it is acceebile from command prompt then check for authorization that wether you have access to post the file at FTP or not (Full access READ , WRITE and EXCECUTE)
2- in your adpater change the connection mode from Per file transfer to "Permanent".
Please feel free to reply on this thread if you are not able to.
Thanks

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
help me.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
HI Arivazhagan K,
Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Post Processing Failed in XML Publiser

Hi all,
We are dealing with XML Publisher reports and when trying to run one XML PUblisher report it is completing with warning.
Log file is showing the following message.
Malaysia Payroll: Version : UNKNOWN
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
TP3 module: Borang TP3
Current system time is 30-MAY-2011 01:28:20
XDO Data Engine Version No: 5.6.3
Resp: 64320
Org ID : 204
Request ID: 4532818
All Parameters: P_PERSON_ID=28131:P_BUSINESS_GROUP_ID=7267:P_LEGAL_ENTITY=7267
Data Template Code: TP3
Data Template Application Short Name: MYPAY
Debug Flag: N
{P_BUSINESS_GROUP_ID=7267, P_PERSON_ID=28131, P_LEGAL_ENTITY=7267}
Calling XDO Data Engine...
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 4532818 on node RSTNLIN74 at 30-MAY-2011 01:28:23.
Post-processing of request 4532818 failed at 30-MAY-2011 01:28:24 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
------------- 2) PRINT   -------------
Not printing the output of this request because post-processing failed.
Finished executing request completion options.
Concurrent request completed
Current system time is 30-MAY-2011 01:28:24
-------------------------Output Post Process Log shows-------------------------------------
[5/28/11 12:09:34 PM] [main] Starting GSF service with concurrent process id = 1325195.
[5/28/11 12:09:34 PM] [main] Initialization Parameters: oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
[5/28/11 12:09:34 PM] [Thread-24] Service thread starting up.
[5/28/11 12:09:34 PM] [Thread-25] Service thread starting up.
[5/30/11 12:39:36 AM] [OPPServiceThread0] Post-processing request 4532804.
[5/30/11 12:40:04 AM] [OPPServiceThread1] Post-processing request 4532805.
[5/30/11 12:40:35 AM] [OPPServiceThread0] Post-processing request 4532806.
[5/30/11 12:53:05 AM] [OPPServiceThread0] Post-processing request 4532811.
[5/30/11 1:04:18 AM] [OPPServiceThread1] Post-processing request 4532813.
[5/30/11 1:21:21 AM] [OPPServiceThread0] Post-processing request 4532814.
[5/30/11 1:21:21 AM] [1325195:RT4532814] Executing post-processing actions for request 4532814.
[5/30/11 1:21:21 AM] [1325195:RT4532814] Starting XML Publisher post-processing action.
[5/30/11 1:21:21 AM] [1325195:RT4532814]
Template code: FNDCPPGD_XML
Template app: FND
Language: en
Territory: US
Output type: PDF
[5/30/11 1:21:21 AM] [UNEXPECTED] [1325195:RT4532814] java.sql.SQLException: No corresponding LOB data found :SELECT L.FILE_DATA FILE_DATA,DBMS_LOB.GETLENGTH(L.FILE_DATA) FILE_LENGTH, L.LANGUAGE LANGUAGE, L.TERRITORY TERRITORY, B.DEFAULT_LANGUAGE DEFAULT_LANGUAGE, B.DEFAULT_TERRITORY DEFAULT_TERRITORY,B.TEMPLATE_TYPE_CODE TEMPLATE_TYPE_CODE, B.USE_ALIAS_TABLE USE_ALIAS_TABLE, B.START_DATE START_DATE, B.END_DATE END_DATE, B.TEMPLATE_STATUS TEMPLATE_STATUS, B.USE_ALIAS_TABLE USE_ALIAS_TABLE, B.DS_APP_SHORT_NAME DS_APP_SHORT_NAME, B.DATA_SOURCE_CODE DATA_SOURCE_CODE, L.LOB_TYPE LOB_TYPE FROM XDO_LOBS L, XDO_TEMPLATES_B B WHERE L.APPLICATION_SHORT_NAME= :1 AND L.LOB_CODE = :2 AND L.APPLICATION_SHORT_NAME = B.APPLICATION_SHORT_NAME AND L.LOB_CODE = B.TEMPLATE_CODE AND (L.LOB_TYPE = 'TEMPLATE' OR L.LOB_TYPE = 'MLS_TEMPLATE') AND ( (L.LANGUAGE = :3 AND L.TERRITORY = :4) OR (L.LANGUAGE = :5 AND L.TERRITORY = :6) OR (L.LANGUAGE= B.DEFAULT_LANGUAGE AND L.TERRITORY= B.DEFAULT_TERRITORY ))
     at oracle.apps.xdo.oa.schema.server.TemplateInputStream.initStream(TemplateInputStream.java:402)
     at oracle.apps.xdo.oa.schema.server.TemplateInputStream.<init>(TemplateInputStream.java:235)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.getTemplateFile(TemplateHelper.java:1163)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3444)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3541)
     at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:244)
     at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
[5/30/11 1:21:21 AM] [1325195:RT4532814] Completed post-processing actions for request 4532814.
[5/30/11 1:28:23 AM] [OPPServiceThread1] Post-processing request 4532818.
[GC 8210K->5080K(11276K), 0.0012260 secs]
[GC 8216K->5078K(11276K), 0.0012560 secs]
[GC 8214K->5083K(11276K), 0.0011170 secs]
[GC 8219K->5087K(11276K), 0.0011670 secs]
[GC 8223K->5082K(11276K), 0.0011230 secs]
[GC 8218K->5087K(11276K), 0.0011180 secs]
[GC 8223K->5092K(11276K), 0.0011080 secs]
[GC 8228K->5092K(11276K), 0.0012260 secs]
[GC 8228K->5090K(11276K), 0.0010840 secs]
[GC 8226K->5089K(11276K), 0.0012210 secs]
[GC 8225K->5097K(11276K), 0.0010610 secs]
[GC 8233K->5091K(11276K), 0.0011330 secs]
[GC 8227K->5098K(11276K), 0.0011240 secs]
[GC 8234K->5096K(11276K), 0.0010460 secs]
[GC 8232K->5103K(11276K), 0.0022520 secs]
[GC 8239K->5098K(11276K), 0.0011190 secs]
[GC 8234K->5105K(11276K), 0.0011640 secs]
[GC 8241K->5102K(11276K), 0.0014740 secs]
[GC 8238K->5103K(11276K), 0.0011120 secs]
[GC 8239K->5101K(11276K), 0.0010530 secs]
[GC 8237K->5106K(11276K), 0.0010870 secs]
[GC 8242K->5104K(11276K), 0.0010420 secs]
[GC 8240K->5105K(11276K), 0.0010480 secs]
[GC 8241K->5108K(11276K), 0.0011200 secs]
[GC 8244K->5115K(11276K), 0.0011700 secs]
[GC 8251K->5111K(11276K), 0.0010490 secs]
[GC 8247K->5117K(11276K), 0.0012940 secs]
[GC 8253K->5112K(11276K), 0.0011300 secs]
[GC 8247K->5116K(11276K), 0.0010980 secs]
[GC 8252K->5115K(11276K), 0.0010890 secs]
[GC 8251K->5119K(11276K), 0.0010890 secs]
[GC 8255K->5117K(11276K), 0.0010370 secs]
[GC 8253K->5118K(11276K), 0.0011740 secs]
[GC 8254K->5120K(11276K), 0.0011840 secs]
[GC 8256K->5121K(11276K), 0.0012260 secs]
[GC 8257K->5125K(11276K), 0.0011040 secs]
[GC 8261K->5124K(11276K), 0.0010090 secs]
[GC 8260K->5125K(11276K), 0.0011170 secs]
[GC 8260K->5129K(11276K), 0.0011130 secs]
[GC 8265K->5128K(11276K), 0.0010480 secs]
[GC 8264K->5135K(11276K), 0.0011050 secs]
[GC 8271K->5130K(11276K), 0.0010600 secs]
[GC 8266K->5131K(11276K), 0.0010950 secs]
[GC 8267K->5135K(11276K), 0.0010570 secs]
[GC 8271K->5134K(11276K), 0.0010880 secs]
[GC 8270K->5141K(11276K), 0.0010960 secs]
[GC 8277K->5137K(11276K), 0.0010790 secs]
[GC 8273K->5138K(11276K), 0.0011670 secs]
[GC 8274K->5141K(11276K), 0.0010620 secs]
[GC 8277K->5145K(11276K), 0.0011940 secs]
[GC 8281K->5143K(11276K), 0.0011200 secs]
[GC 8279K->5147K(11276K), 0.0010760 secs]
[GC 8283K->5150K(11276K), 0.0012490 secs]
[GC 8286K->5150K(11276K), 0.0010610 secs]
[GC 8286K->5156K(11276K), 0.0010800 secs]
[GC 8291K->5151K(11276K), 0.0011010 secs]
[GC 8287K->5157K(11276K), 0.0012580 secs]
[GC 8293K->5153K(11276K), 0.0010330 secs]
[GC 8289K->5157K(11276K), 0.0011080 secs]
[GC 8293K->5161K(11276K), 0.0012330 secs]
[GC 8297K->5155K(11276K), 0.0011780 secs]
[GC 8291K->5157K(11276K), 0.0066620 secs]
[GC 8293K->5158K(11276K), 0.0010720 secs]
[GC 8294K->5163K(11276K), 0.0011140 secs]
[GC 8299K->5161K(11276K), 0.0010860 secs]
[GC 8297K->5169K(11276K), 0.0010910 secs]
[GC 8305K->5164K(11276K), 0.0010540 secs]
[GC 8300K->5170K(11276K), 0.0010750 secs]
[GC 8306K->5167K(11276K), 0.0010910 secs]
[GC 8303K->5168K(11276K), 0.0010290 secs]
[GC 8304K->5176K(11276K), 0.0011060 secs]
[GC 8312K->5170K(11276K), 0.0010690 secs]
[GC 8306K->5178K(11276K), 0.0011290 secs]
[GC 8314K->5174K(11276K), 0.0010470 secs]
[GC 8310K->5174K(11276K), 0.0010680 secs]
[GC 8310K->5179K(11276K), 0.0010430 secs]
[GC 8315K->5176K(11276K), 0.0010710 secs]
[GC 8312K->5183K(11276K), 0.0011260 secs]
[GC 8319K->5179K(11276K), 0.0010770 secs]
[GC 8315K->5180K(11276K), 0.0010760 secs]
[GC 8316K->5185K(11276K), 0.0010610 secs]
[GC 8321K->5312K(11276K), 0.0013210 secs]
[GC 8448K->5353K(11276K), 0.0019140 secs]
[GC 8489K->5415K(11276K), 0.0018470 secs]
[GC 8551K->5325K(11276K), 0.0011910 secs]
[GC 8461K->5354K(11276K), 0.0014650 secs]
[GC 8490K->5332K(11276K), 0.0011390 secs]
[GC 8468K->5377K(11276K), 0.0014780 secs]
[GC 8513K->5478K(11276K), 0.0017080 secs]
[GC 8614K->5582K(11276K), 0.0024720 secs]
[GC 8718K->5683K(11276K), 0.0019120 secs]
[GC 8819K->5782K(11276K), 0.0019170 secs]
[GC 8918K->5887K(11276K), 0.0019020 secs]
[GC 9023K->5988K(11276K), 0.0019350 secs]
[GC 9124K->6093K(11276K), 0.0019290 secs]
[GC 9229K->5954K(11276K), 0.0020720 secs]
[GC 9090K->5966K(11276K), 0.0012100 secs]
[GC 9102K->6046K(11276K), 0.0016590 secs]
[GC 9182K->6143K(11276K), 0.0018650 secs]
[GC 9279K->6049K(11276K), 0.0016840 secs]
[GC 9185K->6162K(11276K), 0.0017150 secs]
[GC 9298K->6267K(11276K), 0.0020640 secs]
[GC 9403K->6374K(11276K), 0.0020920 secs]
[GC 9510K->6482K(11276K), 0.0020880 secs]
[GC 9618K->6593K(11276K), 0.0021410 secs]
[GC 9729K->6693K(11276K), 0.0021760 secs]
[GC 9829K->6804K(11276K), 0.0021370 secs]
[GC 9940K->6910K(11276K), 0.0022810 secs]
[GC 10046K->7015K(11276K), 0.0019900 secs]
[GC 10151K->7125K(11276K), 0.0026840 secs]
[GC 10261K->7227K(11276K), 0.0020670 secs]
[GC 10363K->7338K(11276K), 0.0020980 secs]
[GC 10474K->7444K(11276K), 0.0021910 secs]
[GC 10580K->7556K(11276K), 0.0020750 secs]
[GC 10692K->7663K(11276K), 0.0023720 secs]
[GC 10799K->7770K(11276K), 0.0022450 secs]
[GC 10906K->7876K(11276K), 0.0021890 secs]
[GC 11012K->7979K(11404K), 0.0021700 secs]
[Full GC[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor13]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor6]
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor14]
7979K->6712K(11404K), 0.0792140 secs]
[GC 11320K->6865K(16308K), 0.0017910 secs]
[GC 11473K->7026K(16308K), 0.0027120 secs]
[GC 11634K->7185K(16308K), 0.0027560 secs]
[GC 11793K->7348K(16308K), 0.0039630 secs]
[GC 11956K->7501K(16308K), 0.0027250 secs]
[GC 12109K->7659K(16308K), 0.0025460 secs]
[GC 12267K->7815K(16308K), 0.0028180 secs]
[GC 12423K->7973K(16308K), 0.0025780 secs]
[GC 12581K->8129K(16308K), 0.0026230 secs]
[GC 12737K->8287K(16308K), 0.0026940 secs]
[GC 12895K->8447K(16308K), 0.0028530 secs]
[GC 13055K->8603K(16308K), 0.0029410 secs]
[GC 13211K->8763K(16308K), 0.0028360 secs]
[GC 13371K->8918K(16308K), 0.0030280 secs]
[GC 13526K->8696K(16308K), 0.0069120 secs]
[GC 13304K->8988K(16308K), 0.0032800 secs]
[GC 13595K->9017K(16308K), 0.0052690 secs]
What would be the key problem for this issue.
Can some one please provide us with solution.
Thanks and Regards
Imran
Edited by: 848314 on May 29, 2011 11:50 PM

Duplicate post -- java.sql.SQLException: No corresponding LOB data found XML publisher 12.0.4

XSL-process in C XML-parser

L.S.
I get a memory-leak when executing xslprocess in a loop without initiating my input-xml and xsl-contexts.:
xctx=xmlinit( ) /* (xml invoer initialiseren) */
xslctx=xmlinit( ) /* (xsl invoer initialiseren) */
for (i=0;i<10;i++) {
resctx=xmlinit( ) /* (xml uitvoer initialiseren) */
free(result);
xslprocess(xctx, xslctx, resctx, &result))
xmlterm(resctx);
xmlterm(xctx);
xmlterm(xslctx);
There is no leak, when I initiate both contexts within the loop like this:
for (i=0;i<10;i++) {
xctx=xmlinit( ) /* (xml invoer initialiseren) */
xslctx=xmlinit( ) /* (xsl invoer initialiseren) */
resctx=xmlinit( ) /* (xml uitvoer initialiseren) */
free(result);
xslprocess(xctx, xslctx, resctx, &result))
xmlterm(xctx);
xmlterm(xslctx);
xmlterm(resctx);
Is this a bug ? Or is there an explanation ??
Regards,
Rik

The xml- and xsl-source look normal (there is no import or include). When I look in the process-table I see the size of the process increasing.
XML:
<body>
<addCustomer>
<CustomerDetail>
<CustomerName>
<Name>Diederik Lakerveld</Name>
</CustomerName>
<MobielNummer>
<telephoneNumber>31123456789</telephoneNumber>
</MobielNummer>
</CustomerDetail>
</addCustomer>
</body>
XSL:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="*|@*|comment()|processing-instruction()|text()">
<xsl:copy>
<xsl:apply-templates
select="*|@*|comment()|processing-instruction()|text()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="telephoneNumber">
<xsl:copy>
<xsl:variable name="d" select="."/>
<xsl:value-of select="concat('06-', substring(string($d),3,9))"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
Regards,
Rik

Non-English characters processed correctly by XML Parser 2 XSLT?

I'm trying to transform an XML document (parsed as an XMLDocmument) using an XSL stylesheet (parsed as an XSLStylesheet) and the XSLProcessor class in Java, I encounter the following problem:
Non-US characters such as German umlauts, stored in the XML in &#xxx; style, are not processed properly. "|" (ü), for example, comes out as "C<". Is this a bug in the XSLProcessor class or am I doing something wrong? I'm using this stylesheet declaration:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml1/strict"> Or should I mess with the encoding attribute of the ?xml ...? PI?
tia
John Smith

I have not specified any encoding.
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="completeproduct.xsl"?>
<PRODUCT connection="demosample" xmlns:xsql="urn:oracle-xsql">
<xsql:query>
select * from products
</xsql:query>
should i specify encoding
null

Urgent: Calling web service from PL/SQl fails with XML parsing

Hi,
I am trying to call a web service from PL/SQL (using SOAP protocol and UTL_HTTP built in Package).I am using Oracle 9i .I am calling from pl/sql block invoking web service method created in java.
I am getting the below response object as a SOAP protocol, but i couldn't able to parse the SOAP.
Could you please provide the values of FirstName, LastName and ErrorDescription
declare
request_env varchar2(32767);
v_xml XMLTYPE;
l_user_first_name varchar2(100);
l_user_last_name varchar2(100);
l_error_value varchar2(100);
begin
response_env:='<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<UserInfoObjResponse xmlns:axis2ns1="http://www.test.com/services">
<axis2ns1:FirstName >First Name Output</axis2ns1:FirstName>
<axis2ns1:LastName>Last Name Output</axis2ns1:LastName>
<axis2ns1:ErrorDescription />
</UserInfoObjResponse>
</soapenv:Body>
</soapenv:Envelope>';
dbms_output.put_line('Length of Request:' || length(response_env));
dbms_output.put_line ('Request: ' || response_env);
v_xml := XMLTYPE(response_env);
-- SELECT EXTRACTVALUE(v_xml, '//UserInfoObjResponse/FirstName') INTO l_user_fast_name varchar2(100); FROM DUAL;
dbms_output.put_line ('l_user_first_name: ' || l_user_first_name);
dbms_output.put_line ('l_user_last_name : ' || l_user_last_name);
dbms_output.put_line ('l_error_value: ' || l_error_value);
end;

In Oracle 9i:
SQL> declare
2    response_env varchar2(32767);
3    v_xml XMLTYPE;
4    l_user_first_name varchar2(100);
5    l_user_last_name varchar2(100);
6    l_error_value varchar2(100);
7 begin
8    response_env:='<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
9                     <soapenv:Body>
10                       <UserInfoObjResponse xmlns:axis2ns1="http://www.test.com/services">
11                         <axis2ns1:FirstName >First Name Output</axis2ns1:FirstName>
12                         <axis2ns1:LastName>Last Name Output</axis2ns1:LastName>
13                         <axis2ns1:ErrorDescription />
14                       </UserInfoObjResponse>
15                     </soapenv:Body>
16                   </soapenv:Envelope>';
17
18    dbms_output.put_line('Length of Request:' || length(response_env));
19 -- dbms_output.put_line ('Request: ' || response_env);
20
21    v_xml := XMLTYPE(response_env);
22
23    select EXTRACTVALUE(v_xml,'/*:Envelope/*:Body/*:UserInfoObjResponse/*:FirstName/text()') first_name,
24           EXTRACTVALUE(v_xml,'/*:Envelope/*:Body/*:UserInfoObjResponse/*:LastName/text()') last_name,
25           EXTRACTVALUE(v_xml,'/*:Envelope/*:Body/*:UserInfoObjResponse/*:ErrorDescription/text()') error_description
26      into l_user_first_name, l_user_last_name, l_error_value
27      from dual;
28
29    dbms_output.put_line ('l_user_first_name: ' || l_user_first_name);
30    dbms_output.put_line ('l_user_last_name : ' || l_user_last_name);
31    dbms_output.put_line ('l_error_value: ' || l_error_value);
32 end;
33 /
Length of Request:530
l_user_first_name: First Name Output
l_user_last_name : Last Name Output
l_error_value:
PL/SQL procedure successfully completed.In Oracle 10g:
SQL> declare
2    response_env varchar2(32767);
3    v_xml XMLTYPE;
4    l_user_first_name varchar2(100);
5    l_user_last_name varchar2(100);
6    l_error_value varchar2(100);
7 begin
8    response_env:='<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
9                     <soapenv:Body>
10                       <UserInfoObjResponse xmlns:axis2ns1="http://www.test.com/services">
11                         <axis2ns1:FirstName >First Name Output</axis2ns1:FirstName>
12                         <axis2ns1:LastName>Last Name Output</axis2ns1:LastName>
13                         <axis2ns1:ErrorDescription />
14                       </UserInfoObjResponse>
15                     </soapenv:Body>
16                   </soapenv:Envelope>';
17
18    dbms_output.put_line('Length of Request:' || length(response_env));
19 -- dbms_output.put_line ('Request: ' || response_env);
20
21    v_xml := XMLTYPE(response_env);
22
23    select r.*
24      into l_user_first_name, l_user_last_name, l_error_value
25    from XMLTABLE('/' PASSING v_xml
26                  COLUMNS
27                  first_name varchar2(30) PATH '/*:Envelope/*:Body/*:UserInfoObjResponse/*:FirstName/text()',
28                  last_name varchar2(30) PATH '/*:Envelope/*:Body/*:UserInfoObjResponse/*:LastName/text()',
29                  error_description varchar2(30) PATH '/*:Envelope/*:Body/*:UserInfoObjResponse/*:ErrorDescrition/text()'
30                  ) r;
31
32    dbms_output.put_line ('l_user_first_name: ' || l_user_first_name);
33    dbms_output.put_line ('l_user_last_name : ' || l_user_last_name);
34    dbms_output.put_line ('l_error_value: ' || l_error_value);
35 end;
36 /
Length of Request:530
l_user_first_name: First Name Output
l_user_last_name : Last Name Output
l_error_value:
PL/SQL procedure successfully completed.Max
http://oracleitalia.wordpress.com
Edited by: Massimo Ruocchio on Feb 14, 2010 11:55 PM
Added the first one.

Exception in XML Parser

Hi all,
I have a file-XI-file scenario.
In this scenario the Transport Protocol used is FTP.
The remote sender and the receiver system have Golden FTP server installed.
The xml file is getting properly picked from the sender system. The format of this file is:
<?xml version="1.0" encoding="UTF-8" ?>
<ns:file_mt xmlns:ns="http://namespace4BPM1">
<file_type>binary</file_type>
<file_name>input</file_name>
<file_ext>txt</file_ext>
<content_dt>
<firstname>neetu</firstname>
<middlename>k</middlename>
<lastname>gupta</lastname>
</content_dt>
</ns:file_mt>
But the reciever file adapter is giving the following error:
Receiver Adapter v1027 for Party '', Service 'Receiver_Service':
Configured at 10:21:05 2006-06-05
Last message processing started 10:21:35 2006-06-05, Error: Message processing failed with java.lang.Throwable: ftp access error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns:file_mt' found in document', probably configuration error in file adapter (XML parser error)'
The parameters specified in the receiver adapter are:
Connect mode: per file transfer
Transfer mode: Binary
put file: directly
file type : binary
I also tried sending the file after removing the structure 'ns:file_mt', but it gave the structure missing error message.
Pls if anybody could guide me as to what should be done.
Thanks in advance.
Regards
Neetu

check the document name in file adapter configuration channel and message type name of the interface and name space..both should have same name...
check thz blog for more inputs
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
Go through them and cross check ur config..

XML parsing failed - Works in Oracle Developer fails in SQLplus

Hello,
I am trying to figure out what could possibly be causing my XML parsing to fail from sqlplus. Basically the exact same sql script fails with the following error when run from sqlplus but works fine in Oracle Developer.
Now I have read a number of posts talking about the NLS_Lang and characterset issues. But these are all running on the same machine.
Error Message Received:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00222: error received from SAX callback function
ORA-06512: at "SYS.DBMS_XMLSTORE", line 78
ORA-06512: at line 53
Exact SQL Script
DECLARE
insCtx DBMS_XMLStore.ctxType;
rows NUMBER;
xmldoc CLOB :=
'<DepotData DepotCode="B106">
<tblPoint_of_Call>
<DEPOTCODE>B106</DEPOTCODE>
<MASTERKEY>2077</MASTERKEY>
<ADDR_ID>45286159</ADDR_ID>
<ADDR_MAIL_ID>45286160</ADDR_MAIL_ID>
<STREETBLOCK_KEY>45</STREETBLOCK_KEY>
<PC_ID>19603417</PC_ID>
<ST_ID>40034414</ST_ID>
<BUILDING_KEY>0</BUILDING_KEY>
<ADDR_NUM>505</ADDR_NUM>
<POCTYPE>154</POCTYPE>
<RECEPTACLETYPE>964</RECEPTACLETYPE>
<TOTALPOCS>1</TOTALPOCS>
<TOTALPOCSOCCUPIED>1</TOTALPOCSOCCUPIED>
<TOTALADMAIL>1</TOTALADMAIL>
<OLD038POC>0</OLD038POC>
<OCCUPIED>1</OCCUPIED>
<ADMAIL>1</ADMAIL>
<BAGGER>0</BAGGER>
<SORTED>1</SORTED>
<DELIVERED>1</DELIVERED>
<AMOBLIGATORY>0</AMOBLIGATORY>
<POCICANDIDATE>0</POCICANDIDATE>
<DELIVERYSEQUENCE>10</DELIVERYSEQUENCE>
<NUMSEPARATIONS>0.50</NUMSEPARATIONS>
<SEPSGROUPID>0</SEPSGROUPID>
<DELETED>0</DELETED>
<CARDID>0</CARDID>
<CARD>0</CARD>
<FORCECARD>0</FORCECARD>
<DNC>0</DNC>
<PRINTED>0</PRINTED>
<A12CARD>0</A12CARD>
<EXTRACARDS>0</EXTRACARDS>
<DSOUPDATECODE>0</DSOUPDATECODE>
<TRANSACTION_TYPE>0</TRANSACTION_TYPE>
<UPDATE_TYPE>0</UPDATE_TYPE>
<SORTSEQUENCE>10</SORTSEQUENCE>
<BUILDINGBASE>0</BUILDINGBASE>
</tblPoint_of_Call>
</DepotData>';
BEGIN
insCtx := DBMS_XMLStore.newContext('AIMPRIME.TBLPOINT_OF_CALL'); -- get saved context
-- set the columns to be updated as a list of values
-- Now insert the doc.
-- This will only insert into EMPNO, SAL and HIREDATE columns
DBMS_XMLStore.setRowTag(insCtx,'tblPoint_of_Call');
rows := DBMS_XMLStore.insertXML(insCtx, xmlDoc);
-- Close the context
DBMS_XMLStore.closeContext(insCtx);
END;
System Information:
Oracle XE on windows XP. Everything is running on the same machine, sqlplus, Oracle Developer and the database are all on the same machine.
If you need any more information please let me know, and how to get the information you want. I am not a DBA so I don't know how to do a lot of things with oracle, but I do know that this SQL should be working.

NLS...read up on them
on the same machine, yeah and...?
(1) c:\> set NLS_LANG=.....
(2) c:\> sqlplus
-- sqlplus has the active nls settings set from (1)
3) you now connect to a database
- this database has an NLS character settings that where set during using a spfile or pfile
- or, as in the case of the characterset, was defined and set once, during the creation of the database.
So...
Your NLS settings in (1) can be different from the ones that are active in the database (3).
Your NLS settings are / can be set on windows on 5 levels
In the registry under /software/oracle:
1) on HKEY_LOCAL_MACHINE
2) on HKEY LOCAL USER
In the envionment settings from windows under control panel, system, advanced, environment settings:
3) on system level
4) on user level
5) On command level via explicitly setting the parameter before starting the actual program
So in all, you can have the case where the NLS settings from sqlplus or Oracle Developer or the database are all different.
http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm

Since I updated Firefox 4, I cannot open any attachments in my Gmail, whether Word or PDF files, I can only view them. When trying to download attachments I get an error message: "XML Parsing Error:undefined entity. Help!

The full error message is the following:
XML Parsing Error: Undefined entity
Location chrome://mozapps/content/downloads/unknown content type.xul
Line Number 30, Column 18

In order to use ''nxm://'' links, Nexus Mod Manager must be installed and associated with the ''nxm'' protocol.
* http://www.nexusmods.com/skyrim/mods/modmanager/
In case of problems with this third-party program, please refer to its support forum:
* http://forums.nexusmods.com/index.php?/forum/1413-nmm-code-development-chat

Exception in XML Parser (format problem?)

Hi Experts,
I am working on IDOC -> AS2 Configuration and the AS2 Configuration has the below structure
<RecordSet>
     <Row1>
                   <row1 - field1>
                   <row1 - field2>
                   <row1 - field3>
     </Row1>
     <Row2>
                   <row2 - field1>
                   <row2 - field2>
                   <row2 - field3>
     </Row2>
     <Records>
          <Record1>
                    <Record1-Field1>
                    <Record1-Field1>
                    <Record1-Field1>
          </Record1>
          <Record2>
                    <Record2-Field1>
                    <Record2-Field1>
                    <Record2-Field1>
          </Record2>
     </Records>
</RecordSet>
We are getting the expected Structure when we AS2 Receiver has the xml format. But while doing module development with the strctxml2Plain, we are getting the below error in RWB CC Monitoring.
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
Any ideas, why this error we are getting.....
Thanks in advance,
Regards,
Vasu

Hi Vasu,
Not in the Mapping of IR.
In BIC Mapping Designer you have to test with the standard Mappings by providing the sample file whether the Conversion is happening correctly or not.
You have to take the same input file that what ever you are having now.
So that it will say clearly what is the problem in converting the XMLto the required EDI Format...
Check whether you have any Date Format Values are comming from the input file.
Regards
Seshagiri

Xml parsing error while selecting whole result set for sql query

Hi All,
I am having xml parsing error while selecting whole query result set. The data is coming fine for default result set of 50 rows.
My exception is below.
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00234: namespace prefix "xsi" is not declared
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 254
ORA-06512: at line 1
*31011. 00000 - "XML parsing failed"*
**Cause: XML parser returned an error while trying to parse the document.*
**Action: Check if the document to be parsed is valid.*
My sql query is below that is giving results for default result set of 50 rows.
select extract(xmlType(clob_xml_colm_name), '//v2:node1//childnode/text()','xmlns:v2="namespace_url"').getStringVal() from table_name
My sql developer version is below.
Java(TM) Platform     1.7.0_04
Oracle IDE     3.1.07.42
Versioning Support     3.1.07.42
My database version is below.
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit
Please could any one help me urgently as the sql query is supposed to be correct as it is returning query results, but the problem happening when i try to select whole result set.
Thanks and regards,

What does the XML look like? It appears that some of the supposed XML stored as a CLOB is not really valid XML. Find the row in the table that is causing your issue and review the "XML" in it.

Message processing failed in XML parser

Similar Messages

Maybe you are looking for