Rightsizing for SAP S/4HANA
- Problem description
SAP systems are growing. The storage capacity has to be expanded and computing resources increased after just only a short time. And time and time again, so that system queries from business users do not noticeably have a negative impact on performance. Therefore, it may even be necessary to reorder and purchase licenses. Operation and maintenance are becoming more and more costly. Updates and upgrades also take more and more time and soon a weekend is not long enough anymore.
A new challenge is also added for existing SAP customers. As generally their existing systems do not run on the new SAP HANA database yet but on a DBMS system from Oracle or Microsoft, etc. In future, however, they will have to switch to the new SAP database technology. They will therefore have to purchase licenses for SAP HANA, which are also dependent on volume. Existing SAP customers therefore have a strong interest in reducing their databases before they migrate to the HANA database. Such a reduction is also the perfect preparation for the switch to SAP S/4HANA.
If existing SAP customers want to reduce the volume of their ERP database from 10 TB to half, for example, they need ways and means to extract and archive the data and documents they no longer need. However, unexpected difficulties often arise while implementing this project. SAP systems in particular have a large number of complex dependencies, which generally prevent a reduction in storage volume of 50 percent or more.
One alternative is to place a new SAP system with HANA as the data pool next to the inventory system and continue working with it, while the legacy system continues to operate, albeit with fewer resources. After all, this is the only way to guarantee the legally prescribed access to data and documents.
From a strategic point of view, both classic approaches fall short. Either the data volume in the live system cannot be reduced to the desired extent or the number of systems increases. In any case, both the personnel and financial effort increases disproportionately though.
The solution really appropriate to this challenge is to extract all data and documents from the SAP inventory system before the entries in the data pool that are no longer required for live operation can be erased.
It is crucial that the extracted information is stored together with its business context on a neutral, central and modern platform. This allows them to be searched independently of the original system and displayed in the Web browser or ideally in the new SAP system’s interface. To comply with legal requirements, this kind of platform must also be able to manage the entire life cycle of historical data and documents up to their controlled and final erasure. It must therefore also contain functionalities for retention management.
The Java-based information management platform JiVS IMP is just such a platform. It is certified by auditors, so that the data and documents can be stored permanently without the original system and still meet all legal requirements.
This makes it possible to reduce the volume of data in the SAP inventory system from a business, non-technical point of view. The volume can be reduced by up to 95 percent as a result. The data and documents that remain on the live system can be edited and changed in future without the risk of problems with internal auditing or external auditors. After all, they are all stored in JiVS IMP in an audit-proof manner and are still available in read mode.
JiVS IMP acts as a central collection point and provisioning area or “data staging area” for company information in the course of rightsizing projects for SAP S/4HANA, among others. Analyzes of the information pool’s reduction potential can be created and the filter rules for reduction can be defined with this. Once the project is complete, JiVS IMP provides legally compliant access to information independent of the device, time and location and subjects the legacy information pool to end-to-end retention management for the seamless management of the historical data and documents’ life cycle. In addition, JiVS IMP’s business object-focused approach provides the option of integrating the platform into the SAP S/4HANA or SAP C/4HANA target environments.
Customers can implement JiVS IMP both in their own data center or use offers from the public cloud for implementation. Supported environments include the Google Cloud Platform, Amazon Web Services and Microsoft Azure. At the same time, customers can choose from a variety of popular database management systems (DBMS), from IBM Db2 to Oracle Database and Microsoft SQL Server to SAP IQ.
- Customer benefits
JiVS IMP wholeheartedly plays its strategic role during the operational phase as an integral part of the target architecture. With JiVS IMP, many problems typical for existing SAP environments can be avoided right from the start in the SAP S/4HANA world. This includes in particular the continuously rising need for resources. As a result, data and documents that are no longer needed in day-to-day business after a certain point in time can be regularly historized using JiVS IMP. SAP S/4HANA therefore remains permanently lean, which reduces operating costs accordingly over time.
The greatest benefit of this approach for existing SAP customers is that their systems remain permanently lean and performant. As a result, they support the agility of the company as a whole. JiVS IMP also provides the ideal prerequisite for migration to SAP S/4HANA at the same time.
JiVS IMP costs up to 80 percent less to operate than live systems with comparable data volumes. With the help of the platform, the rightsizing of existing SAP customers can be made part of the IT work routine and general risk management.
- Price and availability
JiVS IMP is available now. The range of functions and price are determined specifically for the project.