Prerequisites when accessing SAP HANA via SAP Application Server

Before SAP HANA can be used as a source endpoint in a replication task, the prerequisites described in this section must be met.

Install the SAP NetWeaver RFC Client

This topic explains how to copy the required SAP NetWeaver RFC Client files to the Qlik Replicate machine.

Windows

Extract the contents of the NWRFC_xxx.SAR file and then copy the .dll files from the nwrfcsdk/lib directory to the Qlik Replicate bin directory.

Linux

Extract the contents of the NWRFC_xxx.SAR file and then copy the .so files from the nwrfcsdk/lib directory to the Replicate lib directory.

Install the Replicate for SAP Client on the SAP machine

This section describes how to install the transports that make up the Replicate for SAP Client (R4SAP).

1. Go to Product Downloads.

2. Select Qlik Data Integration.

3. Scroll down the Product list and select Replicate.

4. In the Download Link column, locate the QlikReplicate_<version-build>_R4HANA.zip file. Before starting the download, check the Version column to make sure the QlikReplicate_<version-build>_R4HANA.zip version you are downloading corresponds to your current Replicate version.

There are seven transports in total, which are provided in the following folders:

• DeleteCode - Required for uninstalling the Replicate for SAP Client.
• DeletePackage - Required for uninstalling the Replicate for SAP Client.
• DeleteCodeCommon - Required for uninstalling the Replicate for SAP Client.
• DeletePackageCommon - Required for uninstalling the Replicate for SAP Client.
• InstallCode (e.g. K902086.ESD) - The main transport.

Permissions required for installing Qlik Replicate for SAP Client

SAP users for Replicate

A dialog user in SAP is required to access the Qlik Replicate for SAP Client GUI in SAP. In addition, a communication user is required to support the RFC calls from the Qlik Replicate software to the SAP system.

Identify existing users in SAP or create dedicated users for the Qlik Replicate software.

Authorizations for Replicate

Both the dialog and communication users will need to be assigned to a role with authorization object S_TCODE and value /QTQVC/REPLICATE.

The communication user will also require the following authorization objects: S_RFC, S_OC_SEND,S_BTCH_JOB, /QTQVC/RFC, and /QTQVC/CAL:

Importing the Qlik Replicate transports into the SAP system

There are two types of files required to import the ABAP objects into the SAP system: the data-file and the co-file.

Importing the data-file

The data-file begins with an "R"

The data-file should be placed in the /usr/sap/trans/data file system or in the directory of the server where the transports are stored.

• Typically this is a shared directory, but if not, individually place the file into that directory location for all SAP host servers.
• This file must be accessible by all systems where the Qlik Replicate for SAP Client is to be installed.
• Set the permissions on the file to All for the user, Read and Execute for the group, and Read and Execute for others.
• The owner of the file should be the <sid>adm user of the system to be installed. The group ownership should be sapsys.

Importing the co-file

The co-file begins with a "K"

The co-file should be placed in the /usr/sap/trans/cofiles file system or in the directory of the server where the transports are stored.

• Typically this is a shared directory, but if not, individually place the file into that directory location for all SAP host servers.
• This file must be accessible by all systems where the Qlik Replicate for SAP Client is to be installed.
• Set the permissions on the file to All for the user, Read and Execute for the group, and Read and Execute for others.
• The owner of the file should be the <sid>adm user of the system to be installed. The group ownership should be sapsys.

Once the files are in the correct location, import the transport into the system using either the Operating System level transport tools (TP), or the Transport Management System (TMS) internally within SAP.

Importing the transports via TP

1. Log on to the system at the Operating System level as the <sid> adm.
2. Change the directory to /usr/sap/trans

3. Add the transport to the R/3 buffer with the following command:

   # tp ‘addtobuffer SID’

4. Import the transport to the target R/3 system with the following command:

   # tp ‘import SID client=000 U16’

The expected result of the addtobuffer step is a successful return code of `0’.

If problems occur during the addtobuffer step, it is likely there is a problem with the files. They may be missing, in the wrong location, or have incorrect ownership or permissions.

The expected result of the import step is a successful return code of either `0’ or `4’. A return code of `8’, `12’ or `16’ indicates transport failure. Return codes higher than `16’ indicate a major failure within the transport tool. If this occurs, check the present working directory to ensure the correct location. Also, check the files for existence, location, and proper ownership and access.

If problems exist during the import, retry the import step. If problems persist, check the import and activation logs for failure reason. These files are in the /usr/sap/trans/log location and named.R6U (the `?’ stands in as a wildcard).

Importing the transports via TMS

Beginning in R/3 version 4.0, SAP allows importing transports through the SAP system via transaction code STMS.

1. Sign-on to SAP system with a User ID that contains proper authority.
2. Execute transaction STMS.
3. Select the Transport (Truck) icon from the toolbar.
4. Select the desired system for import.

5. Add the Transport to the import queue by selecting the following path from the menu list:

   Extras > Other Requests > Add

   Add the transport request number to the proper import queue and execute. Re-authentication of the user.s SAP User ID is likely in order to complete the step.

   If an Information message is received that the "Transport request is invalid" check that the transport number was typed correctly. Otherwise, it may indicate a problem with the files. Verification of existence, location, permissions, or ownership may be needed.

6. Import the Transport request by selecting the transport number from the queue, and clicking the Import (Truck) icon from the toolbar. Set the target client to either `000’ or any other valid client within the system and execute with the truck icon. Once again, re-authentication of the SAP User ID may be necessary. The transport will execute in asynchronous mode; a record of success or failure can be found in the transport logs.

7. The system will return to the import queue screen, where the Transport results can be checked. Select the Logs icon from the toolbar, or follow the menu path:

   Request > Display > Logs

   Locate the source system and verify all relevant logs. For this transport there should be 5 logs:

   • DD Import
   • DD Activation
   • Import
   • Check Versions
   • ABAP/scrn. Generation

   All logs should display Ended OK (return code 0) or Ended with warning (return code 4). If any logs are missing, or display a return code of 8 or higher, follow the instructions in step 6 to re-import the transport.

Upgrading/patching and uninstalling the Qlik Replicate SAP Client

The following instructions explain how to upgrade/patch, and uninstall the Qlik Replicate SAP Client.

To upgrade or patch the Qlik Replicate SAP Client on ECC Systems

1. Apply the new main transport (InstallCode.zip).
2. Apply the new ECC-specific transport (InstallCodeECC.zip).

To upgrade or patch the Qlik Replicate SAP Client on non-ECC systems

• Apply the new main transport (InstallCode.zip).

To uninstall the Qlik Replicate SAP Client

1. Apply the "Delete Main" transport (DeleteCode.zip).

2. Apply the "Delete Package" transport (DeletePackage.zip).

   Information note

   Do not apply items 3 and 4 if you are also running Qlik Gold Client Solution.

3. Apply the “Delete Common” transport (DeleteCodeCommon.zip)
4. Apply the “Delete Common Package” transport (DeletePackageCommon.zip)

Managing business groups and tables

This prerequisite is only necessary if you want to edit the default Business Groups and/or tables before replicating them.

Before you can manage business groups and tables, you first need to launch the SAP Client UI.

To launch the SAP Client UI:

1. Open your SAP client console.

2. Double-click one of the SAP Application Sources.

   You will be prompted for your user name and password.

3. Enter your credentials for logging in to the selected SAP Application Source.
4. Enter /QTQVC/REPLICATE in the drop-down list at the top of the console and then press [Enter].

5. Click the Business Groups Configuration button.

   A list of Business Groups is displayed in the left pane.

Managing business groups

To add a new Business Group:

1. Right-click the Business Groups folder and select Create.

   The Create Business Group dialog box opens.

2. Enter a name for your Business Group and then press [Enter].

   The new Business Group is added to the Business Groups list in the left pane.

To duplicate a Business Group

1. Right-click the group you want to duplicate and select Copy.

   The Business Group Configuration dialog box opens.

2. In the New Bus Object field, enter a name for the new Business Group and then press [Enter].

   The duplicated Business Group is added to the Business Groups list in the left pane.

To delete a Business Group

• Right-click the Business Group you want to delete and select Delete.

  The Business Group is deleted.

Managing tables

To add a new table to a Business Group:

1. Double-click the desired Business Group.

   A list of tables is shown in the right pane.

2. Click the button on the menu tab in the tables pane.

   An empty row is added to the tables list.

3. Enter the Table Name (i.e. the virtual ABAP table) and the name of the corresponding Source Table (i.e. the physical table).
4. To save your changes click the Save button in the main toolbar.

To remove a table from a Business Group:

1. Select the row with the table and Click the button above the table list.

   The table is deleted.

2. Click the Save button in the main toolbar to save your changes.

Copying Business Groups and Tables from Transaction ZR4SAP

If business groups and tables are already defined in transaction ZR4SAP for the SAP Application (DB) or SAP Application source endpoints, the report /QTQVC/REPLICATE_MIGRATE_CFG can be used to migrate them to /QTQVC/REPLICATE.

To do this:

1. To copy all business groups, leave the Business Group field blank.
2. To overwrite existing settings in /QTQVC/REPLICATE with those from ZR4SAP, select the Overwrite Configuration check box.

Target collation

As SAP is case-sensitive, when a replication task is defined with a SAP Application source, the target database needs to be set up with case-sensitive collation.