SAP ECC IDoc Spoke
Summarize
Summary of SAP ECC IDoc Spoke
The SAP ECC IDoc spoke, developed by Bristlecone, Inc., enables ServiceNow customers to manage finance, items, and procurement processes within their SAP ECC IDoc account directly from their ServiceNow instance. This spoke integrates SAP ECC system functions with ServiceNow workflows to automate key SAP ECC IDoc tasks efficiently.
Show less
The spoke requires an Integration Hub subscription and is available exclusively through the ServiceNow Store since March 2022. The latest version is 1.5.1 and supports SAP ECC6 (developed on EHp8) with SAP NetWeaver 7.5 and SAP JCo 3.0.20.
Key Features
- Automated Finance Actions: Create and update fixed assets, general ledger accounts, invoices, and journal entries in SAP ECC IDoc.
- Item Management: Create and update materials (items) within SAP ECC IDoc.
- Procurement Functions: Create goods receipts, purchase orders, and vendors, and update purchase orders.
- Customer Management: Create and update customer accounts in SAP ECC IDoc.
- Connection and Credential Management: Uses Integration Hub aliases to manage credentials and connections efficiently across multiple environments without reconfiguration of actions.
- MID Server Integration: Supports execution of actions via the MID Server using SAP’s Remote Function Call (RFC) protocol through the Application Link Enabling (ALE) framework. This allows flexible deployment and secure communication between ServiceNow and SAP ECC.
Requirements and Dependencies
- Obtain SAP proprietary JAR files (sapidoc3.jar, sapjco3.jar) and platform-specific native libraries (libsapjco3.so for Linux or sapjco3.dll for Windows) from your SAP ECC admin.
- A custom JAR file (sapConnector-1.0.1.jar) is provided with the spoke to interface between SAP ECC IDoc and ServiceNow.
- Record the client value of the SAP ECC IDoc target host for configuration.
- If using SAP ECC RFC spoke alongside this spoke, upgrade both simultaneously to maintain compatibility.
- Ensure dependent ServiceNow plugins (IntegrationHub Runtime, Complex Object, Flow Designer Action Step - Script on MID) are installed and appropriately licensed if used outside the spoke.
Practical Benefits for ServiceNow Customers
By implementing the SAP ECC IDoc spoke, customers can automate critical SAP ECC finance, procurement, item, and customer management tasks within ServiceNow, reducing manual effort and improving process integration. The spoke’s design with Integration Hub aliases and MID Server support ensures secure, scalable, and manageable connectivity to SAP systems. This integration empowers ServiceNow users to streamline business workflows, maintain accurate SAP ECC data, and enhance operational efficiency across IT and business functions.
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
Visit the ServiceNow Store 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. Starting on March 1st 2022, all SAP spokes will be available only on the Store.
Integration Hub subscription
This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.
Spoke version
SAP ECC IDoc spoke v1.5.1 is the latest version.
Supported versions
- SAP application version: SAP ECC6 (Spoke is developed on EHp8.)
- NetWeaver Version: SAP NW 7.5
- SAP JCo:3.0.20
Spoke requirements
- 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.
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.
Spoke dependencies
- 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)
Spoke actions
The SAP ECC IDoc spoke provides actions to automate SAP ECC IDoc tasks when events occurs in your ServiceNow instance. Available actions include:
| Category | Action | Description |
|---|---|---|
| Finance | Create Fixed Assets | Creates fixed asset in your SAP ECC IDoc account. |
| Create GL Account | Creates a GL account in your SAP ECC IDoc account. | |
| Create Invoice | Creates an invoice document in your SAP ECC IDoc account. | |
| Post Journal Entry | Posts a journal entry in your SAP ECC IDoc account. | |
| Update Fixed Assets | Updates details of the fixed assets in your SAP ECC IDoc account. | |
| 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. |
| 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. |
| Create Purchase Order | Creates a purchase order in your SAP ECC IDoc account. | |
| Create Vendor | Creates a vendor in your SAP ECC IDoc account. | |
| 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. |
| Update Customer | Update details of the required customer account in SAP ECC IDoc. |
Connection and credential alias requirements
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 .
MID Server requirements
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.
To set up the MID Server for this spoke, see Set up MID Server for a spoke.