SAP-certified · CMIS 1.1 · ArchiveLink
The CaRD Connector links SAP S/4HANA and SAP BTP with Microsoft SharePoint Online over the open CMIS 1.1 standard – ArchiveLink, SAP DMS and business metadata included. Certified by SAP, open to any CMIS application.
Runs on-premises or in the cloud · No changes to standard SAP processes
SAP documents in SharePoint Online — plus standards-compliant access from any CMIS client.
SAP
S/4HANA · SAP BTP · ArchiveLink · DMS
Microsoft 365
SharePoint Online · Microsoft Graph
Open standard
CMIS 1.1 · OASIS · Apache Chemistry
Cloud storage
Azure Blob · AWS S3 · STACKIT Cloud
Compatible with all SAP deployment models — S/4HANA on-premise, RISE with SAP, SAP BTP and SAP Public Cloud.
Why CaRD Connector
SAP receipts, invoices and attachments land directly in SharePoint Online: native browser preview, Microsoft Search, Teams integration and your tenant's permission and compliance tooling. Content stays entirely within your environment – data sovereignty included.
The connector passed SAP's official certification – including compliance scenarios such as legal hold. Verified in live operation with SAP S/4HANA on-premises and the SAP BTP Document Management Service.
CMIS 1.1 Browser Binding per OASIS, compatible with Apache Chemistry / OpenCMIS. The same certified codebase also serves Azure Blob Storage and AWS S3 – switching backends is configuration, not a new project.
Features
From classic ArchiveLink to CMISQL search across millions of documents – the connector covers the SAP content scenarios that actually occur in daily business.
Two-step ArchiveLink filing, document info records (DMS) with original components, KPro flows and multifiling via object links: the connector handles SAP's real-world upload sequences – verified live against S/4HANA, including special-character file names and automatic routing into the right folder structure. Even older SAP systems connect through the classic ArchiveLink interface.
Files automatically receive the proper extension in SharePoint and open right in the browser – while the SAP-side document name stays untouched. SAP finds its components, users get real Office and PDF previews.
Company code, document number and friends are maintained as indexed SharePoint columns – filterable, searchable, ready for reporting. The included REST API lets SAP enrich metadata after the fact, too.
CMISQL queries run against a dedicated metadata index instead of folder trees – designed for millions of documents per repository, with fast property and full-text filters. SAP discovery queries (such as during repository setup) respond instantly.
SELECT * FROM sapbo:JournalEntry WHERE Name = '0500000123'Inbound: Basic, JWT, API key, mTLS and IP allowlist – combinable through a central auth gate. Outbound: app-only access to Microsoft Graph via certificate. Secrets stay in your infrastructure.
Legal hold (records management) with delete protection, versioning via check-out/check-in – and protection against silent overwrites on name collisions.
One installation serves several repositories in parallel – each with its own backend, its own authentication and its own type model. If one repository fails, the others keep running.
The same certified codebase that connects SharePoint also serves Azure Blob Storage, AWS S3 and the STACKIT Cloud. Start with SharePoint and expand later without switching connectors.
SAP BTP & S/4HANA
Cloud-first through the Business Technology Platform, or a direct line to your existing S/4 system: the connector supports both routes. SharePoint Online is the destination either way.
The connector acts as an external CMIS repository behind the SAP BTP Document Management Service (“Bring Your Own Repository”). This is the exact scenario the SAP certification was run in: your SAP cloud applications speak the SAP standard – SharePoint Online is the archive behind it.
Your S/4 system talks to the connector directly via ArchiveLink/CMIS – no BTP layer in between. Verified in live operation with a real S/4HANA: classic ArchiveLink filing, DMS uploads with original components, and KPro flows.
Beyond SAP
The CaRD Connector is a full, standards-compliant CMIS 1.1 interface for SharePoint Online. Any CMIS-capable application – Apache Chemistry / OpenCMIS clients, ECM and DMS systems, or your own software – can file, search and manage documents in SharePoint through it. SAP is the flagship use case, not a prerequisite.
Certification
The CaRD Connector passed SAP's official certification for document management integration – without a single failure in the final certification run.
The same test suite also ran successfully against the connector's Azure Blob and AWS S3 backends.
How it works
SAP S/4HANA, SAP BTP or any other CMIS application files a document through the open CMIS 1.1 standard. The connector stores it in SharePoint Online via Microsoft Graph.
Architecture
Clear separation: applications speak the open CMIS 1.1 standard, SharePoint is connected through Microsoft Graph, and an indexed metadata layer keeps search fast at any scale.
FAQ
CMIS (Content Management Interoperability Services) is an OASIS standard for accessing content repositories. SAP uses CMIS in the SAP BTP Document Management Service, among other places. The CaRD Connector implements CMIS 1.1 (Browser Binding), turning SharePoint Online into a standards-compliant SAP repository – with no proprietary interfaces.
Yes. The connector passed SAP's official test suite for document management integration – including compliance scenarios such as legal hold. On top of that, it is verified in live operation with SAP S/4HANA on-premises.
Yes. The CaRD Connector acts as an external CMIS repository behind the SAP BTP Document Management Service – the exact scenario in which the SAP certification was performed. It works the same way across every SAP deployment model: SAP S/4HANA on-premise, RISE with SAP and SAP S/4HANA Public Cloud. On-premises S/4HANA can also talk to the connector directly via ArchiveLink, without BTP.
Yes. The CaRD Connector is a general-purpose CMIS 1.1 server for SharePoint Online. Any CMIS-capable client – such as Apache Chemistry / OpenCMIS or your own applications – can use it to store, query and manage documents in SharePoint; no SAP system is required.
Classic ArchiveLink (two-step filing), SAP DMS / document info records including original components, KPro flows, and multifiling via object links. Automatic routing files documents in a clean structure by business object and instance.
Yes. The connector stores content directly in your SharePoint libraries; there is no intermediate store outside your infrastructure. Access is app-only via certificate through Microsoft Graph – your tenant's permissions and compliance rules apply unchanged.
Like perfectly normal files: with the correct file extension, native browser preview and indexed metadata columns such as company code or document number. The SAP-side document name stays stable, so SAP can always find its components.
Metadata and CMISQL queries run against a dedicated, fully indexed metadata store – independent of the folder structure. Searches stay fast even with millions of documents per repository.
Either in your own infrastructure (on-premises) or in the cloud – as a lightweight service that requires no changes to SAP or SharePoint. Several repositories – even mixed SharePoint, Azure Blob Storage, AWS S3 and STACKIT Cloud – run in a single installation.
Built on trusted platforms
Delivering SAP solutions since 1994 — and an SAP partner and Microsoft partner for almost as long.