Accessing and Using R/3 Data |
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 have to activate it during
installation. A description of the implementations follows:
Authorization Check Implementations
Authorization Check Implementation |
Description |
(Default, no BAdI) |
Authorization object S_TABU_DIS |
Classic BAdI /SAS/AUTHBW01 |
This BAdI is 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 |
This BAdI is 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. |
Copyright © 2008 by SAS Institute Inc., Cary, NC, USA. All rights reserved.