GRC 10 SP13: Authorizations for RFC User

[Former Member]

Hi Gurus,

Had been reading some stuff on the authorisations needed for the RFC user which is required to connect to the backend ECC systems and getting mixed opinions. Just needed a quick confirmation and views if all the authorisations mentioned in the Migration guide titled "AC10_Migration_SP09_en" are enough for the RFC user?

For your reference, copying below the section of the migration guide (Section 4.3.1, Page 16 onwards) mentioing the required objects - FOR AC. Could you please confirm if these Authorizations are enough?

Many thanks as always. Would appreciate a quick reply as I need to schedule the background 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).