SAP Master Data Integration
A multi-tenant cloud service that replicates master data between two or more clients, giving a hybrid landscape a consistent view of it, with filters set through SAP Business Data Orchestration service.
SAP Master Data Integration is a multi-tenant cloud service for master data integration. It provides a consistent view on master data across a hybrid landscape, and it can be used to replicate master data between two or more clients. Which records that replication carries is configured through filters set via SAP Business Data Orchestration service, and the aligned master data objects it replicates can be extended with fields and entities to support an application's own business requirements.
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 4
- Regions
- 11
- Support component
- BC-CP-CF-ONEMDS
For data federation
- Strategy
- copy
Connections
Reading data from another system as if it were local
Download
What’s New
from SAP Help Portal, readIntegration Models
About This Service
Monitoring and Troubleshooting
Service Degradation
New ODM Entities Released
Optional GTID Instance Configuration
Removal of Unused ODM Product Versions from Production
logSys Service Instance Configuration
Monitoring and Troubleshooting
Extensibility v1 API
Deprecation of v0 Extensibility for Business Partner (SOAP and REST)
Document removal of SOAP APIs for Product and other related Product configurations
Mandatory Write Permissions in Master Data Integration Configuration
Safeguarding Mechanism for Disconnecting Clients
Read Access Logging Enhancements
Protect administrative access by Multi Factor Authentication
Removal of BusConfignVersion attribute from Business System Configuration.
Others providing
Compare all 6 on the Data federation page →- cds-federation-synonymscds-federation-synonymsAn experimental CAP plugin for CAP-to-CAP data federation over SAP HANA synonyms, so one project reads another's tables without the rows being copied.sap official, capCAP-to-CAP data federation over SAP HANA synonymsfrom CAP
- @cap-js-community/common@cap-js-community/commonSix independent features for CAP services in one package: replication cache, migration check, rate limiting, a Redis client broker, a local HTML5 repository and a CDM builder.community org, capSix CAP features in one package, from replication cache to rate limitsfrom CAP
- cds-data-federationcds-data-federationA data federation plugin for SAP CAP applications that declares delegation, caching and replication on a consumption view through CDS annotations, instead of hand-written handlers.independent, capData federation for CAP via delegation, caching and replicationfrom CAP
- cds-data-pipelinecds-data-pipelineDeclarative scheduled pipelines between CAP services — each one a linear READ, MAP, WRITE from a single source to a single target, with tracking, retry, delta support and a management API.independent, capScheduled READ, MAP, WRITE pipelines between CAP servicesfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-master-data-integration- JSON
- /artifacts/btp-master-data-integration.json
- MCP
- Connecting an agent