Home › Filing from Windows Explorer
Not every document arrives by mail. Drawings, contracts, inspection reports and scanned documents sit on a drive and stay there, because the route into SAP is too cumbersome. This tool turns it into a right click — “Send to → File in SAP”, validated and correctly named.
There is a solution for emails, one for invoices, one for paper. What remains is the largest and least conspicuous group: everything that already exists as a file and therefore stays on the drive “for now”.
Every department has one. It grows, it is never tidied up, and when it matters only one person knows where anything is. None of it shows up in SAP.
Open SAP, find the process, find the attachment list, upload — for a single drawing. Nobody does that willingly, and so hardly anybody does it.
A record on a drive is not a record on the document. Whatever hangs on the SAP object can be found by anyone — whatever sits beside it has to be remembered by somebody first.
Click a file in Explorer — or several at once. A drawing, a contract, an inspection report, a scanned invoice: anything sitting on a drive.
Right click, “Send to”, “File in SAP”. No extra window to find, no program to start, no upload to some intermediate portal.
A small window asks for the profile and the business object and validates the number against your SAP system. What does not exist there is not filed.
The file hangs in the attachment list on the SAP object — under its proper name and with the right extension, so SAP can hand it back out later.
It is the retrieval key. If a file arrives in the archive with the wrong extension, it cannot be opened cleanly later — and that often only becomes apparent months afterwards, when somebody actually needs the document.
This is exactly where many tools take the easy way out: on upload, standard libraries set an unspecific file type, and every filing turns into an identically named, unusable file. This tool determines the type explicitly and refuses the unspecific case instead of waving it through.
No shell extension, no registry, no admin rights — just a shortcut in the user profile.
For international sites there is nothing to set up — everyone sees their own language.
Through the Windows account the user is already signed in to.
Who sees which business objects is controlled centrally — not at the workstation.
SAP S/4HANA Public Cloud and private cloud as well as RISE with SAP and S/4HANA on-premise. It builds on the released SAP standard attachment service, which exists in every deployment model — so no modification and no custom program in the core system is needed.
A small Windows application and a shortcut in the user’s “Send to” folder. No shell extension, no registry changes, no admin rights. Setup happens per user and can be removed just as easily.
All of them. PDF, Office files, images, CAD drawings, emails saved as files — whatever sits on the drive can go to SAP. What matters is that the correct extension survives: in SAP the file name is the retrieval key, and a file that arrives there mislabelled cannot be opened cleanly later. That is exactly what the tool watches.
No. Every Windows user has known “Send to” for years. That is the real trick of this solution: it does not introduce a new way of working, it attaches itself to one everybody already uses.
Yes. Select several files in Explorer and send them off together — they are attached to the same business object in one pass. For a case with a quotation, a drawing and an inspection report that is a single action instead of three.
With the Windows account they are already signed in to — usually without a further sign-in prompt. Permissions are controlled centrally through roles; without an assignment nothing happens.
In 23 languages. For international sites there is nothing to set up — every user sees the interface in their own language.
We quote per customer — by number of users and the business objects you need. Request an individual quote; we are happy to show you a no-obligation live demo first.
Tell us which documents currently stay on your drives and which SAP objects they ought to hang on.
