Data storage – your document data remains in your SAP system
MailCenter is an SAP add-on. It runs entirely in your system: in ABAP, in your client, under your authorizations. Documents, attachments and process data are processed where they are created. There is no intermediate storage with us, no transmission to a service provider and no second database that would have to be kept synchronized.
This also applies to document recognition in incoming invoices. Commercially available solutions transfer incoming invoices to a provider cloud for evaluation. MailCenter does not provide for this: by default, processing remains within your system boundary. If you want to use an external OCR or AI service, it can be connected – the decision is yours, not the product architecture.
What this means in practice:
- No order processing agreement for your document data because no third party processes it
- No additional system operation, no additional interface in the emergency and restart concept
- Archiving via your existing archive via ArchiveLink, not in a third-party system
- Authorizations, logging, and auditability follow your SAP role concept
Even in a RISE landscape, this does not change: The add-on runs in the system stack you have ordered – the data does not leave it.
Clean Core – Expand without changing the SAP standard
MailCenter is delivered in a namespace registered with SAP and does not change any objects of the SAP standard. Extensions run through the designated paths: released APIs, BAdIs and extension points instead of modifications.
For you, this means one thing above all: When changing releases, there is no need to compare modifications. No SPAU or SPDD rework because of our add-on, no customization project before the next upgrade, no maintenance debt that builds up over the years.
Clean Core does not necessarily mean that extensions have to leave the system and run on a platform next to it. It is crucial that the core remains untouched and that only approved interfaces are used. This is exactly how MailCenter is built: in the system, but without interfering with the standard.
Evidence:
- SAP Certified Integration for SAP S/4HANA and SAP ECC, including the ATC exam required in the certification process
- Certified for RISE with SAP
- Delivery in a namespace registered with SAP, no modification of standard objects
- ISO 9001 tested development process, certified by DEKRA