The challenge
The challenge
Technical specifications and equipment manuals were stored in SAP, where they were hard to find and only one person could edit a file at a time.
Approach
SAP stored the documents, and working on them was slow
Burckhardt Compression makes reciprocating compressors for industrial and energy applications and runs its business on SAP. Engineers and field staff depended on documents stored in SAP, from technical specifications to equipment manuals and maintenance records.
Getting to those documents was slow. Search needed the exact document number or filing location, and two people could not edit the same document. Editing in Office meant downloading the file and uploading it again after every change, and field staff had no practical way to open documents from a phone.
Two-way synchronization between SAP and SharePoint
We built the integration with Azure Functions and Azure Logic Apps. Functions watch the SAP document library for changes through SAP APIs. Logic Apps move documents in both directions and detect conflicts when the same document changes in both places.
A document created or updated in SAP appears in SharePoint within minutes, and changes made in SharePoint flow back to SAP. Business logic maps SAP document attributes to SharePoint metadata, so each document keeps its business context.
Permissions and governance carried over from SAP
SAP authorization profiles map automatically to SharePoint security groups, so a person sees the same documents in SharePoint as in SAP. Staff sign in once, with their Azure Active Directory account (now Microsoft Entra ID), for both systems.
Each SAP document category has its own SharePoint content type and metadata fields. Retention policies follow corporate governance, and version history records every change. Azure Information Protection guards sensitive documents, and access and changes are logged for audits.
Working on SAP documents in Microsoft 365
Several people can now edit the same Office document at once, which ended the version conflicts that came from emailed copies. SharePoint search indexes document content and metadata, so people search in plain words instead of typing SAP document numbers. Field engineers open equipment manuals on service calls through the SharePoint mobile app.
Piloted with engineering, then rolled out by business unit
In weeks 1 and 2 we assessed how Burckhardt used SAP document management. Together we decided which document types to integrate first, how SAP metadata maps to SharePoint, how often to synchronize and how the security model works. Development and testing ran from week 3 to week 8 and ended with integration tests against an SAP sandbox.
From week 9 to week 11 the engineering department, which works with documents heavily, piloted the integration. Pilot users could reach each document both through SAP and through SharePoint. From week 12 to week 16 we rolled out across all departments, one business unit at a time, with training and support for each.
Inside the implementation
Architecture overview
SAP stays the system of record. An integration layer on Azure watches SAP for document changes and keeps SharePoint libraries in step in both directions, carrying metadata and permissions with each document.
SAP and SharePoint document flow
- 01
SAP document management
Documents are created and updated in SAP as before.
- SAP
- SAP APIs
- 02
Change capture
Functions notice new and changed documents in SAP.
- Azure Functions
- Metadata mapping
- 03
Two-way synchronization
Documents move in both directions, with conflict detection.
- Azure Logic Apps
- Conflict detection
- Permission mapping
- 04
SharePoint
People find, open and co-author the documents in Microsoft 365.
- Content types
- Retention policies
- Version history
- SharePoint mobile app
Permissions follow SAP
SAP authorization profiles map to SharePoint security groups, and staff sign in once with Azure Active Directory.
Protection and audit
Azure Information Protection guards sensitive documents, and access and changes are logged.
Key design decisions
Keep SAP as the system of record
SharePoint gives people a better way to work on the documents, and every change flows back to SAP, so SAP keeps its role.
Map metadata before moving documents
SAP document attributes become SharePoint metadata and content types, so a document keeps its business context in SharePoint.
Write conflict rules down
When the same document changes in SAP and in SharePoint, agreed rules decide the outcome, so nothing is lost or overwritten by accident.
How the workflow fits together
A document changes in SAP
Azure Functions pick up the change through SAP APIs.
Metadata and permissions are mapped
SAP attributes become SharePoint metadata, and SAP authorization profiles become SharePoint groups.
The document appears in SharePoint
Logic Apps place it in the right library within minutes.
Edits flow back
Changes made in SharePoint return to SAP, with conflict detection on both sides.
Questions for a similar implementation
Use these review points when you assess this architecture for your own environment.
- Which SAP document types should move first, and which can wait?
- How do your SAP authorization profiles map to SharePoint groups?
- How often does each document type need to synchronize?
Results
The outcome
In the engineering pilot, the time to find documents fell by 75%. After the rollout, staff across all departments open and co-author SAP documents in SharePoint, and SAP remains the system of record.
Stack
Technology used
- SAP
- SharePoint
- Azure Functions
- Azure Logic Apps
- Azure Active Directory
- Azure Information Protection
First published on our blog on 12 May 2025.