GRC 10 SP13: Authorizations for RFC User

[Former Member]

Hi Gurus,

Just wanted to get your opinion on the RFC user authorizations required for the Backend ECC connector. Have been getting mixed opinions so thought would discuss it with you here. The authorizatios as per the Migration guide (Section 4.3.1) for Access controls are as under:

Just wanted to confirm if there have been any revisions for this or are these more than sufficient?

Many thanks in advance.

Would appreciate an early response as I am about to start the sync jobs soon.

Regards,

Ronnie.

[former_member193066]

You need to have trusted RFC

Before a trusted system can be defined, a destination for this system must be created in the trusting system. In addition, the RFC users must have the corresponding authorizations in the trusting system (authorization object S_RFCACL). You can check the authorizations for the logged on users in the trusting system in advance, by using the function module AUTHORITY_CHECK_TRUSTED_SYSTEM.

Authorization Object S_RFCACL

Defined Fields
This authorization object contains the following fields:

RFC_SYSID: ID of the calling system or the domain of the satellite system

RFC_CLIENT: Client of the calling system

RFC_USER: ID of the calling user

RFC_EQUSER: Flag that indicates whether the user can be called by a user with the same ID (Y = Yes, N = No)

RFC_TCODE: Calling transaction code

RFC_INFO: Additional information from the calling system (currently inactive)

ACTVT: Activity
Currently, this field can take the value 16 (Execute).

[former_member225453]

Hi Ronnie,

The Auth object S_RFCACL for RFC Trusted connections.

Regards,

Shreya Gupta