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.

Native Storage Extension (NSE): HANA NSE allows organisations to designate specific data as "warm," moving it from expensive in-memory storage to disk-based storage within HANA. This provides a middle tier between fully active data and archived data, reducing memory consumption without removing data from the database entirely.

Multi-temperature data management: Building on NSE, S/4HANA supports a tiered approach to data storage: hot (in-memory, frequently accessed), warm (disk-based within HANA, occasionally accessed), and cold (archived to external storage, rarely accessed). This tiered model was not natively available in ECC and represents a significant evolution in S/4HANA data archiving strategy.

Enhanced ILM capabilities: SAP Information Lifecycle Management features have been extended in S/4HANA to support more sophisticated retention management, automated policy enforcement, and integration with GDPR compliance requirements. Organisations already using ILM in ECC will find expanded functionality, whilst those new to ILM have a more mature starting point for archiving in S/4HANA.

What organisations must change

Given these differences, organisations moving from ECC to S/4HANA should take the following steps to ensure effective S/4HANA data archiving:

1. Reassess archiving scope and objects. Do not carry forward ECC archiving configurations without reviewing their relevance in S/4HANA's simplified data model.
2. Evaluate NSE opportunities. Identify data sets that are accessed infrequently but do not yet warrant full archiving, and consider moving them to warm storage through HANA NSE.
3. Update retention policies. Align data retention rules with S/4HANA's enhanced ILM capabilities and current regulatory requirements.
4. Review HANA database management practices. Establish monitoring for memory consumption, data growth trends, and archiving effectiveness to maintain ongoing control.
5. Train archiving teams. Ensure that staff responsible for data archiving understand the differences between ECC vs S/4HANA archiving and can operate effectively in the new environment.

Failing to adapt archiving strategies can lead to significant cost overruns and performance issues. Organisations that achieved lean databases in ECC will find those gains eroded if their approach is not updated for S/4HANA's different architecture and data structures.

Conclusion

S/4HANA data archiving is not simply a continuation of what organisations did in ECC. The in-memory architecture, simplified data models, and new capabilities like NSE and enhanced ILM create a fundamentally different landscape for HANA database management. Organisations that recognise these differences and adapt their strategies accordingly will maintain better control over costs, performance, and compliance. Those that attempt to replicate their ECC approach unchanged risk escalating expenses and diminished system performance. The organisations that approach archiving in S/4HANA with proper planning and expert guidance will be best positioned to unlock the full benefits that the platform promises.

Teams that want a structured way to run this reassessment can use TJC Group's Archiving Sessions Cockpit (ASC), which plans, schedules and documents SAP archiving sessions from one place, in ECC before the move and in S/4HANA after it.

Frequently asked questions

Can I use the same archiving objects in S/4HANA that I used in ECC?