SAP Reference

Understanding the SAS Federation Server Driver for SAP

The SAS Federation Server Driver for SAP enables SAS Federation Server to read tables from SAP systems. The SAS Federation Server Driver for SAP has read-only capabilities.

The SAS Federation Server Driver for SAP supports most of the FedSQL functionality. The driver does not support the application's ability to submit native SQL statements.

The SAS Federation Server Driver for SAP is a remote driver, which means that it connects to a server process in order to access data. The process might be running on the same machine as SAS Federation Server, or it might be running on another machine in the network.

Data Service Connection Options for SAP

The table below describes the data service connection options for the SAS Federation Server Driver for SAP.

Option

Description

ABAPFM

ABAPFM = abap_function_name

Specifies the name of the Advanced Business Application Programming (ABAP) function module that the driver uses internally. The default is /SAS/Z_SAS_DIALOG.

Alias: ABAPFUNCTION, ABAPFUNC

ABAP_NAMESPACE

ABAP_NAMESPACE
                                 =namespace

Specifies the namespace for ABAP functions and programs that are used by the driver. If the ABAP programs are installed in the customer namespace rather than in the default namespace, this parameter identifies where the ABAP programs are installed. The default is /SAS/

Alias: ABAPNAMESPACE, ABAP_NAME_SPACE, ABAPNS, ABAP_NS

ABAPPROG

ABAPPROG
                                 = abap_program

Specifies the name of the ABAP language that the driver uses internally. This value is set by the ABAP function module. The default is /SAS/Z_SAS_READ.

Alias: ABAPREPORT, ABAPPROGRAM

ASHOST

ASHOST=application_server_host

Specifies the host name of the server or IP address of a specific application server. There is no default.

Alias: HST, RFCHOST, R3HOST

BATCH

BATCH =
                                 0 | 1 | Y | N

Specifies whether the SAS Federation Server Driver for SAP should use SAP batch jobs for the data extracts. If set at Y (Yes), the SAS Federation Server Driver for SAP uses batch jobs to extract R/3 data. When set at N (No), the SAS Federation Server Driver for SAP uses dialog processes to extract R/3 data. The default is N (No).

Alias: BATCH_MODE, BATCHMODE

BUFFER_SIZE

BUFFER_SIZE
                                 = buffersize

Sets the minimum buffer size for data transfers in batch and dialog modes. The number of bytes should be greater than 10,000 and no more than eight digits. The default is 100,000 bytes.

Alias: BUFFERSIZE, BUFFSIZE, BLOCK_SIZE, BLOCKSIZE

CLIENT

CLIENT=client_number

Specifies the SAP logon parameter client. Examples for a client are 000 or 800. The default is the SAP system default.

Note: When you access the SAP system using the driver, specify valid logon information including CLIENT,

USER
                                 NAME

, PASSWORD, and LANGUAGE. The user ID and password can also be passed through single sign-on (SSO). The driver performs a logon check at OPEN time.

Alias: CLI, RFCCLIENT, RFCCLI

DEFAULT_ATTR

DEFAULT_ATTR=(attr=value)

Used to specify connection handle or statement handle attributes supported for initial connect-time configuration, where attr=value corresponds to any of the following options:

CURSORS=n- Connection handle option. This option controls the driver’s use of client side result set cursors. The possible values are 0, 1 or 2.

0	Causes the driver to use client-side static cursor emulation if a scrollable cursor is requested but the database server cannot provide one.
1	Causes the driver to always use client-side static cursor emulation if a scrollable cursor is requested. The database server’s native cursor is not used.
2	(Default) Causes the driver to never use client-side static cursor emulation if a scrollable cursor is requested. The database server’s native cursor is used if available. Otherwise, the cursor will be forward-only.

Example: DEFAULT_ATTR=(CURSORS=2)

USE_EVP=n - Statement handle option. This option optimizes the driver for large result sets. The possible values are 0 (OFF) or 1 (ON), which is the default. Example: DEFAULT_ATTR=(USE_EVP=0)
XCODE_WARN=n - Statement handle option. Used to warn on character transcoding errors that occur during row input or output operations. Possible values are 0 (returns an error), 1 (returns a warning), or 2 (ignore transaction errors). 0 is the default. Example: DEFAULT_ATTR=(XCODE_WARN=1)

DESTGROUP

DESTGROUP=destination_group

Specifies the name of the destination group for batch access to the SAP system. The destination groups are defined in the /SAS/DESTS table in SAP. The default is SAS1.

DESTINATION

DESTINATION=destination

Specifies the destination in the saprfc.ini file, if working with a saprfc.ini file. If the RFC server is an R/3 system, this destination must also be defined in the SIDEINFO file for the SAP gateway.

Alias: DEST, DST, DSTN

GROUP

GROUP=application_server_group

Specifies the name of the group of application servers for load balancing.

GWHOST

GWHOST = gateway_host_name

Specifies the host name of the SAP gateway, if the server is R/2 or external.

Alias: GATEWAY_HOST

GWSERV

GWSERV = gateway_service

Specifies the service of the SAP gateway, if the server is an R/2 server or external.

Alias: GATEWAY_SERVICE

IEEE_REVERSE

IEEE_REVERSE
                                 = Y | N

Specifies whether floating point numbers are byte reversed. The possible values are Y (floating-point numbers are byte reversed) and N (floating-point numbers are not byte reversed). The default value for an R/3 application server on Windows NT is Y. On other platforms, the default value is N.

INENCODING

INENCODING
                                 = code_page

Specifies the code page. Indicates the code page of the SAP server. The encoding is determined by the value returned by the SAP server. In some rare cases, it might be necessary to override this value by setting the

inencoding
                                 =

connection parameter.

LANGUAGE

LANGUAGE
                                 = language

Specifies the SAP logon parameter language. The value for language is either the 2-byte ISO-language key or the 1-byte SAP-language. Examples for the language are EN, DE or E, D. If not specified, the language set on the SAP system is the default.

Note: When you access the SAP system using the driver, specify valid logon information including CLIENT,

USER
                                 NAME

, PASSWORD, and LANGUAGE. The user ID and password can also be passed through single sign-on (SSO). The driver performs a logon check at OPEN time.

Alias: LANG, LNG, RFCLANG, RFCLNG

MAX_TABLE_JOINS

MAX_TABLE_JOINS
                                 = number

Specifies the number of tables that can be used in a left outer join or an inner join in ABAP Open SQL. The default is 25.

Alias: MAX_TABLES_JOIN, MAX_TABLES_JOINS, MAX_TABLE_JOIN

MSHOST

MSHOST = message_server_host

Specifies the host name of the Message Server for load balancing.

NAMESPACE

NAMESPACE=namespace

Specifies the name space to be viewed with directory services. Also used to apply table filters that limit the number of SAP namespaces returned by the SAS Federation Server Driver for SAP by specifying multiple items in a comma-delimited string:

NAMESPACE={T000,
                                    AAA, B1}

PWD

PWD=password

Specifies the SAP logon parameter password.

Note: When you access the SAP system using the driver, specify valid logon information including CLIENT,

USER
                                 NAME

, PASSWORD, and LANGUAGE. The user ID and password can also be passed through single sign-on (SSO). The driver performs a logon check at OPEN time.

Alias: PASSWORD, PASSWD, PW, PASS

R3NAME

R3NAME=system_name

Specifies the name of the R/3 system, if load balancing is being used.

RFC_STRING

RFC_STRING
                                 = additional_rfc_options

Specifies additional logon or connection parameters for the RfcOpenEx() call. The SAS Federation Server Driver for SAP uses the RfcOpenEx() call to log on to the SAP system. Using this option, parameters which are not connection attributes for the SAS Federation Server Driver for SAP, can be passed to the RfcOpenEx call. For example: RFC_STRING = "ABAP_DEBUG=1". This option can be used to support future extensions of the RfcOpenEx call.

Alias: RFCSTRING, RFC_OPTIONS_EXT, RFCOPENEX, ADDITIONAL_RFC_OPTIONS

SAPLOGON_ ID

SAPLOGON_ID
                                 = saplogon_id

Specifies the string defined for SAPLOGON on a Windows 32-bit system.

SYSNR

SYSNR=system_number

Specifies the SAP system number, if load balancing is not being used. The number is the two-byte code that identifies the system on the host, for example, 00 and 01.

Alias: SYS, SYSTEM, SYSNO

TRACE

TRACE =
                                 0 | 1 | Y | N

Specifies if the SAS Federation Server Driver for SAP should trace requests. If the trace option is set to 1 or Y, the driver writes log information into a file. The RFC library logs messages in the dev_rfc file. The default setting is 0 (N), RFC trace is off.

Note: The RFC trace directory is set using the RFC_TRACE_DIR environment variable.

UID

UID = user

Specifies the SAP logon parameter user.

Note: When you access the SAP system using the driver, specify valid logon information including CLIENT,

USER
                                 NAME

, PASSWORD, and LANGUAGE. The user ID and password can also be passed through single sign-on (SSO). The driver performs a logon check at OPEN time.

Alias: USR, USER, RFCUSER, USERNAME, USERID

Installing and Configuring the SAS Federation Server Driver for SAP

Overview

Installing the Driver for SAP involves several steps that you must complete in the appropriate sequence. Review the system requirements and authorization profiles, set up the SAS Federation Server Driver for SAP, and then install the SAP® components on the SAP system and SAS Federation Server.

After installing the SAS Federation Server Driver for SAP, you must complete additional steps to configure it to be used by SAS Federation Server.

SAS Federation Server Driver for SAP Requirements

The following list identifies the system requirements for a SAS Federation Server Driver for SAP that are used by SAS Federation Server. After the driver is installed, verify that the following requirements have been met:

SAP System

The SAP Kernel Release 4.6C or higher is required.

The SAS Federation Server Driver for SAP for Windows® and UNIX® requires the 64-bit SAP Unicode RFC library, Release 7.10, which is provided by SAP AG. Refer to SAP Note 413708 for the current version, download and installation instructions.

SAPGUI

During the installation of the SAP components, a SAPGUI is required.

User IDs

An SAP user ID and password is required. The user ID must have appropriate authorizations to access data and use communication methods. For more information about customizing the authorization, see Authorization Profiles below.

To install and run SAS Federation Server Driver for SAP, the following SAP user IDs are required:

RFC user This is an SAP user ID that is used for the communication link between the SAS Federation Server Driver for SAP and the SAP System Application Server. Typically, there are several RFC user IDs (one per person).
SAP System Administrator An SAP System Administrator ID is required for the installation of ABAP programs and function modules, for the configuration of destinations and variant for batch operations, and for setting up authorizations for user IDs to use the SAS Federation Server Driver for SAP. This user ID is used only for the installation.

Connectivity

The SAS Federation Server Driver for SAP and the SAP Application Server usually use TCP/IP communication. Refer to the RFC documentation from SAP AG. The host of the SAP Application Server must be known by the host of the SAS Federation Server Driver for SAP. Alternatively, you can use the IP address to identify the SAP System Application Server. The TCP/IP services file must contain entries for the services, ports, and protocols used for the communication.

The following is an example for entries in the services file:

sapdp00 3200/tcp
sapdp01 3201/tcp
sapdp99 3299/tcp
sapgw00 3300/tcp
sapgw01 3301/tcp
...
sapgw99 3399/tcp
sapsp00 3400/tcp
sapsp01 3401/tcp
...
sapsp99 3499/tcp

Note: If the SAPGUI is installed on the system, the TCP/IP services file already contains these entries.

Authorization Profiles

To install and use the SAS Federation Server Driver for SAP, a user ID with certain authorizations is required. An authorization has an authorization object. Several authorizations can be bundled together into an authorization profile.

If the batch functionality of the SAS Federation Server Driver for SAP is used, the RFC user ID needs to have authorization to submit batch jobs already released.

The RFC user IDs require authorizations for the following authorization objects:

Object	Minimum Requirement for Values	Example for Predefined Authorization
S_RFC (Authorization check for RFC access)	ACTVT: * RFC_NAME: * RFC_TYPE: *	S_RFC_ALL
S_TABU_DIS (Table maintenance via standard tools such as SM31)	ACTVT: 03 DICBERCLS: *	S_TABU_SHOW
S_BTCH_JOB (Background processing: Operations on Background Jobs) ¹	JOBACTION: RELE JOBGROUP: *
¹ Required only if batch functionality of the RFC server is used.

The existing authorizations, for example S_TABU_SHOW, can be used. The S_RFC and the S_TABU_DIS authorizations are in authorization profile A_ANZEIGE.

Setting Up the SAS Federation Server Driver for SAP

This section describes the set up for the SAS Federation Server Driver for SAP after the software has been installed.

Complete the following steps on SAS Federation Server:

Install the Unicode RFC libraries from SAP.

The SAS Federation Server Driver for SAP requires the 64-bit version of the SAP Unicode RFC libraries, Release 7.10. The libraries must be installed on SAS Federation Server. These shared libraries are provided by SAP AG. Download and install the 64-bit Unicode libraries for your platform, following the instructions in SAP Note 413708.

Set the environment variables.

The SAS Federation Server Driver for SAP executable uses the SAP shared libraries. You must add the location of the SAP RFC shared libraries to the shared library path environment variable specific to your operating system. For Windows, ensure that the shared libraries are installed in the system path, or add the directory of the installed SAP Unicode RFC libraries to the Path environment variable. For UNIX, replace rfclib_directory in the table below with the directory where the RFC shared libraries are installed.

AIX
Bourne Shell	$ LIBPATH=rfclib_directory:$LIBPATH $ export LIBPATH
C Shell	$ setenv LIBPATH rfclib_directory:$LIBPATH

HP-UX
Bourne Shell	$ LD_LIBRARY_PATH=rfclib_directory:$LD_LIBRARY_PATH $ export LD_LIBRARY_PATH
C Shell	$ setenv LD_LIBRARY_PATH=rfclib_directory:$LD_LIBRARY_PATH

HP-UX for the Itanium Processor Family Architecture
Bourne Shell	$ LD_LIBRARY_PATH=rfclib_directory:$LD_LIBRARY_PATH $ export LD_LIBRARY_PATH
C Shell	$ setenv LD_LIBRARY_PATH=rfclib_directory:$LD_LIBRARY_PATH

Linux for Intel Architecture, Linux for x64, Solaris, and Solaris for x64
Bourne Shell	$ LD_LIBRARY_PATH=rfclib_directory:$LD_LIBRARY_PATH $ export LD_LIBRARY_PATH
C Shell	$ setenv LD_LIBRARY_PATH=rfclib_directory:$LD_LIBRARY_PATH

Installing SAP Components

Verify the Prerequisites

Make sure that you have fulfilled the following prerequisites:

SAPGUI Prerequisites

The installation of the SAS Federation Server Driver for SAP components require SAPGUI software to be installed on your PC or workstation.

Note: Although it is not absolutely necessary to have the SAPGUI installed on the same PC or workstation where the SAS Federation Server Driver for SAP is going to be installed, you need access to the SAPGUI during the installation. Because the usage of the SAPGUI complements SAP functionality, it is recommended that the SAPGUI be installed on the same PC or workstation.

SAP Administrator ID Prerequisites

A valid SAP user ID and password is required. The user must have authorization to transport files and for RFC destination maintenance. It is strongly recommended to get assistance from your SAP System Administrator to perform these tasks.

Install ABAP Programs and Function Modules

Delivery transport files are included in the SAS Federation Server Driver for SAP. These transport files include all of the components, ABAP programs and function modules needed to run the SAS Federation Server Driver for SAP.

The delivery transports have to be imported on each SAP application server that is going to be accessed by SAS Federation Server. If an SAP system is upgraded, the delivery transports have to be imported again.

Two sets of transports are included, one for releases prior to SAP Release 7.0 and one for SAP Release 7.0 and above. You must import the transport files that apply to your system.

Version	Transport	Purpose	To be applied to
SAP systems prior to SAP NetWeaver 7.0 (Kernel 6.40 or earlier)	SAPKA93120INSAS Note: This transport must be installed first.	Supports the SAS Federation Server Driver for SAP	All SAP systems to be accessed by the SAS Federation Server Driver for SAP
SAP NetWeaver 7.0 based systems and later	SAPKA93130INSAS Note: This transport must be installed first.	Supports the SAS Federation Server Driver for SAP	All SAP systems to be accessed by the SAS Federation Server Driver for SAP
	SAPKB93031INSAS	Supports new BI 7.0 authorization concept	Optional; SAP BI 7.0 systems and above; only apply if you are using the new authorization concept

To import the transport files to your SAP systems, follow the instructions below. The instructions are based on the usage of the tp program (a utility for transport between SAP systems) on the operating system level.

Note: Replace HOME in these instructions with the actual directory path where SAS Federation Server is installed.

Log on as SAP System Administrator to the SAP application server.

Move the transport files from SAS Federation Server into the appropriate directories on your SAP systems.

Windows	Copy the r3trans.exe file to your SAP application server and extract the files into the transport directory, for example, HOME:\share\SAP. The files for all transports will be put into the cofiles and data subdirectories.
UNIX	Copy the r3trans.tar file to your SAP application server and extract the files into the transport directory, for example, HOME:/share/SAP. Assuming that the TAR file is downloaded to the user's HOME directory, follow these procedures to extract the files into the cofiles and data subdirectory in `/usr/sap/trans`. .`$ cd /usr/sap/trans$ tar -xvf $HOME/r3trans.tar`

Change to the transport program directory using the following command:

Windows	`<drive>:` `cd \usr\sap\trans\bin`
UNIX	`$ cd /usr/sap/trans/bin`

Load the transport into the transport buffer and import the transport into your SAP system with the following commands. Replace SID with the system ID for your SAP system.

tp addtobuffer  SAPKA93120INSAS SID
tp import SAPKA93120INSAS SID U2

Note:

Make sure you are using the correct profile for the transport control program tp. In some cases it might be necessary to use the parameter pf= to specify the TPPARAM file.
Because the transport file uses a long name, the nbufform=true TP option must be set. The option can either be maintained in the SAP system using transaction STMS, or it can be specified as a parameter to the tp command. Also, the TP option tp_version= must be set to at least 264 to allow the long names.
The U2 option allows the originals to be overwritten if the user has previously installed these ABAP objects.
The transports contain only client-independent ABAP objects. The tp import can therefore use any existing client that is correctly set up for imports. Verify that the ABAP program RDDIMPDP is correctly scheduled in the client that you use for the import.
If the transport files are imported into a Unicode SAP system, use the transport profile parameter "setunicodeflag=true" to force setting the Unicode flags in the imported programs. Refer to SAP Note 330267 for more details. The "setunicodeflag=true" is not necessary if you are using the transports for SAP NetWeaver 7.0 based system and higher. Those transports have been created with the Unicode flag.

Considering these notes, the tp commands might require additional parameters. Replace SID with the system ID for the SAP system.

Note: The tp commands listed on several lines in the following examples should be entered on a single command line. Be sure to include a space before adding the text from each of the following lines.

SAP Release prior to SAP NetWeaver 7.0 (Kernel 6.40 or lower), non-Unicode SAP Server
Windows	tp addtobuffer SAPKA93120INSASSID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL -D"nbufform=true" -D"tp_version=264" tp import SAPKA93120INSASSID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL -D"nbufform=true" -D"tp_version=264"
UNIX	$ tp addtobuffer SAPKA93120INSAS SID pf=/usr/sap/trans/bin/TP_DOMAIN_sid.PFL -D"nbufform=true" -D"tp_version=264" $ tp import SAPKA93120INSASSID pf=/usr/sap/trans/bin/TP_DOMAIN_sid.PFL -D"nbufform=true" -D"tp_version=264"
SAP Release prior to SAP NetWeaver 7.0 (Kernel 6.40 or lower), Unicode SAP Server
Windows	tp addtobuffer SAPKA93120INSASSID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL -D"nbufform=true" -D"tp_version=264" -D"setunicodeflag=true" tp import SAPKA93120INSASSID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL -D"nbufform=true" -D"tp_version=264" -D"setunicodeflag=true"
UNIX	$ tp addtobuffer SAPKA93120INSASSID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL -D"nbufform=true" -D"tp_version=264" -D"setunicodeflag=true" $ tp import SAPKA93120INSASSID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL -D"nbufform=true" -D"tp_version=264" -D"setunicodeflag=true"
SAP NetWeaver 7.0 based systems and later, Unicode SAP Server
Windows	tp addtobuffer SAPKA93130INSASSID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL -D"nbufform=true" tp import SAPKA93130INSASSID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL
UNIX	$ tp addtobuffer SAPKA93130INSASSID pf=/usr/sap/trans/bin/TP_DOMAIN_sid.PFL -D"nbufform=true" $ tp import SAPKA93130INSASSID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL -D"nbufform=true"

Maintaining RFC Destinations

Note: If the SAS Federation Server Driver for SAP will execute requests using the SAP batch processing facility (recommended), you must complete this section.

The SAS Federation Server Driver for SAP uses multiple RFC destinations (TCP/IP connection type) for accessing an SAP System in batch. The number of destinations setup for the SAS Federation Server Driver for SAP limits the number of concurrent requests to the SAP application server.

For example, create six destinations with connection type T and activation type Registered Server Program that can be used by the SAS® server. The program ID for the registered server program must be unique on the SAP gateway.

RFC Destination Name	Program ID
SAS1	RFC.SAS1
SAS2	RFC.SAS2
SAS3	RFC.SAS3
SAS4	RFC.SAS4
SAS5	RFC.SAS5
SAS6	RFC.SAS6

Complete the following steps:

Call transaction SM59 in SAP. Specify transaction code /nsm59 in the command field.
Click Create.
Enter SAS1 as the RFC destination.
Enter T as the Connection type.
Enter a description for the destination.
Click Enter.
Choose Registration for the Activation Type or Registered Server Program in the Technical Settings tab.
Enter the RFC.SAS1 as the program ID.
If required, enter the gateway host and gateway service in the Gateway Options panel. The gateway host is the host name of the local gateway and gateway service is usually sapgwsysnr, where sysnr is replaced by the system number of the SAP system.
(Unicode SAP systems only) Select the Unicode on the MDMP & Unicode tab. Ignore the message about performing the Unicode test. The Unicode test cannot be performed with the destinations created for the SAS Federation Server Driver for SAP.
Save the destination.
Repeat step 1 through 11 for each of the new RFC destinations.

Maintaining the /SAS/DESTS Table

The RFC destinations defined in the previous step must be grouped into destination groups. The groups are defined in table /SAS/DESTS which is used for controlling the access to the destinations from the SAS Federation Server that accesses the SAP system. The destination group is a parameter of the SAS Federation Server Driver for SAP. The default is "SAS1".

Complete the following steps:

Call transaction SM30 in SAP. On the command line, type transaction code /nsm30.
In the Table field, enter the table name /SAS/DESTS.
In the Restrict Data Range field, select No Restrictions.
Click Maintain.
An information message appears. Click OK.
Click New Entries.

For each of the RFC destinations that you defined in step 2, enter the destination group ID as the SAS ID and the RFC destination name. The following examples define the destinations for destination group SAS1:

SAS ID	RFC Destination	Used
SAS1	SAS1
SAS1	SAS2
SAS1	SAS3
SAS1	SAS4
SAS1	SAS5
SAS1	SAS6

Save the table.

Activating BAdI Implementation

The SAS Federation Server Driver for SAP has three basic implementations for table access authorization checks. The default implementation uses the SAP authorization object S_TABU_DIS to check the authorization. If you want to use any of the other two implementations you have to activate the appropriate BAdI implementation.

BAdI Implementation
Default	Authorization object S_TABU_DIS
Classic BAdI /SAS/AUTHBW01	For BW and BI: User authorization checks at the InfoCube, InfoObject and ODS level using the reporting authorization (SAP standard authorization concept).
New BAdI enhancement /SAS/IM_AUTHBI01	For BI 7.0+ only: User authorization checks using the analysis authorization. This not only provides an authorization check for the infoProvider (infoCube, infoObject, DSO) but also column level restrictions on master data attributes and key figures, and row-level restrictions on attributes.

In releases prior to SAP NW BI 7.0, SAP uses the reporting authorization concept that uses the SAP standard authorization concept. If you want to activate the SAS implementation for those authorization checks:

Call transaction SE19 in SAP. In the command field, type transaction code /nse19.
Enter /SAS/AUTHBW01 as the implementation.
Click Activate.

In BI 7.0, SAP introduces a new authorization concept for analysis authorization. If you want to use the SAS implementation for those authorization checks, import the appropriate transport (SAPKB92331INSAS). The implementation is activated by default. If you want to deactivate the implementation:

Call transaction SE19 in SAP. In the command field, type transaction code /nse19.
In the Edit Implementation field, select the New BAdI check box.
Enter /SAS/IM_AUTHBI01 as the enhancement implementation.
Click Change.
Double-click the BAdI Implementation to deactivate (such as /SAS/BADI_CHECK_FILTER) and clear the Implementation is active check box in the Runtime Behavior field. Repeat for each of the implementations listed in the left hand side of the Enh.Implementation Elements tab.
Save and activate the changes.