SAP RFC/BAPI

Call SAP function modules and BAPIs, run them as one unit of work, and read table data

Signs in with: Connection details
Runs on: Cloud or On-Prem Worker
Operations: 11
Ready-made triggers: 0

Connect SAP RFC/BAPI

In Neblex open Connect › Connections and click New Connection.
Search for SAP RFC/BAPI and give the connection a clear name.
Fill in the fields. Secret values are encrypted and never shown again.
Click Test, then Create Connection.

If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.

Field	What to enter
ProtocolRequired	RFC uses the SAP NW RFC SDK installed on an On-Prem Worker and offers every operation. HTTP uses the system's SOAP RFC and IDoc services over HTTPS and also runs in the Cloud.
Application serverOptional	Host name or address of the application server. Leave empty to log on through a message server.Example: `s4app01.example.internal`
System numberOptional	The two-digit instance number of the application server.Example: `00`
Message serverOptional	Host of the message server, for load-balanced logon through a logon group.
Message server serviceOptional	Port or service name of the message server, when it is not sapms followed by the system ID.
System IDOptional	The three-character system ID, for logon through a message server.
Logon groupOptional	The logon group the message server balances over, for example PUBLIC.
SAP router stringOptional	The route through one or more SAP routers, for example /H/router.example.com/S/3299/H/.
System addressOptional	The HTTPS address of the SAP system, without a path.Example: `https://s4.example.com:44300`
ClientRequired	The three-digit SAP client to log on to.Example: `100`
UserOptional	The SAP user. Leave empty when SNC or a client certificate signs the user on.
PasswordOptionalSecret
LanguageOptional	The logon language, as a two-letter ISO code.Example: `EN`
SNC partner nameOptional	The SNC name of the SAP system, for example p:CN=S4H. Setting it turns on Secure Network Communications.
SNC protection levelOptional	1 authentication, 2 integrity, 3 privacy, 8 the system's default, 9 the maximum.
SNC own nameOptional	The SNC name of this client, when it is not the default of the security library.
SNC libraryOptional	Full path of the SNC security library on the host that runs the step, for example the SAP Cryptographic Library.
Gateway hostOptional	To receive calls and IDocs from SAP: the host of the SAP gateway this connection registers at.
Gateway serviceOptional	The gateway service or port, sapgw followed by the system number.Example: `sapgw00`
Program IDOptional	The program ID of the registered server program, as entered in the TCP/IP RFC destination (transaction SM59).
Client certificateOptional	PEM certificate for logon with an X.509 client certificate.
Client certificate keyOptionalSecret	PEM private key of the client certificate.
Trusted server certificateOptional	PEM certificate authority of the SAP system, when it is not publicly trusted.

Use it in a flow

Open a flow, open the node library and search for SAP RFC/BAPI.
Drag it onto the canvas and choose an Operation and your connection.
Map the operation's fields from earlier steps, or click Map with Matt.
Use Test this step to see what it returns, then save.

To start a flow from SAP RFC/BAPI without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if SAP RFC/BAPI can send webhooks, a Webhook trigger receives them at its own URL.

Operations

11 operations in 6 groups. Each one is a step you can add to a flow.

Connection1

Test the connectionping Log on to the SAP system and return its system ID, client, release and code page.

Function2

Call a function module or BAPI`callFunction`		Call a remote-enabled function module once per record and return its exporting, changing and tables parameters.
Run BAPIs as one unit of work`callBapiTransaction`		Call several BAPIs in one SAP session and commit them together with BAPI TRANSACTION COMMIT, or roll all of them back when one fails or reports an error.

Metadata3

Describe a function module`describeFunction`		Return every parameter of a function module with its direction, type, length and fields, and its exceptions.
Describe a structure or table type`describeType`		Return the fields of a dictionary structure or table type.
Search function modules`searchFunctions`		Search the system's function modules by name and function group.

Server1

Receive calls from SAPreceiveCalls Register at the SAP gateway as a server program and receive the calls SAP makes to it (tRFC, qRFC, bgRFC and synchronous).

Table1

Read table rowsreadTable Read rows of a table or view, filtered by a selection, in pages.

Transactional RFC3

Get bgRFC unit state`getBackgroundUnitState`		Return whether SAP has the background unit in process, committed, rolled back or confirmed.
Send as bgRFC unit`sendBackgroundUnit`		Send calls as one background RFC unit: processed at once without queues, or through the named bgRFC inbound queues.
Send as tRFC or qRFC`sendTransactional`		Send calls as one transactional unit that SAP runs exactly once, in order (tRFC), or in an inbound queue (qRFC).