Symptom
One or more of the following may be observed for SAP Signavio Process Intelligence SAP RFC–type connections when the on‑premises extractor (OPE) is running as a service:
- Extra Connection Arguments (ECAs) are configured but not reflected during extraction.
- During debugging of RFC_READ_TABLE, expected flags (e.g. USE_ET_DATA_4_RETURN, GET_SORTED) are not set.
- Extraction behavior remains unchanged after implementing relevant SAP Notes in the SAP source system.
Cause
- The on‑premises extractor is running as a service.
When running as a service, the extractor:- Loads configuration and runtime context only at service start‑up.
- Does not automatically reload changes to ECAs or SAP system behavior introduced by newly applied SAP Notes.
- SAP Notes are correctly implemented on the SAP source system.
- Extra Connection Arguments are correctly configured in SAP Signavio Process Intelligence for SAP RFC connections.
- As a result, previously loaded settings remain active until the service is restarted.
Resolution
As a best practice, restart the on‑premises extractor service whenever:
- Extra Connection Arguments are added or modified for SAP RFC connections, or
- SAP Notes relevant to RFC extraction behavior are implemented or updated in the SAP source system.
Keywords
sap signavio, process intelligence, sap rfc, on‑premises extractor, ope, service, extra connection arguments, eca, sap notes, rfc_read_table, use_et_data_4_return, get_sorted, best practice, soe
, KBA , BPI-SIG-PI-DI , Data Import for SAP Signavio Process Intelligence , Problem
Product
SAP Signavio Process Intelligence all versions
SAP Knowledge Base Article - Public