SUM Prerequisite Check Extended:
As a concept, tool is intended to get the list of issues which probably could occur during S/4HANA conversion before starting the real execution. So that team on ground are well prepared with the intention that Major issues can be ignored and proceed with rest of the uptime related tasks/steps.
Please refer SAP standard document & blog for further details on the execution.
Following are our observations and learnings while executing this in live environment.
- Use this option,if you have ample time and developers are available to fix the issues.
- SPDD related changes need to be fixed and cannot be ignored. Usually many of the client scenarios, efforts like Basis/ABAP/Functional etc., are planned while starting the project and not before. If you plan to run before then make sure it is taken care
- Of course, effort is required from Basis team. So plan for this execution, as it is expected to run entire uptime tasks
- Please note that as of SUM 2.0 SP 09 offers the Prerequisite Check Extended now for an upgrade of S/4HANA system as well.
- SI check errors can be ignored and proceeded with rest of the steps
- Checks can be done without the target HANA. In this case it will not execute checks related to HANA DB
- Overall runtime will be same as real run.
- Others checks still will be validated like open repairs, locked objects etc.,
- Table comparison is possible. However we did not explore.
- Gives option to recreate the existing tenant in case target HANA is already installed.
- For the tasks which are failed, tool gives the option stating, “Add phase errors to Prerequisite check extended error list and proceed with next steps” . At the end of the run, it provides list with all information about issues faced during the tool execution.
- Reset will be as simple as any other SUM run
- If your intent is to run this check well in advance & you have ample time with SMEs available to execute, then go ahead with this tool execution.
- Uptime related tasks runtime will be same as real execution. So no benefit on runtime and you may have spend equal time like a real run with the focus on optimization
- Helps in checking add-on, SP level validation etc., with SI checks are done and errors can be ignored.
- SPDD effort has to be planned and can’t be skipped
Hope this information helps you to plan the tool execution in future, based on learnings.