Below is a simplified high level integration looks like for the example of SAP Ariba and specifically the SAP Risk module.
Here is the same example with a sample flow of how Prewave scores are exhibited in the desired integration system.
Above is a sample workflow where the Target API may be sending Scoring data to the SAP Ariba API for example. Another well used scenario is that of a “push” of supplier data is sent to Prewave using the Sites Upsert API. Customers can do “full” updates or “delta” updates of their supplier information this way. There are API endpoints for both.
The following table covers the most common flows requested by customers if we are doing an SAP integration with them. The standard Transmission Method used by Prewave is our APIs and the APIs of the target integration system.
For external system integrations, we create microservices internally which act as a middleware to consume data. This is the “SAP Ariba Integration Service” shown in the diagram above.
|
Object / Flow Name |
Source System (API/Endpoint) |
Target System (API/Endpoint) |
Operation (Request) |
Details |
|
Supplier Read |
SAP Ariba: Vendor Details |
Prewave: Sites Upsert API (Full/Delta) |
Read (GET) |
Get the supplier information from the source system |
|
Supplier Sync |
SAP Ariba: Vendor Details |
Prewave: Sites Upsert API (Full/Delta) |
Update (POST) |
FULL is used for more comprehensive adding of targets, suppliers and collection maintenance DELTA is used for continuous adding and removing of suppliers. |
|
Source Supplier Information |
SAP Ariba: Contract Workspaces OR Process Details |
Prewave: Sites Upsert API (Full/Delta) |
Read / Update |
Additional common information needed from customers: categories, spend/purchase, … |
|
Centralisation of Risk Scoring |
Prewave: Targets API |
SAP Ariba: Patch Suppliers |
Update (PATCH) |
One of the more popular functionalities/scenarios for our customers is writing Prewave Scores to their desired system. There are multiple score related endpoints like the core scores and the score components, depends on user scenario what is needed. |
|
Tier N |
Prewave: Network |
|
|
Common Scenario used to get visibility of supply chain and the map of suppliers at different depths |
|
Alerts |
Prewave: Disruptions |
|
|
Common Scenario of getting data on alerts, like in the UI, for specific Targets |