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

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 RFC_VERIFY_DESTINATION 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 RFCPING 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

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

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

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®

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

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

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

Enable Secure communication for RFC destinations by using sm59 transaction

Dear friends,
We would like to enable secure communications for RFC destinations by using the sm59 transaction in our systems.
We need to do this manually, by changing the internal communication settings in a way they can communicate securely.
Any idea or advice on the way it can be done ?
We need to take each RFC, manually check it and secure it.
Thanks in advance,
Jordan

In SM59 open up a RFC destination and go to Logon & Security. There you can enable Trusted relashionship and activate status of secure protocol.
And yes you have to do it manually for the desired RFC's

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 Test?

Is there FM to Test a RFC Destination?

Hi Ruben,
SM59 is the transaction to test for RFC destination.
Just click on REMOTELOGON button. It will open destination system logon.
The function module /SDF/SL_RFC_GET_CLIENT_REMOTE will determine the RFC destination.
The function module ARFC_DEST_CONFIRM will confirms destionation of RFC.
The function module RFC_CHECK_DESTINATION will check the destionation of RFC.
Thanks,
Vinay

NO RFC Destination for BAPI

Hi,
I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
BUS6010 Method POST & CHECK
BUS2072 Method FINDDETAILS
I am using the Program RHINLV00_LSO to transfer data.
When i execute this report it's throwing an error
" NO RFC Destination for 2 BAPI's".
An RFC Destination is created in SM59 to link the two systems and i have distributed the distribution model to R/3 4.7.
The Function modules are marked as Remote enabled function modules.
Regards,
Ramesh K.

Hello,
Did you test RFC destination whether the definition is working fine or not?
You can test the destination,if it's working fine,then Bapis' should be able to execute.
Thanks.
Mark points if helpful.

NO RFC Destination for BAPI's

Hi,
I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
BUS6010 Method POST & CHECK
BUS2072 Method FINDDETAILS
I am using the Program RHINLV00_LSO to transfer data.
When i execute this report it's throwing an error
" NO RFC Destination for 2 BAPI's".
An RFC Destination is created in SM59 to link the two systems and i have distributed the distribution model to R/3 4.7.
The Function modules are marked as Remote enabled function modules.
Regards,
Ramesh K.

Hi,
After creating the distribution model with 3 methods in ECC 6.0 (source system). Generated Partner profile automatically from BD64. Then distributed the distribution model to the other system i.e., SAP R/3 4.7 successfully. Then created partner profile from that system automatically.
Port, partner profiles,outbound parameters, inbound parameters were created successfully.
Thanks
Ramesh

Table stores RFC destination

Dear all,
Do you know the table that stored RFC destination that defined via SM59?
Please comment.

HI,
Check the Table RFCATTRIB and RFCDES
Cheerz
Ram

Check RFC Destination without access to SM59

Similar Messages

Maybe you are looking for