In part 1, we covered the “Preparation Activities” in the Prepare Phase and the relevant Technical and Application activities that are required to be completed during the business uptime. In part 2, we will dive into the Realize Phase with “Follow-On Activities” but focus on the activities following the completion of the Software Update Manager (SUM). Part 2 – Follow-On Activities (Realize Phase)
Now that you have completed the “Preparation Activities” in the Prepare Phase, application activities in the Business Downtime Phase and the system conversion with Software Update Manager (SUM) in the Realize Phase, the system is still in Business Downtime. To complete the Business Downtime, we will focus on part 2 of the blog to identify and share tips on completing the “Follow-On Activities” in the Realize Phase. Below is a table to illustrate the Follow-On activities required from both technical and application teams during a system conversion project.
|Technical Business Downtime||Application Business Uptime|
|Run Installation Check
Run the SAP Initial Consistency Check (transaction SICK).
These application specific activities can run in parallel and should be covered by experienced application consultants for the respective area:
Sales & Distribution
Environment, Health and Safety
Finance – Preparation and Migration of Customizing
Accounting – from Classic Asset Accounting
Finance – Migration
Activities after Migration
Convert to SAP Cash Management – SAP Integrated Business Planning
|Backup Hana DB
Use the SAP HANA Studio or your preferred backup solution to take a complete backup of the HANA database.
|Check and Update Profile Parameters/ User Environment
During the conversion, the old instance profiles are merged with new instance profiles. For this reason, obsolete profile parameters can remain in the new instance profiles.
|Check the Converted System
To evaluate the migration, run a migration check 1785060.
|Define Database Actions
After the conversion to SAP S/4HANA and migration to the SAP HANA database, the scheduled database jobs are no longer relevant because they are database-specific. For this reason, these jobs have to be deleted. New jobs for the SAP HANA database are available and have to be scheduled, too.
|Check Self-Defined External Commands
During the conversion, the content of the kernel directory is completely deleted before the new SAP kernel is imported. In case additional programs had been installed into this directory, they have to be installed again. In case the additional programs are moved to a new location, the configuration of the external commands needs to be adapted.
|Adjust Repository Objects
If you made modifications to programs, screens or interfaces (GUIs), you must adjust them with transaction SPAU.
|Adjust the User and Role Administration
After the conversion, you must make adjustments to the user and role administration. They depend on whether you have already used the profile generator in the source release.
|Check for Unused Indexes
After the conversion, there might be unused indexes.
|Configure Cryptographic Software
For cryptographic functions, for example, digital signatures and SSL, the SAP Cryptographic Library is required. If SAP Cryptographic Library is still not installed on the system, you can do it in this step. For more information, see the SAP Note 597059 License conditions of SAP Cryptographic Library.
|Execute SAP Load Generator
The ABAP loads are platform-dependent programs that are generated during runtime and stored in database tables. They must be generated again after the conversion to SAP S/4HANA.
|Adapting System to SAP S/4HANA
After the conversion to SAP S/4HANA several features and functions in many areas are modified or new which makes an adaptation of the system mandatory. This process can be very time consuming and cannot be handled in the restricted downtime of a productive system conversion.The following areas should be considered in the system adaptation:
SAP S/4HANA RIG