How can an SAP system be decommissioned securely and completely?
By Emanuel Böminghaus, Legacy Systems Expert and Managing Director, AvenDATA
by Emanuel Böminghaus
Legacy Systems Expert and
Managing Director, AvenDATA
Managing Director, AvenDATA
Decommissioning an SAP system is one of the most demanding IT projects in a company’s lifecycle. An SAP system is deeply embedded in operational processes, tax-relevant data flows and technical dependencies. When it needs to be shut down, all data must remain legally compliant and accessible. At the same time, it must be ensured that no technical risks or compliance gaps arise. For this reason, decommissioning an SAP system is always a structured and highly precise undertaking.
Why Decommissioning SAP Systems is so Complex
An SAP system contains data in various technical structures that cannot be captured with a simple export. For legally required retention, the data must remain complete, correct, unaltered and readable in the long term. At the same time, during decommissioning, access rights and security-critical components must be removed. Companies must therefore follow a process that considers all relevant data formats and ensures future auditability.
Which Data must be extracted during SAP System Decommissioning
In SAP systems, information is not only stored in the classic relational database but distributed across different layers, storage locations and archive structures. To ensure data completeness, the following areas must be handled professionally during system decommissioning:
- ADK files from SAP archiving
- Tables and content from the regular SAP database
- GOS documents attached to records or processes
- Documents and objects from the SAP document archive
- Content from cluster tables that require special handling and validation
The combination of these formats clearly shows that decommissioning an SAP system is almost impossible without deep technical expertise. Cluster tables present significant challenges if they are not extracted or interpreted correctly. Their data is stored in complex, compressed structures rather than in clear table rows, which requires specialised processing methods.
The Importance of ADK Files during Decommissioning
ADKs are a central component of SAP data retention. Many companies use SAP archiving for years without realising that ADKs are not just files but structured archives essential for future audits. Without these archives, it is almost impossible to fully reconstruct historical processes. During system decommissioning, ADKs must therefore be reliably extracted, validated and provided in an audit-compliant manner. Any loss or damage to ADKs can cause significant legal risks as they may contain key records or transaction data.
Why the Regular Database is not enough
Many companies assume that decommissioning focuses solely on the relational database. In practice, this is only part of the picture. Tables such as BKPF, BSEG or MARA still contain large portions of historical processes, but without the associated archive data, GOS attachments or document archive structures, the system remains incomplete. Only the combination of these different information sources ensures full compliance for tax authorities, auditors or internal departments.
The Role of GOS Documents in SAP System Decommissioning
GOS documents are often the most underestimated part of an SAP system. They are attached directly to records via the Generic Object Services function and frequently include contracts, correspondence, PDF files and other relevant information objects. These attachments are not stored in the regular database schema but managed through dedicated SAP mechanisms. During decommissioning, they must be fully extracted and clearly assigned to the corresponding records. Missing GOS documents can later lead to gaps in documentation, which is particularly problematic during tax audits.
The SAP Document archive as a Critical Component of the Data Landscape
The SAP document archive stores documents that are not kept in the database but managed via SAP Archive Link procedures. Invoices, delivery notes, purchase orders or HR records are physically located outside the regular SAP instance. For system decommissioning, this means that both logical references and physical files must be cleanly extracted and permanently made readable. Without this step, the archived system remains incomplete.
Special Care with Cluster Tables
Cluster tables represent one of the greatest technical challenges. They are not standard tables but contain compressed data packets that SAP stores internally and unpacks when read. Incorrect handling can damage transaction data or make certain information impossible to reconstruct. During SAP system decommissioning, cluster tables must therefore be processed using specialised extraction logic to ensure both data integrity and long-term readability.
Why a structured System Decommissioning is Essential
SAP system decommissioning does not end with data extraction. At the end of the process, the SAP system and all technical components must be fully and audit-compliantly shut down. This includes dismantling servers, deactivating interfaces, removing old backups and documenting the decommissioning process. Only when all data has been extracted, all archive objects secured and all table structures correctly processed can the system be permanently taken out of operation.
Decommissioning an SAP System requires maximum Precision
Decommissioning an SAP system is more demanding than shutting down other applications. The reason lies in the diversity of data formats and the close interconnection of archive objects, database tables, GOS documents, ADKs and cluster tables. Companies must ensure that all relevant information is complete, audit-compliant and permanently readable. Only in this way can an SAP system be shut down without creating risks or problems during audits.
Planning to archive a legacy system?