RFC Destination issue

Hi
I am facing an issue  while providing destination for RFC function module.I dont know  how to get the destination.
Many of friends suggested me that we can get it through SM59. As I dont have authorisations for SM59,I could'not do.
Is there any table or other alternate??
I have one more doubt,
Say suppose my RFC function module exist in R/3  development system and I am calling it from SCM  development system. assume  that destination for R/3 development system is DA4200.When  we move our calling program and R/3 RFC function module  to Quality system, destination will be changed.For quality system destiantion would be QA4200. How can we achieve it  programatically?/
do we need to pass RFC destiantion dynamically?/ if  yes? how ?
Please reply me. It is an urgent
thanks
Rama

Hi Rama,
We have to define the RFC Destination at the time of Function Module Call.
Check this link for more:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
and this is step by step for SM59
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/frameset.htm
Sachin

Similar Messages

  • Inbound proxies rfc destination issue

    Hi Gurus,
    Im currently using sending xml message to Integration server using runtime workbench to inbound proxy of SAP ECC system
    I used XI adapter on the receiver side ..the HTTP destination configured in PI server connecting to sap ecc system is having the following details.
    host name ---sap ecc hostname
    service no --abap http port 8080 which is available in smicm.
    logon client is 110(testing client not dev client)
    i dont know why even after making all the settings in SM59 ,the message is not going to SAP ECC system.
    am i missing anything.
    Any help appreciated.
    Thanks,
    Jay

    Jay ,
    try giving your IP address insted of your host name.
    Regards,
    naveen

  • Issue with RFC destination during HCM - VDS - IDM configuration

    Hi,
    I am trying to configure HCM and IDM (v7.1) using VDS. I am following the Configuration Guide. While creating the RFC Destination, I specified program ID as LDAP_VD and in Gatewayhost I have entered the host of IDM Server (where VDS is also installed). In Gateway service I have put sapgw00. But when I do connection test, I get u201CERROR: SAP gateway connection failed. Is SAP gateway started?u201D. Looks like it is trying to connect to IDM server and is looking for sapgw00 (on port 3300) and is not able to find it.
    What could be the reason for error? Am I doing RFC destination configuration correct? Do I need to put HCM system host in the Gatewayhost field?
    Regards,
    Anurag

    Hi Anurag
    You have to enter the hostname of the SAP server, not the LDAP server.
    The LDAP connection is configured later.

  • An RFC destination could not be specified for the logical system

    Hello Experts,
    I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
    An RFC destination could not be specified for the logical system
    SB3CLNT011
    Message No. B1550
    Diagnosis
    An RFC destination should be specified for the logical system SB3CLNT011.
    This could not be done in this case. SB3CLNT011 is not your local logical system
    and this system is not included in the relevant Customizing tables.
    Procedure
    Check:
    RFC
    destination
    Port
    definitions
    oubound partner profile of
    message type SYNCH for this logical system
    Regards,
    Khushboo

    Hi Oritra and Suraj,
    I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
    Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
    System SB3CLNT011 as a partner type already exists
    System SB3CLNT012 as a partner type already exists
    Port A000000018 with RFC destination SB3CLNT011 already exists
    Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
    Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
    Outbound parameters for message type SYNCH SYNCHRON already exist
    Am I missing something in WE20?
    Regards,
    Khushboo

  • RFC Destination Connection Pool requirement

    Hi Experts,
    I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
    There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
    I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
    Application & Access Details
    Application Location : Home Screen
    Concurrent Users     : 600 concurrent users maximum possible value
    Connection Usage    : Close connection immediately using disconnectIfAlive() method.
    Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
    I have read a lot of post and documents but could not acheive clarity of thought on this.
    Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
    Regards,
    Porselvan

    Hi Muthavudaiyan,
    Hope you are doing good.
    Basically from the JCo perspective, there are only 5 parameters that are involved here:
    jco.destination.pool_capacity:
    Maximum number of connections that are held open in the pool for reuse (default: 1)
    jco.destination.peak_limit:
    Maximum number of connections that can be obtained from a pool at peak usage times
    jco.destination.max_get_client_time:
    Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
    jco.destination.expiration_time:
    Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
    jco.destination.expiration_check_period:
    Regular time interval for checking if pooled connections have expired and will be closed
    The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth

  • Error in Local Message System: RFC destination MB3AP1039 does not exist.

    Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
    Message no. BCOS088
    Hi,
         When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
    Can anyone help me in resolving the above issue.
    Thanks & Regards,
    Mirza Kaleemulla Baig.

    Dear friend
    You have to of following option
    1.Define Service Desk destination in the R/3 systems:
    Note: for this you need to log in the R/3 system.
    Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
    2.a. Go to transaction SM30.
    b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
    c. Press the Continue button in the following screen:
    d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
    e. In the next screen, enter the following information:
    In the RFC Destination you should point to your Solution Manager destination RFC.
    0ss_msg   w   sm_bsmclnt_back    cust620     1.0
    shailesh

  • Third Party (Garnishment) checks - RFC destination error

    We have an issue with our testing of Third Party Garnishment checks.  We have a split system, with our HCM system residing separately from the remaining ECC modules.
    We are getting an error in regards to the printing of the checks in A/P.
    The posting is working fine
    the vendor account is cleared
    However, It’s not creating a check # or check form.
    We can do other check runs in this client fine; it’s just the 3PR runs that cause the error.
    The text of the error message is as follows:  An RFC destination could not be specified for the logical system HPQCLNT210.
       We have exhausted our resources here looking into the RFC connection and the partner profile and we cannot find anything wrong with them.
    Can someone offer suggestions on what else we could check?  Thanks so much.

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • RFC destination error in posting 3rd party payment in 4.7 FI system

    Hi,
    We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
    The error says "An RFC destination could not be specified for the logical system HD1CLNT014
        Message no. B1550
    Diagnosis
        An RFC destination should be specified for the logical system
        HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
        local logical system and this system is not included in the relevant
        Customizing tables.
    Procedure
        Check:
            -   RFC destination
               -Port definition
             -oubound partner profile of message type SYNCH for this logical system
    We checked our configuration for all Logical system and RFC destination and everything seems fine.
    Any help in this regard is appreciated.
    Thanks
    Kesav

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • RFC destination definition with non-unicode external program

    Hello All,
    we have one issue with our RFID system connecting to WM system (SWD). 
    For most functions, external RFID server/middleware makes RFC call to SAP system.  Means, from outside system to inside SAP.  This seems to be working fine.
    But in one case, SAP needs to print label to RFID printer.  In this case, SAP is calling external RFID server/middleware using RFC destination.  Means, from inside SAP to outside system.  This is failing.
    We think this has something to do with ECC60 being unicode system, and the RFC destination setup.  We define rfc destination "ZRFID_SSI" in SM59.  We define it same way as in as-is SSI 4.6B production system.  But in SWD ECC60 system, SM59 has more options.  We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server.  RFC destination is actually working ok.
    To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI.   Listener on RFID server/middleware will respond to function call.  This also seems to be working.  But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0".  (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
    Compared with production environment, everything is the same, except that SAP is unicode system.  So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data.  I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange.  Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
    Anyone know how to help ?

    Hi Jeongbae,
    as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
    In earlier releases, this is not possible.
    In general, SAP systems use the logon language (SY-LANGU)  to determine the code page, if this is available.
    Please check SAP note 788239.
    Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
    In addition I would recommend to have a look at SAP note 1021459.
    However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
    For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
    Best regards,
    Nils Buerckel
    SAP AG

  • RFC Destination was incorrect,send complete BP Data again from CRM to R3

    Hello All
    Iam facing in issue in CRM - BP Application due to incorrect RFC Destination maintained for SAP R3.
    Our CRM Testing system (CRO - Client 300) is connected to R3 Testing System (NCQ - Client 300), but when CRM system went for refresh, RFC Destination was overwritten, and due to that CRM system started pointing to wrong R3 server (NCD - Client 002).
    Till we got to know the problem, User had created a BP in CRM and it had flown to incorrect server. later we corrected the RFC Destination , but now the issue is that If I make any small change in CRM BP data, Bdoc  is going in error state and message says:
    Messages for business partner 0090001677:
    No customer is assigned to business partner 4A13ACE0AB356006E10000000A212
    Entry 0500   does not exist in  - check your entry
    I tried to send BP data through middleware tCode /CRMM_Bupa_Send as well, but Bdoc gain got in error state saying :
    Entry 0500   does not exist in  - check your entry
    I think, these errors are coming because system is assuming that it has already sent the data to R3, and it expects certain data to be present in R3 system, which it is unable to find since data for corresponding BP is not present in SAP R3.
    I there any way, transaction through which I can send complete BP data from CRM to R3??? Please help.
    Edited by: Surbhi Goel on Jun 2, 2009 3:25 PM

    Hi Surbhi,
    Could you try transaction CRMM_BUPA_MAP in order to see what mapping the system thinks there is (if any). It then allows you to send (same as BUPA_SEND) or retrieve data. I guess this will run into the same error, but it might be worth a try.
    Hope this helps.
    Sincerely,
    KZ

  • Error in Local Message System: RFC destination 10.189.98.10 does not exist.

    Error in Local Message System: RFC destination 10.189.98.10 does not exist. Message was Not Created
    Message no. BCOS088
    Hi,
          When iam going inside the tcode SM30 in the satellite system and entering the destination ip of solution manager system and after that when iam creating a message from HELP-CREATE SUPPORT MESSAGE, then it is throwing the following error.
    Can anyone please help me in the above issue.
    Regards,
    Mirza Kaleemulla Baig.

    Hi Mirza,
    For the RFC destination don't enter the IP address,enter the RFC name,somthing like SM_SP1CLNT200_BACK which is maintained in sm59.
    Revert for any clarifications.
    Thanks and Regards,
    Avinash.

  • How to create RFC Destination without using SM59?

    Hello all:
    We are troubleshooting an issue.   An user created a RFC destination.   He claims that he did not use SM59.   We checked his access and do not have SM59 in his roles.
    He configured VIRSA FireFighter.   During the configuration, he created RFC destination.   Document says use SM59 or contact BASIS Admin.     He claims that he used a config table and he don't remember the config table name.   RFC screen shows his ID as creator of the RFC.
    We are trying to understand how an RFC can be created (outside of SM59) and plug the security hole in the environment.
    Any insights would be appreciated.
    --Anand

    The FireFighter solution changes the RFC destination of the service user "on the fly" without S_TCODE checks for 'SM59'. But if I can remember correctly when looking into this, it does not create the RFC destination (in SM59) "on the fly".
    > He claims that he used a config table and he don't remember the config table name.
    Theoretically this is possible - a config table to define the name of the destination, and then create it if it does not exist yet (when used).
    Otherwise, see SAP note 587410 and restrict (remove) his authority for the test environment (concentrate on S_DEVELOP, not S_TCODE - as you have also experienced).
    Cheers,
    Julius

  • How to send data to RFC Destination(RFC SENDER Adapter)

    Hi ,
    Scenario:  R/3 Backendà RFC Sender Adapterà XIàsome other system.
    I have configured the RFC destination (of the type TCP/IP) at R/3 System and have registered the Program ID (specified in the RFC destination) in the XI server and using it in the configuration parameters of the RFC Sender Adapter.
    Problem: I do not know how I can send data to the RFC destination. (Should I use a report program/ ABAP Function Module?) Can anybody provide me with a sample code of Report Program/Function module (whichever is required), how to send data to the RFC Destination, so that it may be picked up by my RFC Sender Adapter.
    Thanks and Regards,
    Siva Maranani

    I have one query for you that
    I am trying to develop a scenario in SAP XI
    SAP R/3 ( RFC function module) sends a synchronous request to the XI and SAP XI will send this request to a third party web application using HTTP receiver adapter.
    I am able to send the data/message and it is successfully received at the third party web application.
    But I am facing one issue that I am unable to receive any message/data in my RFC module back.i have seen in sxmb_moni that the two messages are displayed in successfuly processed but in SAP R/3 side nothing get happedned
    Can you tell me how to use some waiting mechanism in function module to wait for the response from SAP XI.
    Regards
    Gopesh

  • After Transporting the request RFC Destination is empty in SWCV and BEA

    Hi All,
    we are using SAP NW Mobile 7.1 SP08
    After transporting the SWCV & Backend adapter, in the transported system the RFC Destination is empty
    Please help me to fix this issue.
    Thanks and Regards,
    Joseph Beevin.

    Hi,
    When an SWCV is trnasported to a another system,the backend destination will be empty in the target system.,We need to configure the bakcned destination in the target sytem through the DOE Adimin.
    DOE_ADmin Portal -->Configuration --->Backend Configuration.
    In the backend configuration,select the SWCV for which the destination needs to be configured.Select the parameter "RFC  DESTINATION FOR BACKEND"
    When the SWCV is selected all the active Data Objects will be listed in the table below
    Insert the above parameter to the parameter list(the table below)
    Give the name of the availlable backemnd destination name in the "text value" column of the table for each data object and save it.
    Now the backend destination is configured correctly in the target system.Please try this..
    Regards,
    Muralikrishna T.

  • RFC Destination SAPFTPA is not working

    Hi,
    I am able to connect FTP via RFC Destination SAPFTP which is for front end but RFC Destination SAPFTPA for background run is not able to connect with FTP location.
    I have checked the trace with program RSFTP005 and it looks okay. However, when I run RSFTP002 to test the RFC destination SAPFTPA it gives error message " Attempted to connect ftp destination failed "
    Please, let me know if I need to check something in SM59 ( I suppose all is well there as the RFC destination would be created automatically ).
    Thanks,
    Alok Mehta

    Hi
    Greetings!!
    Actually i am also stuck up in a similar situation.
    When I use SAPFTP as the destination since it works. However with SAPFTPA, i am getting the same login error as in your case.
    If you were successful in getting the issue resolved, can you please share the solution.
    with best regards,
    Hector

Maybe you are looking for