SAP Library - Find your answers

SAP Trusted Relationships between each other. (Ex : R/3 to CRM, R/3 to BW)

If a calling SAP system is known to the called system as a trusted system, no password must be supplied.

The calling SAP system must be registered with the called SAP system as a trusted system. The called system is called the trusting system.

A calling system can be defined in the called system as a 'trusted system', using transaction SMT1. The called system is then referred to as the 'trusting system'.

Trusted ABAP systems can log on to other ABAP-based SAP systems without a password. This kind of trusting relationship between ABAP-based SAP systems has the following advantages:

"Single sign-on" can be used across systems

No passwords are transferred across the network

Timeout mechanisms for logon data prevent misuse

User-specific logon data for the trusted system is checked

You can set up multiple SAP systems as mutually trusting systems. When a trusted relationship is set up between two systems, the initiative comes from the called system (server system). The user of the calling system, who can execute RFC calls by means of a trusted relationship, has to be made known in the called system (trusted user).

Before a trusted system is defined, a destination has to be created for this trusted system in the trusting system. Also, the RFC users have to have the corresponding authorizations in the trusting system ( authorization object S_RFCACL). The authorization for the logged- on user in the trusting system can be checked in advance using the AUTHORITY_CHECK_TRUSTED_SYSTEM function module.

In a trusting relationship, the calling system (client system) has the role of the trusted system, and the called system (server system) has the role of the trusting system.


Configure Trusted Systems : SMT1

Display Trusting systems : SMT2