Prepare for SAP BW integration

Your SAP team sets up three things before Dawiso can scan SAP BW / BW4HANA: a technical user, display authorizations, and the SAP RFC libraries the runtime needs.

Dawiso reads SAP BW metadata over RFC (SAP’s native remote-call protocol) using two standard SAP function modules — RFC_PING and RFC_READ_TABLE. Nothing is installed in your SAP system: no transport, no custom ABAP, no add-on, and no write access of any kind.

Connection prerequisites

• SAP BW 7.x or BW/4HANA reachable over RFC from the machine that runs the Dawiso Integration Runtime
• A technical SAP user of type System or Communications Data (see Create the technical user)
• Display authorization for the BW metadata tables (see Grant authorizations)
• The SAP NetWeaver RFC SDK libraries placed in the runtime folder (see the next section) — these are licensed by SAP and must be downloaded by you
• Network access to the SAP application server on port 33<SYSNR>
• Direct application server logon must be permitted. Dawiso connects to a named application server (host + system number). Logon-group balancing through the SAP message server is not currently supported — see Landscapes that need load balancing below.

Install the SAP NetWeaver RFC SDK libraries

Dawiso calls the SAP RFC protocol through SAP’s own C library. SAP licenses these files and does not permit redistribution, so they are not included with Dawiso. You download them under your own SAP S-user and place them in the runtime.

1. Download the SDK

1. Go to https://support.sap.com/en/product/connectors/nwrfcsdk.html and sign in with an S-user.
2. Open the download area for SAP NW RFC SDK 7.50.
3. Choose the package matching the operating system of the machine running the Dawiso Integration Runtime — not the operating system of your SAP server:

• Windows on x86_64
• Linux on x86_64

4. Download the latest patch level and extract the archive.

2. Copy the libraries into the runtime

Place the files in the providers/sap-bw/ folder of your Dawiso Integration Runtime installation. Copy them from the lib folder of the extracted SDK.

Windows

<runtime folder>/providers/sap-bw/
    sapnwrfc.dll
    icuin57.dll
    icuuc57.dll
    icudt57.dll
    libsapucum.dll

Linux

<runtime folder>/providers/sap-bw/
    libsapnwrfc.so
    libicui18n.so.*
    libicuuc.so.*
    libicudata.so.*
    libsapucum.so

The icu* file names contain a version number that depends on the patch level you downloaded — copy whatever names are present in the SDK’s lib folder.

3. Install the C++ runtime (Windows only)

On Windows the SAP library requires the Microsoft Visual C++ Redistributable 2015–2022 (x64): https://aka.ms/vs/17/release/vc_redist.x64.exe

Without it the library cannot load and the scan fails with Unable to load DLL 'sapnwrfc' or a missing MSVCP140.dll.

Get your connection details

Ask your SAP Basis team for the following. These are the same details used for any RFC connection and appear in every SAP GUI logon entry.

Detail	Example	Notes
Application server host	bwprod01.example.com	hostname or IP
System number (SYSNR)	01	two digits — determines the network port
Client (mandant)	800
Logon language	EN	Dawiso reads all available languages and picks the best per object

Landscapes that need load balancing

Dawiso logs on to a specific application server, identified by host name and system number.

Load-balanced logon through the SAP message server is not currently supported. Some standards require connecting via a logon group — message server host, service and group, rather than a single application server. Raise this with Dawiso before starting the integration. As a workaround, ask your Basis team to nominate one application server that the runtime may connect to directly.

Create the technical user

Use a dedicated technical user rather than a personal account. A personal (Dialog) account consumes a named-user license and ties the integration to an individual who may leave. It is also subject to a password-expiry policy that silently stops the scan.

1. In SAP, create a new user in the BW client to be catalogued.
2. Set the user type to System (recommended for scheduled scanning) or Communications Data. Both permit RFC and prevent interactive logon.
3. Exempt the password from expiry, or plan to rotate it in your secret store — an expired password stops the scan.
4. Assign the authorizations below.

Grant authorizations

The user needs display-only rights. Two authorization objects are required.

S_RFC — permission to call the function modules

Field	Value
RFC_TYPE	FUGR (function group), and/or FUNC
RFC_NAME	the function group containing RFC_READ_TABLE, plus RFC_PING
ACTVT	16 (Execute)

S_TABU_NAM — display access to the metadata tables

Field	Value
ACTVT	03 (Display)
TABLE	the tables listed below

S_TABU_NAM is preferred because it can be limited to an explicit list. If your standard is authorization-group based, S_TABU_DIS with ACTVT 03 for the groups covering the RS* tables also works, but grants broader access than Dawiso needs.

Tables read (display only):

RSDAREA  RSDAREAT  RSOADSO  RSOADSOFIELDMAP  RSOHCPR  RSOOBJXREF
RSDCUBE  RSDCUBET  RSDCUBEIOBJ  RSDIOBJ  RSDIOBJT  RSDCHABAS  RSDKYF
RSDS  RSDST  RSKSNEW  RSKSNEWT  RSTRAN  RSTRANT  RSTRANFIELD
RSBKDTP  RSBKDTPT  RSRREPDIR
RSZCOMPDIR  RSZELTDIR  RSZELTTXT  RSZELTPROP  RSZELTXREF  RSZRANGE
RSPCCHAIN  RSPCCHAINT  RSPCCHAINATTR  RSPCTRIGGER
RSBOHDEST  RSBOHDESTT  RSFBP  RSFBPT
RSDDSTAT_OLAP

On classic SAP BW 7.x only, three further tables hold the DataStore Objects that BW/4HANA replaces with ADSOs. Grant these as well if the system being catalogued is classic BW; they do not exist on BW/4HANA:

RSDODSO  RSDODSOT  RSDODSOIOBJ

What Dawiso does not need

State these explicitly when requesting access — they are often the sticking points in a security review:

• No transport, custom ABAP or add-on — nothing is installed in your SAP system
• No S_DEVELOP — Dawiso does not read ABAP source code
• No write access — display activities only
• No SAP GUI, SE16 or SE38 access — RFC only
• No database-level (HANA) access — Dawiso talks to the ABAP layer
• No business data — only the metadata repository: object names, structures and relationships

Network requirements

Direction	outbound, from the machine running the Dawiso Integration Runtime to the SAP application server
Port	33<SYSNR> — for example 3301 for system number 01
Cloud upload	outbound HTTPS (443) to your Dawiso ingestion endpoint
Encryption	plain RFC

Usage statistics and personal data

Dawiso can report how often each BEx query is run, by how many distinct people, when it was last used and its average runtime. This comes from SAP’s own OLAP statistics table.

That table records the SAP user ID of each person who ran a report. Dawiso stores only an aggregated count of distinct users — individual user IDs are never written to the catalogue. If your works council agreement or data protection policy requires it, usage statistics can be excluded entirely.

Verify the connection

When the scan runs it first performs a connection test — an RFC_PING followed by a trial read of the RSDAREA table — so authorization problems surface immediately rather than part-way through.

Message	Meaning
Unable to load DLL 'sapnwrfc' / missing MSVCP140.dll	SDK libraries missing from providers/sap-bw/, or the C++ Redistributable is not installed
RFC_COMMUNICATION_FAILURE	wrong host or system number, or the port is blocked by a firewall
RFC_LOGON_FAILURE	wrong user, password or client
An error immediately after logon, when reading RSDAREA	the user is missing table display authorization

Next steps

• Create SAP BW connection
• Create SAP BW data source