Skip to end of metadata
Go to start of metadata

ICF services can be transported in accordance with the configuration of the Transport Management System. ICF services must always be transported from the same source system, otherwise inconsistencies may occur

To transport ICF services, a workbench request is needed with the below data:

Program ID "R3TR"
Object Type "SICF"
Object name: <ICFSERVICE-ICF_NAME> <ICFSERVICE-PARGUID> - these values can be obtained from the table ICFSERVICE.

ICF services are stored in several different database tables - the object type SICF will pick up the relevant entries from all the affected tables. 

For details, see the below Help article:


Regarding the active/inactive status of the transported services, the expected behavior is:

- If a new ICF service is created in a DEV system and transported to another system e.g. QAS, the service will have inactive status in the target system QAS. It needs to be activated manually or via mass activation in QAS.

- If a service already exists in the QAS system, and it is changed in the DEV system, the transport will not affect the status of this service in the target system (SAP Note 1447439). E.g. if the service in the target system QAS is already active, then it will still be active after the transport.

If necessary, a mass activation can be performed with the report RS_ICF_SERV_MASS_PROCESSING. Beforehand, the list of active services must be exported from the source system, using the report RS_ICF_SERV_ADMIN_TASKS. See the SAP Note 1555208 for details.


To transport external aliases, a different approach is needed. This is described in the below Help article:


Note 1: When transporting ICF services or aliases, logon data is not transported. This applies to the client, user, password, and even the logon language. The logon data need to be maintained manually in the target system. This is the intended system behavior as per the SAP Note 732218.

Note 2: The table ICFSERVLOC contains local, system specific data, such as the load balancing server group, and the Active flag for ICF services. Therefore this table is not included in the transport object SICF. If necessary, the Active flag can be set with mass processing reports, as explained in the SAP Notes 1498575 and 1555208.