An authorization based on what object is required for trusted system access to an SAP Fiori back-end server?

Question

Options

• AS_START
• BS_SERVICE
• CS_RFC
• DS_RFCACL

• A
  4% (1)
• B
  12% (3)
• C
  8% (2)
• D
  77% (20)

Explanation

S_RFCACL is the authorization object specifically governing trusted system (trusted RFC) connections between SAP systems. In a Fiori architecture, the front-end server communicates with the back-end server via a trusted RFC destination, and S_RFCACL controls which external systems are permitted to call the back-end without providing a password - making it the gating object for this trust relationship.

Why the distractors are wrong:

• S_RFC (C) authorizes access to RFC function modules/groups for a user, but does not govern whether a system-level trust relationship is permitted - it's about what can be called, not who is trusted to call.
• S_SERVICE (B) authorizes access to ICF (Internet Communication Framework) services and is relevant to Fiori's HTTP/OData layer, but not to trusted RFC back-end access.
• S_START (A) controls the authorization to start applications (transactions, Fiori apps), which is a UI/launchpad concern, entirely unrelated to trusted system connectivity.

Memory tip: The "ACL" in S_RFCACL stands for Access Control List - think of it as the bouncer's list for RFC callers claiming to be "trusted." If your system's name isn't on S_RFCACL, it doesn't get trusted entry to the back-end, no matter what.

No community discussion yet for this question.