View Source

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) ElevenVMS 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

if the activity report doesn't contains any working day (workUnitNumber = 0), we don't send anything tp SAP SRM7 we just update the activity report status to validated by calling the Service Reception API (status: validated , message: Ignored because no working days were perfromed during the month)

3. Integration Design

Frequency	How often data is sent	each time a purchase request is approved in 11VMS
Direction	Data flow orientation	`Inbound`, `Outbound`, `Both - to be discussed with Owen`
Versioning Strategy	How interface versioning is managed	`URI`, `Header`, `SmartID`

4. 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

5. Error & Exception Handling

Retry Logic: 3 attempts every 30s
Dead Letter Queue: Enabled
Alerting: SAP Cloud Alert Notification Services
Error Logging: CPI Logs

6. Monitoring & Runbook

Monitoring Tool: CPI Logs
Runbook Location: Link to runbook
Dashboard URL: Link to dashboard

7. Technical Artefacts

APIs	EventMeshWrapperFor11VMS_v2 & EventMeshAPI_v1 & 11VMSProxy_V2
iFlow IDs	"process 11VMS notification_EventMesh" & "process purchase request"
GitHub	N/A
API Specification	OpenAPI Spec
Mapping Document	Mapping Sheet
Technical Documentation	11VMS Webhooks technical Specification

8. Ownership & Contacts

Business Owner	Procurement Team
Technical Owner	Integration Team

9. Lifecycle & Changes

Current Status: Active
History:
- 2025-12-28 – Created as version V1

10. Related Interfaces

11. Sequence Diagram

Diagram Image:

12. 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

13. Functional Requirements & Rules

N/A