Skip to main content

Celonis Product Documentation

Installing RFC Module

Celonis RFC Module is responsible for extracting data from the SAP database. It gets the job metadata from the Extractor, i.e. which table, which columns, filters, etc, and then generates a background job in SAP. The job extracts the data and writes it in CSV files in a directory that is monitored by the Extractor.

The minimum requirements for a successful installation of the extractor component in the SAP system are:

  • Minimum Version: SAP ECC 6 and Netweaver 7.0

    • For SAP ECC 4.6C and 5.0 we provide separate transports respectively

  • Development rights on the SAP system to install the modules (not required for the execution of an extraction)

  • 100 GB of free disk space on the SAP system server hard drive or a network drive at the location used for installation step B for the temporary data folder

  • The system user running the SAP system needs to have access (reading and writing) rights to the temporary data folder


The minimum required disk space is only used for the temporary storage of the data chunks which are removed after a successful transfer. The size of the compressed chunks varies from table to table, but their size is likely below 1 GB per chunk.

  1. Check the folder where transports are placed with the transaction AL11 and look under DIR_TRANS; the default is /usr/sap/trans/ on Linux

  2. Unzip the provided ZIP file and copy the cofile (K...) into DIR_TRANS/cofiles and the data file (R...) into DIR_TRANS/data

  3. Run the transaction STMS in your SAP system

  4. Click on import overview (F5)

  5. Double-click on the import queue of the target system

  6. Click on Extras → Other Requests → Add

  7. Specify the name of the transport which is AI1K... (where "..." should be replaced by the number that is contained in the file names of the two transport files)

  8. Click on import

  9. Check the Troubleshooting Appendix at the bottom of this page in case you get an error during the import



Make sure to include the placeholder <FILENAME> at the end of the directory.

  1. Create a dedicated directory on the file system of your SAP (preferably a network drive) and make sure that the user running the SAP system has read and write access to it


    In case you are using Logon Groups, or there are multiple application servers where the extraction jobs can run, make sure that the directory is on a network drive, and is accessible from all the servers.

  2. Run the transaction FILE in your SAP system

  3. Find the Logical Path Z_CELONIS_TARGET in the list

  4. Edit the entry by clicking on the button to the left of the new entry and then double-click on the folder "assignment logical and physical paths"

  5. Set a path for UNIX and/or Windows (shown in the screenshot on the left); the path should be the directory on the system or a network drive that you created in step 1.

TIP: Make sure to INCLUDE the placeholder <FILENAME> at the end of the directory

Add a technical service user for the RFC connection.

Afterward follow these steps to apply the correct roles to the user:

  1. Run the transaction PFCG

  2. Go to Role → Upload

  3. Select the provided role file (CELONIS_EXTRACTION.SAP).

  4. Apply the uploaded role CELONIS_EXTRACTION to the RFC user

If you wish to set up the user yourself, make sure that the user has the following permissions:

  • Permission to write on the server hard disk under the path specified in step B

  • Permission to execute all RFC modules contained in the transport imported in step A (package name /CELONIS/DATA_EXTRACTION )

  • Read access to all tables that should be extracted

After the installation of the extractor component in the SAP system, the following information is needed to continue with the setup:

  • Username and password of the created user for the RFC connection

  • Host name or IP of the SAP server system that is used for the RFC connection from the extractor server

  • System number

  • Client

  • Maximum number of parallel table extractions to be done by the extractor

TMS import queue warning message: "Does not match component version" or "Checking components of the requests"


When importing the RFC Module into your SAP system you may get the error message below.


With Version SAP_BASIS 702 a new feature was added to the TMS system to check the component version of the transport which was released and the component version of the system where the transport was going to be imported. If there is a difference, this difference is highlighted in the import queue (transaction stms_import) and if you try to import the transport, the import will stop with a warning message about the difference in the SAPCOMPONENT versions.


Ideally, the source system and target system should match in relation to component versions, but this is not possible for the RFC Module, because Celonis has only 1 development system, while our customers have a multitude.

You can bypass the warning with the import option "Ignore invalid component version". You will see this option in the options tab upon import.