Integration Description
A short description of what this interface does, for whom, and why.
Summary:
This integration generate a good receipt in SAP SRM based on the reception of a activity report event sent by 11VMS when an activity report is approved .
The integration is triggered by 11VMS calling the EventMeshWrapperFor11VMS API on each activity report validation
1. Overview
Smart ID/Legacy IDs | ISINT01
PROC-11VMS-SRM7-ACTIVITY-REPORT-V1 |
|---|
Artefact(s) | - Event Mesh Queue(s)
- API(s)
- EventMeshWrapperFor11VMS_v2
- EventMeshAPI_v1
- 11VMSProxy_V2
- Integration Flow(s)
- 11VMS webhooks
- process 11VMS notification_EventMesh
- process activity report
|
|---|
| LeanIX Fact Sheet(s) |
|
|---|
| Service Pool / Process / Domain | Procurement Data
PRC-S4-SF-O2C-V1
Link to a higher-level process if applicable.
|
|---|
| Integration Type | Event-Driven |
|---|
| Data Volume | Expected volume of records
Low
|
|---|
| Frequency | Real-time |
|---|
| Source System | 11VMS |
|---|
| Source Protocol | REST |
|---|
| Source Data Format | JSON |
|---|
| Source Authentication mechanism | OAuth2 |
|---|
| Target System | SAP SRM7 |
|---|
| Target Protocol | RFC |
|---|
| Target Data Format | XML |
|---|
| Target Authentication mechanism | Client Certificate (Authenticated via Cloud Connector) |
|---|
| SLA | Go to Source and Target Application in LeanIX and look at Business Criticality and Functional Fit section |
|---|
|
2. Low Level Design
3. Systems Involved
| Source | 11VMS | purchase request provider |
| Target | SAP SRM | SRM creating shopping cart |
4. Integration Design
| Frequency | How often data is sent | each time a purchase request is approved in 11VMS |
| Direction | Direction of the data flow | Inbound |
| Data Object | Business object | Shooping Cart |
| Data Volume | Estimated volume | Low (less than 10/day) |
| SLA | Performance expectations | 99.9% uptime, < 500ms |
- Source
| Communication Protocol | Protocol used to transfer data | HTTPS / REST / AMQP |
| Data Format | Format of exchanged data | JSON |
| Versioning Strategy | Approach to manage versions | Explicit versioning in ID |
- Target
| Communication Protocol | Protocol used to transfer data | RFC |
| Data Format | Format of exchanged data | XML |
| Versioning Strategy | Approach to manage versions | Explicit versioning in ID |
5. Security & Access Control
| 11VMS(source) | OAuth2 | HTTPS | N/A |
|
| CPI iFlow | OAuth2 | N/A | N/A | Secured within CPI runtime |
| SAP SRM (target) | Client Certificate | HTTPS (TLS 1.2) | SAP Roles | Authenticated via Cloud Connector |
6. Error & Exception Handling
- Retry Logic: 3 attempts every 30s
- Dead Letter Queue: Enabled
- Alerting: SAP Cloud Alert Notification Services
- Error Logging: CPI Logs
7. Monitoring & Runbook
8. Technical Artefacts
9. Ownership & Contacts
| Business Owner | Procurement Team |
| Technical Owner | Integration Team |
10. Lifecycle & Changes
- Current Status: Active
- History:
2025-12-28 – Created as version V1
11. Related Interfaces
12. Sequence Diagram
Diagram Image:
13. Technical Components Involved
| SAP Integration Suite | CPI / iflow-customer-sync-v1 | Executes transformation and forwarding |
| SAP APIM | API Proxy: customer-api-v1 | Secures and publishes the REST endpoint |
| SAP Event Mesh | Topic: sap/s4/customer/created | Event source when asynchronous |
14. Functional Requirements & Rules