The complete update procedure is divided into roadmap steps. The following actions are involved in the respective roadmap:
(i) Initialization – The update GUI is assembled. According to the result of the previous roadmap steps, either the ABAP or Java tab page or both are displayed.
(ii) Extraction – The Software Update Manager extracts the required software.
(iii) Configuration – In the Configuration roadmap step, all the information required for the update Procedure is entered. This includes the passwords, the pre-configuration mode, information regarding components, concerning add-ons and Support Packages that need to be encircled more as data regarding the shadow system.
(iv) Checks – The Software Update Manager checks if the system fulfils the necessities for the update procedure (for example, whether or not the specified free area is available).
(v) Pre-processing – In this roadmap step, the software Update Manager creates the shadow system. This shadow system is then used for varied update activities whereas the first system continues to be in production operation. The software Update Manager builds up the shadow system by cloning parts of the first system. All tables of the SAP NetWeaver Application Server are required as shadow tables to control the shadow system. The shadow system is employed to perform the modification adjustment of the ABAP dictionary objects and therefore the activation of recent ABAP dictionary objects that are a part of the update. Finally, the software Update Manager performs the shadow import and writes directly into the shadow tables. Modifications to the contents of the first tables are indicated by triggers. These tables are copied and imported during downtime.
(vi) Execution – In this roadmap step, the switch to the target system takes place. The software Update Manager completes the copy import action throughout downtime for all tables with triggers set. The EU_SWITCH section completes the switch to the new system. All tables ready within the shadow system are copied to the target system. The KX_SWITCH_1 part switches the SAP kernel. The PARCONV_UPG phase converts the application table, and therefore the phase TABIM_UPG imports the remaining information. Finally, the XPRAS_UPG part starts the XPRAs required by the system.
(vii) Post Processing – The Software Update Manager saves the log files and prompts the start of certain follow-up activities.
(viii) Finalization – The Software Update Manager removes files and directories that are no longer required and completes the update.
The image below gives a pictorial representation of the various steps involved in the Upgrade
Notifications only about new new blog post updates.
Current SAP customers are encouraged to move to S/4HANA from ECC by 2025. This is to ensure a smooth digital transformation among organisations globally. This change results in a complete change in the data model with significantly lesser data footprints than the traditional ERP system.