“Taking dead code with you involves work,” says Hois, who advises eliminating code that is no longer needed. This isn’t absolutely necessary, but it’s a good idea to take a look at the code in your system and rid it of excessive bloat. Clean up your custom code and data management (recommended) “It is possible to go from here to EHP 7, which is the latest enhancement package at the moment, without converting to Unicode,” explains Rudolf Hois, vice president and head of SAP S/4HANA development, “but because most customers combine this step with their database migration to SAP HANA, it makes sense to convert first, as a preliminary measure.” 2. There are companies out there that, for example, still work with SAP R/3 Release 4.6. But if you want to run SAP HANA, you’ll need to convert to Unicode, regardless of your current ERP release or which enhancement package you are on. However, not all companies have been interested in converting to Unicode, particularly those that do not do business globally. As a result, code pages can be displayed in multiple languages. SAP Business Suite has already been enabled for Unicode – the international standard for encoding, representing, and handling text – for some eight years. Andreas Schmitz has documented this short process considering individual steps. Regardless of whether you deploy SAP ERP 6.0 with or without enhancement packs (EHPs) or are on an even older release, the journey to SAP S/4HANA is always similar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |