Why is Custom Code Adaptation required for S/4HANA Conversion Project?
ECC users will get confused when they hear of S/4HANA Conversion. SAP S/4HANA is an intelligent ERP built on the intelligent database - SAP HANA. This new-generation ERP is completely detached from the traditional SAP ERP Business Suite (ECC)
The new-generation S/4HANA ERP is so completely detached from the traditional SAP ERP Business Suite (ECC), that SAP termed the process as ‘System Conversion’ and not ‘Upgrade’ for the migration from ECC system .
For years, SAP customers have heavily invested in their custom developments in ECC, CRM, SRM systems. The ECC system might have been highly configured according to their business processes. Hence, they expect the SAP S/4HANA custom ABAP development adaptation during conversion as well. Hence, custom code adaptation is a very significant step in the S/4HANA conversion process.
Table of contents
- S/4HANA Custom Code Check
- Challenges in S/4HANA Custom Code Adaptation
- Simplification Database
- Illustration of a Simplification Item: MATNR length extension
- Planning for Custom Code Adaptation
- Preparation
- Next Steps
S/4HANA Custom Code Check
Before upgrading to SAP S/4HANA, users may assess the calibre of their custom code using a tool offered by SAP. This is an essential step in ensuring a successful update because bespoke code is typically the cause of upgrading issues.
The SAP S/4HANA Custom Code Analysis tool analyses custom code and rates it against a set of best practises. The report it generates can subsequently be used by customers to fix any coding issues.
Before deploying SAP S/4HANA, bugs in custom code should be fixed to avoid upgrading issues and provide a smooth transition to the new system.
Challenges in S/4HANA Custom Code Adaptation
In SAP ECC implementations, modifications and enhancements of any SAP Module can be implemented without any limitations. This was not an issue since the dependencies of those enhancements and modifications are compatible across all ECC versions. However, after converting to S/4HANA, there is a high possibility of getting depreciated since S/4HANA was simplified and in some way those cases may not be compatible.
Simplification Database
-
The simplification database is the repository of all incompatible changes of the SAP code in S/4HANA compared to the ECC as simplification items.
-
Each Simplification Item notifies the changed or removed SAP standard objects and has a dedicated SAP Note against each Simplification Item.
-
The SAP Note gives the detailed information on how the change impacts the S/4HANA functionality and the process of custom code adaptation.
| Simplification Database |
|
|
|
Illustration of a Simplification Item: MATNR length extension
The important simplification item is the MATNR field length extension from 18 to 40 characters. The MATNR Field extension impacts the existing Custom objects to a large extent.
If the custom developed MATNR fields (Material Number) of 18 characters length comes into action with the new MATNR field of 40 characters length in new S/4HANA System, few possible issues may evolve at that time:
- Loss of data when MATNR referred variable in custom programs (since the MATNR is 18 characters length)
- Type Conflicts during parameter passing in ABAP Methods
- Length conflicts at comparison with SAP Standard Field - MATNR
- Length conflicts at concatenation with SAP Standard Field - MATNR
In all these cases you need to adapt your custom material numbers to the new SAP material number type.
Although the maximum length of the database field used to store the material number is now 40 Characters, the way how the material number content is stored in the database field has not been changed compared to SAP Business Suite. This means that for such fields usually no data conversion is needed when converting from SAP Business Suite to SAP S/4HANA, on-premise edition.
Planning for Custom Code Adaptation
The SAP ECC customers are advised to run SCMON (SAP Code Monitor) for at least 1 year to know the productively used custom code so as to find and clean up the unused custom code before S/4HANA Conversion.
In order to minimize the scope of custom code for the S/4HANA conversion project, you should start today to carry out new developments “S/4HANA ready” and educate the developers in the new ABAP technologies like CDS, AMDP, ABAP Development Tools in Eclipse, which becomes mandatory in SAP S/4HANA.
Preparation
SAP S/4HANA system conversion consists basically of two major phases.
Before SAP S/4HANA system conversion
During preparation phase – we recommend to get rid of your old unused custom code (custom code evaluation) and then analyse the custom ABAP code with the Simplification Database and find out which objects need to be changed to get adapted to the SAP HANA and SAP S/4HANA (SAP S/4HANA checks).
After SAP S/4HANA system conversion
During the realization phase – you need to adapt your custom ABAP code to the new SAP S4/HANA software (functional adaptation) and optimize the performance for SAP HANA database (performance tuning).
Custom code scoping is a mandatory task before beginning the S/4HANA migration project. The list of custom objects impacted should be listed based on the levels of impact, usability, velocity, business value and viability in Custom code scoping.
Is that possible to find out the highly important custom objects to be migrated?
NO! If you don’t use any automated tool like KTern. KTern is an all-in-one product suite built for SAP Digital Transformations, which will take minutes to produce you the results of Custom Code scoping by connecting your ECC system remotely. The blend of AI and SAP subject matter experience has developed a Knowledge base called S/4HANApedia to enable this feature.
Next Steps
Curious to learn more about KTern and SAP S/4HANA Conversion? Please do go through our articles and on-demand webinars at your convenience.
To learn even more, do schedule your direct 60 mins express session on KTern along with a demo of the product at Schedule Demo
