System Landscapes Flashcards
SAP Cloud Appliance Library
Offers a quick and easy way to create SAP workloads in your cloud infrastructure.
Also provides an option for tool-guided migration of an on-premise instance from SAP ERP to SAP S/4HANA.
Updated with both, appliances for demo, proof of concept and exploration of new business cases as well as new versions of SAP S/4HANA software installation stacks for production use.
SAP S/4HANA Trial System
Used for exploration,
30-day free trial, Deploy via SAP CAL.
There is a cost to host the system on one of the third party infrastructure providers (Microsoft Azure, Google Cloud, Amazon Web Services).
Sandbox System - New implementation
Fully configured system is deployed via SAP CAL to use as a demonstration system by partner consultants.
In explore phase - deliver Fit-to-Standard workshops to customer business experts.
Only required till customer’s own systems are implemented.
Customization requirements are documented in SAP Cloud ALM.
Software Update Manager (SUM) tool
Customer’s existing sandbox system is converted to SAP S/4HANA Cloud Private Edition with the Software Update Manager (SUM) tool
Sandbox System - System conversion
Focus is on existing processes, SAP S/4HANA Simplification Items, reviewing new functionality and whether the customer’s current Workflow, Report, Interface, Conversion, Enhancement, and Forms (WRICEF) can be eliminated by adopting SAP standard business processes.
Deploy a system from CAL to review business processes from the compatibility scope, and new functionality the customer may also want enabled in their new SAP S/4HANA Cloud Private Edition system.
Client tenants
Client is an organizational unit in the system with specific user master records and authorizations.
Development tenant / client 080
For developer extensibility in the ABAP environment, where developers have full ABAP development tool access and can even modify the SAP source code, although modification is NOT recommended.
The development tenant is client-independent.
Changes are recorded on development workbench requests and are released for transport with the Transport Organizer view in ABAP Development Tools.
Client-independent Tenant
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.
Customizing tenant / client 100
Main project, used for business process configuration and key user extensibility with the SAP Fiori extensibility apps.
Customizing tenant is client-dependent.
To transport extensions, create a software package with the Configure Software Packages Fiori app, and assign the package to a transport request with the Register Extensions for Transport app.
Client-dependent
Configurations or extensions made here can only be accessed within the customizing tenant. This is because master and transactional data is stored in database tables within a client column.
Development system - New implementation
Fresh development system is deployed with SAP standard business process content, or as a blank system where customizing is done via the IMG (Implementation Guide).
Development system - System conversion
Customer’s existing development system is converted to SAP S/4HANA Cloud Private Edition based on the migration approach validated with the sandbox.
Quality System
Used for thorough testing before any changes or extensions are transported to production.
To make transports available for testing in the quality system, an administrator releases transport requests from the development system with the Transport Organizer (SE09) transaction in the backend.
Quality System - New Implementation
The configuration from the development system is transported to the quality system.
Quality System - System conversion
The customer’s existing quality system is converted to SAP S/4HANA Cloud Private Edition, based on the migration approach validated in the sandbox and development systems
Production System
Used for daily business-related operations and tasks.
To make transports available for use in the production system, an administrator releases transport requests with the Transport Organizer (SE09) transaction in the backend.