Audit-proof archiving for SAP

If only SAP archives and the existing landscape should stay untouched, ArchiveLink is the most direct route: it replaces the content server without changing your SAP processes. If non-SAP applications should reach the same archive, or if you want to keep interface freedom, CMIS is the better choice. The decision can differ per repository.

It can be — provided it is configured correctly. Azure immutable blobs, AWS S3 Object Lock and SharePoint retention policies deliver the immutable storage; combined with defined retention periods, legal hold and an audit trail, that forms the technical basis for compliant record keeping. The final assessment always also depends on your own procedures and process documentation — we bring the technical side, the organisational side we agree with you.

Yes. Content resides in your own storage account, your Microsoft 365 tenant or your data centre – you choose region and provider. The connector itself stores no document content.

That depends on document volume and history. In systems that have grown over years, the combination of document offloading and SARA data archiving regularly accounts for a substantial share of the database. We determine the potential up front from your table and document statistics, before you decide.

Four things: it tags and classifies incoming documents automatically, so metadata exists where previously there was only a file. It enables natural-language search — you describe what you are looking for instead of knowing the exact field value. It finds documents similar to a given case. And it supports processing: summaries, detection of duplicates and anomalies across large inventories. We developed this ourselves and support it in operation.

No, and that is deliberate. The AI functions are opt-in; classic rule-based search across metadata, CMISQL and full text remains fully intact and unchanged. If you do not need it, you simply do not switch it on.

That is defined together up front. Operation is possible on-premise or in a sovereign EU cloud, and which content a model gets to see at all is part of the concept — with archive inventories that is regularly the most important point. Automatically assigned keywords are treated as a reviewable suggestion, not as established truth.

Yes – that is exactly why we decouple connection and storage. Moving from one backend to another is configuration plus migration of the inventory, not a new SAP project.

Yes. The connection uses the SAP standard interfaces, available in every deployment model – from ECC through on-premise S/4HANA to RISE, private and public cloud. Under RISE and in the public cloud the route runs through the SAP BTP Document Management Service, behind which the connector sits as an external CMIS repository.

No. It is the same connector for all four backends – Microsoft Azure Blob Storage, Microsoft SharePoint Online, AWS S3 (and S3-compatible storage) and STACKIT. The storage target is a matter of configuration, not product choice; one installation can serve several repositories in parallel, including different backends.

Yes, and that is one of the main reasons for CMIS. Because it is an open OASIS standard, any CMIS-capable application can use the same repository – Apache Chemistry/OpenCMIS clients, ECM and DMS systems or your own line-of-business applications. SAP is the most common use case, but not a prerequisite.