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.

Status	InActive
Created	2026-03-16
Updated	2025-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)	Linked LeanIX Interface Fact Sheet For example, MyID to SAP SuccessFactors Employee Central
Service Pool / Process / Domain	Travel & 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 Protocol	REST
Source Data Format	JSON
Source Authentication mechanism	None
Target System	WP2 or PF2
Target Protocol	IDOC
Target Data Format	XML
Target Authentication mechanism	Basic Authentication
SLA	Go 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

API calls loop to get all card transactions based on the field sumPage

Integration Flow

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
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 Type	Name / Detail	Role / Description
Integration Flow	CMB China Bank to SAP WP2 CMB China Bank to SAP PF2 Get Card Transactions	Executes logic
API Management	`N/A`	Secures and routes requests
Event System	`N/A`	Publishes asynchronous events
File Gateway	`N/A`	For batch file interfaces
Monitoring	CPI Logs	Monitoring tools
Alerting	SAP Cloud Alert Notification	Alerting tools

Integration Design

Core interface behaviour and configuration.

Attribute	Description	Example
Direction	Data flow orientation	`Inbound`, `Outbound`, `Both - to be discussed with Owen`
Versioning Strategy	How interface versioning is managed	`URI`, `Header`, `SmartID`

Transformation

Security & Access Control

Per-component security model.

Component	Authentication	Transport Security	Authorization	Notes
SAP ECC	`Client Certificate`	`TLS 1.2`	`SAP Roles`	Cloud Connector
CPI	`OAuth2`	`N/A`	`Internal Only`	Managed by tenant
CMB China API	`Basic`	`HTTPS`	`Token Scopes`	Dedicated user

Error & Exception Handling

Resilience and error management.

Retry Logic	3x every 30s
Dead Letter Queue	Not Applicable
Alerting	SAP Cloud Alert Notification
Error Logging	CPI Logs

Monitoring & Runbook

How is the interface observed and troubleshooted.

Monitoring Tool	SAP Cloud ALM, Grafana, Elastic
Runbook Location	[Runbook PDF](#)
Dashboard URL	[Grafana Dashboard](#)

Other Artefacts

Implementation assets.

Artefact	Notes
Git Repository
API Specification	Please refer to API Reference tab
Test Results