SM 59 in Proxy scenario

I have a proxy to file scenario.
Do I have to create SM 59 transaction details mandatorily ? There are already existing proxy to file scenarios from the same SAP syatem in the development server. So someone would have already created the RFC Destination. Or should I do it now ?
Again, I guess without creating RFC destination,  we will not be able to see the interfaces while  using client proxy and creating proxy using T code SPROXY. Is my understanding correct ?
Also when we are dealing with server proxies then do we have to go for RFC Destinations ?

Hi Ajith,
the connetion are for systems, once RFC destination is maintained for you PI system in SAP system  and vice versa.Then no need to create again the connection for the similare scenario.Do a connection test in SM59 to test the same or configure your new scenario and test.
I guess without creating RFC destination, we will not be able to see the interfaces while using client proxy and creating proxy using T code SPROXY. Is my understanding correct ?
In SPROXY you will see the PI ESR content.There is no link between the RFC connection for systems and SPROXY.
But there are some RFC destination to be created to enable SAP system to connect to ESR when you execute the SPROXY tcode.
If your facing issues like the Service interface/SWCV  which is there in ESR is not visible in SPROXY then please check.
If a connection to the Integration Repository could not be established at the start of the transaction, you can ascertain more exactly what went wrong, and fix this problem (or have it fixed), by choosing Goto  ®  Connection Test.On connection test you will get a description of what is missing and create it accordingly
refer the configuration guide.

Similar Messages

  • FTP to ABAP Proxy Scenario - getting error CO_TXT_CHANNEL_PASSWORD_ERROR

    We have transported PI and EP data from development server to respective production, every thing is running fine except the abap proxy scenarios i.e. PI reads file from ftp location and calls the abap proxy but we are getting following errors:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter
    <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="">
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = FD768D4A8772DB50E1000000AC10041E) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023)</SAP:Stack>
    Any solution?
    Please note that I have searched and applied solutions given on SDN forums but didn't get any success. So I am looking for new suggestions.
    Jawed Ali

    Jawed ,
    Please test the HTTP destination of your receiver comm channel.
    Which is the RFC connection to your R3 system.
    Transaction SM59 and check the logon parameter for the connection you are using.

  • EOIO is not working for file- BPM- Proxy scenario.

    Hi All,
    I have one File to BPM (Merge pattern ) to Proxy scenario.
    I have two file communication channel at the sender side and defined QOS as EOIO for both. In SXMB_MONI it assings same queue for all messages.
    BPM is merging that messages. However during that it assings different queue for merged messages.
    When it comes to proxy , again different queues are assingned to the messages.
    Is there any way I can define QOS in BPM or at the proxy side ( I know it should be at the sender side only , but it's not working..)
    Thanks & Regards,
    Dijesh Tanna.

    Within the current release the BPM will always only use EO (SAP Note 833740).
    May be the SAP note  905049 will help you on this ...

  • Issue in Iodc- abap proxy scenario

    Hi all
    I have a idoc to abap proxy scenario. The issue is ,
    when we send the idoc to client A of target system, it works ifne.
    But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
    Is it because of any error in XI configuration or somethin else.

    hi all
    thanks for all your responses.
    I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
    I gave the conditions in Receiver Determination.
    Same Server Proxy  is used in both the target business sytems.
    I have done all the Configuration Steps ,( Created two separate business systems also )
    Also I have checked wiht all the system settings to be made in the target system B.
    When i trigger the idoc to Client 100, it goes to XI and then reaches  Client 100 of System B
    without any problem. I get the desired result from proxy code.
    When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
    the Call Inbound PRoxy step. (from sxmb_moni)
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
    Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
    But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

  • Error in FILE 2 Proxy Scenario

    Hi All,
    I am doing File to Proxy Scenario i am getting following error
    Could any one provide the solution for this.
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Inbound Proxy*
    - <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="">
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_Emp_Sender, request message, namespace )</SAP:Stack>
    Thanks in Advance
    Edited by: Mahesh Reddy on Jul 10, 2008 12:47 PM

    Hi Mahesh,
    1) Use SPROXY transaction.
        Menu-> Proxy -> Activate All.
    2) check in the interface determination if u are using correct
    inbound interface.
    3) If this if fine....try deleting all proxy objects of the interface
    and create new.
    Praveen K

  • Data stuck in QRFC in client proxy scenario

    In client proxy scenario (proxy to file async). I triggered the report porgram from ECC and I the green flag moni in ECC but the mesage is did nto reach PI as it got stuck in qrfc. It reaches PI upon clearing the message from SMQ2. Please help solve this.

    this problem persists when queues are not registered or any abapstack workitem gets into error.
    select the workitem in smq2. execute it manually. after completing the execution, goto sxmb_adm tcode, there select manage queues. then register queues.

  • File to Proxy Scenario : Error in communication channel monitoring

    I have developed File to Proxy Scenario on PI 7.1 system and it is not working. I see the below error in communication channel monitoring.
    u201CError: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.u201D
    File will be picked from the FTP server.
    I have created File system in SLD of type "Third Party", Can this be the issue?
    Please guide me on this.

    Check if the tcode SLDCHECK is ok!
    Check note #764176.
    Also, refer to link below and execute each steps from the links there MANUALLY.
    Wizard-Based Configuration:
    Caio Cagnani

  • File to ABAP Proxy Scenario

    Hi All,
    I am  doing File-to-ABAP Proxy Scenario, in the sender side side it is picking the file, but in sxmb_moni it is giving the error:
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Adapter*
    - <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="1">
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Message ID 4CFF4691EEE211DC85E30019D1522982 already exists in called system (pipeline CENTRAL)</SAP:Stack>
    Can u plz tell me why this error is occurring and how we can resolve this error.
    Thanks & Regards,

    Hi Vikas
    make a dummy change and activate your object then make a full refresh
    you can make it through in 3 ways
    1) tcode SXI_CACHE
    2) go to ID -> environment and make a full cache refresh
    3) http://<host>:5<sys#>00/CPACache/refresh?mode=full     Full CPA cache refresh
    when you do the developement then these are stored in ABAP data dictionary table which can be refreshed by delta cache
    while full cache will delete this temporary object and make this cahe into runtime
    hope this will help you
    if helpful reward points

  • SOAP - Proxy Scenario

    In my SOAP to Proxy scenario I have a proxy that will return "true" or "false" depending on the logic in my method.  When I execute the proxy it returns the false value for cases that are false in SAP.  The scenario does not return the "true" value when the logic is true in SAP.  If I go into SAP and run the method, both the true and the false logic paths work and the method returns the correct value.  If I hard code the variable in the method to "test" and execute the XI scenario it will return the word "test" for both cases, true and false.  I have the same scenario in my XIQ system and it works fine. 
    So, what I have done...
    I have flushed the cache, that did not work.
    I have rebooted my XI system that has the problem.
    I have compared my XI broken system with the one that is working and there are no differences.
    Does anyone know how I can see what is truely being sent back to the SOAP side?  Is there a way to debug the ABAP code from the XI / SOAP side?
    Any help would be greatly appreciated.
    Skip Ford

    Hi Ford
    When you try with SAP its working right. Did you see that response in XI. If not then no need to touch XI.
    Take the payload and try to debug the proxy. You will come to know if it really returns the true value or there is a data issue itself and no problem with XI and SAP.
    Check in XI mapping as well. if the value from source is moving to target or not. If you make any changes or found problem do regenerate and activate proxy.

  • SOAP to Proxy scenario communication error

    Hi Friends,
         Now i am developing SOAP to Proxy scenario,  i am testing WSDL file using SOAP UI software and i am getting an error in SOAP UI tool.
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <title>Error Report</title>
    td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
    A:link {color : #0059AA;}
    A:visited {color : #999999;}
    A:active {color : #999999;}
    <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
    <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
    <tr bgcolor="#FFFFFF">
    <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  403   Forbidden</b></font></td>
    <tr bgcolor="#3F73A3">
    <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
    <td height="23"><img width=1 height=1 border=0 alt=""></td>
    <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP NetWeaver Application Server </b></font></td>
    <tr bgcolor="#9DCDFD">
    <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
    <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  Error: You are not authorized to view the requested resource.</b></font></p>
    <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>  <a href="">SAP Technology Troubleshooting Guide</a></b></font></p>
    <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table>
    <td valign="top"><b> Details:</b></td>
    <td valign="top"><PRE>No details available.</PRE></td>
    I have tried with the same WSDL earlier  it was working fine, now its not working and throwing the above error.
    Kindly suggest me to overcome from this issue.

    Hi Senthil,
    Try with the authentication preemtive. Also, check your URL because that error seems that you are accessing to wrong PI section or your user has not the enough credentials, try with PIAPPLUSER or with the same roles that this user.

  • SOAP- Proxy scenario, issue with WS adapter

    Hi guys,
    i've set up a soap->abap proxy scenario (on 7.1) and want to use the new WS adapter. unfortunately I'm facing some issues. The proxy has been generated properly and I also set it up in soamanager. I tested it from XML Spy and it works fine. So there shouldn't be any problem with it.
    But when I try to run the scenario, I get following error:
    <sap:ExceptionChain xmlns:sap=""><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException><sap:ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException></sap:ExceptionChain>
    System error while calling Web service adapter: <sap:ExceptionChain xmlns:sap=""><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when processing Web service
    I checked the /sap/xi/engine service on both - PI & ECC and it is activated.
    Any hint, what could be wrong?
    Thanks a lot,

             "ICM_HTTP_CONNECTION_FAILED" this error is relaed to ICM. Does your Type H connection "INTEGRATION_SERVER_HMI" works fine.And check integration engine configuration in SXMB_ADM.
    And here is a similar thread.
    Re: HTTP to Enterprise Services.

  • Proxy Scenario (abap client)- XI, ICM_CONNECTION_FAILED

    Hi Forum,
    I have a problem with a Proxy Scenario (ABAP client proxy),
    My scenario is R/3 (abap client proxy)--->XI   ,
    the client proxy while sending message to XI throws an error, which is seen in SXMB_MONI as:
    404 Resource not found
    Partner not reached
    Error: -20
    Version: 6040
    Component: ICM
    Date/Time: Fri Jan 25 09:20:54 2008 
    Module: icxxconn_mt.c
    Line: 2124
    Server: xxxap5_RP1_05
    Detail: Connection request from (143/22024/0) to host:, service: 8000 failed (NIEHOST_UNKNOWN) AP-T143, U22024, 500 xxUSER, , 09:20:54, M0, W0, , 1/0
    I can see a stuck entry (LUW), for this in SMQ2, even on several re-execution of that LUW in SMQ2, it gives an error:
    XI Error Client_Receive_Filaed

    404 Resource not found
    There might be the problem with the server having not to find anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    *Possible Tips:- *
    • 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
    • Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
    • If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
    • If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination
    Refer below link

  • INTERNAL - AMF_ERROR in XML -- ABAP proxy scenario

    Hi Experts,
    Can any one help me to solve this following issue please, it is happening while I am executing the scenario between XML File to ABAP Proxy scenario.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
    - <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="">
      <SAP:Code area="INTERNAL">AMF_ERROR</SAP:Code>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error when processing message number 1 in package No object type found for the message. Check that the corresponding process is activated An exception has occurred.</SAP:Stack>
    This XML message has got 5 Lines Header and more than 100 Lin Items, this kind of Header and Lin item message 3 to 4 in one XML, I am using multi mapping. Message mapping shows working fine, OM also shows working fine. BPM is splitting messages to send messages to ABAP Proxy on SNC 7.0. After I have done all with SDN experts support, still I am having the above issue. can any one experties might help to resolve this?
    I will appreciate your support.
    Thanks & Regards

    Can you please explain the solution.

  • HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

    Hi Friends
    I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
    - <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="">
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
    Any ideas will be helpful.

         I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check  specific server confiration in SXMB_ADM.

  • ABAP Application Error in Proxy scenario

    Hi All,
    I have a Proxy to Proxy scenario. I can see that few message are successful, whereas few are failing in ECC side. The messages are not stuck in Queue. It is giving a "ABAP" _APPLICATION ERROR. Has anyone faced this error before?
    Lavanya R

    Issue with Application end, Ask to developer to deebug the codu using the failed xml message.

  • Creation of package structure for ABAP proxy scenario

    Hi All,
    I have a doubt on package structure used for ABAP proxy scenario. What is the specific reason to create a four level package structure? Can some one please explain? Thanks in advance.

    Hi Sudheer,
    Can you pls clarify what do you mean by 'four level package structure' ?
    Are you referring to the ABAP structures that get created during creating the proxy by SPROXY transaction ? These structures get automatically created. We simply have to write the code using these structures.
    Or do you mean the 'package' which is mandatory to create a transportable ABAP object ? i.e. transport from Development to Staging and then Production.

Maybe you are looking for