Error with ABAP proxy

Hi all,
I have an ABAP proxy - XI - Webservice scenario, in the XI side we are getting error saying input data not coming in. How to check weather proxy is triggering the actual payload or data?
There has been a change in the WSDL from the Webservices side, they have changed the data type, so we too updated the mapping in XI. So do we need to change anything in the ABAP program which triggers the proxy,
how do I check weather proxy is triggering data or not?
I want to see weather its problem with the ABAP trigger program.
Thanks,
Srinivas

Hi ramakrishna,
Does R/3 side SXMB_MONI give successful chequered flag when the message is processed?
Because for correctly processed message, the data is being updated in the table, but I can't see the chequered flag on the R/3 side.
But for the wrongly processed ones its showing PL_TIMEOUT error and showing red flag on R/3 side, this is what I see on the R/3 side:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Call Integration Server
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Pipeline timeout condition satisfied</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>

Similar Messages

  • Error in ABAP Proxy generation?

    hai pals,
    my intention is to push the data from XI to SAPBWSEM system throgh an ABAP PROXY.
           but , here i got an error which i already mentioned in the forum, that is " no connection to integration builder(only local data visible) ".
            i went to the integration engine configuration in "SXMB_ADM" transaction in SAPBWSEM server.
            in sxmb_adm transaction ,the system ask for the "specific configuration data-catagory" like TUNNING , MONITOR,RUNTIME,TRACELOG,DEBUG and RFCADAPTER.
             im little bit confused in choosing the "catagory of configuration data".so can u pls help me in this error.
    with cheers.
    rajesh

    Did you create the RFC Destinations LCRSAPRFC and SAPSLDAPI to point your SLD ? If not do that.
    Then create RFC Dest INTEGRATION_DIRECTORY_HMI type H. Look at your XI box and make these 3 RFC Dests.
    Then use the following thread to fix your IFR_ADDRESS
    Values for table SPROXSET
    regards
    SKM

  • Issues with ABAP Proxy in XI 3.0

    Hi,
    We are on XI 3.0.  We are doing a scenario of file >XI> R/3 (ABAP Proxy).
    The XML message is going to R/3 with no errors as indicated in the monitors on both XI and R/3.  The XML messages has the status of 'Message Processed'.  But, the proxy never gets executed.  Is there a step I must perform to execute the Proxy?  My understanding is that if the Receiver Communication Channel is of XI type, it will automatically execute the Proxy on the R/3 (receiving) system.
    We tested the proxy using the report SPRX_TEST_INBOUND, and it works as expected.
    Please advise.
    Thanks in advance.
    Best Regards,
    Doo

    Hi Doo,
    how do you know, that the proxy was not called?
    If you are missing database updates, check if you have a commit work in the code.
    Regards
    Stefan

  • "SOAP:Fault" in scenario with ABAP proxy client

    Hello,
    I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
    XI:
    The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
    CRM:
    The proxy generation is ok.
    SLDCHECK is ok.
    All RFC destinations are ok.
    APPINT_200_620 for CRM was installed and configured well (I think so, but...).
    When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = EST</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = BABKIN_RA</Trace>
      <Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
      <Trace level="1" type="T">PLNAME = SENDER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
      <Trace level="1" type="T">system-ID = EST</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = BABKIN_RA</Trace>
      <Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
    - <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
      <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
      <Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
      </Trace>
      <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
      <Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
      <Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      </SAP:TraceHeader>
    I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
    Does anybody know where to find a solution?
    Regards,
    Roman

    Hi Roman
    There is no need for an XI adapter for client proxy.... we only use that for server proxies.
    Vaibhav

  • Error monitoring abap proxy in WorkBench

    Hi all...
    I have a problem monitoring an abap proxy in RWB. I receive this message when i try to see the details of the message (Message Content and Queue Monitor options in Message Display Tool) in message monitoring in RWB: User PIRWBUSER has no RFC authorization for function group HTTPTREE ., error key: RFC_ERROR_SYSTEM_FAILURE. In the other side, i can see the header of the message in the message data of the same option.
    Any idea with this problem?
    Thanks...

    Hi,
    check your RFC destination. Here is more info about this error message.
    In general we get this error while trying to access Unicode / Non Unicode system using Non Unicode / Unicode RFC connection...Your RFC destination should have same Character Format of your target system
    Please checkc this property in RFC desctination under Special Option tab.
    For r/3 system, Menu->Status. Check if its unicode or not and it should have the same format as that is listed in RFC.
    The user should have following authorizations:
    SAP_XI_APPL_SERV_USER
    SAP_XI_IS_SERV_USER
    Regards,
    Venkat.

  • SAVE_STYLESHEET RC_6 error in ABAP proxy- CRM

    Hi,
    I developed a POC with just 2 fields in DT,for sender SOAP adapter and reciver ABAP proxy. It is running successfully.
    But when i developed a actual scenarios with big structure it is giving the following error.
    <?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">STYLESHEET_GENERATION_FAILURE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Attempt to generate transformation required for rendering/parsing failed (, class , method ) STYLESHEET_GENERATION_FAILURE Attempt to generate transformation required for rendering/parsing failed (SAVE_STYLESHEET RC_6, class ZII_HSBP_IN_MI, method EXECUTE_ASYNCHRONOUS /1SAI/TXS) Attempt to generate transformation required for rendering/parsing failed (SAVE_STYLESHEET RC_6, class ZII_HSBP_IN_MI, method EXECUTE_ASYNCHRONOUS /1SAI/TXS)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The only difference in both cases is, i developed everything in client 120 for POC. For actual scenario i created proxy class in client 110 and Technical system and everyting is pointing to client 120. Is it causing any problem?
    Everyting is fine in XI but in CRM SXMB_MONI i can see the above error...
    How to solve this issue.
    Message was edited by:
            ashok sri

    i tired again.. i regenerated the proxy ... but still same problem..
    i dont think internal framework problem.. because it worked for other scenario ( test scenario). I think i only messed it up some where.. but i dont know how to find out  or how to debug the problem..
    I have  a doubt on package structure in which i am saving the proxy class.
    i created a structuer package( level1) for which i assigned SAPPINT and for all other packages( level2- main package,level3-non main package, level4-non main package)i assigend SAI_SXMS, SAI_TOOLS, SAPPINT. I am saving the proxy class in level4 package. I am not able to assing SAI_SXMS,SAI_TOOLS to structure package. Is it causing any problem???????
    any help please...
    Message was edited by:
            ashok sri

  • Send message with abap proxy client

    I'm trying to send message to XI, but no message in sxmb_moni.
    I have created logical port with LPCONFIG.
    ABAP code
    REPORT  Z_HTTP_SEND.
    DATA:
    * Reference variables for proxy and exception class
      lo_clientProxy     TYPE REF TO ZPCO_MI_COMPANY_OB,
      lo_sys_exception   TYPE REF TO cx_ai_system_fault,
    * Structures to set and get message content
       ls_request         TYPE ZPMT_COMPANY_ID,
       ls_response        TYPE ZPMT_COMPANY_DETAILS.
    *Complete the structure ls_request for the request message.
    *DATA: zmt_id type ZPMT_COMPANY_ID,
    *zdt_id type ZPDT_COMPANY_ID,
    *z_id_tab type ZPCOMPANY_ID_TAB,
    *z_id type ZPCOMPANY_ID.
    *z_id-COMPANY_ID = '3000'.
    *append  z_id to z_id_tab.
    *  zdt_id-RECORD = z_id_tab.
    *zmt_id-MT_COMPANY_ID = zdt_id.
    DATA tab TYPE ZPCOMPANY_ID_TAB WITH HEADER LINE.
    tab-COMPANY_ID = '3000'.
    APPEND tab.
    ls_request-MT_COMPANY_ID-RECORD = tab[].
    TRY.
    * create proxy client
    *CREATE OBJECT lo_clientProxy( u2018LOGICAL_PORT_NAMEu2019 ).
        CREATE OBJECT lo_clientProxy.
    * do synchronous client proxy call
        CALL METHOD lo_clientProxy->execute_synchronous
                 EXPORTING output  = ls_request
                 IMPORTING input   = ls_response.
        CATCH cx_ai_system_fault INTO lo_sys_exception.
    *   Error handling
    ENDTRY.
    Any ideas? Thanks very much,

    Hi,
    Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
    ABAP Proxies uses Webservice and Http Protocols. And if you use RFC it is mainly meant for Sync. call. But Proxies is used for both Sync and Async.
    If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
    How do you activate ABAP Proxies? - Activate Proxy
    ABAP Server Proxies - ABAP Server Proxy
    ABAP Proxies in XI(Client Proxy) - ABAP Client Proxy
    Re: JDBC Sender select/update problem
    If u generate proxy for outbound interface then its client proxy and for inbound interface its server proxy.
    In client proxy u can call the method to send messages but u can't modify it but in server proxy its possible to write a user code within the method to execute proxy.
    CLIENT PROXY:
    A WSDL description from a UDDI server (or an Internet page) is usually used to make a service executable in the Internet and to describe the interface of this service. You require a client proxy and not a server proxy to call this service by using the Web service infrastructure.
    SERVER PROXY:
    You can only generate ABAP server proxies from a WSDL description if they originate in the Integration Repository.You can also generate server proxies for Java and client proxies for ABAP from message interfaces.
    s refer these doc about ABAP proxy ..
    How do you activate ABAP Proxies? - Activate Proxy
    ABAP Server Proxies - ABAP Server Proxy
    ABAP Proxies in XI(Client Proxy) - ABAP Client Proxy
    Re: JDBC Sender select/update problem
    ABAP Server Proxies
    How do you activate ABAP Proxies?
    ABAP Proxies in XI(Client Proxy)
    File to R/3 via ABAP Proxy
    http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336ea78
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd1c81
    Smarter Approach for coding ABAP Proxies
    regards,
    Surya

  • Idoc syntx error me21 , abap proxy call transaction

    Hi Experts,
    I am struck with the below problem, could you please shed some light on the issue, appreciate your help and  rewarded.
    scenario:
    XI sends NEW PO message to abap proxy, in abap proxy we populate bdc_tab
    and call ME21 as below
    CALL TRANSACTION  'ME21' using bdc_tab mode 'N' update 'S'  messages into messtab.
    problem:
    EKSEKS01 idoc is getting created with syntax error status code :26  in ECC5.0
    only 5 sigments are generated in the idocs. the three segments ( E1PISHO, E1PISIO,E1PISSO not generated).
    after transaction executed it returns subrc 1001, msgid--> ME, MSGNO --> 218.
    Thanks In Advance.
    Ranjit.

    Hi Atish and Nishant,
    Thanks much  for the immediate response.
    1.Would like to know what is the mandatory data to be passed for PO creation in BDC table.
    2. Is there any user exit or where the idoc creation happens during me21 execution.
    I have verified the po in we02 , as before mentioned the three sigments are not getting created and i am not sure the reason.
    Note: We didnot have any output configured in ECC 5.0 for this idoc to be created.
    I am really not able to locate in debug mode FOR  ME21, where this ekseks01 idoc getting created and triggered.
    Appreciate your help.
    Thanks in Advance.
    Ranjit.

  • Error in ABAP Proxy

    Hi ,
    I am getting an error in the proxy , it was working fine but today only it is throughing the following error :
      <SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
      <SAP:P1>CREATE_OBJECT_CLASS_NOT_FOUND</SAP:P1>
      <SAP:P2>ZZCL_MIIA_UKEUROPE_TLOG</SAP:P2>
      <SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during proxy processing</SAP:Stack>
    Please let me know the reason of this .
    Thanks in anticipation
    Anita

    Hi,
    I am assuming you have a server proxy (Inbound interface).
    Your proxy objects have not been created properly.
    To check this, send a message to XI.
    Either XI itself will throw an error message, or running SXI_MONITOR in receiving SAP application will show you the error . If you do not see any entry for corresponding interface, then proxy objects have not been created properly.
    Regards,
    Puloma.

  • How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

    Hi all,
           In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
    Thanks,
    YiNing

    Hi,
    While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
    I think ur data is worng,if it is wrong then only u will get this type of errors.
    Regards,
    Phani

  • Forwarding Application Error in ABAP Proxy to CCMS

    Hi,
    We are using fault messages for inbound ABAP proxy interfaces to capture application errors, and we can see the error in the monitoring of ECC. However, Is there a way, we can forward it to CCMS of ECC (and not XI), because we want to use an external tool linked to CCMS via SOLMAN to get alerted in case of application errors.
    Best regards,
    Rahul Kumar

    Is there a way of getting the above thing done? I have a very similar Issue.
    Rahul if you have found out a way of doing the same please let me know by email. [email protected]
    Thanks,
    Karthik

  • Issue with ABAP Proxy

    Hi,
        My scenario is SAP(ABAP Proxy) - XI - Web service. I can not see any messages in XI when I run the Proxy program, when I check for the outbound messages from SXMB_MONI in SAP system the message status is "Scheduled" and Q.Status shows "Message waiting in Queue" .   What could be the message status if the outbound proxy is successful?
           Can someone let me know what could be the problem and where I can check for entire scenario for these problesm?
    Thanks
    Suresh

    Hi,
    If this is not a Production System means,
    goto SMQ2 and delete all the Strucked Messages in all the Queues.
    And now goto SMQR say De-Register Queueus and
    goto SXMB_ADM--Manage Queues--Just say Register Queues
    Now Trigger your Report Program to send the data to XI.
    Check in R/3 side as well as in Xi side also in the T-code SXMB_MONI for Successfully processed messages.
    REgards
    Seshagiri

  • Transaction Update Error using ABAP Proxy

    Hi Experts,
    I am facing an issue using ABAP Proxy.
    File is coming from PI to SAP system and it will update the Transaction IE02 using this inbound ABAP Proxy. If records fails then a mail is going to concerned team.
    Issue:
    When File has been sent from PI to SAP through ABAP Prxoy, it shows that record has been updated in the Transaction IE02 but when I checked manually the record, it has not updated the same. But when I test the same record through my ABAP Prox, it updates the record and when I checked it, Reocrd hs been updated.
    Can anybody help me in this case?
    Regards
    Sachin

    Hi Anup,
    Can you please explain me for the same? If I need to put External Commit then how It is working when I running it manually
    Regards
    Sachin

  • Error With ABAP Client proxy

    Hi All,
       I am trying to use ABAP Client Proxy(Sync). I am getting the error.
    1. Message from SXMB_ADMIN on Business system.
    <b>  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="400" p2="ICM_HTTP_CONNECTION_FAILED" p3="" p4="">HTTP.HTTP_CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:Text language="EN">Error during http receive: Error code: 400 Error text: ICM_HTTP_CONNECTION_FAILED</SAP:Text>
      </SAP:ErrorHeader></b>
    2. No message On XI server.
    3.Went through the Ravikumar Allampallam's blog
    on ABAP ClientProxy .
    4. Went through the  vijaya kumari's " How do you activate ABAP Proxies?"
    5. created connections (sld)and one http connections in SM59. Tested the connections.
    6. Went throught the Forms.
    Any help would be appriaciated.
    Thank you
    Ganges Leaves.

    Vijaya Kumari,
       1. I have checked it. For XI server these are the values.
        Business System Role  : Integration Server.
        Pipe Line url : http://server:8000/sap/xi/engine?type=entry.
    8000 is the http port which i see in the SMICM+shift F1.
    Thank you
    Ganges Leaves

  • Error with ABAP in SAP HANA studio  Version: 1.80.3

    Hi,
    Am using SAP HANA studio Version: 1.80.3 and have got the ABAP perspective in here.
    I am able to connect to the SAP ABAP system via the studio, however when I open the folder, am not able to open the ABAP system folder and see objects.. on expanding the system node, I see nothing!.
    I am able to connect to this same system with HANA Studio Version: 1.0.70.
    Can you please suggest what might be wrong?
    Regards
    Sudarshan
    On a related note, when I click on the "Check for Updates" button, I get a PROXY authentication required error. Is there a way to configure the proxy authentication details in HANA studio version 1.80.3?

    PFA the screen prints of the errors and the version

Maybe you are looking for