Converting a Three-System Landscape

The SAP S/4HANA conversion of a standard three system landscape can be performed as follows:

Make early experiences in the sandbox system: technical conversion procedure, modification adjustment, test of customer developments, check functionality, test of core business processes.

Reduce dual maintenance period: do high effort work in sandbox system before converting the actual landscape, reduce time window between conversion of DEV and PRD system.

Reasons for a sandbox system:

Test technical conversion procedure

Learn about specifics of your SAP system

Test of customer developments in SAP S/4HANA Server

Understand and plan custom development changes in detail

Start modification and custom development adjustment

• Limit efforts by focusing on objects in production

• Reduce double maintenance/code freeze period

Perform first tests of core business processes in SAP S/4HANA Server

Understand and plan integration tests requirements

Perform first checks of new functions

Obtain insight in SAP S/4HANA Server and plan future functional rollouts

Obtain first test results of technical conversion downtime

Understand and plan downtime optimization requirements

A temporary maintenance landscape is set up during the project to ensure the maintenance of the production system on the old release until it is converted. The SAP systems will be removed after the completion of the conversion project.

Always set up a three system landscape for maintenance - only emergency corrections allowed.

Plan and communicate code freeze time.

Lessons Learned: Project Management

• Make early experiences in the sandbox system
  • Technical conversion procedure
  • Modification adjustment
  • Test of customer developments
  • Customizing
  • Check functionality of processes
  • Test of core business processes
• Reduce dual maintenance period
  • Do additional effort work in sandbox system before conversion of system landscape
  • Reduce time window between conversion of DEV and PRD system
• Involvement and commitment

  Early involvement of key users and management commitment are key success factors

Plan and communicate code freeze time!

Lessons Learned: Functional Aspects

• Good housekeeping drives efficiency of conversion
  • Archiving, cleansing of unused custom code and SAP modifications
  • Document table changes thoroughly and their usage in custom programs
• The older the release, the more money spent on training

  Utilize computer based training: easy to distribute and review at the convenience of the user

• Industry solutions

  Customers with industry solutions should review the specific information

• Tackle custom developments as early as possible

  The faster the development team can have access, the faster business process issues can get resolved

• Modification adjustments and testing are key cost drivers

  The better the documentation and existing test procedures, the easier and less time consuming those project tasks will be