Study guide

11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration

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.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration

Key Takeaways Explain This Topic AI

Fit-to-standard workshops validate SAP Best Practices processes in a sandbox and document only need-to-have requirements in SAP Cloud ALM.

In conversions, the workshops cover only compatibility-scope items, ERP functions not available in SAP S/4HANA, and additional scope.

The SAP S/4HANA Fully-Activated Appliance is the recommended workshop system for most customers.

SAP Best Practices are activated once in the development system with Solution Builder (/SMB/BBI) and transported to quality and production; processes are copied before they are changed.

Last updated: October 2026

Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration

Fit-to-standard workshops in the Explore phase decide how the system will be configured in the Realize phase. For a sales consultant, they are where requirements such as an extra field on the sales order or a different order confirmation are found and documented. The S4C03 units Gathering Data in Fit-to-Standard Workshops and Validating and Configuring Business Processes describe the approach.

Purpose by Project Type

New Implementation System Conversion

Focus Validate the predefined SAP Best Practices processes against the customer's needs; gather configuration data and extension requirements Most processes convert unchanged; workshops cover only compatibility-scope items, ERP functions that are not available in SAP S/4HANA, and additional scope

Preparation Review the SAP Best Practices documentation; set up a preconfigured system Analyze the simplification items with the SAP Readiness Check; use a preconfigured sandbox or a converted copy of production

Demonstration The SAP Best Practices processes selected in the Digital Discovery Assessment The customer's processes in the fit-to-standard system plus new innovations

In both cases the team decides whether SAP GUI transactions are replaced by SAP Fiori apps, documents and prioritizes the requirements, and then holds design workshops and plans the configuration sprints (prioritized backlog, estimated effort).

Choosing the Workshop System

SAP S/4HANA Fully-Activated Appliance from SAP Cloud Appliance Library: the best choice for most customers, including conversions, where it shows compatibility-scope processes and new functions.

SAP S/4HANA Cloud Private Edition Customer Evaluation System , delivered by SAP Enterprise Cloud Services: it takes longer and costs more, so it suits larger customers who want to reuse its configuration later.

Converted sandbox : the first conversion can take a month or more, and SAP Best Practices content cannot be deployed into a converted system with Solution Builder, so it is often not ready in time.

Planning the Workshops

Demonstrate the complete test procedures of each process's test script (the preliminary steps can be skipped).

Use the length of the test script as a gauge: the course compares Material Requirements Planning ( J44 , about 40 pages) with Production Capacity Leveling ( 3LQ , 11 pages). One or two processes fit into a half-day workshop and two or three into a full day.

Group processes in which the same business roles do most of the work, using the process flows in SAP Signavio Process Navigator.

Run the chart of accounts and organizational structure workshops first; the other line-of-business workshops can follow in parallel.

Invite at least two and no more than four people per business role. If customer experts cannot find time, escalate through the project managers to the executive sponsors, who must tell managers that the workshops have priority.

Running a Workshop

Each workshop starts with a mini kick-off that explains why the participants are there, where the project stands (Explore, then Realize, then their UAT), and the cloud mindset : change the standard as little as possible, use the in-app tools first, move further extensions to SAP BTP, and avoid backend changes. Every change has to be checked after each upgrade (the Release Assessment and Scope Dependency tool helps), so only need-to-have requirements count, not nice-to-have ones. Participants also learn where to find process flows, test scripts, and tutorials: in SAP Signavio Process Navigator and in the system help (question mark icon, then the graduation cap icon, or the learning center).

For each process, the team:

Shows the process flow and test script in SAP Signavio Process Navigator and runs the test procedures in the sandbox, including how to reach embedded support.

Validates the level 2 answers and gathers the level 3 answers of the Business Driven Configuration Questionnaire (BDCQ) .

Documents requirements in SAP Cloud ALM: business role, space, and page changes; data visibility restrictions; custom fields and custom logic; form and email template changes; analytical app changes; additional integrations; data migration values or contacts; and the perceived change impact , which goes to the change management team.

Ideally two consultants run a workshop: one demonstrates and moderates, the other records each requirement separately in the SAP Cloud ALM Processes app ( Create → Requirement ); the Requirements app shows the master list. A requirement is the difference between what the standard system does and what the customer needs it to do.

Design Workshops

Design workshops document solutions for the prioritized delta requirements; requirements already met by the preconfigured processes are not documented. The design document contains a short process description, the high-level requirements, the process flow changes (the SAP Best Practices flow is the baseline, so only adjustments are shown), a configuration summary, user roles and authorization requirements, interfaced IT systems, customization requirements and solutions, developments, organizational aspects, and the process quantification (data volume). In new implementations, detailed configuration requirements are documented outside the design document and linked to a process; in conversions, the focus is on what configuration must change.

A master data design document is produced (in conversions, updated) and later used for the data migration design. Functional specifications are written for the WRICEF objects (workflows, reports, interfaces, conversions, enhancements, and forms) so the Realize phase can be estimated. Custom business roles also need custom spaces and pages.

Configuring and Validating the Processes

New implementation : SAP Best Practices are deployed with the Solution Builder (transaction /SMB/BBI ). A solution contains scenarios, and each scenario consists of building blocks with Customizing settings and master data steps. Content is activated once in the development system and transported to quality and production. Copy a process before changing it, because directly changed processes no longer receive enhancements during upgrades; entirely custom processes are documented in SAP Signavio Process Manager. A report documents the configuration for any level (activity, building block, scope item, or solution). As a standard service, SAP activates the SAP Best Practices the customer selects during provisioning; customer-specific configuration is a partner service. The LoB experts then enter their BDCQ values in the customizing tenant and work through their open requirements.

System conversion : the sandbox is converted and tested first. Sprint 1 tests the current processes, for example in order to cash: review an open sales order, create the delivery, post goods issue, create the billing document, and complete the collection. Sprint 2 looks for improvements, mainly replacing SAP GUI transactions with SAP Fiori apps that the customer can now try with their own data. The other systems are then converted the same way and tested formally in SAP Cloud ALM.

Partner solutions : SAP Certified Solutions (listed in the SAP Certified Solutions Directory) and SAP Qualified Partner-Packaged Solutions (found in the Partner-Packaged Solution Finder) can add industry content on top of the SAP Best Practices baseline.

Tip

If an exam scenario asks where a requirement from a workshop is recorded, the answer is SAP Cloud ALM (Processes app, then the Requirements app), not the BDCQ, which collects configuration values.