Create, Test & List RFC Destinations

Verify SAP Time Zone Configuration

Make sure the SAP system and the operating system use the same time zone. If they don't match, the Agent won't be able to collect accurate time data.

Recommended Practice

In SAPGUI, use transaction SE16 to display table TTZCU and confirm that field TZONESYS contains the same time zone as the OS time zone. If not, then use transaction STZAC to correct the system time zone.

The time zone must also match for the specific SAP user used to establish the RFC connection. Even if the system time zone is correct, a mismatch in the user's individual time zone setting will cause time data collection errors. To verify or update the user's time zone, use transaction SU01 and check the Logon Data tab.

Create RFC Destinations

The next step is to create RFC Destinations for your QAS and Production systems.

Prerequisite: Run slabapcli sealights set before running rfc set. The automatic verification step requires a valid SeaLights token.

Creates or updates an RFC Destination for an SAP system. The username and password are entered interactively and stored encrypted.

Command Prompt

Syntax

slabapcli.exe rfc set --name <rfc> --hostname <hostname> --sysnr <sysnr> --client <client> --lang <language>

PowerShell

Syntax

.\slabapcli.exe rfc set --name <rfc> --hostname <hostname> --sysnr <sysnr> --client <client> --lang <language>

Parameter	Required	Description
--name	Yes	RFC Destination name (e.g. S21).
--hostname	Yes	SAP system hostname.
--sysnr	Yes	SAP system number (instance number).
--client	Yes	SAP client number.
--lang	Yes	SAP login language (e.g. EN).

Example

Command Prompt

Command

slabapcli.exe rfc set --name "S21" --hostname "vwsvtstsap13.tricentis.com" --sysnr "00" --client "100" --lang "EN"

PowerShell

Command

.\slabapcli.exe rfc set --name 'S21' --hostname 'vwsvtstsap13.tricentis.com' --sysnr '00' --client '100' --lang 'EN'

Expected output (PowerShell, abbreviated)

.\slabapcli.exe rfc set --name 'S21' --hostname 'vwsvtstsap13.tricentis.com' --sysnr '00' --client '100' --lang 'EN'
[2026-05-07 11:37:08.572+01:00] [info] Config pathname: ..\config\config.toml
Enter username: hunterh
Enter password:
Confirm password:
Password accepted (a3f***...***d2b).
Running 'rfc test --name S21' to verify the new RFC destination...
[2026-05-07 11:37:15.910+01:00] [info] Testing rfc: S21
  Connected
  System info:
    RFCDBHOST: sapqas01
    RFCSYSID: S21
    RFCIPADDR: 10.0.1.50
    RFCKERNRL: 753
    RFCSAPRL: 750
  SeaLights ABAP add-on:
    Installed
  SeaLights ABAP add-on version:
    Installed version: RELEASE=2025_01 EXTRELEASE=0012 (minimum supported ...)
  Time synchronization:
    ...
  RFC function modules:
    All required RFC function modules callable
  Tables:
    All required tables readable
  SCMON Configuration:
    ...
    SCMON is running and configured to stay active until 2027-12-31
  SCMON_COLLECT callability:
    SCMON_COLLECT call succeeded

The password and confirmation are not displayed in the terminal window for security. The command automatically runs rfc test after saving the RFC Destination.

Test RFC Destinations

To test the connection to an RFC Destination, run the following from your PowerShell window:

Tests the connection to an RFC Destination and runs a comprehensive set of diagnostic checks. Verifies connectivity, SAP system info, SeaLights add-on installation and version, time synchronization, RFC function module and table authorizations, SCMON configuration, and SCMON_COLLECT callability.

Command Prompt

Syntax

slabapcli.exe rfc test --name <rfc>

PowerShell

Syntax

.\slabapcli.exe rfc test --name <rfc>

Parameter	Required	Description
--name	Yes	The RFC Destination name to test.

Example

Command Prompt

Command

slabapcli.exe rfc test --name "S21"

PowerShell

Command

.\slabapcli.exe rfc test --name 'S21'

Expected output (PowerShell, abbreviated)

.\slabapcli.exe rfc test --name 'S21'
[2026-05-07 11:45:36.907+01:00] [info] Config pathname: ..\config\config.toml
[2026-05-07 11:45:36.910+01:00] [info] Testing rfc: S21
  Connected
  System info:
    RFCDBHOST: sapqas01
    RFCSYSID: S21
    RFCIPADDR: 10.0.1.50
    RFCKERNRL: 753
    RFCSAPRL: 750
  SeaLights ABAP add-on:
    Installed
  SeaLights ABAP add-on version:
    Installed version: RELEASE=2025_01 EXTRELEASE=0012 (minimum supported RELEASE=2024_01 EXTRELEASE=0001)
  Time synchronization:
    K_DateTime: 2026-05-07 12:45:38
    L_DateTime: 2026-05-07 12:45:38
    Average delay of RFC connection: 00:00:00.022
    RFC K_Datetime: 2026-05-07 12:45:38. UTC offset: 02:00:00
    RFC UTC datetime: 2026-05-07 10:45:38
    (Local UTC datetime - RFC UTC datetime) difference: 00:00:00.864
    Agent UTC sent to SeaLights : 2026-05-07 10:45:43.906
    SeaLights server UTC        : 2026-05-07 10:45:44.301
    SeaLights - agent offset    : 00:00:00.395
  RFC function modules:
    All required RFC function modules callable
  Tables:
    All required tables readable
  SCMON Configuration:
    DEACTIVATE_ON: 20271231
    SCMON is running and configured to stay active until 2027-12-31
  SCMON_COLLECT callability:
    SCMON_COLLECT call succeeded

The command-line interface returns details for the RFC Destination.

List RFC Destinations

To list the RFC Destinations defined in your config.toml file, run the following from your PowerShell window:

Lists all RFC Destinations defined in your config.toml file.

Command Prompt

Syntax

slabapcli.exe rfc list

PowerShell

Syntax

.\slabapcli.exe rfc list

This command takes no parameters.

Example

Expected output (PowerShell)

.\slabapcli.exe rfc list
[2025-06-17 13:54:05.666+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[2025-06-17 13:54:05.666+01:00] [info] Config pathname: ../config/config.toml
Name        : S21
Hostname    : vwsvtstsap13.tricentis.com
Sysnr       : 00
Client      : 100
Language    : EN
Username    : hunterh
Cached usage: false

Name        : S23
Hostname    : vwsvdevsap01.tricentis.com
Sysnr       : 00
Client      : 200
Language    : EN
Username    : hunterh
Cached usage: false