/sap-btp-master-data-integration
Configures and integrates SAP Master Data Integration (MDI) service on SAP Business Technology Platform. Use when setting up MDI tenants, connecting applications (S/4HANA, SuccessFactors, Ariba, Fieldglass, etc.), configuring distribution models, SOAP APIs for business partners,
$ npx -y skills add secondsky/sap-skills --skill sap-btp-master-data-integration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/sap-btp-master-data-integration
Context preview
The summary Claude sees to decide when to auto-load this skill.
Configures and integrates SAP Master Data Integration (MDI) service on SAP Business Technology Platform. Use when setting up MDI tenants, connecting applications (S/4HANA, SuccessFactors, Ariba, Fieldglass, etc.), configuring distribution models, SOAP APIs for business partners,
SKILL.md
sap-btp-master-data-integration.SKILL.mdname: sap-btp-master-data-integration
description: |
Configures and integrates SAP Master Data Integration (MDI) service on SAP Business Technology Platform. Use when setting up MDI tenants, connecting applications (S/4HANA, SuccessFactors, Ariba, Fieldglass, etc.), configuring distribution models, SOAP APIs for business partners, extensibility, or troubleshooting master data replication. Covers One Domain Model integration, Business Data Orchestration, client authentication (OAuth2, mTLS), and security configurations.
license: GPL-3.0
metadata:
maintainer: "Eduard Jiglau"
maintainer_email: "hello@sap-ai-skills.com"
website: "https://sap-ai-skills.com"
version: "2.4.1"
last_verified: "2025-11-27"
SAP BTP Master Data Integration
Related Skills
- **sap-btp-cloud-platform**: Use for subaccount, entitlement, and service instance setup
- **sap-btp-connectivity**: Use for destination and authentication configuration around connected systems
- **sap-btp-integration-suite**: Use for MDI Adapter and broader integration orchestration scenarios
- **sap-api-style**: Use when documenting MDI SOAP/API contracts and integration behavior
When to Use This Skill
Use this skill when setting up MDI tenants, connecting SAP applications, configuring distribution models, choosing MDI service plans, integrating business partner SOAP APIs, handling One Domain Model versions, or troubleshooting master data replication.
Table of Contents
- [Quick Reference](#quick-reference)
- [Core Concepts](#core-concepts)
- [Decision Trees](#decision-trees)
- [Setup Workflow](#setup-workflow)
- [System Limitations](#system-limitations)
- [Client Configuration](#client-configuration)
- [SOAP Endpoints](#soap-endpoints)
- [Common Integration Scenarios](#common-integration-scenarios)
- [Security Best Practices](#security-best-practices)
- [Troubleshooting](#troubleshooting)
- [Bundled Resources](#bundled-resources)
SAP Master Data Integration (MDI) is a central master data hub on SAP BTP that enables applications to synchronize local master data databases with a centralized repository.
Quick Reference
What MDI Does
- Replicates master data between connected applications
- Supports 34 master data types via SAP One Domain Model
- Provides filtering to control data distribution scope
- Enables extensibility with custom fields
What MDI Does NOT Do
- Consolidation (use SAP Master Data Governance)
- Data quality control
- Central governance workflows
- Referential integrity validation
Core Concepts
Key Terms
| Term | Definition | |------|------------| | Tenant | Isolated MDI environment per subaccount with own database and configs | | Client | Application that integrates with MDI (producing or consuming) | | Producing Client | Sends change requests to MDI (upstream/writing client) | | Consuming Client | Receives change events from MDI (downstream/reading client) | | Distribution Model | Configuration controlling which data replicates where | | Change Token | Unique identifier per change request (max 36 chars) |
Integration Models (SAP One Domain Model)
**Business Partner** - v2.1.1, v3.3.0 (multiversion support restricted for address data) **Finance** - Cost Center v3.1.0, Exchange Rate v4.0.0, Bank v3.0.0 **Workforce** - Person v5.0.0, Job Classification v4.0.0, Organizational Unit v4.0.0 **Procurement** - Purchasing Organization v4.0.0, Purchasing Group v6.0.0 **Assets** - Equipment v5.1.0, Functional Location v5.0.0 **Products** - Product v5.0.0, Product Group v5.0.0
For complete list see `references/integration-models.md`
Decision Trees
Which Service Plan?
Is application SAP-branded cloud?
├─ Yes → sap-integration plan (FREE)
└─ No → Is it SAP S/4HANA On-Premise?
├─ Yes → s4hana-onpremise plan (PAID - storage + bandwidth)
└─ No → Use SAP Integration Suite with MDI AdapterWhich Authentication Method?
Mutual-TLS with X.509 certificates available?
├─ Yes → Use mTLS (RECOMMENDED)
│ credential-type: x509
│ Configure validity: DAYS/MONTHS/YEARS
└─ No → Use Client Credentials Grant (DEFAULT)
Uses client_id/client_secret pairsREST vs SOAP API?
Master data type is Business Partner?
├─ Yes → SOAP API available for:
│ - Business Partner replication
│ - BP Relationship replication
│ - Key Mapping replication
│ - Confirmations
└─ No → REST API (Events API, Requests API, KeyMapping API)
Setup Workflow
1. Prerequisites
- SAP BTP global enterprise account (no trial/free tier)
- Subaccount in supported region: EU10, US10, AP10, AP11
- Cloud Foundry space within subaccount
- User with BusinessConfigurationAdmin role
2. Create Tenant
1. Create subaccount in available region
2. Subscribe to SAP Master Data Integration Tenant application
3. One tenant maximum per subaccount
4. Separate tenants for dev/test/prod recommended
3. Connect Application
1. Create service instance (one per application - MANDATORY)
2. Choose service plan (sap-integration or s4hana-onpremise)
3. Set 'application' attribute (e.g., "s4" for S/4HANA Cloud)
4. Create service binding for credentials
5. Configure writePermissions for entity types
4. Configure Distribution Model
1. Access Business Data Orchestration UI
2. Create distribution model (provider → consumer)
3. Set filters (object selection + data scope)
4. Activate model
System Limitations
| Limit | Value | |-------|-------| | Change Request Size | 256 KB (512 KB for Business Partner) | | Master Data Record Size | 512 KB | | Change Token Length | 36 characters max | | Delta Token Validity | 28 days | | SOAP Payload Size | 10 MB | | Change Token Characters | a-z, A-Z, 0-9, -, _ |
Client Configuration Attributes
businessSystemId
- Required for SOAP API integration
- Max 60 characters, unique per tenant
- Must match SenderBusinessSystemID in SOAP messages
writePermissions
"
Read more
name: sap-btp-master-data-integration description: | Configures and integrates SAP Master Data Integration (MDI) service on SAP Business Technology Platform. Use when setting up MDI tenants, connecting applications (S/4HANA, SuccessFactors, Ariba, Fieldglass, etc.), configuring distribution models, SOAP APIs for business partners, extensibility, or troubleshooting master data replication. Covers One Domain Model integration, Business Data Orchestration, client authentication (OAuth2, mTLS), and security configurations. license: GPL-3.0 metadata: maintainer: "Eduard Jiglau" maintainer_email: "hello@sap-ai-skills.com" website: "https://sap-ai-skills.com" version: "2.4.1" last_verified: "2025-11-27"
SAP BTP Master Data Integration
Related Skills
- **sap-btp-cloud-platform**: Use for subaccount, entitlement, and service instance setup
- **sap-btp-connectivity**: Use for destination and authentication configuration around connected systems
- **sap-btp-integration-suite**: Use for MDI Adapter and broader integration orchestration scenarios
- **sap-api-style**: Use when documenting MDI SOAP/API contracts and integration behavior
When to Use This Skill
Use this skill when setting up MDI tenants, connecting SAP applications, configuring distribution models, choosing MDI service plans, integrating business partner SOAP APIs, handling One Domain Model versions, or troubleshooting master data replication.
Table of Contents
- [Quick Reference](#quick-reference)
- [Core Concepts](#core-concepts)
- [Decision Trees](#decision-trees)
- [Setup Workflow](#setup-workflow)
- [System Limitations](#system-limitations)
- [Client Configuration](#client-configuration)
- [SOAP Endpoints](#soap-endpoints)
- [Common Integration Scenarios](#common-integration-scenarios)
- [Security Best Practices](#security-best-practices)
- [Troubleshooting](#troubleshooting)
- [Bundled Resources](#bundled-resources)
SAP Master Data Integration (MDI) is a central master data hub on SAP BTP that enables applications to synchronize local master data databases with a centralized repository.
Quick Reference
What MDI Does
- Replicates master data between connected applications
- Supports 34 master data types via SAP One Domain Model
- Provides filtering to control data distribution scope
- Enables extensibility with custom fields
What MDI Does NOT Do
- Consolidation (use SAP Master Data Governance)
- Data quality control
- Central governance workflows
- Referential integrity validation
Core Concepts
Key Terms
| Term | Definition | |------|------------| | Tenant | Isolated MDI environment per subaccount with own database and configs | | Client | Application that integrates with MDI (producing or consuming) | | Producing Client | Sends change requests to MDI (upstream/writing client) | | Consuming Client | Receives change events from MDI (downstream/reading client) | | Distribution Model | Configuration controlling which data replicates where | | Change Token | Unique identifier per change request (max 36 chars) |
Integration Models (SAP One Domain Model)
**Business Partner** - v2.1.1, v3.3.0 (multiversion support restricted for address data) **Finance** - Cost Center v3.1.0, Exchange Rate v4.0.0, Bank v3.0.0 **Workforce** - Person v5.0.0, Job Classification v4.0.0, Organizational Unit v4.0.0 **Procurement** - Purchasing Organization v4.0.0, Purchasing Group v6.0.0 **Assets** - Equipment v5.1.0, Functional Location v5.0.0 **Products** - Product v5.0.0, Product Group v5.0.0
For complete list see `references/integration-models.md`
Decision Trees
Which Service Plan?
Is application SAP-branded cloud?
├─ Yes → sap-integration plan (FREE)
└─ No → Is it SAP S/4HANA On-Premise?
├─ Yes → s4hana-onpremise plan (PAID - storage + bandwidth)
└─ No → Use SAP Integration Suite with MDI AdapterWhich Authentication Method?
Mutual-TLS with X.509 certificates available?
├─ Yes → Use mTLS (RECOMMENDED)
│ credential-type: x509
│ Configure validity: DAYS/MONTHS/YEARS
└─ No → Use Client Credentials Grant (DEFAULT)
Uses client_id/client_secret pairsREST vs SOAP API?
Master data type is Business Partner? ├─ Yes → SOAP API available for: │ - Business Partner replication │ - BP Relationship replication │ - Key Mapping replication │ - Confirmations └─ No → REST API (Events API, Requests API, KeyMapping API)
Setup Workflow
1. Prerequisites
- SAP BTP global enterprise account (no trial/free tier)
- Subaccount in supported region: EU10, US10, AP10, AP11
- Cloud Foundry space within subaccount
- User with BusinessConfigurationAdmin role
2. Create Tenant
1. Create subaccount in available region 2. Subscribe to SAP Master Data Integration Tenant application 3. One tenant maximum per subaccount 4. Separate tenants for dev/test/prod recommended
3. Connect Application
1. Create service instance (one per application - MANDATORY) 2. Choose service plan (sap-integration or s4hana-onpremise) 3. Set 'application' attribute (e.g., "s4" for S/4HANA Cloud) 4. Create service binding for credentials 5. Configure writePermissions for entity types
4. Configure Distribution Model
1. Access Business Data Orchestration UI 2. Create distribution model (provider → consumer) 3. Set filters (object selection + data scope) 4. Activate model
System Limitations
| Limit | Value | |-------|-------| | Change Request Size | 256 KB (512 KB for Business Partner) | | Master Data Record Size | 512 KB | | Change Token Length | 36 characters max | | Delta Token Validity | 28 days | | SOAP Payload Size | 10 MB | | Change Token Characters | a-z, A-Z, 0-9, -, _ |
Client Configuration Attributes
businessSystemId
- Required for SOAP API integration
- Max 60 characters, unique per tenant
- Must match SenderBusinessSystemID in SOAP messages
writePermissions
"
40 SAP development plugins with evidence-tracked verification SAP development plugins for AI coding assistants, with public-source or package-registry verification tracked where available.
Repo: secondsky/sap-skills
Other skills on sap-skills.
- /sap-abap-cds
Comprehensive SAP ABAP CDS (Core Data Services) reference for data modeling, view development, and semantic enrichment. Use when creating CDS views or view entities, defining data models with annotations, working with associations and cardinality, implementing input parameters,
Open skill - /sap-abap
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing,
Open skill - /sap-ai-core
Guides development with SAP AI Core and SAP AI Launchpad for enterprise AI/ML workloads on SAP BTP. Use when: deploying generative AI models, building orchestration workflows with templating/filtering/grounding, implementing RAG with vector databases, managing ML training
Open skill - /sap-api-policy
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use",
Open skill - /sap-api-style
This skill provides comprehensive guidance for documenting SAP APIs following the SAP API Style Guide standards. It should be used when creating or reviewing API documentation for REST, OData, Java, JavaScript, .NET, or C/C++ APIs. The skill covers naming conventions,
Open skill - /sap-browser-automation
Use when an agent must inspect or operate an authenticated SAP web UI through an in-app Browser, Microsoft Edge CDP, or an existing Playwright client, especially when SAP SSO reuse, isolated Edge profiles, deterministic target selection, screenshots, or browser bootstrap
Open skill

