{"id":96233,"date":"2019-08-22T11:53:36","date_gmt":"2019-08-22T09:53:36","guid":{"rendered":"https:\/\/easy-software.com\/?p=96233"},"modified":"2025-03-28T15:21:23","modified_gmt":"2025-03-28T14:21:23","slug":"s-4hana-migration-the-missing-link-s-4hana-archiving","status":"publish","type":"post","link":"https:\/\/easy-software.com\/en\/newsroom\/s-4hana-migration-the-missing-link-s-4hana-archiving\/","title":{"rendered":"S\/4HANA\u00ae Migration & the Missing Link: S\/4HANA Archiving"},"content":{"rendered":"
\n
\n
\n
\n\n

Elementary questions about the S\/4HANA migration<\/strong> have now been clarified: Greenfield or brownfield migration, on-premises installation, etc. The road maps to the goal as well as the migration path to it have also been determined. In preparation for a S\/4HANA migration, everything has to be planned carefully and meticulously. How do things stand with your S\/4HANA readiness<\/strong>?<\/p>\n\n\n\n

In this respect, one question is often neglected: What happens to the data from the former product system in S\/4HANA\u00ae<\/em><\/strong>? From experience, we know that the question about which stock of data you would like to migrate<\/strong> to the new S\/4HANA<\/strong>, and which data you would prefer to archive externally, is rarely asked. Many customers have data in their SAP system that has never been archived \u2013 dating from the go-live twenty years ago, for example. Have you already thought about this<\/strong>, or don\u2019t you care about the costs that result from the change over<\/em> to the S\/4HANA migration<\/strong>?<\/p>\n\n\n\n

If the S\/4HANA migration is properly planned, it means cost savings are achieved<\/h2>\n\n\n\n

The core component of the new SAP system is the S\/4HANA<\/strong> in-memory database<\/strong>. Experience has shown that the main memory is one of the more expensive types of memory \u2013 which is, of course, priced in on the basis of gigabyte-based<\/strong> SAP\u00ae licensing<\/strong>. It is naturally clear that in this way, a genuine performance boost<\/strong> in the S\/4HANA system is achieved. It is also clear, however, that from now on, almost every byte counts, or should count, during the S\/4HANA migration. After all, the licenses <\/strong>for S\/4HANA are now gigabyte-based<\/strong>, while in the past, the licenses were independent of volume. As a result, the costs of the S\/4HANA in-memory database<\/strong> are approximately <\/em>three to five times higher than those of a conventional database.<\/p>\n\n\n\n

In the context of the data archiving <\/strong>and document storage<\/strong> in particular, the chances of<\/strong> keeping costs under control and even achieving lower costs<\/strong> through a well-considered strategy for S\/4HANA migration<\/strong> are very good<\/strong>. Of course, data archiving has always been an issue, but it\u2019s becoming more important now!<\/p>\n\n\n\n

In pre-S\/4HANA times<\/strong> (R\/3, for example), storing the SAP document chain in the SAP system, for example, was considered a viable approach. In addition, keeping all the data<\/strong> in the database, starting from when the SAP system first went live, wasn\u2019t unusual either. Therefore, data from up to twenty years ago isn\u2019t uncommon. The advantage was, quite simply, making savings on the added costs posed by an archive system<\/em>. Things are now moving in the opposite direction, and should always be considered before a S\/4HANA migration.<\/p>\n\n\n\n

The solution: S\/4HANA archiving before the migration<\/h2>\n\n\n\n

In the upcoming S\/4HANA system, all the data and documents<\/strong> will be stored in the S4\/HANA database<\/strong> and therefore in the main memory<\/strong>. And that isn\u2019t cheap \u2013 on the contrary. Now is the time to get used to the idea of outsourcing the data and documents from the productive S\/4HANA system<\/strong> to an archive system<\/strong> \u2013 ideally before the S\/4HANA migration.<\/strong> This is all the more important, as the amount of data held by companies is growing exponentially, at least according to the experience of recent years. And this is obviously associated with a cost factor after the migration to S4\/HANA. But more than that: If the planning is excessively restrictive, performance problems in the production system are also possible. At this point, it makes sense to ask yourself which data and documents no longer need to be available in the HANA database. After all: Although access is required to a lot of data, it no longer has to be stored in the HANA database of the production system.<\/p>\n\n\n\n

The advantages of S\/4HANA archiving at a glance<\/h3>\n\n\n\n