This template is designed to guide integration architects and developers in documenting all required information for an interface. Each section includes a short explanation (tooltip) and example values to clarify usage.

Lifecycle & Changes

Historical context and milestones.

StatusInActive
Created2026-03-16
Updated2025-05-01

Integration Description

What is this interface about? Who uses it and for what purpose? 

Summary

This interface integrates the card transactions from the CMB china bank into SAP WP2 and SAP PF2

Use Case Reference

Example: Project Sunrise - Use Case: Customer Creation

Overview

Basic metadata and lifecycle of the interface.

Smart ID/Legacy IDs

 T&E-CMB_CHINA-WP2-INVOICES-V1

Artefact(s)

  • Value mapping(s)
    • CMB Parameters Selector for SAP
  • Integration Flow(s)
    • CMB China 
      • CMB China Bank to SAP WP2
      • CMB China Bank to SAP PF2
      • Get Card Transactions
LeanIX Fact Sheet(s)
Service Pool / Process / DomainTravel & Expense Data
Integration Style

Application Integration

Data Volume

Low - less than 1000 per day

Frequency
  • Daily 08:30 PM CET for WP2
  • Daily at 09:30 PM CET for PF2
Source System

CMB China

Source ProtocolREST
Source Data Format

JSON

Source Authentication mechanismNone
Target System

WP2 or PF2

Target ProtocolIDOC
Target Data FormatXML
Target Authentication mechanismBasic Authentication
SLAGo to Source and Target Application in LeanIX and look at Business Criticality and Functional Fit section
Version

Increment for significant logic changes, for example, V1

Functional Requirements & Rules

Integration Flow


  1. CMB China Bank to SAP WP2
    1. get card transactions by calling the API "Transaction Data Query" with the company 7728 credentials (WP2)
    2. if sumPage is greater than 1, loop to get all card transactions
    3. merge all card transactions in one single payload
    4. based on this payload generate the IDoc INVOIC02
    5. send the IDoc to WP2
  2. CMB China Bank to SAP PF2
    1. get card transactions by calling the API "Transaction Data Query" with the company 5876 credentials (PF2)
    2. if sumPage is greater than 1, loop to get all card transactions
    3. merge all card transactions in one single payload
    4. based on this payload generate the IDoc INVOIC02
    5. send the IDoc to PF2

 

Technical Components Involved

Detailed list of systems and middleware used.

Component TypeName / DetailRole / Description
Integration Flow
  • CMB China Bank to SAP WP2
  • CMB China Bank to SAP PF2
  • Get Card Transactions
Executes logic
API ManagementN/ASecures and routes requests
Event SystemN/APublishes asynchronous events
File GatewayN/AFor batch file interfaces
MonitoringCPI LogsMonitoring tools
AlertingSAP Cloud Alert NotificationAlerting tools

Integration Design

Core interface behaviour and configuration.

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

Transformation

Security & Access Control


Per-component security model.

ComponentAuthenticationTransport SecurityAuthorizationNotes
SAP ECCClient CertificateTLS 1.2SAP RolesCloud Connector
CPIOAuth2N/AInternal OnlyManaged by tenant
CMB China APIBasic HTTPSToken ScopesDedicated user

Error & Exception Handling

Resilience and error management.

Retry Logic3x every 30s
Dead Letter QueueNot Applicable
AlertingSAP Cloud Alert Notification
Error LoggingCPI Logs

Monitoring & Runbook

How is the interface observed and troubleshooted.

Monitoring Tool
Runbook Location
Dashboard URL

Other Artefacts

Implementation assets.

ArtefactNotes
Git Repository
API Specification
Test Results

Step by Step Configuration

CMB China Bank to SAP WP2

Start On Schedule (Timer Start)

CMB China Bank to SAP PF2

Start On Schedule (Timer Start)


Related Interfaces

Grouped interfaces or dependencies.