Skip to Content
Technical Articles

Maintain RFC’s in Managed system Configuration- Common Errors

Wondering how to handle the Step Maintain RFC’s in Managed system configuration in a rigid restricted environment.? Of course, managed system configuration is pretty hard task when we don’t have access to the managed system and limited access as a Solman consultant.

 

 As shown Above  1. Assign Product and 2. check prerequisite is pretty much automated whereas the real task begins from step 3 Maintain RFC. Automated user creation from Solman system is simple but when comes to secured environment its not possible and they are created explicitly by authorization team which we need to use ,where one can find a lot of challenges.

I ll make sure this scenario is simplified and by end of this blog you ll be able to complete the RFC steps seamlessly, as I have covered few significant recurring errors.

 

Most frequent Errors during RFC step are covered below 

 

  1. RFC Error when providing the Managed system Master User

  1. RFC Error-2 when providing the Managed system Master User

 

  1. RFC Error during READ & TMW RFC

 

  1. Few RFC Error Logs

  1. No RFC Authorization for function module “RFCPING” (ST22 Dump)

 

  1. No RFC Authorization for function module SUSR_GENERATE_PASSWORD” (ST22 Dump)

 

Here are the common solution steps for all the above issue

  1. Ensure the Host file entries of managed systems are maintained with physical and virtual server entry.
  1. Check if the correct host name of managed system is maintained in RFC step 3.

 

(Go to advanced mode in Step 3 and check/maintain correct host name in right side as shown below. Do not touch left side, as it is meant for Solman host.)

 

     3. Double check if Role ZSAP_RCA_CONF_ADMIN, ZSAP_SM_USER_ADMIN (its equivalent              role in customer namespace) is applied to Managed system Master user.

4. “If you connect a managed system with SAP_BASIS component (check in system status )                   higher than 702, check SAP Note 2257213. For some scenarios, you must manually add a                 role.” – Add those updated roles from given Note 2257213.

5. Check ST22 for dump with any missing Function Module /Function group. Those missing ones           has to be added under S_RFC object. Below is the list of updated Function Module values as of         8/2020 which you can adapt under RFC_NAME (Below shown is a rough idea)

List of updated Function Module values under S_RFC object

For Managed system Admin User (Check latest Note 2257213 for newly added values frequently)

S.NO RFC_NAME values S.NO RFC_NAME values S.NO RFC_NAME values S.NO RFC_NAME values S.NO RFC_NAME values
1 /BDL/* 9 DSVAS* 17 SALC 25 SCSM* 33 SUGX
2 /SDF/* 10 DSWP* 18 SALF 26 SCT1 34 SUU6
3 /SDF/CCMS_READ 11 DSWP_BPM_FUNC 19 SALH 27 SCT2 35 SYST
4 /SDF/SM 12 HTTPTREE 20 SALS 28 SEC_SSO2 36 S_CUS_IMG_ACTIVITY
5 /SOMO/* 13 QRFC 21 SAL_CACHE_RECEIVE 29 SEWA* 37 S_IMG_TOOL_3
6 /SSF/INTRFC 14 RFC1 22 SCCA 30 SLCA 38 THFB
7 BDL* 15 RFCPING 23 SCCR 31 SRFC 39 URFC
8 DMD* 16 SADB 24 SCPR_HELP 32 SRTT 40 W3_UTILITIES

  

 

As mentioned earlier ,direct user creation from Solman system is a straightforward process., however the catch is when we don’t have access to the satellite systems.
For the latter scenario, highly recurring RFC issues have been addressed in this blog, this should certainly resolve the RFC issue. For any other uncommon issue related to RFC , please check the referenced Notes and you’ll certainly nail it down.
Hope this helps. Get going.
Cheers !!

 

 

References:

  1. 2569749 – Troubleshooting RFC_NO_AUTHORITY dump – Guided Answers

2. 2779684 – “BACK destination SM_<SOLMAN SID>CLNTXXX_BACK, with user                                                    SMB_<MSSID>, created with errors” in step Maintain RFC’s

Be the first to leave a comment
You must be Logged on to comment or reply to a post.