Unable to configure trusted RFC no matter what

[symon_braunbaer]

dear Experts,

We need working trusted RFC connections from Solution Manager to an S/4 Hana system and vice versa.
The connection from S/4 to the Solution Manager works!

However, no matter what we tried, from the Solution Manager to the S/4 system simply doesn't work. It ALWAYS 
comes back with the following error:

What we tried so far:

- Recreated the trusts in SMT1 for both systems!
- Fixed yellow fields of role SAP_S_RFCACL and regenerated the profile and reassigned the roles. Profiles are in place too!
- Parameter rfc/allowoldticket4tt is set to value both on all systems
- Transaction SSO2 is green
- We tried also using role SAP_S_SM_RFCACL
- Resetting all buffers

PLEASE suggest a solution!

[symon_braunbaer]

Thanks for not posting even a single reply!
But I will share one update. I have tried setting the following profile parameters:

Unfortunately still NO LUCK 😞

[Vera_Jiang]

Just adding tag "NW ABAP Remote Function Call (RFC)" to involve more attention to the question.

[Sandra_Rossi]

You didn't tag correctly your question, it's not a SolMan-specific question, it's RFC or admin question. "Fixed yellow" is meaningless, which exact authorization for the fields of the authorization object S_RFCACL?

[Vera_Jiang]

Dear Customer, 

What's the value of parameter auth/rfc_authority_check in the S/4HANA system? If it is allowed, please set it to 1. For other values of the parameter, please check the SAP Note 2216306. If the parameter auth/rfc_authority_check is set it to 6, implement SAP Note 2765303 in transaction SNOTE of SAP Solution Manager system and check the result in step Maintain RFCs.

Best regards,
Vera Jiang 

[symon_braunbaer]

Dear Vera, many thanks for having a look at my BIG problem! On Friday I tried a ton of things which might solve the issue. One of them was also manipulating the parameter auth/rfc_authority_check. It was already set to 1. I also tried with the value 4. Unfortunately all this without any luck. I wanted to post this here, but was busy with other stuff. So there must be some other reason... I am starting to think about something with the gateway ??

[Vera_Jiang]

Dear Symon, A similar case I worked before was resolved by the RFC team by the following steps: 1. review and apply Note 3287611 - Bugfixes in Trusted/Trusting Migration in both the solman and managed ABAP system if it is valid. 2. proceed with the migration steps mentioned in this SAP Note 3157268 - How-To-Guide: Migration of Trusted/Trusting Relationships. Please try the steps. Best regards, Vera Jiang

[symon_braunbaer]

Thanks a lot for your suggestion! I started implementing Note 3287611 in the DEV Solution Manager. Unfortunately it didn't work 😞 I am getting the following error:

What to do now ?

P. S.: I have read in some SAP note, that if parameter rfc/allowoldticket4tt is set to both, a migration is not necessary. An in our case this parameter is set like that.

[Vera_Jiang]

Dear Symon, please do the following 1. see and perform the solution in KBA 3321072 'Object Directory Entry LIMU COMM does not exist' when implementing TCI 2. see the content in Note 3287611: In case you are on SAP_BASIS relaese 7.31 or 7.40 and downloaded the note 3089413 before 25th February 2023 please apply note 3304520. Please know that Note 3089413 is a bit complicated. Read it carefully. Also share the Kernal version patch and SAP_BASIS version. Best regards, Vera Jiang

[symon_braunbaer]

Dear Vera, thank you very much! The Solution Manager has Kernel 753 Patch 1217, SAP_BASIS is 740 Patch 29. I have so far implemented notes 3257359 and 3304520. Now I will try to continue with the other 2 notes that you have mentioned. One note was again giving the LIMU missing error, which shouldn't be the case anymore 😞

[symon_braunbaer]

Dear Vera, I made quite some effort - updated the Kernel of the Solution Manager system to version 7.54 Patch 500. I have also implemented the following notes:

1. Implement SAP Note 3257359 - SNOTE: To allow object overwriting if there is no customer modification
2. Implement SAP Note 3304520 - Trusted trusting
3. Implement TCI note 3089413
4. Implement the latest version of SAP Note 3287611

In the end, I have launched the migration of RFC destinations in transaction SMT1 on the Solution Manager system. For the system to which we need to have working trusted RFC destinations, the job log says: Uses new method already. However when I click Login, the same error message 00024 keeps showing up 😞 Please advise how to fix this! Thank you!

[Vera_Jiang]

Dear Customer, Thank you for your efforts. I have suggested all from solution manager support point of view, it's suggested to wait for "NW ABAP Remote Function Call (RFC)" team response, or for complex issue, please contact SAP Support on BC-MID-RFC. Best regards, Vera Jiang

[symon_braunbaer]

Thanks a lot for your help! I really hope that someone else will give further ideas and suggestions...