Overview
This article provides an overview of how to integrate SAP systems with Workiva, including supported connection methods, authentication types, and integration models (Push vs. Pull). Use this guide to understand which integration strategy works best for your SAP environment and reporting needs.
Note: This article assumes some familiarity with SAP and Workiva integration basics.
If you're new to integrations or unsure where to start, please contact your Workiva representative or SAP administrator.
Push vs. Pull Integration
To integrate SAP data with Workiva, it’s important to understand whether Workiva should pull the data or SAP should push it.
| Mode | Description | Responsibility | When to Use |
|---|---|---|---|
| Pull | Workiva Chains calls a SAP API | SAP must develop and expose an OAuth2-secured API | On-demand, controlled, or reactive access to SAP data. |
| Push | SAP sends data to Workiva | SAP handles delivery, format and schedule | SAP initiated data delivery to the Workiva Platform |
Pull
If you prefer Workiva to pull data from SAP, follow the steps below to expose SAP BW or S/4HANA data as OData services. This enables Workiva Chains to securely call SAP APIs.
| Steps to expose SAP BW data via OData | Steps to expose SAP S/4HANA data via OData | ||
|---|---|---|---|
| 1 | Create an SAP BW query using either EasyQuery or ABAP CDS-based queries | Build a custom CDS view. Define and model the required dataset. |
|
| 2 | Expose the query as an OData service. | Expose the CDS view as OData service. | |
| 3 |
Optionally expose the API using one of the following: |
Optionally expose the API using one of the following: |
|
| 4 | Secure the Endpoint with OAuth 2.0 Client Credentials. | Secure the Endpoint with OAuth 2.0 Client Credentials. | |
| 5 | Test the API Endpoint using Postman or similar tools. | Test the API Endpoint using Postman or similar tools. | |
Push
If you prefer SAP to push data into Workiva, consider using SAP CPI as middleware. It manages both the scheduling and formatting of data before it's delivered to Workiva APIs.
CPI functions similarly to Workiva Chains, providing logic, scheduling, and transformation capabilities, but the configuration and maintenance are fully owned by SAP.
With SAP CPI, you can Push data directly into Workiva using Workiva APIs.
SAP Integration Matrix
This matrix provides a high-level overview of how different SAP systems can integrate with Workiva. It outlines supported integration methods, required middleware, authentication types, and whether the approach is compatible with Chains. Use this as a quick reference to identify the best integration path based on your SAP environment.
| SAP System | Integration Method | Middleware / Tooling | Authentication | Integration Flow | Chain-Compatible |
| S/4 HANA Cloud | CDS View + OData API | Optional: SAP APIM, SAP CAP | OAuth 2.0 | Workiva pulls from exposed SAP API endpoint via Http Connector | ✅ Yes |
| SAP BW (NetWeaver) | BEx Query or ABAP CDS views + OData | SAP Cloud Connector + SAP APIM | OAuth 2.0 | Workiva pulls from exposed APIM endpoint via Http Connector | ✅ Yes |
| SAP BW (Non-NW) |
SFTP | Chains | Username/Password or Private Keys | Workiva pulls via SFTP connector | ✅ Yes |
| SAP BW/4HANA on-prem | SAP BW Connector + Ground Runner | Chains | Username/Password | Workiva pulls via SAP BW connector | ✅ Yes |
| SAP BPC NW / MS 10.0 (Non-HANA) |
SAP BW Connector + Ground Runner | Chains | Username/Password | Workiva pulls via SAP BW connector | ✅ Yes |
| SAP HANA Database | SAP HANA JDBC Connector + Ground Runner | Chains | Username/Password | Workiva pulls from SAP via the connector | ✅ Yes |
| SAP Datasphere | SAP HANA JDBC Connector + Cloud Runner | Chains | Username/Password | Workiva pulls from SAP via the connector | ✅ Yes |
| SAP CPI (Push Model) |
HTTP Endpoint to Workiva API/Webhook | SAP CPI | OAuth 2.0 | SAP pushes to Workiva via Workiva API | ✅ Yes |