SAP SQL Connector user configuration
Create one or more SAP users that will be used for back-end jobs from Qlik and administrative tasks in SAP. These users are not intended for Qlik end-users so only a few SAP users should be created. Creating several users provides traceability, and you can give the users different authorizations.
Authorizations are required to use the SQL Connector. Qlik provides two roles that contain the necessary authorizations. You can assign different roles to different users, depending on need, or both roles can be assigned to one user.
The QTQVCADMIN role is required for users who perform Qlik transactions in the SAP GUI.
The QTQVCACCESS role is used by a connector back-end user who performs extraction jobs from Qlik.
Configuring users
After the transports have been installed in the system, create one or more users as needed. You can also assign the roles to existing users.
Do the following:
- In the SAP system, go to transaction SU01.
- Click Create (F8).
- Give the new user a user a name and a password.
- For an existing user, enter the User ID and click Change (Shift + F6).
- On the Logon data tab, assign new users to User Type: Service.
- On the Roles tab, add the desired roles.
- Click Save.
If the installation is an upgrade from a previous version and the role QTQVCACCESS has been updated, update all users assigned to the role:
-
Go to transaction PFCG.
-
Enter the role name QTQVCACCESS and click Change Role.
-
On the User tab, enter the name of the user(s) created above.
-
Click User comparison.
-
Click Complete comparison.
- Click Save.
Testing SQL statements
The /n/QTQVC/SQL transaction allows testing of SQL SELECT statements. After installing the transports and creating a user, test that everything has been correctly installed.
Do the following:
-
Log on with the newly created user and test transaction /n/QTQVC/SQL.
- Enter the SQL statement.
- Click Open Stream to start the job.
-
Click Fetch Stream to display one page of the result. Click Close Stream to end the job.
or:
-
Click all Data to execute the complete job and get the run-time statistics.
Then either: