SAP Document Management at scale
Millions of documents, terabytes of files, distributed Content Servers — SAP Engineering Control Center handles this. The Fiori and OData surface in S/4HANA doesn't. We bridge that gap.
Sounds familiar?
Fiori and OData in S/4HANA weren't designed for large-scale document handling — but your document store didn't get smaller.
Millions of documents, and the APIs don't keep up
Your DMS has grown over years — millions of document info records, terabytes of files across Content Servers. The modern S/4HANA interfaces choke on the volume that SAP Engineering Control Center handles without issues.
File access gets slower the more distributed you are
Every file download goes through the central SAP host instead of the nearest Content Server. The more locations you have, the worse it gets.
Engineering systems and SAP don't talk
External systems need to sync documents with SAP DMS, but standard integration middleware doesn't handle both metadata and files at volume.
DMS migration is a transformation project
Moving documents between SAP systems means selective extraction, format transformations, duplicate detection, and restructuring.
Tooling built for real DMS scale
Purpose-built from years of working with large document stores.
Fast document access from any location
Direct file access from Content Servers, no detour through SAP — exposed as a standard HTTP API your applications can use.
Reliable document sync with external systems
Bidirectional sync between SAP DMS and engineering systems — metadata, files, versions, status changes — handled as a continuous workflow.
From access to sync to migration
HTTP API, .NET library, engineering system sync, controlled migration — a complete toolchain, not isolated point solutions.
RFC handles it — but your new applications can't use RFC
SAP Engineering Control Center accesses Content Servers directly via RFC — no bottleneck, even with large files across distributed locations. But Fiori and OData route every file through the SAP host. If you're building modern web applications or integrations, you're stuck with the slow path. Our tooling uses RFC underneath and exposes it as HTTP, so your applications get the same efficient access pattern without needing RFC client libraries.
Engineering companies need documents flowing
When external systems need to sync documents with SAP DMS — status changes, new versions, metadata updates, and the actual files — you can't just route this through CPI. Standard integration middleware isn't designed for large file blobs. You need something that handles metadata and files separately, understands document lifecycle, and moves terabytes reliably. That's what DMSHub was built for.
The DMS toolchain
Purpose-built for SAP Document Management — from API access to migration.
dms-connector HTTP
HTTP proxy for SAP DMS documents — uses RFC underneath for direct Content Server file access, exposed as OData with TUS chunked upload/download.
Give any HTTP client efficient DMS access without SAP-specific libraries or file routing through the SAP host.
sap-dmsclient
.NET library for managing SAP documents programmatically — metadata, versions, status, file operations.
Build custom DMS workflows, automation, and integrations from .NET with full access to document info records and Content Server files.
DMSHub
Async sync engine for documents between SAP DMS and external systems.
Bidirectional document sync with transformation plugins, state tracking, and full lifecycle handling.
dms-migration
Development framework for DMS migration projects — adapted to each project's needs, with the knowledge of previous migrations built in.
Selective extraction, file format transformations, duplicate detection. Evolved through 3 large-scale migration projects.
Related integration domains
Document management connects to the broader SAP integration picture.
DMS migration or integration ahead?
We've done this before — across 3 large-scale projects. Let's talk about your document landscape.