Practical Concepts for the Implementation of SAP S/4HANA Cloud Public Edition

The operational landscape relates to the request for development, test, and productive systems. As you request the starter system, you will become familiar with some key concepts prior to initiating it from the SAP for Me dashboard. We remind you of the criticality of these settings, as incorrect inputs may result in project delays due to the need for systems to be reprovisioned.

Key Areas:

- Scoping

- Organizational structure

- Primary Finance settings: Ledger, Group Currency, Fiscal Year Variant

• Ledger Ledger | SAP Help Portal
• Group Currency Setting Your Group Currency | SAP Help Portal
• Fiscal Year Variant Fiscal Year and Fiscal Year Variant | SAP Help Portal

Please note that after the productive system becomes available, the starter system will be decommissioned within 30 days.

In addition you also the parallel project line. This is an addition CBC workspace with two additional tenants which allows adding new countries, extend the business configuration, test it and then transport it to the productive system, without disturbing the ongoing implementation project. See more in this blog.

SAP Central Business Configuration enables you to manage configurations for SAP S/4HANA Cloud Public Edition implementations and ongoing operations centrally through Project Experience. You can initiate changes at any time to expand your scope, add countries or regions, modify organizational structures, or adjust configuration settings.

The process of creating initial users should already be familiar, as it is similar to what was used for the starter system. However, with the setup of the operational landscape, automated user creation is now possible. Additionally, it is important to understand how the maintenance of business roles occurs in the system, as these roles grant access to business processes and data, as well as the ability to extend the system.

Users can be created either through an integrated HR system or without its integration. You will find detailed guidance for this process here.

For business roles and catalogs, which include granting access to specific apps, detailed information can be found here.

The Output Management apps include activities related to the distribution of business documents via print or e-mail. You can select the output channel directly within the app, choosing either print or e-mail.

For printed output, you can set up print queues to manage document printing and monitor print jobs within each queue. Documents can be printed on an ad-hoc basis, for example, by previewing them in Adobe® Reader.

For e-mail output, you can streamline your correspondence by creating custom templates based on pre-delivered ones. Additionally, you can monitor e-mail transmissions within your area over a specific time frame, checking for successful deliveries or errors.

For more information, see further here.

Extensibility allows our customers to extend the system to meet specific needs. We have categorized it into three types:

- Key user extensibility

- Developer extensibility

- Side-by-side extension.

Each capability is intended for different key users, has varying impacts on the system, and requires different skill sets to apply these developments effectively. Additionally, the methods for transporting these extensions across the landscape vary.

The course Implementing SAP S/4HANA Cloud Public Edition will provide a deep dive into these concepts, should they be applicable to your needs.

SAP continues to publish remote APIs for SAP S/4HANA Cloud Public Edition enabling you to integrate with other SAP Cloud solutions, on-premise systems, or third-party solutions. You can also build cloud apps on the SAP Cloud Platform and connect them to your core business processes. SAP S/4HANA offers various types of APIs, including web technology-based APIs (OData, REST, and SOAP), traditional SAP APIs (BAPIs and IDOCs), and CDS views, which can be exposed as OData services.

The course Implementing SAP S/4HANA Cloud Public Edition will provide a deep dive into the integration capabilities of SAP S/4HANA Cloud Public Edition helping you understand how to best align it with your business needs.

SAP enables data migration to SAP S/4HANA Cloud Public Edition for customers transitioning from any legacy system. Customers of SAP S/4HANA Cloud Public Edition can leverage reliable migration approaches built into the system using the SAP S/4HANA Migration Cockpit, along with a set of predefined data migration objects.

The course Implementing SAP S/4HANA Cloud Public Edition provides an introduction to the data migration capabilities in SAP S/4HANA Cloud Public Edition helping you understand how to best align them with your business needs. Additionally, further guidance on effectively using these data migration capabilities in the SAP S/4HANA Cloud Public Edition system can be found in the SAP Help Portal.

Automated testing in SAP S/4HANA Cloud Public Edition can be conducted using the SAP S/4HANA Cloud Test Automation Tool. This tool assists in automating tests during various project phases and upgrades. It is a functionality that can be set up during the implementation process.

Nonetheless, as illustrated, testing also includes unit testing, integration testing, user acceptance testing, and more, as applicable to specific projects. We recommend maintaining the entire testing strategy in Cloud ALM.

The course Implementing SAP S/4HANA Cloud Public Edition will provide further guidance on planning the testing strategy and leveraging the test automation tools available in the system.

As part of our continuous delivery approach, SAP provides Hotfix collections designed to rectify errors and system bugs. Twice a year, we synchronize all customer systems—once in February and again in August. This process begins with an e-mail notification sent to the system administrator six weeks prior to the upgrade. The exact schedule for upgrades and hotfixes can be accessed via the link. Additionally, the diagram illustrates the various steps involved in the upgrade process, and we recommend using the test automation tool for regression testing preparation.

During and after the test system upgrade, we advise executing regression testing and conducting an analysis of post-upgrade tests. This is crucial to minimize any impact on production and provides an opportunity to report any issues to SAP. After upgrading the productive system, it is important to review roles to ensure that everything is correctly set up. The process concludes with a successful e-mail notification after the upgrade of the productive system.

• Upgrades are scheduled to begin with the Test System, followed by Development and Production Systems three weeks later.
• All customer systems maintain the same release and hotfix package.
• The SLA (Service Level Agreement) for cloud services can be found here.
• SAP sends release upgrade schedule notifications via e-mail to each customer approximately six weeks in advance.
• Detailed information on the upgrade and patching schedules can be found here.

A dedicated roadmap viewer is available to guide you through the process. Please find it here

After learning how to request operational systems and understanding their key settings, you should now be able to identify the core resources needed for extending and integrating with other systems. Additionally, the resources for data migration and testing should be clear, enabling you to get started effectively. Finally, you should now be aware of the framework through which SAP continuously innovates and delivers in a cloud environment.