Skip to Content
Technical Articles
Author's profile photo Vivian Mafra

Cutover highlights for SAP S/4HANA New implementation

The process of transitioning from any ERP system to an SAP S/4HANA on-premise or SAP S/4HANA Cloud, private edition requires a deliverable called Cutover. This deliverable  includes the Cutover Plan document which covers all the activities related to planning, preparing and executing the tasks, describing how to lock down the system from a technical perspective, preparing the system for operation and release it for end users. Important to say that the plan should be based on previous migrations that the client has already performed in QAS environment.

A cutover plan describes all required tasks that must be performed before the go-live and needs to cover the following tracks:

  • Infrastructure – Production Environment Preparation
  • System Design – Transaction Data Migration
  • Security – Security access enabled
  • Data – Master Data Migration
  • Training – Business Readiness
  • Organizational – Business Preparation
  • Deployment – Go Live Support

And includes the key areas: Technical, Functional, Development , Authorizations; Data Cleansing & Data migration; Organization Change Management and Project Management.

Highlighted below there are some examples to be considered in cutover plan from Infrastructure; System Design, Security Roles & Data perspective:

  • A technical and functional checklist of productive environment vs. quality environment must be done by technical and functional consultants:
    • Technical
      • Validate that SAP S/4HANA and SAP HANA Licenses have been installed in the system. Verify the Disaster Recovery environment as well
      • Validate and schedule standard mandatory jobs
      • Validate the Client Settings, Logical system and so on
      • Validate SSL and SSO configuration
      • Validate the Logon Groups and Operation Modes
      • Validate TMS configuration
      • Check and create RFC Server Groups
      • Validate the RFC Connections between systems
      • Activate Embedded Analytics queries and CDS views
      • Verify that the operational team is ready to receive support request
      • Check all the backups are scheduled
      • If any high availability is configured, make sure you have done failover tests
      • Enable SAP support connections for SAP S/4HANA, SAP HANA and HTML (launchpad URL)
      • Document all manual steps to be executed during the transport request import activities
      • Verify the Installed Add-ons in the system
      • Ensure that security roles (including Fiori) are built appropriately assigned and tested
      • Assign BP role accordingly especially if SAP HCM/ SFSF is in use, because employee BPs are created in SAP S/4HANA
      • Implement the identified system parameters tuning
      • If required, verify that all SCOT settings are configured
      • If required, verify ADS Configuration and setup
      • If there are additional steps regarding extensions/integrations validate as well
    • Functional
      • Schedule and validate the required jobs
      • Validate Transport Requests content
      • Validate Organizational Structure customizing (Controlling Area, Credit Control Area, Company Codes, Chart of Accounts, Cost centers, Profit centers, Plants, Storage Location)
      • Make sure all relevant settings for apps Manage House Banks & Manage Bank Accounts are done
      • Number Range Creation for Business Partner, Customer, Vendor, Material, FI, CO, MM, SD, QM, PM, PP Documents, Bank Accounts (Sequence Numbers, Requests)
      • Validate Document Types
      • Check and maintain posting periods for GL, AA, CO, MM
      • Create condition records for MM, SD, and others required
      • Validate Tax Configuration and Pricing Procedures
      • Make sure that the business relevant movement types are updated
      • Validate output messages for Procurement and Sales
      • Spot validation to adjacent systems
  • A Master Data checklist must be performed:
    • Pre and Post Data load verification
      • Master data load verification – Controlling Area, Company Codes, Chart of Accounts, Fixed Assets, Business Partner, Material, Cost Centers, Profit Centers, Banks, House Banks, Bank Accounts, Inventory, Production Version
  • The Initial Upload must be planned and executed:
    • Authorizations to upload and download files from/to the server
    • Verify user system profiles to execute initial uploads (date format, decimal, point)
    • Upload relevant historical Exchange rates (including those for initial uploads)
    • Initial Balances upload – Consistency Verification
    • Open items upload – Verification: Special attention on Asset Accounting: Fixed Asset Values (Useful Life, Depreciation), Accounts Payables, Accounts Receivables, Banks and so on
    • Open documents from Sales, Procurement, Production, Plant Maintenance and so on

The SAP Fiori also must be considered inside the plan:

    • Ensure the following reports are run and corresponding jobs are set:
      1. Reports to synch backend catalogs
      2. Report /UI5/APP_INDEX_CALCULATE
      5. Ensure end-users clear browser cache so latest available version of the apps in your system is used in runtime.
    • For Embedded Analytics:
      • Ensure all required info objects are active or that task list SAP_BW_SETUP_INITIAL_S4HANA has been run
      • You should find all info objects (40 in total) in transaction RSD5 with status green/active.
    • For Enterprise Search:
      • Ensure task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT has been run
      • Running the following steps is recommended:
        • Re-index connectors via task-list SAP_ESH_INDEX_USER_AUTHORITY.
        • Run task list SAP_ESH_CONSISTENCY_CHECK to identify issues in search connectors.

It is important to say that simulation of cutover activities is recommended to finally document sequences and estimated times. And all the steps, tasks and times must be validated with the business, execute sequenced migrations according to planning with control points:

  • Perform Cut-Over Rehearsal
  • Issue Financial statements
  • Execute End User Training

You can also explore the Cutover Preparation from Roadmap Viewer.

The Focused Build for SAP Solution Manager also provides the “Cutover Checks and Post-Cutover Activities” to reduce the manual effort of cutover activities, please review: Focused Build for SAP Solution Manager

Please be aware that cutover approach is an organization specific strategy, and this blogs only spotlight some examples.

Hope this blog helps you

Thank you

Brought to you by the S/4HANA RIG

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Basanth Swain
      Basanth Swain

      Very Informative with granular details. Thanks for the Blog

      Author's profile photo venu gopal
      venu gopal

      Hello Mafra,

      Thank you for your crisp and clear information, it will be helpfull to number of people in this forum.

      Author's profile photo Srini Tanikella
      Srini Tanikella

      Hello Vivian, great blog and very informative.

      A question on Brownfield implementation from ECC 6.0 EHP7 to S4H 1909 - Is period closing mandatory before the conversion to S/4?

      We have 11 company codes, with 9 sets upon a fiscal year variant of September to August whereas there are 2 company codes that have a calendar year variant.

      We are currently working on an S4 brownfield migration project ( From ECC 6.0 Ehp7 SoH to  S/4HANA 1909 Package 2 )  with an expected go-live date of the end of June. We are given to understand that S4 brownfield migration is to be done on a period closing day.

      However, since we have 2 different fiscal variants, what should be the process for cutover?

      I'm sure there are other companies that have the same requirement, so any help on this is much appreciated.





      Author's profile photo Jarlei Nascimento Gonçalves
      Jarlei Nascimento Gonçalves

      Srini Tanikella  Is necessary to always close the older companies before starting the new implementation because this is a statutory requirement.

      Author's profile photo Kishore Panchakarla
      Kishore Panchakarla

      Very informative

      Author's profile photo Tariq Mehmood
      Tariq Mehmood

      Nice information sharing

      Author's profile photo Waldemar Falinski
      Waldemar Falinski

      Dear Vivian Mafra this is very interesting

      but have got questions. You write "A cutover plan describes all required tasks that must be performed before the go-live" - but some operations and even transactions in Legacy happen after Go-Live like preparing and then closing the accounting books, shen some values may be moved to (or recreated) in New system for the sake CB=OB - is this not considered still as the cutover?

      Look forward to hearing from you soon!



      Author's profile photo Ansari Mohammad
      Ansari Mohammad

      Informative blog.