How data archiving changes when you move from ECC to S/4HANA

Introduction

Organisations that have managed data archiving successfully in SAP ECC environments often assume that the same approach will work seamlessly in S/4HANA. This assumption can prove costly. The architectural changes introduced in S/4HANA, from the in-memory HANA database to simplified data models and restructured tables, fundamentally alter how data archiving operates and what strategies are effective.

Understanding the differences between ECC vs S/4HANA archiving is not merely an academic exercise; it has direct implications for system costs, performance, and compliance. This article explores the key changes, their implications for HANA database management, and what organisations must do to implement effective archiving in S/4HANA.

The architectural shift: from disk to in-memory

The most significant change underpinning S/4HANA data archiving is the shift from a disk-based database to SAP HANA's in-memory architecture. In ECC, data resided on disk, and the cost of storing additional data, whilst not negligible, scaled relatively predictably. In S/4HANA, all active data is loaded into memory, making every additional gigabyte directly and significantly more expensive.

A common guideline suggests that approximately 2TB of HANA memory is required for every 1TB of active data, illustrating the direct financial impact of carrying unnecessary data in the new environment. This change elevates the importance of HANA database management and makes data archiving not merely a best practice but a financial imperative. Organisations that neglect archiving in S/4HANA face rapidly escalating memory and licensing costs that far exceed what they experienced in ECC.

Simplified data models and the Universal Journal

S/4HANA introduced significant changes to its data model that directly affect archiving approaches. The most notable is the Universal Journal (table ACDOCA), which consolidates financial data from multiple tables in ECC into a single table. In ECC, financial accounting, controlling, and asset accounting data existed in separate tables with distinct archiving objects. In S/4HANA, much of this data converges into ACDOCA.

This consolidation changes the archiving landscape considerably. Organisations cannot simply replicate their ECC archiving object selections when planning archiving in S/4HANA. The archiving objects available, the data they cover, and the interdependencies between them have all changed. A thorough reassessment of archiving scope is essential to ensure that the approach reflects S/4HANA's restructured data model.

Similarly, other areas of S/4HANA have undergone data model simplification. Material management, sales, and logistics tables have been restructured, meaning that archiving strategies developed for ECC may target tables or objects that no longer exist or function differently. These changes make the distinction between ECC vs S/4HANA archiving a critical consideration during any migration project.

New tools and capabilities for archiving in S/4HANA

The shift to S/4HANA also introduces new capabilities that were not available in ECC, creating opportunities for more effective HANA database management.