SAP Ariba Spoke – Need guidance on complete configuration after connection setup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
I’m currently working on integrating SAP Ariba with ServiceNow using the SAP Ariba Spoke (IntegrationHub). Our objective is to synchronize Vendors (Suppliers) from SAP Ariba into ServiceNow and eventually create/update records in the core_company table.
Current Progress:
1. Installed the SAP Ariba Spoke.
2. Configured the required Connection & Credential Aliases.
3. Successfully configured several REST/OAuth connections.
4. OAuth token is being generated successfully.
5. We have reviewed the official ServiceNow documentation and completed the connection configuration.
Challenge:
The documentation mainly explains how to configure the connections, but it doesn’t explain the complete end-to-end process after the connections are established. We’re looking for guidance on:
1. Which SAP Ariba action should be executed first to retrieve supplier/vendor data?
2. Is there any out-of-the-box Flow or Subflow that should be used, or do we need to create our own Flow?
3. How do the following components work together?
- Execute Export Task
- Copy Ariba File to Data Source
- Import Set
- Transform Map
4. Are there any out-of-the-box Data Sources and Transform Maps available, or are they expected to be created manually?
5. What is the recommended approach to synchronize vendors into the core_company table?
6. Are there any implementation guides, sample flows, or best practices that demonstrate the complete end-to-end process?
Additional Information Our initial scope is only:
- Synchronize Suppliers/Vendors from SAP Ariba
- Populate the core_company table
- Run the synchronization on a scheduled basis (daily/weekly) If anyone has implemented this integration or can share the recommended approach, documentation, or sample implementation, it would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The SAP Ariba Spoke enables seamless integration between Servicenow and SAP Ariba using Flow Designer. It provides built-in, bidirectional flows and actions to automate sourcing, procurement, and supplier data management.
Yes spokes provides subflows which you need to call using your flow.
Check demo videos from here as per your usecase.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I’m implementing an integration using the SAP Ariba Spoke in ServiceNow, and our client has specifically requested that we use the OOTB SAP Ariba Spoke instead of direct REST API calls. I have successfully:
1. Installed the SAP Ariba Spoke
2. Configured the Connection & Credential Alias
3. Verified that the Create Job action is available under Async Reporting Job Management.
However, I’m blocked on the Create Job action.
The action requires a mandatory Schema object containing fields such as:
- Request ID
- View Template Name
- Filters
- etc. In Flow Designer, the Schema field only accepts an Object data pill. It doesn’t allow manual entry, and I cannot find any OOTB action or subflow that generates this object. My questions are: 1. How is the Schema object supposed to be created? 2. Is there an OOTB action or Data Stream that builds this object? 3. Do we need to construct the object manually using Script Steps? 4. If anyone has a working example of the Create Job flow for Operational Reporting, could you please share the design or screenshots? I’m specifically looking for the recommended OOTB approach using the SAP Ariba Spoke. Any guidance would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @RifqaF924293819,
Besides the decision on how you will load your data, make sure you set up the Normalization Data Services before ingesting your company data. This will avoid duplicates that you might need to clean-up later.
No OOTB import table or transform map exists, but you can just create them. There is no need to use the spokes unless you want to trigger Ariba business logic.
You can either do direct API calls or calls via middleware, e.g., Integration Hub or Workflow Data Fabric, depending on your integration pattern. Meaning you populate to the import table whenever creating or modifying supplier/vender data in SAP Ariba or MDM and let ServiceNow handle the transform later. An alternative will be reading the data from SAP periodically with IRE/WDF and add new or modified data to the import table.
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I’m implementing an integration using the SAP Ariba Spoke in ServiceNow, and our client has specifically requested that we use the OOTB SAP Ariba Spoke instead of direct REST API calls. I have successfully:
1. Installed the SAP Ariba Spoke
2. Configured the Connection & Credential Alias
3. Verified that the Create Job action is available under Async Reporting Job Management.
However, I’m blocked on the Create Job action.
The action requires a mandatory Schema object containing fields such as:
- Request ID
- View Template Name
- Filters
- etc. In Flow Designer, the Schema field only accepts an Object data pill. It doesn’t allow manual entry, and I cannot find any OOTB action or subflow that generates this object. My questions are: 1. How is the Schema object supposed to be created? 2. Is there an OOTB action or Data Stream that builds this object? 3. Do we need to construct the object manually using Script Steps? 4. If anyone has a working example of the Create Job flow for Operational Reporting, could you please share the design or screenshots? I’m specifically looking for the recommended OOTB approach using the SAP Ariba Spoke. Any guidance would be greatly appreciated.