/
How To Run the INI Process in SAP RISE Without Client 000

How To Run the INI Process in SAP RISE Without Client 000

In SAP RISE environments where client 000 is not available, the classic INI process via transaction /RTC/TM_INI cannot be used due to missing access rights.
To address this, a new transaction /RTC/TM_INI_COM was introduced with SmartChange Release 5.6.3.0 (SP6 HF3).

Option 1: Automatic Initialization Using /RTC/TM_INI_COM (Recommended)

Purpose

The new transaction /RTC/TM_INI_COM enables full system initialization (creation of RFCs, user assignments, etc.) directly in a working client, such as client 100.
It replicates the behavior of /RTC/TM_INI from client 000.

Prerequisites

  • SmartChange Release: ≥ 5.6.3.0 (SP6 HF3)

  • Imported Transport: The latest communication roles must be imported into each system's working client

  • Required Roles: /RTC/TM_RFC* (recommended: /RTC/TM_RFC_HIGH)

  • Created User: ZRTC4_TM_ADM will be automatically created and used during the process

Execution

  1. Log into your working client (e.g., 100)

  2. Execute transaction /RTC/TM_INI_COM

  3. Follow the guided steps to complete the initialization

Option 2: Manual Initialization for Older Versions (< 5.6.3.0)

If your SmartChange version does not yet support /RTC/TM_INI_COM, you can manually configure the RFC setup in the working client as follows:

Step 1: Create the Communication User

In all relevant systems (TM Server + connected systems), create the following user in a working client using SU01:

  • User: ZRTC4_TM_ADM

  • Type: Service

  • Role: /RTC/TM_RFC_HIGH

  • Remember Password! Recommendation: Use identical password in all systems

Step 2: Create RFC Connections

In each target system (not the TM Server), create an RFC destination via transaction SM59:

  • Type: ABAP Connection (Type 3)

  • Name: ZRTC4_TM_[SID of TM Server]
    (Example: ZRTC4_TM_ES1)

  • Target: Host or IP of TM Server

  • User: ZRTC4_TM_ADM

Step 3: Register the Systems in TM Server

In the TM Server, go to System and Groups and use the wizard to connect the systems:

  • Enter the working client instead of client 000 in the Connection Data and previously created User ZRTC4_TM_ADM

Step 4: Enable positive list (only needed if RFC callback parameter = “SECURE”)

In the TM Server system, go to SE38 and execute report /RTC/SC_WHITELIST to add positive list entries to all ZRTC4* RCF connections and enable the positive list.