Receiver SOAP channel error-- Cant parse the document; HTTP 200 OK

Hi All,
I am facing below error in SOAP receiver communication channel
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
If I use "Do Not se SOAP Envelop" in receiver communication channel then it shows successfully delivered in message monitoring but never reached to target application. And if I uncheck "Do Not se SOAP Envelop" then the error is as I mentioned above.
Both ways it not working foe me.
Please advice.
Thanks
Shivi

Hi
I had a similar issue recent times and I have enablede the xpi inspector to check the logs of the request and the response sent and received...
Based on that you can check whether your payload is able to sent to receiver in proper format or any other issues..
Also try to check the payload format using the SOAPUI whether the ws is working fine for that or not.
HTH
Rajesh

Similar Messages

XI SOAP adapter : Error during parsing the SOAP part

Hello experts,
We have several scenarios SOAP to IDocs.
We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :
#1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#
It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?
Many thanks,
Best regards,
Guislain

Hello Michal,
Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :
test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK
test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK
test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.
So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.
Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question
Would you have any other ideas ?
Thanks a lot,
Best regards,
Guislain

Receiver SOAP channel error: Communication over HTTPS. Unable to create a socket

Hi,
I am getting following error while sending message from PI (7.1) to SalesForce system:
'SOAP: call failed: java.io.IOException: Communication over HTTPS. Unable to create a socket'
Scenario: Sending Customer data from SAP via Async proxy to PI which is sent further to SalesForce system via SOAP webservice call.
When I am trying to Post data to the same webservice via SOAP UI it is working fine and data is getting updated in SalesForce system.
XPI inspector logs for the channel suggest the following:
client [103965] RequestImpl.initSslAttributes(): Initially sslAttributes = null
client [103965] RequestImpl.initSslAttributes(): Cannot find SSL headers in the request.
client [103965] RequestImpl.initSslAttributes(): No SSL attributes: not found in headers and not searched in FCA, because connection.isSecure() = false; sslAttributes = null
I have checked the following SAP Note and requested for updation of SSL icm parameters
891877 - Message-specific configuration of HTTP-Security
I checked the following discussions:
http://scn.sap.com/message/8910518#8910518
http://scn.sap.com/message/6244674#6244674
http://scn.sap.com/thread/2100000
http://scn.sap.com/thread/1632114
which are suggesting a different approach. Kindly suggest a way forward.
Thanks,
Vishwajeet

This is related network issue.
Did you do telnet in pi server with target system ip and port?
If you use https then you need to install certificates.
Check below threads
http://scn.sap.com/thread/190299
Unable to create socket error

Receiver JDBC Channel Error : Incorrect syntax near 'OR'

hi,
we are facing the below error at the receiver communication channel:
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'OR'.
When we again reprocess the message,it shows the exact error at the channel.
Any ideas why the first error shows up?

Hi, Anu
The most probable it's that your target XML it's not correct because it haven't a correct format.
Please, check your target XML and see
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/465581929734d9e10000000a42189d/frameset.htm
Regards,
Carme

Soap Receiver adpater: HTTP 20 OK, canu2019t parse the document

Hi Everyone,
The scenario is SAP ECC -> PI -> server (third party remote server).
Here the PI has to post the message (payload) which is coming from the SAP ECC to the third party remote server.
We have the soap receiver adapter to send the payload to the remote client system.
When we do the end-to-end testing, in RWB the soap receiver adapter is throwing an error
HTTP 20 OK, canu2019t parse the document
Any idea what might the error or any configuration we missed out.
Thanks,
Lalitkumar.

Hi Stefan,
You mentioned that PI will be waiting response ,
The Web service has to respond an empty SOAP envelope, but it does not return anything.
Itu2019s fine if it is waiting for the response.
But when we logon to the server using different link (that the portal of the server) to which we submit the payload, none of the invoices is seen whenever we submit.
just a basic question, can we use the soap receiver adapter to post the invoices to external server (async scenario)
i had tried with the HTTP receiver adapter too, with that also facing the same problem.
kindly reply to that thread also...
[unable to post the payload|successfully configured http receiver adapter, unable to post the payload;
Thanks,
Lalitkumar.

[IWAF JCA PeopleSoft] **** Error in parsing the input document.

Hi,
I configured Peoplesoft Adapter 10.1.3.1 with Oracle BPEL 10.1.3.1, I am able to invoke BPEL from Peoplesoft using JCA configurtaion. But I am not able to invoke Peoplesoft component interface from BPEL PM, Invoke call fails with following error. Did any one know solution to this issue.
Thanks,
Manish
Tue, 6 Nov 2007 16:40:20.0954 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [info ] [IWAF JCA PeopleSoft] IWAFManagedConnection for PeopleSoft:Peoplesoft has listener registered: com.evermind.server.connector.ConnectionContext@b78555
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [info ] [IWAF JCA PeopleSoft] Local transaction not supported by underlying adapter.
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [info ] [IWAF JCA PeopleSoft] IWAFManagedConnection for PeopleSoft:Peoplesoft dispatch event 2
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [error] [IWAF JCA PeopleSoft] **** Error in parsing the input document.
oracle.xml.parser.v2.XMLParseException: Start of root element expected.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
     at com.iwaysoftware.idom.XmlDocument.parse(XmlDocument.java:120)
     at com.iwaysoftware.idom.XmlDocument.setRootXML(XmlDocument.java:77)
     at com.ibi.afjca.cci.IWAFInteraction.execProcess(IWAFInteraction.java:195)
     at com.ibi.afjca.cci.IWAFInteraction.exec(IWAFInteraction.java:136)
     at com.ibi.afjca.cci.IWAFInteraction.execute(IWAFInteraction.java:93)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:470)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:431)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:416)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:222)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:736)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:371)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3271)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1697)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:184)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:269)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5244)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1083)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:132)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:161)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:499)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:451)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:125)
     at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:455)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:278)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:129)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [error] [IWAF JCA PeopleSoft] SOS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [error] [IWAF JCA PeopleSoft] oracle.xml.parser.v2.XMLElement@1f73ac7
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [error] [IWAF JCA PeopleSoft] EOS !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tue, 6 Nov 2007 16:40:21.0204 IST - Thread[AJPRequestHandler-HTTPThreadGroup-56,5,HTTPThreadGroup] [info ] [IWAF JCA PeopleSoft] IWAFManagedConnection for PeopleSoft:Peoplesoft dispatch event 4

Kris,
I tried your suggestion, but it didn't help. I think the Ci jar file is getting loaded, because when I try to call any other interface whos class files are not included in CI jar file, it gives different error like "Not Authorized (90,6)Failed to execute PSSession request Cannot find Component Interface {LACATION_TABLE} (91,2)".
We verified all the configuration on Adapter and Peoplesoft aerver, every thing seems to be absolutely fine, even I turned on debug log level for adapter but that is not of any use.
I tried searching on the google, it seems many people who used Component Interface Java Classes faced such type of problem, they recommended some peoplesoft configuration, I tried their suggestions as well, but that also didn't work out.
Even though we are using Peoplesoft 8.4 Adapter asks for pstools.properties file whenever the BPEL Process is invoked, this file is there in the adapters lib directory, and jca-app-adapter directory, see below the log.
<2007-11-26 18:33:17,656> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2007-11-26 18:35:13,296> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://192.168.133.164:8888/orainfra/wsil/adapters/applications/CI_PERSONAL_DATA_invoke.wsdl?wsdl [ CI_PERSONAL_DATAPortType::CI_PERSONAL_DATA(input_CI_PERSONAL_DATA,output_CI_PERSONAL_DATA) ] - Using JCA Connection Pool - max size = <unbounded>
<2007-11-26 18:35:13,312> <WARN> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://192.168.133.164:8888/orainfra/wsil/adapters/applications/CI_PERSONAL_DATA_invoke.wsdl?wsdl [ CI_PERSONAL_DATAPortType::CI_PERSONAL_DATA(input_CI_PERSONAL_DATA,output_CI_PERSONAL_DATA) ] - Unable to provide Log4j handle to com.ibi.afjca.cci.IWAFConnectionFactory via <public void setLog4jLogger(org.apache.log4j.Logger logger)> due to: com.ibi.afjca.cci.IWAFConnectionFactory.setLog4jLogger(org.apache.log4j.Logger)
Mon, 26 Nov 2007 18:35:13.0312 IST - Thread[HTTPThreadGroup-59,5,HTTPThreadGroup] [debug] [IWAF JCA] IWAFConnectionFactory:getConnection called with ConnectionSpec:
User :null
Password :null
AdapterName :PeopleSoft
Config :PSOFT9
Mon, 26 Nov 2007 18:35:13.0312 IST - Thread[HTTPThreadGroup-59,5,HTTPThreadGroup] [debug] [IWAF JCA] IWAFConnectionFactory:getConnection called with ConnectionSpec:
User :null
Password :null
AdapterName :PeopleSoft
Config :PSOFT9
Mon, 26 Nov 2007 18:35:13.0312 IST - Thread[HTTPThreadGroup-59,5,HTTPThreadGroup] [debug] [IWAF JCA] IWAFManagedConnectionFactory:createManagedConnection() entered.
Mon, 26 Nov 2007 18:35:13.0312 IST - Thread[HTTPThreadGroup-59,5,HTTPThreadGroup] [debug] [IWAF JCA] setLogWriter() gets called.
07/11/26 18:35:14 PSProperties not loaded from file. Couldn't find file: pstools.properties
07/11/26 18:35:18 PSProperties not loaded from file. Couldn't find file: pstools.properties
07/11/26 18:39:12 PSProperties not loaded from file. Couldn't find file: pstools.properties
07/11/26 18:51:38 PSProperties not loaded from file. Couldn't find file: pstools.properties
Thanks,
manish
Message was edited by:
user604262

Error in parsing the input document

Dear All
When I am trying to fetch data from SAP thro OracleAS with BPEL , I am getting this error. I dont know whee i did worng, Pl. clarify me if any body know this....
<summary>
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - WSIF JCA Execute of operation 'GetDetail' failed due to: Error in parsing the input document.; nested exception is:
javax.resource.ResourceException: Error in parsing the input document.
</summary>

Sir,
From the JCA Log I got the below message
Tue, 1 Jul 2008 18:30:43.0220 IST - Thread[HTTPThreadGroup-56,5,HTTPThreadGroup] [error] [IWAF JCA SAP] Error in processing the input document.
getMessage(): java.lang.Exception: Function module inputVariable does NOT exist.
int getError(): Server
getAdapterCode(): null
getVendorThrowable(): null
Also i am not giving my input in xml format. when i am running the bpel console its asking for input in html format , there im giving my input, after urs question only im doubting on my input. how can i give my input in which format, how to defin that format. pl. give me yours views and also i will try myself.

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>
          <b> <ZZAD_STREET_CO>Torre B1 - B Unimev</ZZAD_STREET_CO></b>
              <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>
           <b><STREET>Torre B1 - B Unimev</STREET></b>
              <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

Could not parse XMBMessage due to Can't parse the document

*Dear all,*
*i have a SOAP to RFC Scenario. XML Validation by Adapter is turned on in SenderAgreement.*
*XSD Files are placed in the correct directory. Incoming requests are validated. However,*
*it seems that responses produce an error in the soap adapter.*
*This is the error message i am getting:*
+SOAP:Fault>+
         +<faultcode>SOAP:Server</faultcode>+
         +<faultstring>Server Error</faultstring>+
         +<detail>+
            +<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">+
               +<context>XIAdapter</context>+
               +<code>ADAPTER.JAVA_EXCEPTION</code>+
               +<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage due to Can't parse the document+
+     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1173)+
+     at sun.reflect.GeneratedMethodAccessor678.invoke(Unknown Source)+
+     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+     at java.lang.reflect.Method.invoke(Method.java:592)....+
*In SXMB_MONI my response includes the following passages*
+- 
+<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RS_OUT</Trace>+
+<Trace level="3" type="T">Skip Inbound Validation =</Trace>+
+<Trace level="3" type="T">Skip Outbound Validation =</Trace>+
+<Trace level="3" type="T">Area = XML_VALIDATION_OUT</Trace>+
+<Trace level="1" type="T">Reading sender agreement</Trace>+
+<Trace level="3" type="T">Validation Mode = Validation by Adapter</Trace>+
+<Trace level="1" type="T">Outbound validation of response takes place</Trace>+
+<Trace level="3" type="T">Interface Name = SI_xxx_xxx_xxx_Sync_Outbound</Trace>+
+<Trace level="3" type="T">Interface Namespace = http://xxx.de/xxx</Trace>+
+<Trace level="3" type="T">Software Component Version = D390B9E10A6B11DF8C15C7540A484C06</Trace>+
+<Trace level="2" type="T">Java Validation Service Call</Trace>+
+<Trace level="1" type="T">System error occurred during XML validation</Trace>+
+<Trace level="1" type="E">CL_XMS_PLSRV_VALIDATION~ENTER_PLSRV</Trace>+
+</Trace>+
+<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />+
+- 
+<Trace level="3" type="T">Persisting message Status = 023</Trace>+
+<Trace level="3" type="T">Message version 009</Trace>+
+<Trace level="3" type="T">Pipeline CENTRAL</Trace>+
+</SAP:Trace>+
*I see the following error message:*
+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>+
+- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XML_VALIDATION_OUT">CX_XMS_SYSERR_VALIDATION</SAP:Code>
<SAP:P1>Schema xxx.response.xsd not found in J:\usr\sap\xxx\SYS\global\xi\runtime_server\validation\schema\00000000000000000000000000000000\ u00D3u00B9u00E1 k u00DF u00C7T HL \SI_xxx_xxx_xxx_Sync_Outbound\urnsap-comdocumentsaprfc~functions\xxx.response.xsd (J:\usr\sap\xxx\SYS\global\xi\runtime_server\validation\schema)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>not used at the moment.</SAP:AdditionalText>
<SAP:Stack>System error occurred during XML validation</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
There seems to be an error in the adapter trying to validate the response. Does anyone has a clue as to why ?

Since i cannot get i running, i helped myself using a java mapping, that i packaged into a jar
along with the xsd files. See code below:
import com.sap.aii.*;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.BufferedReader;
import java.io.OutputStream;
import java.io.OutputStreamWriter;
import java.io.UnsupportedEncodingException;
import java.io.InputStreamReader;
import java.io.Reader;
import javax.xml.transform.sax.SAXResult;
import javax.xml.transform.sax.SAXSource;
import javax.xml.transform.stream.StreamSource;
import javax.xml.validation.Schema;
import javax.xml.validation.SchemaFactory;
import javax.xml.validation.Validator;
import org.xml.sax.InputSource;
import org.xml.sax.SAXException;
@SuppressWarnings("unused")
public class CustomValidator extends AbstractTransformation {
     public void transform(TransformationInput arg0, TransformationOutput arg1)
               throws StreamTransformationException {
          Validator validator;
          InputStreamReader insr;
          String inputPayloadString;
          try {
               // Trace
               getTrace().addInfo("com.xxx.pi.mapping.validation.CustomValidator called");
               InputStream inputPayloadStream = arg0.getInputPayload()
                         .getInputStream();
               insr = new InputStreamReader(inputPayloadStream);
               InputHeader inpHeader = arg0.getInputHeader();
               String intfName = inpHeader.getInterface();
               getTrace().addInfo("Interface Name is :" + intfName);
               String xsdName = "";
               if (intfName
                         .equalsIgnoreCase("SI_xxx_Sync_Outbound")) {
                    xsdName = "Z_xxx.xsd";
               if (intfName.equalsIgnoreCase("SI_xxx")) {
                    xsdName = "Z_xxx.xsd";
               if (intfName
                         .equalsIgnoreCase("SI_xxx_Sync_Outbound")) {
                    xsdName = "Z_xxx.xsd";
               if (intfName
                         .equalsIgnoreCase("SI_xxxx_Sync_Outbound")) {
                    xsdName = "Z_xxx.xsd";
               getTrace().addInfo("Using schema: " + xsdName);
               if (xsdName.equals(""))
                    throw new StreamTransformationException("Schema für "
                              + intfName + " nicht gefunden.");
               BufferedReader reader = new BufferedReader(new InputStreamReader(
                         getClass().getResourceAsStream(
                                   "/com/xxx/pi/mapping/xsd/" + xsdName)));
               // prepare document validator:
               String schemaLang = "http://www.w3.org/2001/XMLSchema";
               SchemaFactory jaxp = SchemaFactory.newInstance(schemaLang);
               Schema schema = jaxp.newSchema(new StreamSource(reader));
               validator = schema.newValidator();
          } catch (SAXException saxe) {
               throw new StreamTransformationException(saxe.getMessage());
          // validate
          try {
               SAXSource source = new SAXSource(new InputSource(insr));
               validator.validate(source);
          } catch (Exception e) {
               getTrace().addInfo(e.getMessage());
               String trace = e.getMessage();
               throw new StreamTransformationException(trace, e.getCause());
          // Write the response
          try {
               inputPayloadString = convertStreamToString(arg0.getInputPayload()
                         .getInputStream());
               arg1.getOutputPayload().getOutputStream()
                         .write(inputPayloadString.getBytes("UTF-8"));
               getTrace().addInfo("Schema Validierung erfolgreich !");
          } catch (Exception e) {
               throw new StreamTransformationException(e.getMessage());
     // helper to convert to String
     private static String convertStreamToString(InputStream in) {
          StringBuffer sb = new StringBuffer();
          try {
               InputStreamReader isr = new InputStreamReader(in);
               BufferedReader reader = new BufferedReader(isr);
               String line;
               while ((line = reader.readLine()) != null) {
                    sb.append(line);
          catch (Exception exception) {
          return sb.toString();

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

Error while generating the Document... Bursting Status Report

Hey all,
I am getting some errors in a production environment when trying to burst out some invoice data.
This process has been pretty robust and out of 1000+ invoices a day, I can only find 4 that are failing regularily.
Why am I mentioning?, just to show that I am thinking this is a data issue, but just cannot see anything that stands out.
I can take the xml output and run it through my development suite on my local machine and all runs fine.
Just when it is running live through the db is when it fails.
Here is the Bursting output that shows the error....
<?xml version="1.0" encoding="UTF-8"?>
<BURS_REPORT>
<REQUESTID>27044820</REQUESTID>
<PARENT_REQUESTID>27044726</PARENT_REQUESTID>
<REPORT_DESC>Invoice Print Selected Invoices</REPORT_DESC>
<OUTPUT_FILE>[$OUT_DIR]/o27044820.zip</OUTPUT_FILE>
<DOCUMENT_STATUS>
<KEY></KEY>
<OUTPUT_TYPE>pdf</OUTPUT_TYPE>
<DELIVERY></DELIVERY>
<OUTPUT></OUTPUT>
<STATUS>fail</STATUS>
<LOG>Error while generating the Document...</LOG>
</DOCUMENT_STATUS>
</BURS_REPORT>
The problem is that this output doesn't necessarily help, nor can I find any hints in the OPP logs.
So... the question becomes...
Any ideas on where I can look to resolve this issue?+
Or where I can find any clues at, that would possible point at the issue?+
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
BI Publisher 5.6.3
Thanks
Hayden,

Tim,
Thanks for the suggestion, always seems to slip my mind that the Bursting Report has debug on it.
As far as what is generating the XML, it is oracle's standard, only slightly modified ... ;), invoice generating report, RAXINV_SEL.
Well RAXINV_SEL, or RAXINV_NEW, doesn't matter, same code, that is the executable.
I have turned on the debug, for both the source xml and the burst request, and unfortunately, still nothing stands out to me.
I was really expecting to see something in the burst log, pasted at the bottom...
but, it yet avoids me.
If I had to guess, I would bet the user went, in our terminology, "slashwit crazy", or example "model /w options", in some description.
But can't seem to find which field it is blowing up on, since we are catching these special characters in several places already, and slashwit is littered throughout the output.
I was also looking in the bursting control file for the special xml tags identified there, as those would require no slashes. But those are all clean.
Hayden,
XML Publisher: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XDOBURSTREP module: XML Publisher Report Bursting Program
Current system time is 21-SEP-2009 10:43:12
XML/BI Publisher Version : 5.6.3
Request ID: 27048106
All Parameters: ReportRequestID=27044726:DebugFlag=Y
Report Req ID: 27044726
Debug Flag: Y
Updating request description
Updated description
Retrieving XML request information
Node Name:{node}
Preparing parameters
null output =/u007/app/applmgr/{instance}/out/{instance}/o27048106.out
inputfilename =/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
Data XML File:/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
Set Bursting parameters..
Temp. Directory:/u007/app/applmgr/{instance}/temp
[092109_104315337][][STATEMENT] Oracle XML Parser version ::: Oracle XDK Java 9.0.4.0.0 Production
[092109_104315340][][STATEMENT] setOAProperties called..
Bursting propertes.....
{burstng-source=EBS, font.Free 3 of 9.normal.normal=truetype./usr/java/jre/lib/fonts/FREE3OF9.TTF, font.Times New Roman.normal.normal=truetype./usr/java/jre/lib/fonts/TIMES.TTF, system-temp-dir=/u007/app/applmgr/{instance}/temp, font.Arial.italic.normal=truetype./usr/java/jre/lib/fonts/ARIALI.TTF, user-variable:cp:parent_request_id=27044726, user-variable:cp:application_short_name=XDO, font.Courier New.normal.bold=truetype./usr/java/jre/lib/fonts/COURBD.TTF, font.Times New Roman.normal.bold=truetype./usr/java/jre/lib/fonts/TIMESBD.TTF, user-variable:cp:request_id=27048106, font.Arial.normal.normal=truetype./usr/java/jre/lib/fonts/ARIAL.TTF, font.Courier New.normal.normal=truetype./usr/java/jre/lib/fonts/COUR.TTF, user-variable.OA_MEDIA=http://diierp.corio.com:8002/OA_MEDIA, font.Courier New.italic.bold=truetype./usr/java/jre/lib/fonts/COURBI.TTF, user-variable:cp:org_id=83, user-variable:cp:DebugFlag=Y, font.Times New Roman.italic.bold=truetype./usr/java/jre/lib/fonts/TIMESBI.TTF, user-variable:cp:responsibility=51270, font.Arial.italic.bold=truetype./usr/java/jre/lib/fonts/ARIALBI.TTF, font.Courier New.italic.normal=truetype./usr/java/jre/lib/fonts/COURI.TTF, user-variable:cp:user=HAYDEN, user-variable:cp:reportdescription=Invoice Print Selected Invoices, user-variable:cp:language=en, font.Times New Roman.italic.normal=truetype./usr/java/jre/lib/fonts/TIMESI.TTF, user-variable:cp:ReportRequestID=27044726, user-variable:cp:locale=en-US, user-variable:cp:territory=US, font.Arial.normal.bold=truetype./usr/java/jre/lib/fonts/ARIALBD.TTF}
Start bursting process..
Bursting process complete..
Generating Bursting Status Report..
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 27048106 on node {node} at 21-SEP-2009 10:43:19.
Post-processing of request 27048106 completed at 21-SEP-2009 10:43:20.
Finished executing request completion options.
Concurrent request completed
Current system time is 21-SEP-2009 10:43:20
---------------------------------------------------------------------------

How can I parse the document in WebI using sdk?

I wanna to parse the document in WebIntelligence using sdk. My question is :
1) By which sdk, I can parse the document. 'Report Application Server SDK' ?
2) I wanna to parse the 'Self-Defined SQL' and 'Query' components of the document. Can the sdk support this request ?
My enviroment is BO XI Release 2.
Thanks all.

Hi shao,
1) By which sdk, I can parse the document. 'Report Application Server SDK' ?
'Report Application Server SDK' is For Crystal reports so for WebIntelligence or DesktopIntelligence Report it is "Report Engine SDK".
Apart from this if you want to do more on these reports "BusinessObjects Enterprise SDK" can be used.
You can get more information on below link for XI R2.
http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/devsuite.htm
For question 2,
I am not sure about it but Report Engine SDK provides classes and interface of Data Providers.
i.e. Building and Editing Data Providers and Working with Recordsets.
Also you can have look on
Report Engine SDK's
Interface "Query"
Hope these helps you.
Thanks,
Praveen.

Bursting Program errors with "Error while generating the Document"

Hello Folks
Here is my bursting control file
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:globalData location="stream">
</xapi:globalData >
<xapi:request select="/XMLEXCEL1/LIST_G_Q0">
<xapi:delivery>
<xapi:email server="mycompany.com" port="25" from="[email protected]"
reply-to ="[email protected]">
<xapi:message id="1234" to="[email protected]"
attachment="true" content-type="html/text"
subject="Employee Report for Empno"> Dear
Please review the attached document</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document key="123" output-type="XLS" delivery="1234"
output="XMLEXCEL1" >
<xapi:template type="RTF" location="xdo://AR.XMLEXCEL1.en.00/?getSource=true">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
this is the output of bursting status report:
<?xml version="1.0" encoding="UTF-8"?>
<BURS_REPORT><REQUESTID>40403415</REQUESTID>
<PARENT_REQUESTID>40403339</PARENT_REQUESTID>
<REPORT_DESC>XMLEXCEL1</REPORT_DESC>
<OUTPUT_FILE>/opt/local/application/orafin/applmgr/out/outfaud/S1759.zip
</OUTPUT_FILE>
<DOCUMENT_STATUS>
<KEY>123</KEY>
<OUTPUT_TYPE>XLS</OUTPUT_TYPE>
<DELIVERY></DELIVERY>
<OUTPUT>
</OUTPUT>
<STATUS>fail</STATUS>
<LOG>Error while generating the Document...</LOG>
</DOCUMENT_STATUS>
</BURS_REPORT>
Can anyone help on this please.

can anyone help me?

Error Message "Error while Opening the Document"

Hi Friends,
I have a problem while opening the SFP transaction and Clicking on the Layout Tab the SAP System is giving an error message saying "Error while Opening the Document".
I have tried testing on several systems like IDES, ERP, Retail systems. But it is giving me same error. Is this the problem with ADOBE LIVECYCLE DESIGNER?
And when I click on the Performance Assistant it has given me some information:
Error while opening document
Message no. SOFFICEINTEGRATION143
Diagnosis
An error occurred in the desktop application while opening a document.
Friends can you help me in solving this problem.
Thanking yoy in Advance
Pradeep Goli

Pradeep,
Maybe Live Cycle Designer has not been uninstalled correctly from your system. So goto the following lcaotions and remove the Designer folder if you find them:-
C:\Program Files\Adobe
C:\Documents and Settings\<your-username>\Application Data\Adobe\
Alternatively try installing Live Cycle Designer on some other machine in your network and see if you encounter the same error.
Similar thread for reference : Error - Adobe Live Cycle designer
Chintan

Exchange Office Web Apps Preview Does not work in OWA. An error occurred while the document preview was being created

Hi,
I have managed to configure intergration between Office Web App server 2013 and Exchange 2013 OWA.
I have created a test users Test1 and Test 2. I have given full access on Test2 mailbox to user test 1.
When I login to owa for user test1 and preview the attachment it works fine.
However when I use "Open another mailbox" in OWA and open test2 mailbox and try to preview the attachments in test2 inbox it errors as
" An error occurred while the document preview was being created. Please try again later " as follows
I am new to office web apps server 2013 and implemented it first time. Can anyone suggest resolutions or troubleshooting ?

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Does the error appear when you directly access test 2 mailbox through OWA?
2. Check if there is 141 error in your event log.
3. Check whether Office web app server connects with Exchange server when the issue happens.
Access the URL: https://hostname/hosting/discovery
4. Grant full access permission again and check the result.
For more information about Office web app integration with Exchange, please refer to the following article:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-2013-office-web-apps-server-integration.html
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Receiver SOAP channel error-- Cant parse the document; HTTP 200 OK

Similar Messages

Maybe you are looking for