When you maintain authorizations for SAPUI5 Fiori apps, which of the following object types is the front-end authorization object type?

Question

Options

• ATADIR IWSV - SAP Gateway Business Suite Enablement-Service
• BTADIR G4BA - SAP Gateway Odata V4 Backend Service Group & Assignments
• CTADIR IWSG - SAP Gateway: Service Groups Metadata
• DTADIR INA1- InA Service

• A
  79% (41)
• B
  6% (3)
• C
  12% (6)
• D
  4% (2)

Explanation

TADIR IWSV (SAP Gateway Business Suite Enablement-Service) is the front-end authorization object type because it represents the OData services registered and exposed on the SAP Gateway (front-end) server - access to these services is enforced at the front-end layer via the S_SERVICE authorization object, which checks against IWSV entries. IWSG (C) is incorrect because it represents Service Group metadata used for grouping and cataloging services, not the direct authorization check object. G4BA (B) is incorrect because it pertains to OData V4 backend service group assignments, placing it on the back-end side of the two-system Fiori architecture. INA1 (D) is incorrect because InA (Information Access) services are used by SAP Analytics tools like SAP Analytics Cloud, not standard Fiori app front-end authorization.

Memory tip: Think "SV = Service on the front-end Viewer side" - IWSV is the object your users see and call through the browser, so it lives on the front-end Gateway where the UI5 app is served.

No community discussion yet for this question.