SharePoint add-in: from the library into SAP
The CaRD Connector brings SAP documents into SharePoint. This add-in goes the other way — for everything that is created in a library and missing from the SAP transaction.
A button in the document library
The CaRD SAP Filer for SharePoint adds an entry to the command bar of a document library. The user selects one or more files, picks the SAP object in a dialog — purchase order, sales order, supplier, document info record — and files. Afterwards the file hangs at the SAP business object and is visible to anyone who opens the transaction in SAP.
The interesting part is the choice made while filing, because it decides the later order of things. Copy leaves the file in the library and puts a copy into SAP — convenient, but two versions now exist. Reference replaces it with a small reference file pointing at the SAP document: the transaction stays visible in SharePoint while the original exists only once. Move puts the file into the library’s recycle bin after filing — and explicitly only when SAP has actually confirmed the filing.
What comes back is the SAP document identifier, which can be written into a column of the library. That makes it traceable in SharePoint what already exists in SAP, without anybody maintaining a list. If the identifier is missing in an individual case, the column stays empty; the filing itself was still successful.
The principle from the mail add-ins applies here too: the same service sits behind it, the same SAP connection and the same released SAP standard service. Anyone already working with the Outlook add-in gains another surface, not a second connection. Technically it is an extension in the current SharePoint framework — the old add-in model has been retired and is not used.
At a glance
- Button in the command bar of a document library
- File several documents in one operation
- Three filing modes: copy, reference or move
- Moving happens only after confirmed filing in SAP
- SAP document identifier lands in a library column
- The same service as the mail add-ins
Why this matters
What happens when both worlds run side by side.
- Documents are created in Teams and SharePoint, the transaction lives in SAP
- Without a bridge, copying is manual — or does not happen
- Two filing locations mean two versions and two retention questions
- Anyone checking in SAP will not find last week’s version
- When the library is tidied up, whatever never reached SAP disappears
The three filing modes
The decision you make once and then stick to.
- Copy: the file stays in the library, a copy goes to SAP
- Reference: a small reference file replaces the original, the transaction stays visible
- Move: the original goes into the library’s recycle bin
- Moving happens exclusively after confirmed filing
- The mode can be prescribed per library
Feedback into SharePoint
So you can see what is already over there.
- The SAP document identifier is returned
- Written into a column of the library
- Filter and sort by filed or not filed
- No separate list for anybody to maintain
- If the identifier is missing, the column stays empty — the filing stays valid
Technical classification
Why this shape.
- An extension in the current SharePoint framework
- The old SharePoint add-in model has been retired
- Provisioning through your tenant’s app catalogue
- Permissions follow those of the library
- Nothing is changed in the Outlook add-in — a separate deployment of the same service
The reverse of the connector
Two routes that complement each other.
- The CMIS connector brings SAP documents into SharePoint
- This add-in brings SharePoint files into SAP
- Together they make filing end to end
- Where the original lives is your decision per document type
- See also SharePoint & SAP
Status and introduction
Where the product stands, stated plainly.
- The solution is new and fully built
- Role-based access is verified against a test tenant
- A deployment against a productive SAP system is still outstanding
- We are deliberately looking for pilot customers and accompany the roll-out ourselves
- What is proven and what is not, we say openly in conversation
Frequently asked questions
What exactly does the add-in do?
It adds an entry to the command bar of a SharePoint document library. Selected files are assigned to an SAP business object through a dialog and filed there. Afterwards the file hangs at the SAP transaction and is visible to everyone who opens it in SAP.
Does the file stay in SharePoint?
That is your decision per library. With copy it stays where it is. With reference it is replaced by a small reference file pointing at the SAP document — the transaction stays visible in SharePoint while the original exists only once. With move it goes into the library’s recycle bin, and only when SAP has confirmed the filing.
How do we see in SharePoint what is already in SAP?
From the SAP document identifier written back into a column of the library, which you can filter and sort by. Nobody has to keep a parallel list. If SAP returns no identifier in an individual case, the column stays empty — that does not invalidate the filing.
Is this the old SharePoint add-in model?
No. Microsoft has retired that model and it is not used here. The current extension technology is used instead; provisioning runs through your tenant’s app catalogue and permissions follow those of the library.
Do we need a second SAP connection for this?
No. It is the same service as for the mail add-ins, with the same SAP connection and the same profiles. Your users gain another surface, your operations team gains nothing to run.
What is the status of the product?
The solution is new: it is fully built and role-based access is verified against a test tenant, but a deployment against a productive SAP system is still outstanding. We are deliberately looking for pilot customers and accompany the introduction personally. We say openly in conversation what is proven and what is not — an unfounded assurance would serve nobody.
Does this match your project?
Talk directly to our consultants — no detours.