Versions Compared

Old Version 2

changes.mady.by.user HISLER, Olivier

Saved on

compared with

New Version Current

changes.mady.by.user HISLER, Olivier

Saved on

Key

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

...

Summary:
This integration creates a shopping cart in SAP SRM based on the reception of a  purchase request event sent by 11VMS when a purchase request is approved .

The integration is triggered by 11VMS calling the EventMeshWrapperFor11VMS API on each purchase request validation


...

1. Overview

...

Page properties
idheaders

Smart ID/Legacy IDs

ISINT01

PROC-11VMS-SRM-SHOPPING-CART-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 purchase request
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 SystemElevenVMS
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 Added

...

3. Integration Design

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

2. Systems Involved

RoleSystem NameDescription
Source11VMS

purchase request provider

TargetSAP SRMSRM creating shopping cart

3. Integration Design

...

  1. Source

...

  1. Target
AttributeDescriptionExampleCommunication ProtocolProtocol used to transfer dataRFCData FormatFormat of exchanged dataXMLVersioning StrategyApproach to manage versionsExplicit versioning in ID


...

4. Security & Access Control

ComponentAuthenticationTransport SecurityAuthorizationNotes
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 4 attempts every 30s
  • Dead Letter Queue: Enabled
  • Alerting: SAP Cloud Alert Notification Services
  • Error Logging: CPI Logs

...

...

7. Technical Artefacts

Artifact TypeLocation
iFlow ID
APIs
Global
EventMeshWrapperFor11VMS_
Customer_Master_Data_PF2 and Global_Customer_Master_Data_WP2Git Repo/PRC-S4-SF-O2C-V1/CUSTOMER/APP-S4-SF-CUSTOMER-V1
v2 & EventMeshAPI_v1 & 11VMSProxy_V2
iFlow IDs"process 11VMS notification_EventMesh" & "process purchase request"
GitHubN/A
API SpecificationOpenAPI Spec
Mapping DocumentMapping Sheet
Technical Documentation 
ETQ Master Data
11VMS Webhooks technical Specification

...

8. Ownership & Contacts

RoleTeam or Person
Business OwnerProcurement Team
Technical OwnerIntegration Team

...

9. Lifecycle & Changes

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

...

11. Sequence Diagram

  • Diagram Image:
    Sequence DiagramImage Removed

  • PlantUML Source: /diagrams/customer_sync_sequence.puml

  • Image Added

...

12. Technical Components Involved

Component TypeName / DetailRole / Description
SAP Integration SuiteCPI / iflow-customer-sync-v1Executes transformation and forwarding
SAP
ISAM
APIMAPI Proxy: customer-api-v1Secures and publishes the REST endpoint
SAP Event MeshTopic: sap/s4/customer/createdEvent source when asynchronous
MFTFile Adapter on B2B Gateway(If used) Handles secure file transportMonitoringSAP Cloud ALMLogs, alerts, KPIsGit Repository/integrations/customer-sync
Holds specs and artifacts

...

13. Functional Requirements & Rules

  • Field CustomerCategory must be transformed into AccountType
  • If SalesOrg is missing, reject the message
    • All customer records must be enriched with region code from value map
  • N/A