Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page properties
idheaders

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 / DomainProcurement Data
PRC-S4-SF-O2C-V1
Link to a higher-level process if applicable.

Integration Type

Event-Driven

Data VolumeExpected volume of records
Low
FrequencyReal-time
Source System11VMS 
Source ProtocolREST
Source Data Format

JSON

Source Authentication mechanismOAuth2
Target SystemSAP SRM7
Target ProtocolRFC
Target Data FormatXML
Target Authentication mechanismClient Certificate (Authenticated via Cloud Connector)
SLAGo to Source and Target Application in LeanIX and look at Business Criticality and Functional Fit section


...

2. Low Level Design

Image Removed

3. Systems Involved

Source11VMS

purchase request provider

TargetSAP SRMSRM creating shopping cart

...

Image Added

  • 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


FrequencyHow often data is senteach time a purchase request is approved in 11VMS
DirectionDirection of the data Data flow Inbound
Data ObjectBusiness objectShooping Cart 
Data VolumeEstimated volumeLow (less than 10/day)
SLAPerformance expectations99.9% uptime, < 500ms
  1. Source

...

orientationInbound, Outbound, Both - to be discussed with Owen
Versioning StrategyHow interface versioning is managedURI, Header, SmartID


...

4

  1. Target
Communication ProtocolProtocol used to transfer dataRFC
Data FormatFormat of exchanged dataXML
Versioning StrategyApproach to manage versionsExplicit versioning in ID

...

. Security & Access Control


11VMS(source)OAuth2HTTPSN/A
CPI iFlowOAuth2N/AN/ASecured within CPI runtime
SAP SRM (target)Client CertificateHTTPS (TLS 1.2)SAP RolesAuthenticated 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

...

7. Technical Artefacts


APIsEventMeshWrapperFor11VMS_v2 & EventMeshAPI_v1 & 11VMSProxy_V2
iFlow IDs"process 11VMS notification_EventMesh" & "process purchase request"
GitHubN/A
API SpecificationOpenAPI Spec
Mapping DocumentMapping Sheet
Technical Documentation 11VMS Webhooks technical Specification

...

8. Ownership & Contacts


Business OwnerProcurement Team
Technical OwnerIntegration 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 SuiteCPI / iflow-customer-sync-v1Executes transformation and forwarding
SAP APIMAPI Proxy: customer-api-v1Secures and publishes the REST endpoint
SAP Event MeshTopic: sap/s4/customer/createdEvent source when asynchronous

...

13. Functional Requirements & Rules

  • N/A