---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up the SAP S4 HANA RFC spoke

# Set up the SAP S4 HANA RFC
spoke {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
Integrate the ServiceNow instance and SAP S4 HANA RFC spoke by
using the Basic Auth credentials to authenticate ServiceNow
requests.

## Before you begin

* Request an Integration Hub subscription.
* Activate the SAP S4 HANA RFC spoke.
* Role required: admin.

{#setup-saphana-rfc__ul_agy1_qfxd_rlb}  
Note:  
To retrieve information for authorization purposes, use the Execute RFC spoke action.

## Procedure

1. Configure MID Server using the SAP proprietary JAR files.
   1. **Optional:** Navigate to System PropertiesSecurity.  
      Note:  
      This is applicable only if your MID Server is installed on a Linux machine
   2. **Optional:** Disable the MIME type validation for file attachments.  
      Note:  
      This is applicable only if your MID Server is installed on a Linux machine.
   3. Navigate to MID ServerJAR Files.
   4. Upload the required SAP proprietary files (JAR, SO, or DLL) obtained after contacting your SAP S4 HANA RFC admin.  
      For more information, see [Synchronize a JAR file to MID Servers](https://www.servicenow.com/docs/access?context=t_SynchronizeAJARFiletoMIDServers&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).

   {#setup-saphana-rfc__substeps_ggr_tv5_f4b}  
   Note:  
   Ensure that the files are synchronized in the \<MID-Server-root-directory\>/agent/extlib directory. If the files aren't synchronized, restart the MID Server.
2. Create a credential record for the SAP S4 HANA RFC account.
   1. Navigate to Connections \& CredentialsCredentials.
   2. Click New.  
      The system displays this message: What type of Credentials would you like to create?
   3. Select Basic Auth Credentials.
   4. On the form, fill these values.  
      {#setup-saphana-rfc__table_q3d_tjd_ymb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name to uniquely identify the record. For example, <kbd class="ph userinput">SAP S4 HANA RFC Cred</kbd>. |
      | User name | User name to log in to your SAP S4 HANA RFC account. |
      | Password | Password to authenticate and log in to your SAP S4 HANA RFC account. |
      | Active | Option to actively use the credential record. |
      | Order | Order to apply this credential. For example, <kbd class="ph userinput">100</kbd>. |
      | Credential alias | Credential alias associated with the spoke. |
      [Table 1. Basic Auth Credentials form]

      {#setup-saphana-rfc__table_q3d_tjd_ymb}
   5. Click Submit.
   {#setup-saphana-rfc__substeps_pqb_3w5_f4b}
3. Create a connection record for your SAP S4 HANA RFC account.
   1. Navigate to Connections \& CredentialsConnections \& Credentials Aliases.
   2. Open the alias record for SAP S4 HANA RFC.
   3. From the Connections tab, click New.
   4. On the form, fill in the fields.  
      {#setup-saphana-rfc__table_vp2_3ld_ymb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name to uniquely identify the record. For example, <kbd class="ph userinput">SAP S4 HANA RFC Connection</kbd>. |
      | Credential | Credential record created for SAP S/4 HANA IDoc spoke. For example, <kbd class="ph userinput">SAP S4 HANA RFC Cred</kbd>. |
      | Connection alias | Alias record associated with this connection. |
      | Host | Fully qualified domain name of the target host where the SAP S4 HANA RFC server is installed. |
      | Active | Option to actively use the connection record. |
      | Domain | Domain that the action runs in. |
      | Override default port | Target port used by the connection. If blank, the system uses the default port. |
      | Use MID server | Option to use a MID Server for this connection. Select the check box and define the fields in the Advanced MID Server Configuration tab. |
      [Table 2. Connection form]

      {#setup-saphana-rfc__table_vp2_3ld_ymb}
   5. In the Advanced MID Server Configuration tab, provide these details.  
      {#setup-saphana-rfc__table_mqc_3yd_ymb__entry__2}

      | Field | Description |
      |-|-|
      | MID Selection | Option to select MID Server as required. This field is available when Define Connection Inline is selected from the Source Connection list. |
      | MID Application | Option to use a MID Server to run the SFTP step. This field is available when Define Connection Inline is selected from the Source Connection list and Auto-Select MID Server is selected from the MID Selection list. To learn more about how a MID Server is selected during runtime, see [MID Server selection](https://www.servicenow.com/docs/access?context=c_MIDServerSelector&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). |
      | Capabilities | Capability of the MID Server. Select SSH. This field is available when Define Connection Inline is selected from the Source Connection list and Auto-Select MID Server is selected from the MID Selection list. Required capabilities determine which MID Server is selected at runtime. To learn more about how a MID Server is selected during runtime, see [MID Server selection](https://www.servicenow.com/docs/access?context=c_MIDServerSelector&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). |
      | MID Server | Data pill of the required MID Server. This field is available when Define Connection Inline is selected from the Source Connection list and Specific MID Server is selected from the MID Selection list. |
      [ ]

      {#setup-saphana-rfc__table_mqc_3yd_ymb}
   6. In the Attributes tab, provide these details.  
      {#setup-saphana-rfc__table_eq2_ccq_xmb__entry__2}

      | Field | Description |
      |-|-|
      | u_client | Client value of the target host where the SAP S4 HANA RFC server is installed. |
      | u_system_number | System number of the target host where the SAP S4 HANA RFC server is installed. |
      | u_lang | Language selected in the target host where the SAP S4 HANA RFC server is installed. |
      [ ]

      {#setup-saphana-rfc__table_eq2_ccq_xmb}
   7. Click Submit.
   {#setup-saphana-rfc__substeps_qrr_4w5_f4b}
4. Create a record in the SAP S/4HANA Flow Executions module to specify date up to which you want to retrieve the invoice data.
   1. Navigate to SAP S/4HANA - RFC SpokeSAP S/4HANA Flow Executions.
   2. Click New.
   3. In Last Successful Execution, specify the date up to which you want to retrieve the invoice data.
   4. Click Submit.  
      The Retrieve Incoming Invoice flow takes this date as an input and retrieves the invoice data. Depending on the configured flow trigger, the Retrieve Incoming Invoice flow periodically retrieves the invoice data. To view the invoice data, navigate to SAP S/4HANA - RFC SpokeSAP S/4HANA Invoice Data.
   {#setup-saphana-rfc__substeps_p4s_1z1_p4b}
{#setup-saphana-rfc__steps_s5b_1s1_p4b}

## Result

The spoke is configured and the actions can be used.  
Note:  
If you want to use multiple connections, ensure that you create them as child alias records under the default connection alias record. Also, you must ensure that all the connection records are active.

*[\>]: and then