Study guide

11.2 System Landscapes, System Provisioning, and Release Upgrades

SAP S/4HANA Sales C_TS462

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure

1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration

2 Chapter 2: The Order-to-Cash Process and Sales Master Data

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements

3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries

4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs

4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders

5 Chapter 5: Pricing and the Condition Technique

5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement

6 Chapter 6: Availability Check (ATP) and Delivery Scheduling

6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

7 Chapter 7: Delivery Processing and Embedded EWM

7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries

8 Chapter 8: Billing and Integration with Financial Accounting

8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output

9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables

10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core

10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels

11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition

11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM

11.2 System Landscapes, System Provisioning, and Release Upgrades

Key Takeaways Explain This Topic AI

The development system has client 080 for developer extensibility and client 100 for configuration and key user extensibility; transports go from development to quality to production.

SAP Cloud Appliance Library deploys trial and sandbox systems such as the SAP S/4HANA Fully-Activated Appliance in about two to three hours on a hyperscaler.

The IT Contact provisions SAP Cloud ALM in SAP for Me and must activate the Identity Authentication Service first; SAP Signavio Process Manager, Process Collaboration Hub, and SAP BTP are provisioned automatically.

SAP S/4HANA follows a two-year release cycle with seven years of mainstream maintenance; Private Edition customers must upgrade at least once every seven years.

Last updated: October 2026

System Landscapes, System Provisioning, and Release Upgrades

Before anyone configures a sales document type, the right systems must exist and the right people must be able to log on. The S4C03 units Defining System Landscapes and Setting Up Systems for Implementation describe these systems, how they are provisioned, and how they are kept current.

The Implementation Landscape

  • System Purpose
  • Trial system Fully configured SAP S/4HANA system from SAP Cloud Appliance Library (CAL) for exploration
  • Sandbox system Demonstration system for fit-to-standard workshops
  • Development system Configuration and extensions
  • Quality system Testing before changes reach production
  • Production system Daily business operations
  • Trial and Sandbox Systems from SAP Cloud Appliance Library

CAL deploys a fully configured SAP S/4HANA system in about two to three hours with a hosting partner (Microsoft Azure, Google Cloud, or Amazon Web Services). The software of the SAP S/4HANA Fully-Activated Appliance is free for 30 days ; the hosting provider charges for the infrastructure (the course quotes about EUR 3 per hour), and after 30 days SAP also charges for the software. Because Private Edition runs the on-premise software in SAP's cloud, appliances titled "SAP S/4HANA" can be used for Private Edition projects. An appliance is a compressed system image that keeps everything that was configured when it was built. Relevant appliances:

SAP S/4HANA Fully-Activated Appliance : SAP Best Practices for Private Edition activated for core functions, plus scenarios such as Service, Master Data Governance, Transportation Management, Portfolio Management, and Analytics, with prebuilt demo scripts. It is the usual system for fit-to-standard workshops.

Enterprise Management Layer for SAP S/4HANA : a preconfigured template for international companies with 43 local versions and 25 languages, a group ledger as the leading ledger, and four predefined parallel ledgers per country.

System Conversion to SAP S/4HANA, Parts 1-3 : preparation, technical conversion, and post-conversion activities.

For a new implementation , the sandbox is a CAL system used to demonstrate processes; it can expire once the customer's own systems exist. For a system conversion , the customer's existing sandbox is converted with SUM; the focus is on existing processes, simplification items, and whether custom WRICEF objects (workflows, reports, interfaces, conversions, enhancements, forms) can be replaced by standard processes. A CAL system is often added to show compatibility-scope processes and new functions.

The Development System and Its Two Clients

Client Use Dependency Transport

080 (development tenant) Developer extensibility in the ABAP environment; modifying SAP code is possible but not recommended Client-independent objects Workbench requests released with the Transport Organizer in ABAP Development Tools

100 (customizing tenant) Business process configuration and key user extensibility Client-dependent settings and data Software packages ( Configure Software Packages app) assigned to transport requests ( Register Extensions for Transport app)

For a new implementation, the development system is delivered with SAP Best Practices content or blank, with configuration done through the IMG. Transports move the configuration from development to quality and then to production; administrators release them with the Transport Organizer ( SE09 ). In a conversion, each existing system is converted in turn, using the approach proven in the sandbox.

SAP for Me, SAP Cloud Identity Services, SAP Cloud ALM, and SAP BTP

SAP for Me is the one-stop portal for customers and partners. Its dashboards include Systems & Provisioning (provision purchased cloud solutions, track systems, remote connections, and license and migration keys), Services & Support (support cases, SAP Notes and knowledge base articles, and lifecycle tools; it replaced the decommissioned SAP ONE Support Launchpad), Users & Contacts (find your company's SAP administrators), Products & Portfolio , and Finance & Legal .

SAP Cloud Identity Services run on SAP BTP and consist of the Identity Authentication Service (IAS) and the Identity Provisioning Service (IPS) , which provide single sign-on across SAP systems. They are provisioned automatically with the first SAP cloud solution. The IT Contact uses IAS to create users for the project team; IPS jobs create the users and permissions in the connected systems.

SAP Cloud ALM runs on SAP BTP and is included in SAP Enterprise Support for cloud editions. Its areas: SAP Business Transformation Center (selective data transitions), SAP Cloud ALM for Implementation (SAP Activate tasks, scope, requirements, and tests), SAP Cloud ALM for Operations (monitoring, section 11.7), and SAP Cloud ALM for Service .

SAP BTP hosts SAP Cloud ALM, the identity services, SAP's standard integrations, and the SAP Build tools (Build Apps, Build Process Automation, and Build Work Zone) included in the RISE with SAP enablement package. It offers around 90 services, described in the SAP Discovery Center.

Onboarding and Provisioning Sequence

After signing, the contract signer receives a purchase confirmation and, on the contract start date, a one-time welcome email ; the same information is kept in the Customer Onboarding Resource Center . A separate SAP BTP welcome email follows.

There is only one IT Contact , although several communication contacts are possible. If the wrong person holds the role, a support case in SAP for Me (component XX-S4C-OPR-SRV ) changes it.

The IT Contact provisions SAP Cloud ALM in SAP for Me → Systems & Provisioning , choosing an existing SAP Cloud Identity tenant or letting a new one be created in the chosen region.

Several notification emails arrive; IAS must be activated first , and the users for SAP Cloud ALM are then created there.

SAP Signavio Process Manager , SAP Signavio Process Collaboration Hub , and SAP BTP are provisioned automatically.

For a new implementation, the Private Edition systems are provisioned later. For a conversion, no new systems are provisioned, because SUM converts the existing ones.

Release Upgrades

After the 2023 release, SAP S/4HANA moved to a two-year release cycle , and mainstream maintenance was extended from five to seven years .

For the latest base release, Feature Pack Stacks (FPS) with non-disruptive new features follow every six months. The previous release receives Support Pack Stacks (SPS) with corrections only until its mainstream maintenance ends.

Private Edition customers must install at least one upgrade every seven years . With the RISE with SAP services they can request one upgrade per year : SAP performs the technical upgrade, while planning, preparation, and testing remain with the customer or the partner. After go-live, the upgrade tasks are managed in SAP Cloud ALM with the roadmap RISE with SAP S/4HANA Cloud Private Edition - Upgrade (section 11.3).

Sources of information: the notification banner and the megaphone icon (What's New) in the system, the What's New Viewer in the SAP Help Portal, the SAP Road Map Explorer for planned enhancements, and the Customer Influence & Adoption site for improvement requests and early adopter programs.

Tip

Remember the client numbers: configuration and key user extensions in the customizing tenant (client 100), ABAP Cloud development in the development tenant (client 080).