The SAP system release
level determines how authorization checks are performed for BW and
BI objects. In releases before SAP BI 7.0, SAP uses the reporting
authorization that uses the SAP standard authorization concept. For
BI 7.0 and later, SAP uses an authorization concept for analysis authorization.
SAS/ACCESS Interface to R/3 delivers one Business Add-In (BADI) that
implements the reporting authorization and one BADI that implements
analysis authorization.
During installation,
SAS is configured to use one of three implementations for table access
authorization checks. The default implementation when no BADI is activated
uses the SAP authorization object S_TABU_DIS. If you want to use one
of the two BADI implementations, you must activate it during installation.
Here is a description of the implementations.
Authorization Check Implementations
Authorization Check
Implementation
|
|
|
S_TABU_DIS authorization
object
|
Classic BADI /SAS/AUTHBW01
|
Compatible with BW and
BI systems. User authorization checks are performed at the InfoCube,
InfoObject, and ODS levels using the reporting authorization (SAP
standard authorization concept).
|
Enhanced BADI /SAS/IM_AUTHBI01
|
Compatible with BI 7.0
and later systems. User authorization checks are performed using the
analysis authorization. This not only provides an authorization check
for the infoProvider (infoCube, infoObject, and DSO) but also column-level
restrictions on master data attributes and key figures, and row-level
restrictions on attributes.
|