--- 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 --- # SAP ECC IDoc Spoke # SAP ECC IDoc Spoke {#sap-ecc-idoc-spoke__sap-ecc-idoc} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of SAP ECC IDoc Spoke The SAP ECC IDoc spoke, developed by Bristlecone, Inc., enables ServiceNow customers to manage finance, items, and procurement within SAP ECC IDoc accounts directly from their ServiceNow instance. This integration leverages SAP ECC6 (developed on EHp8) and SAP NetWeaver 7.5, using SAP JCo 3.0.20 to facilitate communication. Show full answer Show less ## Key Features * **Integration Hub Subscription:** The spoke requires an Integration Hub subscription to operate. * **Version and Compatibility:** The latest spoke version is 1.5.1, compatible primarily with SAP ECC6 and SAP NW 7.5. * **Required Files:** Customers must obtain SAP proprietary JAR files (sapidoc3.jar, sapjco3.jar) and platform-specific libraries (libsapjco3.so for Linux or sapjco3.dll for Windows) for MID Server communication. * **Custom Interface JAR:** The spoke includes sapConnector-1.0.1.jar to interface SAP ECC IDoc with ServiceNow, installed as part of the spoke. * **Spoke Dependencies:** Ensure ServiceNow IntegrationHub Runtime, Complex Object, and Flow Designer Action Step - Script on MID plugins are installed and licensed as needed. * **Connection and Credential Aliases:** Uses aliases to manage SAP connection and credential data, simplifying environment management and updates. * **MID Server Requirements:** Actions use SAP's RFC protocol via ALE framework and require proper MID Server setup and configuration. ## Key Outcomes The spoke provides a comprehensive set of actions to automate SAP ECC IDoc tasks triggered by events in ServiceNow, streamlining financial, procurement, and item management processes. These actions include: * **Finance:** Create and update fixed assets, GL accounts, invoices, and journal entries. * **Items:** Create and update materials (items). * **Procurement:** Create goods receipts, purchase orders, vendors; update purchase orders. * **Customer Management:** Create and update customer accounts. Using this spoke, ServiceNow customers can efficiently synchronize and manage SAP ECC IDoc data, reducing manual efforts and improving operational accuracy. ## Practical Considerations * Coordinate with SAP ECC IDoc administrators to obtain necessary proprietary files and client values for setup. * When upgrading, if using alongside the SAP ECC RFC spoke, upgrade both simultaneously to maintain compatibility. * Configure MID Server selection and connection aliases properly to ensure secure and reliable communication. * Install the spoke from the ServiceNow Store, as all SAP spokes have been available exclusively there since March 2022. The SAP ECC IDoc spoke is built by Bristlecone, Inc. Manage finance, items, and procurement in SAP ECC IDoc account from your ServiceNow instance. ## Request apps on Store {#sap-ecc-idoc-spoke__section_d11_4nm_rsb} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html). Starting on March 1st 2022, all SAP spokes will be available only on the Store. ## Integration Hub subscription {#sap-ecc-idoc-spoke__section_zpw_dwc_ymb} This spoke requires an Integration Hub subscription. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf). ## Spoke version {#sap-ecc-idoc-spoke__section_kd4_kkx_bsb} SAP ECC IDoc spoke v1.5.1 is the latest version. For version history of the spoke, see [SAP ECC IDoc spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-sap-ecc-idoc.html).{#sap-ecc-idoc-spoke__sap-ecc-idoc-ver-spk} ## Supported versions {#sap-ecc-idoc-spoke__section_aqw_dwc_ymb} This spoke was built for these SAP ECC IDoc versions, but may be compatible with later versions: * SAP application version: SAP ECC6 (Spoke is developed on EHp8.) * NetWeaver Version: SAP NW 7.5 * SAP JCo:3.0.20 {#sap-ecc-idoc-spoke__ul_dmp_kzd_ymb} ## Spoke requirements {#sap-ecc-idoc-spoke__section_dqw_dwc_ymb} * Contact the admin of your SAP ECC IDoc account and obtain these SAP proprietary JAR files and other required files: * sapidoc3.jar and sapjco3.jar. * libsapjco3.so: If your MID Server is installed on a Linux machine, obtain this file. * sapjco3.dll: If your MID Server is installed on a Windows machine, obtain this file. {#sap-ecc-idoc-spoke__ul_agf_vpp_xmb} A JAR file, sapConnector-1.0.1.jar is available along with the spoke to provide a custom interface between SAP ECC IDoc account and ServiceNow instance. The JAR file is installed as part of the spoke in your ServiceNow instance. * Copy and record the client value of the target host where the SAP ECC IDoc server is installed. * If you are using this spoke along with the SAP ECC RFC spoke, during spoke upgrades, ensure that you upgrade both the spokes. {#sap-ecc-idoc-spoke__ul_g3f_np4_xmb} ## Spoke dependencies {#sap-ecc-idoc-spoke__section_fqw_dwc_ymb} If you're having trouble installing the app, ensure that these dependent plugins are installed: * ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime) * Complex Object (com.glide.cobject) * Flow Designer Action Step - Script on MID (com.glide.hub.action_step.script_mid) {#sap-ecc-idoc-spoke__ul_gqw_dwc_ymb} Note: Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation. ## Spoke actions {#sap-ecc-idoc-spoke__section_lqw_dwc_ymb} The SAP ECC IDoc spoke provides actions to automate SAP ECC IDoc tasks when events occurs in your ServiceNow instance. Available actions include: {#sap-ecc-idoc-spoke__table_mqw_dwc_ymb__entry__3} | Category | Action | Description | |-|-|-| | Finance | Create Fixed Assets | Creates fixed asset in your SAP ECC IDoc account. | | Finance | Create GL Account | Creates a GL account in your SAP ECC IDoc account. | | Finance | Create Invoice | Creates an invoice document in your SAP ECC IDoc account. | | Finance | Post Journal Entry | Posts a journal entry in your SAP ECC IDoc account. | | Finance | Update Fixed Assets | Updates details of the fixed assets in your SAP ECC IDoc account. | | Finance | Update GL Account | Updates details of the specified GL account in your SAP ECC IDoc account. | | Items | Create Material | Creates a material (item) in your SAP ECC IDoc account. | | Items | Update Material | Updates details of the specified material (item) in your SAP ECC IDoc account. | | Procurement | Create Goods Receipt | Creates a goods receipt in your SAP ECC IDoc account. | | Procurement | Create Purchase Order | Creates a purchase order in your SAP ECC IDoc account. | | Procurement | Create Vendor | Creates a vendor in your SAP ECC IDoc account. | | Procurement | Update Purchase Order | Updates details of the specified purchase order in your SAP ECC IDoc account. | | Customer | Create Customer | Creates a customer account in SAP ECC IDoc. | | Customer | Update Customer | Update details of the required customer account in SAP ECC IDoc. | [ ] {#sap-ecc-idoc-spoke__table_mqw_dwc_ymb} ## Connection and credential alias requirements {#sap-ecc-idoc-spoke__section_sqw_dwc_ymb} Integration Hub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection. For more information, see [Connections and Credentials](https://www.servicenow.com/docs/access?context=r-credentials&version=australia&pubname=australia-platform-security&ft:locale=en-US). ## MID Server requirements {#sap-ecc-idoc-spoke__section_tqw_dwc_ymb} These actions use Remote Function Call (RFC) protocol (SAP Proprietary protocol -- SAP Standard Interface) leveraging Application Link Enabling (ALE) framework, which can run on an instance or MID Server. Use the connection record associated with the SAP ECC IDoc alias to configure where actions run as well as set MID Server selection attributes. For more information about running actions on the MID Server, see [Integration steps](https://www.servicenow.com/docs/3HAkBEjCzmcSEOfq7SkGnQ "Enable custom actions to integrate with external systems by activating Integration Hub, which adds integration steps to the Workflow Studio interface."). To set up the MID Server for this spoke, see [Set up MID Server for a spoke](https://www.servicenow.com/docs/OEkPOX7xORDj2GD6UZwzjg "Configure MID Server settings on your ServiceNow instance that enables it to integrate with a third-party application via MID Server after you have set up the connection record for a spoke.").