Gestão de Contratos de Condições

Prévia do material em texto

<p>S/4HANA</p><p>March 2023</p><p>English</p><p>Condition Contract</p><p>Management -</p><p>Sales Commission for</p><p>External Sales Agent</p><p>SAP SE</p><p>Dietmar-Hopp-Allee 16</p><p>69190 Walldorf</p><p>Delivered Standard Configuration in S/4HANA 2022</p><p>2</p><p>Copyright</p><p>© 2023 SAP SE or an SAP affiliate company. All rights reserved.</p><p>No part of this publication may be reproduced or transmitted in any form or for any purpose without the express</p><p>permission of SAP SE or an SAP affiliate company.</p><p>SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or</p><p>registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see</p><p>http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and</p><p>notices.</p><p>Some software products marketed by SAP SE and its distributors contain proprietary software components of other</p><p>software vendors.</p><p>National product specifications may vary.</p><p>These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without</p><p>representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or</p><p>omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and</p><p>services are those that are set forth in the express warranty statements accompanying such products and services,</p><p>if any. Nothing herein should be construed as constituting an additional warranty.</p><p>In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this</p><p>document or any related presentation, or to develop or release any functionality mentioned therein. This</p><p>document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future</p><p>developments, products, and/or platform directions and functionality are all subject to change and may be changed</p><p>by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is</p><p>not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking</p><p>statements are subject to various risks and uncertainties that could cause actual results to differ materially from</p><p>expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak</p><p>only as of their dates, and they should not be relied upon in making purchasing decisions.</p><p>http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark</p><p>3</p><p>Icons</p><p>Icon Meaning</p><p>Caution</p><p>Example</p><p>Note</p><p>Recommendation</p><p>Syntax</p><p>Typographic Conventions</p><p>Type Style Description</p><p>Example text Words or characters that appear on the screen. These include field</p><p>names, screen titles, pushbuttons as well as menu names, paths and</p><p>options.</p><p>Cross-references to other documentation.</p><p>Example text Emphasized words or phrases in body text, titles of graphics and tables.</p><p>EXAMPLE TEXT Names of elements in the system. These include report names,</p><p>program names, transaction codes, table names, and individual key</p><p>words of a programming language, when surrounded by body text, for</p><p>example, SELECT and INCLUDE.</p><p>Example text Screen output. This includes file and directory names and their paths,</p><p>messages, source code, names of variables and parameters as well as</p><p>names of installation, upgrade and database tools.</p><p>EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the</p><p>ENTER key.</p><p>Example text Exact user entry. These are words or characters that you enter in the</p><p>system exactly as they appear in the documentation.</p><p>Variable user entry. Pointed brackets indicate that you replace these</p><p>words and characters with appropriate entries.</p><p>4</p><p>Contents</p><p>1. Purpose ...................................................................................................... 6</p><p>2. Configuration ............................................................................................. 6</p><p>2.1 Configure Pricing Including Condition Contract Conditions ..................... 7</p><p>2.1.1. Condition Tables ................................................................................................ 7</p><p>2.1.2. Access Sequences ............................................................................................. 8</p><p>2.1.3. Condition Types ............................................................................................... 10</p><p>2.1.4. Specify CC-Relevance for Condition Types ...................................................... 32</p><p>2.1.5. Define Condition Type Groups ......................................................................... 32</p><p>2.1.6. Assign Condition Types to Condition Type Groups ........................................... 33</p><p>2.1.7. Define Account Keys ........................................................................................ 34</p><p>2.1.8. Define Pricing Procedures ................................................................................ 35</p><p>2.1.9. Condition Exclusion For Groups Of Conditions ................................................. 44</p><p>2.1.10. Define Document Schema Groups for Settlement Document Types ................. 45</p><p>2.1.11. Specify Pricing Procedure Determination .......................................................... 46</p><p>2.1.12. Specify General Settings .................................................................................. 47</p><p>2.2 Configure Condition Contract Maintenance ............................................. 48</p><p>2.2.1. Define Number Ranges .................................................................................... 48</p><p>2.2.2. Define Condition Contract Categories ............................................................... 48</p><p>2.2.3. Define and Configure Field Status Groups for Header Fields ............................ 49</p><p>2.2.4. Define Text Determination Procedures ............................................................. 50</p><p>2.2.5. Specify Text Types for Text Determination Procedure ...................................... 50</p><p>2.2.6. Define Check Groups ....................................................................................... 51</p><p>2.2.7. Specify Settings for Transfer Manager .............................................................. 51</p><p>2.2.8. Define Condition Contract Types ...................................................................... 65</p><p>2.3 Configure Condition Contract Settlement ................................................. 67</p><p>2.3.1. Assign Partner Functions to Predefined Partner Relations ................................ 67</p><p>2.3.2. Define Amount Field Groups ............................................................................ 68</p><p>2.3.3. Define Explosion Groups for Business Volume Base ........................................ 68</p><p>2.3.4. Define and Configure Profiles for Business Volume Determination ................... 69</p><p>2.3.5. Define and Configure Field Combinations for Business Volume Selection ......... 74</p><p>2.3.6. Define and Configure Sets of Field Combinations ............................................. 78</p><p>2.3.7. Define and Configure Condition Type Groups for Accruals ............................... 79</p><p>2.3.8. Define Number Ranges .................................................................................... 80</p><p>2.3.9. Define Country-Specific Number Ranges ......................................................... 81</p><p>2.3.10. Define Process Categories ............................................................................... 81</p><p>2.3.11. Specify Text Determination .............................................................................. 82</p><p>5</p><p>2.3.12. Define and Configure Text Transfer Groups .....................................................</p><p>activity:</p><p>Customizing activity Logistics – General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Assign Partner Functions to Predefined Partner Relations</p><p>2. Check the partner function assignment as shown below.</p><p>Explanation: This Customizing setting is characteristic for the sales commission scenarios.</p><p>Sales commission with field name LIFNR_COMMISSION Commission Recipient represents one</p><p>of the predefined partner relations. As you can see the newly defined partner function ES</p><p>External Agent with partner type LI Vendor is assigned. In chapters Define and Configure Field</p><p>Combinations for Business Volume Selection and Define and Configure Sets of Field</p><p>Combinations, you will see that a set of field combinations 0C01 Commission Settlement -</p><p>External is defined which contains field combination 0026 Commission Recipient. This allows</p><p>you to specify the commission recipient in the business volume selection criteria of a condition</p><p>contract. This Customizing setting controls, that only those billing documents are selected for</p><p>which the commission recipient has been specified for partner function ES External Agent with</p><p>the value entered in the condition contract.</p><p>68</p><p>2.3.2. Define Amount Field Groups</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics – General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Define Amount Fields Groups</p><p>2. Check amount fields groups as shown below.</p><p>Explanation: You can optionally specify amount field groups when you maintain amount fields in</p><p>profiles for business volume determination. The amount field groups are specified in the profiles</p><p>decribed in this document.</p><p>Amount field group 0C01 Commission Net Amount is the default when creating a new condition</p><p>contract as controlled by transfer group 0C01 of transfer event 75, see chapter Specify Settings</p><p>for Transfer Manager. So, you can see that as default the net amount determined in the pricing</p><p>procedure for a source document is used as business volume base.</p><p>2.3.3. Define Explosion Groups for Business Volume Base</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Define Explosion Groups for Business Volume Base</p><p>2. Check explosion group 0S01 Sales Rebate as shown below.</p><p>69</p><p>Explanation: You can optionally specify explosion groups when you define profiles for business</p><p>volume determination (see chapter Define and Configure Profiles for Business Volume</p><p>Determination). Explosion group 0S01 is assigned to profiles 0CS1 Commission External: Billing</p><p>Document and 0CS2 Commission External: Billing Doc Paid.</p><p>Explosion group 0S01 contains a rule that explodes higher nodes of product hierarchy – see</p><p>source field PRODH – into end nodes of the hierarchy (target field is also PRODH) using explosion</p><p>class CL_WB2_BVB_EXPLOSION_PRODH.</p><p>2.3.4. Define and Configure Profiles for Business Volume</p><p>Determination</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics – General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Define and Configure Profiles for Business Volume</p><p>Determination</p><p>2. Check profile 0CS1 Commission External: Billing Document and 0CS2 Commission</p><p>External: Billing Doc Paid for commission settlement as shown below.</p><p>70</p><p>3. Choose Amount Fields in the Dialog Structure frame and check the corresponding</p><p>parameters as shown below.</p><p>71</p><p>4. Choose Split Criteria for Settlement in the Dialog Structure frame and check the split criteria</p><p>with the corresponding parameters as shown below.</p><p>5. Choose Additional Business Volume Tables in the Dialog Structure frame, double-click and</p><p>entry in the following table, and check the business volume tables with the corresponding</p><p>parameters as shown below.</p><p>72</p><p>Explanation: You assign profiles for business volume determination to condition contract types.</p><p>Profile 0CS1 Commission External: Billing Document is assigned to condition contract types</p><p>0CS1 Commission External: Billing Document and 0CS2 Commission External: Billing Doc,</p><p>2Step (see chapter Specify Settlement Settings for Condition Contract Types).</p><p>The business volume table VWB2_VBRKVBRP_7 is a view for database view</p><p>VWB2_VBRKVBRP_1 joined with partner data for the billing document. View VWB2_VBRKVBRP_1</p><p>is used for commission processing reading business volume data from database tables VBRK</p><p>73</p><p>Billing Document: Header Data and VBRP Billing Document: Item Data. Accordingly, the</p><p>parameter Document Type Business Volume is set to 02 SD Invoice and fields VBELN and</p><p>POSNR are specified for the source document key.</p><p>To find relevant source documents with respect to the condition contract validity, the Date</p><p>Selection parameter is set to Standard and the FKDAT Billing Date for Billing Index and Printout</p><p>is used to specify the source document's relevant date.</p><p>As currency for the business volume, field WAERK SD Document Currency is used.</p><p>As the material group is supported as business volume selection criteria, which also includes</p><p>that a material group hierarchy is specified (see chapters Define and Configure Field</p><p>Combinations for Business Volume Selection and Define and Configure Sets of Field</p><p>Combinations), the Explode Material Group Hierarchy checkbox is selected to explode a</p><p>specified material group hierarchy into single material groups in the business volume</p><p>determination.</p><p>Similarly, value A Standard Hierarchy is chosen for the Explode Customer Hierarchy parameter,</p><p>which means that the standard hierachy for customers will be exploded to single customers.</p><p>Third, explosion group 0S01 Sales Rebate is chosen for the Explosion Group for Business</p><p>Volume parameter in order to explode a product hierarchy.</p><p>In the Amount Fields view, amount fields NETWR Net value of the billing item in document</p><p>currency, BONBA Rebate basis 1 and the subtotal fields KZWI1 to KZWI6 Subtotal 1 (2-6) from</p><p>pricing procedure for condition are specified as amount field from business volume data.</p><p>The business volume amount determined with these fields is transferred to condition type RCBV</p><p>Commission BusVol within the relevant pricing procedures of the settlement documents (see</p><p>chapter Define Pricing Procedures).</p><p>As the Detailed Statement feature is supported in the commission settlement scenarios,</p><p>BUSVOL_1 is set in the Fieldname in Detailed Statement column.</p><p>Additionally, the amount field group 0C01 Commission Net Amount is set for NETWR line,</p><p>amount field group 0C02 Commission Rebate Basis is set for BONBA line, and 0C03(04-08)</p><p>Commission Subtotal 1 (2-6) for KZWI1 to KZWI6.</p><p>In the Split Criteria for Settlement view, fields GSBER Business Area, KOSTL Cost Center,</p><p>MATNR Material, PRCTR Profit Center, and WAERK SD document currency are specified as split</p><p>criteria on item level. Target fields in the settlement document are identical for the first four</p><p>fields, for WAERK it’s target field WAERS_BV. The accruals reversal split should be identical to the</p><p>settlement amount. However, as the fields for the mentioned split criteria (GSBER, KOSTL,</p><p>MATNR and PRCTR) are not available in index table WCOCOF, the fields GSBER_CDS,</p><p>KOSTL_CDS, MATNR_CDS, PRCTR_CDS have been specified for the accruals reversal split. With</p><p>this setting, the system determines the split information from the source documents. For WAERK,</p><p>the existing WCOCOF field WAERS is assigned.</p><p>There is only one difference for profile 0CS2 compared with 0CS1: the business volume table is</p><p>VWB2_VBRKVBRP_9. This view joins database view VWB2_VBRKVBRP_8 with partner data for</p><p>the billing document, and database view VWB2_VBRKVBRP_8 again joins database view</p><p>VWB2_VBRKVBRP_1</p><p>with the corresponding journal entry.</p><p>Profile 0CS2 Commission External: Billing Doc Paid is assigned to condition contract types</p><p>0CS3 Commission External: Billing Doc Paid and 0CS4 Commission External: Bill Doc</p><p>Paid,2Step (see chapter Specify Settlement Settings for Condition Contract Types).</p><p>74</p><p>2.3.5. Define and Configure Field Combinations for Business</p><p>Volume Selection</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics – General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement → Define</p><p>and Configure Field Combinations for Business Volume Selection</p><p>2. Check the field combinations as shown below. We show all available field combinations.</p><p>75</p><p>3. Select field combination 0001 and choose Field Assignment in the Dialog Structure frame.</p><p>Check name field KUNNR with the corresponding parameters as shown below.</p><p>76</p><p>4. Choose Field Combinations in the Dialog Structure frame again.</p><p>5. Repeat the procedure described in steps 3 and 4 for the other field combinations.</p><p>Check the content according to this table view. The selection type is always initial.</p><p>77</p><p>Explanation: Note: Field combinations are grouped in sets of field combinations (see chapter</p><p>Define and Configure Sets of Field Combinations) which are assigned to condition contract</p><p>types (see chapter Specify Settlement Settings for Condition Contract Types).</p><p>78</p><p>2.3.6. Define and Configure Sets of Field Combinations</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics – General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Define and Configure Sets of Field Combinations</p><p>2. Check set of field combination 0C01 Commission Settlement - External as shown below.</p><p>Not shown columns in the Assign Field Combinations table have an initail parameter value.</p><p>79</p><p>Explanation: Sets of field combinations are assigned to condition contract types, set of field</p><p>combination 0C01 Commission Settlement - External is assigned to condition contract types</p><p>0CS1 Commission Settlement, 0CS2 Commission External: Billing Doc, 2Step, 0CS3</p><p>Commission External: Billing Doc Paid and 0CS4 Commission External: Bill Doc Paid,2Step.</p><p>Set of field combination 0C01 Commission Settlement – External contains the relevant field</p><p>combinations supported in the commission settlement scenarios.</p><p>Characteristic is field combination 0026 Commission Recipient with value 1 for the MaxEntries</p><p>parameter which allows you to specify just one sales commission recipient in the business</p><p>volume selection criteria of a condition contract.</p><p>Concerning field combination group A: As known, a field combination group within a set of field</p><p>combinations effects that the business volumes for the field combinations included in the group</p><p>are summarized. This means that you add the business volume of specified materials, material</p><p>groups and so on.</p><p>The field combination group C shall indicate that similarly you can also select single customers</p><p>and customers from customer hierarchies.</p><p>2.3.7. Define and Configure Condition Type Groups for</p><p>Accruals</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Define and Configure Condition Type Groups for Accruals</p><p>2. Check condition type group 0C01 Commission Settlement for accruals and the assigned</p><p>condition types as shown below.</p><p>80</p><p>Explanation: Condition type groups for accruals are assigned to condition contract types,</p><p>condition type group 0C01 Commission Settlement is assigned to the four condition contract</p><p>types described in this document (see chapter Specify Settlement Settings for Condition</p><p>Contract Types).</p><p>Condition type RCA1 Commission Accruals within the condition type group 0C01 Commission</p><p>Settlement is the accruals condition type for which you maintain records in the condition</p><p>contract. Condition type RCA6 Commission Accruals belongs to commission condition type</p><p>RCS6 for which you also maintain accruals in one line in the condition contract.</p><p>The assigned target conditon type RCA2 Commission AccrRev is used in pricing procedure</p><p>A10009 to adopt the amount for the accruals reversal during a settlement run (see chapter</p><p>Define Pricing Procedures).</p><p>The assigned target conditon type for delta accruals RCD2 Commission Accr Total is used in</p><p>pricing procedure A10013 to adopt the total amount of already reversed accruals (see chapter</p><p>Define Pricing Procedures).</p><p>Condition type RCA5 Commission AccrSettl is the condition type that is used for the situation in</p><p>a settlement run when not all accruals are to be reversed (for example, accruals higher than the</p><p>settlement amount are to be transferred to the next settlement). You also specify this condition type</p><p>directly in the condition contract type (see chapter Specify Settlement Settings for Condition</p><p>Contract Types).</p><p>2.3.8. Define Number Ranges</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Define Number Ranges</p><p>2. On the following Edit Intervals: Settlement Managemnt, Object W_LFAKTURA screen,</p><p>choose function Display intervals check number range 01 as shown below.</p><p>81</p><p>Explanation: You assign number ranges to settlement document types (see chapter Define</p><p>Settlement Document Types). In the standard delivery, number range 01 is assigned to all</p><p>settlement document types contained in the standard delivery for commission scenarios.</p><p>2.3.9. Define Country-Specific Number Ranges</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Specify Country Specific Number Ranges</p><p>2. Check number range group 0001 General.</p><p>Explanation: In some countries, country specific number ranges are required for settlement</p><p>documents - at least for settlement documents which require a payment run in Financial</p><p>Accounting.</p><p>The general setting of the number ranges is defined on settlement document type level which is</p><p>of course not country specific. To allow a country specific number range assignment this</p><p>customizing activity was introduced to assign on a group level unique number ranges per</p><p>country.</p><p>For the countries which require country specific number ranges you have to define the country</p><p>related number ranges and you have to assign the number ranges to the number range group.</p><p>The number range group 0001 General is already assigned to the settlement document types</p><p>which will create journal entries with open items for payment. When the number range group</p><p>contains relevant country specific number ranges then theses number ranges have a higher</p><p>priority than the number range explicitly assigned to a settlement document type.</p><p>2.3.10. Define Process Categories</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Define Process Categories</p><p>2. Check process category 0C Commission Settlement as shown below.</p><p>82</p><p>Explanation: You assign process categories to settlement process types. Process category 0C</p><p>Commission Settlement is assigned to the settlement process types 0C10 to 0C60 described in</p><p>this document (see chapter Define Settlement Process Types).</p><p>Process category 0C is used to bundle settlement documents for commission settlement, for</p><p>example, in reporting.</p><p>2.3.11. Specify Text Determination</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Specify Text Determination</p><p>2. Choose activity Set Up Access Sequence for Settlement Document Header.</p><p>Check access sequences with corresponding</p><p>accesses as shown below.</p><p>83</p><p>Explanation: You assign access sequences to text IDs as shown in the next configuration step.</p><p>In case of a settlement document cancellation, these settings for the access sequences enable</p><p>the copying of texts for text IDs 0C02 and 0C03 from the reversed settlement document to the</p><p>reversal settlement document.</p><p>3. Choose activity Set Up Text Determination for Settlement Management Document Header.</p><p>Check text procedures with corresponding text IDs and text procedures assignment to</p><p>settlement document types as shown below. (Note that you usually assign text procedures in</p><p>the maintenance of settlement document described below but this view gives you a good</p><p>averview already.)</p><p>84</p><p>Explanation: The text procedure for collectice settlement documents does not contain text ID</p><p>0C03 Contract Text for Output/Forms as a collective settlement document is usually related to</p><p>several condition contracts for which this text can be different.</p><p>2.3.12. Define and Configure Text Transfer Groups</p><p>In this Custiomizing activity, you make settings to copy texts from the condition contract into</p><p>settlement documents.</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settllement</p><p>→ Define and Configure Text Transfer Groups</p><p>2. Check text transfer group 1 Commissions as shown below</p><p>85</p><p>Explanation: The text maintained for text ID 0C03 Text for Settlement Document in a condition</p><p>contract is copied to the settlement document, text ID 0C03 Contract Text for Output/Forms.</p><p>You assign text transfer groups to condition contract types. Text transfer group 1 Commissions</p><p>is assigned to condition contract types 0CS1 to 0CS4.</p><p>2.3.13. Define Posting Rules</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Define Posting Rules</p><p>2. Check posting rule 0A Accruals Only as shown below.</p><p>Explanation: You assign posting rules to settlement document types. Posting rule 0A Accruals</p><p>Only is assigned to settlement document type 0C61 (0C63) Commission Accruals Reversal</p><p>(Reversal), see chapter Define Settlement Document Types. The posting rule ensures that for</p><p>the accruals reversal settlement, which is similar to a normal settlement, only the accruals</p><p>reversal is posted but no commission amounts.</p><p>86</p><p>2.3.14. Define Field Change Groups for Cancellation</p><p>Documents</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Define Field Change Groups for Cancellation Documents</p><p>2. Check field change group for cancellation 0R Rebate as shown below.</p><p>Explanation: You assign field change group for cancellation to settlement document types, field</p><p>change group for cancellation 0R Rebate is assigned to the settlement document types for</p><p>cancellation used in the commission scenarios; excepted is settlement document types for the</p><p>reversal of manual settlement documents (see chapter Define Settlement Document Types).</p><p>Field change group for cancellation 0R Rebate allows you to change the document date (field</p><p>BLDAT) and the reference document number (field XBLNR) in the reversal settlement document.</p><p>A related configuration setting is the field status group (see chapter Define Field Status Groups).</p><p>The field status group 0C02 Commission Settlement Manual sets fields KOMLFK-XBLNR and</p><p>KOMLFK-BLDAT as required fields.</p><p>87</p><p>2.3.15. Define Settlement Document Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Documents → Settlement Document Types → All Document</p><p>Types</p><p>2. Check the following settlement document types.</p><p>Settlement Document Type Description</p><p>0C11 Commission</p><p>0C13 Commission Reversal</p><p>0C15 Commission Debit</p><p>0C17 Commission Debit Reversal</p><p>0C21 Commission Parked</p><p>0C23 Commission Parked Reversal</p><p>0C31 Commission Manual</p><p>0C33 Commission Manual Reversal</p><p>0C41 Commission Delta Accruals</p><p>0C43 Commission Delta Accruals Reversal</p><p>0C4A Commission Manual Delta Accruals</p><p>0C4C Commission Manual Delta Accruals Rev</p><p>0C51 Commission Proforma</p><p>0C53 Commission Proforma Reversal</p><p>0C55 Commission Debit Proforma</p><p>0C57 Commission Debit Proforma Reversal</p><p>0C61 Commission Accruals Reversal</p><p>0C63 Commission Accruals Reversal Reversal</p><p>0C91 Commission Settlement Collection</p><p>0C93 Commission Settlement Collection Rev</p><p>0C95 Commission Settlement Collection Debit</p><p>0C97 Commission Settlement Coll Debit Rev</p><p>88</p><p>You assign settlement document types to condition contract types. The following table gives you</p><p>an overview of this assignment.</p><p>Settlement Document Types for</p><p>Condition</p><p>Contract</p><p>Type</p><p>Customer</p><p>Settlement</p><p>Proforma</p><p>Settlement</p><p>Manual</p><p>Settlement</p><p>Delta</p><p>Accruals</p><p>Settlement</p><p>Accruals</p><p>Reversal</p><p>0CS1 0C11 0C51 0C31 0C42 0C61</p><p>0CS2 0C21 0C51 0C31 0C42 0C61</p><p>0CS3 0C11 0C51 0C31 0C42 0C61</p><p>0CS4 0C21 0C51 0C31 0C42 0C61</p><p>The basic settlement document type for the commission settlement scenario is 0C11</p><p>Commission Invoice. Parameters for this settlement document types are explained in detail. For</p><p>all other settlement document types, only the diffferences are explained.</p><p>The following table gives you an overview of the alternative settlement document types. The</p><p>relationship is mutual.</p><p>0C11 0C15</p><p>0C51 0C55</p><p>0C91 0C95</p><p>89</p><p>Settlement document type 0C11 Commission</p><p>90</p><p>91</p><p>Explanation: This settlement document type represents the settlement option that you send the</p><p>supplier an invoice. Accordingly, the settlement document category is 01 Single Document of</p><p>Type Invoice in the General Control group box.</p><p>You also see that change documents are active at document level.</p><p>Concerning the handling of a negative amount for the settlement document, you can see –</p><p>because of value 3 Change Settlement Document Type if Partner Posting for the Handle</p><p>negative Amount parameter – that the system shall then use the alternative settlement</p><p>document type 0C15 Commission Debit. You also see that the material validity shall not be</p><p>checked.</p><p>In the Number Range group box above, you can see that the number range is 01 Settlement</p><p>Managemnt (see chapter Define Number Ranges). Additionally, number range group 0001</p><p>General is assigned (see chapter Specify Country Specific Number Ranges).</p><p>In the Document Entry / Default Data group box, you can see that the change scope is restricted</p><p>to 1 Only Posting Date and Posting Period. Settlement documents should not be changed or</p><p>deleted deliberately or by accident. If a change is required, the best practice is to cancel the</p><p>settlement document, do necessary changes in the condition contract, and then re-create the</p><p>settlement document. On the other hand, posting date or posting period changes are</p><p>sometimes required when a certain posting period has already been closed.</p><p>The Zero Values Allowed for Items Amounts checkbox is selected because zero is calculated as</p><p>value, for example, when the first scale level, serving as threshold, has not been reached.</p><p>In the VAT Registration Number group box, you can see that the supplier VAT ID is proposed</p><p>from the supplier’s master data and that the company code country is used for the country</p><p>determination.</p><p>In the Partner group box, you can see the partner schema for header partner 0CS1 Commission</p><p>and the partner schema for item partner 0C01 Commission. Value 1 Are Determined from</p><p>92</p><p>Master Data for the Partner Determination from Master Data parameter controls that partners</p><p>are determined from the master data of the condition contract partner.</p><p>In the Text Determination group box, you can see text determination procedure 0C</p><p>Sales</p><p>Commissions for the document header. Text ID 0C02 External Text for Output/Forms shall</p><p>appear on the Accounting tab page. Text change is always allowed even when the settlement</p><p>document has already been posted to Accounting.</p><p>In the Pricing group box, you can see that the application for price determination is V</p><p>Sales/Distribution. Accordingly, pricing procedures A10012 to A10014 have been defined for</p><p>application V (see chapter Define Pricing Procedures). Document schema group 0C</p><p>CommissionSettlement (see chapter Define Document Schema Groups for Settlement</p><p>Document Types) is assigned to differentiate the pricing procedure determination (see chapter</p><p>Specify Pricing Procedure Determination). You can also see that not only zero values are</p><p>allowed but also a negative net value and a negative effective value. In a certain settlement</p><p>period, for example, the amount of returns could be higher than the amount of sales. The No</p><p>Check for Price Condition in Calculation Schema is selected as there is no price condition in the</p><p>pricing procedure. The Propose Tax Departure Country/Region checkbox is selected to get a</p><p>default value for the tax departure country.</p><p>In the Accounting group box, you can see that according to settlement document category 01</p><p>Single Document of Type Invoice a journal entry with journal entry type KR Vendor Invoice will</p><p>be created. Note: As the Posting Block for Transfer to Accounting checkbox is not selected, the</p><p>settlement document will be passed to FI automatically. Additionally, you can see that statistical</p><p>conditions are not passed to FI, and that no tax type check will be performed for the journal</p><p>entry creation.The current settlement document number will be used for the reference number in</p><p>the journal entry. In addition, the Fill Reference Item in Universal Journal checkbox is selected</p><p>so that the item number of the settlement management document is filled in the universal journal line</p><p>item. You can also see that the profitability analysis is active together with value 3 Customer</p><p>from Item / Bill-To Party for the Customer for Profitability Analysis parameter.</p><p>In the Control of Account Determination group box, you can see that for the FI postings related</p><p>to settlement documents the account determination procedure has been set to V SD Account</p><p>Determination. This means that settings you maintain in the Customizing for Settlement</p><p>Management under Basic Functions → Account Account Determination → Revenue Account</p><p>Determination (SD) are relevant (see chapter Assign G/L Accounts). You also see that KOFRC0</p><p>Commission Settlement has been specified as the procedure for account determination.</p><p>Account key 0C1 Commission Settlement is set for the Account Key for Clearing Line</p><p>parameter.</p><p>In the Cancellation group box, you can see that 0C13 Commission Invoice Reversal is specified</p><p>as the settlement document type for the reversal settlement document.</p><p>In the Special processes group box, you can see value 1 Events are Called for the Control of</p><p>Event Call-Up parameter so that the event management for the business workflow is called.</p><p>93</p><p>Settlement document type 0C13 Commission Reversal</p><p>Explanation: As 0C13 Commission Reversal is the reversal settlement document type for</p><p>settlement document type 0C11 Commission, the settlement document category is 03 Single</p><p>Document of Type Credit Memo. Note: This settlement document category ensures that you can</p><p>cancel a document when you have cleared items in FI. Because of the inverse settlement</p><p>category, the Invert Sign for Amount/Qty in Reporting parameter is set to 1 Invert Sign of</p><p>Amount / Quantity Fields.</p><p>In the VAT Registration Number group box, you can see that the customer VAT ID shall not be</p><p>proposed for the cancellation document because this information is copied from the cancelled</p><p>document.</p><p>Similarly, partner data are not determined new from master data but copied from the canceled</p><p>document.</p><p>In the Cancellation group box, no settlement document type for reversal is specified. Instead,</p><p>the Settlement Doc Type Only f. Cancellation checkbox is selected. FI Cancellation Method X</p><p>Cleared Automatically if Possible supports an automatic clearing of the open FI items. If a</p><p>payment has taken place the standard FI creation process will be performed. Value 1</p><p>Independent of Preceding Document is chosen for the Posting of Reversal Document parameter</p><p>to ensure that in case of standard FI creation the posting of the reversal settlement document is</p><p>done independently of the posting of the reversed settlement document. See field help for more</p><p>information. You can see that 0R Rebate (see chapter Define Field Change Groups for</p><p>Cancellation Documents) is used for the field change group for cancellation.</p><p>All other parameter values are identical to 0C11.</p><p>94</p><p>Settlement document type 0C15 Commission Debit</p><p>Explanation: Settlement document type 0C15 Commission Debit is the alternative settlement</p><p>document type for settlement document type 0C11 Commission, which the system uses to create</p><p>the settlement document when the determined gross amount is negative. The settlement document</p><p>category is 03 Single Document of Type Credit Memo to create a credit memo with positive</p><p>amount instead of an invoice with negative amount. Accordingly, the Invert Sign for Amount/Qty</p><p>in Reporting parameter is set to 1 Invert Sign of Amount / Quantity Fields and the journal entry</p><p>type is KG Vendor Credit Memo. The settlement document type for the reversal settlement</p><p>document is 0C17 Commission Debit Reversal (not shown in screenshot).</p><p>All other parameters are identical to 0C11 which is also checked when you specify an</p><p>alternative settlement document type.</p><p>Settlement document type 0C17 Commission Debit Reversal</p><p>Explanation: As 0C17 Commission Debit Reversal is the reversal settlement document type for</p><p>settlement document type 0C15 Commission Debit, the settlement document category is 01</p><p>Single Document of Type Invoice. As reversal settlement document type for an alternative</p><p>settlement document type having the same settlement document category as settlement</p><p>document type 0C11, the Invert Sign for Amount/Qty in Reporting parameter is blank.</p><p>Additionally, the inversed journal entry type is KG Vendor Credit Memo is used (not shown as</p><p>screenshot).</p><p>All other parameters are identical to 0C13.</p><p>95</p><p>Settlement document type 0C21 Commission Parked</p><p>Explanation: Settlement document type 0C21 is used for the scenario in which settlement</p><p>documents are not transferred directly to FI but bundled in a so called collective settlement</p><p>document. This document is then transferred to FI. The creation of the collective settlement</p><p>document is controlled by the corresponding settlement process type 0C20 Commission</p><p>Settlement - Two Step (see chapter Define Settlement Process Types).</p><p>There are the following differences for 0C21 Commission Parked compared with 0C11. There is</p><p>no number range group assigned. This is not necessary because no country-specific</p><p>differentiation is required as the FI transfer happens with the collective settlement document.</p><p>There is no special handling for a negative gross amount – and therefore no alternative</p><p>settlement document type is specified – as this handling happens with the collective settlement</p><p>document (see settlement document type 0C91).</p><p>The tax determination method is Redetermine from FI. The profitability analysis is inactive. The</p><p>Credit Memo with Value Date checkbox is not selected for a parked settlement document. The</p><p>Account Key for Clearing Line parameter is initial (not shown as screenshot).</p><p>The settlement document type for the reversal settlement document is 0C23 Commission</p><p>Parked Reversal.</p><p>Settlement document types 0C23 Commission Parked Reversal</p><p>Explanation: There are the following differences compared with 0C13: There is no number</p><p>range group assigned.</p><p>The tax determination method is Redetermine from FI. The profitability</p><p>analysis is inactive, the Credit Memo with Value Date checkbox is not selected. The Account</p><p>Key for Clearing Line parameter is initial.</p><p>96</p><p>Settlement document type 0C31 Commission Manual</p><p>Explanation: There are several differences for 0C31 Commission Manual compared with 0C11.</p><p>There is no number range group assigned.</p><p>The Handle Negative Amount parameter has value 1 Error if Partner Posting as a negative</p><p>gross amount is not allowed for manual settlement documents. Accordingly, no alternative</p><p>settlement document type is specified.</p><p>The value for parameter Change Scope is Unrestricted reflecting the manual settlement</p><p>document creation.</p><p>In the Pricing group box, you can see that document schema group 0E Commission Manual</p><p>(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so</p><p>that the different pricing procedure A10014 Commission Manual (Germany) is determined (see</p><p>chapter Specify Pricing Procedure Determination).</p><p>In the Accounting group box, you can see that parameter Partner Lines at Item Level has value</p><p>X Yes.</p><p>In the Cancellation group box, you can see settlement document type 0C33 Commission</p><p>Manual Reversal for the reversal settlement document (not shown as screenshot).</p><p>97</p><p>Settlement document types 0C33 Commission Manual Reversal</p><p>Explanation: There are three differences compared with (!) 0C31: Supplier VAT ID is not</p><p>determined, there is no settlement document type for cancellation assigned, the Settlement Doc</p><p>Type Only f. Cancellation checkbox is selected.</p><p>Note: No field change group for cancellations is assigned – in contrast to other settlement</p><p>document types for cancellation – as settlement documents with this settlement document types</p><p>are created manually anyway.</p><p>98</p><p>Settlement document type 0C41 Commission Delta Accruals</p><p>Explanation: There are several differences compared with 0C11.</p><p>There is no number range group assigned.</p><p>In the General Control group box, you can see that the settlement category is F Material</p><p>Adjustment. This settlement category ensures that the offset posting will be done on a G/L</p><p>account instead on a supplier or customer account.</p><p>There is no special handling of a negative gross amount.</p><p>In the Document Entry / Default Data group box, you can see that the Entry of Tax Code</p><p>parameter has value 3 No Input of Tax Codes Possible. This value is used since no tax code or</p><p>tax items will be passed to FI for the delta accrual posting anyway.</p><p>There is no text determination, that is no text determination procedure and text ID is maintained</p><p>(not shown as screenshot).</p><p>99</p><p>In the VAT Registration Number group box, you can see that the values for parameters</p><p>Customer VAT ID and Country Determination for Cust. VAT ID are initial (not shown as</p><p>screenshot) as the customer VAT ID is not relevant for delta accruals.</p><p>In the Pricing group box, the document schema group is 0D Commission DeltaAcc so that</p><p>pricing procedure A10013 is determined (see chapter Specify Pricing Procedure</p><p>Determination). Checkbox Propose Tax Departure Country is not selected as tax does not play</p><p>a role.</p><p>In the Accounting group box, you can see that the journal entry type is AB Accounting</p><p>Document. The Credit Memo with Value Date checkbox is not selected.</p><p>In the Control of Account Determination group box, account key 0C1 Commission Settlement</p><p>(see chapter Define Account Keys) has been set for the Account Key Offset Acc. Mat.</p><p>Adjustment field. This account key controls which account is determined for the accruals posting</p><p>in the delta accruals settlement run (see chapter Assign G/L Accounts).</p><p>In the Cancellation group box, you can see settlement document type 0C43 Commission Delta</p><p>Accruals Reversal for the reversal settlement document (not shown as screenshot).</p><p>Settlement document type 0C43 Commission Delta Accruals Reversal</p><p>Explanation: When you compare 0C43 with (!) 0C41 you can see that the only differences that</p><p>occur concern the Invert Sign for Amount/Qty in Reporting parameter – inversion is active - and</p><p>settings for document cancellation (the settlement document category and settings in the</p><p>Cancellation group box) as described, for example, for 0C13.</p><p>Settlement document type 0C4A Commission Delta Accruals</p><p>Explanation: There are the following differences compared with 0C31 (!).</p><p>In the Pricing group box, you can see that document schema group 0H Commission Man DAccr</p><p>(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so</p><p>that pricing procedure A10017 Commission ManDAccr (Germany) is determined (see chapter</p><p>Specify Pricing Procedure Determination).</p><p>In the Cancellation group box, you can see settlement document type 0C4C Commission</p><p>Manual Delta Accruals Rev for the reversal settlement document (not shown as screenshot).</p><p>Settlement document type 0C4C Commission Manual Delta Accruals Rev</p><p>100</p><p>Explanation: There are the following differences compared with 0C33.</p><p>In the Pricing group box, you can see that document schema group 0H Commission Man DAccr</p><p>(see chapter Define Document Schema Groups for Settlement Document Types) is assigned so</p><p>that pricing procedure A10017 Commission ManDAccr (Germany) is determined (see chapter</p><p>Specify Pricing Procedure Determination).</p><p>101</p><p>Settlement document type 0C51 Commission Proforma</p><p>Explanation: Settlement document type 0C51 Commission Proforma has the following</p><p>differences compared with 0C11. First, there is no number range group assigned.</p><p>The alternative settlement document type for a negative gross amount is 0C55 Commission</p><p>Debit Proforma.</p><p>In the General Control group box, you can see that the settlement category is D Pro Forma</p><p>Invoice reflecting the purpose of this settlement document type.</p><p>In the VAT Registration Number group box, you can see (not shown as screenshot) that the</p><p>supplier VAT ID shall not be proposed as the supplier VAT ID is not relevant for pro forma</p><p>invoices.</p><p>The tax determination method is Redetermine from FI.</p><p>The Account Key for Clearing Line parameter is initial (not shown as screenshot).</p><p>In the Cancellation group box, you can see settlement document type 0C53 Commission</p><p>Proforma Reversal for the reversal settlement document (not shown as screenshot).</p><p>Settlement document types 0C53 Commission Proforma Reversal</p><p>Explanation: When you compare 0C53 with (!) 0C51 you can see that the only differences</p><p>concern the Invert Sign for Amount/Qty in Reporting parameter – inversion is active - and</p><p>settings for document cancellation (the settlement document category and settings in the</p><p>Cancellation group box) as described, for example, for 0C13.</p><p>Alternative settlement document types 0C55 & 0C57</p><p>Explanation: Same differences compared with 0C51 & 0C53 as explained for 0C15 & 0C17</p><p>102</p><p>Settlement document type 0C61 Commission Accruals Reversal</p><p>Explanation: Settlement document type 0C61 has the following differences compared with</p><p>0C11. There is no number range group assigned. There is no special handling of a negative</p><p>gross amount.</p><p>In the VAT Registration Number group box, you can see (not shown as screenshot) that the</p><p>supplier VAT ID shall not be proposed as the supplier VAT ID does not play a role for the</p><p>accruals reversal. There is no output determination (not shown as screenshot).</p><p>In the Pricing group box, the tax determination method is Redetermine from FI. The Propose</p><p>Tax Departure Country checkbox is not selected (not shown as a screenshot) as tax does not</p><p>play a role.</p><p>In the Accounting group box, you can see – as the relevant difference – that the supplier posting</p><p>rule is 0A Accruals Only (see chapter Define Posting Rules).</p><p>In the Cancellation group box, you can see settlement document type 0C63 Commission</p><p>Accruals Reversal Reversal for the reversal settlement document (not shown as screenshot).</p><p>Settlement document types 0C63 Commission Accruals Reversal Reversal</p><p>Explanation: When you compare 0C63 with (!) 0C61, you can see that the only differences</p><p>concern the Invert Sign for Amount/Qty in Reporting parameter – inversion is active - and</p><p>103</p><p>settings for cancellation (the settlement document category and settings in the Cancellation</p><p>group box) as described, for example, for 0C13.</p><p>Note: During document reversal, the posting rule is copied from the document to be reversed</p><p>but the supplier posting rule 0A is set (redundantly) for transparency reasons.</p><p>Settlement document type 0C91 Commission Settlement Collection</p><p>Explanation: Settlement document type 0C91 has the following differences compared with</p><p>0C11.</p><p>The use of this settlement document type is reflected in the variant V Settlement Document</p><p>Collection.</p><p>The alternative settlement document type for a negative gross amount is 0C95 Commission</p><p>Settlement Collection Debit (not shown as screenshot).</p><p>In the VAT Registration Number group box, you can see (not shown as screenshot) that the</p><p>supplier VAT ID shall not be proposed as the supplier VAT ID is copied from the single</p><p>settlement documents.</p><p>In the Text Determination group box, you can see that the text determination procedure is 1S</p><p>Commissions Coll.</p><p>In the Follow-On Document Creation General group box, you can see value 1 Take Settlement</p><p>Doc Category Preceding Document into Account for the Consid. of SDoc. Cat. for Follow-On</p><p>Docs parameter.</p><p>In the Cancellation group box, you can see settlement document type 0C93 Commission</p><p>Settlement Collection Rev for the reversal settlement document (not shown as screenshot).</p><p>Settlement document type 0C93 Commission Settlement Collection Rev</p><p>Explanation: There are the following differences compared with 0C13.</p><p>104</p><p>The usage of this settlement document type is reflected in the variant V Settlement Document</p><p>Collection.</p><p>In the Text Determination group box, you can see that the text determination procedure is 1C</p><p>Commissions Coll.</p><p>In the Follow-On Document Creation General group box, you can see value 1 Take Settlement</p><p>Doc Category Preceding Document into Account for the Consid. of SDoc. Cat. for Follow-On</p><p>Docs parameter (not shown as screenshot).</p><p>Alternative settlement document types 0C95 & 0C97</p><p>Explanation: Same differences compared with 0C91 & 0C93 as explained for 0C15 & 0C17</p><p>105</p><p>2.3.16. Assign Transfer Groups to Settlement Document Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Documents → Specify Settings for Transfer Manager</p><p>2. Choose activity Assign Transfer Groups to Settlement Document Type (via Event) on the</p><p>following dialog box.</p><p>3. Select transfer event 18 Data Transfer - Collective Document Header and choose Assign</p><p>Settlement Document Types in the Dialog Structure frame. Check the assignment of</p><p>settlement document types with transfer group 0C01 as parameter as shown below.</p><p>4. Select transfer event 20 Pricing Data - Change Header (KOMK) Supplier Side. Check the</p><p>assignment of settlement document types with transfer group 0C01 Commission Settlement</p><p>as parameter as shown below.</p><p>106</p><p>5. Select transfer event 22 Pricing Data - Change Item (KOMP) Supplier Side. Check the</p><p>assignment of settlement document types with transfer group 0C01 Commission Settlement</p><p>as parameter as shown below.</p><p>107</p><p>6. Select transfer event 3H Account Determination in Sales and Distribution (SD). Check the</p><p>assignment of settlement document types with transfer group 0CC1 as parameter as shown</p><p>below.</p><p>7. Select event 63 Default Header Data - Document Reversal. Check the assignment of</p><p>108</p><p>settlement document types with transfer group 0R Rebate as parameter as shown below.</p><p>8. Select event 6I Set Final Document Number. Check the assignment of settlement</p><p>document types with transfer group 0R as parameter as shown below.</p><p>Explanation: Transfer group 0C01 Commission Settlement (see chapter Specify Settings for</p><p>Transfer Manager) for transfer event 18 is assigned to settlement document type 0C91 / 0C95</p><p>to create the collective settlement document.</p><p>Transfer group 0C01 Commission Settlement (see chapter Specify Settings for Transfer</p><p>Manager) for transfer events 20 and 22 is assigned to settlement document types used in the</p><p>commission settlement scenarios.</p><p>Transfer group 0R Rebate (see chapter Specify Settings for Transfer Manager) for transfer</p><p>event 63 is assigned to all settlement document types for reversal settlement documents used</p><p>in the commission settlement scenarios except the settlement document type for the reversal of</p><p>manual created settlement documents.</p><p>109</p><p>Transfer group 0C01 Commission Settlement (see chapter Specify Settings for Transfer</p><p>Manager) for transfer event 6I is assigned to all settlement document types used in the</p><p>commission settlement scenarios with a data transfer to FI.</p><p>2.3.17. Define Field Status Groups</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Process → Define Field Status Groups</p><p>2. Check field status groups with the assigned fields as shown below.</p><p>110</p><p>Explanation: Note: You assign field status groups to settlement process types. Field status</p><p>group 0C02 Commission Settlement Manual is assigned to settlement process type 0C30</p><p>Commission Settlement Manual and field status group 0C01 Commission Settlement is</p><p>assigned to all other settlement process types described in this document (see chapter Define</p><p>Settlement Process Types).</p><p>Field status group 0C01 Commission Settlement hides the Fix Value Date (Customer) and</p><p>Additional Value Days (Customer) fields in the settlement document's header area as these</p><p>fields are not filled automatically by the settlement report.</p><p>Additionally, the Payment Reference field on the Basic Data tab page is hidden.</p><p>Field status group 0C02 Commission Settlement Manual sets the document date (field</p><p>KOMLFK-BLDAT) and the reference document number (field KOMLFK-XBLNR) as required fields.</p><p>2.3.18. Define Column Sorting Groups</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Process → Define Column Sorting Groups</p><p>2. Check the column sorting groups with corresponding colums as shown below.</p><p>111</p><p>112</p><p>Explanation: You assign column sorting groups to settlement process types (see chapter Define</p><p>Settlement Process Types). Column sorting group 0C01 Commission Settlement is assigned to</p><p>settlement process types 0C10 Commission Settlement, 0C20 Commission Settlement - Two</p><p>Step, 0C40 Commission Settlement Delta Accruals, and 0C60 Commission Settlement Accruals</p><p>Reversal. Column sorting group 0C02 Commission Settlement Manual is assigned to settlement</p><p>process type 0C30 Commission Settlement Manual.</p><p>113</p><p>2.3.19. Define Settlement Process Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Process → Define Settlement Process Types</p><p>2. Check the following settlement process types.</p><p>Settlement Process Type Description</p><p>0C10 Commission Settlement</p><p>0C20 Commission Settlement - Two Step</p><p>0C30 Commission Settlement Manual</p><p>0C40 Commission Settlement Delta Accruals</p><p>0C60 Commission Settlement Accruals Reversal</p><p>The basic settlement process type for the commission settlement scenarios is 0C10</p><p>Commission Settlement. So, parameters are explained for this settlement document type in</p><p>detail. For all other settlement process types, only the diffferences are explained.</p><p>All parameter values starting from</p><p>group box Customer-Side Settlement are initial – with the</p><p>exception of settlement process 0C20 for which you specify settings for the collection of</p><p>settlement documents in the Collection of Settlement Documents group box. So, this part is only</p><p>shown once for settlement process type 0C10. In addition, group box Collection of Settlement</p><p>Documents is shown for 0C20.</p><p>114</p><p>Settlement process type 0C10 Commission Settlement</p><p>115</p><p>Explanation: In the commission settlement scenarios, we create settlement documents during</p><p>the settlement runs. So, Settlement Document is set for the settlement process category in the</p><p>Control group box. This also means that settlement documents are directly transferred to FI and</p><p>not parked.</p><p>As the settlement document is a purchasing-sided document, value 1 Only Supplier Side is set</p><p>for the Settlement Partner Category parameter and value Supplier-Side is set for the Price</p><p>Determin. on Supplier/Customer parameter.</p><p>You can see value D Only Document Schema for the Calculation Schema Determination Type</p><p>(see chapter Specify Pricing Procedure Determination).</p><p>You can see value C Material-Related With Logistics Data for the Entry Category for Logistics</p><p>Data parameter as settlement data is entered including material related data.</p><p>As the Post Business Volume in Accounting parameter has value P Using Pricing, the business</p><p>volume is posted in the journal entry using the account keys specified in the pricing procedure (see</p><p>chapters Define Pricing Procedures, Define Settlement Document Types see section Control of</p><p>Account Determination, and chapter Assign G/L Accounts).</p><p>You can see that the tax code is determined from pricing (value 3 From Price Determination for</p><p>the Tax Code Determination parameter).</p><p>The Post Tax Amounts checkbox is selected as the tax amount has to be posted to FI as well</p><p>for the right A/P account.</p><p>The Check Allowed Settlement Doc. Type checkbox is selected with view on the future</p><p>enhancement, for example, for the entry of the settlement document type when you want to</p><p>cancel a settlement document.</p><p>You can see that 0C Commission Settlement is set for the Business Process Category</p><p>parameter (see chapter Define Process Categories).</p><p>In the Check Settlement Management Relevance for Business Partner sub group box, you can</p><p>see – from value 1 No Check for the Check Sett. Mgmt. Relevance for Supplier parameter –</p><p>that the Settlement Management relevance shall not be checked for the supplier. Typically, this</p><p>check is only relevant for the core settlement management processes such as agency business.</p><p>In the Default Values group box, you can see that the tax amount and the gross item amount is</p><p>calculated - Calculate Tax Amount checkbox is selected and value C Automatically for List and</p><p>Single Documents for the Determine Gross Value Automatically parameter is set.</p><p>116</p><p>In the Document Entry Control group box, you can see value 0C01 Commission Settlement for</p><p>the field status group (see chapter Define Field Status Groups) and 0C01 Commission</p><p>Settlement for the column sorting group (see chapter Define Column Sorting Groups).</p><p>In the Assigned Settlement Document Types group box, sub group box Single Document, you</p><p>can see value 0C11 Commission for the Settlement Document Type parameter (see chapter</p><p>Define Settlement Document Types and chapter Allowed Combinations Settlement Process</p><p>Type / Settlement Document Type).</p><p>117</p><p>Settlement process type 0C20 Commission Settlement - Two Step</p><p>Explanation: Settlement process type 0C20 is designated to create so called parked settlement</p><p>documents that are not released to FI immediately. Instead, these settlement documents shall</p><p>be bundled in a collective settlement document which is then released to FI. Accordingly, the</p><p>Settlement Process Category parameter is B Document Parking and the settlement procedure is</p><p>2 Collection of Settlement Documents.</p><p>In addition, settlement process type 0C10 Commission Settlement and settlement document</p><p>type 0C91 Commission Settlement Collection for the collection settlement document are</p><p>specified for 0C20 in the Collection of Settlement Documents group box. Value 2 Active at Item</p><p>Level is set for the Collection Category for Settlement parameter.</p><p>The settlement document type for the single document is 0C21.</p><p>Other parameter values are identical to 0C10.</p><p>118</p><p>Settlement process type 0C30 Commission Settlement Manual</p><p>Explanation: Settlement process type 0C30 is designated to create manual settlement</p><p>documents. In the Control group box, you can see B With Logistics Data for the Entry Category</p><p>for Logistics Data parameter.</p><p>Additionally, you can see value Manual Entry for the Tax Code Determination parameter, as the</p><p>tax code is specified on the external invoice.</p><p>In the Document Entry Control group box, you can see value 0C02 Commission Settlement</p><p>Manual for the field status group (see chapter Define Field Status Groups) and 0C02</p><p>Commission Settlement Manual for the column sorting group (see chapter Define Column</p><p>Sorting Groups).</p><p>In the Assigned Settlement Document Types group box, you can see value 0C31 Commission</p><p>Manual for the Settlement Document Type parameter (not shown as screenshot).</p><p>Other parameter values are identical to 0C10.</p><p>119</p><p>Settlement process type 0C40 Commission Settlement Delta Accruals</p><p>Explanation: Settlement process type 0C40 is designated to create a settlement document for a</p><p>delta accruals settlement run.</p><p>In the Default Values group box, you can see value D No Terms of Payment for the Default for</p><p>Payment Terms of Supplier because payment terms can be defined on condition contract level.</p><p>In the Assigned Settlement Document Types group box, you can see value 0C41 Commission</p><p>Delta Accruals for the Settlement Document Type parameter (see chapter Define Settlement</p><p>Document Types and see also following chapter Allowed Combinations Settlement Process</p><p>Type / Settlement Document Type).</p><p>Other parameter values are identical to 0C10.</p><p>Settlement process type 0C4A Commission Manual Delta Accruals</p><p>Explanation: Settlement process type 0C4A is designated to create a settlement document for a</p><p>delta accruals settlement run in manual settlement scenarios.</p><p>In the Default Values group box, you can see value D No Terms of Payment for the Default for</p><p>Payment Terms of Supplier because payment terms can be defined on condition contract level.</p><p>The column sorting group is 0004 Commission Settlement Manual Accruals.</p><p>In the Assigned Settlement Document Types group box, you can see value 0C41 Commission</p><p>Delta Accruals for the Settlement Document Type parameter (see chapter Define Settlement</p><p>Document Types and see also following chapter Allowed Combinations Settlement Process</p><p>Type / Settlement Document Type).</p><p>Other parameter values are identical to 0C10.</p><p>120</p><p>Settlement process type 0C60 Commission Settlement Accruals Reversal</p><p>Explanation: Settlement process type 0C60 is designated to create a settlement document for a</p><p>final accruals reversal.</p><p>In the Assigned Settlement Document Types group box, you can see value 0C61 Commission</p><p>Accruals Reversal for the Settlement Document Type parameter (see chapter Define Settlement</p><p>Document Types and see also following chapter Allowed Combinations Settlement Process</p><p>Type / Settlement Document Type).</p><p>Other parameter values are identical compared with 0C10.</p><p>121</p><p>2.3.20. Allowed Combinations Settlement Process Type /</p><p>Settlement Document Type</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Process → Allowed Combinations Settlement Process Type /</p><p>Settlement Document Type</p><p>2. Check allowed combinations as shown below.</p><p>Explanation: In the commission settlement scenarios, we have pre-defined combinations of</p><p>settlement process type</p><p>and settlement document type for the different types of settlement</p><p>('normal' partial and final settlement, proforma settlement, manual settlement, delta accruals</p><p>settlement, and accruals reversal settlement).</p><p>2.3.21. Specify Copy Control</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Specify Copy Control</p><p>2. Choose activity Settlement Management Document to Settlement Management Document.</p><p>3. Check copy control entries as shown. Double-click an entry to see the corresponding</p><p>parameter settings. The parameter values are identical for all copy control entries. So,</p><p>values are only shown once for target settlement document type 0C91 and source</p><p>settlement document type 0C21.</p><p>122</p><p>123</p><p>2.3.22. Specify Settlement Settings for Condition Contract</p><p>Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Specify Settlement Settings for Condition Contract Types</p><p>2. On the Display View “Condition Contract Types”: Overview screen, double-click an entry</p><p>and check the settlement settings for the following condition contract types as shown below.</p><p>Condition Contract Type Description</p><p>0CS1 Commission External: Billing Document</p><p>0CS2 Commission External: Billing Doc, 2Step</p><p>0CS3 Commission External: Billing Doc Paid</p><p>0CS4 Commission External: Bill Doc Paid,2Step</p><p>The basic condition contract type for the settlement settlement scenario is 0CS1 Commission</p><p>External: Billing Document. So, parameters are explained for this condition contract type in</p><p>detail. For the three other condition contract types, only the diffferences are explained.</p><p>124</p><p>Condition contract type 0CS1 Commission External: Billing Document</p><p>125</p><p>Explanation: The condition contract settlement type is 1 Supplier Contract Settlement –</p><p>meaning that you perform a supplier-sided settlement.</p><p>In the Business Volume group box, 0CS1 Commission External: Billing Document is specified</p><p>for the profile for business volume determination (see chapter Define and Configure Profiles for</p><p>Business Volume Determination) and 0C01 Commission Settlement - Extrenal for the set of</p><p>field combinations. Value 1 Error if no Entry Exists for the Check Entries for the BV Selection</p><p>Criteria parameter means that the user has to specify business volume selection criteria when</p><p>maintaining a condition contract. Eligible partners do not play a role for the business volume</p><p>determination.</p><p>In the Settlement Dates group box, you can see that partial settlement is supported with type 1</p><p>Cumulative as well as delta settlements with a maximum of 3 settlement runs.</p><p>Because of value 1 for the condition contract settlement type, the Settlement Type Supplier</p><p>parameter is relevant in the Settlement group box and you can see that as default the supplier-</p><p>sided settlement is performed As Account Payables. Technically, you can change the</p><p>settlement type when creating a new condition contract, but this settlement type is not</p><p>configured (as not suitable from a business perspective). Because of the specified supplier</p><p>126</p><p>contract settlement, settlement process types and settlement document types (see chapter</p><p>Define Settlement Process Types and Define Settlement Document Types) are specified in the</p><p>Supplier Settlement group box. As settlement using the A/P account of the supplier is relevant</p><p>entries are made for the ...(Accounts Payable) entry fields</p><p>Condition type RCS2 Commission PartSetRe specified for the Condition Type Reverse Partial</p><p>Settlemnt parameter is used in the A10012 pricing procedure to adopt the amount of previous</p><p>(cumulative) partial settlements which the system determines in a settlement run (compare</p><p>chapter Define Pricing Procedures).</p><p>You can see that a detailed statement is saved with a settlement run (see chapter Define and</p><p>Configure Profiles for Business Volume Determination, BUSVOL_1 is set in the Fieldname in</p><p>Detailed Statement column for the NETWR amount field line). You can also see that manual</p><p>settlement documents are allowed and that text transfer group 1 Commissions is specified.</p><p>In the Accruals group box, you can see several parameters for the accruals processing as, for</p><p>example, 0C01 Commission Settlement for the Condition Type Group for Accruals parameter</p><p>(see chapter Define and Configure Condition Type Groups for Accruals). You can also see</p><p>condition type RCA5 Commission AccrSettl in the Condition Type Accruals from Settlement field.</p><p>With this entry, you identify the condition type which shall adopt the amount of the excessive</p><p>accruals amount, determined during a settlement run, that shall be written back to the accruals</p><p>index table WCOCOF. This condition type is included in pricing procedures A10012 (compare</p><p>chapter Define Pricing Procedures). The Transfer Group Accruals Bill Doc -Item parameter has</p><p>value 0C01 Commission Settlement.</p><p>In the Delta Accruals sub group box, you can see that the delta accruals processing is active.</p><p>The condition type RCA1 specified in the Condition Type for Delta Accruals field is identical to</p><p>the condition type for which you maintain records in the condition contract (see chapters Assign</p><p>Condition Types to Condition Type Groups and Define Condition Contract Types). Value 2</p><p>Partial and Final Settlement with Delta Accruals Allowed for the Multiple Settlements on the</p><p>Same Date parameter means that you can perform a delta accruals settlement run and a partial</p><p>or final settlement run on the same day.</p><p>In the Contract Extension group box, you can see that condition contract extension is supported</p><p>whereas AJ Annual arrangement is the default value for the extension calendar.</p><p>127</p><p>Condition contract type 0CS2 Commission External: Billing Doc, 2Step</p><p>Explanation: This condition contract type is related to the two step settlement.</p><p>The only difference compared with 0CS1 concerns the settings for normal (partial, final)</p><p>settlement in the Supplier Settlement group box. The specified settlement process type 0C20</p><p>Commission Settlement - Two Step and settlement document type 0C21 Commission Invoice</p><p>Parked make sure that parked settlement documents are created which are then combined in a</p><p>collective settlement document (see chapters Define Settlement Process Types and Define</p><p>Settlement Document Types).</p><p>Condition contract type 0CS3 Commission External: Billing Doc Paid</p><p>Explanation: This condition contract type is related to the business volume determination from</p><p>paid billing documents.</p><p>The only difference compared with 0CS1 concerns the profile for business volume</p><p>determination. You can see that 0CS2 Commission External: Billing Doc Paid is specified (see</p><p>also chapter Define and Configure Profiles for Business Volume Determination).</p><p>Condition contract type 0CS4 Commission External: Bill Doc Paid,2Step</p><p>Explanation: This condition contract type combines the differences of 0CS2 and 0CS3.</p><p>The profile for business volume determination is 0CS2 Commission External: Billing Doc Paid.</p><p>In the Supplier Settlement group box, the specified settlement process type is 0C20</p><p>Commission Settlement - Two Step, and settlement document type is 0C21 Commission</p><p>Parked.</p><p>128</p><p>3. On the Change View “Condition Contract Types”: Overview screen, select each condition</p><p>contract type and choose Settlement Settings in the Dialog Structure frame to check the</p><p>following settings shown only once for 0CS1.</p><p>129</p><p>2.4 Other Configuration Settings</p><p>2.4.1. Define Access Sequence for Account Determination</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Account Determination → Revenue Account Determination</p><p>(SD) → Define Access Sequences</p><p>And Account Determination</p><p>Types</p><p>2. On the following Select Activity: dialog box, choose Define Access Sequences for Revenue</p><p>Account Determination.</p><p>3. Check access sequence KORC Commission Settlemnt and corresponding accesses with</p><p>access fields as shown below.</p><p>130</p><p>2.4.2. Define Account Determination Type</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Account Determination → Revenue Account Determination</p><p>(SD) → Define Access Sequences And Account Determination</p><p>Types</p><p>2. On the following Select Activity: dialog box, choose Define Account Determination Types.</p><p>3. Check account determination type KORC Commission Settlemnt with the assigned access</p><p>sequence KORC Commission Settlemnt as shown below.</p><p>2.4.3. Define and Assign Account Determination Procedures</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Account Determination → Revenue Account Determination</p><p>(SD) → Define And Assign Account Determination Procedures</p><p>2. On the following Select Activity: dialog box, choose Define account determination</p><p>procedure.</p><p>3. Check account determination procedure KOFRC0 Commission Settlement as shown below.</p><p>131</p><p>2.4.4. Assign G/L Accounts</p><p>Note: In the standard configuration, you cannot deliver an account assignment as the usage of</p><p>accounts is a customer individual setting. However, as this is an important piece of the overall</p><p>configuration, we show how you would create a G/L account assignment.</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Account Determination → Revenue Account Determination</p><p>(SD) → Assign G/L Accounts</p><p>2. On the following Assign G/L Accounts screen, double-click the line for table 015 Company</p><p>Code / Condition Contract Type.</p><p>3. Choose function New Entries and create an entry as indicated below.</p><p>132</p><p>2.4.5. Define Output Types</p><p>No settings were made here as we assume that no message is created for external sales</p><p>agents.</p><p>2.4.6. Define Output Determination Procedures</p><p>No settings were made here as we assume that no message is created for external sales</p><p>agents.</p><p>2.4.7. Assign Output Channels</p><p>1. Access the Customizing activity:</p><p>Customizing activity Cross-Application Components → Output Control → Assign</p><p>Output Channels</p><p>2. Check the following entries as shown below.</p><p>2.4.8. Assign Form Templates</p><p>1. Access the Customizing activity:</p><p>Customizing activity Cross-Application Components → Output Control → Assign</p><p>Form Templates</p><p>2. Check the following entries as shown below (not shown columns have initial value for</p><p>parameter).</p><p>133</p><p>2.4.9. Activation of Scope-Dependent Application Job Catalog</p><p>Entries (S/4HANA)</p><p>1. Access the Customizing activity:</p><p>Customizing activity ABAP Platform → Application Server → System Administration</p><p>→ Activation of Scope-Dependent Application Job Catalog</p><p>Entries (S/4HANA)</p><p>2. Check the following entries.</p><p>84</p><p>2.3.13. Define Posting Rules ........................................................................................ 85</p><p>2.3.14. Define Field Change Groups for Cancellation Documents................................. 86</p><p>2.3.15. Define Settlement Document Types ................................................................. 87</p><p>2.3.16. Assign Transfer Groups to Settlement Document Types ................................. 105</p><p>2.3.17. Define Field Status Groups ............................................................................ 109</p><p>2.3.18. Define Column Sorting Groups ....................................................................... 110</p><p>2.3.19. Define Settlement Process Types ................................................................... 113</p><p>2.3.20. Allowed Combinations Settlement Process Type / Settlement Document Type</p><p>121</p><p>2.3.21. Specify Copy Control...................................................................................... 121</p><p>2.3.22. Specify Settlement Settings for Condition Contract Types............................... 123</p><p>2.4 Other Configuration Settings ................................................................... 129</p><p>2.4.1. Define Access Sequence for Account Determination ...................................... 129</p><p>2.4.2. Define Account Determination Type ............................................................... 130</p><p>2.4.3. Define and Assign Account Determination Procedures ................................... 130</p><p>2.4.4. Assign G/L Accounts ...................................................................................... 131</p><p>2.4.5. Define Output Types ...................................................................................... 132</p><p>2.4.6. Define Output Determination Procedures ....................................................... 132</p><p>2.4.7. Assign Output Channels ................................................................................. 132</p><p>2.4.8. Assign Form Templates ................................................................................. 132</p><p>2.4.9. Activation of Scope-Dependent Application Job Catalog Entries (S/4HANA) ... 133</p><p>6</p><p>1. Purpose</p><p>This configuration guide describes the basic settings for sales commission settlement scenarios</p><p>delivered as of the standard configuration. The guide will help you to set up your own</p><p>configuration by providing information about all necessary steps and associations between</p><p>Customizing activities.</p><p>Note: Some settings described in this document, for example for pricing and taxation, are</p><p>specific for Germany. For other countries, these settings have to be adapted according to local</p><p>requirements.</p><p>In principle, the sales commission scenarios described here belong to purchasing rebate</p><p>processing as the external sales agent is regarded as someone who grants (‘sells’) a service to</p><p>arrange certain sales transactions. Accordingly, the business partner in the condition contract is</p><p>a supplier. However, the relevant business volume is derived from sales data, SD invoices in</p><p>the scenarios described in this document. Accordingly, some configuration settings from</p><p>purchasing rebate processing and sales rebate processing have been reused for sales</p><p>commissions settlement. You will see that sometimes new configuration objects have been</p><p>created with identical parameters. This has two reasons which are also related. First, we wanted</p><p>to have an own ‘namespace’ for the sales commissions settlement scenarios to be prepared for</p><p>potential future enhancements independent from other scenarios. Second, the standard</p><p>configuration settings for an S/4HANA on premise system shall be as much as possible identical</p><p>to S/4HANA Cloud settings. And in the Cloud, you have to follow the rule that it must be</p><p>possible to activate scope items independent from each other. This also requires to use</p><p>separate configuration settings for the different scenarios or scope items.</p><p>Note: For more information about Purchasing Rebate Processing, see document</p><p>CCM_Purchasing_Rebates_Standard_Configuration_1909 delivered with KBA (Knowledge</p><p>Based Article) note 2535889. Purchasing Rebate Processing is a specific scenario within the</p><p>Condition Contract Management (CCM) application. A more generic description of the CCM</p><p>configuration including basic configuration principles is provided with specific configuration</p><p>guide documents delivered with KBA note 2481672.</p><p>2. Configuration</p><p>The configuration of Condition Contract Management comprises three main steps:</p><p>1. Configure Pricing Including Condition Contract Conditions</p><p>In this step, you define pricing conditions that are relevant for the calculation of the</p><p>settlement amount during the condition contract settlement.</p><p>In particular, you make specific settings for the so-called condition contract conditions</p><p>which you enter in the condition contract maintenance in the Conditions screen area.</p><p>Contract conditions usually comprise the commission and accrual conditions.</p><p>2. Configure Condition Contract Maintenance</p><p>7</p><p>In this step, you first define and configure parameters for condition contract types and</p><p>then the condition contract types themselves.</p><p>3. Configure Condition Contract Settlement</p><p>In this step, you first define and configure parameters for condition contract settlement.</p><p>Then you enhance existing condition contract types with these parameters.</p><p>2.1 Configure Pricing Including Condition Contract</p><p>Conditions</p><p>The configuration of pricing in Condition Contract Management for royalties settlement</p><p>processing comprises two areas:</p><p>• Configure settings for pricing used in settlement documents as part of condition contract</p><p>settlement</p><p>• Configure specific settings for condition contract conditions</p><p>Note: The configuration of pricing for condition contract management and the configuration for</p><p>settlement documents as part of the condition contract settlement (see chapter Specify</p><p>Extended Scope of Settlement Management to chapter Allowed Combinations Settlement</p><p>Process Type / Settlement Document Type) overlap thematically, as the pricing procedures</p><p>described here (together with related configuration settings) are used within the settlement</p><p>documents to calculate royalties amounts as well as accrual amounts and to reverse accruals.</p><p>The account key described in chapter Define Account Keys is as well related to settlement</p><p>documents as it controls the posting of pricing data to Financials. However, as it is a parameter</p><p>used in pricing procedures we describe it already in this main chapter.</p><p>2.1.1. Condition Tables</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Sales (SD) → Define Condition Tables → Display</p><p>Condition Tables</p><p>2. Check the following condition tables.</p><p>Condition Table Description</p><p>4AB Condition Contract</p><p>163 Condition Contract / Material</p><p>8</p><p>4AM Condition Contract / Product Hierarchy 1 / PH2 / PH3</p><p>4AN Condition Contract / Material Group 1 / MG2 / MG3 / MG4 /MG5</p><p>4AO Condition Contract / Customer</p><p>The condition tables specifically defined for Condition Contract Management contain the</p><p>condition contract number as key field. The corresponding short description in the configuration</p><p>screen is Condition Contract, the technical field name is COCO_NUM. This is shown here for</p><p>condition table 4AB Condition Contract.</p><p>2.1.2. Access Sequences</p><p>Two additional access sequences have been configured.</p><p>For more details concerning access sequences in rebate scenarios, see documents</p><p>CCM_Sales_Rebates_Standard_Configuration and</p><p>CCM_Purchasing_Rebates_Standard_Configuration_1809.</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Sales (SD) → Define Access Sequences →</p><p>Change Access</p><p>Sequences</p><p>2. Control the following access sequences.</p><p>Access Sequence Description</p><p>RC01 Commision Settlement</p><p>RCA1 Commision Settlement Accruals</p><p>9</p><p>Access sequence RC01 Commission Settlement has the following accesses and access fields.</p><p>Access sequence RCA1 Commission Settlement Accruals has the same accesses like RC01</p><p>Royalties Settlement. However, access 20 has the requirement 67 CCS: AccrMultVal. This</p><p>formula effects that the "exclusive" flag works on level condition type / condition contract and not</p><p>only on condition type level.</p><p>10</p><p>2.1.3. Condition Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Sales (SD) → Define Condition Types → Set</p><p>Condition Types for Pricing</p><p>2. Check the following condition types.</p><p>Condition Type Description</p><p>MWAS Output Tax</p><p>MWVS Input Tax</p><p>MWVN Non-deduct.Input Tax</p><p>MWVZ Non-deduct.Input Tax</p><p>NLXA Acquisition Tax Cred</p><p>NLXV Acquisition Tax Deb.</p><p>RCA1 Commission Accruals</p><p>RCA2 Commission AccrRev</p><p>RCA5 Commission AccrSettl</p><p>RCA6 Commission Accruals</p><p>RCA8 Commission AccrRevN</p><p>RCAT Commission TotalAccr</p><p>RCBD Commission BusV Delta</p><p>RCBT Commission Total Vol</p><p>RCBV Commission BusVol</p><p>RCD1 Commission Accruals</p><p>RCD2 Commission AccrTotal</p><p>RCD5 Cost Recogn. Adjust</p><p>RCD6 Commission Accruals</p><p>RCJ1 Commission Adjustmnt</p><p>RCNE Commission NetExtSet</p><p>RCNT Commission NetAmount</p><p>RCS1 Commission</p><p>RCS2 Commission PartSetRe</p><p>RCS6 Commission</p><p>RCTT Commission TaxTriggr</p><p>11</p><p>RCTX Commission Tax</p><p>RCU1 Commission Unlikelihd</p><p>RCV1 Commission Verified</p><p>Explanation: RCS1 Commission and RCA1 Commission Accruals are the condition types for</p><p>which you maintain data records in the condition contract maintenance separately (see chapters</p><p>Specify CC-Relevance for Condition Types, Define Condition Type Groups and Assign</p><p>Condition Types to Condition Type Groups). Condition type RCS6 Commission is the</p><p>commission condition type that you also maintain in a condition contract together with accruals</p><p>in the same condition record.</p><p>To adjust the commission settlement, you can additionally maintain RCBD Commission BusV</p><p>Delta, RCJ1 Commission Adjustmnt, RCV1 Commission Verified in the condition contract.</p><p>All other condition types are (only) used in the pricing procedures for the settlement documents</p><p>– see chapter Define Pricing Procedures.</p><p>Characteristic for this scenario is that the commission calculation happens within an SD pricing</p><p>procedure because the business volume is determined from SD billing documents. However,</p><p>because the business partner of the condition contract is a supplier you have to calculate an</p><p>input tax. Tax determination is based on a tax trigger condition type with reference to a condition</p><p>type from application M Purchasing, and the result is filled in a line for input tax condition types</p><p>(see chapter Define Pricing Procedures for more details). Accordingly, input tax condition types</p><p>have to be defined for application V Sales/Distribution similar to the condition types in the tax</p><p>calculation schema in application TX Taxes.</p><p>Condition types MWAS Output Tax and MWVS Input Tax have already been delivered as of the</p><p>standard configuration in former releases. The newly configured condition types MWVN Non-</p><p>deduct.Input Tax, MWVZ Non-deduct.Input Tax, NLXA Acquisition Tax Cred, and NLXV</p><p>Acquisition Tax Deb. are also valid for other CCM scenarios with an SD pricing procedure but</p><p>input tax calculation.</p><p>12</p><p>Condition type RCS1 Commission</p><p>Explanation RCS1: You use this condition type in a condition contract with a supplier as</p><p>business partner to maintain commissions conditions for external sales commissions. This</p><p>condition type uses the delivered access sequence RC01 Commission Settlement.</p><p>13</p><p>Condition type RCJ1 Commission Adjustment (not shown parameters have an initial value) and</p><p>RCV1 Commission Verified (same parameter values, not shown as screenshot)</p><p>Explanation RCJ1 / RCV1: You use these condition types in a condition contract to maintain</p><p>settlement conditions allowing to adjust the commissions amount. These condition types use the</p><p>delivered access sequence RC01 Commission Settlement similar to condition type RCS1.</p><p>14</p><p>Condition type RCA1 Commission Accruals (not shown parameters have an initial value)</p><p>Explanation RCA1: You use this condition type in a condition contract to maintain accruals</p><p>conditions in the sales commission scenarios. Therefore, note that the Accruals checkbox is</p><p>selected in the Control Data 2 group box. This condition type uses the delivered access</p><p>sequence RCA1 Commission Settlement Accruals.</p><p>15</p><p>Condition type RCBV Commission BusVolume (not shown parameters have an initial value)</p><p>Explanation RCBV: You use this condition type in a settlement run for the business volume, see</p><p>pricing procedures A10012 and A10014 in chapter Define Pricing Procedures. It's a manual</p><p>condition type without access sequence because the condition amount – accordingly, the</p><p>calculation type is B Fixed Amount – is determined by the settlement program.</p><p>To control the transfer to the pricing procedures in the settlement run, you specify this condition</p><p>type in the Amount Fields view of a profile for business volume determination (see chapter</p><p>Define and Configure Profiles for Business Volume Determination).</p><p>16</p><p>Condition type RCBD Commission BV Delta (not shown parameters have an initial value)</p><p>Explanation RCBD: You use this condition type in a condition contract to correct the business</p><p>volume. This condition type uses the delivered access sequence RC01 Commission Settlement</p><p>similar to condition type RCS1.</p><p>17</p><p>Condition type RCS2 Commission PartSetRe (not shown parameters have an initial value)</p><p>Explanation RCS2: You use this condition type in a settlement run for the total amount of</p><p>previous partial settlements, see pricing procedures A10012 and A10014 in chapter Define</p><p>Pricing Procedures. It's a manual condition type without access sequence because the</p><p>condition amount – accordingly, the calculation type is B Fixed Amount – is determined by the</p><p>settlement program. To control the transfer to the pricing procedures in the settlement run, you</p><p>specify this condition type in a condition contract type (see chapter Specify Settlement Settings</p><p>for Condition Contract Types).</p><p>18</p><p>Condition type RCA2 Commission AccrRev (not shown parameters have an initial value)</p><p>Explanation RCA2: You use this condition type in a settlement run for the amount of the accruals</p><p>reversal, see pricing procedures A10012 in chapter Define Pricing Procedures. Therefore, note</p><p>the selected Accruals checkbox in the Control Data 2 group box. It's a manual condition type</p><p>without access sequence because the condition amount – accordingly, the calculation type is B</p><p>Fixed Amount – is determined by the settlement program. To control the transfer to the pricing</p><p>procedures in the settlement run, you specify this condition type in the condition type group for</p><p>accruals (see chapter Define and Configure Condition Type Groups for Accruals).</p><p>19</p><p>Condition type RCA5 Commission AccrSettl (not shown parameters have an initial value)</p><p>Explanation RCA5: You use this condition type in a settlement run for the amount of the accruals</p><p>index update, see pricing procedures A10012 and A10013 in chapter Define Pricing</p><p>Procedures. All parameter values are identical with values for RCA2. So, note the selected</p><p>Accruals checkbox in the Control Data 2 group box. It’s a manual condition type without access</p><p>sequence because the condition amount is determined by the settlement program. To control</p><p>the transfer to the pricing procedures in the settlement run, you specify this condition type in a</p><p>condition contract type (see chapter</p><p>Specify Settlement Settings for Condition Contract Types).</p><p>20</p><p>Condition type RCD1 Commission Accruals (not shown parameters have an initial value)</p><p>Explanation RCD1: You use this condition type in a settlement run to determine the accruals</p><p>amount for delta accruals, see pricing procedure A10013 in chapter Define Pricing Procedures.</p><p>It is not an accruals condition type itself – the Accruals checkbox in the Control Data 2 group</p><p>box is not selected – but it uses the accruals condition type RCA1 as reference, see</p><p>corresponding entries in the Master Data group box. Such a condition type is required in the</p><p>pricing procedure as accruals conditions are not considered in the net amount determination.</p><p>The net amount is used for the accruals update.</p><p>21</p><p>Condition type RCD2 Commission AccrTotal (not shown parameters have an initial value)</p><p>Explanation RCD2: You use this condition type in a delta accruals settlement run for the total</p><p>amount of accruals to be reversed, see pricing procedure A10013 in chapter Define Pricing</p><p>Procedures. It’s a manual condition type without access sequence because the condition</p><p>amount is determined by the settlement program. To control the transfer to the pricing</p><p>procedures in the settlement run, you specify this condition type in the condition type group for</p><p>accruals (see chapter Define and Configure Condition Type Groups for Accruals).</p><p>As an alternative to condition type triple RCS1, RCA1, and RCD1, you can also use the triple</p><p>RCS6, RCA6, and RCD6.</p><p>Condition type RCS6 Commission has the same parameter values as RCS1. You use this</p><p>condition type in a condition contract for usual commissions scenarios to maintain commission</p><p>conditions and corresponding accruals in one condition record.</p><p>22</p><p>Condition type RCA6 Commission Accruals</p><p>Explanation RCA6: You use this condition type in the pricing procedure of transactional</p><p>documents (billing documents) to control the accruals posting for commission condition RCS6.</p><p>Therefore, note that the Accruals checkbox is selected in the Control Data 2 group box and that</p><p>RCS6 is maintained as reference condition type. This condition type uses the delivered access</p><p>sequence RCA1 Commission Settlement Accruals. See also chapter Specify CC-Relevance for</p><p>Condition Types to check the special settings for the Usage parameter for condition types RCS6</p><p>and RCA6.</p><p>23</p><p>Condition type RCD6 Commission Accruals (not shown parameters have an initial value)</p><p>Explanation RCD6: You use this condition type in a settlement run to determine the accruals</p><p>amount for delta accruals, see pricing procedure A10013 in chapter Define Pricing Procedures.</p><p>It is not an accruals condition type itself - the Accruals checkbox in the Control Data 2 group box</p><p>is not selected – but it uses the accruals condition type RCS6 as reference – see corresponding</p><p>entries in the Master Data group box. Such a condition type is required in the pricing procedure</p><p>as accruals conditions are not considered in the net amount determination. The net amount is</p><p>used for the accruals update.</p><p>24</p><p>Condition type RCD5 Cost Recogn. Adjust (not shown parameters have an initial value)</p><p>Explanation RCD5: You use this condition type in a settlement run for delta accruals to perform</p><p>the cost recognition adjustment to different fiscal periods of a one-time commission payment (as</p><p>for instance an advanced payment) at the beginning of the condition contract validity.</p><p>25</p><p>Condition type RCTX Commission Tax (not shown parameters have an initial value)</p><p>Explanation RCTX: You can use this condition type in a settlement run for the tax condition,</p><p>currently it’s not used in the configured commission scenarios. This condition type uses the</p><p>delivered access sequence RET3 Rebate Inbound Tax.</p><p>26</p><p>Condition type RCNT Commission NetAmount (not shown parameters have an initial value)</p><p>Explanation RCNT: You use this condition type for the commission net amount in manually</p><p>created settlement documents, see pricing procedure A10014 in chapter Define Pricing</p><p>Procedures.</p><p>27</p><p>Condition type RCTT Commission TaxTriggr (not shown parameters have an initial value)</p><p>Explanation RCTT: You use this condition type in a settlement run to determine the tax condition</p><p>from condition records, see pricing procedures A10012 and A10014 in chapter Define Pricing</p><p>Procedures and explanations in this chapter. This condition type uses the delivered access</p><p>sequence RET3 Rebate Inbound Tax.</p><p>28</p><p>Condition type RCU1 Commission Unlikelihd (not shown parameters have an initial value)</p><p>Explanation RCU1: You use this condition types in a condition contract to handle the</p><p>unlikelihood for a commission payment. This condition type uses the delivered access sequence</p><p>RC01 Commission Settlement.</p><p>29</p><p>Condition type MWVN Non-deduct.Input Tax (not shown parameters have an initial value; MWVZ</p><p>Non-deduct.Input Tax and NLXA Acquisition Tax Cred have same parameter values and are</p><p>therefore not shown as screenshot, also MWAS Output Tax and MWVS Input Tax have same</p><p>parameters)</p><p>Explanation MWVN (MWAS, MWVS, MWVZ, NLXA): You use this condition type to adopt the result of</p><p>the tax determination triggered by RCTT or AS01 (see chapter Define Pricing Procedures).</p><p>30</p><p>Condition type NLXV Acquisition Tax Deb. (not shown parameters have an initial value)</p><p>Explanation NLXV: You use this condition type to adopt the result of the tax determination</p><p>triggered by RCTT or AS01 (see chapter Define Pricing Procedures).</p><p>31</p><p>Condition type RCAT Commission TotalAccr (not shown parameters have an initial value)</p><p>Explanation RCAT: You use this condition type in the pricing procedure A10014 for the manual</p><p>settlement document to adopt the remaining total accruals amount determined in the accruals</p><p>distribution function, see chapter Define Pricing Procedures.</p><p>32</p><p>2.1.4. Specify CC-Relevance for Condition Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract</p><p>Conditions → Sales → Specify CC-Relevance and Copy Control</p><p>for Condition Types</p><p>2. Check the Relevant for Condition Contract Determination in Pricing checkbox and the</p><p>Usage parameter for the following condition types.</p><p>Explanation: The Relevant for Condition Contract Determination in Pricing checkbox controls</p><p>that a condition type is relevant for the determination of applicable condition contracts during pricing</p><p>for a transactional document.</p><p>2.1.5. Define Condition Type Groups</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract</p><p>Conditions → Sales → Define Condition Type Groups</p><p>33</p><p>2. Check the condition type group 0C01 Commission Settlemnt.</p><p>Explanation: You assign a condition type group to a condition contract type (see chapter Define</p><p>Condition Contract Types).</p><p>Condition type group 0C01 Commission Settlemnt is assigned to condition contract types 0CS1</p><p>Commission Settlement to 0CS4 Commission External: Bill Doc Paid,2Step used for</p><p>commission settlement.</p><p>2.1.6. Assign Condition Types to Condition Type Groups</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Conditions</p><p>→ Sales → Assign Condition Types to Condition Type Groups</p><p>2. Check the entries for condition type group 0C01 Commission Settlement. Note value A</p><p>Condition Contract Number Must Appear in Access Sequence is selected in column Usage</p><p>of Condition Contract Number for Condition Type.</p><p>3. Select this entry and choose Condition Types for Group in the Dialog Structure frame.</p><p>Check the assigned condition types as shown below.</p><p>34</p><p>Explanation: Condition type group 0C01 contains condition type RCS1 Commission for</p><p>maintaining a commission condition in the condition contract and the corresponding condition</p><p>type RCA1 Commission Accruals for maintaining accruals conditions. It also contains the</p><p>commission condition type RCS1 Commission for which you maintain accruals in the same</p><p>condition record.</p><p>Additionally, condition types RCBD Commission BV Delta, RCJ1 Commission Adjustmnt, and</p><p>RCV1 Commission Verified are assigned which are used to adjust settlement data after</p><p>negotiations with the business partner of the condition contract.</p><p>In condition type group 0C01, you use three maintenance levels – Condition Contract, Condition</p><p>Contract / Material, and Condition Contract / Material Group 1 /MG2 / MG3 / MG4 /MG5 – for</p><p>the mentioned condition types in the condition contract. The maintenance levels correspond</p><p>with the accesses (to condition tables 4AB and 163, respectively) of the access sequence RC01</p><p>(RCA1) assigned to condition type RCS1 (RCA1).</p><p>You also assign condition type RCU1 for the likelihood of commission payments. For the</p><p>condition type only maintenance level Condition Contract is destined as the unlikelihood</p><p>decision is made for the whole condition contract.</p><p>2.1.7. Define Account Keys</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Account Determination → Revenue Account Determination</p><p>(SD) → Define Account Keys for Revenue Account</p><p>Determination</p><p>2. Check account key 0C1 Commission Settlemnt as shown below.</p><p>35</p><p>Explanation: The account key 0C1 Commission Settlemnt is used in the pricing procedures to</p><p>control the account determination for commission and accrual condition types.</p><p>2.1.8. Define Pricing Procedures</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Sales (SD) → Define Pricing Procedure</p><p>2. Check the pricing procedures A10012 Commission (Germany), A10013 Commission</p><p>DeltaAccr. (Germany), A10014 Commission Manual (Germany), and A10017 Commission</p><p>ManDAccr (Germany) as shown below.</p><p>3. Select an entry and choose Control data in the the Dialog Structure frame. Check the steps</p><p>in the pricing procedure as shown below.</p><p>36</p><p>Pricing procedure A10012 Commission (Germany)</p><p>Explanation: The calculation logic for pricing procedure A10012 is the following:</p><p>Step 100, condition type RCBV Commission BusVol</p><p>Contains the business volume amount that the system transfers to the pricing procedure in the</p><p>settlement run. Accordingly, the Manual checkbox is selected for this condition. In addition, the</p><p>Statistics checkbox is selected as you do not want the business volume amount to be</p><p>considered for the net amount. The business volume amount is stored in subtotal 7. Print ID is A</p><p>Total: General</p><p>Step 105, condition type RCBD Commission BV Delta</p><p>In this step, the system determines the condition record with a fixed amount that you have</p><p>maintained for condition type RCBD Commission BV Delta in the condition contract to adjust the</p><p>business volume amount. The condition record is determined with access sequence RC01.</p><p>Therefore, the Manual checkbox is not selected.</p><p>Step 200, condition type RCS1 Commission</p><p>The condition basis for the commission amount calculation is line 100 and line 105 (see From</p><p>Step and To Step column). Base formula 214 in column Alt.Cond.Base Value is required to</p><p>adjust the sign of the condition value if you handle a delta accrual related settlement document</p><p>and to set right value for fixed value conditions types if the condition basis is negative. The</p><p>account for the FI posting is determined using account key 0C1 (see column Account Key). The</p><p>calculated value is stored in subtotal 1. Print ID is A Total: General</p><p>Step 201, condition type RCS6 Commission</p><p>RCS6 is the alternative commission condition type to RCS1. So, explanation for condition type</p><p>RCS1 is valid here as well.</p><p>Step 204, condition type RCJ1 Commission Adjustmnt</p><p>37</p><p>In this step, the system determines the condition record with a fixed amount that you have</p><p>maintained for condition type RCJ1 Commission Adjustment in the condition contract. You use</p><p>this condition type to adjust the commission amount calculated with condition type RCS1 in line</p><p>200.</p><p>Step 205, condition type RCV1 Commission Verified</p><p>In this step, the system determines the condition record with a fixed amount that you have</p><p>maintained for condition type RCV1 Commission Verified in the condition contract. You use this</p><p>condition type to invalidates the previous commission calculation. This invalidation is based on</p><p>an exclusion rule - see chapter Condition Exclusion For Groups Of Conditions.</p><p>Step 300, condition type RCS2 Commission PartSetRe</p><p>Contains the total amount of previous partial settlements. The system determines this amount in</p><p>the settlement run and transfers it to the pricing procedure. Accordingly, the Manual checkbox is</p><p>selected for this condition. The account for the FI posting is determined using account key 0C1</p><p>(see column Account Key). The total amount of previous partial settlements is stored in subtotal</p><p>3. Print ID is A Total: General</p><p>Step 340, condition type RCA8 Commission AccrRevN</p><p>Contains the total amount of previous accruals postings.</p><p>Step 399, Net Amount</p><p>Contains the net commission amount which is the actual calculated commission amount minus</p><p>the amount of previously settled commission. The print ID is A Total: General</p><p>Step 400, tax condition type RCTT Commission TaxTriggr</p><p>Because of the condition class G Tax Classification, the condition type triggers the determination</p><p>of the tax percentage according to the settings in the tax calculation procedure - see first</p><p>screenshot below this section for the tax calculation procedure TAXD in Germany. The result of</p><p>this tax percentage determination is the used to fill the condition value(s) of the relevant line(s)</p><p>of steps 410 to 460. The condition basis for the tax calculation is the net amount of steps 200</p><p>to 300.</p><p>See the second screenshot for tax percentage determination: For tax code V1, for example, the</p><p>tax type Input Tax is relevant and the corresponding condition type of this line is MWVS so that</p><p>step 410 in the settlement pricing procedure is relevant. The data transfer only works when</p><p>relevant condition types for taxes from the tax calculation procedure are included in the pricing</p><p>procedure for condition contract settlement (in our example we do not consider tax type Travel</p><p>Expenses from the tax calculation procedure with condition type MWRK.)</p><p>Steps 410 to 460</p><p>The condition types in theses steps correspond to the condition types in the relevant tax</p><p>calculation procedure. The condition type determined by the relevant tax trigger condition type</p><p>adopts the corresponding tax percentage rate.</p><p>Note: Some tax codes can involve more than one condition type from the tax calculation</p><p>procedure.</p><p>The print ID for a tax line in steps 410 to 460 is A Total: General.</p><p>Step 499, Gross Amount</p><p>38</p><p>Contains the gross amount as sum of net amount and tax amount calculated by formula 4 Net</p><p>value + tax entered in column Alt.Calculation Type. The calculated gross amount is stored in</p><p>subtotal 9 which copies the value to KOMP-BRTWR (gross value). The print ID is A Total: General</p><p>Step 800, condition type RCA2 Commission AccrRev</p><p>Contains the amount of the accruals reversal. The system determines this amount in the</p><p>settlement run and transfers it to the pricing procedure. Accordingly, the Manual checkbox is</p><p>selected for this condition. In addition, the Statistics checkbox is selected as the amount of the</p><p>accruals reversal is not relevant for the total net amount. Account</p><p>key 0C1 (see column</p><p>Accruals) is used to determine the accruals account for the FI posting. The calculated value of</p><p>the line is stored in subtotal 2.</p><p>Step 850, condition type RCA5 Commission AccrSettl</p><p>Contains the amount of the excessive accruals amount that shall be written back to accruals</p><p>index table WCOCOF in a partial settlement. The amount is calculated by condition value formula</p><p>91 CCS: Accr. in Settl, entered in column Alt.Calculation Type, as the difference between the</p><p>absolute value of subtotal 2 and the net value. Account key 0C1 (see column Accruals) is used</p><p>to determine the accruals account for the FI posting.</p><p>Step 900, Effective Value</p><p>Contains the effective value which in fact equals the gross amount as also formula 4 is applied.</p><p>The calculated amount is stored in subtotal S (KOMP-EFFWR).</p><p>Tax calculation procedure TAXD Sales Tax - Germany</p><p>Maintenance of tax rates for the specific tax code V1 19% domestic input tax</p><p>39</p><p>Pricing procedure A10013 Commission Delta Accr (Germany)</p><p>Explanation: The calculation logic for pricing procedure A100013 is the following:</p><p>Step 100, condition type RCBV Commission BusVol</p><p>Contains the business volume amount that the system transfers to the pricing procedure in the</p><p>settlement run. Accordingly, the Manual checkbox is selected for this condition. In addition, the</p><p>Statistics checkbox is selected because the business volume amount should not be considered</p><p>in the calculation of the net amount. The business volume amount is stored in subtotal 7.</p><p>Step 105, condition type RCBD Commission BV Delta</p><p>In this step, the system determines the condition record with a fixed amount that you have</p><p>maintained for condition type RCBD Commission BV Delta in the condition contract to adjust the</p><p>business volume amount. The condition record is determined with access sequence RC01.</p><p>Therefore, the Manual checkbox is not selected.</p><p>Note:</p><p>Step 200 (condition type RCS1) and step 201 (condition type RCD1) reflect some flexibilty in</p><p>how accruals are handled during condition contract processing. This configuration has been</p><p>40</p><p>done to avoid the creation of two different pricing procedures which would lead to a duplication</p><p>of some other parameters (settlement document type, condition contract type).</p><p>If you do not want to differentiate the percentages for commissions and accruals, it is sufficient</p><p>to just maintain the commission conditions with condition type RCS1 and to also use the</p><p>condition type RCS1 for the accruals posting.</p><p>Step 201, condition type RCD1 Commission Accruals represents the usual accruals amount</p><p>determination with the accruals conditions. Here, the accrual condition type RCA1 is not used</p><p>directly. Instead a 'normal' condition type, RCD1 is used for which the accruals condition type</p><p>RCA1 is assigned as reference.</p><p>To avoid double-calculation of the accruals amount in these two steps, a condition exclusion</p><p>group containing condition types RCS1 and RCD1 has been defined and assigned to pricing</p><p>procedure A10013 (see chapter Condition Exclusion For Groups Of Conditions). Like this, only</p><p>the condition type with the higher percentage is applied.</p><p>Step 200, condition type RCS1 Commission</p><p>Represents a percentage condition which is determined using the corresponding access</p><p>sequence. The condition basis for the commission amount calculation is line 100 and line 105</p><p>(see From Step and To Step column). Base formula 214 in column Alt.Cond.Base Value is</p><p>required to adjust the sign of the condition value if you handle a delta accrual related settlement</p><p>document and to set right value for fixed value condition types if the condition basis is negativ.</p><p>The account for the FI posting is determined using account key 0C1 (see column Account Key).</p><p>The calculated value is stored in subtotal 1.</p><p>Step 201, condition type RCD1 Commission Accruals</p><p>Contains the percentage condition type RCD1 Commission Accruals which is determined using</p><p>the corresponding access sequence. The condition basis for the commission amount calculation</p><p>is line 100 and line 105 (see From Step and To Step column). Base formula 214 in column</p><p>Alt.Cond.Base Value is required to adjust the sign of the condition value if you handle a delta</p><p>accrual related settlement document and to set right value for fixed value conditions types if the</p><p>condition basis is negativ. The account for the FI posting is determined using account key 0C1</p><p>(see column Account Key). The calculated value is stored in subtotal 1.</p><p>Note: An accruals condition type is not considered for the net amount calculation in the pricing</p><p>procedure. However, this is required for the accruals amount. To enable consideration for the</p><p>net amount, a 'normal' condition type is used instead which references the actual accruals</p><p>condition type RCA1. Condition type RCD1 has the same access sequence as RCA1.</p><p>Step 202, condition type RCS6 Commission</p><p>Same explanation as for step 200 with alternative condition type.</p><p>Step 203, condition type RCD6 Commission Accruals</p><p>Same explanation as for step 201 with alternative condition type.</p><p>Step 204, condition type RCJ1 Commission Adjustment</p><p>In this step, the system determines the condition record with a fixed amount that you have</p><p>maintained for condition type RCJ1 Commission Adjustment in the condition contract. You use</p><p>this condition type to adjust the commission amount calculated with condition type RCS1 in line</p><p>200 or RCD1 in line 201.</p><p>41</p><p>Step 205, condition type RCV1 Commission Verified</p><p>In this step, the system determines the condition record with a fixed amount that you have</p><p>maintained for condition type RCV1 Commission Verified in the condition contract. You use this</p><p>condition type to invalidates the previous commission calculation. This invalidation is based on</p><p>an exclusion rule - see chapter Condition Exclusion For Groups Of Conditions.</p><p>Step 300, condition type RCS2 Commission PartSetRev</p><p>Contains the total amount of previous partial settlements. The system determines this amount in</p><p>the delta accruals settlement run and transfers it to the pricing procedure. Accordingly, the</p><p>Manual checkbox is selected for this condition type. The account for the FI posting is</p><p>determined using account key 0C1 (see column Account Key).The total amount of previous</p><p>partial settlements is stored in subtotal 3.</p><p>Step 320, condition type RCU1 Commission Unlikelihd</p><p>If the minimum business volume turnover is not reached, no accruals should be created and</p><p>existing accruals should be reversed. This is controlled by this commission unlikelihood</p><p>condition type in the following way: you maintain a condition record of 100% in the condition</p><p>contract. The sign is inversed by base formula 214 that you can see in column Alt.Cond.Base</p><p>Value. Lines 200 to 300 representing the accruals amount calculation form the condition basis</p><p>for the amount calculation.</p><p>Step 350, condition type RCD2 Commission Accr Total</p><p>Contains the total amount of already posted accruals (since the partial settlement). The system</p><p>determines this amount in the delta accruals settlement run and transfers it to the pricing</p><p>procedure. Accordingly, the Manual checkbox is selected for this condition type. The account for</p><p>the FI posting is determined using account key 0C1 (see column Account Key).The total amount</p><p>of already reversed accruals is stored in subtotal 2.</p><p>Step 399, Net Amount</p><p>Contains the net amount as calculated by condition value formula 2 Net value.</p><p>Step 499, Gross Amount</p><p>Contains the gross amount identical to the net amount as there is no tax amount (condition</p><p>value formula 4 Net value + tax adds net amount and tax amount). The gross amount is stored</p><p>in subtotal 9 which copies the value to KOMP-BRTWR (gross value).</p><p>Step 900, Effective Value</p><p>Contains the effective value which in fact equals the gross amount as also formula</p><p>4 is applied.</p><p>The calculated amount is stored in subtotal S (KOMP-EFFWR).</p><p>42</p><p>Pricing procedure A10014 Commission Manual (Germany)</p><p>Explanation: Again, to limit the number of delivered objects, this pricing procedure is used for</p><p>two contexts: the entry of a settlement document for an external document sent by a supplier,</p><p>and the ‘internal’ creation of a settlement document. Accordingly, this procedure combines two</p><p>types of tax amount determination. For an external invoice tax data are copied from the manual</p><p>entries in the settlement document, for the internal creation the tax rate is determined from</p><p>condition records. Requirements 65 LO-AB: Tax entry and 66 LO-AB: Tax determ. establish an</p><p>either(AS01)-or(RRTT) logic.</p><p>The calculation logic for pricing procedure A10014 is the following:</p><p>Step 100, condition type RCNT Commission Net Amount</p><p>The condition value for this step is filled with the net value entered in the settlement document</p><p>item. This data transfer is controlled by the condition value formula 250 in the Alt.Calculation</p><p>Type column.</p><p>Step 400, condition type AS01 Tax trigger</p><p>This pricing step is for the scenario with an external invoice. Requirement 65 LO-AB: Tax entry</p><p>checks a control parameter set by the Settlement Management program that reading conditions</p><p>is not required. Because of condition class G Tax Classification, the condition type triggers the</p><p>tax percentage determination from the tax calculation procedure (see first screenshot below)</p><p>and fills the result into the condition value into the condition value of the relevant line(s) of steps</p><p>410 to 460 (typically it’s condition type MWVS Input tax manually) – compare explanations for</p><p>pricing procedure A10009.</p><p>Steps 401, condition type RCTT Commission TaxTriggr</p><p>This pricing step is for the scenario with an ‘internal’ creation of a settlement document.</p><p>Requirement 66 LO-AB: Tax det Suppl checks a control parameter set by the Settlement</p><p>Management program that reading condition records is required. Because of condition class G</p><p>Tax Classification, the condition type triggers the tax percentage determination from the tax</p><p>calculation procedure as described for AS01.</p><p>Steps 410 to 460</p><p>The condition types in theses steps correspond to the condition types in the relevant tax</p><p>calculation procedure. The condition type determined by the relevant tax trigger condition type</p><p>adopts the corresponding tax percentage rate.</p><p>43</p><p>Note: Some tax codes can involve more than one condition type from the tax calculation</p><p>procedure.</p><p>Print ID for a tax line in steps 410 to 460 is A Total: General.</p><p>Step 499, Gross Amount</p><p>Contains the gross amount as sum of net amount and tax amount calculated by formula 4 Net</p><p>value + tax entered in column Alt.Calculation Type. The calculated gross amount is stored in</p><p>subtotal 9 which copies the value to KOMP-BRTWR (gross value). Print ID is A Total: General</p><p>Step 900, Effective Value</p><p>Contains the effective value which in fact equals the gross amount. The calculated amount is</p><p>stored in subtotal S (KOMP-EFFWR).</p><p>Step 901, condition type RCAT Commission TotalAccr</p><p>Contains the posted accruals as basis for the automatic distribution of the manually settlement</p><p>amount to business objects in accordance with the accruals posting. This line is marked as</p><p>subtotal 6 (see also Specify General Settings for Condition Contract Settlement).</p><p>Note that for this automatic distribution, you also have to select 3 Distribition based on Accruals</p><p>(CCM) for the Control for Document Item Distribution parameter of a settlement document type.</p><p>However, in the configuration delivered as of standard – settlement document type 0C31</p><p>Commission Manual – the distribution is not active.</p><p>Step 950, condition type RCA5 Commission AccrSettl</p><p>Currently, this step serves as placeholder for a future enhancement.</p><p>Pricing procedure A10017 Commission ManDAccr (Germany)</p><p>Explanation: The calculation logic for pricing procedure A10017 is the following:</p><p>Step 100, condition type RCNT Commission NetAmount</p><p>The condition value for this step is filled with the net value you entered in the settlement</p><p>document item. This data transfer is controlled by the condition value formula 251 in the</p><p>Alt.Calculation Type column.</p><p>Step 499, Gross Amount</p><p>Contains the gross amount as the sum of the net and tax amount calculated by condition value</p><p>formula 4 Net value + tax. The calculated gross amount is stored in subtotal 9 which copies the</p><p>value to KOMP-BRTWR (gross value).</p><p>Step 900, Effective Value</p><p>Contains the effective value which in fact equals the gross amount. The calculated amount is</p><p>stored in subtotal S (KOMP-EFFWR).</p><p>44</p><p>2.1.9. Condition Exclusion For Groups Of Conditions</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Sales (SD) → Condition Exclusion For Groups Of</p><p>Conditions</p><p>2. Choose activity Define Condition Exclusion Groups on the dialog screen.</p><p>3. Check exclusion groups as shown below.</p><p>Then choose Back (F3).</p><p>4. Choose activity Assign Condition Types to Exclusion Groups on the dialog screen.</p><p>5. Check assignment of condition types as shown below.</p><p>Then choose Back (F3).</p><p>6. Choose activity Maintain Condition Exclusion for Pricing Procedures on the dialog screen.</p><p>7. Select pricing procedure A10012/13 and choose Exclusion in the Dialog Structure frame.</p><p>Check definition of condition exclusion procedures for pricing procedures as shown below.</p><p>45</p><p>Explanation: The condition exclusion procedure 1 for the two pricing procedures A10012/13</p><p>controls that condition types RCS1 and RCJ1 are excluded when a condition record for RCV1</p><p>has been defined in the condition contract.</p><p>Similarly, the condition exclusion procedure 2 for pricing procedures A10013 controls that</p><p>condition types RCD1 is excluded when a condition record for RCV1 has been defined in the</p><p>condition contract.</p><p>The condition exclusion procedure 3 for pricing procedure A10010 has been configured to</p><p>enable the usage of one pricing procedure for two ways of calculating the accruals amount: a</p><p>calculation based on the 'normal' commission condition and a calculation based on the accrual</p><p>condition - see explanation in chapter Define Pricing Procedures.</p><p>Note: The exclusion group must contain the condition type RCD1 used in pricing procedure</p><p>A10013 and not condition type RCA1 for accruals (for which you maintain entries in the</p><p>condition contract) that is the reference condition type in condition type RCD1.</p><p>2.1.10. Define Document Schema Groups for Settlement</p><p>Document Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Define Document Schema Groups for Settlement</p><p>Document Types</p><p>2. Check document schema groups as shown below.</p><p>Explanation: The document schema groups are used in the pricing procedure determination as</p><p>explained in chapter Specify Pricing Procedure Determination. You assign the document</p><p>schema groups to settlement document types (see chapter Define Settlement Document Types)</p><p>so that the different pricing procedures can be used for the settlement document types fulfilling</p><p>different purposes (partial settlement, delta accruals settlement, etc.).</p><p>46</p><p>Document schema group 0C CommissionSettlement is used for the following settlement</p><p>document types and corresponding settlement document types for the document reversal and</p><p>the corresponding alternative settlement document types (not listed):</p><p>0C11 (0C13) Commission (Reversal)</p><p>0C21 (0C23) Commission Parked (Reversal)</p><p>0C51 (0C53) Commission Proforma (Reversal)</p><p>0C61 (0C63) Commission Accruals Reversal (Reversal)</p><p>0C91 (0C93) Commission Settlement Collection (Rev)</p><p>Document schema group 0D Commission DeltaAcc is used for settlement</p><p>document type 0C41</p><p>(0C43) Commission Delta Accruals (Reversal).</p><p>Document schema group 0E Commission Manual is used for settlement document type 0C31</p><p>(0C33) Commission Manual (Reversal).</p><p>Document schema group 0H Commission Man DAccr is used for settlement document type</p><p>0C4A (0C4C) Commission Manual Delta Accruals (Rev).</p><p>2.1.11. Specify Pricing Procedure Determination</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Basic Settings</p><p>→ Pricing → Specify Pricing Procedure Determination</p><p>2. Choose activity Determination for Settlement Documents and Settlement Document Lists on</p><p>the dialog screen.</p><p>3. Check the entries as shown below.</p><p>Explanation:</p><p>Pricing procedure A10012 Commission (Germany) intended for partial and final settlement is</p><p>assigned to document schema group 0X Commission Settlement.</p><p>Pricing procedure A10013 Commission DeltaAccr. (Germany) intended for delta accruals</p><p>settlement is assigned to document schema group 0Y Commission DeltaAcc.</p><p>Pricing procedure A10014 Commission Manual (Germany) intended for manual settlement</p><p>document entry is assigned to document schema group 0Z Commission Manual.</p><p>Pricing procedure A10013 Commission DeltaAccr. (Germany) intended for delta accruals</p><p>settlement in manual settlement scenarios is assigned to document schema group 0H</p><p>Commission Man DAccr.</p><p>47</p><p>2.1.12. Specify General Settings</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Settlement →</p><p>Specify General Settings</p><p>2. Check the general settings.</p><p>Explanation:</p><p>The setting for the Accruals Total in Manual Settlement parameter identifies the condition type</p><p>containing the posted accruals as basis for the automatic distribution of a manually entered</p><p>settlement amount (see also Define Pricing Procedures, pricing procedure A10014).</p><p>48</p><p>2.2 Configure Condition Contract Maintenance</p><p>The configuration of Condition Contract Maintenance comprises two steps:</p><p>• Configure parameters for condition contract types</p><p>• Define condition contract types</p><p>2.2.1. Define Number Ranges</p><p>No specific settings have been made here. Existing number range interval 01 is used as well in</p><p>the scenarios described here.</p><p>For more details, see document CCM_Purchasing_Rebates_Standard_Configuration.</p><p>2.2.2. Define Condition Contract Categories</p><p>A new condition contract category has been defined for commission scenarios.</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Maintenance →</p><p>Define Condition Contract Categories</p><p>2. Check condition contract category 0C Commission Settlement.</p><p>Explanation: You assign condition contract categories to condition contract types (see chapter</p><p>Define Condition Contract Types).</p><p>Condition contract category 0C Commission Settlement is used to bundle condition contracts for</p><p>commission, for example, in reporting.</p><p>49</p><p>2.2.3. Define and Configure Field Status Groups for Header</p><p>Fields</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Maintenance →</p><p>Define and Configure Field Status Groups for Header Fields</p><p>2. Check the field status groups with corresponding fields as shown below.</p><p>Explanation: You assign field status groups to condition contract types (see chapter Define</p><p>Condition Contract Types).</p><p>Field status group 0C01 Commission External: Billing Document is assigned to condition</p><p>contract types 0CS1 Commission Settlement, 0CS2 Commission External: Billing Doc, 2Step,</p><p>0CS3 Commission External: Billing Doc Paid and 0CS4 Commission External: Bill Doc</p><p>Paid,2Step.</p><p>Field status group 0C01 sets the purchasing-related fields (EKORG Purchasing Organization,</p><p>EKGRP Purchasing Group, BUKRS Company Code) as required entries. All sales related</p><p>organizational data are hidden so that the Sales tab page is hidden completely.</p><p>Field ACCESS_TYPE Access Type is hidden as currently only the value blank Exclusive out of</p><p>two options is supported.</p><p>50</p><p>2.2.4. Define Text Determination Procedures</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Maintenance →</p><p>Text Control → Define Text Determination Procedures</p><p>2. Check text determination procedure 0C Commission Settlement.</p><p>Explanation: You assign text determination procedures to condition contract types. Text</p><p>determination procedure 0C Commission Settlement is assigned to condition contract types</p><p>0CS1 Commission Settlement, 0CS2 Commission External: Billing Doc, 2Step, 0CS3</p><p>Commission External: Billing Doc Paid and 0CS4 Commission External: Bill Doc Paid,2Step.</p><p>Text determination procedure 0C Commission Settlement allows the user to enter texts on</p><p>header level.</p><p>2.2.5. Specify Text Types for Text Determination Procedure</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Maintenance →</p><p>Text Control → Specify Text Types for Text Determination</p><p>Procedure</p><p>2. Check the assignment of text types to text determination procedure 0C Commission</p><p>Settlement as shown below.</p><p>51</p><p>Explanation: Client-independent text IDs 0C01 Internal Text and 0C02 External Text that are</p><p>assigned to text determination procedure 0C Commission Settlement delivered as of the</p><p>standard configuration.</p><p>2.2.6. Define Check Groups</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Maintenance →</p><p>Additional Checks → Define Check Groups</p><p>2. Check the check groups 0C01 Commission Settlement as shown below.</p><p>Explanation: You assign check groups to condition contract types: 0C01 Commission</p><p>Settlement is assigned to condition contract types 0CS1 Commission Settlement, 0CS2</p><p>Commission External: Billing Doc, 2Step, 0CS3 Commission External: Billing Doc Paid and</p><p>0CS4 Commission External: Bill Doc Paid,2Step.</p><p>Currently, check group 0C01 Commission Settlement does not provide any additional checks.</p><p>However, it can be regarded as preparation for future releases to allow the definition of</p><p>customer-specific checks.</p><p>2.2.7. Specify Settings for Transfer Manager</p><p>Note: The settings for transfer event 75 Condition Contract Creation - Default Header Data are</p><p>relevant for the definition of condition contract types (see next chapter). Therefore this</p><p>Customizing activity is described now, starting with transfer event 75. However, to avoid</p><p>repeating this Customizing activity at other places in this document, the settings made for other</p><p>transfer events – mostly relevant for the settlement document types – are already described</p><p>here (in alphanumeric order).</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Settlement</p><p>Documents → Specify Settings for Transfer Manager</p><p>52</p><p>2. Choose activity Define Transfer Groups.</p><p>3. Select event 75 Condition Contract Creation - Default Header Data and choose Transfer</p><p>Groups in the Dialog Structure frame. Check transfer group 0C01 Commission Settlement</p><p>and the corresponding transfer rule as shown below.</p><p>4. Select event 18 Data Transfer - Collective Document Header and check transfer group</p><p>0C01 Commission Settlement and the corresponding transfer rules as shown below.</p><p>53</p><p>54</p><p>55</p><p>5. Select event 20 Pricing Data - Change Header (KOMK) Supplier Side and check transfer</p><p>56</p><p>group 0C01 Commission Settlement and the corresponding transfer rule as shown below.</p><p>6. Select event 22 Pricing Data - Change Item (KOMP) Supplier Side and check transfer</p><p>group 0C01 Commission Settlement and the corresponding transfer rule as shown below.</p><p>57</p><p>58</p><p>7. Select event 3H Account Determination in Sales and Distribution (SD) and check transfer</p><p>group 0CC1 Commission Settlement Collection and the corresponding transfer rule as</p><p>shown below.</p><p>59</p><p>8. Select event 63 Default Header Data - Document Reversal and check transfer group 0R</p><p>Rebate and the corresponding transfer rules shown below.</p><p>Note: This transfer group is also used in other rebate scenarios.</p><p>60</p><p>61</p><p>9. Select transfer event 6I Set Final Document Number and check transfer group 0C01</p><p>Commission Settlement and the corresponding transfer rules as shown below.</p><p>62</p><p>10. Select transfer event 78 Accounting Document - Accruals Line Billing Document and check</p><p>63</p><p>transfer group 0C01 Commission Settlement and the corresponding transfer rules as shown</p><p>below.</p><p>Explanation:</p><p>Transfer event 75 Condition Contract Creation - Default Header Data</p><p>Transfer group 0C01 Commission Settlement with transfer rule 1 sets the default value 0C01</p><p>Commission Net Amount for the amount field group when you create a new condition contract</p><p>with one of the condition contract types described here.</p><p>Transfer group 0C01 Commission Settlement is assigned to the two condition contract types</p><p>described in this document.</p><p>Transfer event 18 Data Transfer - Collective Document Header</p><p>Transfer group 0C01 Commission Settlement includes three transfer rules to copy the actual</p><p>settlement date (field KOMLFK-ACT_SETTLE_DATE), the start date of the settlement period</p><p>(field KOMLFK-SETTLE_START_DATE), and the settlement date type (field KOMLFK-</p><p>SETTLE_DATE_TYPE) from the single settlement document to the collective document.</p><p>64</p><p>Transfer event 20 Pricing Data - Change Header (KOMK) Supplier Side</p><p>Transfer group 0C01 Commission Settlement sets the fixed value 1 for field TAXK1 Tax</p><p>Classification 1 for Customer in the pricing communication structure KOMK Communication</p><p>Header for Pricing for the pricing feature in the creation process of a settlement document</p><p>(compare chapter Define Pricing Procedures).</p><p>Transfer event 22 Pricing Data - Change Item (KOMP) Supplier Side</p><p>Transfer group 0C01 Commission Settlement sets the fixed value 1 for field TAXM1 Tax</p><p>Classification Material in the pricing communication structure KOMP for the pricing feature in the</p><p>creation process of a settlement document (compare chapter Define Pricing Procedures). This</p><p>reflects that the commission is regarded as a kind of service for which the full tax can be applied</p><p>independent from the tax classification of the material.</p><p>Transfer event 63 Default Header Data - Document Reversal</p><p>Transfer group 0R Rebate for transfer event 63 Default Header Data - Document Reversal</p><p>concerns the cancellation of settlement documents. Transfer rule 1 initializes the reference</p><p>document number (KOMLFK-XBLNR) for the cancellation settlement document. Transfer rule 2</p><p>copies the creation date of the settlement document to be cancelled to the document date</p><p>(KOMLFK-BLDAT) of the cancellation settlement document.</p><p>Transfer group 0R Rebate is assigned to all settlement document types for cancellation</p><p>(exception for the settlement document type to cancel manual settlement documents) used in</p><p>the commission scenarios described in this document (see chapter Assign Transfer Groups to</p><p>Settlement Document Type).</p><p>A related configuration setting is the field change group for cancellation. The field change group</p><p>0R Rebate allows to change fields KOMLFK-XBLNR and KOMLFK-BLDAT and is also assigned to</p><p>the settlement document types (see chapter Define Field Change Groups for Cancellation</p><p>Documents and Assign Transfer Groups to Settlement Document Type).</p><p>Transfer event 6I Set Final Document Number</p><p>Transfer group 0C01 Commission Settlement for transfer event 6I Set Final Document Number</p><p>sets the reference document number also for the payment reference. This transfer group is</p><p>assigned to settlement document types for ‘normal’ settlement (see chapter Assign Transfer</p><p>Groups to Settlement Document Type).</p><p>Transfer event 78 Accounting Document - Accruals Line Billing Document</p><p>The purpose is to transfer the condition contract number to the assignment field of the journal</p><p>entry.</p><p>65</p><p>2.2.8. Define Condition Contract Types</p><p>1. Access the Customizing activity:</p><p>Customizing activity Logistics - General → Settlement Management → Condition</p><p>Contract Management → Condition Contract Maintenance →</p><p>Define Condition Contract Types</p><p>2. Check the following condition contract types as shown and explained below.</p><p>Condition Contract Type Description</p><p>0CS1 Commission External: Billing Document</p><p>0CS2 Commission External: Billing Doc, 2Step</p><p>0CS3 Commission External: Billing Doc Paid</p><p>0CS4 Commission External: Bill Doc Paid,2Step</p><p>Condition Contract Type 0CS1 Commission External: Billing Document</p><p>66</p><p>Explanation: Fundamental for a condition contract used for purchasing rebates with a certain</p><p>supplier – this is also the case for commission scenarios – is that the type of contract partner is</p><p>V Supplier and the type of eligible partner is N No Eligible Partner.</p><p>In this condition contract type, several previously defined parameters are specified: number</p><p>range 01, condition contract category 0C Commission Settlement, sales condition type group</p><p>0C01 Commission Settlement, text determination procedure 0C Commission Settlement, field</p><p>status group 0C01 Commission Settlement, check group 0C01 Commission Settlement, and</p><p>transfer group for default values in the contract header 0C01 Commission Settlement.</p><p>Value 1 Synchronous to Settlement Condition if no Scales Maintained for parameter Input</p><p>Control for Accrual Rate controls that the accrual rate is synchronized with the entered</p><p>commission rate for commission conditions with accruals such as RCS6 Commission.</p><p>You can also see that the approval process is not active and that changes on the user interface</p><p>are allowed. When a condition contract is in approval, you can only change the condition</p><p>contract status.</p><p>Tab page Post Processing Framework Actions will be hidden for corresponding condition</p><p>contracts as the Hide Tab Page for PPF Actions checkbox is selected.</p><p>The Enable Creation of Successor Contracts checkbox is selected as the creation of successor</p><p>condition contracts is included in the designed commission scenario.</p><p>As the Contract Partner is Optional checkbox and the Condition Contract Validity is Optional</p><p>checkbox is not selected, you must specify the supplier and condition contract validity when you</p><p>create a new condition contract.</p><p>Condition contract types 0CS2 Commission External: Billing Doc, 2Step, 0CS3 Commission</p><p>External: Billing Doc Paid, and 0CS4 Commission External: Bill Doc Paid,2Step have the same</p><p>parameter values.</p><p>67</p><p>2.3 Configure Condition Contract Settlement</p><p>The configuration of Condition Contract Settlement comprises five main areas.</p><p>• Business Volume Determination</p><p>• Settlement Calendar</p><p>• Creation of the Settlement Documents</p><p>• Pricing in Settlement Documents - Calculation of the Commission Amount, Taxes etc.</p><p>• Accruals Posting & Reversal (involving Pricing)</p><p>Note:</p><p>Settings for pricing in settlement documents have already been described in main chapter</p><p>Configure Pricing Including Condition Contract Conditions.</p><p>Calendar settings are included in the settlement settings for a condition contract type (chapter</p><p>Specify Settlement Settings for Condition Contract Types).</p><p>2.3.1. Assign Partner Functions to Predefined Partner Relations</p><p>1. Access the Customizing</p>