Study guide
11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side
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.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side
Key Takeaways Explain This Topic AI
Key user extensibility uses SAP Fiori apps in the customizing tenant (client 100); developer extensibility uses ABAP Cloud with released APIs in the development tenant (client 080).
Side-by-side extensions run on SAP BTP and are built with SAP Build (low-code) or SAP Business Application Studio (code).
Tier 1 extensions are the default, Tier 2 wraps unreleased SAP objects temporarily, and Tier 3 classic ABAP should be modernized.
Key user extensions are transported with the Adaptation Transport Organizer through the Configure Software Packages and Register Extensions for Transport apps.
After a conversion, SPDD, SPAU, and SPAU_ENH adjust modifications, and the ABAP Test Cockpit with quick fixes helps adapt custom code.
Last updated: October 2026
Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side
Section 10.4 explained why a clean core matters. This section covers the tools from the S4C03 unit Customizing Applications : what each extensibility option is for, how key user extensions are created and transported, and what happens to custom code in a system conversion.
The Extensibility Options
Extensibility covers changes that go beyond configuration: data model extensions, data exposure, changes to UIs, forms, and reports, and new UIs or applications. Extensions made with the built-in tools are separated from the core, so SAP can upgrade the system without breaking them. Whatever cannot be done in-app should be decoupled to SAP Business Technology Platform (SAP BTP) .
Option Where Who Tools
Key user extensibility (in-app) Customizing tenant (client 100) Key users and LoB consultants without coding skills SAP Fiori extensibility apps
Developer extensibility (in-app) Development tenant (client 080) ABAP developers ABAP Cloud: released APIs, BAdIs, and extension points only
Classic extensibility Development tenant ABAP developers Any SAP object can be changed; still available but not recommended
Side-by-side extensibility SAP BTP Low-code builders or developers SAP Build (Build Apps, Build Process Automation, Build Work Zone) or SAP Business Application Studio (Java, JavaScript, or Python with the Cloud Application Programming model; extra license)
In ABAP Development Tools, choosing the language version ABAP for Cloud Development switches on the strict ABAP Cloud syntax check and limits custom code to released APIs, such as the CDS view I_PRODUCT . Custom database tables have no default security, and Information Lifecycle Management and the Information Retrieval Framework cannot be used for them, so data access must be tested carefully.
The Three-Tier Model
Tier 1 : key user extensions and ABAP Cloud developments. They are upgrade-stable and the default for every new extension, in converted and in new systems.
Tier 2 : custom wrappers around SAP objects that are not released yet; replace them with Tier 1 once SAP releases an API.
Tier 3 : classic ABAP that does not follow the ABAP Cloud rules; it should be modernized after a conversion.
Resources: the SAP Extensibility Explorer for sample scenarios and patterns, and the SAP Business Accelerator Hub for APIs, events, CDS views, and integration content, with a dedicated SAP S/4HANA Cloud Private Edition tile. LoB configuration experts are not expected to develop with SAP Build or SAP Business Application Studio; requirements that key user tools cannot meet are escalated to the project managers, who bring in an ABAP developer or a BTP resource from the partner or the customer.
Key User Extensibility Apps
First check whether an app supports extensibility: in the SAP Fiori Apps Reference Library, open the app documentation and look for the App Extensibility section, which lists the business contexts, the UI elements for custom fields, and the BAdIs for custom logic.
App Purpose
Adapt UI (runtime authoring) Move, hide, or combine fields and create variants for countries, organizational units, or user groups; requires the Administrator or an extensibility specialist role. Activate a new version (wand icon) and publish it to the transport (truck icon).
Custom Fields Create a field once and enable it for related apps, reports, form and email templates, and APIs; publishing runs as a job that can take up to 30 minutes. Custom fields are not covered by read access logging or by data protection blocking and deletion.
Custom Logic Implement released BAdIs with generated ABAP code, sample code, and a controlled code editor.
Custom Tiles Add tiles that open external URLs; assign them to a business catalog with Custom Catalog Extensions and add them to a page.
Custom Business Objects Create objects with nodes and fields, optionally with a generated UI and the option to associate them with custom fields; assign the UI to a business catalog.
Custom CDS Views Build views for analytical scenarios or for APIs.
Extensibility Inventory Master list of all extensions: who changed them last, their export and import status, and dependencies.
A sales example: a new field on the sales order that also flows to the delivery and the invoice is created in Custom Fields with the sales business context and its business scenarios, and then placed on the screen with Adapt UI (section 10.4).
Forms and Email Templates
Output parameters such as channel, recipient, and form template come from the Output Parameter Determination app (section 9.7), and sent emails can be checked in Display Email Transmissions . Templates are changed by copying the standard ones: Maintain Email Templates for emails, Manage Logos and Manage Texts for the content of master forms, and Maintain Form Templates for forms. XDP files are edited in Adobe LiveCycle Designer; XSD files can be changed with any text editor when only texts change. There are three types of form templates: master forms (page layout, logo, sender address, and footer), application forms (the business content, placed in a master form layout), and standalone forms (content and layout in one). Only print forms are supported; interactive forms need the SAP Forms Service by Adobe on SAP BTP. Customized templates are created in the customizing tenant and transported.
Transporting Key User Extensions
Key user extensions start as local objects . The Adaptation Transport Organizer (ATO) must be set up. In Configure Software Packages , a software package is assigned to a transport request and task so that changes are recorded; in Register Extensions for Transport , the extension items are assigned to that package. An administrator then releases the transport requests in SE09 to move them to quality and production.
Custom Code in a System Conversion
The Simplification Database lists the simplification items; each refers to an SAP Note that explains the impact and how related custom code can be adapted.
Custom code scoping with the Custom Code Migration app, run in the ERP system or on SAP BTP, finds the code that is used and must be adapted and the unused code that can be deleted with deletion transports during the conversion. Its results can be uploaded to the SAP Readiness Check.
During the conversion, ABAP Dictionary modifications are adjusted with SPDD ; after SUM, repository modifications are adjusted with SPAU and SPAU_ENH .
Then the ABAP Test Cockpit (ATC) with SAP S/4HANA checks lists the findings, each linked to SAP Notes. Quick fixes in ABAP Development Tools resolve frequent findings such as ORDER BY issues and data model changes, for example around KONV and BSEG . Apply them in portions, fix syntax errors first, and run ATC again, because ATC checks only syntactically correct objects.
Finally, modernize Tier 3 code toward Tier 1 or Tier 2, and use the SQL performance tuning worklist together with the SQL Monitor to find and prioritize performance hot spots.
- Situation Tool
- Add a field to a sales app Custom Fields plus Adapt UI
- Trigger extra logic when a document is saved Custom Logic (released BAdI)
- Rearrange or hide fields for a user group Adapt UI with a variant
- New application on another platform SAP Build or SAP Business Application Studio on SAP BTP
- Find custom code affected by a conversion Custom Code Migration app and ATC
Tip
The pattern behind most extensibility questions: in-app and key user first, ABAP Cloud second, side-by-side on SAP BTP third, and classic modifications only as documented technical debt.