cancel
Showing results for 
Search instead for 
Did you mean: 

Issue due to different Ids of Basis and developers in SolMan and Managed Systems

Former Member
0 Kudos

Hi Experts,

I am in the process of implementing GChaRM.

My client has different naming convention for user Ids in different systems.

The naming convention for the user Id in Non-PRD differs from the convention for PRD.

Naming convention for the users in SolMan is also different.

Due to this different set of naming conventions, we are facing issue in establishing a trusted connection through the Trusted RFC.

As this RFC utilizes the user Id currently logged in SolMan but the same Id is not available in the managed system.

Due to this different set of Ids, even the developers are not able to navigate to the related managed systems through the ChaRM UI webpage.

Can anyone suggest a possible long-term solution to this issue?

Thank you.

Regards,

Gopal

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member186154
Active Participant
0 Kudos

Hi Gopal,

It is mandatory for the user id to be exactly same in both the trusted and the trusting system involved in the Trusted RFC connection. Without this the trusted logon wouldn't be possible to connect to the managed system through the RFC.

Regards,

Kathir

rishav54
Active Contributor
0 Kudos

Hi Gopal,

Strange situation though.

Can you check if you can address your situation through S_RFCACL through individual user, though it will be a lot of manual work.

RFC_EQUSER Value N

Change the values for fields  RFC_USER and RFC_CLIENT accordingly.

Please find below note with detailed explanation.

128447 - Trusted/trusting systems

Thanks

Rishav