Checking RFC destination availability

Hello,
In a transaction I'm working on, I loop at a table containing RFC destinations, and I call the same function module on each of these destinations. What I would like to do is, prior to the call, test if the system behind the RFC destination is available (neither completely crashed, nor just blocked by an administrator).
I tried to do this by simply calling any BAPI on the remote system, and check if there was a connection error. But the problem is, if the system is not down but just blocked by an administrator, the transaction suddenly displays the logon page of the remote system.
Do you know of a simple way to do this ?
Thanks in advance.

Hello Thomas
You could try with asynchronous RFC calls (for details refer to the ABAP documentation of CALL FUNCTION).
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Regards
Uwe

Similar Messages

To check RFC destination

hello All,
Is there any function module available to check RFC destination is active or not?
Thanks,
Johnny

Hi Johnny,
You can use this FM <b>RFC_VERIFY_DESTINATION</b> if your release is greater than 4.6C.
Check this sample code from Craig Cmehil's weblog.
CALL FUNCTION 'RFC_VERIFY_DESTINATION'
EXPORTING
    DESTINATION = TMP
        TIMEOUT = 10
EXCEPTIONS
    INTERNAL_FAILURE           = 1
    TIMEOUT                    = 2
    DEST_COMMUNICATION_FAILURE = 3
    DEST_SYSTEM_FAILURE        = 4
    UPDATE_FAILURE             = 5
    NO_UPDATE_AUTHORITY        = 6
    OTHERS                     = 7.
IF SY-SUBRC EQ '0'.
    "* Do code here
ENDIF.
or you can also use this FM <b>RFCPING</b> and check this sample code from other thread.
DATA : IT_RFCSI LIKE RFCSI OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'RFC_PING'
DESTINATION IT_SLS-SYST
EXCEPTIONS
    SYSTEM_FAILURE = 1
    MESSAGE RFC_MESS1
    COMMUNICATION_FAILURE = 2
    MESSAGE RFC_MESS1.
IF NOT RFC_MESS1 IS INITIAL.
MESSAGE I000(YHPA0K) WITH RFC_MESS1.
ELSE.
CALL FUNCTION 'RFC_SYSTEM_INFO'
     DESTINATION IT_SLS-SYST
     IMPORTING
       RFCSI_EXPORT = IT_RFCSI
     EXCEPTIONS
       COMMUNICATION_FAILURE = 1
       MESSAGE MSG_TEXT
       SYSTEM_FAILURE        = 2
       MESSAGE MSG_TEXT.
MESSAGE I001 WITH 'Connection to '(029)
                    IT_SLS-SYST
                    'Succeeded'(030).
ENDIF.
ENDIF.
Hope this will help.
Regards,
Ferry Lianto

CCMS aler for RFC destinations availability

Hi Experts,
We have configured ccms alert autoreaction method for availability of RFC destinations.
alert is configured with yellow thershold as 10% and red threshold as 5%.
alert text is :&1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements)".
We are receiving mail alerts for CCMS red alert for RFC saying" 0 % < 5 % 15 min. avg. value below threshold value (1 measurements) ".
But when we checked the corresponding RFC is working fine.
Can anyone please explain how this RFCs destinations check alert will work and what is the meaning of alert text ":&1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements)"."
Thank you,
Kavitha

Hi
I have done
1. RFC connection from x to y and y to x
In X system:
1. In transaction RZ21, mark Method definitions, and choose Display overview
Copyed standard CCMS_RFCDest_Availability_Col method definition to ZCCMS_RFCDest_Availability_Col
Parameters tab
For x
Parameter name = RFC_DEST
value = SM_XCLNT510_TRUSTED
Parameter name1 = COLL_METHOD
value = ZCCMS_RFCDest_Availability_Col
Same in Y but for RFC_DEST give
Parameter name = RFC_DEST
value = SM_YCLNT100_TRUSTED
Execution Tab
Type of call = Function module
Call SALK = SALK_RFCDEST_AVAILABILITY
Execute method on = The local server of the MTE to be processed
Execute method for = Individual MTE
Control tab :
Execute method for = Individual MTE
Execute method = periodically in dialog process (short-running program)
Startup method = Execute method immediately after monitoring segment start
Execution location
of startup method = Only on the central instance
Start Tab:
Execute method = Data Collection Method
also try in so many way as in :Parameter Tab:
RFC_DEST               SM_XCLNT510_TRUSTED
COLL_METHOD            ZCCMS_RFCDest_Availability_Col
MTE_CLASS              Availability_RFC_Destinations
MTE_CLASS              CCMS_RFCDest_Availability_MO_Class
MTE_CLASS              CCMS_RFCDest_Availability_Col
COLL_METHOD            CCMS_RFCDest_Availability_Col
RFC_DEST               CCMS_RFCDest_Availability_Col
Problem:
I am not able to Reset the segment in WARMUP status
not able to find the node in RZ20
Regards,
Neni

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

Post Install Activities Problem - Checking RFC Destination

I "successfully" installed Web AS 6.4 SR1 ABAP Non-Unicode. I am following the instructions in SAP Web Application Server 6.40 SR1 ABAP on Windows: MS SQL Server guide. The Post Installation instructions (2.2.6) require that I Check the RFC Destinations if my the database is located on a remote server from the central instance server.
The instructions tell me to locate the SAPOSCOL_<DB_Hostname> under the TCP/IP connections and if I cannot locate it I must add it.
In my case I cannot locate it so I want to add it. However, I do not know what data I must enter in the various fields of the RFC Destination screen. Example: what is the connection type for SQL Server
Thank you.

Hi Doug,
Is your database installed on a separate host from the SAP software? If not, you can safely ignore this recommendation and move on.
We have many systems on Win / MSS on 6.40 ABAP / Java with db and SAP on the same systems. None of my systems have this RFC, and I am not aware of any problems due to the lack there of.
Regards,
Sanket

Check RFC Destination without access to SM59

Hi,
Typically SM59 is reserved for BASIS teams in our organization.
Assuming there is no access( even read only) for SM59, is there a way (another tool) to test a RFC destination and check whether its functioning correctly ?
Regards,
Jon

Or with SE37 test RFC_PING and input the target RFC destination (and of course not NONE as in my screen)
Regards,
Raymond

Check RFC destination and Valid User

HI all!
I'm trying to verify the RFC destination in SM59 transaction. I have 2 trusted connection to other sap system with an associated account. My goal is to verify that there isn't problem regarding the account and the connection, the best it's something that try to made a remote logon and give an exception in case of:
- account isn't working
- account is working but there's no connection (think about a network problem)
Which function i could try to use to accomplish this goal ?? any idea or just made report?
I have only make a function using a BDL_SERVER_PING but isn't enough.
Help are Very apreciated
thanks!

Hi,
Use fm RFC_GET_SYSTEM_INFO
a®

Error when test for checking RFC destination

hi all,
I config "Vitual Administrator" successful follow document "Configuring ADS for Guided Procedures.pdf",
when i create ADS(sm59) with use ADSUser, system raise error "You are not authorized to view the requested resource"
and when run checking the ADS, using report FP_TEST_00, system raise error
ADS: com.adobe.ProcessingException Problem accessing d(200201)
Message : FPRUNX001
if any one seen this error, pls help me !!!
Thanks,

Have you assingned the role to that. it should be like this
7.You perform post-installation steps for Adobe Document Services.
a.You assign the required roles to users ADSUSER and ADS_AGENT
Assigning Role SAP_BC_FP_ICF to ADS_AGENT
     1. Log on to the ABAP system with user DDIC or SAP*.
     2. Call transaction SU01.
     3. Enter ADS_AGENT in the User field.
     4. Choose User Names® Change
5. Choose the Roles tab and assign the role     SAP_BC_FP_ICF to the user ADS_AGENT.
b.     You perform quick tests for Adobe Document Services (ADS).
Creating Role ADSCallers and Assigning it to ADSUSER
     1. Log on to the ABAP system.
     2. Call transaction PFCG.
     3. Enter ADSCallers in the Role field.
     4. Choose Role® Create.
     5. On the Create Roles screen, choose Role® Save
6. Choose the User tab and assign the user ADSUSER in the User   ID field.
     To Check if Adobe Services are working
Checking the User and Password
1. Open a web browser.
2. Enter the following URL:                      http:///AdobeDocumentServices/Config
3. Choose Test.
4. Choose rpdata(test...).
5. Choose Send without entering any parameters.
6. Enter ADSUser as user name and the password you   entered for this user previously.
Regards
Subhash

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 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 None Error for MIGO

Hi,
I am getting RFC Destinatnation NONE error while posting Goods Receipt. GTS service for SD and MM is not active. Error showing for FM GRC01_COST_OBJECT_COST.
Can any one help in this regard.
Thanks in advance.
SP Raj

Hi,
Pl find the details below of the error.
Short text
    RFC destination "NONE" does not exist.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLCK36" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The 'destination' "NONE" for a Remote Function Call
    is unknown.
    You can display the RFC destinations available in the system using
    the transaction SM59.
Trigger Location of Runtime Error
    Program                                 SAPLCK36
    Include                                 ISAUTO_CK_SAPLCK36============E
    Row                                     812
    Module type                             (FORM)
    Module Name                             PRICE_STRATEGY_NEW
806 ************************************************************************
807 *     DOERNER, GRC, 10/11/1999: Add one new strategy:
808 * 3b. Create costestimate during goods receipt
809 ************************************************************************
810     when 4.
811       if k_debug_loc is initial.
>>>>>         call function 'GRC01_COST_OBJECT_COST' destination 'NONE'
813                 exporting
814                      im_vbeln     = f_mtcom-vbeln
815                      im_posnr     = f_mtcom-posnr

The RFC Destination ALESERVER is not available

Hi ,
I am getting the error message " The RFC Destination ALESERVER is not available " in my CRM Web UI screen.But when I login with another User ID , this error message is not showing.
RFC connections are maintained in transaction SM59 and BD97.but I m still facing with this issue.
Please advice what could be the cause of error.
Regards,
Ravi

Hello,
please check in SM59 the LOGON-User for this RFC-Destination.
Maybee the user where it works is maintained, the other not.
Or if there is a general RFC-User maintained the user where it does not work has maybee not the authorization in the target.
Best regards
Manfred

Available RFC Destinations

Hello,
How can i check the available RFC destinations in J2EE engine on Portal.
(without Visual Administrator)
Regards

Hi,
you could for example check the JCO log in the J2EE:
<root>\usr\sap\<SYSID>\DVEBMGS00\j2ee\cluster\server0\dev_jrfc.trc
As well you could check the server or default trace.
--> from above location
.\log\defaultTrace.0.trc
.\log\server\server.0.log
For that you could use the log viewer of the J2EE (under services).
As well check all the settings for the JCO service in the J2EE.
Rgds Thomas

Error-The RFC destination EDSCLNT900 is not available in ICWC

Hi All,
I'm working on CRM Utilities 2007. In the ICWC, I'm getting the error 'The RFC destination EDSCLNT900 is not available'. Kindly help me in resolving this error.
Regards,
Archana.
Edited by: archu_sap on Jul 15, 2009 10:30 AM
Edited by: archu_sap on Jul 15, 2009 10:33 AM

Hi,
You have to maintaine RFC Destination EDSCLNT900 in the CRM system.
generally we have to maintain RFC (t-code SM59) in the sytem where Function Module is present.
Suppose you are having FM in ECC system and you want to call in CRMsystem, then you have to maintain RFC destination (EDSCLNT900) in ECC system.
Thanks & Regards.
ShreeMohan

Function module for checking existance of rfc destination?

hi all,
is their any function module for checking existance of rfc destination?
regards
deepak

Hi,
check teh table 'RFCDES'.
reward if helpful.
Regards,
nagaraj

Checking RFC destination availability

Similar Messages

Maybe you are looking for