> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/setup-and-configuration/command-line-interface/create-test-and-list-rfc-destinations.md).

# 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.

{% hint style="warning" %}
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.
{% endhint %}

## Create RFC Destinations

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

### `slabapcli rfc set`

{% hint style="warning" %}
**Prerequisite:** Run `slabapcli sealights set` before running `rfc set`. The automatic verification step requires a valid SeaLights token.
{% endhint %}

Creates or updates an RFC Destination for an SAP system. The username and password are entered interactively and stored encrypted. After saving, the command automatically runs `rfc test` to verify the connection.

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

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

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

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

{% endcode %}
{% endtab %}
{% endtabs %}

| Parameter    | Short flag | Required | Description                          |
| ------------ | ---------- | -------- | ------------------------------------ |
| `--name`     | `-n`       | Yes      | RFC Destination name (e.g. `S21`).   |
| `--hostname` | —          | Yes      | SAP system hostname.                 |
| `--sysnr`    | `-s`       | Yes      | SAP system number (instance number). |
| `--client`   | —          | Yes      | SAP client number.                   |
| `--lang`     | —          | Yes      | SAP login language (e.g. `EN`).      |

{% hint style="info" %}
If an RFC Destination with the same name already exists, `rfc set` updates it: the connection details and the credentials are replaced, while optional settings such as the router string, the retry settings, and the cached usage data are kept.
{% endhint %}

#### Example

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe rfc set --name "S21" --hostname "sapqas01.customer.com" --sysnr "00" --client "100" --lang "EN"
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe rfc set --name 'S21' --hostname 'sapqas01.customer.com' --sysnr '00' --client '100' --lang 'EN'
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell, abbreviated)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe rfc set --name 'S21' --hostname 'sapqas01.customer.com' --sysnr '00' --client '100' --lang 'EN'
[2026-05-07 11:37:08.571+01:00] [info] Detected Windows version: Windows 11
[2026-05-07 11:37:08.572+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Enter username: hunterh
Enter password: **********
Confirm password: **********
Password accepted (sha1 a3f9c2d1).
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:
    ...
  Authorizations:
    All required authorizations present
  Required tables in DDIC:
    All required tables present in DDIC
  SCMON Configuration:
    ...
    SCMON is running and configured to stay active until 2027-12-31
  SCMON_COLLECT callability:
    SCMON_COLLECT call succeeded
```

{% endcode %}

{% hint style="info" %}
The password and confirmation are not displayed in the terminal window for security. The command automatically runs `rfc test` after saving the RFC Destination.
{% endhint %}

## Test RFC Destinations

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

### `slabapcli rfc test`

Tests the connection to an RFC Destination and runs a comprehensive set of diagnostic checks. Verifies connectivity, SAP system information, SeaLights add-on installation and version, time synchronization, the SAP authorizations the agent requires, that the required tables exist in the ABAP Dictionary (DDIC), SCMON configuration, and SCMON\_COLLECT callability.

{% hint style="warning" %}
**Prerequisite:** `rfc test` also needs a valid SeaLights token, because the time synchronization check contacts SeaLights. Run `slabapcli sealights set` first.
{% endhint %}

The same checks run against every RFC Destination, including your Production system.

{% hint style="info" %}
**Production RFC Destinations:** If the SeaLights add-on is not used on Production (`useaddon = false`, the default), the add-on and SCMON checks fail on the Production RFC Destination. The failures are shown in red and the command exits with code `1`. This is expected, and you can ignore those failures for the Production RFC Destination in that case. See [Production usage data source](broken://pages/DZM4uWEu5r51kMDWCmDB#production-usage-data-source).
{% endhint %}

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe rfc test --name <rfc>
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

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

{% endcode %}
{% endtab %}
{% endtabs %}

| Parameter | Short flag | Required | Description                       |
| --------- | ---------- | -------- | --------------------------------- |
| `--name`  | `-n`       | Yes      | The RFC Destination name to test. |

#### Example

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe rfc test --name "S21"
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

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

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell, abbreviated)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe rfc test --name 'S21'
[2026-05-07 11:45:36.906+01:00] [info] Detected Windows version: Windows 11
[2026-05-07 11:45:36.907+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\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
  Authorizations:
    All required authorizations present
  Required tables in DDIC:
    All required tables present in DDIC
  SCMON Configuration:
    DEACTIVATE_ON: 20271231
    SCMON is running and configured to stay active until 2027-12-31
  SCMON_COLLECT callability:
    SCMON_COLLECT call succeeded
```

{% endcode %}

Passed checks are shown in green. A failed check starts with `Error:` (red). A check that could not be completed starts with `Warning:` (yellow). The command exits with code `0` if all checks pass and `1` if any check fails; a warning can also cause exit code `1` when the check was skipped.

## List RFC Destinations

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

### `slabapcli rfc list`

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

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe rfc list
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

```powershell
.\slabapcli.exe rfc list
```

{% endcode %}
{% endtab %}
{% endtabs %}

This command takes no parameters.

#### Example

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe rfc list
[2026-05-07 13:54:05.665+01:00] [info] Detected Windows version: Windows 11
[2026-05-07 13:54:05.666+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Name        : S21
Hostname    : sapqas01.customer.com
Sysnr       : 00
Client      : 100
Language    : EN
Username    : hunterh
Password    : ****** (Encrypted)
Cached usage: false
Cached PRD RFC:

Name        : S23
Hostname    : sapprd01.customer.com
Sysnr       : 00
Client      : 200
Language    : EN
Username    : hunterh
Password    : ****** (Encrypted)
Cached usage: false
Cached PRD RFC:
```

{% endcode %}

The password is never shown when secret protection is enabled, which is the default. If secret protection is not enabled on the installation, the password is printed in clear text. `Cached usage` and `Cached PRD RFC` show whether usage data was imported for the RFC Destination with `slabapcli rfc phd`, and for which Production system.

{% hint style="info" %}
To remove an RFC Destination, edit `config.toml` directly and delete its `[[rfc]]` entry. Do not remove an RFC Destination that is referenced by an existing Pipeline.
{% endhint %}