After completing this lesson, you will be able to:
SAP Central Business Configuration is a new tool that will make it possible to configure business processes spanning multiple SAP cloud solutions from one central place.
SAP Central Business Configuration currently supports the system provisioning and configuration of SAP S/4HANA Cloud, public edition. The long-term goal is to support implementation of all solutions in SAP's Intelligent Enterprise to enable seamless end-to-end business process configuration from one single SAP Central Business Configuration system, meaning solutions such as SuccessFactors Employee Central, Ariba, Concur, and others would be provisioned and configured from SAP Central Business Configuration, just as SAP S/4HANA Cloud, public edition is currently provisioned and configured.
You can also easily find support and resources with the embedded user assistance and Conversational AI chatbot.
The tool for deploying SAP Best Practices in the private cloud or on premise deployments is the SAP Solution Builder. The focus of the Solution Builder is on solutions.
A solution contains a set of SAP Best Practices scenarios, which are predefined process flows for a particular line of business or business area.
Scenarios consist of one or more building blocks, which are self-contained and reusable entities that include customizing settings and/or master data steps. Best Practices are only activated once in the development system.
Transports are used to provide the quality and production systems with the business configuration defined in the development system.
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.
Transaction SPRO is used.
A system conversion involves many different components. For SAP S/4HANA Cloud, private edition, SAP performs the technical tasks of the conversion that cannot be performed by the customer or partner. This includes activities in SAP HANA Enterprise Cloud, such as tasks in Client 000 (the main admin client where the system is installed/upgraded). The technical conversion activities executed by SAP require standard scheduled downtime to implement.
Responsibility for other conversion activities, such as the SAP Readiness Check, custom code optimization, and functional or integration testing are the responsibility of the implementation partner and customer.
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.
The SAP Fiori launchpad and SAP Fiori apps are an essential component to the SAP S/4HANA user experience. After installation, there should be no need for general business users to have to use the SAP GUI Easy Access menu to complete their job tasks through transaction codes, as all apps to complete daily business tasks will be available in the launchpad based on the user's assigned business role.
For both new implementation and system conversion scenarios of SAP S/4HANA Cloud, private edition, the SAP Fiori launchpad and apps must be configured separately.
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