Outbound Client ABAP Proxy Timeout Error

Hello everybody we have the next scenario:
R/3 Client Synchronous ABAP Proxy->XI-> Synchronous RFC
and we are having problems cause the Sender R/3 is not waiting for the RFC in the Receiver system to process so XI is in log  status fot this messages, is there a parameter to increase the time for R/3 Sender to wait for the Call method sentence to complete succesfully??????, thanks in advance.
Regards,
Raul Alvarado

Hi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in  change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna.

Similar Messages

  • Error handling using fault message type in outbound synchronous ABAP proxy

    Hi,
    We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
    Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
    Source Structure
    Req_Proxy
        req (0..unbounded, string)
    Response Structure
    Resp_SOAP
      Resp (0..Unbounded)
           respString (0..1, String) (carries the actaul response message)
          status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
    And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
    Please calrify.
    Thanks.
    Rohit

    For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
    for valid and 2 for invalid accordingly.
    Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
    Regards,
    Abhishek.

  • 7.1 Client ABAP proxy code sample (outbound)

    Hi guys,
    has somebody implemented new 7.0(7.1) abap proxies using ws runtime?
    Could you please post some sample code of client abap proxy?
    The 3. proxies were quite easy, but I'm a little bit confused in 7.0 and it's ws-rm.
    Thanks a lot, Olian

    Create a client proxy (for eg. the name would be like ZCO_MI_EMP_OUT_SYNC).
    Create a report program for the client proxy.
    report  yh_proxyclient.
    *  tables: ZEMP_DTLS_COPY.
       data: input type zmt_emp_tar1 .
       data: output type zmt_emp_src1 .
       data: client type ref to zco_mi_emp_out_sync .
      output-mt_emp_src-dept_id = 'SAP EP'.
      data wa_emp type zdt_emp_tar_employee.
      data wa_empinsert type zemp_dtls_copy. "ZDT_EMP_TAR_EMPLOYEE.
    try.
        create object client
    *  EXPORTING
    *    logical_port_name  =
      catch cx_ai_system_fault .
    endtry.
    try.
    call method client->execute_synchronous
      exporting
        output = output
      importing
        input  = input
    catch cx_ai_system_fault .
    catch cx_ai_application_fault .
    endtry.
    loop at input-mt_emp_tar-employee into wa_emp.
      write: / wa_emp-emp_id, wa_emp-dept_id, wa_emp-emp_name, wa_emp-emp_address.
    endloop.
      commit work.
    endmethod
    the above code is taken fron this wiki  (step by step guide using an example)
    [https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/abapClientProxytoABAPServerProxy+Scenario]

  • What is package structure for Client ABAP Proxy?

    1.     What is the package structure need to be  followed for creating abap client proxy.
    2.     I read some where in the form, it need to be 4 levels. Why is it?
    Thank you
    Ganges Leaves

    Hi
    U hav to create a 4 level package structure for client ABAP proxy.
    U can create ur on packages
    1st level-structure package.
    2nd level-main package.
    3rd and 4th level-sub packages.
    To the 4th level only u hav to create proxy.
    The classes and code wil be automatically generated at the time of proxy creation.
    I think the 4 level structure bcz while in r/3 everythin in integration builder like software component version and all wil be takin as different levels.
    Also u can go through the weblogs in the above replies u got.
    Regards
    Victoria.

  • Sample Client ABAP Proxy Program - PI 7.1

    I created Proxy. I need to call in a Report Program. I am using PI 7.1
    Can anyone send me a sample Client ABAP Proxy program to use with PI 7.1

    Hi,
    >>>Can anyone send me a sample Client ABAP Proxy program to use with PI 7.1
    it's exactly the same as for 7.0 and there are blogs that show such sample reports on SDN
    just do a little search and I'm sure you can find it
    Regards,
    Michal Krawczyk

  • Dynamic Configuration from Client ABAP Proxy

    Hello Experts,
    Is it possible somehow to set Dynamic Configuration values to Message Header when calling Client ABAP Proxy from SAP system?
    Best Regards

    I managed to get the dynamic header configuration at least with inbound proxies:
        DATA:
            server_context TYPE REF TO if_ws_server_context,
            proxy_framework TYPE REF TO if_proxy_framework,
            internal_protocol TYPE REF TO if_wsprotocol_internal,
            lo_inb_pxy TYPE REF TO cl_xms_inbound_proxy_plsrv,
            lo_dyn_header TYPE REF TO if_xms_msghdr30_dynamic.
          server_context = cl_proxy_access=>get_server_context( ).
          internal_protocol ?= server_context->get_protocol( 'INTERNAL' ).
          lo_inb_pxy ?= internal_protocol->get_framework( ).
          lo_dyn_header ?= lo_inb_pxy->xmb_message->get_dynamic_header( ).

  • Client ABAP proxy error handling. Please help!

    Hi Experts,
       I have following scenario:
       SAP ECC (ABAP Client Proxy) -> PI(XI)-->(SOAP) Third party web service System
       This is Asynchronous.
       What will happen when ABAP client Proxy in ECC sends data to PI but PI is down?
       Will the message be queued in ECC? Can the queued message be processed automatically when PI is UP later?
       Please help.
    Thanks & Regards
    Gopal

    Hello Gopal,
    Correct, it should be an automatic entry into the queue!
    refer below for a detailed understanding!
    /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies     XI: Reliable Messaging u2013 EOIO in ABAP Proxies
    /people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy     Monitoring for Processed XML messages in ABAP Proxy
    Weblog to send Response from RFC to File in Asyn Mode Using Proxy [original link is broken]     Weblog to send Response from RFC to File in Asyn Mode Using Proxy
    /people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method     PI/XI: ABAP Proxies say goodbye to Execute_Asynchronous method
    /people/krishnakumar.ramamoorthy3/blog/2008/11/02/error-handling-framework-for-abap-proxies--part-1     Error handling framework for ABAP proxies - Part 1
    /people/krishnakumar.ramamoorthy3/blog/2008/12/19/error-handling-framework-for-abap-proxies--part-2     Error handling framework for ABAP proxies - Part 2
    Regards,
    Jilan

  • Client ABAP Proxy : how to know which program is calling that service interface proxy

    Hi All,
    I have prepared some client proxy in ECC to communicate with PI.
    But, if I am not wrong, unlike server proxy which is written directly in the class Provider class in SPROXT transaction, in client proxy we write abap code to trigger proxy in SE38 .
    My question is : If I am in SPROXY and looking at any outbound SI, of which proxy is already generated, then how can in SE38  can I find which program is triggering that interface or proxy?

    Hi,
    check below thread for calling client proxy
    ECC outbound abap proxy (client) - Get ECC messageID from Protocol
    Regards,

  • ABAP Proxy Timeout

    Hi!
    I have this scenario:
    SAPR3 (A.Proxy) -> XI ->SOAP
    SAP R3 sends Sync Messages to XI, through ABAP proxy, which starts a BPM, this BPM calls a WebService that sometimes takes more than one minute to give a response.
    When the process reaches "Close S/A Bridge", it raises a Timeout Exception.
    I have already increased HTTP_TIMEOUT in SXMB_ADM and icm/keep_alive_timeout in SMICM, in XI with no effect.
    Do i need to change other parameter? Maybe in SAP R3?

    Hi Jose,
    go through tuning guide of XI (Once i find the link i update this thread ). The HTTP timeout property can be used for SOAP as well as the underlying transport protocol is http for SOAP messages too. That might help.
    Also, the second thing you could do is that by default the Web service client socket timeout is set to 60. Try changing this parameter in the Visual Administrator: Server -> Services -> Web Services Container on the Settings tab.
    Regards
    joel.

  • ABAP Proxy timeout issue

    Hi,
    I have a scenario in where I provide a web service. I get called by this web service and then call a abap proxy (synch). The abap side takes time to gather the data. after 600 secs, the connection gets a timeout.
    It says, "500 Connection timed out"
    "Detail: Connection to partner timed out after 600s"
    In smicm I increased the HTTP value to 9000. So, how do I get this error?
    Parameters are like below in PI:
    icm/server_port_0     = PROT=HTTP,PORT=50000,TIMEOUT=90,PROCTIMEOUT=9000
    icm/keep_alive_timeout (sec.)  = 50
    icm/conn_timeout (msec.)       = 5000
    xiadapter.inbound.timeout.default = 5400000

    Hi,
    Check if you are getting some short dumps in ABAP side due to this timeout in ST22.
    Probably the issue is the work process time out  in the ABAP side as you mentioned it takes more time to gather data. the profile parameter is rdisp/max_wprun_time  and it has default value of 600 seconds. if thats the case then you can increas it.
    regards,
    francis

  • ABAP proxy Creation error

    Hi All,
    I'm trying to create a synchronous ABAP proxy out of my outbound interface. When I do that I get an error saying that
    <b>Cannot generate proxy (object <attributename="type"> missing in WSDL, see long text)</b>
    Now when I remove the reponse message from the interface and make it asynchronous, I'm able to create it without any trouble. So the trouble lies in the reponse message which is a XSD file imported as an external definition. Request message is also an external definition.
    The reponse WSDL is as follows:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:ebay:api:PayPalAPI">
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:ebay:api:PayPalAPI" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified">
                   <xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/" schemaLocation="DoDirectResponse.xsd" />
                   <xsd:import namespace="http://schemas.xmlsoap.org/ws/2002/12/secext" schemaLocation="wsse.xsd" />
                   <xsd:import namespace="http://www.w3.org/1999/XMLSchema-instance" schemaLocation="xsi.xsd" />
                   <xsd:import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="ebl.xsd" />
                   <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="RequesterCredentials">
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element ref="ebl:Credentials" />
                             </xsd:sequence>
                             <xsd:attribute ref="xsi:type" use="required" />
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="DoDirectPaymentResponse">
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element ref="ebl:Timestamp" />
                                  <xsd:element ref="ebl:Ack" />
                                  <xsd:element ref="ebl:Version" />
                                  <xsd:element ref="ebl:Build" />
                                  <xsd:element ref="Amount" />
                                  <xsd:element ref="AVSCode" />
                                  <xsd:element ref="CVV2Code" />
                                  <xsd:element ref="TransactionID" />
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="Amount">
                        <xsd:complexType>
                             <xsd:simpleContent>
                                  <xsd:extension base="xsd:decimal">
                                       <xsd:attribute name="currencyID" type="xsd:NCName" use="required" />
                                       <xsd:attribute ref="xsi:type" use="required" />
                                  </xsd:extension>
                             </xsd:simpleContent>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="AVSCode">
                        <xsd:complexType>
                             <xsd:simpleContent>
                                  <xsd:extension base="xsd:NCName">
                                       <xsd:attribute ref="xsi:type" use="required" />
                                  </xsd:extension>
                             </xsd:simpleContent>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="CVV2Code">
                        <xsd:complexType>
                             <xsd:simpleContent>
                                  <xsd:extension base="xsd:NCName">
                                       <xsd:attribute ref="xsi:type" use="required" />
                                  </xsd:extension>
                             </xsd:simpleContent>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="TransactionID" type="xsd:NMTOKEN" />
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="RequesterCredentials">
              <wsdl:part xmlns:generateduniqueprefix15="urn:ebay:api:PayPalAPI" name="RequesterCredentials" element="generateduniqueprefix15:RequesterCredentials" />
         </wsdl:message>
         <wsdl:message name="DoDirectPaymentResponse">
              <wsdl:part xmlns:generateduniqueprefix16="urn:ebay:api:PayPalAPI" name="DoDirectPaymentResponse" element="generateduniqueprefix16:DoDirectPaymentResponse" />
         </wsdl:message>
         <wsdl:message name="Amount">
              <wsdl:part xmlns:generateduniqueprefix17="urn:ebay:api:PayPalAPI" name="Amount" element="generateduniqueprefix17:Amount" />
         </wsdl:message>
         <wsdl:message name="AVSCode">
              <wsdl:part xmlns:generateduniqueprefix18="urn:ebay:api:PayPalAPI" name="AVSCode" element="generateduniqueprefix18:AVSCode" />
         </wsdl:message>
         <wsdl:message name="CVV2Code">
              <wsdl:part xmlns:generateduniqueprefix19="urn:ebay:api:PayPalAPI" name="CVV2Code" element="generateduniqueprefix19:CVV2Code" />
         </wsdl:message>
         <wsdl:message name="TransactionID">
              <wsdl:part xmlns:generateduniqueprefix20="urn:ebay:api:PayPalAPI" name="TransactionID" element="generateduniqueprefix20:TransactionID" />
         </wsdl:message>
    </wsdl:definitions>
    I would be really grateful if I could get a resolution as I'm badly stuck because of this issue.
    Thanks
    Arvind

    Hi Arvind,
    Check the following,
    1. The tag <part name="" type=""> is not supported with ABAP Proxies.
    Cannot generate proxy
    2. Check for recursion - Cannot generate ABAP proxy
    3. keep in mind tht ur application system is based on 6.40 or higher versions.
    Regards,
    Prateek

  • ABAP Proxy PARSE_APPLICATION_DATA ERROR

    Hi Guys,
    Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error  on SNC target system.
    <?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="">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:P1>Request Message</SAP:P1>
      <SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
      <SAP:P3>/1SAI/TXSF8E9D07F84DB493AAA0A Line 3340</SAP:P3>
      <SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)ProductActivity(2)Item(3)ShipToLocation(1)StandardID(2)</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/TXSF8E9D07F84DB493AAA0A Line 3340 An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)P An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A Data loss occurred when converting 00900012300355698</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks in Advance
    Regards
    San

    Hi  Folks,
    I have got application error while doing in Inbound proxy scenario. This inbound message is ProductActivityNotification, this message has got fault message. This message is triggering for faults. How to control this fault message or how to divert this error as an alert to RWB. Please give me your ideas step by step. Error as follows:
    <?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="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SAPGlobal20/Global">ProductActivityNotificationFault</SAP:ApplicationFaultMessage>
      <SAP:Stack>Application has thrown an exception</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please find the fault message has got following values
    <?xml version="1.0" encoding="utf-8" ?>
    - <n0:ProductActivityNotificationFault xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:RAS:/1SAI/TAS653D9A9CCD9A8EF3AF9B:701:2009/02/10">
    - <standard>
      <faultText>Proxy Class (Generated)</faultText>
    - <faultDetail>
      <severity>information</severity>
      <text>Start of inbound processing: ProductActivityNotification (ID )</text>
      <id>000(/SCA/BIF_PROACT)</id>
      </faultDetail>
    - <faultDetail>
      <severity>error</severity>
      <text>Message ID is missing</text>
      <id>032(/SCA/BIF_MI)</id>
      </faultDetail>
      </standard>
      </n0:ProductActivityNotificationFault>
    Will you please focus bit light on this error message please?
    Regards
    San

  • ABAP Proxy PARSE_APPLICATION_DATA ERROR   - Deserialisation error

    Hi All,
    Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SAP target system.
    - <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:P1>Request Message</SAP:P1>
      <SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
      <SAP:P3>/1SAI/SASF1B34BDF7BC867BECB1E Line 127</SAP:P3>
      <SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6)</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SASF1B34BDF7BC867BECB1E Line 127 An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E Data loss occurred when converting ON</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The error is shown  for the field GBDEP. It is of type char(3) both in the source system and the target system.
    Still i am getting this error.
    Kindly help me in resolving the issue.
    Regards,
    Sridevi S

    Hi Klaus,
         Thanks for the t-code.
         I couldn't figure out any issue in that program. Below is the line of code in the program for the field GBDEP which is same as for the other fields.
        <tt:cond s-check="not-initial('ROOT.GBDEP')">
         <tt:ref name="ROOT">
          <GBDEP tt:ref="GBDEP">
           <tt:deserialize>
            <tt:assign to-var="_C_NIL" val="' '"/>
            <tt:d-cond>
             <tt:attribute name="xsi:nil">
              <tt:read var="_C_NIL" map="xml('true', '1') &gt; val(C('2'))"/>
             </tt:attribute>
            </tt:d-cond>
           </tt:deserialize>
           <tt:cond-var check="_C_NIL!='2'">
            <tt:value maxLength="3"/>
           </tt:cond-var>
          </GBDEP>
    kindly help.

  • ABAP Proxy configuration Error (Not able to connect R/3  to IB )

    Hello All...
    I am trying to configure the connection from R/3 to XI using the ABAP proxy generation.For that I have followed the steps given in the below blog
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    We created all the credentials required for the XI and R/3 side configuration and its working fine individually when we have tested for the connection and also assigning this at SXMB_ADM,but in integration engine configuration,when I am trying with the URL <b>dest://<RFC destination(http</b>).Its giving error and in sproxy at R/3 its giving that no integration engine is connected to Business system.
    Whats worng with my configuration.How can I resolve this.
    I am having R/3 system WAS 6.40

    Hi,
    <i>But when I am giving the path prefix as you have specified I am getting an Error Query String Not Allowed.</i>
    I think thats the warning not error. Just press enter again and go to the logon detail Tab and give the userid password
    <i>And how can give the SLD details using the SLDAPICUST.</i>
    go to transaction SLDAPICUST and give the following details:
    Alias name :any name u want
    Prim: check this box
    Hostanme: give the Hostname where your SLD (XI server name if you are using the XI SLD)
    PORT: Java Port
    UserId/Password: for XIAPPLUSER
    I think you are missing on the configuration. I think its better if you go through the weblog again.
    Regards
    Vijaya

  • FILE TO INBOUND ABAP PROXY - " LOOP_IN_MESSAGE_ROUTING  ERROR "

    Hi , 
    Getting the following Error in *FILE TO INBOUND ABAP PROXY* which is updating a Database table in R/3.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
      <SAP:P1>is.01.lgscms</SAP:P1>
      <SAP:P2>IS</SAP:P2>
      <SAP:P3>XI</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>XI protocol error</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    How to rectify the Error..
    Regards,
    Ravi

    Hi Ravi !
    Check if the url for the receiver is
    http://<host>:<port>/sap/xi/engine?type=receiver
    or
    http://<host>:<port>/sap/xi/engine?type=entry
    if using XI 3.0
    Regards,
    Matias.
    Edited by: Matias Denker on Feb 25, 2008 2:12 PM

Maybe you are looking for