Sproxy to SOAP

Hello,
   I am working on a existing Proxy to SOAP scenario and have a query on the interface.
I am supposed to add two fields to the data type in XI and regenerate the proxy program in R/3.
Now how does the following actions affect the existing database table names in R/3 system
1) what happens to the names of the existing data structures when i regenerate the proxy at Outbound message Interface level?
2) what happes to the names of the exisitng structures when i regenerate the proxy at Data type level?
Eg: Data type has Emp Name, Emp Address, Emp Payroll as existing nodes.A new node called Emp Hobbies is supposed to be added which should contain two fields called Personal & Professional. Earlier each node used to refer the data structure of R/3 as follows ;
Emp name     -  ZABC_PQR_Employee_Emp
Emp Address - ZABC_PQR_Employee_Emp1
Emp Payroll -   ZABC_PQR_Employee_Emp2
So when i regenerate the proxy as asked above, Does the Structure names change ?
If yes , In which case the names  get changed?
Appreciate your answers
Please post a message for further clarification or if the information provided above is insuffiecient...Thanks

Udo,
Unfortunately, i have to say you that the structure names have changed.
As part of developing the object i added the new node to the data type and Activated the object.
In the R/3 system, i have regenerated the Data tpye instead of Message Interface without my knowledge.
Later i came to know about the right way and regenerated the message interface and activated the proxy.
Back in the ABAP calling program, it showed an new syntax error which is related to the Data structure naming conflict. When i did an analysis i found that the data structed names got changed.
1) But i am not sure when did this change happened at the data type level or message interface level?
So before the proxy generation if the Emp Name was referring to ZABC_PQR_Employee_EMP1,
after the generation it got changed and referred to ZABC_PQR_Employee_EMP2.
2) Does this mean every time i add new node to the data type and run the proxy this structres change?
or is it just because i regenerated the data type which i am not supposed to do?
By the way the term "Node" here refers to : Emp name, emp address, Emp Payroll and Emp hobbies ....apologise if that has misleaded you....
EMP_DT
Emp Name
First Name
Last Name
Emp Address
line_1
line_2
Emp Payroll
Basic
HRA
Emp Hobbies
Private
Professinal

Similar Messages

  • Manual Testing of Enterprise services

    Hello Colleagues,
    Please let me know the different methodes of testing Enterprise services manually.
    I have used below methodes :
    SPROXY
    SOAMANAGER
    SOAP UI
    Is there any other way apart from the once mentioned above.
    Also let me know how to test the non sap services in an SAP environment, for example the standard services are avalialbe in the UDDI how can i test these services in an SAP environment.
    Please let me know if you need any further details.
    Thanks,
    Ajay

    Hi Ajay,
    SPROXY ---> This t-code is used to generate/create webservices from out of application system(R/3 or ECC system) called OUTSIDE IN APPROACH.Where the webservice will be generated on inbound service interface and we can test the webservice from here.       
    SOAMANAGER -
    > When ever we create a proxy on inbound service interface.we need to implement the method(interface) and logic will be written based on our requirement.The name of the interface will be displayed in SOAMANAGER to make it as WEBSERVICE we need to create endpoint and binding,now it will be exposed as webservice  and after that we can generate WSDL file and we can test from WS NAVIGATOR.
    SOAP UI : The above exposed webservice or generated WSDL can be tested using the test tool like SOAP UI.
    Hope it clears.....
    Thanks

  • ABAP.INTERFACE_REGISTRATION_ERROR while run SOAP - PI - RFC - R3 scenario.

    Hi all,
    My scenario is a third party send a request (through SOAP message) to PI, then PI will made RFC call to R3 system to retrieve data.  (call BAPI_CUSTOMER_DISPLAY).
    At IR i've created.
    Namespace: http://send
    1.  Data type: DT_request (which include customer number )
         Data type: DT_response
    2.  Message type for 2 data types above.
    3.  Message Mapping for request: MT_request  => BAPI_CUSTOMER_DISPLAY and for response: BAPI_CUSTOMER_DISPLAY.response => MT_response.
    4. Service Interface: SI_BAPI_CUSTOMER_DISPLAY_REQUEST: Outbound, stateless and synchronous.
        Operator Mapping: which mapping SI_BAPI_CUSTOMER_DISPLAY_REQUEST and SI_CUSTOMER_DISPLAY_RESPONSE (please see 6).
    At business system B (on R3 WS ABAP).
    Namespace: http://rec
    5. Importing BAPI_CUSTOMER_DISPLAY rfc.
    6. Inbound Service Interface: SI_BAPI_CUSTOMER_DISPAY_RESPONSE: Inbout, statelss and synchronous (corresponding to  4.)
    And then, at ID I've created:
    7. SOAP communication channel (cc) for business system A. This cc is sender.
    8. RFC communication channel for business system B. This cc is receiver.
    9. Sender agreement, receiver determination...
    10. Generate WSDL and got the ws url is: http://sapsrv:50100/sap/xi/engine?type=entry&version=3.0&Sender.Service=BVI&Interface=http%3A%2F%2Fsend%5ESI_BAPI_CUSTOMER_DISPLAY_REQUEST
    Then,  I tried to test with XML spy but get this error:
    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context/>
                             <code>ABAP.INTERFACE_REGISTRATION_ERROR</code>
                             <text>No implementing class registered for the interface (ABAP interface, request message SI_BAPI_CUSTOMER_DISPLAY_REQUEST, request message, namespace http://send)</text>
    PS: - I've generated all proxy at r3 system. (via tcode Sproxy)
             - And Sxmb_adm I've set Business System is Application System.
    Please help me to fix this error.
    Many thanks.

    >>ABAP.INTERFACE_REGISTRATION_ERROR
    You did not complete proxy objects coding yet.

  • SOAP error in synchronous scenario for ABAP Proxy with Oracle D/B

    Dear Experts,
    I am working in Sender ABAP Proxy <====>SAP PI 7.31 JAVA only <====> Oracle Database. My proxy configuration are working successfully.
    Apart from that, I have maintained a SOAP sender communication channel under the ECC business system with
    Transport Protocol as HTTP
    Message Protocol as XI 3.0
    Adapter Engine as Central Engine
    When I am testing from ECC at Tx SPROXY, I am receiving following error.
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at
    1. In XI3.0 protocol, I can not select BE but when selected HTTP 1.0 as Message protocol then I can find the BE.
    2. No Response message is shown in ECC when testing the message.
    3. How do Receiver JDBC adapter for Oracle Database is configured 
    4. What would be Message Protocol for Oracle Database i.e. XML SQL Format or Native SQL format for Select operation.
    Please guide.. All your inputs will be appreciated......
    Regards
    Rebecca

    Dear Indrajit,
    Appreciate your inputs.. Yes I have configured all the ABAP proxy configurations and there no question of missing any thing as Tx SLDCHECK in ECC is working perfectly fine.
    But still to go, some of the queries needs more input.
    1.In ID, i have created a Sender SOAP communication channel with listed details.
    Transport Protocol as HTTP
    Message Protocol as XI 3.0
    Adapter Engine as Central Engine
    Is there any parameters which I may be missing from Module tab of Synchronous SOAP Cc ?
    2. In the Cc monitoring, the JDBC receiver status shows "Database operation successfully completed" but I could not find any response data from database. The Message monitoring should have 2 messages for 1 trigger, but I could find only 1 message by SOAP only?
    Sorry to bother experts...Please answer in sequence...
    Regards
    Rebecca

  • Soap to abap proxy

    Hi,gurus:
        I wanna to configure a scenario about soap to abap proxy,do you have any step by step configurations about that?Any help will be appreciated!

    Sender SOAP Adapter
    Receiver RFC/IDOC/ABAP proxies.
    IR
    Step 1:
    Create the Sender/Receiver Datatypes for Request & Response
    step2:
    Create the MT for Req & Res
    Step3 :
    Create OB Message Interface ( Syncronous) /IB Message Interface( Synchronous)
    step5 :
    Request Mapping : Sender Req MT--> REcv Req
    Response Mapping : Recv Res----->Sender Res MT
    Step6:
    Interface Mapping
    ID
    Step1 :
    Configure Sender Soap Adapter
    Step2 :
    Configure Receiver XI  Adapter
    Step 3: Configure Sender Agreement, receiver determination,Interface determination,Receiver agreement
    Step 4:
    Create WSDL file.( ID->tools-Defien webservice)
    save the file as .wsdl file
    Give the file to sender system
    SAP System
    Step 1:
    Goto Sproxy T.code -> select IB interface -. Right click create object ,it will automatically create aproxy class.
    Step2 ;
    write an ABAp program to send the data to class.
    Below weblog helps in wrting  ABAP program
    File to R/3 via ABAP Proxy
    Regards,
    Jayasimha

  • Soap to proxy scenario Getting exception caught with cause   error

    Hi Experts,
    MY scenario is soap to proxy i am  getting below exception message in advanced engine configuration in ICO.
    OAP: request message entering the adapter with user J2EE_GUEST
    09/10/2014 11: 06: 03 346 XI Information Packaging (Bulk Mode) is not Enabled, Proceeding to the Normal Processing.
    09/10/2014 11: 06: 03 346 XISOAP Information: Received an XI message for processing
    09/10/2014 11: 06: 03 598 Error SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
    09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
    OAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
    09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
    09/10/2014 11: 06: 03 598 Information SOAP: response message to continuing 7477aafa-38da-11e4-beed-00000028af0a
    09/10/2014 11: 06: 03 599 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
    09/10/2014 11: 06: 03 599 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
    payload is contains some  special charters in  which is in protiguse language
    example.
    • AWPJ SERV DE TERCERIZ and
    dot is the special char
    same payload while testing using sproxy tcode dot "•" is converting in " # "symbol and with out error its successfully updating the database in ECC.
    while testing using the same payload using soap ui removing the dot symbol from the field its successfully processing  and updating the database.
    is this interface is failing in PI level ? or ECC i am not getting dump in ecc.
    is there any special character conversation in sap pi level.
    where this message exactly failing is in PI level or in ECC level?
    Help us find the solution.

    Hi Ravinder,
    When you mark the option Do not use SOAP envelope the adapter will not generate the SOAP envelope therefore you need to set an extra mapping in the Request to wrap the SOAP envelope. For example with XSL:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml"/>
        <xsl:template match="/">
            <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
                <SOAP:Header/>
                <SOAP:Body>
                    <xsl:copy-of select="/"/>
                </SOAP:Body>
            </SOAP:Envelope>
        </xsl:template>
    </xsl:stylesheet>
    Later in the response you will have the SOAP envelope tags. (You can do a first try without java mapping only to see in the monitoring the response with the junk character).
    When you determine the junk character you can try to use and to modify the next java mapping SAP PI - Deciphering apostrophes in XML - Process Integration - SCN Wiki to deal with your problem.
    Hope this helps.
    Regards.

  • Soap Action missing in the WSDL generated for Service Interface

    Hi All,
    I have modelled an interface in the ESR and have created the proxy in the back-end ECC6 system. It is basically an outside-in approach. I have generated a WSDL using the Wizard in the SPROXY transaction. But the WSDL does not have any SOAP Action. I tried to create a web-service for an existing BAPI. That WSDL also did not have any SOAP Action. Can you please let me know why the SOAP Action is missing? Is there any other way of generating the WSDL?
    Regards,
    Geetha

    Hi Geetha,
    Please try configuring the entire scenario in PI.
    If you are using PI 7.1, You can see the WSDL by right clicking on Sender agreement. Please use SENDER SOAP Channel. In PI 7.0 you will have to generate WSDL manually.
    Regards,
    Vikas

  • SOAP adapter Using XI 3.0 error: invalid content type for SOAP: TEXT/HTML

    Hi All,
      I have the scenario to send a message to proxy via SOAP adapter . My PI server is 7.3 and my BI application server also 7.3. I have created service interface in the ESR and created the ABAP proxy in the Application server. Im using the receiver SOAP adapter with message protocol as XI 3.0. Am running this scenario in the central adapter engine. (That is i didnt create integrated configuration). I am facing the issue in the receiver SOAP channel as 'invalid content type for SOAP: TEXT/HTML: 401 Unauthorized'. But i can able to login into the URL which is given in the channel using the username and password used in the channel.
    Can you please let me know if any addtional settings need to be done in PI side.
    Regards,
    Ramalakshmi.G

    Hi,
      Thanks for your reply. I have done my scenario with the integration configuration. Still i am facing the same issue " SOAP: TEXT/HTML; HTTP 401 Unauthorized". I have given the correct URL, username and password. Is this enough to connect to the receiver integration server from AE. Any settings need to be do in the receiver ABAP system and PI system. If so please share the corressponding note for the same.  What should be the role is assigned to the userid given in the channel.
    I have used sproxy to create the proxy in the receiver ABAP system. In PI i am using the SOAP adapter with XI 3.0 ,message protocol to call to this proxy. I have not done any settings in any of the servers. Do i need to do any settings.
    Regards,
    Ramalakshmi.G

  • Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

    My scenario: SPROXY => XI => 3rdParty WebService. Communication is synchronous. I've a problem with soap envelope. It is required by webservice, but when I use standard soap envelope generated by SAP I've a problem with receiving response from webservice.
    So I want to create my own envelope. For this reason I've used DO NOT USE SOAP ENVELOPE option. Now the challenge comes. How can I create my own soap envelope?
    Do you have any working example? Soap envelope should be added to message send from XI to 3rdParty WebService.
    Helping answers => a lot of points

    I'm talking about HTTP header.
    When I'm sending SOAP request from SAP my whole message looks like when I use soap envelope
    POST / HTTP/1.0
    Accept: */*
    Host: 192.168.132.179:54000
    User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
    Content-ID: <soap-02cce7702b1a11dd9902000c29ee261e[at]sap.com>
    Content-Type: text/xml; charset=utf-8
    Content-Disposition: attachment;filename="soap-02cce7702b1a11dd9902000c29ee261e[at]sap.com.xml"
    Content-Description: SOAP
    Content-Length: 259
    SOAPACTION:
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:Sd2Ids_SzfExport xmlns:ns0='http://www.dat.de/sdii/ids/Sd2SOAP.wsdl'><arg1>1234567899-0</arg1><arg2>1</arg2></ns0:Sd2Ids_SzfExport></SOAP:Body></SOAP:Envelope>
    Always after such request I got and HTTP 411 error.
    In opposite, when I'm sending request from e.g. Altova or SoapUI, my message looks:
    POST / HTTP/1.1
    Content-Type: text/xml; Charset=UTF-8
    User-Agent: XML Spy
    Host: 192.168.132.179:54000
    Content-Length: 489
    Connection: Keep-Alive
    Cache-Control: no-cache
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <m:Sd2Ids_SzfExport xmlns:m="http://www.dat.de/sdii/ids/Sd2SOAP.wsdl">
                   <arg1 xsi:type="xsd:string">1234567899-0</arg1>
                   <arg2 xsi:type="xsd:string">1</arg2>
              </m:Sd2Ids_SzfExport>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    After that request WebService response is correct.
    You can find such differences (except Content-length which is a result of XML message formatting) in those two headers:
    - for first is used HTTP 1.0 protocol for later 1.1
    - in SAP header an info about attachment is added
    After a lot of test I thing that those attachment info in header of HTTP is causing a problem. So I want to use DO NOT USE SOAP ENVELOPE option to generate HTTP header without Content-Disposition and generate SOAP Envelope manually.

  • CX_SY_MOVE_CAST_ERROR in SPROXY Class after creating fault messages in PI ?

    Hi All,
    We created a SOAP to Proxy synchronous scenario and everthing works fine.
    Now we have created a fault message in PI and regenerated the proxy in ECC, after regenerating the proxy, if i debug the proxy from service registry, breakpoint gets triggered in proxy class and iam getting an exception "CX_SY_MOVE_CAST_ERROR" at the status bar (but not dump). After executing the proxy class i could get the required response in service registry but with the exception ( Connection IO Exception. Check nested exception for details. (Invalid SOAP Response. Runtime can not find return parameter <(http://hostname.com/soaptoproxy)MT_Soap_Response>.). In MONI i could see this as a successful message. Can anyone tell me reason for this exception both in proxy class and in Service registry ? I also regenerated the proxy class after creating fault message in PI.
    Thanks,
    Sivakumar.C

    Hi,
    Thanks. I have tested in locally in SPROXY and i found that exception occurs in the constructor method of exception class, which was created by adding Fault Messages in PI.  Any Suggestions ? 
    Thanks,
    Sivakumar.C
    Edited by: kumar.sappi on Feb 6, 2012 12:19 PM
    Edited by: kumar.sappi on Feb 6, 2012 1:49 PM

  • Handling SOAP errors and parsing error

    Hi,
    I guess these are two questions.
    We are implementing a webservice from a provider. The WSDL is RPC-style. We could import it in PI and generate the proxies in ABAP. The requests are properly sent to the provider but we have problems with the returning message.
    Line: -
    When the response is positive, we get a parsing problem. Executing the service in SoapUI, this is the returning message:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP-ENV:Body>
          <SOAP-ENV:loginResponse>
             <Result>s4vep9dm4iu1teh877cdduk0e1</Result>
          </SOAP-ENV:loginResponse>
       </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    When testing in SPROXY, this is the result (without the soap body):
    - <SOAP-ENV:loginResponse xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <Result>0s5bbett500h183v7fi32jm2o3</Result>
      </SOAP-ENV:loginResponse>
    We get the following error message from the parser: Element 'loginResponse' expected. Should the 'loginResponse' tag refer to another namespace? Does this mean the provider's respons is wrong?
    Line: -
    When the response is negative, we get the following response (as seen in SoapUI):
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP-ENV:Body>
          <SOAP-ENV:Fault>
             <faultcode>0001</faultcode>
             <faultstring>Invalid account credentials.</faultstring>
          </SOAP-ENV:Fault>
       </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    This is the error we see when we test in SPROXY:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Invalid account credentials.</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    In order to be able to catch this standard soap fault, we took a look at this blog:/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
    It guided us through the fault mapping, but still we don't get the correct respons. Are there some supplementary settings we have to pay attention to?
    Thanks for any help.
    Kris

    > We get the following error message from the parser: Element 'loginResponse' expected. Should the 'loginResponse' tag refer to another namespace?
    > Does this mean the provider's respons is wrong?
    Yes, indeed. The namespace "http://schemas.xmlsoap.org/soap/envelope/" must not be used for SOAP body elements.
    Here the webservice has to be changed.
    > In order to be able to catch this standard soap fault, we took a look at this blog:/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
    > It guided us through the fault mapping, but still we don't get the correct respons. Are there some supplementary settings we have to pay attention to?
    I think the SOAP adapter changes the application fault into a system fault. So you should have the response in the system fault exception in ABAP proxy.

  • SPROXY: XSLT Type Error when testing

    We are using SAP PI 7.1 to consume ABAP Proxies. We have performed all the necessary configurations and are able to see the ESR from within SAP R/3. When testing an ABAP Proxy via SPROXYI receive the error shown below. In fact I receive this error for all proxies that I try to test, including standard SAP functions. I am assuming this is a configuration issue rather than a specific issue with a proxy. I have checked SDN and SAP Service and I can't find any mention of this specific error. Is there anyone out there who can help?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:P1>Request Message</SAP:P1>
      <SAP:P2>CX_CALL_ST_ERROR</SAP:P2>
      <SAP:P3 />
      <SAP:P4>Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during XML => ABAP conversion (Request Message; error ID: CX_CALL_ST_ERROR; ( Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION)) A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>

    Hi Robert,
    i know that this is quite late. The problem is with the XSLT which gets generated when you generate PROXY. And some times the kernel doesn't doesn't set the conversion of XSLT correctly. you can check the syntax of the XSLT /1SAI/TXS1EF71A636AE519CFE80A in the transaction STRANS.
    There should be some basis notes from the component BC-DWB-PRX to solve the problem.

  • SOAP: response message contains an error Application/UNKNOWN/APPLICATION

    Hi,
    My scenario is Proxy>Soap>WS. When I tested proxy using SPROXY,the web service call is working fine and I am getting response. However, when I call proxy in the the program, I am getting "SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault" in adapter engine. I have gone through many similar posts in SDN but did not help.
    Thanks for your help.

    Thanks. I used SOAPUI outside SAP and it works perfectly fine. Even in SAP, it works fine when using Sproxy.  Here is the error from adapter engine:
    2010-06-24 12:59:34     Success     SOAP: continued from request message 6600174c-8a22-613e-e100-000018280c11
    2010-06-24 12:59:34     Error     SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    2010-06-24 12:59:34     Success     SOAP: response message leaving the adapter
    2010-06-24 12:59:34     Success     MP: Leaving module processor
    2010-06-24 12:59:34     Success     Application attempting to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System.
    2010-06-24 12:59:34     Success     Trying to put the message into the send queue.
    2010-06-24 12:59:34     Success     The response message for message 6600174c-8a22-613e-e100-000018280c11(INBOUND) was successfully transmitted to the calling application.
    2010-06-24 12:59:34     Success     The message status set to DLVD.
    2010-06-24 12:59:34     Success     The application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application.

  • Error with Proxy - Soap sync scenario - "invalid http response:HTTP/1.1 5"

    Hello,
    I'm working on a PI scenario as displayed below:
    Proxy <-> ECC <-> Soap
    I've already imported the WSDL provided by 3th party and mapped one of the actions of the interface.
    In the PI configuration I`d created the Scenario, using a Soap Receiver communication channel, passing only the URL and the action (no more options used).
    When I`m trying testing using SPROXY or Runtime Workbench, the error bellow is displayed, and no receive message is created:
    "com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: HTTP/1.1 5"
    Someone knows the error cause?
    Thanks,
    Ana Paula Lavieri

    Hello,
    "com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: HTTP/1.1 5"
    HTTP 1.1 is not natively supported by standard SOAP or Plain HTTP Adapter, you should use SOAP Axis for that. See SAP Note 1039369 - FAQ XI Axis Adapter, under Receiver Adapter General -> 16. Can I use HTTP 1.1? Otherwise, you would have to ask the third-party to use HTTP 1.0 instead.
    Hope this helps,
    Mark

  • Problem: Adapter SOAP

    Hello.
    My problem is recepcionar a SOAP external errors produced. The idea is that XI / IP register those errors and surrendered to a proxy SAP ECC.
    SOAP you want to capture.
    <Soap: Envelope xmlns: soap = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns: xsd = " http://www.w3.org/2001/XMLSchema ">
        <soap:Body>
           <soap:Fault>
              <faultcode> Soap: Server </ faultcode>
              <faultstring> Error for data decimal  </ faultstring>
              Transactions <faultactor> </ faultactor>
              <detail>
                 It was not possible to make <message> Transaction Order Income </ message>
                 <description> Problems in accessing the repository </ description>
              </ Detail>
           </ Soap: Fault>
        </ Soap: Body>
    </ Soap: Envelope>
    The flow is:
    (1) SAP ECC (Proxy) <-> (2) SAP XI / IP Mapping <-> (3) External WebService

    Hello.
    My design is next.
    IN SAP XI/PI
    - Interface Object
    1.- Create Fault Message Types. (MT_FAULT)
    2.- Message Interfaces / add Fault Message Types (MT_FAULT) (Add Proxy and SOAP interfaces)
    - Mapping Object
    3.- Message Mapping / Add Mapping (MT_FAULT mapping MT_FAULT)   -> (MM_FAULT = mapping generate)
    4.- Interfaces Mapping / Method Request,Response and Fault.
                In Method Fault add (MM_FAULT).
    IN SPROXY SAP ECC
    5.- Execute transacction Sproxy and regenerate namespaces of interface.
    6.- Debug interface and NOT MESSAGE ERROR.
    But entry transaction SXI_MONITOR, in SAP ECC the XML is next.
    (SOAP HEADER - ERROR)
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: Server was unable to read request. ---> There is an error in XML document (1, 526). ---> Instance validation error: 'CL' is not a valid value for SolicitudOrdenPagoMonedaOperacion.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

Maybe you are looking for

  • B2B capability of SAP PI 7.1

    Need clarification on the B2B capability of SAP PI 7.1. I have the following scenario: SAP ERP <-> SAP PI 7.1 <-> (xml) <-> B2B Trading partners I have three questions on the above scenario: 1. SAP PI will have to send standard XML message to B2B tra

  • I have one pc with service not available"sapdp00"

    In my 8 year career I never had problem using "services" file in "c:\windows\service32\drivers\etc". However there is an XP machine (with regular connection to network) with problem "service not available"sapdp00". It is like this settings come from

  • VDSK1 configuration not working

    Hi Experts , I have set up all the necessary configurations for feature VDSK1 , including creation rules but when i create IT0001 for an employee , the desired combination is not getting fulfilled . -Mentioned the combination for VDSK1 in creation ru

  • [HELP] Problem on JTree node mouse event !

    I implement a JTree component in my application. Now, I want it acts like windows XP's file explorer: When mouse cursor hovers over some tree node, that node's text became underlined, (font may be also changed as well) and the cursor changes to a 'ha

  • HT201210 i forgot my backup password how to restore my backup?

    i forgot my backup password how to restore my backup?