ASAP4hana Brownfield Approach

Below is a high level overview of preparatory tasks that are needed for SAP S/4 HANA migration from earlier SAP ERPs in a brownfield implementation option. These tasks can vary depending upon the modules implemented, level of customization, current system version, complexity, etc. The idea here is to provide a high level understanding of the preparatory tasks specific to SAP S/4 HANA migration.

Following are some general considerations if you are already running SAP and interested in upgrading to S/4 HANA.

  • The upgrade can be done at any period.
  • Only Unicode systems are converted, starting NetWeaver 7.5.
  • Software Upgrade Manager (SUM) and Database Migration Option (DMO) can be done at the same time so that only one downtime is needed.
  • Data Volume Strategy is highly recommended. Archiving, cleaning up the logs will help the migration process.
  • Level of customization is one of the important influencing factor. ASAP will make analyzing the custom code for the upgrade purpose, typical it is time to clean up not used code.
  • Check and cleanup any cancelled batch jobs
  • Remember to cancel any periodic jobs. Postings are not permitted between S/4 installation and migration.
  • Near Zero Downtime (NZDT) is possible for S/4 migration
  • S/4 HANA sizing and report will be delivered by ASAP4hana

Brownfield migration considerations:

  • The entire system can be migrated with the possible innovations
  • The prerequisite projects should be weighed in for timeline and effort
  • Limited possibilities for process improvements
  • Duration of the project and carrying over the custom development
  • Reporting tools and systems used, i.e. BI, BOBJ, etc.

As a result from the analyses you will have a SOW for the entire upgrade project containing the expected effort for each phases of the project:

  • Analysis
  • Blueprint
  • Upgrading/Development/Transformation/migration
  • Test
  • Pre-go-live
  • GO-LIVE
  • Hypercare and Project closure