SAP Cloud Identity Services
SAP Cloud Identity Services consists of two separate systems hosted in SAP Business Technology Platform: Identity Authentication Service (IAS) and Identity Provisioning Service (IPS). The identity tenants are provisioned right away, because the other SAP S/4HANA Cloud systems are connected to them.
Identity Authentication is a cloud service for authentication, single sign-on, and user management in SAP cloud and on-premise applications. It can act as an identity provider itself or be used as a proxy to integrate with an existing single sign-on infrastructure.
Identity Provisioning offers a comprehensive, low-cost approach to identity lifecycle management in the cloud. It helps you provision identities and their authorizations to various cloud and on-premise business applications. Collectively, IAS and IPS enable customers to manage access to applications across their landscape.
SAP Central Business Configuration
SAP Central Business Configuration is hosted on SAP Business Technology Platform and is used to provision, activate business content, and configure the SAP S/4HANA Cloud systems.
First, SAP Central Business Configuration is used to activate the predefined content and configuration in the SAP S/4HANA Cloud Starter System. The Starter System is used to gather customer configuration requirements and finalize the scope during Fit-to-Standard Workshops.
After all configuration values have been gathered, and the customer's Development, Test, and Production systems have been provisioned via SAP for Me, SAP Central Business Configuration is used to activate business scope, define the organizational structure and primary finance settings, and configure business processes in the customer's actual system.
After go-live, customers continue to use SAP Central Business Configuration to maintain their SAP S/4HANA Cloud systems through future release upgrades and business changes. For example, new country or business scope activation, defining additional organizational entities, or making configuration changes.
SAP S/4HANA Cloud, public edition Systems
The SAP S/4HANA Cloud, public edition Trial System is a shared landscape with guided tours to help you experience SAP S/4HANA Cloud applications as different business roles. Each tour guides you through business process flows and apps the user would work with to complete their job tasks. Start your 14-day free trial here.
The SAP S/4HANA Cloud Starter System is a preconfigured system with the enterprise scope (all lines of business enabled) and business data that aligns with the SAP Best Practices test scripts. Consultants use the Starter system to deliver Fit-to-Standard workshops to customer business experts in each line of business during the Explore phase of the SAP Activate Methodology. The purpose is to teach the customer experts how to navigate the new system and to gather configuration data and extension requirements. Customization requirements are documented in SAP Cloud ALM to ensure there is a record of each requirements the consultants must implement in the customer's actual system during the Realize phase of the SAP Activate Methodology. The Starter system can be decommissioned after the customer's own systems are implemented, as it would not be needed any longer.
3-System Landscape (3SL) for SAP S/4HANA Cloud, public edition
In August of the year 2022 (release 2208), the 3-system landscape (3SL) became available. The 2-system landscape included a Quality system, where customizations were both created and tested, and a Production system. 3SL includes a Development system, Test system (previously named, Quality), and Production system. This enables developers to build more complex on-stack extensions using stable SAP objects in the Development system, and separates testing activities into a dedicated Test system.
Within a system, there can be one or more client tenants with different purposes. A client is an organizational unit in the system with specific user master records and authorizations. The SAP S/4HANA Cloud Starter and Development systems have two client tenants:
- Development tenant / client 080 is for developer extensibility in the SAP S/4HANA Cloud ABAP environment, where developers have full ABAP development tool access to released SAP S/4HANA Cloud business objects and extension points. The development tenant is client-independent, meaning development objects built here can be accessed from the customizing tenant if permission is granted. This is because development objects are stored in database tables without a client column. Changes are recorded on development workbench requests and are released for transport with the Transport Organizer view in ABAP Development Tools.
- Customizing tenant / client 100 is the main project, used for business process configuration and key user extensibility with the SAP Fiori extensibility apps. The customizing tenant is client-dependent, meaning configurations or extensions made here can only be accessed within the customizing tenant. This is because master and transactional data is stored in databased tables within a client column. Changes to business configuration in this tenant are recorded on customizing requests and are released for transport with the Export Customizing Requests SAP Fiori app. Key user extensions built with the SAP Fiori extensibility apps in this tenant are added to software collections and released for transport with the Export Software Collections SAP Fiori app.
An administrator imports development requests, customizing requests, and software collections with the Import Collection SAP Fiori app, in the Test system to validate business configurations and extensions.
An administrator imports development requests, customizing requests, and software collections with the Import Collection SAP Fiori app in the Production system to make the configurations and extensions available for productive use.