Study guide
5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
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
5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
Key Takeaways Explain This Topic AI
Condition contract management administers supplier and customer conditions that are agreed in logistics processes but settled later, such as sales rebates.
Configuration has three steps: pricing including condition contract conditions, condition contract maintenance (contract types), and condition contract settlement.
Contract type 0S01 is the basic sales rebate with one customer and 0S02 covers multiple customers; 0S01-0S04 use taxation as a service and 0SG1-0SG4 goods-related taxation.
Rebate conditions use condition type RES1 and accrual conditions REA1; RED1 determines delta accruals in pricing procedure A10006.
Settlement types are partial, final, delta, and delta accruals settlement; a final settlement deducts the amounts already paid in partial settlements.
Last updated: October 2026
Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
Many customer agreements cannot be settled on the invoice. A customer who reaches 25,000 USD of purchases in a quarter receives a 4% rebate, but nobody knows on the first invoice whether the threshold will be reached. Such conditions requiring subsequent settlement are agreed during the logistics process and settled later . In SAP S/4HANA, Condition Contract Management (CCM) , part of Settlement Management, handles them. It replaces classic SD rebate processing, which is not the target architecture in SAP S/4HANA. The S46200 course spends 170 minutes on CCM.
What CCM Provides
According to the course, CCM is a central, standardized solution for administering supplier and customer conditions :
It handles conditions that accompany an invoice (prices, quantity and value conditions) and conditions that require subsequent settlement .
A condition contract stores the conditions , the settlement dates , the data used to determine the business volume that forms the basis of the settlement amount, and the scope of validity .
Accruals can be posted for conditions requiring subsequent settlement, either when the source documents (such as SD billing documents) are posted or in a delta accruals settlement run .
Contracts can be settled automatically or manually , either by sending settlement documents to the partner or by using the partner's own settlement document.
Automated processes support contract extensions , copying documents, and correcting accruals after condition changes.
Contracts can be entered and settled with a validity date in the past , so the contract need not exist before the documents that make up the business volume are posted.
The condition contract is maintained with transaction WCOCO and is the single point of entry for the contract data and its conditions. It shows all documents in which a contract condition was determined and accruals were posted, and it offers a detailed settlement overview (list and graphical) with the FI status of all settlement documents.
Configuring CCM: Three Steps
Configure pricing including condition contract conditions : define the pricing conditions used to calculate the settlement amount, especially the condition contract conditions that are entered in the contract (usually rebate and accrual conditions).
Configure condition contract maintenance : define the parameters for condition contract types and then the types themselves (IMG: Logistics - General → Settlement Management → Condition Contract Management → Condition Contract Maintenance → Define Condition Contract Types ).
Configure condition contract settlement : define the settlement parameters and add them to the contract types.
Delivered Condition Contract Types
Contract Types Scenario
0S01 Basic sales rebate with one customer ; settlement documents of partial, final, and delta accruals settlements go directly to Financial Accounting
- 0S02 Sales rebate with multiple customers
- 0S01 - 0S04 Variants with taxation as a service (the rebate is treated as a service for the customer)
0SG1 - 0SG4 Variants with goods-related taxation (the rebate is a revenue reduction taxed like the sale of the material)
0ST1 - 0ST4 Integration with Trade Promotion Management (TPM), corresponding to 0S01 / 0S02 with taxation as a service
Pricing Procedures and Condition Types
SAP delivers pricing procedures for settlement: A10005 (Rebate), A10006 (Rebate Delta Accrual), A10007 (Rebate, goods-related), and A10008 (Rebates Manual). SAP Note 2535889 describes the delivered configuration. The key condition types are:
Condition Type Role
RES1 Rebate Rebate condition maintained in the condition contract; access sequence RE01 ; set up as a discount but with a positive plus/minus sign because a credit memo is created; in A10005 , base formula 214 keeps the base value positive for fixed amounts, account key 0S1 , subtotal 1
REA1 Rebate Accruals Accrual condition maintained in the contract; the Accruals indicator is set in Control Data 2; access sequence REA1 ; contains the accruals reversal amount in the settlement run
RED1 Used in the settlement run to determine the delta accruals amount ( A10006 ); not an accruals condition itself, but references REA1 , because accrual conditions are not part of the net amount
Settlement pricing procedures contain as few condition types as possible to keep run times short. In the contract you can select the calculation rule and the scale base indicator at condition record level, independent of the condition type's defaults, which further reduces the number of condition types needed.
Business Volume Determination
Settlement is usually not done per document item but on cumulative key figures , the business volume , determined from the transactional data:
The field selection and field combinations used for business volume determination can be defined without restriction, with inclusive and exclusive criteria.
The source of the business volume is defined in Customizing: purchase orders, deliveries, billing documents, point-of-sale data, or agreed fixed budgets.
The key figures can be quantity, monetary sales, weight, volume, or points (the business volume base ).
Business volume determination is independent of the condition record.
In the order-to-cash process, the basic scenarios are rebates based on billing documents , rebates based on cash sale data , and rebates based on agreed budgets . Rebate amounts can be distributed to eligible partners , such as plants or customers, according to their share of the business volume, down to the level at which the business volume is stored (for example, plant, cost center, or material).
Accruals
Legal requirements demand accruals for customer settlement processes. Accrual conditions are defined independently of settlement conditions : they support different calculation types, can be determined in the source documents, are cleared in the settlement run, and are not affected by changes to settlement conditions. If accruals are not posted with the billing documents, the delta accruals settlement determines the pending accruals periodically and posts them to FI, taking existing accruals into account, so billing documents never need to be re-evaluated.
The Settlement Calendar and Settlement Types
Settlement dates are defined in a settlement calendar in the contract, each with a settlement type; dates can be derived automatically from calendars, and the execution date can be set per date.
Settlement Type Purpose
Partial settlement Provisional settlement for a period within the contract term. In a cumulative partial settlement, already settled sales are rolled up so better scale levels apply earlier. Partial settlements are settled finally by the final settlement.
Final settlement Permanently settles a period, from the contract start (or the last final settlement) to the final settlement date. All previously partially settled values are included; final settlements are not settled again, but can be corrected by delta settlements.
Delta settlement Settles late postings or corrections that changed the business volume of a finally settled period; can be repeated (for example, after a 31 December final settlement on 15 and 31 January).
Delta accruals settlement Creates accruals in accumulated form and corrects accruals after condition changes; existing accruals are cleared automatically. It cannot change the moving average price, but accruals can be posted to G/L accounts.
Worked Example from the Course
A condition contract is valid from October to December, with a scaled rebate (2% from 5,000 USD of business volume, 4% from a higher level) and monthly partial settlements.
- Settlement Date Cumulative Business Volume Rebate Rate Calculated Rebate Paid in This Run
- End of October 3,000 USD Below the 5,000 USD minimum 0 USD 0 USD
- End of November 3,000 + 4,000 = 7,000 USD 2% 140 USD 140 USD
- End of December (final) 27,000 USD 4% (second scale level) 1,080 USD 1,080 - 140 = 940 USD
The final settlement calculates the rebate on the whole period and deducts what was already paid: 4% of 27,000 USD is 1,080 USD, minus the 140 USD from November, leaves 940 USD . Accruals are updated with each run. The document flow of the contract shows all delta accruals, partial, and final settlement documents.
Reporting
Predefined reports for condition contracts are built on CDS views and IDA ALV, support customer-specific fields and flexible selections, and are optimized for SAP HANA.