Skip to Content

As you already know from my blogs SAP S/4HANA System Conversion – Challenge for your custom code and  SAP S/4HANA System Conversion – Custom code adaptation process the adaptation of custom code is an important milestone on your journey towards SAP S/4HANA.

But do you know that your journey has already started and that you can prepare a lot of things already today in your existing landscape? Why is this so important?

You need at least 1 year to collect the data about your productively used custom code with the SCMON to detect and clean up the unused custom code before the SAP S/4HANA conversion.

In order to minimize the scope of your custom code for the S/4HANA conversion project you should start today to carry out new developments “S/4HANA ready” and educate your developers in the new ABAP technologies like CDS, AMDP, ABAP Development Tools in Eclipse, which become mandatory in SAP S/4HANA.

So what can you do today in your SAP Business Suite landscape to prepare your custom code for SAP S/4HANA journey? This blog offers recommendations and checklists for you what to do.

Learn more: in our SAP TechEd 2017 sessions about Custom Code Adaptation to SAP S/4HANA


YOU SHOULD

   

Collect productive usage and SQL execution data

Switch on SCMON

Switch on SQL Monitor

   

Create new code already SAP S/4HANA ready

Setup remote ATC

Use SAP S/4HANA  ATC checks in your development system

   

Educate your developers to be SAP S/4HANA ready

Gain practical skills in ADT in Eclipse

Get familiar with SAP S/4HANA must-have technologies
(e.g. SQL, CDS, BOPF, OData)


YOU COULD

   

Start to adapt your code in your dev system

Convert to Unicode

Fix SAP HANA ATC findings (e.g. NO ORDER)

Optimize performance critical SQLs found in SQL Monitor

   

Estimate custom code adaptation efforts

Run SAP S/4HANA ATC checks for all custom code


 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply