Gmail add-on: filing e-mails into SAP
Not every company runs Outlook. That changes nothing about the problem: in Google Workspace too, transaction correspondence sits in mailboxes rather than at the business object.
The same filing, a different surface
The Gmail version of the CaRD Mail Add-In appears as a side panel in Gmail. The user opens a message, picks the SAP object and files — the message and its attachments land at the business object and are visible there to everyone who opens it in SAP. In the browser just as in the Gmail app on mobile.
Important for the decision: the same service sits behind it as behind the Outlook variant. Filing into SAP runs through the same released SAP standard service, the same profiles determine the permitted object types, and the same configuration applies to both front ends. A company running both worlds therefore needs no second SAP connection and no second operations team — one service, two surfaces.
The differences lie where the platforms differ: Google prescribes its own card layout for add-ons, which leaves less design freedom than a free-form interface. The result is deliberately reduced — pick the object, check the preview, file. In daily use that is an advantage rather than a limitation.
Provisioning happens in your own Google Workspace account, so approval and assignment to users stay with you. The SAP credentials, too, live in the service you operate — not in the user’s browser. More depth: scannen-und-archivieren.de.
At a glance
- Side panel in Gmail, in the browser and on mobile
- File a message with its attachments at the SAP business object
- The same service and SAP connection as the Outlook version
- Filing through a released SAP standard service
- Provisioning in your own Google Workspace account
- SAP credentials stay in the service you operate
Why this matters
The filing weakness does not depend on the mail client.
- Transaction correspondence in a mailbox leaves with the mailbox
- People looking for an agreement ask colleagues instead of the system
- Forwarded messages create copies with no owner
- A mailbox is not evidence in an audit
- Two mail worlds must not mean two SAP connections
What the user does
Three steps, no training.
- Open the message, open the side panel
- Pick the object or accept the suggestion
- File — with or without attachments
- Confirmation with the SAP identifier created
- Done; the message stays in the mailbox where it is
One service for both worlds
The actual reason this adds up.
- A shared service for Gmail and Outlook
- One SAP connection, one configuration, one set of operations
- Profiles determine the permitted object types for both
- Changes take effect on both surfaces
- Filing from Windows Explorer uses the same service too
Operations and responsibilities
Who keeps hold of what.
- Provisioning in your own Google Workspace account
- Approval and user assignment stay with you
- The service runs in your data centre or your cloud
- SAP credentials live in the service, not with the user
- We set it up and hand it over to your operations team
Boundaries
What this variant does not do.
- Google Workspace is the prerequisite
- Private Gmail accounts are not the target of the solution
- Google’s card layout prescribes the presentation
- For Outlook there is a dedicated version — not the same file
- For files from a library: SharePoint add-in
Introduction
What has to happen until the button is there.
- On the SAP side: service activation and authorisations
- Set up the service and connect it to your SAP system
- Define profiles for the relevant object types
- Provision and assign the add-on in your own Workspace account
- A short briefing — operation is three steps
Frequently asked questions
Is this a separate solution or the same one as for Outlook?
The surface is a separate one, because Google prescribes its own add-on technology. The service behind it is the same: the same SAP connection, the same profiles, the same configuration. For operations that means one connection instead of two — the essential difference from procuring two separate tools.
Does it work on mobile?
Yes, in the Gmail app on mobile devices as well as in the browser. Google’s add-on technology renders the same card on both, so an order confirmation that arrives while you are out can land at the right object straight away.
Does anything have to be developed in SAP?
No. Filing uses a released SAP standard service — no modification, no custom program in the core system. What has to be set up is service activation or the communication scenario, plus the authorisations.
Who provisions the add-on?
You do, in your own company’s Google Workspace account. That keeps approval and user assignment in your hands and avoids any dependency on publication by a third party. We supply the package and the instructions and accompany the setup.
What about private Gmail accounts?
They are not the target of the solution. Filing into SAP presupposes a managed environment — both because of provisioning and assignment and because business correspondence belongs in a managed account.
Can we run Outlook and Gmail in parallel?
Yes, and that is exactly what the shared service is for. Both surfaces talk to the same service and file to the same place. To your users it looks like two tools; to your operations team it is one.
Does this match your project?
Talk directly to our consultants — no detours.