If your company falls into this camp, this article will explain the difference between archiving and ILM and, importantly, why it matters.
What is SAP ILM?
Data archiving is one, albeit very important, aspect of data management. The rationale behind archiving is primarily cost related and it deals with reducing data volumes. ILM goes well beyond archiving and tries to achieve a good balance between TCO, risk, and legal compliance. To be able to implement an ILM strategy, you will need a good data management strategy as a basis. In addition to managing data volumes, ILM also manages data retention requirements, including such things as the final destruction of information.
Although ILM is concerned with data, much of the activity around ILM happens outside of the IT system. Its effectiveness is culturally driven, governed by the levels of communication between the different departments in your organization. ILM cannot work in isolation. It needs to be supported by relevant stakeholders, using suitable products and tools to address the management of structured and unstructured data, plus data from live and legacy systems.
SAP’s definition of ILM hints at this. It explains that ILM is comprised of the policies, processes, practices, and tools needed to align the business value of information with the most appropriate and cost-effective IT infrastructure. This starts from the time information is conceived through to its final disposal.
1. Data archiving versus SAP ILM
Many people get confused about the difference between SAP data archiving and SAP ILM and they believe that one can replace the other. They think that Information Lifecycle Management can replace data archiving, but in fact, archiving is just an important subset of an ILM strategy. If you have an established data archiving strategy in place already, this is a very good basis for SAP ILM as a starting point. From here, you can gradually work your way towards having a fully-fledged ILM process, by beginning to establish data retention rules.
2. Data retention versus data residence
Data retention is another commonly misunderstood term. People often get it confused with data residence. They are totally different, but both are essential for ILM policy making.
Residence relates to the amount of time that data reside on the SAP database before they are archived. Retention is the amount of time data are available to be displayed from an SAP system before being able to be deleted. This is regardless of whether they reside on the SAP database or are retrieved from the archive before they are destroyed.
When managing data in a complex compliance environment, different countries will have different rules regarding the length of time records must be held before deletion or destruction. As part of an automated SAP ILM strategy, different retention and residence periods are set up for different organizational structures, so that the data management is specific to local legislation for that set of data.
3. Data deletion versus data destruction
The final SAP ILM concepts to be explained are deletion and destruction of data. Many people think they are used interchangeably, but in the context of ILM, deletion and destruction are two different concepts.
When we talk about the deletion of data, we mean the physical deletion of a technical unit in the system. When we talk about the final destruction of information, we mean the deletion of all data records and their references, so that certain information or its existence can never be traced again.
Understanding this distinction is very important for GDPR compliance. For example, when data are archived, they are written to the file system and then deleted from the database. They can still be accessed and viewed in their archived state. The final destruction of this information would mean deleting the archive file, all references to it, and copies of it in the system, including change documents and related messages. This relates to the right to be forgotten. An ILM strategy will help your company to remain compliant with GDPR.
In addition to ensuring GDPR compliance, an SAP ILM strategy offers many other benefits. It makes the finance team happy by meeting financial compliance and audit requirements. It makes the IT team happy by reducing system complexity, because less resources are needed to manage the IT environment. And it makes the sustainability or CSR manager happy, because your company will use less energy year-on-year.
Data archiving is an important part of ILM, but it is just one element. Using ILM to maintain control of the TCO of your SAP environment is what every company should be striving for – in addition to archiving. Implementing an ongoing ILM strategy early in the process, especially if you are considering a migration to S/4 Hana, will minimize migration costs, control future data growth, and ensure ongoing compliance.