SAP S/4HANA Conversion

SAP S/4HANA Conversion: A Guide to Executing and Simplifying Your Conversion by Ravi Surya Subrahmanyam

Download - SAP S/4HANA Conversion: A Guide to Executing and Simplifying Your Conversion by Ravi Surya Subrahmanyam - PDF, ePUB 

As per the SAP announcement, mainstream maintenance of SAP Business Suite 7 applications will end by 2027. Optional extended maintenance will end by 2030. Consequently, SAP ECC customers are preparing for a digital transformation. They understand the importance of moving to SAP S/4HANA. Many SAP ECC customers have attended the SAP S/4HANA movement program to explore different aspects and to finalize the process of moving to SAP S/4HANA.


Every SAP customer has a unique set of challenges and goals. They must consider these challenges during their plan to move to SAP S/4HANA. Experienced SAP S/4HANA conversion architects can help SAP ECC customers design their move to SAP S/4HANA. S/4HANA conversion architects can define the best fit strategy for customers after analyzing their systems. The SAP S/4HANA system conversion path allows customers to convert their existing ECC systems to SAP S/4HANA.


SAP S/4HANA conversion is a complete, technical, in-place conversion of current SAP ECC systems to SAP S/4HANA. Without re-implementation, customers can change their SAP ECC system to an SAP S/4HANA system. The conversion process migrates the ERP data model into the SAP S/4HANA data model. It changes the SAP ECC functional core to an SAP S/4HANA application core. As of now, it is not mandatory to migrate SAP GUI to SAP Fiori apps. Customers will be able to do this selectively in a later step.


During conversion, the special tables will be converted to transparent tables. The standard code will be automatically adjusted to switch from calling the special tables to calling the transparent tables. Secondary indexes will be dropped during the conversion process. Indexes are usually not needed in SAP HANA. If any of the existing Z code refers to them, you must adjust that code to be able to work on SAP S/4HANA. SAP Clients have to make their own checks and adjust their code where necessary. If existing custom codes refer to a standard table that has been removed, SAP provides views for those obsolete tables. This means the existing Z code will still work and will just use the view.


There are SAP tools that ca accelerate and automate the code review to make sure nothing is lost. The ABAP Code Inspector will help programmers choose the type of checks they want to do.

For example:

• You can use it to find pool and cluster tables.

• You can ask the program to show where you used SELECT *.

• You can use it to identify bottlenecks.

You can also identify code that is rarely used or not completely used (i.e., dead code).


The SAP Readiness Check helps SAP ECC customers plan their transition to SAP S/4HANA and provides them with an overview of the current system’s readiness to convert as SAP S/4HANA. It also provides consultants with all the information needed to understand the system to be converted. This tool also provides several aspects of the conversion project.


20
Views
0
Likes

Licenses:

  • CC BY-NC-SA 3.0 PH
  • The author's reference is not required

Share on networks

eBooks Details:

  • Английский / English Book Language
  • April 28, 2022 Publication date
  • 392 pages Pages
  • PDF | ePUB eBook Format
  • 27.6 Mb | 43.7 Mb Size
  • Computers & Technology / Business & Money Category

Comments (0) Add

Кликните на изображение чтобы обновить код, если он неразборчив
No comments yet. Your comment will be the first!