Configuring the SAP S/4HANA Cloud Deployment Options

• Project Experience
  • Manage your SAP Cloud solutions (currently only SAP S/4HANA Cloud, public edition).
• Scoping
  • View and select business scenarios to activate from SAP Best Practices.
  • Select the countries/regions in which to activate each SAP Best Practices scenario.
• Central Configuration
  • Define core finance settings
  • Build the organizational structure
  • Enter data in the configuration activities to configure business scenarios selected during scoping.
  • Transport business configurations from SAP Central Business Configuration to SAP S/4HANA Cloud, public edition.

You can also easily find support and resources with the embedded user assistance and Conversational AI chatbot.

Signavio Process Manager and SAP Process Collaboration Hub by Signavio are included in the SAP S/4HANA Cloud, private edition package. Signavio Process Manager enables you to document, model, and simulate business processes, and the Collaboration Hub provides transparency and a centralized location for managing your processes.

Alternatively, if a customer already has a license to SAP Solution Manager, their SAP Best Practices business processes live in the central library, Solution Documentation. Customer-specific content and supporting documentation is also created and maintained in Solution Documentation.

1. Use SAP Activate Methodology and SAP Best Practices content.
   • We strongly recommend that you use SAP Activate and SAP Best Practices as this will simplify both the initial implementation process and future updates of your software.
   • The SAP Best Practices content configures a client with automatic content activation, and contains only essential configuration settings for the selected scope.
   • This option is required if you want to use the Enterprise Management Layer from SAP (provided by SAP Best Practices content).
2. Use SAP Activate Methodology and SAP Best Practices content as templates for your system configuration, then make changes using the Implementation Guide (IMG).
   • This allows you to adapt the SAP-delivered configuration settings to your specific requirements.
   • If you choose this option, the automatic content upgrade to the next release will not be possible with Solution Builder.
3. Use only the Implementation Guide (IMG) to configure your system.

   Transaction SPRO is used.

• For new implementations, SAP will activate SAP Best Practices content as part of the RISE with SAP services in one system. The SAP Best Practices Questionnaire must be completed by a consultant and provided to SAP.
• Customer or implementation consultant is responsible for tasks such as configuration and customization of the solution business processes and applications.

Note

Refer to the Roles & Responsibilities document for details.

This tool allows you to search and browse simplification items online. Each simplification item details the steps that need to be taken for the conversion from a business and technical point of view. Access the Simplification Item Catalog

This tool analyzes your SAP ERP 6.0 system and highlights important aspects of the conversion to SAP S/4HANA, such as identification of relevant simplification items, high-level custom code analysis, add-on compatibility, sizing, and more.

Although not mandatory, completing the Readiness Check is highly recommended.

The maintenance planner tool needs to be run as the first step in the conversion process. It checks your system components, add-ons, and business functions to ensure compatibility with SAP S/4HANA, and creates the stack file used for the actual conversion process (done by the Software Update Manager tool).

This step is mandatory, because the Software Update Manager requires the stack file for the conversion process.

These checks identify important steps you need to take to make sure your system can technically be converted and that your business processes can start running directly after the conversion process has been completed.

This step is mandatory and will be triggered by the Software Update Manager (SUM). Ideally, this check is run early in the process so the information provided by the checks can be used for planning.

The custom code migration tool checks your custom code against a list of simplifications developed for SAP S/4HANA.

While not mandatory, this step is highly recommended.

When the prepare phase steps have been completed, the SUM can begin. The SUM does the database migration (if required), the actual software update, and the data conversion.

Migration of application data usually happens during release upgrades or updates while the system is down. SAP provides the Silent Data Migration Infrastructure (SDMI) to allow migration of application data after the upgrade during business operations.

Embedded deployment (recommended)

SAP Fiori front-end server is deployed into the AS ABAP of a back-end system.

Hub deployment for single back-end systems

• A dedicated AS ABAP front-end server with SAP Fiori front-end server is deployed in a standalone system in front of the back-end system, either behind or in front of the firewall.
• Existing apps continue to run against the SAP Business Suite back-end systems while the newly installed SAP Fiori applications need to be configured to run against the SAP S/4HANA system.

• SAP Fiori Launchpad enablement for one client (client 100) is completed by SAP (new implementations only). This includes activation of predefined sample SAP Fiori apps to validate the setup of the launchpad.
• Customer or implementation consultant is responsible for non-technical activities, such as enabling and configuring the relevant SAP Fiori apps for customer business processes.

Note

Refer to the Roles & Responsibilities document for details.