S/4 HANA System Conversion Process Overview

In my previous posts, I had explained about the features of S/4 HANA and the delta from SAP

Below is the S/4 HANA System Conversion Sequence as mentioned in the System Conversion
Guide.

The whole process of system conversion can be broken down into the following sub phases:

Prepare Phase
t1 – System Requirements
In this phase technical evaluation of the systems is done like for eg:
System Design, Architecture and Sizing, new hardware resources required?

Dependencies on SAP NetWeaver Gateway / Front-End servers?

t2 – Maintenance Planner
In this phase, there are some additional preparatory activities are done like for eg:

S/4HANA source system should be connected to SAP Solution Manager

System data in SAP Service Marketplace are up to date

3rd Party Vendor Add-Ons are evaluated and checked if they are compatible with S/4 HANA for
the respective version. There could be few roadblocks if not compatible and if necessary, same
has to be removed of possible.

t3 – Prechecks
This phase would involve the functional team to do the functional conversion activities. The
report R_S4_PRE_TRANSITION_CHECKS is to be run to check if the prerequisites are met from
the application standpoint. You cannot proceed with the conversion process if there are any
errors.

Following are some key activities which need to be done for the report to show no errors:

 Convert Customers, Vendors to BP. Important note for this process would be 2265093 –
S4TWL – Business Partner Approach. The note has details about how to set up and use
CVI for the business partner conversion. The steps in the Business Partner Guide can be
followed to complete this process. Report CVI_UPGRADE_CHECK_RESOLVE can be
very useful during this phase.
 Activate Material Ledger. The note 2352383 can be useful for this.
 Material Field Length Extension. The note 2267140 can be useful here.
 Pricing Data Model Changes – Use the cookbook in the note 2220005 to take care of the
custom code for pricing.
 Inventory Management Data Model simplification – The note 2206980 can be used as
reference to complete this activity. There is a cookbook as well which comes with the
note which can be useful for this activity.
 Run the program FINS_MIG_PRECHECK_CUST_SETTNGS for consistency check in
ledger, company code and controlling area.

t4 – Custom Code Remediation

This phase is an extension of t3. If there are errors in the report
R_S4_PRE_TRANSITION_CHECKS because of custom code conflicts, you will not be able to
proceed to the next step. Code Inspector can be used to identify the conflicts and remediated.
Potential conflict areas could be Material Number Field length, Pricing, key tables like BKPF,
BSEG, MKP, MSEG table enhancement, document flow and document status tables usage,
CI_COBL, etc.

Once the report R_S4_PRE_TRANSITION_CHECKS indicates that all the errors have been
corrected. You can then proceed to the next step.

Realize Phase
t5 – Software Update Manager (SUM)
This is the technical conversion phase. Follow the guided procedure of the SUM Phases. The
below are the steps in SUM as per the conversion guide.

1. Database migration (optional). If your source system is not yet running on the SAP HANA
database, use the database migration option (DMO) of the Software Update Manager to
migrate your database to SAP HANA during the conversion.
2. Installation of the SAP S/4HANA software.
3. Conversion of your data into the new data structure used by SAP S/4HANA (this is the
automated part of the data migration).

t6 – Cross Application Follow up activities

In this phase, you need to do the necessary steps to make the S/4 HANA system ready. Some of
the key activities are as below:

 SPAU/SPDD checks
 Configure new output management
  Run the reports RASUVAR1 and RASUVAR2 for variants updates
 Run PRC_MIG_POST_PROCESSING for pricing updates
 Activation of Webdynpro services (SICF)
 Run the Finance Migration activities. Note 2332030 can be useful for this.
 Configure and Migrate credit management. Note 2270544 can be used as reference for
this.
 Carry out pricing related updates. Notes 2267308 and 2220005can be used to check for
technical changes needed
 If you are using rebates, follow the notes 2267308 and 2226380.
 Migrate to Material Ledger
 Activate necessary business functions and implement the necessary notes as mentioned
in the note 2389807.

This would conclude the conversion activities and the system can be released for testing after a
sanity test if there are no issue