SAP S/4HANA Condition Contract Management Sales Rebate Configuration Guide

S/4HANA
March 2023
English
Condition Contract
Management Sales Rebate Processing
Delivered Standard Configuration S/4HANA 2022
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Copyright
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see
http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and
notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other
software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without
representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services,
if any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this
document or any related presentation, or to develop or release any functionality mentioned therein. This
document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed
by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is
not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
2
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
3
Contents
1. Purpose ...................................................................................................... 6
2. Configuration ............................................................................................. 8
2.1
Configure Pricing Including Condition Contract Conditions ..................... 8
2.1.1.
Condition Tables ................................................................................................ 9
2.1.2.
Access Sequences........................................................................................... 10
2.1.3.
Condition Types ............................................................................................... 13
2.1.4.
Specify CC-Relevance for Condition Types ...................................................... 38
2.1.5.
Define Condition Type Groups ......................................................................... 38
2.1.6.
Assign Condition Types to Condition Type Groups ........................................... 39
2.1.7.
Define Account Keys ........................................................................................ 42
2.1.8.
Define Pricing Procedures ................................................................................ 42
2.1.9.
Condition Exclusion For Groups Of Conditions ................................................. 55
2.1.10.
Define Document Schema Groups for Settlement Document Types ................. 57
2.1.11.
Pricing Procedure Determination ...................................................................... 58
2.1.12.
Specify General Settings .................................................................................. 59
2.2
Configure Condition Contract Maintenance ............................................. 60
2.2.1.
Define Number Ranges .................................................................................... 60
2.2.2.
Define Condition Contract Categories ............................................................... 61
2.2.3.
Define and Configure Field Status Groups for Header Fields ............................ 61
2.2.4.
Define Text Determination Procedures ............................................................. 64
2.2.5.
Specify Text Types for Text Determination Procedure ...................................... 64
2.2.6.
Define Check Groups ....................................................................................... 65
2.2.7.
Specify Settings for Transfer Manager .............................................................. 66
2.2.8.
Define Condition Contract Types ...................................................................... 98
2.2.9.
Activate Additional Functions.......................................................................... 102
2.3
Configure Condition Contract Settlement ............................................... 103
2.3.1.
Define Amount Field Groups .......................................................................... 103
2.3.2.
Define Explosion Groups for Business Volume Base ...................................... 104
2.3.3.
Define and Configure Profiles for Business Volume Determination ................. 105
2.3.4.
Define and Configure Field Combinations for Business Volume Selection ....... 113
2.3.5.
Define and Configure Sets of Field Combinations ........................................... 117
2.3.6.
Define and Configure Condition Type Groups for Accruals ............................. 119
2.3.7.
Specify Extended Scope of Settlement Management ...................................... 121
2.3.8.
Define Number Ranges .................................................................................. 122
2.3.9.
Define Country-Specific Number Ranges ....................................................... 123
2.3.10.
Define Process Categories ............................................................................. 123
4
2.3.11.
Specify Text Determination ............................................................................ 124
2.3.12.
Define and Configure Text Transfer Groups ................................................... 127
2.3.13.
Define Posting Rules ...................................................................................... 127
2.3.14.
Define Field Change Groups for Cancellation Documents............................... 128
2.3.15.
Define Field Status Groups ............................................................................ 129
2.3.16.
Define Settlement Document Types ............................................................... 132
2.3.17.
Assign Transfer Groups to Settlement Document Types ................................. 174
2.3.18.
Define Column Sorting Groups ....................................................................... 182
2.3.19.
Define Settlement Process Types................................................................... 186
2.3.20.
Allowed Combinations Settlement Process Type / Settlement Document Type
200
2.3.21.
Specify Copy Control...................................................................................... 202
2.3.22.
Specify Settlement Settings for Condition Contract Types............................... 203
2.4
Other Configuration Settings ................................................................... 220
2.4.1.
Define Access Sequence for Account Determination ...................................... 220
2.4.2.
Define Account Determination Type ............................................................... 221
2.4.3.
Define and Assign Account Determination Procedures ................................... 222
2.4.4.
Assign G/L Accounts ...................................................................................... 223
2.4.5.
Define Output Types ...................................................................................... 224
2.4.6.
Define Output Determination Procedures ....................................................... 225
2.4.7.
Assign Output Channels ................................................................................. 225
2.4.8.
Assign Form Templates ................................................................................. 226
2.4.9.
Activation of Scope-Dependent Application Job Catalog Entries (S/4HANA) ... 226
5
1. Purpose
This configuration guide describes the settings for the Sales Rebate Processing scenario
delivered as of standard in S/4HANA 2022. The guide shall help you to set up your own
configuration by providing information about all necessary steps and the associations between
Customizing activities.
Note: Some settings described in this document, for example for pricing and taxation, are
specific for Germany. For other countries, these settings have to be adapted according to local
requirements.
Note: Sales Rebate Processing is a specific scenario within the Condition Contract
Management (CCM) application. A more generic description of the CCM including basic
configuration principles is delivered in a dedicated configutraion guide.
The standard configuration comprises settings for the basic sales rebate scenario and settings
for several variations of this basic scenario. The basic scenario concerns the sales rebate
agreement with one customer. The settlement documents that you create in the different
settlement runs (partial and final settlement, delta accruals settlement) are directly transferred to
Financial Accounting. This basic scenario is related to condition contract type 0S01 Sales
Rebate.
The standard delivery also contains a variation concerning settings for contracts that are valid
for several customers (e.g. condition contract 0S02 Sales Rebate - Multiple Customers) and a
variation for the collection of settlement documents before their posting to Financial Accounting.
Another variation affects the way how taxes for the rebate amount are determined. There are
two options: You can consider sales rebate agreements as a service for the customer. Under
this perspective, you apply the usual value added tax for services. Alternatively, you can regard
subsequent sales rebates as normal revenue reductions. Then you must apply the tax valid for
the sales of a material (goods-related taxation). In the standard delivery you find four scenarios
with taxation as a service (condition contract types 0S01 to 0S04) and four corresponding
scenarios with goods-related taxation (condition contract types 0SG1 to 0SG4). Note: when you
compare the condition contract types from these two types of scenarios, all settings are
identical, except for those that concern taxation.
In addition, there are special settings for the integration of Condition Contract Management with
Trade Promotion Management (TPM). The four condition contract types 0ST1 to 0ST4
correspond to the condition contract types 0S01 and 0S02 for the taxation as a service. The
standard delivery does not contain settings for the TPM integration in connection with goodsrelated taxation, as they can easily be derived from the settings for 0SG1 and 0SG2 and 0ST1 to
0ST4 presented in this document.
These are the scenarios and their corresponding condition contract types:
•
Basic scenario with a condition contract for one customer (0S01)
•
Condition contract for multiple customers (0S02)
•
Condition contract for one customer with a two-step settlement (0S03)
•
Condition contract for multiple customers with a two-step settlement (0S04)
•
Condition contract for one customer with goods-related rebate taxation (0SG1)
•
Condition contract for multiple customer and goods-related rebate taxation (0SG2)
6
•
Condition contract for one customer, goods-related taxation, 2Step settlement (0SG3)
•
Condition contract for multiple customer, goods-related taxation, 2Step settlement (0SG4)
•
Condition contract for TPM integration, one customers (0ST1)
•
Condition contract for TPM integration, multiple customers (0ST2)
•
Condition contract for TPM integration with claims, one customers (0ST3)
•
Condition contract for TPM integration with claims, multiple customers (0ST4)
The configuration settings of the different scenarios are identical for the most part. To avoid
reduncancies, this configuration guide only describes the settings of the basic scenario in detail.
For the other scenarios, only the differences that are relevant for the process variation are
outlined.
The sequence of the chapters reflects the order in which the settings are to be maintained,
meaning that you first have to define parameters that are then used in other Customizing
settings. For example: You have to define a condition contract category first before you can
assign it to a condition contract type.
7
2. Configuration
The configuration of Condition Contract Management comprises three main steps:
1. Configure Pricing including Condition Contract Conditions
In this step, you define pricing conditions that are relevant for the calculation of the
settlement amount during the condition contract settlement.
In particular, you make specific settings for the so-called condition contract conditions
which you enter in the condition contract maintenance in the Conditions screen area.
Contract conditions usually comprise the rebate and accrual conditions.
2. Configure Condition Contract Maintenance
In this step, you first define and configure parameters for condition contract types and
then the condition contract types themselves.
3. Configure Condition Contract Settlement
In this step, you first define and configure parameters for condition contract settlement.
Then you enhance existing condition contract types with these parameters
2.1 Configure Pricing Including Condition Contract
Conditions
The configuration of pricing in Condition Contract Management comprises two areas:
•
Configure settings for pricing used in settlement documents as part of condition contract
settlement
•
Configure specific settings for condition contract conditions
Note: The configuration of pricing for condition contract management and the configuration for
settlement documents as part of the condition contract settlement (see chapter Specify
Extended Scope of Settlement Management to chapter Allowed Combinations Settlement
Process Type / Settlement Document Type) overlap thematically, as the pricing procedures
described here (together with related configuration settings) are used within the settlement
documents to calculate rebates as well as accrual amounts and to reverse accruals.
The account key described in chapter Define Account Keys is as well related to settlement
documents as it controls the posting of pricing data to Financials. However, as it is a parameter
used in pricing procedures we describe it already in this main chapter.
8
2.1.1. Condition Tables
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Sales (SD) → Define Condition Tables → Display
Condition Tables
2. Check the following condition tables.
Condition Table
Description
4AB
Condition Contract
163
Condition Contract / Material
4AM
Condition Contract / Product Hierarchy 1 / PH2 / PH3
4AN
Condition Contract / Material Group 1 / MG2 / MG3 / MG4 /MG5
4AO
Condition Contract / Customer
The condition tables specifically defined for Condition Contract Management contain the
condition contract number as key field. The corresponding short description in the configuration
screen is Condition Contract, the technical field name is COCO_NUM. This is shown here for
condition table 4AB Condition Contract.
In addition, condition tables for taxes are relevant as for instance 002 Domestic Taxes delivered
with the business content for Sales and Distribution. Condition table 4AU Settlement Input Tax is
delivered specifically for the scenario with a settlement of sales rebates using the A/P account.
Condition tables 166 Region-Dependent Tax on Sales (delivered with the business content for
Sales and Distribution) and 167 Region-Dependent Settlement Input Tax are applied in the
context of Brexit and Northern Ireland protocol (see note 2999929 BREXIT: Necessary
adjustments for the determination of tax conditions after the BREXIT transition period in
Settlement Management).
9
2.1.2. Access Sequences
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Sales (SD) → Define Access Sequences →
Change Access Sequences
2. Control the following access sequences.
Access Sequence
Description
RE01
Sales Rebate
REA1
Sales Rebate Accruals
RET1
Sales Rebate Tax
RET2
Sales Rebate Tax Trigger
RET3
Rebate Inbound Tax
RET4
Sales Rebate Tax (Region)
RET6
Rebate Inbound Tax (Region)
TPCA
Trade Promo Cond Contract Accr
TPCC
Trade Promo Condition Contract
Access sequence RE01 Sales Rebate has the following accesses and access fields.
10
Accesses 26 uses field KOMP-MVGR2, access 27 uses KOMP-MVGR3, access 28 uses KOMPMVGR4, and access 29 uses KOMP-MVGR5.
11
Access sequence REA1 Sales Rebate Accruals has the same accesses like RE01 Sales
Rebate. However, accesses 20 to 50 have the requirement 67 CCS: AccrMultVal. This formula
effects that the "exclusive" flag works on level condition type / condition contract and not only on
condition type level (see requirement documentation).
Access sequences TPCC Trade Promo Condition Contract and TPCA Trade Promo Cond
Contract Accr belong to the TPM integration. Compared with access sequence RE01, TPCC
contains additional accesses for material groups and product hierarchies. TPCA contains the
same accesses than TPCC. Again, the difference is that the accesses, unlike the last, have
requirement 67.
Access sequence RET1 Sales Rebate Tax has the following access and access fields.
Access sequence RET2 Sales Rebate Tax Trigger has the same access and access fields but
the access has requirement 69 CCS: No Tax Code. This requirement checks the existence of a
tax code in the data of a pricing item (see requirement documentation).
Access sequence RET3 Rebate Inbound Tax has the following access and access fields.
12
This access sequence is applied to determine the input tax when you settle sales rebates via
the A/P account.
Access sequences RET4 Sales Rebate Tax (Region) and RET6 Rebate Inbound Tax (Region)
have been configured to fulfill legal requirements for the different taxation scenarios in the
context of Brexit and Northern Ireland protocol. For details concerning the tax determination in
these scenarios, see note 2999929 BREXIT: Necessary adjustments for the determination of
tax conditions after the BREXIT transition period in Settlement Management.
Note: There is another CCM-related access sequence COMP Condition Contract & CC/Mat. that
is part of the standard delivery since several years. The technical name is derived from the
previous naming of the solution in SAP ERP – Compensation Management. The description
reflects the two accesses to table 4AB Condition Contract and 163 Condition Contract /
Material. As the accesses are also included in access sequence RE01 as shown above, we do
not show details for COMP.
2.1.3. Condition Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Sales (SD) → Define Condition Types → Set
Condition Types for Pricing
2. Check the following condition types.
Condition Type
Description
AS01
Tax Trigger
MWAS
Output Tax
MWVS
Input Tax
REA1
Rebate Accruals
REA2
Rebate Accruals Rev
REA3
Rebate TPM Accruals
REA4
TPM Accruals Rev
REA5
Rebate AccrualsSettl
REA6
Rebate Accruals
13
REA7
AccrClearing Open
REA8
Rebate Accruals RevN
REAB
AccrClearing Base
REAT
Rebate TotalAccruals
REBD
Rebate BusVol Delta
REBT
Rebate Total BusVol
REBV
Rebate Business Vol.
RED1
Rebate Accruals
RED2
Rebate Accr Total
RED3
Rebate TPM Accruals
RED4
TPM Accr Total
RED5
Cost Recogn. Adjust
RED6
Rebate Accruals
REJ1
Rebate Adjustment
RENT
Rebate Net Amount
RES1
Rebate
RES2
Rebate PartSettl Rev
RES3
Rebate TPM
RES4
TPM PartSettl Rev
RES6
Rebate
RETI
Rebate Tax Inbound
RETT
Rebate Tax Trigger
RETX
Rebate Tax
REU1
Rebate Unlikelihood
REV1
Rebate Verified
Explanation:
RES1 Rebate, REA1 Rebate Accruals, and RES6 Rebate are the condition types for which you
maintain data records in the condition contract maintenance (see chapters Specify CCRelevance for Condition Types, Define Condition Type Groups and Assign Condition Types to
Condition Type Groups).
RES3 Rebate TPM and REA3 Rebate TPM Accruals are the corresponding condition types for
the TPM integration.
All other condition types are (only) used in the pricing procedures for the settlement documents
– see chapter Define Pricing Procedures.
14
Condition type RES1 Rebate
15
Explanation RES1: You use this condition type in a condition contract to maintain sales rebate
conditions in the usual sales rebate scenarios. This condition type uses the delivered access
sequence RE01 Sales Rebate.
Condition type REJ1 Rebate Adjustment (not shown parameters have an initial value) and REV1
Rebate Verified (same parameter values, not shown as screenshot)
Explanation REJ1: You use this condition types in a condition contract to maintain a correction
for the sales rebate amount. This condition type uses the delivered access sequence RE01
Sales Rebate.
16
Condition type REA1 Rebate Accruals
Explanation REA1: You use this condition type in a condition contract to maintain accruals
conditions in the usual sales rebate scenarios. Therefore, note that the Accruals checkbox is
17
selected in the Control Data 2 group box. This condition type uses the delivered access
sequence REA1 Sales Rebate Accruals.
Condition type RES3 Rebate TPM (not shown parameters have an initial value)
Explanation RES3: You use this condition type in a condition contract to maintain rebate
conditions in the TPM scenarios. This condition type uses the delivered access sequence TPCC
Trade Promo Condition Contract. All other parameters are identical to RES1 Rebate.
Condition type REA3 Rebate TPM Accruals (not shown parameters have an initial value)
Explanation REA3: You use this condition type in a condition contract to maintain accruals
conditions in the TPM-related sales rebate scenarios. This condition type uses the delivered
access sequence TPCA Trade Promo Cond Contract Accr. All other parameters are identical to
REA1 Rebate Accruals.
18
Condition type REBV Rebate Business Vol. (not shown parameters have an initial value)
Explanation REBV: You use this condition type in a settlement run for the business volume, see
pricing procedures A10005, A10006 and A10007 in chapter Define Pricing Procedures. It's a
manual condition type without access sequence because the condition amount – accordingly,
the calculation type is B Fixed Amount – is determined by the settlement program.
To control the transfer to the pricing procedures in the settlement run, you specify this condition
type in the Amount Fields view of a profile for business volume determination (see chapter
Define and Configure Profiles for Business Volume Determination).
19
Condition type REBD Rebate BusVol Delta (not shown parameters have an initial value)
Explanation REBD: You use this condition type in a condition contract to maintain a business
volume correction. This condition type uses the delivered access sequence RE01 Sales Rebate.
Other parameters are identical to REBV Rebate Business Vol.
20
Condition type RES2 Rebate PartSettl Rev (not shown parameters have an initial value)
Explanation RES2: You use this condition type in a settlement run for the total amount of
previous partial settlements, see pricing procedures A10005, A10006, and A10007 in chapter
Define Pricing Procedures. It's a manual condition type without access sequence because the
condition amount – accordingly, the calculation type is B Fixed Amount – is determined by the
settlement program. To control the transfer to the pricing procedures in the settlement run, you
specify this condition type in a condition contract type (see chapter Specify Settlement Settings
for Condition Contract Types). Not shown parameters have an initial value.
Condition type RES4 TPM PartSettl Rev plays the same role for the TPM-related sales rebate
scenarios and has parameter values identical with those in RES2.
21
Condition type REA2 Rebate Accruals Rev
Explanation REA2: You use this condition type in a settlement run for the amount of the accruals
reversal, see pricing procedures A10005 and A10007 in chapter Define Pricing Procedures.
Therefore, note the Accruals checkbox in the Control Data 2 group box. It's a manual condition
type without access sequence because the condition amount – accordingly, the calculation type
22
is B Fixed Amount – is determined by the settlement program. To control the transfer to the
pricing procedures in the settlement run, you specify this condition type in the condition type
group for accruals (see chapter Define and Configure Condition Type Groups for Accruals).
Condition type REA4 TPM Accruals Rev plays the same role for the TPM-related sales rebate
scenarios and has parameter values identical with those in REA2.
Condition type REA5 Rebate AccrualsSettl has the same parameter values as REA2. You use
this condition type in a settlement run for the amount of the accruals index update, see pricing
procedures A10005 and A10007 in chapter Define Pricing Procedures. All parameter values
are identical with values for REA2. So, note the Accruals checkbox in the Control Data 2 group
box. It’s a manual condition type without access sequence because the condition amount is
determined by the settlement program. To control the transfer to the pricing procedures in the
settlement run, you specify this condition type in a condition contract type (see chapter Specify
Settlement Settings for Condition Contract Types).
23
Condition type RED1 Rebate Accruals (not shown parameters have an initial value)
Explanation RED1: You use this condition type in a settlement run to determine the accruals
amount for delta accruals, see pricing procedure A10006 in chapter Define Pricing Procedures.
It is not an accruals condition type itself - the Accruals checkbox in the Control Data 2 group box
is not selected – but it uses the accruals condition type REA1 as reference – see corresponding
entries in the Master Data group box. Such a condition type is required in the pricing procedure
as accruals conditions are not considered in the net amount determination. The net amount is
used for the accruals update.
24
Condition type RED3 Rebate TPM Accruals (not shown parameters have an initial value)
Explanation RED3: This condition type plays the same role in the TPM-related sales rebate
scenarios as RED1 for normal sales rebates. It uses the accruals condition type REA3 TPMrelated sales rebate scenario as reference, and the access sequence is TPCC Trade Promo
Condition Contract. Other parameter values are identical with those in RED1.
25
Condition type RED2 Rebate Accr Total (not shown parameters have an initial value)
Explanation RED2: You use this condition type in a delta accruals settlement run for the total
amount of already reversed accruals, see pricing procedure A10006 in chapter Define Pricing
Procedures. It’s a manual condition type without access sequence because the condition
amount is determined by the settlement program. To control the transfer to the pricing
procedures in the settlement run, you specify this condition type in the condition type group for
accruals (see chapter Define and Configure Condition Type Groups for Accruals).
Condition type RED4 TPM Accr Total plays the same role for the TPM-related sales rebate
scenarios and has parameters values identical with those in RED2.
As an alternative to condition type triple RES1, REA1, and RED1, you can also use the triple
RES6, REA6, and RED6.
Condition type RES6 Rebate has the same parameter values as RES1. You use this condition
type in a condition contract for usual sales rebate scenarios to maintain sales rebate conditions
and corresponding accruals in one condition record.
26
Condition type REA6 Rebate Accruals
Explanation REA6: You use this condition type in the pricing procedure of transactional
documents (billing documents) to control the accruals posting for sales rebate condition RES6.
Therefore, note that the Accruals checkbox is selected in the Control Data 2 group box and that
27
RES6 is maintained as reference condition type. This condition type uses the delivered access
sequence REA1 Sales Rebate Accruals. See also chapter Specify CC-Relevance for Condition
Types to check the special settings for the Usage parameter for condition types RES6 and
REA6.
Condition type RED6 Rebate Accruals (not shown parameters have an initial value)
Explanation RED6: You use this condition type in a settlement run to determine the accruals
amount for delta accruals, see pricing procedure A10006 in chapter Define Pricing Procedures.
It is not an accruals condition type itself - the Accruals checkbox in the Control Data 2 group box
is not selected – but it uses the accruals condition type RES6 as reference – see corresponding
entries in the Master Data group box. Such a condition type is required in the pricing procedure
as accruals conditions are not considered in the net amount determination. The net amount is
used for the accruals update.
28
Condition type RED5 Cost Recogn. Adjust (not shown parameters have an initial value)
Explanation RED5: You use this condition type in a settlement run for delta accruals to perform
the cost recognition adjustment to different fiscal periods of a one-time sales rebate payment
(as for instance in a fixed amount agreement) at the beginning of the condition contract validity.
29
Condition type RETX Rebate Tax (not shown parameters have an initial value)
Explanation RETX: In scenarios in which you regard sales rebate agreements as a kind of
service, you use this condition type in a settlement run for the tax condition, see pricing
procedure A10005 in chapter Define Pricing Procedures. This condition type uses the delivered
access sequence RET1 Sales Rebate Tax.
30
Condition type RETT Rebate Tax Trigger (not shown parameters have an initial value)
Explanation RETT: In scenarios with goods-related taxation of the sales rebate amount, you use
this condition type in a settlement run for the tax condition, see pricing procedure A10007 in
chapter Define Pricing Procedures. This condition type uses the delivered access sequence
RET2 Sales Rebate Tax Trigger.
31
Condition type RETI Rebate Tax Inbound
Explanation RETI: Not shown parameters have an initial value. In scenarios with A/P settlement
of the sales rebate amount, you use this condition type in a settlement run for the tax condition,
see pricing procedures A10005 and A10007 in chapter Define Pricing Procedures. As to the
purpose, this condition type has condition type RET0 Settlement Tax from application M
Purchasing as reference. This condition type uses the delivered access sequence RET3 Rebate
Inbound Tax.
32
Condition type RENT Rebate Net Amount
Explanation RENT: Not shown parameters have an initial value. You use this condition type for
the business volume in manually created settlement documents, see pricing procedure A10008
in chapter Define Pricing Procedures.
33
Condition type AS01 Tax trigger
Explanation AS01: Not shown parameters have an initial value. You use this condition type as
trigger for the tax determination in manually created settlement documents, see pricing
procedure A10008 in chapter Define Pricing Procedures.
Condition class G Tax Classification ensures to determine the tax conditions based on the tax
code of the item. Tax conditions are not determined via pricing; they are taken from the
corresponding tax code determination in FI directly.
34
Condition type MWAS Output Tax
Explanation MWAS: Not shown parameters have an initial value. You use this condition type to
adopt the result of the output tax determination triggered by RETT or AS01 (see chapter Define
Pricing Procedures).
Condition type MWVS Input Tax has parameters values identical with those in MWAS and you use
this condition type to adopt the result of the input tax determination triggered by RETT or AS01
(see chapter Define Pricing Procedures).
35
Condition type REU1 Rebate Unlikelihood (not shown parameters have an initial value)
Explanation REU1: You use this condition types in a condition contract to handle the
unlikelihood for a sales rebate payment. This condition type uses the delivered access
sequence RE01 Sales Rebate.
36
Condition type REAT Rebate TotalAccruals
Explanation REAT: You use this condition type for the posted accruals in manually created
settlement documents, see pricing procedure A10008 in chapter Define Pricing Procedures.
37
2.1.4. Specify CC-Relevance for Condition Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract
Conditions → Sales → Specify CC-Relevance and Copy Control
for Condition Types
2. Check the Relevant for Condition Contract Determination in Pricing checkbox and the
Usage parameter for the following condition types:
Explanation: The Relevant for Condition Contract Determination in Pricing checkbox controls
that a condition type is relevant for the determination of applicable condition contracts during pricing
for a transactional document.
2.1.5. Define Condition Type Groups
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract
Conditions → Sales → Define Condition Type Groups
38
2. Check the following condition type groups 0S01 Sales Rebate, 0S02 Sales Rebate
MultCus, and 0ST1 Sales Rebate TPM.
Explanation:
You assign a condition type group to a condition contract type (see chapter Define Condition
Contract Types).
Condition type group 0S01 Sales Rebate is assigned to condition contract types for contracts
with one customer – that are 0S01 Sales Rebate, 0S03 Sales Rebate - 2Step, 0SG1 Sales
Rebate Goods Related, and 0SG3 Sales Rebate Goods Related - 2Step.
Condition type group 0S02 Sales Rebate MultCus is assigned to condition contract types for
condition contracts valid for multiple customers – that are 0S02 Sales Rebate - Multiple
Customers, 0S04 Sales Rebate - Mult. Customers - 2Step, 0SG2 Sales Rebate Goods Rel.Mult. Customers, and 0SG4 Sales Rebate Goods Rel- MultCust - 2Step.
Condition type group 0ST1 Sales Rebate TPM is assigned to condition contract types for the
TPM integration – that are 0ST1 Sales Rebate TPM, 0ST2 Sales Rebate TPM - Multiple
Customers, 0ST3 Sales Rebate TPM with Claims, and 0ST4 Sales Rebate TPM with Claims Mult Cust.
2.1.6. Assign Condition Types to Condition Type Groups
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract
Conditions → Sales → Assign Condition Types to Condition
Type Groups
2. Check the entries for condition type groups 0S01 Sales Rebate, 0S02 Sales Rebate
MultCus, and 0ST1 Sales Rebate TPM. Note value A Condition Contract Number Must
Appear in Access Sequence is selected in column Usage of Condition Contract Number for
Condition Type.
39
3. Select an entry and choose Condition Types for Group in the Dialog Structure frame.
Check the assigned condition types as shown below.
40
Explanation:
In condition type groups 0S01 and 0S02, you assign condition type RES1 Rebate for
maintaining a rebate condition in the condition contract and condition type REA1 Rebate
Accruals for maintaining accruals conditions.
Additionally, you assign condition types REBD Rebate BusVol Delta, REJ1 Rebate Adjustment,
and REV1 Rebate Verified in order to adjust settlement data after negotiations with the business
partner of the condition contract.
41
You also assign condition type REU1 Rebate Unlikelihood for the likelihood of rebate payments.
In condition type group 0S01, you use three maintenance levels – Condition Contract, Condition
Contract / Material, and Condition Contract / Material Group 1 / MG2 / MG3 / MG4 /MG5 – for
condition types RES1 and REA1 in the condition contract. The maintenance levels correspond
with the accesses (to condition tables 4AB, 4AN, and 163, respectively) of the access sequence
RE01 (REA1) assigned to condition type RES1 (REA1).
In condition type group 0S02, you can see the additional maintenance level for Condition
Contract / Customer so that you can maintain variable rebate and accrual conditions for different
customers.
In condition type group 0STI, you can see condition types RES3 and REA3 with the additional
maintenance level for product hierarchies.
2.1.7. Define Account Keys
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Account Determination → Revenue Account Determination
(SD) → Define Account Keys for Revenue Account
Determination
2. Check account key 0S1 Rebate Sales as shown below.
Explanation:
The account key 0S1 Rebate Sales is used in the pricing procedures to control the account
determination for rebate and accrual condition types. The assignment of accounts for the Cloud
releases is described in chapter Assign G/L Accounts.
2.1.8. Define Pricing Procedures
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Sales (SD) → Define Pricing Procedures
42
2. Check the pricing procedures A10005 Rebate (Germany), A10006 Rebate Delta
Accrual(Germany), A10007 Rebate (Goods Rel.) (Germany), and A10008 Rebates Manual
(Germany) as shown below.
3. Select an entry and choose Procedures - Control Data in the the Dialog Structure frame.
Check the steps in the pricing procedure as shown below.
Pricing procedure A10005 Rebates (Germany)
Explanation:
An objective when creating the standard configuration was to avoid unnecessary duplication of
objects. Therefore, pricing procedures A10005, A10006, and A10007 contain the conditions for
both, the usual sales rebate scenarios and the TPM-related sales rebate scenarios. However,
you can simply ignore the TPM-related condition types in a non-TPM sales rebate scenario, and
vice versa. The simplified pricing procedures are part of the Cloud delivery as here the TPM
solution is yet not included. S/4HANA Cloud contains more simple pricing procedures without
43
TPM condition types, because the TPM solution is not yet available in S/4HANA Cloud. In
addition, S/4HANA Cloud does not include the alternative rebate conditions and condition types
for accruals clearing. As an example, the simplified A10005 pricing procedure is shown at the
end of this section.
The calculation logic for pricing procedure A10005 is the following:
Step 100, condition type REBV Rebate Business Vol.
Contains the business volume amount that the system transfers to the pricing procedure in the
settlement run. Accordingly, the Manual checkbox is selected for this condition. In addition, the
Statistics checkbox is selected as the business volume amount shall not be considered for the
net amount. The business volume amount is stored in subtotal 7. The print ID is A Total:
General
Step 105, condition type REBD Rebate BusVol Delta
In this step, the system determines the condition record with a fixed amount that you have
maintained for condition type REBD Rebate BusVol Delta in the condition contract to adjust the
business volume amount. The condition record is determined with access sequence RE01.
Therefore the Manual checkbox is not selected.
Step 200, condition type RES1 Rebate:
The condition basis for the rebate amount calculation is line 100 and line 105 (see From Step
and To Step column). Base formula 214 in column Alt.Cond.Base Value controls that in case of
a fix amount rebate condition the condition base value is positive (see formula documentation).
The account for the FI posting is determined using account key 0S1 (see column Account Key).
The calculated value is stored in subtotal 1. The print ID is A Total: General
Step 201, condition type RES6 Rebate:
RES6 is the alternative condition type to RES1. So, explanation for condition type RES1 is valid
here as well.
Step 204, condition type REJ1 Rebate Adjustment
In this step, the system determines the condition record with a fixed amount that you have
maintained for condition type REJ1 Rebate Adjustment in the condition contract. You use this
condition type to adjust the rebate amount calculated with condition type RES1 in line 200.
Step 205, condition type REV1 Rebate Verified
In this step, the system determines the condition record with a fixed amount that you have
maintained for condition type REV1 Rebate Verified in the condition contract. You use this
condition type to invalidates the previous rebate calculation. This invalidation is based on an
exclusion rule - see chapter Condition Exclusion For Groups Of Conditions.
Step 210, condition type RES3 Rebate:
Similar to step 200, now for TPM-related scenarios.
Step 300, condition type RES2 Rebate PartSettl Rev:
Contains the total amount of previous partial settlements. The system determines this amount in
the settlement run and transfers it to the pricing procedure. Accordingly, the Manual checkbox is
44
selected for this condition. The total amount of previous partial settlements is stored in subtotal
3. The print ID is A Total: General
Step 310, condition type RES4 Rebate:
Similar to step 300, now for TPM-related scenarios.
Step 399, Net Amount
Contains the net rebate amount which is the actual calculated rebate amount minus the amount
of previously settled rebates. The print ID is A Total: General
Step 400, tax condition type RETX Rebate Tax
According to requirement 76 LO-AB: Tax det Cust, this condition type is valid only for an A/R
settlement (the Price Determination parameter in the relevant settlement process type is
Customer Side, see chapter Define Settlement Process Types). The tax value is determined
using the corresponding access sequence. The condition basis is the net amount of the
previous line. The print ID is A Total: General.
Step 410, tax condition type RETI Rebate Tax Inbound
According to requirement 66 LO-AB: Tax det Suppl, this condition type is valid only for an A/P
settlement (the Price Determination parameter in the relevant settlement process type is
Supplier Side, see chapter Define Settlement Process Types). The tax value is determined
using the corresponding access sequence. The condition basis is the net amount of the
previous line. The print ID is A Total: General.
Step 499, Gross Amount
Contains the gross amount as sum of net amount and tax amount. The calculated gross amount
is stored in subtotal 9 which copies the value to KOMP-BRTWR (gross value). Print ID is A Total:
General
Step 800, condition type REA2 Rebate Accruals Rev
Contains the amount of the accruals reversal. The system determines this amount in the
settlement run and transfers it to the pricing procedure. Accordingly, the Manual checkbox is
selected for this condition. In addition, the Statistics checkbox is selected as the amount of the
accruals reversal is not relevant for the total net amount. Account key 0S1 (see column
Accruals) is used to determine the accruals account for the FI posting. The calculated value of
the line is stored in subtotal 2.
Step 810, condition type REA4 TPM Accruals Rev
Similar to step 800, now for TPM-related scenarios.
Step 850, condition type REA5 Rebate Accruals Rev
Contains the amount of the excessive accruals amount that shall be written back to accruals
index table WCOCOF. The amount is calculated by condition value formula 91 CCS: Accr. in
Settl, entered in column Alt.Calculation Type, as the difference between the absolute value of
subtotal 2 and the net value.
Step 900, Effective Value
45
Contains the effective value which in fact equals the gross amount. The calculated amount is
stored in subtotal S (KOMP-EFFWR).
Simplified pricing procedure A10005 Rebates (Germany) as part of the Cloud delivery
46
Pricing procedure A10006 Rebates Delta Accrual(Germany)
Explanation: The calculation logic for pricing procedure A10006 is the following:
Step 100, condition type REBV Rebate Business Vol.
Contains the business volume amount that the system transfers to the pricing procedure in the
settlement run. Accordingly, the Manual checkbox is selected for this condition. In addition, the
Statistics checkbox is selected because the business volume amount should not be considered
in the calculation of the net amount. The business volume amount is stored in subtotal 7.
Step 105, condition type REBD Rebate BusVol Delta
In this step, the system determines the condition record with a fixed amount that you have
maintained for condition type REBD Rebate BusVol Delta in the condition contract to adjust the
business volume amount. The condition record is determined with access sequence RE01.
Therefore, the Manual checkbox is not selected.
Note:
Step 200 (condition type RES1) and step 201 (condition type RED1) reflect some flexibility in
how accruals are handled during condition contract processing. The configuration has been
done to avoid the creation of two different pricing procedures which would lead to a duplication
of some other parameters (settlement document type, condition contract type).
If you do not want to differentiate the percentages for rebates and accruals, it is sufficient to just
maintain the rebate conditions with condition type RES1 and to also use the condition type RES1
for the accruals posting.
Step 201, condition type RED1 Rebate Accruals represents the usual accruals amount
determination with the accruals conditions. Here, the accrual condition type REA1 is not used
directly. Instead a 'normal' condition type, RED1 is used for which the accruals condition type
REA1 is assigned as reference.
To avoid double-calculation of the accruals amount in these two steps, a condition exclusion
group containing condition types RES1 and RED1 has been defined and assigned to pricing
procedure A10006 (see chapter Condition Exclusion For Groups Of Conditions). Like this, only
47
the condition type with the higher percentage is applied. A typical scenario in this context is that
at the beginning of a contract the accruals percentage is higher than the rebate percentage
derived from a low scale level. During the term of validity, the rebate percentage can become
higher because of a higher scale level.
Step 200, condition type RES1 Rebate
Represents a percentage condition that is determined using the corresponding access
sequence. The condition basis for the rebate amount calculation is from step 100 (see the From
Step and To Step column). Base formula 214 in column Alt.Cond.Base Value is only required
for fixed amount condition contracts (see formula documentation), therefore it is not relevant for
the sales rebate scenarios described here. The account for the FI posting is determined using
account key 0S1 (see column Account Key). The calculated value is stored in subtotal 1.
Step 201, condition type RED1 Rebate Accruals
Contains the percentage condition type RED1 Rebate Accruals which is determined using the
corresponding access sequence. The condition basis for the rebate amount calculation is from
step 100 (see the From Step and To Step column). Base formula 214 in column Alt.Cond.Base
Value is required for the sales rebate scenarios to adjust the sign of the condition value (see
formula documentation). The account for the FI posting is determined using account key 0S1
(see column Account Key). The calculated value is stored in subtotal 1.
Note: The system does not consider accruals condition types for the net amount determination
in the pricing procedure. However, this is required for the accruals amount. To enable the
consideration for the net amount, a 'normal' condition type is used instead which references the
actual accruals condition type REA1. Condition type RED1 has the same access sequence as
REA1.
Step 202, condition type RES6 Rebate
Same explanation as for step 200 with alternative condition type.
Step 203, condition type RED6 Rebate Accruals
Same explanation as for step 201 with alternative condition type.
Step 204, condition type REJ1 Rebate Adjustment
In this step, the system determines the condition record with a fixed amount that you have
maintained for condition type REJ1 Rebate Adjustment in the condition contract. You use this
condition type to adjust the rebate amount calculated with condition type RES1 in line 200, or
RED1 in line 201, or RED3 in line 202.
Step 205, condition type REV1 Rebate Verified
In this step, the system determines the condition record with a fixed amount that you have
maintained for condition type REV1 Rebate Verified in the condition contract. You use this
condition type to invalidates the previous rebate calculation. This invalidation is based on an
exclusion rule - see chapter Condition Exclusion For Groups Of Conditions.
Step 208, condition type RED5 Rev. Recogn. Adjust
In this step, the system uses condition type RED5 to perform the cost recognition adjustment to
different fiscal periods of a one-time rebate payment at the beginning of the condition contract
validity.
Step 210, condition type RES3 Rebate TPM
48
Simlar to step 200, now for TPM-related scenarios.
Step 211, condition type RED3 Rebate TPM Accruals
Simlar to step 201, now for TPM-related scenarios.
Step 250, condition type REU1 Rebate Unlikelihood
If the minimum business volume turnover is not reached (in the non-TPM scenarios), no
accruals should be created and existing accruals should be reversed. This is controlled by this
condition type in the following way: you maintain a condition record of 100% in the condition
contract. The sign is inversed by base formula 214 that you can see in column Alt.Cond.Base
Value. Lines 200 to 205 representing the accruals amount calculation form the condition basis
for the amount calculation.
Step 300, condition type RES2 Rebate PartSettl Rev
Contains the total amount of previous partial settlements. The system determines this amount in
the delta accruals settlement run and transfers it to the pricing procedure. Accordingly, the
Manual checkbox is selected for this condition type. The account for the FI posting is
determined using account key 0S1 (see column Account Key).The total amount of previous
partial settlements is stored in subtotal 3.
Step 310, condition type RES4 TPM PartSettl Rev
Simlar to step 300, now for TPM-related scenarios.
Step 350, condition type RED2 Rebate Accr Total
Contains the total amount of already reversed accruals. The system determines this amount in
the delta accruals settlement run and transfers it to the pricing procedure. Accordingly, the
Manual checkbox is selected for this condition type. The account for the FI posting is
determined using account key 0S1 (see column Account Key).The total amount of already
reversed accruals is stored in subtotal 2.
Step 360, condition type RED4 TPM Accr Total
Simlar to step 350, now for TPM-related scenarios.
Step 399, Net Amount
Contains the net amount as calculated by condition value formula 2 Net value.
Step 499, Gross Amount
Contains the gross amount as the sum of the net and tax amount calculated by condition value
formula 4 Net value + tax. The calculated gross amount is stored in subtotal 9 which copies the
value to KOMP-BRTWR (gross value).
Step 900, Effective Value
Contains the effective value which in fact equals the gross amount as also formula 4 is applied.
The calculated amount is stored in subtotal S (KOMP-EFFWR).
Pricing procedure A10007 Rebates (Goods Rel.) (Germany)
49
Explanation: Compared to pricing procedure A10005, the calculation logic for pricing procedure
A10007 only differs in the way how the tax amount is determined:
Step 400, condition type RETT Rebate Tax Trigger
Because of the condition class G Tax Classification, the condition type triggers the determination
of the tax percentage according to the settings in the tax calculation procedure - see first
screenshot below this section for the tax calculation procedure TAXD in Germany. The result of
this tax percentage determination is then used to fill the condition value of the relevant line of
steps 410 or 420. The condition basis for the tax calculation is the net amount of steps 200 to
310.
See the second screenshot for tax percentage determination: For tax code V1, for example, the
tax type Input Tax is relevant and the corresponding condition type of this line is MWVS so that
step 410 in the settlement pricing procedure is relevant. The data transfer only works when
relevant condition types for taxes from the tax calculation procedure are included in the pricing
procedure for condition contract settlement (in our example we do not consider tax type Travel
Expenses from the tax calculation procedure with condition type MWRK.)
The requirement formula 69 CCS: Tax Trigger controls that this condition type becomes active
only when the system could not determine a tax code from business volume data - e.g. because
there is no business violume for a certain settlement item - so that the tax code is determined
from condition records.
Step 401, condition type AS01 Tax trigger
This tax trigger condition type is complementary to condition type RETT. The requirement
formula 69 CCS: Tax Trigger controls that this condition type is only active when the system
has determined a tax code from business volume data. And because the tax code comes from
business volume data, this condition type does not have an access sequence to determine the
tax code from condition records.
50
Also here, the system fills the condition value of the relevant line of step 410 or 420 with the
result of the tax percentage determination from the tax calculation procedure.
Note: In this couple of condition types RETT and AS01, condition type RETT acts as a fallback
condition type when there is no business volume for a settlement item. One might think that
condition type RETT is redundant because the tax calculation in the case of no business volume
will return a tax amount of 0. However, this condition type is required because the tax
percentage determination triggered by AS01 without any tax code can lead to a program error.
Step 410, condition type MWVS Input Tax
Adopts the result of the tax percentage determination triggered by condition type RETT or AS01.
Step 420, condition type MWAS Output Tax
Adopts the result of the tax percentage determination triggered by condition type RETT or AS01.
Tax calculation procedure TAXD Sales Tax - Germany
Maintenance of tax rate for tax code V1 19% domestic input tax
Pricing procedure A10008 Rebates Manual (Germany)
51
Explanation: Again, to limit the number of delivered objects, this pricing procedure is used for
two contexts: the entry of a settlement document for an external invoice sent by a customer, and
the ‘internal’ creation of a settlement document as part of the TPM process. Accordingly, this
procedure combines two types of tax amount determination. For an external invoice tax data is
copied from the manual entries in the settlement document. For the internal creation, the tax
rate is determined from condition records. Requirements 65 LO-AB: Tax entry and (76 LO-AB:
Tax det Cust or 66 LO-AB: Tax det Suppl ) establish an either(AS01)-or(RETX, RETI) logic.
The calculation logic for pricing procedure A10008 is the following:
Step 100, condition type RENT Rebate Net Amount
The condition value for this step is filled with the net value you entered in the settlement
document item. This data transfer is controlled by the condition value formula 251 in the
Alt.Calculation Type column.
Step 400, condition type AS01 Tax trigger
This pricing step is used in the scenario with an external invoice. Requirement 65 LO-AB: Tax
entry checks a control parameter set before by the Settlement Management program that
reading conditions is not required. The functionality of this condition type has already been
explained for pricing procedure A10002.
Step 410, condition type MWVS Input Tax
Adopts the result of the tax percentage determination triggered by condition type AS01 for
purchasing-sided manual settlement documents.
Step 420, condition type MWAS Output Tax
Adopts the result of the tax percentage determination triggered by condition type AS01 for
sales-sided manual settlement documents.
Step 450, condition type RETX Rebate Tax
According to requirement 76 LO-AB: Tax det Cust, this condition type is only valid for an A/R
settlement (compare details for A10005). The tax value is determined using the corresponding
access sequence. The condition basis is the net amount of line 100.
Step 460, condition type RETI Rebate Tax Inbound
According to requirement 66 LO-AB: Tax det Suppl, this condition type is only valid for an A/P
settlement (compare details for A10005). The tax value is determined using the corresponding
access sequence. The condition basis is the net amount of line 100.
Step 499, Gross Amount
52
Contains the gross amount as the sum of the net and tax amount calculated by condition value
formula 4 Net value + tax. The calculated gross amount is stored in subtotal 9 which copies the
value to KOMP-BRTWR (gross value).
Step 900, Effective Value
Contains the effective value which in fact equals the gross amount. The calculated amount is
stored in subtotal S (KOMP-EFFWR).
Step 901, condition type REAT Rebate TotalAccruals
Contains the posted accruals as basis for the automatic distribution of the manually settlement
amount to business objects in accordance with the accruals posting. This line is marked as
subtotal 6 (see also Specify General Settings for Condition Contract Settlement).
Note that for this automatic distribution, you also have to select 3 Distribition based on Accruals
(CCM) for the Control for Document Item Distribution parameter of a settlement document type.
However, in the configuration delivered as of standard – settlement document type 0S32 Sales
Rebate Manual – the distribution is not active.
Step 950, condition type REA5 Rebate Accruals Settl
Currently, this step serves as placeholder for a future enhancement.
Pricing procedure A10016 Rebates ManDeltaAccr (Germany)
Explanation: The calculation logic for pricing procedure A10016 is the following:
Step 100, condition type RENT Rebate Net Amount
The condition value for this step is filled with the net value you entered in the settlement
document item. This data transfer is controlled by the condition value formula 251 in the
Alt.Calculation Type column.
Step 499, Gross Amount
Contains the gross amount as the sum of the net and tax amount calculated by condition value
formula 4 Net value + tax. The calculated gross amount is stored in subtotal 9 which copies the
value to KOMP-BRTWR (gross value).
Step 900, Effective Value
Contains the effective value which in fact equals the gross amount. The calculated amount is
stored in subtotal S (KOMP-EFFWR).
53
Pricing procedure A10019 Rebates Manual Goods (Germany)
Explanation: The calculation logic for pricing procedure A10019 is the following:
Step 100, condition type RENT Rebate Net Amount
The condition value for this step is filled with the net value you entered in the settlement
document item. This data transfer is controlled by the condition value formula 251 in the
Alt.Calculation Type column.
Step 400, condition type AS01 Tax trigger
This pricing step is used in the scenario with an external invoice.
Step 401, condition type RETT Rebate Tax Trigger
This tax trigger condition type is complementary to condition type AS01.
Also here, the system fills the condition value of the relevant line of step 410 or 420 with the
result of the tax percentage determination from the tax calculation procedure.
Step 410, condition type MWVS Input Tax
Adopts the result of the tax percentage determination triggered by condition type AS01 for
purchasing-sided manual settlement documents.
Step 420, condition type MWAS Output Tax
Adopts the result of the tax percentage determination triggered by condition type AS01 for
sales-sided manual settlement documents.
Step 499, Gross Amount
Contains the gross amount as the sum of the net and tax amount calculated by condition value
formula 4 Net value + tax. The calculated gross amount is stored in subtotal 9 which copies the
value to KOMP-BRTWR (gross value).
Step 900, Effective Value
Contains the effective value which in fact equals the gross amount. The calculated amount is
stored in subtotal S (KOMP-EFFWR).
Step 901, condition type REAT Rebate TotalAccruals
Contains the posted accruals as basis for the automatic distribution of the manually settlement
amount to business objects in accordance with the accruals posting. This line is marked as
subtotal 6 (see also Specify General Settings for Condition Contract Settlement).
54
Note that for this automatic distribution, you also have to select 3 Distribition Based on Accruals
(CCM) for the Distribution Category for Document Items parameter of a settlement document
type. However, in the configuration delivered as of standard – settlement document type 0SG2
Sales Rebate Goods Manual Credit to Custl – the distribution is not active.
Step 950, condition type REA5 Rebate AccrualsSettl
Currently, this step serves as placeholder for a future enhancement.
2.1.9. Condition Exclusion For Groups Of Conditions
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Sales (SD) → Condition Exclusion For Groups Of
Conditions
2. Choose activity Define Condition Exclusion Groups on the dialog screen.
3. Check exclusion groups as shown below. Then choose Back (F3).
4. Choose activity Assign Condition Types to Exclusion Groups on the dialog screen.
5. Check assignment of condition types to exclusion groups as shown below.
Then choose Back (F3).
55
6. Choose activity Maintain Condition Exclusion for Pricing Procedures on the dialog screen.
7. Select pricing procedures A10005 to A10007 and check the assignment of exclusion rules
as shown below.
Explanation:
The condition exclusion procedure 1 for the three pricing procedures A10005/6/7 controls that
condition types RES1, RES3, RES6, and REJ1 are excluded when a condition record for REV1
has been defined in the condition contract.
Similarly, the condition exclusion procedure 2 for pricing procedure A10006 controls that
condition types RED1 and RED3 are excluded when a condition record for REV1 has been
defined in the condition contract.
56
The condition exclusion procedure 3 for pricing procedure A10006 has been configured to
enable the usage of one pricing procedure for two ways of calculating the accruals amount: a
calculation based on the 'normal' rebate condition and a calculation based on the accrual
condition - see explanation in chapter Define Pricing Procedures.
Note: The exclusion group 0S01 must contain the condition types RED1 / RED3 / RED6 used in
pricing procedure A10006 and not condition type REA1 / REA3 / REA6 for accruals (for REA1 /
REA3 you maintain entries in the condition contract) that is the reference condition type in
condition type RED1 / RED3 / RED6, respectively.
2.1.10. Define Document Schema Groups for Settlement
Document Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Define Document Schema Groups for Settlement
Document Types
2. Check document schema groups as shown below.
Explanation: The document schema groups are used in the pricing procedure determination as
explained in chapter Pricing Procedure Determination. You assign the document schema
groups to settlement document types (see chapter Define Settlement Document Types) so that
the different pricing procedures can be used for the settlement document types fulfilling different
purposes (partial settlement, delta accruals settlement, etc.).
Document schema group 0S Sales Rebate is used for the following settlement document types
(and the corresponding settlement document types for the document reversal and for the
corresponding alternative settlement document types):
0S12 (0S14) Sales Rebate (Reversal)
0S22 (0S24) Sales Rebate Parked (Reversal)
0S52 (0S54) Sales Rebate Proforma (Reversal)
0S62 (0S64) Sales Rebate Accruals Reversal (Reversal)
0S92 (0S94) Sales Rebate Collection (Reversal)
57
Document schema group 0T Sales Rebate DeltaAc is used for settlement document type 0S40
(0S44) Sales Rebate Delta Accruals (Reversal).
Document schema group 0U Sales Rebate GoodsRl is used for the following settlement
document types (and the corresponding settlement document types for the document reversal):
0SA2 (0SA4) Sales Rebate Goods Related (Reversal)
0SB2 (0SB4) Sales Rebate Goods Related Parked (Rev)
0SE2 (0SE4) Sales Rebate Goods Rel Proforma (Reversal)
0SF2 (0SF4) Sales Rebate Goods Rel Accruals Reversal (Sales Rebate Goods Rel Accruals
Rev Rev)
0SI2 (0SI4) Sales Rebate Goods Rel Collection (Rev)
Document schema group 0V Sales Rebate Manual is used for settlement document type 0S30
(0S34) Sales Rebate Manual (Reversal).
Document schema group 0G Sales Rebate Man DA is used for settlement document type 0S4B
(0S4D) Sales Rebate Manual Delta Accruals (Rev).
Document schema group 0_ Sales Rebate ManGood is used for settlement document type
0SG2 (0SG4) Sales Rebate Goods Manual Credit to Cust (Sales Rebate Goods Manual Credit
to C Rv).
2.1.11. Pricing Procedure Determination
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Pricing → Specify Pricing Procedure Determination
2. Choose activity Determination for Settlement Documents and Settlement Document Lists on
the dialog screen.
3. Check the entries as shown below.
Explanation:
Pricing procedure A10005 Rebates (Germany) intended for partial and final settlement is
assigned to document schema group 0S Sales Rebate – both for A/R and A/P settlement.
Pricing procedure A10006 Rebates Delta Accrual(Germany) intended for delta accruals
settlement is assigned to document schema group 0T Sales Rebate DeltaAc.
Pricing procedure A10007 Rebates (Goods Rel.) (Germany) intended for partial and final
settlement within the goods-related taxation scenarios is assigned to document schema group
0U Sales Rebate GoodsRl.
58
Pricing procedure A10008 Rebates Manual (Germany) intended for manual settlement
document entry is assigned to document schema group 0V Sales Rebate Manual – both for A/R
and A/P settlement.
Pricing procedure A10016 Rebates ManDeltaAccr (Germany) intended for delta accruals
settlement in manual settlement scenarios is assigned to document schema group 0G Sales
Rebate Man DA.
Pricing procedure A10019 Rebates Manual Goods (Germany) intended for goods related
settlement in manual settlement scenarios is assigned to document schema group 0_ Sales
Rebate ManGood.
2.1.12. Specify General Settings
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settlement →
Specify General Settings
2. Check the general settings.
Explanation: The setting for the Accruals Total in Manual Settlement parameter identifies the
condition type containing the posted accruals as basis for the automatic distribution of a
manually entered settlement amount (see also Define Pricing Procedures, pricing procedure
A10008).
59
2.2 Configure Condition Contract Maintenance
The configuration of Condition Contract Maintenance comprises two steps:
•
Configure parameters for condition contract types
•
Define condition contract types
2.2.1. Define Number Ranges
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Define Number Ranges
2. On the following Edit Intervals: Condition Contract, Object WCB_CC screen, choose
function Intervals and check the number range 01 as shown below.
Explanation:
Note: You assign number ranges to condition contract types. Number range 01 is assigned to
all condition contract types in the standard delivery.
However, it’s recommendable to differentiate number ranges according to the sales rebate
scenarios. This has been configured in the Cloud delivery.
Number ranges 1 to 19 have been reserved for condition contract types used in supplier rebate
scenarios. Number ranges 20 to 29 are intended for sales rebate condition contracts whereas
60
the number range 20 with a corresponding restricted interval is used for condition contract
types for one customer scenarios, which are 0S01 Sales Rebate, 0S03 Sales Rebate - 2Step,
0SG1 Sales Rebate Goods Related, 0SG3 Sales Rebate Goods Related - 2Step. Number range
21 is used for condition contract types for multiple customer condition contracts, which are
0S02 Sales Rebate - Multiple Customers, 0S04 Sales Rebate - Mult. Customers - 2Step, 0SG2
Sales Rebate Goods Rel.- Mult. Customers, 0SG4 Sales Rebate Goods Rel- MultCust - 2Step.
2.2.2. Define Condition Contract Categories
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Define Condition Contract Categories
2. Check condition contract category 0S Sales Rebate.
Explanation:
Note: You assign condition contract categories to condition contract types (see chapter Define
Condition Contract Types).
Condition contract category 0S Sales Rebate is used to bundle condition contracts for sales
rebates, for example, in reporting.
Currently, only one condition contract category is delivered as of standard. As soon as further
condition contract types for sales rebates and also purchasing rebates are delivered, the
condition contract category will become more important.
2.2.3. Define and Configure Field Status Groups for Header
Fields
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Define and Configure Field Status Groups for Header Fields
2. Check the field status groups with assigned fields as shown below.
61
62
Explanation:
You assign field status groups to condition contract types (see chapter Define Condition
Contract Types).
Field status group 0S01 Sales Rebate is assigned to condition contract types for condition
contracts with one customer, for example, 0S01 Sales Rebate.
Field status group 0S02 Sales Rebate - Multiple Customers is assigned to condition contract
types for condition contracts with multiple customers, for example, 0S02 Sales Rebate - Multiple
Customers.
Field status group 0S03 Sales Rebate TPM is assigned to condition contract types 0ST1 Sales
Rebate TPM and 0ST3 Sales Rebate TPM with Claims.
Field status group 0S04 Sales Rebate TPM - Multiple Customers is assigned to condition
contract types 0ST2 Sales Rebate TPM - Multiple Customers and 0ST4 Sales Rebate TPM with
Claims - Mult Cust.
Field status group 0S01 hides the purchasing-related fields that are not relevant for 0S01 Sales
Rebate condition contracts. As all three fields (EKORG Purchasing Organization, EKGRP
Purchasing Group, BUKRS Company Code) of the Purchasing tab page are hidden, the whole
tab page is hidden.
Field ACCESS_TYPE Access Type is hidden as currently only the value blank Exclusive out of
two options is supported.
Sales-related organizational fields (VKORG Sales Organization, VTWEG Distribution Channel,
SPART Division) are set as required entries.
63
Field AF_GROUP_CCS Amount Fields Group is set as required field. As a default, it is filled with
value 0S01 Sales Rebate using transfer group 0S01 Sales Rebate (compare chapter Specify
Settings for Transfer Manager).
In field status group 0S02, the sales related organizational fields (VKORG Sales Organization,
VTWEG Distribution Channel, SPART Division) are not set as required entries (that is they are not
included in the field status group) as these fields are usually determined in the settlement run.
Field status group 0S03 is similar to 0S01. Different is that field ACCESS_TYPE Access Type is
not part and, in addition, the calendar for final settlement is hidden as well.
In all four fild status groups the field PROCESS VARIANT Condition Contract Process Variant is
ready for input.
2.2.4. Define Text Determination Procedures
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Text Control → Define Text Determination Procedures
2. Check text determination procedure 0S Sales Rebate.
Explanation:
You assign text determination procedures to condition contract types (see chapter Define
Condition Contract Types). Text determination procedure 0S Sales Rebate is assigned to all
condition contract types.
Text determination procedure 0S Sales Rebate allows the user to enter texts on header level.
2.2.5. Specify Text Types for Text Determination Procedure
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Text Control → Specify Text Types for Text Determination
Procedure
64
2. Check the assignment of text types to text determination procedure 0S as shown below.
Explanation:
Client-independent text IDs 0S01 Internal Text, 0S02 External Text, 0S03 Text for Settlement
Document, and 0S04 External Text for Output/Forms that are assigned to text determination
procedure 0S Sales Rebate are delivered as of standard.
2.2.6. Define Check Groups
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Additional Checks → Define Check Groups
2. Check the check groups 0S01 Sales Rebate as shown below.
Explanation:
You assign check groups to condition contract types: 0S01 Sales Rebate is assigned to the
condition contract types that do not involve TPM, 0ST1 Sales Rebate TPM is assigned to
condition contract types for TPM integration (see chapter Define Condition Contract Types).
Currently, check groups 0S01 Sales Rebate and 0ST1 Sales Rebate TPM do not provide any
additional checks. However, it can be regarded as preparation for future releases to allow the
definition of customer-specific checks.
65
2.2.7. Specify Settings for Transfer Manager
Note: The settings for transfer event 75 Condition Contract Creation - Default Header Data are
relevant for the definition of condition contract types (see next chapter). Therefore this
Customizing activity is described now, starting with transfer event 75. However, to avoid
repeating this Customizing activity at other places in this document, the settings made for other
transfer events – mostly relevant for the settlement document types – are already described
here (in alphanumeric order).
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Documents → Specify Settings for Transfer Manager
2. Choose activity Define Transfer Groups.
3. Select event 75 Condition Contract Creation - Default Header Data and choose Transfer
Groups in the Dialog Structure frame. Check transfer group 0S01 Sales Rebate and the
corresponding transfer rule as shown below.
66
4. Select event 18 Data Transfer - Collective Document Header and check transfer group
0S01 Sales Rebate and the corresponding transfer rules as shown below.
67
68
69
70
5. Select event 20 Pricing Data - Change Header (KOMK) Supplier Side and check transfer
group 0S01 Sales Rebate and the corresponding transfer rule as shown below.
71
6. Select event 22 Pricing Data - Change Item (KOMP) Supplier Side and check transfer
group 0S01 Sales Rebate and the corresponding transfer rules as shown below.
72
73
7. Select event 23 Pricing Data - Change Item (KOMP) Customer Side and check transfer
group 0S01 Sales Rebate and the corresponding transfer rules as shown below.
74
75
76
77
78
79
80
81
8. Select event 32 Accounting Document - Change Customer Line and check transfer groups
and the corresponding transfer rules as shown below.
82
83
84
85
9. Select event 3H Account Determination in Sales and Distribution (SD) and check transfer
group 0SC1 Sales Rebate Collection and the corresponding transfer rule as shown below.
86
10. Select event 63 Default Header Data - Document Reversal and check transfer group 0R
Rebate and the corresponding transfer rules shown below.
87
88
11. Select transfer event 6I Set Final Document Number and check transfer group 0S01 Sales
Rebate and the corresponding transfer rules as shown below.
89
90
12. Select transfer event 70 Condition Contract Settlement - Change Header Data and check
transfer group 0S01 Sales Rebate and the corresponding transfer rule as shown below.
91
92
93
13. Select transfer event 78 Accounting Document - Accruals Line Billing Document and check
transfer group 0S01 Sales Rebate and the corresponding transfer rule as shown below.
94
Explanation:
Transfer event 75 Condition Contract Creation - Default Header Data
Transfer group 0S01 Sales Rebate with transfer rule 1 sets the default value 0S01 Sales
Rebate for the amount field group when you create a new condition contract.
Transfer group 0S01 Sales Rebate is assigned to all condition contract types for sales rebate
scenarios without TPM (see chapter Define Condition Contract Types). Note: an amount field
group is not configured for sales rebate scenarios with TPM integration.
Transfer event 18 Data Transfer - Collective Document Header
Transfer group 0S01 Sales Rebate includes three transfer rules to copy the actual settlement
date (field KOMLFK-ACT_SETTLE_DATE), the start date of the settlement period (field KOMLFKSETTLE_START_DATE), and the settlement date type (field KOMLFK-SETTLE_DATE_TYPE)
from the single settlement document to the collective document.
95
Transfer event 20 Pricing Data - Change Header (KOMK) Supplier Side
Transfer group 0S01 Sales Rebate sets the fixed value 1 for field TAXK1 Tax Classification 1 for
Customer in the pricing communication structure KOMK Communication Header for Pricing for
the pricing feature in the creation process of a settlement document (compare chapter Define
Pricing Procedures).
Transfer group 0S01 Sales Rebate is assigned to all settlement document types related to sales
rebate scenarios with A/P settlement (see chapter Assign Transfer Groups to Settlement
Document Type).
Transfer event 22 Pricing Data - Change Item (KOMP) Supplier Side
Transfer group 0S01 Sales Rebate sets the fixed value 1 for field TAXM1 Tax Classification
Material in the pricing communication structure KOMP for the pricing feature in the creation
process of a settlement document (compare chapter Define Pricing Procedures). This reflects
that the sales rebate is regarded as service for the customer for which the full tax can be applied
independent from the tax classification of the material.
Transfer group 0S01 Sales Rebate is assigned to all settlement document types related to sales
rebate scenarios with A/P settlement (see chapter Assign Transfer Groups to Settlement
Document Type).
Transfer event 23 Pricing Data - Change Item (KOMP) Customer Side
Transfer group 0S01 Sales Rebate sets the fixed value 1 for field TAXM1 Tax Classification
Material in the pricing communication structure KOMP for the pricing feature in the creation
process of a settlement document (compare chapter Define Pricing Procedures). This reflects
that the sales rebate is regarded as service for the customer for which the full tax can be applied
independent from the tax classification of the material.
Transfer group 0S02 Sales Rebate Goods Related sets the tax code derived from the business
volume in the communication structure for item pricing.
Transfer group 0S01 Sales Rebate is assigned to all settlement document types related to sales
rebate scenarios with A/P settlement (see chapter Assign Transfer Groups to Settlement
Document Type).
Transfer event 32 Accounting Document - Change Customer Line
The purpose is to control that there is no split by tax code.
Transfer event 3H Account Determination in Sales and Distribution (SD)
Transfer group 0SC1 Sales Rebate Collection for transfer event 3H Account Determination in
Sales and Distribution (SD) sets the condition contract type in the account determination
communication structure of the collective settlement document item. This transfer group is
assigned to settlement document types for the collection of settlement documents (see chapter
Assign Transfer Groups to Settlement Document Type).
Transfer event 63 Default Header Data - Document Reversal
Transfer group 0R Rebate for transfer event 63 Default Header Data - Document Reversal
concerns the cancellation of settlement documents. Transfer rule 1 initializes the reference
document number (KOMLFK-XBLNR) for the cancellation settlement document. Transfer rule 2
copies the creation date of the settlement document to be cancelled to the document date
(KOMLFK-BLDAT) of the cancellation settlement document.
96
Transfer group 0R Rebate is assigned to all settlement document types for cancellation
(exception for the settlement document type to cancel manual settlement documents) used in
the sales rebate scenarios (see chapter Assign Transfer Groups to Settlement Document Type).
A related configuration setting is the field change group for cancellation. The field change group
0R Rebate allows to change fields KOMLFK-XBLNR and KOMLFK-BLDAT and is also assigned to
the settlement document types (see chapter Define Field Change Groups for Cancellation
Documents and Assign Transfer Groups to Settlement Document Type).
Transfer event 6I Set Final Document Number
The purpose of transfer event 6I in general is to cover localization requirements for filling the
final document number in certain fields of the journal entry.
Transfer group 0S01 Sales Rebate fills the payment reference field KIDNO with the reference
document number XBLNR (in transfer rule 1) plus a check digit (in transfer rule 2). Source value
class CL_WLF_TR_SV_PAYREF_CHECKNUM in transfer rule 2 determines the check digit for
the payment reference based on data of the company code’s country. With copy requirement
class CL_WLF_TR_REQ_PAYREF_CREATE you can restrict this copying logic to relevant
countries. For more information, see the class documentations.
Transfer group 0S01 is assigned to settlement document types for ‘normal’ settlement (see
chapter Assign Transfer Groups to Settlement Document Type). Note that for these settlement
document types the reference document number XBLNR is filled by the current settlement
document number (see chapter Define Settlement Document Types).
Transfer event 70 Condition Contract Settlement - Change Header Data
The purpose is described in the transfer rule’s comment.
Transfer event 78 Accounting Document - Accruals Line Billing Document
The purpose is to transfer the condition contract number to the assignment field of the journal
entry.
97
2.2.8. Define Condition Contract Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Define Condition Contract Types
2. Check the following condition contract types as shown and explained below.
Condition Contract Type
Description
0S01
Sales Rebate
0S02
Sales Rebate - Multiple Customers
0S03
Sales Rebate - 2Step
0S04
Sales Rebate - Mult. Customers - 2Step
0SG1
Sales Rebate Goods Related
0SG2
Sales Rebate Goods Rel.- Mult. Customers
0SG3
Sales Rebate Goods Related - 2Step
0SG4
Sales Rebate Goods Rel- MultCust - 2Step
0ST1
Sales Rebate TPM
0ST2
Sales Rebate TPM - Multiple Customers
0ST3
Sales Rebate TPM with Claims
0ST4
Sales Rebate TPM with Claims - Mult Cust
Condition Contract Type 0S01 Sales Rebate
98
Explanation: Fundamental for a condition contract used for sales rebates with a certain
customer – this is the scenario for which condition contract type 0S01 has been designed – is
that the type of contract partner is C Customer and the type of eligible partner is N No Eligible
Partner.
In this condition contract type, several previously defined parameters are specified: number
range 01, sales condition type group 0S01 Sales Rebate, text determination procedure 0S
Sales Rebate, field status group 0S01 Sales Rebate, check group 0S01 Sales Rebate, and
transfer group for default values in the contract header 0S01 Sales Rebate.
Value 1 Synchronous to Settlement Condition if no Scales Maintained for parameter Input
Control for Accrual Rate controls that the accrual rate is synchronized with the entered sales
rebate rate for sales rebate conditions with accruals such as RES6 Rebate.
You can also see that the approval process is not active and that changes on the user interface
are allowed. When a condition contract is in approval, you can only change the condition
contract status.
Tab page Post Processing Framework Actions will be hidden for corresponding condition
contracts as the Hide Tab Page for PPF Actions checkbox is selected.
The Enable Creation of Successor Contracts checkbox is selected as the creation of successor
condition contracts is included in the designed Sales Rebate scenario.
As the Contract Partner is Optional checkbox and the Condition Contract Validity is Optional
checkbox is not selected, you must specify the customer and condition contract validity when
you create a new condition contract.
99
Condition Contract Type 0S02 Sales Rebate – Multiple Customers
Explanation: There are three differences for condition contract type 0S02 Sales Rebate Multiple Customers compared with 0S01 Sales Rebate.
Fundamental for a condition contract used for sales rebates with multiple customers – this is the
scenario for which condition contract type 0S02 has been designed – is that the type of contract
partner is N No Contract Partner as for these condition contracts the customers eligible for the
sales rebate agreement are determined during the settlement run.
Sales condition type group 0S02 Sales Rebate MultCus is assigned so that you can also
maintain rebate and accrual conditions on level Condition Contract / Customer in the condition
contract.
Additionally field status group 0S02 Sales Rebate - Multiple Customers is assigned so that the
entry of sales related organizational data is not mandatory.
Condition contract types 0S03 Sales Rebate - 2Step, 0SG1 Sales Rebate Goods Related, and
0SG3 Sales Rebate Goods Related - 2Step are identical to condition contract type 0S01 Sales
100
Rebate for the parameters shown here. Differences concern the settlement settings (see
chapter Specify Settlement Settings for Condition Contract Types).
Condition contract types 0S04 Sales Rebate - Mult. Customers - 2Step, 0SG2 Sales Rebate
Goods Rel.- Mult. Customers, and 0SG4 Sales Rebate Goods Rel- MultCust - 2Step are
identical to condition contract type 0S02 Sales Rebate - Multiple Customers for the parameters
shown here. Differences concern the settlement settings (see chapter Specify Settlement
Settings for Condition Contract Types).
Condition Contract Type 0ST1 Sales Rebate TPM
Explanation:
There are four differences for condition contract type 0ST1 Sales Rebate TPM compared with
0S01 Sales Rebate.
The assigned sales condition type group is 0ST1 Sales Rebate TPM.
The assigned field status group is 0S03 Sales Rebate TPM.
101
Parameter Change on the User Interface has value N No Change on User Interface Allowed as
the changes to the condition contract are only allowed via the TPM solution.
For the same reason, the Enable Creation of Successor Contracts checkbox is not selected.
Condition contract type 0ST3 is identical to 0ST1 for the parameters shown here.
There are two differences for condition contract types 0ST2 Sales Rebate TPM - Multiple
Customers and 0ST4 Sales Rebate TPM with Claims - Mult Cust compared with 0ST1 Sales
Rebate TPM: the type of contract partner is N No Contract Partner and the field status group is
0S04 Sales Rebate TPM – Multiple Customer.
2.2.9. Activate Additional Functions
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Maintenance →
Activate Additional Functions
2. Choose function New Entries and activate all additional functions as shown below.
Explanation: The additional features for the maintenance of conditions in a condition contract
are active in the Cloud delivery.
102
2.3 Configure Condition Contract Settlement
The configuration of Condition Contract Settlement comprises five main areas.
•
Business Volume Determination
•
Settlement Calendar
•
Creation of the Settlement Documents
•
Pricing in Settlement Documents - Calculation of the Rebate Amount, Taxes, etc.
•
Accruals Posting & Reversal (involving Pricing)
Note:
Settings for pricing in settlement documents have already been described in main chapter
Configure Pricing Including Condition Contract Conditions.
Calendar settings are included in the settlement settings for a condition contract type (chapter
Specify Settlement Settings for Condition Contract Types).
2.3.1. Define Amount Field Groups
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settlement →
Define Amount Fields Groups
2. Check amount fields groups as shown below.
Explanation: You can optionally specify amount field groups when you maintain amount fields in
profiles for business volume determination. The amount field groups defined here are used in
the amount field specification of business volume determination profiles 0S01, 0S02, 0SG1, and
0SG2 (see chapter Define and Configure Profiles for Business Volume Determination). From
this usage, you can see that either the net amount determined in the pricing procedure for a
103
source document can be used as business volume basis, the subtotal 7 equivalent to KOMPBONBA for the rebate basis, or subtotals 1 to 6.
2.3.2. Define Explosion Groups for Business Volume Base
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settlement →
Define Explosion Groups for Business Volume Base
2. Check explosion groups 0S01 Sales Rebate and 0ST1 TPM as shown below.
Explanation: You can optionally specify explosion groups when you define profiles for business
volume determination (see chapter Define and Configure Profiles for Business Volume
Determination). Explosion group 0S01 is assigned to profiles 0S01 Sales Rebate, 0S02 Sales
Rebate - Multiple Customers, 0SG1 Sales Rebate Goods Related, and 0SG2 Sales Rebate
Goods Rel.- Mult. Customers. Explosion group 0ST1 is assigned to profiles 0ST1 Sales Rebate
TPM and 0ST2 Sales Rebate TPM - Multiple Customers.
Explosion groups 0S01 and 0ST1 contain a rule that explodes higher nodes of product
hierarchy – see source field PRODH – into end nodes of the hierarchy (target field is also PRODH)
using explosion class CL_WB2_BVB_EXPLOSION_PRODH. Explosion group 0ST1 contains a
second rule that explodes a target group of customers defined in TPM into single customers
(target field KUNNR) using explosion class CL_WB2_BVB_EXPLOSION_TG_ID.
104
2.3.3. Define and Configure Profiles for Business Volume
Determination
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition Contract
Management → Condition Contract Settlement → Define and
Configure Profiles for Business Volume Determination
2. Check profiles as shown below.
3. Double-click profile 0S01 Sales Rebate.
105
4. Choose Amount Fields in the Dialog Structure frame and check the corresponding
parameters as shown below. Not shown columns have an initial parameter value.
5. Choose Split Criteria for Settlement in the Dialog Structure frame and check the split criteria
with the corresponding parameters as shown below.
106
Explanation: You assign profiles for business volume determination to condition contract types.
The following table illustrates the usage of profiles in condition contract types (see chapter
Specify Settlement Settings for Condition Contract Types).
Profile
Description
Condition Contract
Type
Description
0S01
Sales Rebate
0S01
Sales Rebate
0S03
Sales Rebate - 2Step
0S02
Sales Rebate - Multiple
Customers
0S04
Sales Rebate - Mult.
Customers - 2Step
0SG1
Sales Rebate Goods
Related
0SG3
Sales Rebate Goods
Related - 2Step
0SG2
Sales Rebate Goods
Rel.- Mult. Customers
0SG4
Sales Rebate Goods
Rel- MultCust - 2Step
0ST1
Sales Rebate TPM
0ST3
Sales Rebate TPM with
Claims
0ST2
Sales Rebate TPM Multiple Customers
0ST4
Sales Rebate TPM with
Claims - Mult Cust
0S02
0SG1
0SG2
0ST1
0ST2
Sales Rebate - Multiple
Customers
Sales Rebate Goods Related
Sales Rebate Goods Rel.Mult. Customers
Sales Rebate TPM
Sales Rebate TPM - Multiple
Customers
The business volume table VWB2_VBRKVBRP_1 is a view for database tables VBRK Billing
Document: Header Data and VBRP Billing Document: Item Data. That means that SD billing
documents represent the source documents to determine the business volume. Accordingly, the
107
parameter Document Type Business Volume is set to 02 SD Invoice and fields VBELN and
POSNR are specified for the source document key.
To find relevant source documents with respect to the condition contract validity, the Date
Selection parameter is set to Standard and the FKDAT Billing Date for Billing Index and Printout
is used to specify the source document's relevant date.
As currency for the business volume, field WAERK SD Document Currency is used.
As the material group is supported as business volume selection criteria, which also includes
that a material group hierarchy is specified (see chapters Define and Configure Field
Combinations for Business Volume Selection and Define and Configure Sets of Field
Combinations), the Explode Material Group Hierarchy checkbox is selected to explode a
specified material group hierarchy into single material groups in the business volume
determination.
Similarly, value A Standard Hierarchy is chosen for the Explode Customer Hierarchy parameter,
which means that the standard hierachy for customers will be exploded to single customers.
Third, explosion group 0S01 Sales Rebate is chosen for the Explosion Group for Business
Volume parameter in order to explode a product hierarchy.
In the Amount Fields view, amount fields NETWR Net value of the billing item in document
currency, BONBA Rebate basis 1 and the subtotal fields KZWI1 to KZWI6 Subtotal 1 (2-6) from
pricing procedure for condition are specified as amount field from business volume data.
The business volume amount determined with these fields is transferred to condition type REBV
Rebate Business Vol. within the relevant pricing procedures of the settlement documents (see
chapter Define Pricing Procedures).
As the Detailed Statement feature is supported in the sales rebate scenarios, BUSVOL_1 is set
in the Fieldname in Detailed Statement column.
Additionally, the amount field group 0S01 Sales Rebate Net Amount is set for NETWR line,
amount field group 0S02 Sales Rebate Rebate Basis is set for BONBA line, and 0S03(04-08)
Sales Rebate Subtotal 1 (2-6) for KZWI1 to KZWI6.
In the Split Criteria for Settlement view, fields GSBER Business Area, KOSTL Cost Center,
MATNR Material, PRCTR Profit Center, and WAERK SD document currency are specified as split
criteria on item level. Target fields in the settlement document are identical for the first four
fields, for WAERK it’s target field WAERS_BV. The accruals reversal split should be identical to the
settlement amount. However, as the fields for the mentioned split criteria (GSBER, KOSTL,
MATNR and PRCTR) are not available in index table WCOCOF, the fields GSBER_CDS,
KOSTL_CDS, MATNR_CDS, PRCTR_CDS have been specified for the accruals reversal split. With
this setting, the system determines the split information from the source documents. For WAERK,
the existing WCOCOF field WAERS is assigned.
6. Check the differences of profiles 0S02, 0SG1 and 0SG2 compared with profile 0S01.
Profiles 0S02, 0SG1, and 0SG2 have the same details parameter and amount fields. However,
split criteria for settlement are different (as shown below) reflecting the rebate scenario.
108
109
110
The difference of profile 0S02 Sales Rebate - Multiple Customers compared with profile 0S01
Sales Rebate is that it contains the additional split criteria KUNNR Sold-To Party, VKORG Sales
Organization, VTWEG Distribution Channel, and SPART Division on split level 1 Head. This
means that for deviating values of these parameters separate settlement documents are
created. In particular, split criterion KUNNR Sold-To Party means that customers eligible for the
rebate agreement are determined in the settlement run.
The difference of profile 0SG1 Sales Rebate Goods Related compared with profile 0S01 Sales
Rebate is that it contains the additional taxation related item split criteria MWSKZ Tax on
Sales/Purchases Code, STCEG VAT Registration Number, STCEG_L Country/Region of Sales
Tax ID Number, TAX_COUNTRY Tax Reporting Country/Region, TXJCD Tax Jurisdiction and
TXDAT_FROM Valid-From Date of the Tax Rate. This means that for deviating values of these
parameters separate settlement document items are created.
Profile 0SG2 Sales Rebate Goods Rel.- Mult. Customers combines the additional split criteria of
0S02 and 0SG1.
7. Check the differences of profiles 0ST1 and 0ST2 compared with profile 0S01.
111
Profiles 0ST1 and 0ST2 show some specifics for the TPM integration. They are differences for
detail parameters, amount fields, there is an additional split criterion, and there are additional
business volume tables. We show this for profile 0ST1 Sales Rebate TPM.
A smaller difference for the detail parameters compared with 0S01 is the explosion group 0ST1
with the additional explosion of a target group for customers (see chapter Define Explosion
Groups for Business Volume Base). Also the two profiles contain only one amount field BONBA.
Because there is only one amount field, no amount field group is assigned.
Compared with 0S01, profiles 0ST1 and 0ST2 have the additional item split criterion product
hierarchy (PRODH). Profile 0ST2 has, as 0S02, additionally the typical split criteria on header
level for the multiple customer scenario.
A major difference concerns the business volume determination. The business volume table
WB2_S_VBRK_VBRP_TPM entered in the Details view is not used for the business volume
determination as the No Selection from Business Volume Table checkbox is selected. Instead,
the system uses the two business volume tables VWB2_VBRKVBRP_1 (also used for all profiles
not releated to TPM) and VWB2_VBRKVBRP_3 maintained in the Additional Business Volume
Tables view. The second view contains two additional fields: CAMPAIGN Campaign ID and
CAMPAIGN_GUID. The two requirement classes CL_WB2_BVTAB_REQ_NO_CAMPAIGN and
CL_WB2_BVTAB_REQ_CAMPAIGN control that the first one is used when no campaign is
specified in the business volume selection criteria, and the second one when a campaign is
specified.
112
2.3.4. Define and Configure Field Combinations for Business
Volume Selection
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settlement → Define
and Configure Field Combinations for Business Volume Selection
2. Check the field combinations as shown below. We show all available field combinations.
113
3. Select field combination 0001 and choose Field Assignment in the Dialog Structure frame.
Check name field KUNNR with the corresponding parameters as shown below.
114
4. Choose Field Combinations in the Dialog Structure frame again.
5. Repeat the procedure described in steps 3 and 4 for the other field combinations.
Check the content according to this table view. The selection type is always initial.
115
Explanation:
Note: Field combinations are grouped in sets of field combinations (see chapter Define and
Configure Sets of Field Combinations) which are assigned to condition contract types (see
chapter Specify Settlement Settings for Condition Contract Types).
116
2.3.5. Define and Configure Sets of Field Combinations
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settlement →
Define and Configure Sets of Field Combinations
2. Check the sets of field combinations 0S01 Sales Rebate and 0ST1 Sales Rebate TPM as
shown below.
3. Select an entry and choose Assign Field Combinations in the Dialog Structure frame. Check
the assigned field combinations as shown below. Not shown columns have an initail
parameter value.
117
Explanation:
Sets of field combinations are assigned to condition contract types, set of field combination
0S01 Sales Rebate is assigned to condition contract types without TPM integration, set of field
combination 0ST1 Sales Rebate TPM is assigned to condition contract types with TPM
integration.
Set of field combination 0S01 Sales Rebate contains the relevant field combinations supported
in the sales rebate scenarios, set of field combination 0ST1 Sales Rebate TPM contains
additional field combinations (0010, 0019) specific for the TPM integration.
Concerning field combination group A: As known, a field combination group within a set of field
combinations effects that the business volumes for the field combinations included in the group
are summarized. This means that you add the business volume of specified materials, material
groups and so on.
The field combination group B for the customer in set 0S01 shall indicate that similarly you can
also select customers with different selection criteria while applying this summation logic. The
same holds for the field combination group C for a customer group.
118
2.3.6. Define and Configure Condition Type Groups for
Accruals
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settlement →
Define and Configure Condition Type Groups for Accruals
2. Check condition type groups for accruals as shown below.
3. Select an entry and choose Condition Types for Group in the Dialog Structure frame.
4. Check the assigned condition types with parameters as shown below.
Explanation:
Note: Condition type groups for accruals are assigned to condition contract types, condition type
group 0S01 Sales Rebate is assigned to condition contract types for rebate scenarios without
TPM integration, condition type group 0ST1 Sales Rebate TPM is assigned to condition contract
types for rebate scenarios with TPM integration (see chapter Specify Settlement Settings for
Condition Contract Types).
Condition type REA1 Rebate Accruals within the condition type group 0S01 Sales Rebate is the
accruals condition type for which you maintain records in the condition contract. Condition type
REA6 Rebate Accruals belongs to rebate condition type RES6 for which you also maintain
119
accruals in one line in the condition contract.
The assigned target conditon type REA2 Rebate Accruals Rev is used in pricing procedure
A10005 to adopt the amount for the accruals reversal during a settlement run (see chapter
Define Pricing Procedures).
The assigned target condition type for delta accruals RED2 Rebate Accr Total is used in pricing
procedure A10006 to adopt the total amount of already reversed accruals (see chapter Define
Pricing Procedures).
Condition type REA5 Rebate AccrualsSettl is the condition type that is used for the situation in a
settlement run when not all accruals are to be reversed (for example, accruals higher than the
settlement amount are to be transferred to the next settlement). You also specify this condition type
directly in the condition contract type (see chapter Specify Settlement Settings for Condition
Contract Types).
The explanation for condition type group 0ST1 Sales Rebate TPM is similar, REA3 (REA4,
RED4) replaces REA1 (REA2, RED2).
120
2.3.7. Specify Extended Scope of Settlement Management
In the standard delivery for on-premise releases, the extended scope for Settlement
Management is not activated. However, this is part of the configuration content for Cloud
releases.
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Specify Extended Scope of Settlement Management
2. Check the settings as shown below.
Explanation: In the Cloud releases, several extended features for Settlement Management are
supported in the sales rebate scenarios.
121
2.3.8. Define Number Ranges
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Define Number Ranges
2. On the following Edit Intervals: Settlement Managemnt, Object W_LFAKTURA screen,
choose function Display intervals and check number range 01 as shown below.
Explanation:
You assign number ranges to settlement document types (see chapter Define Settlement
Document Types). In the standard delivery, number range 01 is assigned to all settlement
document types contained in the standard delivery for sales rebate scenarios.
In the business content for S/4HANA Cloud, different number ranges for the different types of
settlement documents are foreseen as shown in the table below
Number Range
Settlement Document Type
Meaning of Settlement Document Type
70
0S12 (0S14), 0SA2 (0SA4)
Sales Rebate Standard (Reversal)
71
0S22 (0S24), 0SB2 (0SB4)
Sales Rebate Parked (Reversal)
72
0S92 (0S94), 0SI2 (0SI4)
Sales Rebate Collection (Reversal)
73
0S32 (0S34)
Sales Rebate Manual (Reversal)
74
0S52 (0S54), 0SE2 (0SE4)
Sales Rebate Proforma (Reversal)
122
78
0S42 (0S44)
Sales Rebate Delta Accruals (Reversal)
79
0S62 (0S64), 0SF2 (0SF4)
Sales Rebate Accruals Reversal (Reversal)
Note: In the Cloud business content, number ranges 1 to 59 are reserved for the basic
Settlement Management scenarios such as pooled payment, etc. Number ranges 60 to 69 are
reserved for settlement documents used in supplier rebates scenarios.
2.3.9. Define Country-Specific Number Ranges
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Specify Country Specific Number Ranges
2. Check number range group 0001 General NR Group.
Explanation: In some countries, country-specific number ranges are required for settlement
documents – at least for settlement documents which require a payment run in Financial
Accounting.
The general setting of the number ranges is defined on settlement document type level which is
of course not country specific. To allow a country-specific number range assignment this
customizing activity was introduced to assign on a group level unique number ranges per
country.
For the countries that require country-specific number ranges you have to define the country
related number ranges and you have to assign the number ranges to the number range group.
The number range group 0001 General NR Group is already assigned to the settlement
document types, which will create journal entries with open items for payment. When the
number range group contains relevant country specific number ranges then theses number
ranges have a higher priority than the number range explicitly assigned to a settlement
document type.
2.3.10. Define Process Categories
1. Access the Customizing activity:
123
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Define Process Categories
2. Check process category 0S Sales Rebate as shown below.
Explanation:
You assign process categories to settlement process types. Process category 0S Sales Rebate
is assigned to all the settlement process types used in the sales rebate scenarios (see chapter
Define Settlement Process Types).
Process category 0S is used to bundle settlement documents for sales rebates, for example, in
reporting.
2.3.11. Specify Text Determination
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Specify Text Determination
2. Choose activity Set Up Access Sequence for Settlement Document Header.
check access sequences with corresponding accesses as shown below.
124
Explanation:
You assign access sequences to text IDs as shown in the next configuration step. In case of a
settlement document cancellation, these settings for the access sequences enable the copying
of texts for text IDs 0S02 and 0S03 from the reversed settlement document to the reversal
settlement document.
3. Choose activity Set Up Text Determination for Settlement Management Document Header.
Check text procedures with corresponding text IDs and text procedures assignment to
settlement document types as shown below. (Note that you usually assign text procedures in
the maintenance of settlement document described below but this view gives you a good
averview already.)
125
Explanation: The text procedure for collectice settlement documents does not contain text ID
0S03 Contract Text for Output/Forms as a collective settlement document is usually related to
several condition contracts for which this text can be different.
126
2.3.12. Define and Configure Text Transfer Groups
In this Custiomizing activity, you make settings to copy texts from the condition contract into
settlement documents.
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Condition
Contract Management → Condition Contract Settllement
→ Define and Configure Text Transfer Groups
2. Check text transfer group 3 Sales Rebates as shown below
Explanation: The text maintained for text ID 0S03 Text for Settlement Document in a condition
contract is copied to the settlement document, text ID 0S03 Contract Text for Output/Forms.
You assign text transfer groups to condition contract types. Text transfer group 3 Sales Rebates
is assigned to condition contract types 0S01 to 0S04 and 0SG1 to 0SG4.
2.3.13. Define Posting Rules
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Define Posting Rules
2. Check posting rule 0A Accruals Only as shown below.
127
Explanation:
Note: You assign posting rules to settlement document types. Posting rule 0A Accruals Only is
assigned to the four settlement document types 0S62 (0S64) Sales Rebate Accruals Reversal
(Reversal) and 0SF2 (0SF4) Sales Rebate Goods Rel Accruals Reversal (Sales Rebate
GoodsRel Accr.Rev. Reversal) used for the accruals reversal for the whole condition contract
(see chapter Define Settlement Document Types). This ensures that for the accruals reversal
settlement, which is similar to a normal settlement only the accruals reversal is posted but no
rebate amounts.
2.3.14. Define Field Change Groups for Cancellation
Documents
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Define Field Change Groups for Cancellation Documents
128
2. Check field change group for cancellation 0R Rebate as shown below.
Explanation:
Note: You assign field change group for cancellation to settlement document types, field change
group for cancellation 0R Rebate is assigned to the settlement document types for cancellation
used in the sales rebate scenarios; excepted is settlement document type 0S34 Sales Rebate
Manual Credit Reversal for the reversal of manual settlement documents (see chapter Define
Settlement Document Types).
Field change group for cancellation 0R Rebate allows you to change the document date (field
BLDAT) and the reference document number (field XBLNR) in the reversal settlement document.
A related configuration setting is the field status group (see chapter Define Field Status Groups).
The field status group 0S02 Sales Rebate Manual sets fields KOMLFK-XBLNR and KOMLFKBLDAT as required fields.
2.3.15. Define Field Status Groups
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Process → Define Field Status Groups
129
2. Check field status groups with the assigned fields as shown below
130
Explanation: You assign field status groups to settlement process types or settlement document
types. Field status group 0S01 Sales Rebate is assigned to settlement process types 0S10
Sales Rebate, 0S40 Sales Rebate Delta Accruals, and 0S60 Sales Rebate Accruals Reversal,
field status group 0S02 Sales Rebate Manual is assigned to settlement process type 0S30
Sales Rebate Manual from Customer (see chapter Define Settlement Process Types).
Field status group 0S01 Sales Rebate hides the Fix Value Date (Customer) and Additional
Value Days (Customer) fields in the settlement document's header area as these fields are not
filled automatically by the settlement report.
Additionally, the Payment Reference field KOMLFK-KIDNO and the Reference Document
Number field KOMLFK-XBLNR on the Basic Data tab page are optional entry fields.
Field status group 0S02 Sales Rebate Manual sets the document date (field KOMLFK-BLDAT)
and the reference document number as required fields.
131
2.3.16. Define Settlement Document Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Documents → Settlement Document Types → All Document Types
2. Check the following settlement document types.
Settlement Document Type
Description
0S11
Sales Rebate AccPay
0S12
Sales Rebate
0S13
Sales Rebate AccPay Reversal
0S14
Sales Rebate Reversal
0S15
Sales Rebate AccPay Debit
0S16
Sales Rebate Debit
0S17
Sales Rebate AccPay Debit Reversal
0S18
Sales Rebate Debit Reversal
0S21
Sales Rebate AccPay Parked
0S22
Sales Rebate Parked
0S23
Sales Rebate AccPay Parked Reversal
0S24
Sales Rebate Parked Reversal
0S31
Sales Rebate AccPay Manual
0S32
Sales Rebate Manual
0S33
Sales Rebate AccPay Manual Reversal
0S34
Sales Rebate Manual Reversal
0S42
Sales Rebate Delta Accruals
0S44
Sales Rebate Delta Accruals Reversal
0S4B
Sales Rebate Manual Delta Accruals
0S4D
Sales Rebate Manual Delta Accruals Rev
0S51
Sales Rebate AccPay Proforma
0S52
Sales Rebate Proforma
0S53
Sales Rebate AccPay Proforma Reversal
0S54
Sales Rebate Proforma Reversal
0S55
Sales Rebate AccPay Debit Proforma
0S56
Sales Rebate Debit Proforma
0S57
Sales Rebate AccPay Debit Proforma Rev
0S58
Sales Rebate Debit Proforma Reversal
132
0S61
Sales Rebate AccPay Accruals Reversal
0S62
Sales Rebate Accruals Reversal
0S63
Sales Rebate AccPay Accruals Rev Rev
0S64
Sales Rebate Accruals Reversal Reversal
0S6A
Sales Rebate AccPay Accruals Clearing
0S6B
Sales Rebate Accruals Clearing
0S6C
Sales Rebate AccPay Accruals Clear Rev
0S6D
Sales Rebate Accruals Clearing Reversal
0S72
Sales Rebate Manual Credit to Customer
0S74
Sales Rebate Manual Credit to Cust Rev
0S91
Sales Rebate Collection AccPay
0S92
Sales Rebate Collection
0S93
Sales Rebate Collection AccPay Reversal
0S94
Sales Rebate Collection Reversal
0S95
Sales Rebate Collection AccPay Debit
0S96
Sales Rebate Collection Debit
0S97
Sales Rebate Collection AccPay Debit Rev
0S98
Sales Rebate Collection Debit Reversal
0SA2
Sales Rebate Goods Related
0SA4
Sales Rebate Goods Related Reversal
0SA6
Sales Rebate Goods Related Debit
0SA8
Sales Rebate Goods Related Debit Rev
0SB2
Sales Rebate Goods Related Parked
0SB4
Sales Rebate Goods Related Parked Rev
0SC1
Sales Rebate Goods AccPay Manual
0SC2
Sales Rebate Goods Manual
0SC3
Sales Rebate Goods AccPay Manual Rev
0SC4
Sales Rebate Goods Manual Reversal
0SE2
Sales Rebate Goods Rel Proforma
0SE4
Sales Rebate Goods Rel Proforma Reversal
0SE6
Sales Rebate Goods Rel Debit Proforma
0SE8
Sales Rebate Goods Rel Debit Prof Rev
0SF2
Sales Rebate Goods Rel Accruals Reversal
0SF4
Sales Rebate Goods Rel Accruals Rev Rev
0SFB
Sales Rebate Goods Rel Accruals Clearing
133
0SFD
Sales Rebate Goods Rel Accruals ClearRev
0SG2
Sales Rebate Goods Manual Credit to Cust
0SG4
Sales Rebate Goods Manual Credit to C Rv
0SI2
Sales Rebate Goods Rel Collection
0SI4
Sales Rebate Goods Rel Collection Rev
0SI6
Sales Rebate Goods Rel Collection Debit
0SI8
Sales Rebate Goods Rel Coll Debit Rev
The basic settlement document type for the sales rebate scenario is 0S12 Sales Rebate.
Parameters for this settlement document type are explained in detail. For all other settlement
document types, only the diffferences are explained.
First, the settlement document types of the scenarios with a taxation as service (condition
contract types 0S01 to 0S04) are described, then the additional settlement document types of
the scenarios with goods-related taxation, and finally the additional settlement document types
for the TPM scenarios.
The following table gives you an overview.
Settlement Document Types for
Condition
Customer
Proforma
Manual
Contract
Settlement
Settlement
Settlement
Type
0S01
0S12
0S52
0S32
0S11
0S51
0S31
Delta
Accruals
Settlement
Accruals
Reversal
0S42
0S62
0S61
0S02
0S12
0S11
0S52
0S51
0S32
0S31
0S42
0S62
0S61
0S03
0S22
0S21
0S52
0S51
0S32
0S31
0S42
0S62
0S61
0S04
0S22
0S21
0S52
0S51
0S32
0S31
0S42
0S62
0S61
0SG1
0SA2
0SE2
0S32
0S42
0SF2
0SG2
0SA2
0SE2
0S32
0S42
0SF2
0SG3
0SB2
0SE2
0S32
0S42
0SF2
0SG4
0SB2
0SE2
0S32
0S42
0SF2
0ST1
0S12
0S52
0S32
0S42
0S62
0ST2
0S12
0S52
0S32
0S42
0S62
0ST3
0S62
0S72
0S42
0S62
0ST4
0S62
0S72
0S42
0S62
The following table gives you an overview of the alternative settlement document types. The
relationship is mutual.
134
0S11
0S15
0S12
0S16
0S51
0S55
0S52
0S56
0S91
0S95
0S92
0S96
0SA2
0SA6
0SE2
0SE6
0SI2
0SI6
135
Settlement document type 0S12 Sales Rebate
136
137
138
Explanation: In the sales rebate scenarios you want to grant customers a rebate for sales.
Accordingly, as central setting, the settlement document category is 03 Single Document of
Type Credit Memo in the General Control group box.
You also see that change documents are active at document level.
Concerning the handling of a negative amount for the settlement document, you can see –
because of value 3 Change Settlement Document Type if Partner Posting for the Handle
negative Amount parameter – that the system shall then use the alternative settlement
document type 0S16 Sales Rebate Debit. You also see that the material validity shall not be
checked.
In the Number Range group box above, you can see that the number range is 01 (see chapter
Define Number Ranges). Additionally, number range group 0001 General is assigned (see
chapter Specify Country Specific Number Ranges).
In the Document Entry / Default Data group box, you can see that the change scope is restricted
to 1 Only Posting Date and Posting Period. Settlement documents should not be changed or
deleted deliberately or by accident. If a change is required, the best practice is to cancel the
settlement document, do necessary changes in the condition contract, and then re-create the
settlement document. On the other hand, posting date or posting period changes are
sometimes required when a certain posting period has already been closed.
The Zero Values Allowed for Items Amounts checkbox is selected because zero is calculated as
value, for example, when the first scale level, serving as threshold, has not been reached.
In the VAT Registration Number group box, you can see that the customer VAT ID is proposed
from the customer’s master data and that the company code country is used for the
determination of the country.
In the Partner group box, you can see the partner schema for header partner 0SC1 Sales
Rebate and the partner schema for item partner 0S01 Sales Rebate. Value 1 Are Determined
from Master Data for the Partner Determination from Master Data parameter controls that
partners are determined from the master data of the condition contract partner.
In the Text Determination group box, you can see text determination procedure 0S Sales
Rebate for the document header. Text ID 0S02 External Text for Output/Forms shall appear on
the Accounting tab page. Text change is always allowed even when the settlement document
has already been posted to accounting.
In the Pricing group box, you can see that the application for price determination is V
Sales/Distribution. Accordingly, pricing procedures A10005 to A10008 have been defined for
application V (see chapter Define Pricing Procedures). Document schema group 0S Sales
Rebate (see chapter Define Document Schema Groups for Settlement Document Types) is
assigned to differentiate the pricing procedure determination (see chapter Specify Pricing
Procedure Determination). You can also see that not only zero values are allowed but also a
negative net value and a negative effective value. In a certain settlement period, for example,
the amount of returns could be higher than the amount of sales. The No Check for Price
Condition in Schema checkbox is selected as there is no price condition in the pricing
procedure. The Propose Tax Destination Country/Region checkbox is selected to get a default
value for the tax destination country. The tax determination method is 2 If Multiple Tax Types,
139
then FI, Otherwise from Pricing. In addition, the Credit Memo with Value Date and Summarize
Dedit/Crebit in Posting Items checkboxes are selected. The Fill Reference Item in Universal
Journal checkbox is selected so that the item number of the settlement management document
is filled in the universal journal item.
In the Accounting group box, you can see that according to settlement document category 03
Single Document of Type Credit Memo a journal entry with journal entry type DG Customer
Credit Memo will be created. Note: As the Posting Block for Transfer to Accounting checkbox is
not selected, the settlement document will automatically be passed on to FI. You can also see
that statistical conditions are not passed to FI, and that no tax type check will be performed for
the journal entry creation. An important setting is that the current settlement document number
will be used for the reference number (parameter Filling of Reference Number) in the journal
entry as this number becomes visible for the customer in the credit memo. In addition, the Fill
Reference Item in Universal Journal checkbox is selected so that the item number of the
settlement management document is filled in the universal journal item. You can also see that the
profitability analysis is active and that the bill-to party is used for the profitability analysis.
In the Control of Account Determination group box, you can see that for the FI postings related
to settlement documents the account determination procedure has been set to V SD Account
Determination. This means that settings that you maintain in the Customizing for Sales and
Distribution under Basic Functions → Account Assignment/Costing → Revenue Account
Determination are relevant (see chapter Assign G/L Accounts). You also see that KOFRS0 Sales
Rebate has been specified as the procedure for account determination. Account key 0S1 Sales
Rebate is set for the Account Key for Clearing Line parameter.
In the Message Determination group box, you can see that the Use Output Control checkbox is
selected and that 0S01 Sales Rebate has been set as output procedure header. Value X Only
Output Control is set for the Use Output Control parameter.
In the Cancellation group box, you can see that 0S14 Sales Rebate Credit Reversal is specified
as the settlement document type for the reversal settlement document.
In the Special processes group box, you can see value 1 Events are Called for the Control of
Event Call-Up parameter so that the event management for the business workflow is called.
140
Settlement document type 0S14 Sales Rebate Reversal
Explanation: As 0S14 Sales Rebate Reversal is the reversal settlement document type for
settlement document type 0S12 Sales Rebate, the settlement document category is 01 Single
Document of Type Invoice. Note: This settlement document category ensures that you can
cancel a document when you have cleared items in FI. Because of the inverse settlement
category, the Invert Sign for Amount/Qty in Reporting parameter is set to 1 Invert Sign of
Amount / Quantity Fields.
In the VAT Registration Number group box, you can see that the customer VAT ID should not
be proposed for the cancellation document because this information is copied from the
cancelled document.
Similarly, partner data are not determined new from master data but copied from the canceled
document.
In the Cancellation group box, no settlement document type for reversal is specified. Instead,
the Settlement Doc Type Only f. Cancellation checkbox is selected.
FI Cancellation Method X Cleared Automatically if Possible supports an automatic clearing of
the open FI items. If a payment has taken place the standard FI creation process will be
performed. Value 1 Independent of Preceding Document is chosen for the Posting of Reversal
Document parameter to ensure that in case of standard FI creation the posting of the reversal
settlement document is done independently of the posting of the reversed settlement document.
See field help for more information.
You can see that 0R Rebate (see chapter Define Field Change Groups for Cancellation
Documents) is used for the field change group for cancellation.
141
Settlement document type 0S16 Sales Rebate Debit
Explanation: Settlement document type 0S16 Sales Rebate Debit is the alternative settlement
document type for settlement document type 0S12 Sales Rebate, which the system uses to
create the settlement document when the determined gross amount is negative. The settlement
document category is 01 Single Document of Type Invoice to create an invoice with positive
amount instead of a credit memo with negative amount. Accordingly, the Invert Sign for
Amount/Qty in Reporting parameter is set to 1 Invert Sign of Amount / Quantity Fields and the
journal entry type is DR Customer Invoice. The settlement document type for the reversal
settlement document is 0S18 Sales Rebate Debit Reversal (not shown as screenshot).
All other parameters are identical to 0S12 which is also checked when you specify an
alternative settlement document type.
Settlement document type 0S18 Sales Rebate Debit Reversal
Explanation: As 0S18 Sales Rebate Debit Reversal is the reversal settlement document type for
settlement document type 0S16 Sales Rebate Debit, the settlement document category is 03
Single Document of Type Credit Memo. As reversal settlement document type for an alternative
settlement document type having the same settlement document category as settlement
document type 0S12, the Invert Sign for Amount/Qty in Reporting parameter is blank.
Additionally, the inversed journal entry type DR Customer Invoice is used (not shown as
screenshot).
All other parameters are identical to 0S14.
142
Settlement document type 0S22 Sales Rebate Parked
Explanation: This settlement document type is used for the scenario in which settlement
documents are not transferred directly to FI but bundled into a so called collective settlement
document. This document is then transferred to FI. The creation of the collective settlement
document is controlled by the corresponding settlement process type 0S20 (see chapter Define
Settlement Process Types).
There are the following differences for 0S22 Sales Rebate Parked compared with 0S12. There
is no number range group assigned. This is not necessary because no country-specific
differentiation is required as the FI transfer happens with the collective settlement document.
There is no special handling for a negative gross amount – and therefore no alternative
settlement document type is specified – as this handling happens with the collective settlement
document (see settlement document type 0S92).
The tax determination method is Redetermine from FI. The profitability analysis is inactive. The
Credit Memo with Value Date checkbox is not selected for a parked settlement document. The
Account Key for Clearing Line parameter is initial (not shown as screenshot).
There is no message determination - no output procedure for the header assigned and initial
value for parameter Use Output Control - because the output creation happens with the
collective settlement document.
The settlement document type for the reversal settlement document is 0S24 Sales Rebate
Parked Reversal (not shown in screenshot).
143
Settlement document type 0S24 Sales Rebate Parked Reversal
Explanation: There are the following differences compared with 0S14. There is no number
range group assigned. The tax determination method is Redetermine from FI. The profitability
analysis is inactive, the Credit Memo with Value Date checkbox is not selected. The Account
Key for Clearing Line parameter is initial. There is no output procedure assigned for the header
(not shown as screenshot), since the output creation happens with the collective settlement
document.
Settlement document type 0S32 Sales Rebate Manual
144
Explanation: There are several differences for 0S32 Sales Rebate Manual Credit compared with
0S12. There is no number range group assigned.
The Handle Negative Amount parameter has value 1 Error if Partner Posting as a negative
gross amount is not allowed for manual settlement documents. Accordingly, no alternative
settlement document type is specified.
The value for parameter Change Scope is Unrestricted reflecting the manual settlement
document creation.
In the Pricing group box, you can see that document schema group 0V Sales Rebate Manual
(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so
that pricing procedure A10008 Rebates Manual (Germany) is determined (see chapter Specify
Pricing Procedure Determination).
In the Accounting group box, you can see that parameter Partner Lines at Item Level has the
value X Yes. This is only relevant for claims created in the TPM process as with this setting
item-related dispute case IDs (from different disputes cases) can be transferred to the journal
entry. Without TPM, you can keep this setting initial.
In the Message Determination group box, you can see that there is no message determination.
In the Cancellation group box, you can see settlement document type 0S34 Sales Rebate
Manual Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S34 Sales Rebate Manual Reversal
Explanation: There are the following differences compared with 0S14.
There is no number range group assigned.
The value for parameter Change Scope is Unrestricted (not shown as screenshot).
The document schema group is 0V Sales Rebate Manual (not shown as screenshot).
Parameter Partner Lines at Item Level has value X Yes (not shown as screenshot).
There is no message determination (not shown as screenshot).
No field change group for cancellations is assigned – in contrast to other settlement document
types for cancellation – as settlement documents with this settlement document type are
created manually for external documents anyway.
Settlement document type 0S42 Sales Rebate Delta Accruals
145
Explanation: There are several differences compared with 0S12.
There is no number range group assigned.
In the General Control group box, you can see that the settlement category is F Material
Adjustment. This settlement category ensures that the offset posting will be done on a G/L
account instead on a supplier or customer account.
There is no special handling of a negative gross amount.
In the Document Entry / Default Data group box, you can see that the Entry of Tax Code
parameter has value 3 No Input of Tax Codes Possible. This value is used since no tax code or
tax items will be passed to FI for the delta accrual posting anyway.
There is no text determination, that is no text determination procedure and text ID is maintained
(not shown as screenshot).
146
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial (not shown as
screenshot) as the customer VAT ID is not relevant for delta accruals.
In the Pricing group box, the document schema group is 0T so that pricing procedure A10006 is
determined (see chapter Specify Pricing Procedure Determination). The tax determination
method is Redetermine from FI.
In the Accounting group box, you can see that the journal entry type is AB Accounting
Document. The Credit Memo with Value Date checkbox is not selected.
In the Control of Account Determination group box, account key 0S1 Sales Rebate (see chapter
Define Account Keys) has been set for the Account Key Offset Acc. Mat. Adjustment field. This
account key controls which account is determined for the accruals posting in the delta accruals
settlement run (see chapter Assign G/L Accounts). The Account Key for Clearing Line
parameter is initial.
There is no message determination (not shown as screenshot) as the delta accruals posting is
an ‘internal’ procedure and not relevant for the customer.
In the Cancellation group box, you can see settlement document type 0S44 Sales Rebate Delta
Accruals Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S44 Sales Rebate Delta Accruals Reversal
Explanation: There are the following differences compared with 0S14.
There is no number range group assigned. In the General Control group box, you can see that
the settlement category is F Material Adjustment.
In the Document Entry / Default Data group box, you can see that the Entry of Tax Code
parameter has value 3 No Input of Tax Codes Possible.
In the Pricing group box, the document schema group is 0T.
In the Accounting group box, you can see that the journal entry type is AB Accounting
Document.
In the Control of Account Determination group box, account key 0S1 Sales Rebate (see chapter
Define Account Keys) has been set for the Account Key Offset Acc. Mat. Adjustment field.
There is no message determination (not shown as screenshot).
147
When you compare 0S44 with 0S42, you can see that the only differences that occur concern
the settings for document cancellation as described for 0S14.
Settlement document type 0S4B Sales Rebate Manual Delta Accruals
Explanation: There are the following differences compared with 0S42 (!).
In the Pricing group box, you can see that document schema group 0G Sales Rebate Man DA
(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so
that pricing procedure A10016 Rebates ManDeltaAccr (Germany) is determined (see chapter
Specify Pricing Procedure Determination).
In the Cancellation group box, you can see settlement document type 0S4D Sales Rebate
Manual Delta Accruals Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0S4D Sales Rebate Manual Delta Accruals Rev
Explanation: There are the following differences compared with 0S44.
In the Pricing group box, you can see that document schema group 0G Sales Rebate Man DA
(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so
that pricing procedure A10016 Rebates ManDeltaAccr (Germany) is determined (see chapter
Specify Pricing Procedure Determination).
148
Settlement document type 0S52 Sales Rebate Proforma
Explanation: There are the following differences compared with 0S12.
There is no number range group assigned.
The alternative settlement document type for a negative gross amount is 0S56 Sales Rebate
Debit Proforma.
In the General Control group box, you can see that the settlement category is D Pro Forma
Invoice reflecting the purpose of this settlement document type.
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial as the customer VAT
ID is not relevant for pro forma invoices.
The tax determination method is Redetermine from FI.
The Account Key for Clearing Line parameter is initial (not shown as screenshot).
There is no message determination (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0S54 Sales Rebate
Proforma Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S54 Sales Rebate Proforma Reversal
149
Explanation: There are the following differences compared with 0S14.
There is no number range group assigned. In the General Control group box, you can see that
the settlement category is D Pro Forma Invoice.
Tax is redetermined in FI. The Account Key for Clearing Line parameter is initial.
There is no message determination (not shown as screenshot).
Settlement document type 0S56 Sales Rebate Debit Proforma
Explanation: The settlement category is D Pro Forma Invoice. The alternative settlement
document type is 0S52 Sales Rebate Proforma.
Furthermore, there are the same differences compared with 0S16 as described for 0S52.
In the Cancellation group box, you can see settlement document type 0S58 Sales Rebate Debit
Proforma Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S58 Sales Rebate Debit Proforma Reversal
Explanation: There are the same differences compared with 0S18 as described for 0S54.
150
Settlement document type 0S62 Sales Rebate Accruals Reversal
Explanation: There are the following differences compared with 0S12.
There is no number range group assigned. There is no special handling of a negative gross
amount (not shown as screenshot).
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial (not shown as
screenshot) as the customer VAT ID is not relevant for the accruals reversal.
There is no text determination, text determination procedure, text ID and Text Change Allowed
are initial.
In the Pricing group box, the tax determination method is Redetermine from FI. The Propose
Tax Destination Country/Region checkbox is not selected.
The Account Key for Clearing Line parameter is initial (not shown as screenshot).
In the Accounting group box, you can see customer posting rule 0A Accruals Only (see chapter
Define Posting Rules). This ensures that only the accruals are posted and not the settlement
amount (net amount). The Credit Memo with Value Date checkbox is not selected.
There is no message determination (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0S64 Sales Rebate
Accruals Reversal Reversal for the reversal settlement document (not shown as screenshot).
151
Settlement document type 0S64 Sales Rebate Accruals Reversal Reversal
Explanation: There are the following differences compared with 0S14.
There is no number range group assigned.
In the Accounting group box, you can see customer posting rule 0A Accruals Only (not shown
as screenshot; see chapter Define Posting Rules).
There is no message determination (not shown as screenshot).
Settlement document type 0S6B Sales Rebate Accruals Clearing
Explanation: There are the following differences compared with 0S42.
In the Pricing group box, the document schema group is 0S.
In the Accounting group box, the journal entry type is DG Customer Credit Memo.
In the Cancellation group box, you can see settlement document type 0S6D Sales Rebate
Accruals Clearing Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S6D Sales Rebate Accruals Clearing Reversal
Explanation: There are the following differences compared with 0S44.
In the Pricing group box, the document schema group is 0S.
In the Accounting group box, the journal entry type is DG Customer Credit Memo.
152
Settlement document type 0S11 Sales Rebate AccPay
Explanation: There are the following differences between settlement document type 0S11 and
0S12.
Basically, as 0S11 represents the second settlement option with A/P settlement, the settlement
document category in the General Control group box is 01 Single Document of Type Invoice.
Accordingly, the supplier’s VAT ID is proposed from the master data with again the company
code country (see VAT Registration Number group box).
The partner schema for header partner is 0SS1 Sales Rebate AP.
Additionally, in the Pricing group box the Propose Tax Departure Country is selected instead of
Propose Tax Destination Country. A negative gross amount is also handeled with an alternative
settlement document type which is 0S15 Sales Rebate AccPay Debit in this case. Finally, the
settlement document type for cancellation in the Cancellation group box is 0S13 Sales Rebate
AccPay Reversal (not shown as screenshot).
The journal entry type in the Accounting group box is KR Vendor Invoice.
153
Settlement document type 0S13 Sales Rebate AccPay Reversal
Explanation: As 0S13 Sales Rebate AccPay Reversal is the reversal settlement document type
for settlement document type 0S11 Sales Rebate AccPay, the settlement document category is
03 Single Document of Type Credit. Note: This settlement document category ensures that you
can cancel a document when you have cleared items in FI. The partner schema for header
partner is 0SS1 Sales Rebate AP (not shown as screnshot).
Further differences have already been described when comparing reversal settlement document
type 0S14 with 0S12. We shortly recap this description:
In the VAT Registration Number group box, you can see that the customer VAT ID shall not be
proposed.
In the Cancellation group box, no settlement document type for reversal is specified. Instead,
the Settlement Doc Type Only f. Cancellation checkbox is selected.
FI Cancellation Method X Cleared Automatically if Possible supports an automatical clearing of
the open FI items.
Value 1 Independent of Preceding Document is chosen for the Posting of Reversal Document
parameter.
You can see that 0R Rebate (see chapter Define Field Change Groups for Cancellation
Documents) is used for the field change group for cancellation.
Alternative settlement document types:
0S15 Sales Rebate AccPay Debit
0S17 Sales Rebate AccPay Debit Reversal
Differences are similar to 0S16 and 0S18.
154
Settlement document type 0S21 Sales Rebate AccPay Parked
Explanation: This settlement document type is used for the scenario in which settlement
documents are not transferred directly to FI but bundled in a so called collective settlement
document which is then transferred to FI. The creation of the collective settlement document is
controlled by the corresponding settlement process type 0S16 (see chapter Define Settlement
Process Types).
There are the following differences for 0S21 Sales Rebate AccPay Parked compared with
0S11. There is no number range group assigned because no country-specific differentiation is
required, as the FI transfer happens with the collective settlement document.
The tax determination method is Redetermine from FI instead of 2 If Multiple Tax Types, then
FI, Otherwise from Pricing.
The Credit Memo with Value Date checkbox is not selected. The profitability analysis is inactive.
The Account Key for Clearing Line parameter is initial (not shown as screenshot).
There is no output procedure for the header assigned because the output is created with the
collective settlement document (not shown as screenshot).
The settlement document type for the reversal settlement document is 0S23 Sales Rebate
AccPay Parked Reversal (not shown as screenshot).
Settlement document type 0S23 Sales Rebate AccPay Parked Reversal
Explanation: There are the following differences compared with 0S13.
The number range group is initial. The tax determination method is Redetermine from FI. The
Credit Memo with Value Date checkbox is not selected. The profitability analysis is inactive. The
Account Key for Clearing Line parameter is initial (not shown as screenshot).
No output procedure for the header has been assigned (not shown as screenshot) because the
output is created with the collective settlement document.
155
Settlement document type 0S31 Sales Rebate AccPay Manual
Explanation: There are several differences for 0S31 Sales Rebate Manual Invoice compared
with 0S11.
There is no number range group assigned. As for 0S32, the Handle Negative Amount
parameter has the value 1 Error if Partner Posting. Accordingly, there is no alternative
settlement document type.
The value for parameter Change Scope is Unrestricted, reflecting the manual settlement
document creation.
In the Pricing group box, you can see that document schema group 0V Sales Rebate Manual
(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so
that a different pricing procedure, A10008 Rebates Manual (Germany), is determined (see
chapter Specify Pricing Procedure Determination).
In the Accounting group box, you can see that parameter Partner Lines at Item Level has the
value X Yes. This is only relevant for claims created in the TPM process as with this setting
item-related dispute case IDs (from different disputes cases) can be transferred to the journal
entry. Without TPM, you can keep this setting initial.
In the Message Determination group box, you can see that there is no message determination.
In the Cancellation group box, you can see settlement document type 0S33 Sales Rebate
AccPay Manual Reversal for the reversal settlement document (not shown as screenshot).
156
Settlement document type 0S33 Sales Rebate Manual Invoice Reversal
Explanation: There are the following differences compared with 0S13.
There is no number range group assigned.
The value for parameter Change Scope is Unrestricted (not shown as screenshot).
The document schema group is 0V Sales Rebate Manual (not shown as screenshot).
Parameter Partner Lines at Item Level has value X Yes (not shown as screenshot).
There is no message determination (not shown as screenshot).
No field change group for cancellations is assigned – in contrast to other settlement document
types for cancellation – as settlement documents with this settlement document type are
created manually for external documents anyway.
157
Settlement document type 0S51 Sales Rebate AccPay Proforma
Explanation: There are the following differences compared with 0S11.
There is no number range group assigned.
The alternative settlement document type for a negative gross amount is 0S55 Sales Rebate
AccPay Debit Proforma.
In the General Control group box, you can see that the settlement category is D Pro Forma
Invoice reflecting the purpose of this settlement document type.
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial as the customer VAT
ID is not relevant for pro forma invoices.
The tax determination method is Redetermine from FI instead of 2 If Multiple Tax Types, then
FI, Otherwise from Pricing. The profitability analysis is inactive.
The Account Key for Clearing Line parameter is initial (not shown as screenshot).
There is no message determination (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0S53 Sales Rebate
AccPay Proforma Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S53 Sales Rebate AccPay Proforma Reversal
158
Explanation: There are the following differences compared with 0S13.
There is no number range group assigned. In the General Control group box, you can see that
the settlement category is D Pro Forma Invoice.
The tax determination method is Redetermine from FI instead of 2 If Multiple Tax Types, then
FI, Otherwise from Pricing. The profitability analysis is inactive.
The Account Key for Clearing Line parameter is initial (not shown as screenshot).
There is no message determination (not shown as screenshot).
Alternative settlement document types:
0S55 Sales Rebate AccPay Debit Proforma
0S57 Sales Rebate AccPay Debit Proforma Rev
Differences are similar to 0S56 and 0S58.
159
Settlement document type 0S61 Sales Rebate AccPay Accruals Reversal
Explanation: There are the following differences compared with 0S11.
There is no number range group assigned. There is no handling of a negative gross amount.
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial (not shown as
screenshot) as the customer VAT ID is not relevant for the accruals reversal.
There is no text determination, text determination procedure, text ID and Text Change Allowed
are initial.
The tax determination method is Redetermine from FI instead of 2 If Multiple Tax Types, then
FI, Otherwise from Pricing. The Propose Tax Departure Country/Region checkbox is not
selected.
The Account Key for Clearing Line parameter is initial (not shown as screenshot).
In the Accounting group box, you can see customer posting rule 0A Accruals Only (see chapter
Define Posting Rules). This ensures that only the accruals are posted and not the settlement
amount (net amount). The Credit Memo with Value Date checkbox is not selected.
There is no message determination (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0S63 Sales Rebate
AccPay Accruals Rev Rev for the reversal (not shown as screenshot).
Settlement document type 0S63 Sales Rebate Accruals Rev AccPay Rev
Explanation: There are the following differences compared with 0S13.
There is no number range group assigned.
160
In the Accounting group box, you can see customer posting rule 0A Accruals Only (not shown
as screenshot; see chapter Define Posting Rules).
There is no message determination (not shown as screenshot).
Settlement document type 0S6A Sales Rebate AccPay Accruals Clearing
Explanation: There are the following differences compared with 0S6B.
In the General Control group box, the settlement document category is 01 Single Document of
Type Invoice.
In the Partner group box, the partner schema for header partners is 0SS1 Sales Rebate AP.
In the Accounting group box, the journal entry type is KR Vendor Invoice.
In the Cancellation group box, you can see settlement document type 0S6C Sales Rebate
AccPay Accruals Clear Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0S6C Sales Rebate AccPay Accruals Clear Rev
Explanation: There are the following differences compared with 0S6D.
In the General Control group box, the settlement document category is 03 Single Document of
Type Credit Memo.
In the Partner group box, the partner schema for header partners is 0SS1 Sales Rebate AP.
In the Accounting group box, the journal entry type is KR Vendor Invoice.
161
Settlement document types related to goods-related taxation
Generally, there are two differences for such a settlement document type compared with the
corresponding settlement document type for service-related taxation: First, the document
schema group is different so that a pricing procedure with goods-related taxation is determined.
Second, the settlement document type for reversal is different, as you can see in the following.
Settlement document type 0SA2 Sales Rebate Goods Related
Explanation: There are the following differences compared with 0S12.
The alternative settlement document type for a negative gross amount is 0SA6 Sales Rebate
Goods Related Debit. The field status group is 0SG1 Sales Rebates Goods Related.
In the VAT Registration Number group box, you can see value 4 Tax Destination
Country/Region for the Country/Region for Customer VAT ID parameter.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination). The tax determination
method is Redetermine from FI instead of 2 If Multiple Tax Types, then FI, Otherwise from
Pricing.
In the Cancellation group box, you can see settlement document type 0SA4 Sales Rebate
Goods Related Reversal for the reversal settlement document (not shown as screenshot).
162
Settlement document type 0SA4 Sales Rebate Goods Related Reversal
Explanation: There are the following differences compared with 0S14.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination). The tax determination
method is Redetermine from FI instead of 2 If Multiple Tax Types, then FI, Otherwise from
Pricing.
Settlement document type 0SA6 Sales Rebate Goods Related Debit
Explanation: There are the following differences compared with 0S16.
The field status group is 0SG1 Sales Rebates Goods Related.
In the VAT Registration Number group box, you can see value 4 Tax Destination
Country/Region for the Country/Region for Customer VAT ID parameter.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination). The tax determination
method is Redetermine from FI instead of 2 If Multiple Tax Types, then FI, Otherwise from
Pricing.
In the Cancellation group box, you can see settlement document type 0SA8 Sales Rebate
Goods Related Debit Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0SA8 Sales Rebate Goods Related Debit Rev
Explanation: There are the following differences compared with 0S18.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
163
Settlement document type 0SB2 Sales Rebate Goods Related Parked
Explanation: There are the following differences compared with 0S22.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
In the Settlement Using Follow-On Documents group box, you can see value 0SI2 Sales
Rebate Goods Rel Collection for the Settl. Doc. Type for Coll. of Settl Docs parameter.
In the Cancellation group box, you can see settlement document type 0SB4 Sales Rebate
Goods Related Parked Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0SB4 Sales Rebate Goods Related Parked Rev
Explanation: There are the following differences compared with 0S24.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
In the Settlement Using Follow-On Documents group box, you can see value 0SI2 Sales
Rebate Goods Rel Collection for the Settl. Doc. Type for Coll. of Settl Docs parameter.
Settlement document type 0SC2 Sales Rebate Goods Manual
164
Explanation: There are the following differences compared with 0S32.
In the General Control group box, the field status group is 0SG2 Sales Rebates Manual Goods
Related.
In the VAT Registration Number group box, you can see value 4 Tax Destination
Country/Region for the Country/Region for Customer VAT ID parameter.
In the Cancellation group box, you can see settlement document type 0SC4 Sales Rebate
Goods Manual Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0SC4 Sales Rebate Goods Manual Reversal
Explanation: There no differences compared with 0S34.
Settlement document type 0SC1 Sales Rebate Goods AccPay Manual
Explanation: There are the following differences compared with 0S31.
In the General Control group box, the field status group is 0SG2 Sales Rebates Manual Goods
Related.
In the VAT Registration Number group box, you can see value 3 Tax Departure Country/Region
for the Country/Region for Supplier VAT ID parameter.
In the Cancellation group box, you can see settlement document type 0SC3 Sales Rebate
Goods AccPay Manual Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0SC3 Sales Rebate Goods AccPay Manual Rev
Explanation: There no differences compared with 0S33.
165
Settlement document type 0SE2 Sales Rebate Goods Rel Proforma
Explanation: There are the following differences compared with 0S52.
The alternative settlement document type for a negative gross amount is 0SE6 Sales Rebate
Goods Rel Debit Proforma (not shown as screenshot). The field status group is 0SG1 Sales
Rebates Goods Related.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination) (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0SE4 Sales Rebate
Goods Rel Proforma Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0SE4 Sales Rebate Goods Rel Proforma Reversal
Explanation: There are the following differences compared with 0S54.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
Settlement document type 0SE6 Sales Rebate Goods Rel Debit Proforma
Explanation: There are the following differences compared with 0S56.
The field status group is 0SG1 Sales Rebates Goods Related.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
In the Cancellation group box, you can see settlement document type 0SE8 Sales Rebate
Goods Rel Debit Prof Rev for the reversal settlement document (not shown as screenshot).
166
Settlement document type 0SE8 Sales Rebate Goods Rel Debit Prof Rev
Explanation: There are the following differences compared with 0S18.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
Settlement document type 0SF2 Sales Rebate Goods Rel Accruals Reversal
Explanation: There are the following differences compared with 0S62.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination) (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0SF4 Sales Rebate
Goods Rel Accruals Rev Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0SF4 Sales Rebate Goods Rel Accruals Rev Rev
Explanation: There are the following differences compared with 0S64.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
Settlement document type 0SFB Sales Rebate Goods Rel Accruals Rev Rev
Explanation: There are the following differences compared with 0S6B.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
167
In the Cancellation group box, you can see settlement document type 0SFD Sales Rebate
Goods Rel Accruals ClearRev for the reversal settlement document (not shown as screenshot).
Settlement document type 0SFD Sales Rebate Goods Rel Accruals ClearRev
Explanation: There are the following differences compared with 0S6D.
In the Pricing group box, the document schema group is 0U so that pricing procedure A10007 is
determined (see chapter Specify Pricing Procedure Determination).
Settlement document type 0SG2 Sales Rebate Goods Manual Credit to Cust
Explanation: There are the following differences compared with 0S72.
In the Pricing group box, the document schema group is 0_ so that pricing procedure A10019 is
determined (see chapter Specify Pricing Procedure Determination).
In the Cancellation group box, you can see settlement document type 0SG4 Sales Rebate
Goods Manual Credit to C Rv for the reversal settlement document (not shown as screenshot).
Settlement document type 0SG4 Sales Rebate Goods Manual Credit to C Rv
Explanation: There are the following differences compared with 0S74.
In the Pricing group box, the document schema group is 0_ so that pricing procedure A10019 is
determined (see chapter Specify Pricing Procedure Determination).
168
Settlement document type 0S92 Sales Rebate Collection
Explanation: There are the following differences compared with 0S12.
The usage of this settlement document type is reflected in the variant V Settlement Document
Collection.
The alternative settlement document type for a negative gross amount is 0S96 Sales Rebate
Collection Debit (not shown as screenshot).
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial (not shown as
screenshot) as the customer VAT ID is copied from the single settlement documents.
In the Text Determination group box, you can see that the text determination procedure is 1S
Sales Rebate Coll.
In the Follow-On Document Creation General group box, you can see value 1 Take Settlement
Doc Category Preceding Document into Account for the Consid. of SDoc. Cat. for Follow-On
Docs parameter.
In the Cancellation group box, you can see settlement document type 0S94 Sales Rebate
Collection Reversal for the reversal settlement document (not shown as screenshot).
Note that in the Pricing group box document schema group 0S is maintained as for the single
settlement documents (compare settlement document type 0S22). This setting is redundant as
for the collection settlement document the pricing procedure of the single settlement documents
is used. However, we made this setting for transparency reasons. In addition, the Propose Tax
Destination Country/Region checkbox is not selected as this happens for the parked settlement
documents.
Settlement document type 0S94 Sales Rebate Collection Reversal
Explanation: There are the following differences compared with 0S14.
169
The usage of this settlement document type is reflected in the variant V Settlement Document
Collection.
In the Text Determination group box, you can see that the text determination procedure is 1S
Sales Rebate Coll.
In the Follow-On Document Creation General group box, you can see value 1 Take Settlement
Doc Category Preceding Document into Account for the Consid. of SDoc. Cat. for Follow-On
Docs parameter (not shown as screenshot).
Settlement document type 0S96 Sales Rebate Collection Debit
Explanation: There are the similar differences compared with 0S92 as described for 0S16. The
settlement document category is inverse, the sign for amount/quantity fields in reporting is
inverse, the journal entry type is inverse.
In the Cancellation group box, you can see settlement document type 0S98 Sales Rebate
Collection Debit Reversal for the reversal settlement document (not shown as screenshot).
Settlement document type 0S98 Sales Rebate Collection Debit Reversal
Explanation: There are the similar differences compared with 0S94 as described for 0S18.
170
Settlement document type 0SI2 Sales Rebate Goods Rel Collection
Explanation: There are the following differences compared with 0S92. The alternative
settlement document type for a negative gross amount is 0S96 Sales Rebate Collection Debit
(not shown as screenshot). The field status group is 0SG1 Sales Rebates Goods Related.
In the Pricing group box, the document schema group is 0U. For this setting, compare the note
at the end of explanations for 0S92.
The tax determination method is Redetermine from FI instead of 2 If Multiple Tax Types, then
FI, Otherwise from Pricing.
In the Cancellation group box, you can see settlement document type 0SI4 Sales Rebate
Goods Rel Collection Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0SI4 Sales Rebate Goods Rel Collection Rev
Explanation: There are the following differences compared with 0S94.
In the Pricing group box, the document schema group is 0U.
Settlement document type 0SI6 Sales Rebate Goods Rel Collection Debit
Explanation: There are the typical differences for an alternative settlement document type.
Settlement document type 0SI8 Sales Rebate Goods Rel Coll Debit Rev
Explanation: There are the typical differences for an alternative settlement document type.
171
Settlement document type 0S91 Sales Rebate Collection AccPay
Explanation: There are the following differences compared with 0S11.
The use of this settlement document type is reflected in the variant V Settlement Document
Collection.
The alternative settlement document type for a negative gross amount is 0S95 Sales Rebate
Collection AccPay Debit (not shown as screenshot).
In the VAT Registration Number group box, you can see that the values for parameters
Customer VAT ID and Country Determination for Cust. VAT ID are initial (not shown as
screenshot) as the customer VAT ID is copied from the single settlement documents.
In the Text Determination group box, you can see that the text determination procedure is 1S
Sales Rebate Coll.
In the Follow-On Document Creation General group box, you can see value 1 Take Settlement
Doc Category Preceding Document into Account for the Consid. of SDoc. Cat. for Follow-On
Docs parameter.
In the Cancellation group box, you can see settlement document type 0S93 Sales Rebate
Collection AccPay Reversal for the reversal settlement document (not shown as screenshot).
Note that in the Pricing group box document schema group 0S is maintained as for the single
settlement documents (see settlement document type 0S22). This setting is redundant as for
the collection settlement document the pricing procedure of the single settlement documents is
used. However, we made this setting for transparency reasons. In addition, the Propose Tax
Departure Country/Region checkbox is not selected as this happens for the parked settlement
documents.
Settlement document type 0S93 Sales Rebate Collection AccPay Reversal
Explanation: There are the following differences compared with 0S13.
The use of this settlement document type is reflected in the variant V Settlement Document
Collection. The text determination procedure is 1S Sales Rebate Coll.
In the Follow-On Document Creation General group box, you can see value 1 Take Settlement
Doc Category Preceding Document into Account for the Consid. of SDoc. Cat. for Follow-On
Docs parameter (not shown as screenshot).
172
Alternative settlement document types:
0S95 Sales Rebate Collection AccPay Debit
0S97 Sales Rebate Collection AccPay Debit Rev
There are the typical differences for an alternative settlement document type.
Settlement document type 0S72 Sales Rebate Manual Credit to Customer
Explanation: There are the following differences compared with 0S12.
The value for parameter Change Scope is Unrestricted reflecting the manual settlement
document creation.
In the Pricing group box, the document schema group is 0V so that pricing procedure A10008
Rebates Manual (Germany) is determined (not shown as screenshot, see chapter Specify
Pricing Procedure Determination).
There is no message determination (not shown as screenshot).
In the Cancellation group box, you can see settlement document type 0S74 Sales Rebate
Manual Credit to Cust Rev for the reversal settlement document (not shown as screenshot).
Settlement document type 0S74 Sales Rebate Manual Credit to Cust Rev
Explanation: There are the following differences compared with 0S14.
The value for parameter Change Scope is Unrestricted reflecting the manual settlement
document creation (not shown as screenshot).
In the Pricing group box, the document schema group is 0V so that pricing procedure A10008 is
determined (not shown as screenshot, see chapter Specify Pricing Procedure Determination).
There is no message determination (not shown as screenshot).
173
2.3.17. Assign Transfer Groups to Settlement Document Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Documents → Specify Settings for Transfer Manager
2. Choose activity Assign Transfer Groups to Settlement Document Type (via Event) on the
following dialog box.
3. Select transfer event 18 Data Transfer - Collective Document Header and choose Assign
Settlement Document Types in the Dialog Structure frame. Check the assignment of
settlement document types with transfer group 0S01 as parameter as shown below.
4. Select transfer event 20 Pricing Data - Change Header (KOMK) Supplier Side. Check the
assignment of settlement document types with transfer groups 0S01 Sales Rebate as
parameter as shown below.
174
5. Select transfer event 22 Pricing Data - Change Item (KOMP) Supplier Side. Check the
assignment of settlement document types with transfer groups 0S01 as parameter as
shown below.
175
6. Select transfer event 23 Pricing Data - Change Item (KOMP) Customer Side. Check the
assignment of settlement document types with transfer groups 0S01 and 0SG1 as
parameter as shown below.
176
177
7. Select transfer event 32 Accounting Document - Change Customer Line and check the
assignment of settlement document types with transfer group 0S01 and 0SM1 as parameter
as shown below.
8. Select transfer event 3H Account Determination in Sales and Distribution (SD) and check
the assignment of settlement document types with transfer group 0SC1 as parameter as
shown below.
178
9. Select event 63 Default Header Data - Document Reversal. Check the assignment of
settlement document types with transfer group 0R as parameter as shown below.
179
10. Select event 6I Set Final Document Number. Check the assignment of settlement
document types with transfer group 0S01 as parameter as shown below.
180
11. Select event 70 Condition Contract Settlement - Change Header Data. Check the
assignment of settlement document types with transfer group 0S01 and 0SG1 as parameter
as shown below.
Explanation:
181
Transfer group 0S01 Sales Rebate (see chapter Specify Settings for Transfer Manager) for
transfer event 18 is assigned to settlement document type 0S92 to create the collective
settlement document.
Transfer group 0S01 Sales Rebate (see chapter Specify Settings for Transfer Manager) for
transfer event 20 is assigned to all settlement document types used in the sales rebate scenario
for A/P settlement.
Transfer group 0S01 Sales Rebate (see chapter Specify Settings for Transfer Manager) for
transfer event 22 is assigned to all settlement document types used in the sales rebate scenario
for A/P settlement.
Transfer group 0S01 Sales Rebate (see chapter Specify Settings for Transfer Manager) for
transfer event 23 is assigned to all settlement document types used in the sales rebate
scenario for A/R settlement.
Transfer group 0R Rebate (see chapter Specify Settings for Transfer Manager) for transfer
event 63 is assigned to all settlement document types for reversal settlement documents used
in the sales rebate scenario except the settlement document type for the reversal of manually
created settlement documents.
Transfer group 0S01 Sales Rebate (see chapter Specify Settings for Transfer Manager) for
transfer event 6I is assigned to all settlement document types used in the sales rebate scenario
with a data transfer to FI.
Transfer group 0S01 Sales Rebate (see chapter Specify Settings for Transfer Manager) for
transfer event 70 is assigned to all settlement document types to change the settlement party if
required.
2.3.18. Define Column Sorting Groups
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Process → Define Column Sorting Groups
2. Check column sorting groups with assigned fields as shown below.
182
183
184
Explanation: You assign column sorting groups to settlement process types (see chapter Define
Settlement Process Types). Column sorting group 0S01 Sales Rebate is assigned to settlement
process types 0S10 Sales Rebate, 0S20 Sales Rebate - Two Step Settlement, 0S40 Sales
Rebate Delta Accruals, 0S60 Sales Rebate Accruals Reversal, column sorting group 0S02
Sales Rebate is assigned to settlement process types 0S30 Sales Rebate Manual from
Customer and 0S70 Sales Rebate Manual to Customer.
Both column sorting groups hide purchasing-related columns such as KOMLFP-EKKOL
Condition Group with Supplier, KOMLFP-IDNLF Material Number Used by Supplier etc. or fields
for which related features are currently not supported as, for example, KOMLFP-SKTOF Cash
discount indicator.
The column sorting groups reflect the way how corresponding settlement documents are
created. For settlement documents created in a settlement run, the net value, the tax amount,
the gross amount, and the tax code are displayed (field KOMLFP-NETWR, , -MWSBP, -BRTWR ,
and -MWSK2, column 2-5), followed by material-related data (material number, material text,
quantity, unit of measure, and material group).
In the manual creation of the settlement document, you have to enter the net item amount (field
KOMLFP-PNETWR, column 2), the tax code (field KOMLFP-MWSK2, column 3) and the gross
amount (field KOMLFP-PBRTWR, column 5). Then the material related fields follow as mentioned
above.
185
2.3.19. Define Settlement Process Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Process → Define Settlement Process Types
2. Check the following settlement process types.
Settlement Process Type
Description
0S10
Sales Rebate
0S15
Sales Rebate Accounts Payables
0S16
Sales Rebate AccPayables CustomerInfo
0S20
Sales Rebate - Two Step Settlement
0S25
Sales Rebate Accounts Payable - Two Step
0S26
Sales Rebate AccPayables CInf - Two Step
0S30
Sales Rebate Manual from Customer
0S35
Sales Rebate Manual from Customer AccPay
0S36
Sales Rebate Manual from Customer APCInf
0S40
Sales Rebate Delta Accruals
0S4A
Sales Rebate Manual Delta Accruals
0S60
Sales Rebate Accruals Reversal
0S65
Sales Rebate AccPay Accruals Reversal
0S66
Sales Rebate AccPay CustInf Accruals Rev
0S70
Sales Rebate Manual to Customer
The basic settlement process type for the sales rebate scenarios is 0S10 Sales Rebate Credit.
So, parameters are explained for this settlement document type in detail. For all other
settlement document types, only the diffferences are explained.
All parameter values starting from group box Customer-Side Settlement are initial – with the
exception of settlement process 0S20 for which you specify settings for the collection of
settlement documents in the Collection of Settlement Documents group box. So, this part is only
shown once for settlement process type 0S10 Sales Rebate Credit. In addition, group box
Collection of Settlement Documents is shown for 0S20.
Settlement process types 0S15, 0S25, 0S35, and 0S65 have been introduced in release
S/4HANA 1809 for A/P settlement of sales rebates. Meanwhile they have been replaced with
0S16, 0S26, 0S36, and 0S66 within the same release so that they are currently not used
anymore in condition contract types. Nevertheless, we start with a description of the first four
settlement process types to explain the difference compared with A/R settlement. Then we
explain in the description for 0S16 why a refinement was necessary.
186
Settlement process type 0S10 Sales Rebate
187
Explanation: In the sales rebate scenarios, we create settlement documents during the
settlement runs. So, Settlement Document is set for the settlement process category in the
Control group box. This also means that settlement documents are directly transferred to FI and
not parked.
As the settlement document is a sales-sided document, value 2 Only Customer Side is set for
the Settlement Partner Category parameter and value A Customer-Side is set for the Price
Determin. on Supplier/Customer parameter.
You can see value D Only Document Schema for the Pricing Procedure Determination Type
(see chapter Specify Pricing Procedure Determination).
You can see value C Material-Related with Logistics Data for the Entry Category for Logistics
Data parameter as settlement data is entered including material related data.
As the Post Business Volume in Accounting parameter has value P Using Pricing, the business
volume is posted in the journal entry using the account keys specified in the pricing procedure (see
chapters Define Pricing Procedures, Define Settlement Document Types see section Control of
Account Determination, and chapter Assign G/L Accounts).
You can see that the tax code is determined from pricing (value 3 From Price Determination for
the Tax Code Determination parameter).
The Post Tax Amounts checkbox is selected as the tax amount has to be posted to FI as well
for the right A/R account.
With view on the manual settlement process, the Different Tax Amount Allowed checkbox is
selected to ensure that tax determination carried out according to pricing parameters may differ
from data on paper invoices.
The Check Allowed Settlement Doc. Type checkbox is selected with view on the future
enhancement, for example, for the entry of the settlement document type when you want to
cancel a settlement document.
You can see that 0S Sales Rebate is set for the Process Category parameter (see chapter
Define Process Categories).
In the Default Values group box, you can see that the tax amount and the gross item amount is
calculated - Calculate Tax Amount checkbox is selected and value C Automatically for Single
and List Documents for the Determine Gross Value Automatically parameter is set.
In the Document Entry Control group box, you can see value 0S01 Sales Rebate for the field
status group (see chapter Define Field Status Groups) and the column sorting group (see
chapter Define Column Sorting Groups).
In the Assigned Settlement Document Types group box, you can see value 0S12 Sales Rebate
for the Settlement Document Type parameter (see chapter Define Settlement Document Types
and chapter Allowed Combinations Settlement Process Type / Settlement Document Type).
188
Settlement process type 0S20 Sales Rebate - Two Step Settlement
Explanation: Settlement process type 0S20 is designated to create settlement documents that
are not released to FI immediately. Instead, these settlement documents shall be bundled in a
collective settlement document which is then released to FI. Accordingly, the Settlement
Process Category parameter for 0S20 is B Document Parking and the settlement procedure is 2
Collection of Settlement Documents.
In addition, settlement process type 0S10 Sales Rebate and settlement document type 0S92
Sales Rebate Collection for the collection settlement document is specified in the Collection of
Settlement Documents group box. Value 2 Active at Item Level is set for the Collection
Category for Settlement parameter.
The settlement document type of the single document is 0S22.
189
Settlement process type 0S30 Sales Rebate Manual from Customer
Explanation: In the Control group box, you can see value blank Manual Entry for the Tax Code
Determination parameter, as the tax code is specified on the external invoice.
You can see value B With Logistics Data for the Entry Category for Logistics Data parameter as
a manual settlement document is usually entered without material related data because also the
underlying external invoice from a customer does not contain material information.
In the Default Values group box, you can see that you have to enter the tax amount and the
gross item amount which are also taken from the external invoice.
In the Document Entry Control group box, you can see value 0S02 Sales Rebate Manual for the
field status group (see chapter Define Field Status Groups) and the column sorting group (see
chapter Define Column Sorting Groups in particular with respect to entry fields for tax and gross
amount).
In the Assigned Settlement Document Types group box, you can see value 0S32 Sales Rebate
Manual Credit for the Settlement Document Type parameter (see chapter Define Settlement
Document Types and chapter Allowed Combinations Settlement Process Type / Settlement
Document Type).
190
Settlement process type 0S40 Sales Rebate Delta Accruals
Explanation: In the Default Values group box, you can see value E No Terms of Payment for the
Default for Payment Terms of Customer because payment terms can be defined on condition
contract level.
In the Assigned Settlement Document Types group box, you can see value 0S42 Sales Rebate
Credit for the Settlement Document Type parameter (see chapter Define Settlement Document
Types and chapter Allowed Combinations Settlement Process Type / Settlement Document
Type).
191
Settlement process type 0S4A Sales Rebate Manual Delta Accruals
Explanation: You can see value B With Logistics Data for the Entry Category for Logistics Data
parameter as a manual settlement document is usually entered without material related data.
In the Default Values group box, you can see value E No Terms of Payment for the Default for
Payment Terms of Customer because payment terms can be defined on condition contract
level.
The column sorting group is 0005 Sales Rebate Manual Accruals.
In the Assigned Settlement Document Types group box, you can see value 0S4B Sales Rebate
Manual Delta Accruals for the Settlement Document Type parameter (see chapter Define
Settlement Document Types and chapter Allowed Combinations Settlement Process Type /
Settlement Document Type).
192
Settlement process type 0S60 Sales Rebate Accruals Reversal
Explanation: In the Assigned Settlement Document Types group box, you can see value 0S62
Sales Rebate Accruals Reversal for the Settlement Document Type parameter (see chapter
Define Settlement Document Types and see also following chapter Allowed Combinations
Settlement Process Type / Settlement Document Type).
193
Settlement process type 0S70 Sales Rebate Manual to Customer
Explanation: In the Control group box, you can see value B With Logistics Data for the Entry
Category for Logistics Data parameter as the manual settlement document for TPM claims is
created without material-related data.
In the Assigned Settlement Document Types group box, you can see value 0S72 Sales Rebate
Manual Credit to Customer for the Settlement Document Type parameter (see chapter Define
Settlement Document Types and also see the following chapter Allowed Combinations
Settlement Process Type / Settlement Document Type).
194
Settlement process type 0S15 Sales Rebate Accounts Payables
Explanation: As the settlement document created with this additional configuration settings is a
supplier-sided document, value 1 Only Supplier Side is set for the Settlement Partner Category
parameter and value Supplier Side is set for the Price Determination parameter.
You can see value D Only Document Schema Group for the Calculation Schema Determination
Type (see chapter Specify Pricing Procedure Determination).
You can see value D Material-Related Without Logistics Data for the Entry Category for
Logistics Data parameter as settlement data is entered including material related data.
As the Post Business Volume in Accounting parameter has value P Using Pricing, the business
volume is posted in the journal entry using the account keys specified in the pricing procedure (see
chapters Define Pricing Procedures, Define Settlement Document Types see section Control of
Account Determination, and chapter Assign G/L Accounts).
You can see that the tax code is determined from pricing (value 3 From Price Determination for
the Tax Code Determination parameter).
The Post Tax Amounts checkbox is selected as the tax amount has to be posted to FI as well
for the right A/P account.
With view on the manual settlement process, the Different Tax Amount Allowed checkbox is
selected to ensure that tax determination carried out according to pricing parameters may differ
from data on paper invoices.
The Check Allowed Settlement Doc. Type checkbox is selected with view on the future
enhancement, for example, for the entry of the settlement document type when you want to
cancel a settlement document.
You can see that 0S Sales Rebate is set for the Process Category parameter (see chapter
Define Process Categories).
195
In the Default Values group box, you can see that the tax amount and the gross item amount is
calculated - Calculate Tax Amount checkbox is selected and value C Automatically for Single
and List Documents for the Determine Gross Value Automatically parameter is set.
In the Document Entry Control group box, you can see value 0S01 Sales Rebate for the field
status group (see chapter Define Field Status Groups) and value 0S03 Sales Rebate Accounts
Payable for the column sorting group (see chapter Define Column Sorting Groups).
In the Assigned Settlement Document Types group box, you can see value 0S11 Sales Rebate
Invoice for the Settlement Document Type parameter (see chapter Define Settlement Document
Types and chapter Allowed Combinations Settlement Process Type / Settlement Document
Type).
Settlement process type 0S25 Sales Rebate Accounts Payable - Two Step
Explanation: Settlement process type 0S25 is designated to create settlement documents that
are not released to FI immediately. Instead, these settlement documents shall be bundled in a
collective settlement document which is then released to FI. Accordingly, the Settlement
Process Category parameter for 0S25 is B Document Parking and the settlement procedure is 2
Collection of Settlement Documents.
In addition, settlement process type 0S15 Sales Rebate Accounts Payable and settlement
document type 0S91 Sales Rebate Collection AccPay for the collection settlement document is
specified in the Collection of Settlement Documents group box.
The settlement document type of the single document is 0S21 Sales Rebate AccPay Parked
(not shown as screenshot).
196
Settlement process type 0S35 Sales Rebate Manual from Customer AccPay
Explanation: There are the following differences compared with 0S15:
In the Control group box, you can see value blank Manual Entry for the Tax Code
Determination parameter, as the tax code is specified on the external invoice.
You can see value A Without Logistics Data for the Entry Category for Logistics Data parameter
as a manual settlement document is usually entered without material related data because also
the underlying external invoice from a customer does not contain material information.
In the Default Values group box, you can see that you have to enter the tax amount and the
gross item amount which are also taken from the external invoice.
In the Document Entry Control group box, you can see value 0S02 Sales Rebate Manual
AccPayables for the field status group (see chapter Define Field Status Groups) and 0S04
Sales Rebate Manual AccPayables for the column sorting group (see chapter Define Column
Sorting Groups in particular with respect to entry fields for tax and gross amount).
In the Assigned Settlement Document Types group box, you can see value 0S31 Sales Rebate
Manual Invoice for the Settlement Document Type parameter (see chapter Define Settlement
Document Types and chapter Allowed Combinations Settlement Process Type / Settlement
Document Type).
Settlement process type 0S65 Sales Rebate AccPay Accruals Reversal
The only difference compared with 0S15 is that in the Assigned Settlement Document Types
group box, value 0S61 Sales Rebate Accruals Reversal AccPay is set for the Settlement
Document Type parameter (see chapter Define Settlement Document Types and see also
197
following chapter Allowed Combinations Settlement Process Type / Settlement Document
Type).
Other parameter values are identical to 0S15.
Settlement process types 0S16, 0S26, 0S36, and 0S66 are similar to 0S15 to 0S65 and are
used as well in the context of A/P settlement. But they offer the ‘Customer Information’ as
additional feature.
Settlement process type 0S16 Sales Rebate AccPayables CustomerInfo
Explanation: The main difference compared with 0S15 is that 5 Only Supplier Side – Customer
for Information is set for the Settlement Partner Category parameter. This means that customer
data is filled in the settlement document because this data is required also in an A/P settlement
procedure. For instance, customer data is required in order to update profitability data in
application CO-PA correctly. Additionally, customer data is required in multiple customer
condition contracts for which the customer is a header split criterion. Here, you must be able to
assign accruals to customers.In particular, the A/P partial and final settlement, both automatic
and manual, wouldn’t run anymore when you work with delta accruals as these are always
posted in an A/R mode.
Additional differences are:
Value C Material-Related With Logistics Data is set for the Entry Category for Logistics Data
parameter instead of value D.
The Enter Organizational Data Completely checkbox is selected to allow a check that customer
data is filled.
Value 1 No Check is set for the Check Sett. Mgmt. Relevance for Customer parameter.
198
In the Default Values group box, you see value E No Terms of Payment for the Default for
Payment Terms of Customer parameter. Payment terms are not relevant as there is no
settlement with the customer.
When you compare settlement process type 0S26 with 0S25 and settlement process type 0S66
with 0S65, you see the same differences as described for 0S16 compared with 0S15. When
you compare 0S36 with 0S35, you see that value B With Logistics Data is set for the Entry
Category for Logistics Data parameter instead of value A Without Logistics Data. In addition, you
see the other differences as already mentioned for 0S16.
199
2.3.20. Allowed Combinations Settlement Process Type /
Settlement Document Type
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Settlement
Process → Allowed Combinations Settlement Process Type /
Settlement Document Type
2. Check allowed combinations as shown below.
200
Explanation: In the sales rebate scenarios, we have pre-defined combinations of settlement
process type and settlement document type for the different types of settlement ('normal' partial
and final settlement, proforma settlement, manual settlement, delta accruals settlement, and
accruals reversal settlement).
201
2.3.21. Specify Copy Control
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Specify Copy Control
2. Choose activity Settlement Management Document to Settlement Management Document.
3. Check copy control entries as shown. Double-click an entry to see the corresponding
parameter settings as shown for one combination as they are identical for all combinations.
202
2.3.22. Specify Settlement Settings for Condition Contract
Types
1. Access the Customizing activity:
Customizing activity
Logistics – General → Settlement Management → Condition
Contract Management → Condition Contract Settlement →
Specify Settlement Settings for Condition Contract Types
2. On the Display View “Condition Contract Types”: Overview screen, double-click an entry
and check the settlement settings for the following condition contract types as shown below.
Condition Contract Type
Description
0S01
Sales Rebate
0S02
Sales Rebate - Multiple Customers
0S03
Sales Rebate – 2Step
0S04
Sales Rebate - Mult. Customers - 2Step
0SG1
Sales Rebate Goods Related
0SG2
Sales Rebate Goods Rel.- Mult. Customers
0SG3
Sales Rebate Goods Related - 2Step
0SG4
Sales Rebate Goods Rel- MultCust - 2Step
0ST1
Sales Rebate TPM
0ST2
Sales Rebate TPM - Multiple Customers
0ST3
Sales Rebate TPM with Claims
0ST4
Sales Rebate TPM with Claims - Mult Cust
The basic condition contract type for the sales rebate scenario is 0S01 Sales Rebate. So,
parameters are explained for this condition contract type in detail. For all other condition
contract types, only the diffferences are explained.
First, the condition contract types of the scenarios with a taxation as service (condition contract
types 0S01 to 0S04) are described, then the condition contract types of the scenarios with
goods-related taxation, then the condition contract types for the TPM scenarios.
All parameters in the Supplier Settlement group box are initial for all condition contract types.
So, this group box is only shown once in the screenshots for condition contract type 0S01 Sales
Rebate for the sake of completeness.
Additionally, parameters starting from the Contract Determination in Pricing group box are
identical for all non-TPM scenarios. So, this part is also be shown only for 0S01.
203
Condition contract type 0S01 Sales Rebate
204
205
Explanation: The condition contract settlement type is 2 Customer Contract Settlement –
meaning that you perform a customer-sided settlement.
In the Business Volume group box, 0S01 Sales Rebate is specified for the profile for business
volume determination (see chapter Define and Configure Profiles for Business Volume
Determination) and 0S01 Sales Rebate for the set of field combinations. Value 1 Error if no
Entry Exists for the Check Entries for the BV Selection Criteria parameter means that the user
has to specify business volume selection criteria when maintaining a condition contract. Eligible
206
partners do not play a role for the business volume determination.
In the Settlement Dates group box, you can see that the Manual Changes Allowed checkbox is
selected so that you can make manual entries in the settlement calendar. Partial settlement is
supported with type 1 Cumulative as well as delta settlements with a maximum of 3 settlement
runs. Value 1 Allowed for the Unplanned Settlement parameter means that you can perform an
unplanned settlement run.
Because of value 2 for the condition contract settlement type, the Settlement Type Customer
parameter is relevant in the Settlement group box and you can see that as default the customersided settlement is performed As Accounts Receivable. However, you can change the
settlement type when creating a new condition contract. Because of the specified customer
contract settlement, settlement process types and settlement document types (see chapter
Define Settlement Process Types and Define Settlement Document Types) are specified in the
Customer Settlement group box. As both settlement using the A/R account and settlement using
the A/P account of the customer is supported entries are made for both the ...(Accounts
Payable) and ...(Accounts Receiv.) entry fields.
Condition type RES2 Rebate PartSettl Rev specified for the Condition Type Reverse Partial
Settlemnt parameter is used in the A10005 pricing procedure to adopt the amount of previous
(cumulative) partial settlements which the system determines in a settlement run (compare
chapter Define Pricing Procedures).
You can see that a detailed statement is saved with a settlement run (see chapter Define and
Configure Profiles for Business Volume Determination, BUSVOL_1 is set in the Fieldname in
Detailed Statement column for the NETWR amount field line). You can also see that manual
settlement documents are allowed and that text transfer group 3 Sales Rebates is specified.
In the Accruals group box, you can see several parameters for the accruals processing as, for
example, 0S01 Sales Rebate for the Condition Type Group for Accruals parameter (see chapter
Define and Configure Condition Type Groups for Accruals). You can also see condition type
REA5 Rebate AccrualsSettl in the Condition Type Accruals from Settlement field. With this entry,
you identify the condition type which shall adopt the amount of the excessive accruals amount,
determined during a settlement run, that shall be written back to the accruals index table
WCOCOF. This condition type is included in pricing procedures A10005 (and A10007), compare
chapter Define Pricing Procedures. The Transfer Group Accruals Bill Doc -Item parameter has
value 0S01 Sales Rebate.
In the Delta Accruals sub group box, you can see that the delta accruals processing is active.
Condition type REA1 is specified in the Condition Type for Delta Accruals field. This means that
delta accruals are transferred as a sum on item level to table WCOCOF using this condition type.
This condition type is identical to the condition type for which you maintain records in the
condition contract (see chapters Assign Condition Types to Condition Type Groups and Define
Condition Contract Types). Value 2 Partial and Final Settlement with Delta Accruals Allowed for
the Multiple Settlements on the Same Date parameter means that you can perform a delta
accruals settlement run and a partial or final settlement run on the same day.
In the Contract Extension group box, you can see that condition contract extension is supported
whereas AJ Annual arrangement is the default value for the extension calendar.
207
Condition contract type 0S02 Sales Rebate - Multiple Customers
Explanation: The most important difference between condition contract type 0S02 compared
with 0S01 is that the profile for business volume determination is 0S02 Sales Rebate - Multiple
Customers instead of 0S01 Sales Rebate. As mentioned (see chapter Define and Configure
Profiles for Business Volume Determination), the split criteria in the profile control that separate
settlement documents are created for different customers. In addition, parameter Entry Type of
Manual Settlement has value 1 Preceding Popup for OrgData and Partners as you have to
specify the customer for the manual settlement document.
208
Condition contract type 0S03 Sales Rebate - 2Step
Explanation: The difference between condition contract type 0S03 Sales Rebate – 2Step
compared with 0S01 Sales Rebate is that settlement process type 0S20 Sales Rebate - Two
Step Settlement and settlement document type 0S22 Sales Rebate Parked are specified for
the customer settlement. The different settlement process type entails that parked settlement
documents are created (see chapter Define Settlement Process Types).
209
Condition contract type 0S04 Sales Rebate - Mult. Customers - 2Step
Explanation: Condition contract type 0S04 Sales Rebate - Mult. Customers - 2Step combines
the differences of condition contract types 0S02 and 0S03.
210
Condition contract type 0SG1 Sales Rebate Goods Related
Explanation: The first difference between condition contract type 0SG1 compared with 0S01 is
that the profile for business volume determination is 0SG1 Sales Rebate Goods Related instead
of 0S01 Sales Rebate. As mentioned (see chapter Define and Configure Profiles for Business
Volume Determination), profile 0SG1 contains additional split criteria for tax code and tax
jurisdiction code.
Other differences concern the settlement document types for the different kinds of settlement.
Because of the different document schema, the deviating pricing procedure A10007 containing
the goods-related taxation is determined. The settlement document type for the ‘regular’
customer settlement is 0SA2 Sales Rebate Goods Related instead of 0S12 Sales Rebate, for
accruals reversal it is 0SF2 Sales Rebate Goods Rel Accruals Reversal instead of 0S62 Sales
Rebate Accruals Reversal, for accruals clearing it is 0SFB Sales Rebate Goods Rel Accruals
Clearing instead of 0S6B Sales Rebate Accruals Clearing, for proforma settlement it is 0SE2
Sales Rebate Goods Rel Proforma instead of 0S52 Sales Rebate Proforma, and for manual
settlement it is 0SC2 Sales Rebate Goods Manual instead of 0S32 Sales Rebate Manual.
211
Condition contract type 0SG2 Sales Rebate Goods Rel.- Mult. Customers
Explanation: The most important difference between condition contract type 0SG2 compared
with (!) 0SG1 is that the profile for business volume determination is 0SG2 Sales Rebate Good
Rel.- Mult. Customers instead of 0S01 Sales Rebate. As mentioned (see chapter Define and
Configure Profiles for Business Volume Determination), the split criteria in the profile control that
separate settlement documents are created for different customers. In addition, parameter Entry
Type of Manual Settlement has value 1 Preceding Popup for OrgData and Partners as you have
to specify the customer for the manual settlement document (not shown as screenshot).
Condition contract type 0SG3 Sales Rebate Goods Related - 2Step
Explanation: The difference between condition contract type 0SG3 Sales Rebate Goods Related
- 2Step compared with 0SG1 Sales Rebate Goods Related is that settlement process type 0S20
Sales Rebate - Two Step Settlement and settlement document type 0SB2 Sales Rebate Goods
Related Parked are specified for the customer settlement. The different settlement process type
entails that parked settlement documents are created (see chapter Define Settlement Process
Types).
Condition contract type 0SG4 Sales Rebate Goods Rel- MultCust - 2Step
Explanation: Condition contract type 0SG4 Sales Rebate Goods Rel- MultCust - 2Step
combines the differences of condition contract types 0SG2 and 0SG3.
212
Condition contract type 0ST1 Sales Rebate TPM
213
Explanation: There are the following differences between condition contract type 0ST1 and with
0S01. The profile for business volume determination is 0ST1 Sales Rebate TPM instead of
0S01 Sales Rebate (see chapter Define and Configure Profiles for Business Volume
Determination).
The set of field combinations is 0ST1 Sales Rebate TPM instead of 0S01 Sales Rebate. Both
differences consider that additional selection criteria can be used in the TPM-related scenarios.
Manual changes for the settlement calendar are not allowed.
The Condition Type Reverse Partial Settlemnt parameter has value RES4 instead of RES2.
Parameter Split Items by Dates has value 3 Split by Settlement Condition Validity. There is no
text transfer group.
The condition type group for accruals 0ST1 Sales Rebate TPM is used instead of 0S01 Sales
Rebate as different condition types (REA3, REA4, RED3) are used for accruals in the TPMrelated scenarios. Accordingly, REA3 is used for the Condition Type for Delta Accruals
parameter instead of REA1.
214
Condition contract type 0ST2 Sales Rebate TPM - Multiple Customers
Explanation: The most important difference between condition contract type 0ST2 compared
with 0ST1 (!) is that the profile for business volume determination is 0ST2 Sales Rebate TPM Multiple Customers instead of 0ST1 Sales Rebate TPM. As mentioned (see chapter Define and
Configure Profiles for Business Volume Determination), the split criteria in the profile control that
separate settlement documents are created for different customers. In addition, parameter Entry
Type of Manual Settlement has value 1 Preceding Popup for OrgData and Partners as you have
to specify the customer for the manual settlement document (not shown as screenshot).
Condition contract type 0ST3 Sales Rebate TPM with Claims
215
216
Explanation: Partial and delta settlements are not intended for this TPM-related sales rebate
scenario with claims, as all the settlements are done via claims coming from CRM as manual
settlement settlement documents. Accordingly, the Partial Settlement Type parameter has value
No Partial Settlement and the Maximum Number of Delta Settlements parameter has value 0.
Additionally, proforma settlement is not intended. Accordingly, no settlement process type and
settlement document type for proforma settlement is specified in the Customer Settlement group
box.
A characteristic of the TPM scenario related to this condition contract type is that no real final
settlement is foreseen. Settlement only happens with manually created settlement documents.
So, the settlement process type 0S60 Sales Rebate Accruals Reversal and settlement
document type 0S62 Sales Rebate Accruals Reversal just for accruals reversal is assigned in
the Customer Settlement group box for the normal settlement just to reverse existing accruals
postings at the end of the process.
Last, the settlement process type 0S70 Sales Rebate Manual to Customer and settlement
document type 0S72 Sales Rebate Manual Credit to Customer are different. Here, not an
external invoice from the customer is the basis for the customer settlement document (where
you enter the tax code and amount), but the manual settlement document is created based on a
net amount from the CRM claim, so the tax code must be determined, and the tax amount must
be calculated. For this, a separate pricing procedure and different settings in the settlement
process type are needed.
217
Condition contract type 0ST4 Sales Rebate TPM with Claims - Mult Cust
218
Explanation: The difference between condition contract type 0ST4 compared with 0ST3 (!) is
that the profile for business volume determination is 0ST2 Sales Rebate TPM - Multiple
Customers instead of 0ST1 Sales Rebate TPM.
3. On the Display View “Condition Contract Types”: Overview screen, select each condition
contract type and choose Settlement Settings in the Dialog Structure frame to check the
following settings shown only once for 0S01.
219
2.4 Other Configuration Settings
2.4.1. Define Access Sequence for Account Determination
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Account Determination → Revenue Account Determination
(SD) → Define Access Sequences And Account Determination
Types
2. On the following Select Activity: dialog box, choose Define Access Sequences for Revenue
Account Determination.
3. Check access sequence KORS Sales Rebate and corresponding accesses with access
fields as shown below.
220
2.4.2. Define Account Determination Type
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Account Determination → Revenue Account Determination
(SD) → Define Access Sequences And Account Determination
Types
2. On the following Select Activity: dialog box, choose Define Account Determination Types.
3. Check account determination type KORS Sales Rebate with the assigned access sequence
KORS Sales Rebate as shown below.
221
2.4.3. Define and Assign Account Determination Procedures
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Account Determination → Revenue Account Determination
(SD) → Define And Assign Account Determination Procedures
2. On the following Select Activity: dialog box, choose Define account determination
procedure.
3. Check account determination procedure KOFRS0 Sales Rebate as shown below.
222
2.4.4. Assign G/L Accounts
Note: In the standard configuration, you cannot deliver an account assignment as the usage of
accounts is a customer-individual setting. However, as this is an important piece of the overall
configuration, we show here an example setting for the functional tests in SAP’s Cloud delivery.
In this environment, the known account determination procedure KOFI00 Account
determination is used instead of KOFRS0 Sales Rebate introduced in the chapter before.
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Account Determination → Revenue Account Determination
(SD) → Assign G/L Accounts
2. On the following Assign G/L Accounts screen, double-click the line for table 005 Acct Key.
3. Review the entry of the Cloud delivery as shown below.
Explanation:
The relevant account determination type in the account determination procedure KOFI00
Account determination specified for the settlement document types in the Cloud delivery is
KOFI Acct determination. The relevant chart of accounts in the Cloud delivery is YCOA Standard
Charts of Accounts and the relevant sales organization for tests is 1010 Dom. Sales Org DE.
Using these parameters, relevant accounts from YCOA are assigned to the account key 0S1
Sales Rebate for posting rebates and accruals (see chapter Define Account Keys for definition
of account key 0S1 Sales Rebate, see chapter Define Pricing Procedures for the usage in
pricing procedures, and chapter Define Settlement Document Types for relevant settings for
settlement document types).
223
2.4.5. Define Output Types
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Output Control → Message Determination → Maintain
Message Types
2. Check message type 0S01 Sales Rebate Print with the corresponding parameters as
shown below.
224
2.4.6. Define Output Determination Procedures
1. Access the Customizing activity:
Customizing activity
Logistics - General → Settlement Management → Basic Settings
→ Output Control → Message Determination → Maintain
Message Determination Schema
2. Check procedure 0S01 Sales Rebate and corresponding control data as shown below.
2.4.7. Assign Output Channels
1. Access the Customizing activity:
Customizing activity
Cross-Application Components → Output Control → Assign
Output Channels
2. Check the following entries as shown below.
225
2.4.8. Assign Form Templates
1. Access the Customizing activity:
Customizing activity
Cross-Application Components → Output Control → Assign
Form Templates
2. Check the following entries as shown below (not shown columns have initial value for
parameter).
2.4.9. Activation of Scope-Dependent Application Job Catalog
Entries (S/4HANA)
1. Access the Customizing activity:
Customizing activity
ABAP Platform → Application Server → System Administration
→ Activation of Scope-Dependent Application Job Catalog
Entries (S/4HANA)
2. Check the following entries.
226
227