SAP Connection

The SAP connection type enables automations to communicate with SAP ERP or S/4HANA systems over RFC (Remote Function Call) or REST, allowing workflows to read master data, post business documents, trigger BAPIs, and call function modules. Credentials and server details are stored once and reused across any number of SAP-enabled workflow steps.

Connection Details

Property	Value
Type ID	SAP
Category	Enterprise Applications
Testable	Yes

Friendly Example

What you enter	Example
Connection name	SAP - Purchase Orders (PRD)
Used for	Reading open purchase orders and posting goods receipts into the ERP
Main details to collect	SAP host, system number, client number, RFC username and password
Best person to provide it	SAP BASIS administrator

After it is saved, workflow builders select SAP - Purchase Orders (PRD) in a node instead of entering server details each time.

Mandatory Fields

Field	What It Means	Example
host	Hostname or IP address of the SAP application server	sap-prd.contoso.com
systemNumber	Two-digit SAP instance number that identifies the application server process (00–99)	00
client	Three-digit SAP client number — equivalent to a logical tenant within the SAP system	100
username	SAP logon name of the RFC or communication-type user	RFC_QINFINITE
password	Password for the SAP user. Encrypted at rest.	S@pP@ss#99

System Number vs Client

These are two different concepts that are often confused. The system number identifies which SAP process is listening on the application server (think: port offset). The client is a logical company code partition inside that SAP system. Both are required.

Advanced Fields

Field	What It Means	Example
language	SAP logon language (ISO two-letter code). Controls language of returned text fields and error messages.	EN
poolCapacity	Number of idle RFC connections kept open in the connection pool for reuse	5
peakLimit	Maximum simultaneous RFC connections allowed at any one time	10
timeoutSeconds	Seconds before an RFC call is abandoned and a timeout error is raised	60

Setup Instructions

1. Get connection details from your SAP BASIS team. You need the application server hostname, the instance/system number (visible in SAP GUI in the bottom-right status bar as <SID>/<instance>), and the client number used by your business unit.

2. Create a dedicated RFC user. In SAP, run transaction SU01 and create a user with User Type: Communication (type B — no interactive logon required). Name it something identifiable, e.g., RFC_QINFINITE. Communication-type users do not expire by default and are preferred over dialog users for integrations.

3. Assign RFC authorization objects. Work with your BASIS team to assign a role or authorization profile that includes S_RFC (RFC access), S_TCODE (for relevant transactions), and any business-object authorizations the automations need (e.g., M_BEST_BSA for purchasing). Start with a restrictive profile and expand as needed.

4. Verify connectivity from the Qinfinite host. SAP RFC uses port 33<systemNumber> by default (e.g., 3300 for system number 00). Confirm that the firewall allows inbound traffic from the Qinfinite server on this port.

5. Save and test. Enter all details in Global Configurator and click Test Connection. A successful test confirms that the JCo RFC handshake completes and the user can log on.

Communication-Type Users Only

Do not use Dialog user accounts (type A) for RFC integrations. Dialog accounts are subject to password expiry and concurrent logon limits, which can cause intermittent failures in production automations.

Troubleshooting

Symptom	Likely Cause	Fix
RFC_ERROR_LOGON_FAILURE	Incorrect username or password, or the user is locked	Unlock the user in SU01 and verify credentials
RFC_ERROR_COMMUNICATION	Network cannot reach port 33<systemNumber> on the SAP host	Ask the network team to open the RFC port; verify the host and system number are correct
NO_AUTHORITY on a specific BAPI or function module	The RFC user lacks the required authorization object	Use SU53 while logged in as the RFC user to see the failed authorization check, then add it to the user's role
Connection pool exhausted under load	peakLimit is set too low for concurrent automation executions	Increase peakLimit and confirm SAP work process availability with the BASIS team