SAP S/4HANA Cloud Free Trial
Explore the SAP S/4HANA Cloud system with a free 14-day trial system. The trial includes guided tours based on predefined role-based scenarios. Complete each tour to experience a "day in the life" of each business role.
In the SAP Activate Implementation Methodology, this system is referenced in the Discover (sales) phase as a first-touch user experience for customers and prospects to understand the look and feel of SAP S/4HANA Cloud and support making a purchase decision.
SAP S/4HANA Cloud Implementation Landscapes
The system landscapes used for an SAP S/4HANA Cloud implementation include:
SAP Cloud Identity Services
The SAP Cloud Identity Services tenants are the first systems provisioned for a customer. SAP Cloud Identity Services runs on the SAP Business Technology Platform and consists of two separate tenants, Identity Authentication and Identity Provisioning. SAP Cloud Identity is the default identity provider for SAP S/4HANA Cloud, and provides secure authentication and single sign-on for users in the cloud.
SAP Central Business Configuration
SAP Central Business Configuration (CBC) is a separate tenant that lives in SAP Business Technology Platform where you provision your SAP S/4HANA Cloud systems (Starter, Quality, and Production), activate the business scope, and complete configuration-related activities. Configurations are moved from CBC to SAP S/4HANA Cloud through transports. CBC is used by customers after go-live to continue to maintain their SAP S/4HANA Cloud solution by activating new scope, countries, and making configurations.
The Starter System includes the Enterprise Management scope and comes with preconfigured business processes and master data. The data and configuration in the starter system directly aligns with the scope item test scripts in SAP Best Practices Explorer. Implementation consultants use the starter system to demonstrate SAP Best Practice processes to customer experts in Fit-to-Standard workshops. During the workshops, the business scope that was identified in the Digital Discovery Assessment is confirmed, configuration data is gathered, and customization decisions are made. After consultants move onto configuring the Quality and Production systems, the Starter system can be decommissioned.
The Quality system provisioned and configured via CBC based on the data and requirements gathered during the Fit-to-Standard workshops. The implementation team should transport configurations to the quality system in weekly or bi-weekly sprints, followed by thorough testing of configured processes. Extensions, such as creating custom fields, are done with the relevant extensibility Fiori apps in the S/4HANA Cloud quality system. After thorough testing, extensions can be transported from quality to production using the Software Collection transport Fiori apps in S/4HANA Cloud. Other activities, such as setting up business roles and assigning permissions, setting up integrations, and migrating data are done directly in the SAP S/4HANA Cloud quality system, but cannot be transported and must be done again in the relevant Fiori apps in the production system.
The Production system is provisioned via CBC and kept in sync with the Quality system via weekly or bi-weekly transports. After configurations have been made in CBC, transported to quality and tested thoroughly, the configurations can be released to the production system via CBC. Certain configurations cannot be made in CBC and must be done directly in the production system. The guided workflow tasks in CBC instruct the implementation team members when to make these configurations in the production system. After go-live, the production system is used by end users to run the organization's business processes.
Test Data Refresh Service
Ideally, the Quality and Production systems are mirror images of one another so business process testing or extension testing in the quality system accurately reflects what would occur in the production system (e.g. if a new extension is transported to production). However, the transport path only moves in a single direction from quality to production.
The Test Data Refresh service was developed to solve this problem and provide an ideal testing environment by syncing data in the production system with the quality system. Test Data Refresh is a subscription service that refreshes master and transaction data in the quality system from the production system. A built-in depersonalization feature ensures data privacy compliance.