Exception when calling ABAP Proxy modelled in SAP PI: CL_SOAP_RUNTIME_ROOT

Hi,
We have a scenario where we:
1. Modell an interface in SAP PI
   This interface contains a complex type from a different namespace
2. Use it to create an ABAP proxy in backend system
3. Configure it with SOAManager
4. Call the ABAP proxy ws directly from a third-party system (biztalk)
We're currently testing calling the ABAP proxy from soapUI, but get a strange exception thrown by the SOAP framework in ABAP backend.
The test in soapUI is setup by importing the WSDL acquired from SOAMANAGER.
The error message we in the SOAP response is:
CX_SY_REF_IS_INITIAL:Exception CX_SOAP_ROOT occurred
(program: CL_SOAP_RUNTIME_ROOT==========CP, include: CL_SOAP_RUNTIME_ROOT==========CM004, line: 130)..
An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally,
nor declared in a RAISING clause.Dereferencing of the NULL reference
It is a very low level error from the CL_SOAP_RUNTIME_ROOT program and not a descriptive error message at all.
We've checked the user and the authorizations it has, we've redone the SOAManager config but the problem persists.
We find no dumps in the ABAP proxy since the request never reaches it.
For a limited time I'll make WSDL and SOAP response available
WSDL (some values anonymized) available at http://dl.dropbox.com/u/4379928/SOAP/project.wsdl
Complete SOAP response is available at http://dl.dropbox.com/u/4379928/SOAP/soap_data.xml
Any ideas on where to look?

Hi,
We've now managed to implement a workaround.
The workaround was to create the endpoint in PI as well.
So that the traffic goes from third-party solution->PI-> WS-enabled ABAP Proxy
When we did this initially, we got some errors related to the asynch method of this call, but this was resolved by changing the channel from "best effort" to "Guaranteed delivery". 
Still we don't know what the root cause of the initial problem was, but we assume it is related to the asynch nature of the service (though we have other asynch proxies that work without problems).
Regards
Dagfinn

Similar Messages

  • How to call abap proxy at run time?

    hello frnds,
    i m working on a scenario in which whenever Invoice is saved in SAP R/3 at that time same data should go to Oracle DB. i m using ABAP proxy on SAP R/3 side and JDBC receicver adapter on oracle side of XI.
    so to post data i need to call ABAP Proxy whenever invoice is saved.. i have tried to find out save event for invoice but not able to get... can anybody tell me the solution that how i can call proxy at run time?
    thanx in advance.
    Regards,
    Hetal.....

    Hi Audumbar,
    Check these ...
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    /people/vanita.thareja2/blog/2006/05/23/bpm-sending-message-asynchronously-and-getting-the-response-from-synchronous-system-using-abap-proxies
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    cheers,
    Prashanth
    P.S Please mark helpful answers

  • Abap report for calling abap proxy?

    why do we need  to write abap report for calling abap proxy? i mean what's the use of abap report and what are the things inside the report ...please give me details about abap report.

    Hi,
    In SPROXY for your outbound interface you generate the proxy class.
    The ABAP report is used to fill the data from the ABAP tables and then trigger the call to XI using this class.
    Look into the code in this blog and check what is done,. The data is filled in the report and then the call is made to XI using an object of the class created in SPROXY using the EXECUTE_ASYNCHRONOUS method.
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    Regards
    Bhavesh

  • MSS - Business Event Details - Error Unexpected Exception when Calling RFC

    Dear Experts,
    Manager is getting the Error "Unexpected Exception when Calling RFC from Profile Application 'Business Event' when he tries to get the Training history of ONE employee in MSS. However, he is getting the details for the other employees of his department.
    Any inputs on this?
    Thank you.

    I believe it is our custom iView that is incorrect.

  • CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception when calling Web Service

    I have created a Web Service on our Sandbox SAP server and am attempting to call it from our DEV SAP Server.  The returning structure contains date fields that sometimes are null. A null date field in SAP is equal to 00000000.
    When I call the Web Service and the date values are null, I get the following exception:
    CX_SY_CONVERSION_NO_DATE_TIME:XSLT exception.An error occurred when deserializing in the simple transformation program /1SAI/TXS982F8A669D1A54B7AD0D.
    Value 0000-00-00 is not a valid date in accord with the XML format for ABAP
    I would not expect to see this type of error, sense the call is between two SAP systems. 
    Is there anyway to fix this without moving space to any null date field in the function module?
    That's kind of annoying to do sense I have so many date fields.
    Example:
    IF date1 IS INITIAL.
        MOVE space TO date1.
    ENDIF.
    IF date2 IS INITIAL.
        MOVE space TO date2.
    ENDIF.
    IF date3 IS INITIAL.
        MOVE space TO date3.
    ENDIF.
    IF date4 IS INITIAL.
        MOVE space TO date4.
    ENDIF.

    Hi All,
    I got a solution for this exception. Hope it will help to all facing this problem.
    I was using proxy created from SE80.
    In my proxy for exporting parameters of methods I have changed all date fields.
    Earlier it was having Techn. type under Attributes of fields : XSDDATE_D. I chnaged this to DATS.
    It worked fine.
    Manish

  • How to handle exceptions in sender ABAP Proxy

    Hi Experts,
       I have a synchronous scenario.
       SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
       In system 'A', a function module calls the ABAP Proxy method.
       My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
    For example:
    Exception in PI:
      <SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:P1/><SAP:P2/>
    <SAP:P3/><SAP:P4/>
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace=""/>
    <SAP:Stack/>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    In the calling function module:
    Try
    Call to proxy-> method
    Catch cx_ai_system_fault INTO v_o_fault.
           v_err_msg1 = v_o_fault->GET_TEXT( ).
           v_err_msg2 = v_o_fault->errortext.
           v_err_msg3 = v_o_fault->code.
    Endtry.
    Here I get value "MESSAGE.GENERAL" for  v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
    I want to capture the info available under <SAP:AdditionalText>. How to get that?
    Please help!
    Thanks & Regards
    Gopal

    >
    gopalkrishna baliga wrote:
    > Hi Experts,
    >
    >    I have a synchronous scenario.
    >
    >    SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
    >
    >    In system 'A', a function module calls the ABAP Proxy method.
    >
    >    My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
    >
    >  For example:
    >
    > Exception in PI:
    >
    >   <SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    > <SAP:Category>XIAdapterFramework</SAP:Category>
    > <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    > <SAP:P1/><SAP:P2/>
    > <SAP:P3/><SAP:P4/>
    > <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
    > <SAP:ApplicationFaultMessage namespace=""/>
    > <SAP:Stack/>
    > <SAP:Retry>M</SAP:Retry>
    > </SAP:Error>
    >
    > In the calling function module:
    > Try
    >  Call to proxy-> method
    >
    >  Catch cx_ai_system_fault INTO v_o_fault.
    >        v_err_msg1 = v_o_fault->GET_TEXT( ).
    >        v_err_msg2 = v_o_fault->errortext.
    >        v_err_msg3 = v_o_fault->code.
    > Endtry.
    >
    > Here I get value "MESSAGE.GENERAL" for  v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
    >
    > I want to capture the info available under <SAP:AdditionalText>. How to get that?
    >
    > Please help!
    >
    > Thanks & Regards
    > Gopal
    Hi Gopal,
    Maybe the exception is CX_SY_APPLICATION_FAULT, or you can catch by BPM in PI and send back to proxy like a message response.

  • Netweaver throwing following exception when calling the ProductionOrder WS

    Hi,
    when calling the ProductionOrder web service I get the following exception from the system:
    nested exception is: com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe00103e] ) in rollback.
    The system was migrated from Netweaver CE 7.1 SP4 to SP5 before the error started to occur.
    Any ideas how to fix this? Start/Stopping ME didn't do the trick.
    Kind Regards,
    Christoph Mertins

    Yes the stack trace is:
    System exception 
    [EXCEPTION]
    javax.ejb.EJBException: nested exception is: com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe0013ffffffb6] ) in rollback.
    com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe0013ffffffb6] ) in rollback.
    at com.sap.engine.services.ts.jta.impl.TransactionImpl.rollback(TransactionImpl.java:921)
    at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:486)
    at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:296)
    at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy3782.create(Unknown Source)
    at com.sap.me.productdefinition.wserpimpl.productionOrder.ProductionOrderPersister.createOrUpdate(ProductionOrderPersister.java:133)
    at com.sap.me.productdefinition.wserpimpl.GenericVOServiceImpl.createOrUpdate(GenericVOServiceImpl.java:57)
    at com.sap.me.productdefinition.wserpimpl.productionOrder.ProductionOrderServiceHandlerAdapter.updateProductionOrder(ProductionOrderServiceHandlerAdapter.java:51)
    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:592)
    at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
    at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
    at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
    at com.visiprise.frame.proxy.AdviceInterceptor.intercept(AdviceInterceptor.java:45)
    at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
    at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
    at $Proxy3884.updateProductionOrder(Unknown Source)
    at com.sap.me.production.ws.ProductionOrderService.updateProductionOrder(ProductionOrderService.java:53)
    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:592)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:96)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:525)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:494)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:260)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:178)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:114)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:72)
    at com.sap.engine.services.webservices.servlet.SOAPServletExt.doPost(SOAPServletExt.java:90)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
    at com.sap.me.webservice.ClearServiceContextFilter.doFilter(ClearServiceContextFilter.java:28)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@aa1bf8e has already been closed.
    at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.throwBaseResourceException(LocalTXManagedConnectionImpl.java:89)
    at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.rollback(LocalTXManagedConnectionImpl.java:389)
    at com.sap.engine.services.ts.jta.impl.TransactionImpl.rollback(TransactionImpl.java:813)
    ... 83 more
    Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@aa1bf8e has already been closed.
    at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
    at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
    at com.sap.sql.jdbc.vendor.VendorConnectionHandle.validate(VendorConnectionHandle.java:383)
    at com.sap.sql.jdbc.vendor.VendorConnectionHandle.setAutoCommit(VendorConnectionHandle.java:38)
    at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.rollback(LocalTXManagedConnectionImpl.java:386)
    ... 84 more

  • Response message error in queue when using ABAP proxy

    I am using an abap proxy for the first time, and some of the response messages are getting stuck in the sender's (R/3) inbound queue.  To resolve them, I have to either reset the status or execute the LUW.  Sometimes, this doesn't even work. 
    Here is my "asynchronous" scenario:
    R/3 -> <proxy> -> PI -> <file adapter> -> File
    The R/3 system that I'm using has not used PI before, so I'm thinking something is missing from the set-up on the R/3 side.  On the errors I finally do get to process, I get the following error in the SXMB_MONI on the sender (R/3) side (the PI SXMB_MONI shows successful).  Can someone help me understand what a response message is and how it is different from an acknowledgement?  Also, help me to understand what could be causing the response messages to get stuck in the R/3 queue.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Integration Server -->
       - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
        <SAP:Context />
        <SAP:Code p1="MessageId"
                          p2="4962B2EDB60A003BE1008000A2844D1A"
                          p3="00000000000000000000000000000000"     
                          p4="">PROTOCOL.WRONG_HEADER_IN_RESPONSE</SAP:Code>
        <SAP:Text language="EN">Response message header contains the value 00000000000000000000000000000000 in element MessageId instead of the expected value 4962B2EDB60A003BE1008000A2844D1A</SAP:Text>
      </SAP:ErrorHeader>

    Ultimate testing tool for services is soapUI (Freeware)
    http://www.soapui.org/
    If you can invoke your service from soapUI and you receive a response, then PeopleSoft is working fine and the request handling in the calling system is incorrect.
    Try downloading soapUI and try invoking your service (not that a fan of SendMaster).
    Hakan

  • Call ABAP-Proxy with SOAP adapter?

    Hi all,
    for a PI7.1-scenario I would like to use the Lookup-API in mapping. As I know I can use either RFC or SOAP channels, however I would rather call an ABAP-Proxy in my backend system instead.
    So my question is: Is it technically possible to use the SOAP-adapter to call an ABAP-Proxy?
    Your help would be appreciated, best regards
    David

    Hi Stefan,
    Interesting answer here and one that has got me curious. Hope you can help.
    1. When you say it is going to be possible to call a ABAP proxy using a  UDF in the mapping of XI ( Lookup ), would it be using the WS Adapter of PI 7.1?
    2. If 1 is yes, is there a new API code to do this, or is it the same lookup code as used previously in XI 3.0 and PI 7.0 Days?
    3. If 1 is no, can you explain maybe a little more on how this would be possible using the standard SOAP adapter of XI?
    Thanks a bunch.
    Regards
    Bhavesh

  • Exception when calling SOAP Lookup-API async

    Hello,
    i'm calling a SOAP-Comunication Channel (Lookup-API) out of my MessageMapping. The WebService Called is <u>asynchron</u> because i just send some data and i don't care about the result. The WebService itselfs is implemented on our XI. In other words: we call us self.
    In order to call my WebService asynchronous, i added <i>&QualityOfService=ExactlyOnce</i> at the end of the URL. The SOAP-Action is:
    <i>http://sap.com/xi/WebService/soap1.1</i>
    The problem is: the WebService works perfekt! But: in my mapping i get
    nevertheless the following exception:
    Errorcom.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_Receiver_SetIdocStatusAsync (Party: , Service: SetIdocStatus, Object ID: f6b1ce38e9fa332cba4eb1a6f0a3e17f) null com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel SOAP_Receiver_SetIdocStatusAsync (Party: , Service: SetIdocStatus, Object ID: f6b1ce38e9fa332cba4eb1a6f0a3e17f) null at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:96) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:141) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:74) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.af.service.api.AFException at com.sap.aii.af.service.api.AdapterAccess.call(AdapterAccess.java:122) at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:87) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:141) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:74) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    The problem is: i don't know how to check for the HTTP-Header, because
    my call
    <i>SOAPOutPayload = accessor.call(payload);</i>
    throws the mentioned exception, even though it works behind the scene.
    Is it possible to check for the HTTP-Response-Code in the catch block?
    We want to avoid an synchronous scenario because we don't need the result and the WebService is rather slow.

  • ABAP PROXY CONNECTION TO SAP/XI

    Hi,
    I have the following scenery: Abap Proxy -> XI->RFC. 
    This abap proxy is installed in the enviroment R/3 in the client 041 and client 210. 
    In the client 041 it is executed with success. In the customer 210 when I execute the program abap a login screen appears in SAP/XI. Typing the login works. 
    The subject is: why in the enviroment cliente 210 does the login screen appear when I execute the program abap and in the client 041 not? 
    I enter in the sxmb_moni and appears the following in the client 210 
    <? xml version = "1.0" encoding = "UTF-8" standalone = "yes"?>  
    - <!--Entrance message  
      -->  
    - <SAP:ErrorHeader xmlns:SAP = "http://sap.com/exchange/MessageFormat"> 
      <SAP:Context />  
      <SAP:Code p1 = "401" p2 = "Unauthorized" p3 = "" p4 = ""> HTTP.HTTP_STATUS_CODE_NEQ_OK </ SAP:Code>  
      <SAP:Text language = "EN">HTTP status code 401: Unauthorized </ SAP:Text>  
      </ SAP:ErrorHeader>

    Hi Sergio,
    When you execute the program abap a login screen appears in SAP/XI. Typing the login works. But It gives error
    HTTP status code 401: Unauthorized
    Because it is using your userID and trying to execute it,
    But it is not having enough authorization.
    Go and check the entry for Integration server in
    Go to SXMB_ADM
    Go to Integration engine Configuration
    Check the Integration server Entry -
    It must be
    http://server:port/sap/xi/engine?type=entry
    The solution is make a RFC destination of type HTTP for XI Integration server
    with Target host - host
    service - http port (like 8000)
    Path prefix - /sap/xi/engine/?type=entry
    And in the logon/security Tab, enter the user name and password for user XIAPPLUSER,
    And again Go to SXMB_ADM
    Go to Integration engine Configuration
    Check the Integration server Entry -
    change it to
    dest://<RFCDESTNAME that you have created>
    This way it will not ask for login and XIAPPLUSER will
    have enough permission to execute it.
    Regards,
    Vijay

  • Scripting API: Com exception when calling Session.Record

    Hi,
    I'm communicating with SAP Scripting API Com-Object from my Net application.
    When the Scripting events are disable in server side (by setting sapgui/user_scripting_disable_recording=TRUE in the server profile see Note 692245) ans i try to set the GuiSession.Record property to true i recieve a COM exception.
    System.Runtime.InteropServices.COMException (0x80010105): The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
    at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
    at SAPFEWSELib.ISapSessionTarget.set_Record(Boolean )
    My question is - is this is the expected behavior? (I wouldn't expect exception when mode is disabled).
    Thanks,
    Dror.

    The problem is: i don't know how to check for the HTTP-Header, because
    my call
    <i>SOAPOutPayload = accessor.call(payload);</i>
    throws the mentioned exception, even though it works behind the scene.
    Is it possible to check for the HTTP-Response-Code in the catch block?
    We want to avoid an synchronous scenario because we don't need the result and the WebService is rather slow.

  • NO_PERMISSION Exception when calling secured EJB-methods

    In WL6.1, I have an Ejb with secured methods. The (Swing) client application accesses the Ejb through rmi-iiop using the JDK1.3.1 Orb.
    Unfortunately, it seems that the caller identity (which was supplied in the InitialContext lookup) is not propagated
    to the server: any call to a secured method
    fails with a CORBA NO_PERMISSION Exception.
    Non secured methods work fine.
    Using the t3 protocol the program also works fine, but that would require
    the 25Mb weblogic.jar on all clients,
    which is unattainable for us.
    Any ideas how this situation can be corrected?
    -Allard Siemelink

    I am still getting the NO_PERMISSION Exception when using "weblogic.jndi.WLInitialContextFactory".
    We use Sun's JRE, version 1.3.1_01.
    Am I forgetting something?
    My code is as follows:
    InitialContext context = null;
    try {
    Hashtable ht = new Hashtable();
    ht.put(InitialContext.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    ht.put(InitialContext.PROVIDER_URL, "iiop://localhost:80");
    ht.put(InitialContext.SECURITY_PRINCIPAL, "system");
    ht.put(InitialContext.SECURITY_CREDENTIALS, "system_password");
    context = new InitialContext(ht);
    Object objHome = context.lookup(EJB_NAME);
    MyHome myHome = (MyHome)PortableRemoteObject.narrow(objHome, MyHome.class);
    MyRemote myRemote = myHome.create();
    //NEXT LINE Crashes when method is secured:
    myRemote.securedMethod();
    finally {
    if (context!=null) context.close();
    Andy Piper <[email protected]> wrote:
    Allard Siemelink <[email protected]> writes:
    In WL6.1, I have an Ejb with secured methods. The (Swing) client applicationaccesses the Ejb through rmi-iiop using the JDK1.3.1 Orb.
    Unfortunately, it seems that the caller identity (which was suppliedin the InitialContext lookup) is not propagated
    to the server: any call to a secured method
    fails with a CORBA NO_PERMISSION Exception.Make sure you are using WLInitialContextFactory and not
    CNCtxFactory. Only the former will give you security.
    andy

  • FILE.IO.PERMISSION and SOCKET.PERMISSION when calling jdev proxy from DB

    Hello everybody,
    i deployed a webservide proxy (made in jdev 10.1.3.2) to an oracle 10gR2 database. Invoking this proxy works very well when calling it (as a procedure in the database) on the same machine as the DB is running.
    But when trying to invoke the procedure remote on the DB-server from another pc i get 2 error messages (randomly):
    java.security.AccessControlException: the Permission (java.net.SocketPermission 192.168.20.1:1521 connect,resolve) has not been granted to VECOZO. The PL/SQL to grant this is dbms_java.grant_permission( 'VECOZO', 'SYS:java.net.SocketPermission', '192.168.20.1:1521', 'connect,resolve' )
    java.security.AccessControlException: the Permission (java.io.FilePermission \\WEBFS01\WEBFS01_Vecozo\Temp\Acc\MAY07 read) has not been granted to VECOZO. The PL/SQL to grant this is dbms_java.grant_permission( 'VECOZO', 'SYS:java.io.FilePermission', '\\WEBFS01\WEBFS01_Vecozo\Temp\Acc\MAY07', 'read' )
    I gave this permissions in the sys schema to the vecozo schema following the example the error produces for me, but it doesnt work! When i grant socketpermissions on the port secified by the error and i run the proxy again the db comes up with the same error, only with a different port number. I'm getting crazy here. Also the granting of the file.io permission seems to have no result.
    What is strange is that it all works when invoking the proxy locally (from the pc as where the db is running). I think this is because locally you dont need socketpermissions (as sockets are primarily for communication with other pc's). Furthermore i did not even grant the file permission when working locally in my testenvironmentand it all worked just fine. so i dont know why i suddenly need this permission when invoking the procedure on the productionserver from an external pc.
    Can somebody plz help me with this????
    greetz,
    Kim

    Anybody :)

  • Calling abap proxy synchronous ...

    Hi everyone.
    I have this scenario.
    abap proxy (request) -
    > XI (BPM) -
    > abap proxy (response).
    I'm able to send async the data using the proxy and i would like to send the response to other proxy.
    The best scenario for me would be if the proxy in sync, the BPM do some checks and finally, sender proxy returns the values.
    any idea of how to do this two scenarios?
    Regards,
    Inigo.

    Hi,
    >>>abap proxy (request) -
    > XI (BPM) -
    > abap proxy (response).
    are you sure that processing inside the BPM will take less then 30 sec?
    if not why do you want a syn call ? do you use this sync proxy call
    from an online report in r3 ?
    if you don't need a sync report do it in an async way:
    proxy - BPM - proxy (which writes the results to a table)
    and then from your report you can read from that table...
    one of the possibilities
    Regards,
    michal

Maybe you are looking for

  • How many RE1000 on one Router.

    How many RE1000 extenters can be attaced to one router ?

  • Archive Size

    Hi All, I don't understand ,why my offline Archive logs are in Big size. My Environment OS - -------------- SunOS usa0300ux636 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320 Oracle Version BANNER Oracle Database 10g Enterprise Edition Releas

  • My photo stream is grayed out

    Hi, So I bought iphone 5c and i also restored my pc. but on my computer under iCloud Photos is not activated and when I open the icloud software and the photo part is grayed out and the option button is also grayed out so its not clicable. can you pl

  • Web-base forms and reports

    Hi guy, I am planning to put my existing forms and reports to the web. And I am quite confused about what Oracle software should I buy ? I only know I need to get the Oracle Application Server. Also, what is the difference between using Unix and Win

  • File number is changed on export from lightroom

    using lightroom 4.3...  when I edit a group of photos in lightroom, most of the files will only be edited in lightroom but a few will also be opend into PS6 (by right clicking > edit in>...) Once the PS edits are complete the image is saved & I retur