03 CCM Configuration en V1 3

Condition Contract Management Configuration Guide

CUSTOMER

Version 1.3

CUSTOMER

CONDITION CONTRACT MANAGEMENT

The purpose of this document is to explain the essential configuration steps for Condition Contract Management.

DISCLAIMER: The contents of this document, and SAP’s strategy and possible future developments, products, and/or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP’s intentional or gross negligence. All forward -looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

CUSTOMER

2


The purpose of this document is to explain the essential configuration steps for Condition Contract Management.

DISCLAIMER: The contents of this document, and SAP’s strategy and possible future developments, products, and/or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP’s intentional or gross negligence. All forward -looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

CUSTOMER

2


TABLE OF CONTENTS CONFIGURATION OVERVIEW ............................................................ ................................................................. ....... 4 Prerequisites ................................................................ ............................................................... ........................................ 4 Process .............................................................. .............................................................. ................................................... 5 Result ................................................................ ................................................................ .................................................. 5

CONFIGURE CONDITION CONTRACT CONDITIONS .............................................................. ................................................................................... ..................... 5 Prerequisites ................................................................ ............................................................... ........................................ 5 Procedure........................................................... .............................................................. ................................................... 5 Settings for Purchase-Sided and Sales-Sided Condition Contracts ....................................................... ............................. 6 Define Condition Tables ........................................................ ................................................................. ............................. 6 Define Access Sequences ..................................................................................................................... ............................. 6 Condition Contracts for Suppliers..................................................... ................................................................. .................. 6 Condition Contracts for Customer ..................................................................................................................... .................. 7 Other Conditions ................................................................................................................................................................. 8 Result ................................................................ ................................................................ .................................................. 9

CONFIGURE CONDITION CONTRACT MAINTENANCE M AINTENANCE .......................................................... ............................................................................. ................... 10 Prerequisites ..................................................................................................................................................................... 10 Procedure........................................................... .............................................................. ................................................. 10 Define and Configure Parameters for Condition Contract Types ................................................ ...................................... 11 Define and Configure Condition Contract Types ............................................................... ................................................ 13 Standard Configuration for Restrictions and Checks ........................................................ ................................................. 14 Enhancements Using Business Add-Ins ................................................................................................ ........................... 15 Result ................................................................ ................................................................ ................................................ 15

CONFIGURE CONDITION CONTRACT SETTLEMENT SETT LEMENT ............................................................................... ............................................................................... 16 Prerequisites ..................................................................................................................................................................... 16 Procedure........................................................... .............................................................. ................................................. 16 Configure Business Volume Determination ............................................................ ........................................................... 17 Prerequisites ..................................................................................................................................................................... 19 Basic Configuration with One Data Source .................................................................................................... ................... 19 Extended Configuration with Several Data Sources ......................................................... ................................................. 20 Specify Settlement Calendars .......................................................... ................................................................. ................ 23 Configure Settlement Document Creation and Settlement Amount Calculation ........................................................... ..... 23 Specify settlement document creation for the condition contract types ............................................................. ................ 24 Specify settlement amount calculation & data transfer from settlement p rogram ......................................................... ..... 25 Specify Posting and Reversal of Accruals .............................................................. ........................................................... 27 Steps for the Posting of Accruals ..................................................... ................................................................. ................ 27 Steps for the Reversal of Accruals .............................................................. ................................................................. ..... 29 Enhancements Using Business Add-Ins ................................................................................................ ........................... 32 Additional Settings for the Settlement Settlement Run ............................................................. ........................................................... 32 Result ................................................................ ................................................................ ................................................ 33

CUSTOMER

3


Condition Contract Management Configuration Overview You can use this business process to manage conditions with supplier and customers, in particular conditions requiring subsequent settlement. The solution comprises the administration of conditions in condition contracts together with agreements about the relevant business volume and the settlement of condition contract in order to create corresponding amounts receivable and payable in Financial Accounting. The following figure 1 sketches the main elements for which you have to specify the configuration:

Figure 1: Main elements for the configuration of Condition Contract Management Basically, for Condition Contract Management you have to configure settings for the condition contract processing and for the condition contract settlement. In addition, you have to configure settings for the settlement documents which the system creates in a condition contract settlement. However, as these settings are part of the overall configuration of Settlement Management, we regard them as prerequisite for Condition Contract Management. The central configuration parameter is the condition contract type. This composite parameter contains settings both for the condition contract processing and for the condition contract settlement.

Prerequisites   

Organizational Data Master Data for Business Partners such as suppliers or customers Settings for Settlement Management Documents

CUSTOMER

4


Process The configuration of Condition Contract Management comprises three main steps: 1.

Configure Condition Contract Conditions In this step, you define pricing conditions that are relevant for the calculation of the settlement amount during the condition contract settlement. In addition, you have to define other pricing conditions for the correct condition contract settlement.

2.

Configure Condition Contract Maintenance In this step, you first define and configure parameters for condition contract types and then the condition contract types themselves.

3.

Configure Condition Contract Settlement In this step, you first define and configure parameters for condition contract settlement which you then you enhance existing condition contract types with these parameters

Result You have made the required Customizing settings to manage the processes in Condition Contract Management .

Configure Condition Contract Conditions This section describes Customizing settings for the d efinition and control of pricing conditions that are relevant for the calculation of the settlement amount during the condition contract settlement in Condition Contract Management . This section comprises two parts. First, we describe settings for the so called contract conditions which you enter in the condition contract maintenance on the Conditions detail screen. Contract conditions usually comprise the rebate and accrual conditions. In addition, you have to define other pricing conditions for the correct condition contract settlement. For example, you need to define a condition type for the business volume as starting point of the settlement calculations and conditions for taxes according to country specific regulations. When you post accruals in Financial Accounting when saving source documents (GR for purchase orders, SD invoices etc.) related to condition contracts, you also have to define suitable condition types for the reversal of accruals.

Prerequisites You have defined required tax conditions. This configuration is not described here.

Procedure The configuration of contract conditions follows the usual configuration procedure for pricing as e.g. that for sales orders. The Customizing for Settlement Management contains the corresponding Customizing activities to facilitate the configuration task for this solution.

CUSTOMER

5


In the following, we first explain configuration settings for both purchase-sided and sales-sided conditions contracts and then we distinguish – although very similar - the configuration description for purchase-sided and sales-sided condition contracts to improve readability. To make the required Customizing settings for pricing configuration for Condition Contract Management , in Customizing choose Logistics - General Settlement Management .

Settings for Purchase-Sided and Sales-Sided Condition Contracts Define Condition Tables To define condition tables used for condition types in Condition Contract Management , choose Customizing activity Basic Settings Pricing Maintain Condition Table . Note the following specifics: Usually, the condition table contains the condition contract number as key field. The corresponding short description in the configuration screen is Condition Contract , the technical field name is COCO_NUM. In the delivered standard, SAP provides condition tables 4AB Number and 163 Number/Material as example. In the first condition table the condition contract number is the only business data related key field – beside the validity end of the condition record. In the second condition table, condition contract number and material are the business data related key fields. If you need further key fields for condition tables, you have to extend the field catalog for table key field. Choose Customizing activity Basic Settings Pricing Extend Field Catalog for Condition Tables .

Define Access Sequences To define access sequences used for condition types related to purchase-sided condition contracts in Condition Contract Management , choose Customizing activity Basic Settings Pricing Materials Management (MM) Define Access Sequences . Make sure that you specify (blank) Access sequence relevant for pricing as access category. In the delivered standard, SAP provides access sequence COMP CCM: Only Condition Contract which contains the accesses to the condition tables 163 Number/Material and 4AB Number .

Condition Contracts for Suppliers To make settings for contract conditions related to condition contracts with a supplier as contract partner, choose Customizing activity Condition Contract Management Conditions Purchasing .

Define purchasi ng conditions and activating them for C ondition Contract Manag ement To define condition types related to purchase-sided condition contracts, choose Customizing activity Define Condition Types .

CUSTOMER

6


In the delivered standard, SAP provides the following exemplary condition types: 



Condition type REBT Rebate with access sequence COMP CCM: Only Condition Contract for the settlement amount calculation Condition type REBA Bonus Accrual with access sequence COMP CCM: Only Condition Contract for the posting of accruals. Note that the Accruals checkbox in the Control data 2 group box is selected.

Note the following specific feature: Usually, for the settlement of purchase-sided condition contracts you need condition types with different calculation types such as A Percentage or C Quantity and with a different scale basis such as B Value scale or C Quantity scale. You can create different condition types for the different values of the calculation type and scale basis. However, there is the following alternative to reduce the number of condition types: As you can specify the calculation type and the scale basis during the conditions maintenance in the condition contract – that means, you can overwrite the values copied from the selected condition type -, you can create just one condition type with a certain value for the calculation type and for the scale basis. Accordingly, SAP only provides the two mentioned condition t ypes with calculation type A Percentage and an initial scale basis. To activate condition types related to purchase-sided condition contracts, choose Customizing activity Specify CC-Relevance and Copy Control for Condition Types and select the Condition-ContractRelevant indicator for the relevant condition types.

Defining purchas ing condition type groups with purchas ing conditions For the usage of condition types in the condition contract maintenance, you have to group purchasing condition types in purchasing condition type groups. This purchasing condition type group is then assigned to a condition contract type. To define purchasing condition type groups for purchasing condition types, choose Customizing activity Define Condition Type Groups . To assign purchasing condition types to a purchasing condition type group, choose Customizing activity Assign Condition Types to Condition Type Groups .

Condition Contracts for Customer To make settings for contract conditions related to condition contracts with a customer as contract partner, choose Customizing activity Condition Contract Management Conditions Sales .

Define sales condi tions and activating them for C ondition C ontract Management To define condition types related to sales-sided condition contracts, choose Customizing activity Condition Types .

Define

To activate condition types related to sales-sided condition contracts, choose Customizing activity Specify CC-Relevance and Copy Control for Condition Types and select the Condition-Contract-Relevant indicator for the relevant condition types.

CUSTOMER

7


Define s ales condition type gr oups with s ales conditions For the usage of sales condition types in the condition contract maintenance, you have to group sales condition types in sales condition type groups. This sales condition type group is then assigned to a condition contract type (see chapter Configuring Condition Contract Maintenance). To define sales condition type groups for sales condition types, choose Customizing activity Condition Type Groups .

Define

To assign sales condition types to a sales condition type group, choose Customizing activity Condition Types to Condition Type Groups .

Assign

Note: When you use the Condition Contract Management solution for both supplier and customer rebates, you can re-use condition types and pricing schemas defined for the purchasing-side also for the customersided condition contracts. When you work with the delta accruals settlement process, you do not need salessided conditions at all. Only when you want to consider accruals already in the pricing schema for the salessided operational document (such as the sales order) you have to define an accruals condition type on the sales side (application V Sales/Distribution) and assign it to a sales-sided condition type group. Then you assign the condition type group to the relevant condition contract type – in addition to the purchase-sided condition type group for the rebate.

Other Conditions You define the other required condition types in same way as described above for contract conditions. We repeat shortly the required Customizing activities. Then we describe some specifics for certain required condition types. See also section Specify settlement amount calculation & data transfer from settlement program in chapter Configure Condition Contract Settlement for the usage of these conditions in the pricing procedure. To make the required Customizing settings for other conditions, in Customizing choose General Settlement Management Basic Settings Pricing . To define condition tables, choose Maintain Condition Tables

.

To define access sequences, choose Materials Management (MM) To define condition types, choose Materials Management (MM)

Logistics -

Define Access Sequences

Define Condition Types

.

.

Specifics of Other Conditions Business Volume Amount The condition type that adopts the calculated business volume amount from the settlement run is a manual conditions. This means, you do not specify an access sequence. The condition class is B Prices, the calculation type is B Fixed amount , and the condition category is H Basic price. In group box Changes which can be made, you specify C Manual entry has priority and you select the Item condition, Amount/percent and Value indicator.

CUSTOMER

8


Settled Rebate The condition type that adopts the calculated business volume amount from previous settlement runs e.g. in the case of a cumulative partial settlement or for a final settlement is also a manual conditions. The condition class is A Discount or surcharge, the calculation type is B Fixed amount , and the condition category remains initial. In group box Changes which can be made, you specify C Manual entry has priority and you select the Item condition, Amount/percent and Value indicator. Settled accruals The condition type that adopts the determined amount for the accruals reversal within settlement runs is also a manual conditions. The condition class is A Discount or surcharge, the calculation type is B Fixed amount , and the condition category remains initial. In group box Changes which can be made, you specify C Manual entry has priority and you select the Item condition, Amount/percent and Value indicator.

Result You have made the required Customizing settings for the entry of conditions in condition contract maintenance in Condition Contract Management .

CUSTOMER

9


Configure Condition Contract Maintenance This document describes Customizing settings for the processing of condition contracts in Condition Contract Management .

Prerequisites You have created purchasing condition type groups and/or sales condition type groups as parameters for condition contract types as described in chapter Configuring Condition Contract Conditions. You have implemented ABAP classes that you want to use for additional checks

Procedure The configuration for the condition contract maintenance comprises two main steps. First, you define and configure parameters for condition contract types. Then you define the condition contract types with the configured parameters. Figure 2 gives you an overview for parameters you define for the condition contract type. In section Prerequisites those parameters are mentioned that are not described in the following.

Figure 2: Parameters for the condition contract type

CUSTOMER

10


Define and Configure Parameters for Condition Contract Types Define number ranges To define number ranges for condition contract types, choose Customizing activity Management Condition Contract Define Number Ranges .

Condition Contract

Defining condition contract categ ories You optionally use condition contract categories to group condition contract types. To define condition contract categories for condition contract types, choose Customizing activity Contract Management Condition Contract Define Condition Contract Categories .

Condition

Define and config ure field s tatus g roups You optionally use field status groups to hide condition contract header fields, set them to not ready for input , or make them required fields. To define field status groups for condition contract types, choose Custom izing activity Condition Contract Management Condition Contract Define Field Status Groups for Header Fields .

Define and config ure s tatus profiles You optionally use status profiles to set up your own status management for the condition contract. To define status profiles for condition contract types, choose Customizing activity Management Condition Contract Define and Configure Status Profiles .

Condition Contract

Define and config ure cri tical changes You optionally define critical changes groups containing critical changes for the condition contracts. To define critical changes groups f or condition contract types, choose Customizing activit y Condition Contract Management Condition Contract Define and Configure Critical Changes Groups .

Define and config ure action profiles You optionally use action profiles to define actions for the Post Processing Framework. To define and configure action profiles for condition contract types, choose Customizing activity Contract Management Condition Contract Define and Configure Action Profiles .

CUSTOMER

Condition

11


Define and config ure text determination procedures for header texts and elig ible partner texts The configuration of header texts and eligible partner texts comprises four activities. Choose activity Condition Contract Management Condition Contract Text Control . To define text types for header texts, choose Customizing activity

Define Text Types for Header Texts

To define text types for eligible partner texts, choose Customizing activity Procedures .

.

Define Text Determination

To define text determination procedures for header and eligible partner texts, choose Customizing activity Define Text Types for Header Texts . To assign text types to text determination procedures, choose Customizing activity Text Determination Procedure .

Specify Text Types for

C onfig ure additional checks in addition to the s tandard config uration Checks for data of a condition contract follows a special design which provides, among other things, the extensibility of checks to customer-specific enhancements to the condition contract data model. Checks are implemented in ABAP classes, and SAP provides a standard configuration for the usage of theses ABAP classes for different condition contract scenarios. For more information about the standard configuration for checks, see chapter Standard Configuration for Restrictions and Checks below. Optionally, you can configure additional checks for the condition contract processing based on so called check groups which you assign to condition contract types. Prerequisite is that you have implemented ABAP classes that you want to use for additional checks in this Customizing step. Similar to the standard configuration you assign your customer-specific ABAP check classes to table structures/corresponding fields and field chains for the condition contract. In this assignment step, you also specify the check category characterizing the condition contract usage. Although the entry of the check category implies a certain redundancy with respect to the data model, the assignment has been designed this way to allow an easier overview of all – standard and additional – settings for checks for a certain check category (condition contract scenario). In addition, this design allows to reduce the number of required check groups for example when most of the additional checks are identical for condition contract types having a supplier as contract partner and only a few additional checks have to be differentiated according to whether there are eligible partners or not. To define check groups for condition contract types, choose Customizing activity Management Condition Contract Define Checking Groups .

CUSTOMER

Condition Contract

12


Define and Configure Condition Contract Types Defining condition contract types The condition contract type, with the specified parameters as described above, determines the layout and processing behavior of a condition contract. Note: The condition contract type also comprises settings to control the settlement of a condition contract as described in chapter Configure Condition Contract Settlement below.

To define condition contract types, choose Customizing activity Condition Contract Define Condition Contract Types .

Condition Contract Management

Note the following aspects: Most important, with the Type of Contract Partner attribute you specify whether you define a condition contract type with a supplier or with a customer as contract partner. Value No Contract Partner is used for lists (see below). Additionally, you specify with the Type of Eligible Partners attribute whether eligible partners play a role for the condition contract type. The two fields Type of Contract Partner and Type of Eligible Partners are required entries fields. Optionally, you enter values for the parameters that you have configured, and you make further settings to determine the layout and processing behavior of a condition contract

A ctivate additional func tions for conditi on contract maintenance You can activate additional functions for the condition contract maintenance which are not provided automatically as they require a deeper understanding of the overall condition maintenance.

To activate additional functions for the condition contract maintenance, choose Customizing activity Condition Contract Management Condition Contract Activate Additional Functions for Condition Contract Maintenance . Special condition contract types: customer, supplier and plant lists You can configure special condition contract types in a way that the corresponding condition contracts serve as a customer, supplier, or plant lists. This option has been developed as no other application provides the option to create such lists suitable for the condition contract maintenance. The purpose of these lists is to facilitate the maintenance of eligible partners. Instead of entering a large number of single partners you can also enter a list defined before. In the condition contract type for a list, you choose No Contract Partner for the Type of Contract Partner attribute. With the Type of Eligible Partners attribute, you specify whether the condition contract type is used for a customer, supplier, or plant list. To facilitate data entry for lists several header tab pages such as Purchasing , Sales etc. are hidden as default controlled by the standard configuration as explained in the Standard Configuration for Restrictions and Checks chapter below. Typically, you also select the Hide Conditions Area checkbox - as condition maintenance for lists is usually not required - and the Hide Tab Page for PPF Actions checkbox. Optionally, you can also select the Hide Tab Page for Header Texts checkbox if you do not want to enter header texts.

CUSTOMER

13


Standard Configuration for Restrictions and Checks The condition contract maintenance has been designed in a way to relieve the main program from the implementation of restrictions, e.g. for the ready for input status of condition contract fields, and checks for entered data - in order to provide a higher degree of standardization for restrictions and checks, and to allow further customizable extensions, in particular for customer-specific fields in the table structures relevant for the condition contract. Accordingly, the implementation of restrictions and checks has been transferred to ABAP classes, and a standard configuration has been set up which controls the usage of these ABAP classes for the different condition contract maintenance scenarios. You can display the standard configuration for restrictions and checks using transaction WCC Standard Config. Condition Contract .

Note Do not change the settings of the standard configuration for restrictions and checks . This standard configuration is based on system tables and changes are equivalent with a system modification. A central control parameter used for the standard configuration is the check category. The check category is a composite parameter to characterize the condition contract scenario. It is made up of three parameters of the condition contract type: the type of contract partner, the type of eligible partner, and the Hide Conditions Area indicator which controls whether the condition contract contains conditions entry or not. A selected indicator denotes an eligible partner list. Example: For a chargeback scenario you select Supplier as condition contract partner in the condition contract type, Customer as type of the eligible partner, and you do not select the Hide Conditions Area indicator. The corresponding check category is VE Supplier is Contract Partner/Customers Are Eligible Partners. In the standard configuration, ABAP classes determining restrictions are used in two ways. First, certain ABAP classes are assigned to table structures of the condition contract (see list below) independent from the check category. The corresponding restrictions hold for every condition contract scenario. Example: Certain fields as e.g. the Created On and Created By are display only fields for all condition contract scenarios. Second, ABAP classes are also assigned to table structures dependent on the check category. Example: For an eligible partner (customer, supplier, plant) list, all the fields for organizational data are hidden so that the Purchasing and the Sales tab page do not appear in the header area of the condition contract. The standard configuration for checks is always dependent on the check category. Note the following details of the set up: First of all, you have to distinguish between checks for whole table structures of the condition contract and individual fields of these table structures on the one hand and checks for so called field chains. A field chain is a set of fields of a table structure that belong together logically so that they have to be checked simultaneously. Example: Field chain H005 Sales Area Test in WCOCOH for the existence check of the sales area entered in the condition contract header. Second, for the usage of ABAP classes for check you have to distinguish between direct assignments to table structures/corresponding fields and field chains and a two-step configuration involving a reuse key. The assignment to table structures/corresponding fields can be differentiated according to the execution time (Create, Change, Delete, Before Saving). An example for the direct assignment of an ABAP check class is the existence check for the entered condition contract partner (table fields WCOCOH-CUST_OWNER and WCOCOH-VEND_OWNER for a customer or supplier, respectively). The two step configuration has been introduced to reduce the number of configuration settings when checks are identical for different condition contract scenarios. In the first step, SAP has defined reuse keys – for table structures and corresponding fields and for field chains. The reuse key for table structures and corresponding fields bundles the assignment of ABAP check classes to several table structures and fields. For example, reuse key CONDBEFORESAVING Condition checks before saving (BU) contains ABAP check classes for table structures KONH Condition Header and KONP Condition Item. The reuse key for field chains CUSTOMER

14


bundles the assignment of ABAP check classes to several field chains. For example, reuse key HEADERWITHOWNER bundles the assignment of ABAP check classes to several field chains of the condition contract header. In the second step, the reuse keys have been assigned to check categories. In case of the assignment to table structures/corresponding fields, artificial table structure names ( REUSE1 to REUSE20) are used to enable the assignment of several reuse keys to a check category / execution time combination.

Note With the Customizing for additional checks you can extend the standard configuration for checks, but you cannot overwrite it. The configured ABAP check classes are executed anyway. Table structures of the condition contract relevant for restrictions and checks: WCOCOH

Condition Contract Header

WCOCOI

Condition Contract Item (for eligible partner entry)

KOMG

Condition Key

KONH

Condition Header

KONP

Condition Item

CONDSCALE

Condition Scales

Enhancements Using Business Add-Ins SAP provides a series of Business Add-Ins to change or enhance the user interface of the condition contract and to change or enhance the processing behavior of a condition contract. In Customizing for Condition Contract Enhancements Using Business Add-Ins Condition Contract Maintenance . Management , choose

Result You have made the required Customizing settings to process condition contracts in Condition Contract Management .

CUSTOMER

15


Configure Condition Contract Settlement This document describes Customizing settings required for processing the condition contract settlement. In the settlement process, you determine the settlement amount, for relevant business partners, for a certain period, based on the business volume. The Condition Contract Management solution has been developed to support a large variety of scenarios for a subsequent compensation with different business partners based on different kinds of business volume data. Examples are supplier rebates arrangements based on supplier invoice amounts or delivery quantities, customer rebates based on revenues or sales quantities, chargeback agreements involving customers and a supplier and so on. Accordingly, the configuration of the condition contract settlement has been designed to provide the required high degree of flexibility. Because of this, the following configuration description f irst outlines the basic configuration concepts and explains elements of simple scenarios. Afterwards, specific configuration settings for certain scenarios are described which of course cannot cover the full scope of options. The configuration for the condition contract settlement comprises five main areas: Business volume determination Settlement calendar Calculation of the settlement amount Creation of settlement documents Reversal of accruals This will be detailed in the following in special chapters. Prerequisites The configuration of the condition contract settlement has two main prerequisites. 

 

For the business volume determination, you must create a database view in the data dictionary that is required to select business volume data from relevant physical database tables. You must configure the settlement documents in the Customizing for Settlement Management. You have created the factory calendars that you want to use as settlement calendars for final, partial, delta, and delta accruals settlement.

Details of the prerequisite are explained in the sections below.

Procedure To make the required Customizing settings for the Condition Contract Settlement process step, in Customizing choose Logistics - General Settlement Management Condition Contract Management Condition Contract Settlement .

CUSTOMER

16


Configure Business Volume Determination The business volume forms the basis of the condition contract settlement. Typically, it’s a certain amount derived from the business transactions you make with a business partner. For purchase-sided condition contracts, you usually determine the total amount of supplier invoices, for sales- sided condition contracts it’s typically the total amount of customer invoices. Optionally, you can differentiate the business volume according to certain parameters which influence the settlement amount. For instance, you can determine the total amount of supplier invoices for different merchandise categories for which you get different rebates. Alternatively to amounts, you can also use a quantity derived from business transactions as the business volume, or you can use weights, volumes or points as business volume base. The following figure 3 sketches the central configuration settings for the business volume determination. In this figure we assumed a condition contract for supplier rebates based on supplier invoices as an example. Configuration steps for the central configuration settings are described in section Basic Configuration with One Data Source below. Additional, optional features of the business volume determination are described in section Extended Configuration with Several Data Sources below.

Figure 3: Configuration elements for the business volume determination In the condition contract type, you specify two central composite parameters which first control from which data source you want to select which business volume data and second which selection criteria you can want to use. The first composite parameter is the profile for business volume determination (see left side of figure 3). This profile parameter contains the so called business volume table and settings which fields in the business volume table represent the business volume. The business volume table can be a single database table or a database view for two or more database tables. The database table(s) contain(s) the business transactions. To identify the business volume base, you usually have to specify the date field name in order to limit the business volume to the specified validity of the condition contract and the set tlement periods within the condition contract. When you use an amount as business volume basis (specified in the Amounts Fields dialog structure), you must specify the currency field name, for quantities (weight, volume, points) as business volume basis you specify the quantity (weight, volume, points) field name and the corresponding unit of measure field name.

CUSTOMER

17


Note The supplier and customer field name on the profile have a special function. Sometimes you do not want to use field LIFNR (KUNNR) for the supplier (customer) in the business volume determination in a purchasesided (sales-sided) condition contract. This is for instance the case when only those business transactions with the contract partner shall be considered in which a specified partner role in the source document has a certain value. For these scenarios, you can use the supplier (customer) field name to identify the alternative partner in the business volume selection criteria as well as in the source documents. Additional, this setting is in particular required for the condition contract determination in the pricing of the source documents. In addition to the explained basic settings, the profile contains additional controlling parameters for the business volume determination such as the explosion of a material or customer hierarchy. The second composite parameter for the business volume determination is the set of field combinations (see right side of figure 3). A single field combination contains the selection criteria for the business volume selection in form of field names. Note that these field names have to be included in the business volume table specified in the relevant profile for the business volume determination. Selection criteria within a field combination are connected with an AND logic in the WHERE clause of the selection, different lines for a field combination are taken into consideration with an OR logic. In the example for supplier rebates in figure 3 you use only one field combination which contains the field names LIFNR for the supplier and MATNR for the material. When you create a condition contract with this condition contract type you can specify values for the selection criteria on the Business Volume Selection Criteria tab page, e.g. you specify that you want to select business volume data for Supplier1 and Material1, Material2 and Supplier2 and Material2 . The SELECT statement for the example can be sketched as follows: SELECT ( LIFNR, BUDAT, …, WRBTR, …) FROM ( BUSINESS_VOLUME_TABLE ) WHERE ( ( LIFNR = ‘SUPPLIER1’ AND M ATNR = ‘MATERIAL1’ ) OR ( LIFNR = ‘SUPPLIER1’ AND M ATNR = ‘MATERIAL2’ ) OR ( LIFNR = ‘SUPPLIER2’ AND MATNR = ‘MATERIAL2’ ) ). Different field combinations are connected with an AND logic in the WHERE clause. Continuation of the example: A field com bination with fields LIFNR and MATNR is r easonable when you want to enter combinations with different suppliers and materials. When only one supplier plays a role, you have to enter this supplier in connection with all relevant materials which implies a redundancy in the data entry. In such a case, you can use two different field com binations S001 with field LIFNR (supplier) and M001 with field MATNR (material). You enter suppler Supplier1 only once for field combination S001 and all relevant materials for field combination M001. The WHERE clause for this case can be sketched as follows: … WHERE ( LIFNR = ‘SUPPLIER1’ ) AND ( ( MATNR = ‘MATERIAL1’ OR M ATNR = ‘MATERIAL2’ ) ). Another control parameter for the set of field combinations is the field combination group which also helps you to facilitate the entry of selection criteria in the condition contract. A field combination group effects that the business volumes for the field combinations included in the group are summarized. Accordingly, field combinations within a field combination group are connected with an OR logic instead of AND logic in the WHERE clause for the business volume determination.

CUSTOMER

18


Example The set of field combinations contains three field combination: S001 with field LIFNR (supplier), M001 with field MATNR (material), and M002 with field MATKL (material group). You have specified a field combination group FCG1 for field combinations M001 and M002. In the condition contract, you specify one supplier Supplier1 for field combination S001, one material MAT001 for field combination M001, and one material group MG10 for field combination M002. Accordingly, the business volume is determined for supplier SUPP1 and m aterial MAT001 and for supplier SUPP1 and material group MG10 and both business volume values are added. The WHERE clause for this configuration can be sketched as follows: … WHERE ( LIFNR = ‘SUPP1’ ) and ( MATNR = ‘MAT001’ or MATKL = ‘MG10’ ). Without field combination group you would have to list all relevant materials of material group MG10 for field combination M001. Another parameter controlling the usage of business volume selection criteria for different data sources, the selection group, is explained in the Extended Configuration with Several Data Sources section below.

Prerequisites Create the database views that you want to use to select business volume data from relevant ph ysical database tables. In the delivered standard, SAP provides the following database views: 





WCB_V_RBKP_RSEG Supplier Invoices - Business Volume Determination for a condition contract for supplier rebates based on supplier invoices WCB_VBRK_VBRP_BV Customer Invoices - Business Volume Determination for a condition contract for customer rebates based on customer invoices WCB_V_MATDOC Material Documents - Business Volume Determination for a condition contract for supplier rebates based on material documents for goods receipts

Basic Configuration with One Data Source In the basic configuration you determine business volume data from only one data source. Configuration settings in the context of several business volume sources are explained in the Extended Configuration with Several Data Sources section below this section. In that section we will also introduce Custom izing activities for defining parameters of the profile that you can use when configuring several data sources. The two central parameters for the business volume data selection that you enter for a condition contract type are defined in the f ollowing two steps.

Define and Config ure Profi les for B us ines s V olume Determination In this profile, you specify from which data source business volume data is determined and which information shall be selected. To define and configure profiles for business volume determination for condition contract settlement, choose Customizing activity Define and Configure Profiles for Business Volume Determination .

CUSTOMER

19


Define and config ure field combinations and s ets of field combinations Field combinations contain the selection criteria for the business volume selection. Within a field combination selection criteria are connected with an AND logic. The set of field combinations is a group of field combinations. You assign a set of field combinations to a condition contract type. Accordingly, in the condition contract maintenance you can enter values for the selection criteria on the Business Volume Selection Criteria tab page in the contract’s header area. To define field combinations, choose Customizing activity Selection .

Define Field Combinations for Business Volume

To define sets of field combinations, choose Customizing activity

Define Sets of Field Combinations

.

A s s ig n the profiles for bus ines s volume determination and the sets of field combinations to condition contract types Choose Customizing activity

Specify Settlement Settings for Condition Contract Types

.

First of all, specify the condition contract settlement type in Contract Control group box. Then you specify the profile for business volume determination and the set of field combinations in the Business Volume group box. You can also use the eligible partner type as selection criterion. The eligible partners specified in the condition contract in the Eligible Partners area are the relevant values for this selection criterion. Similar to other selection criteria, you have to enter a field combination for the relevant partner type to specify the corresponding field name in the structure of the business volume table. In addition, you have to specify in the Use of Eligibles field that you want to use the eligible partner type as (optional or mandatory) selection criterion.

Extended Configuration with Several Data Sources You can also configure that the business volume determination shall involve several data sources. This configuration comprises the definition of two additional configuration objects – these are selection groups and business volume table groups – and additional settings for the profile for business volume determination. An objective of the extended configuration design was to keep the number of required profiles for business volume determination small and thus the configuration work low. The idea is that you define profiles with all required data sources for certain condition contract scenarios and you decide in the condition contract which data sources you want to use for the concrete condition contract that you create. This means that it is not necessary to define profiles for all possible combinations of data sources. A similar approach holds for the business volume selection criteria. You can configure that certain selection criteria can be restricted to certain business volume tables. The extended configuration with several data sources is sketched in the following figures 4 and 5.

CUSTOMER

20


Figure 4: Business volume determination with additional business volume tables – Relevant data sources

Figure 5: Business volume determination with additional business volume tables – Relevant selection criteria

CUSTOMER

21


First, you define business volume table groups that you want to use for profiles for business volume determination. The business volume table group is a set of business volume tables. Accordingly, for each business volume table group that you define you specify the corresponding business volume tables. Second, in a profile for business volume determination, you specify two settings for the usage of several data sources. First, you specify the additional business volume tables. And second, you specify the relevant business volume table groups. Make sure that the business volume tables assigned to a business volume table group match with the additional business volume tables you specify for the profile. As known, the profile for business volume determination is assigned to a condition contract type. If you create a condition contract with a condition contract type for which you have maintained business volume table groups for the assigned profile, the entry field for the business volume table group on the Settlement Data tab page gets visible and the dropdown list contains the maintained business volume table groups. With the selection of the business volume table group, you specify which business volume tables become relevant for the condition contract you just create. Note, that the m ain business volume table is always relevant. In the example of figure 4, BV Table Group 2 is selected. Accordingly, business volume table B is relevant beside the main business volume table. Similarly, you define selection groups that you want to use for profiles for business volume determination. Then you make settings for selection groups in the profiles for business volume determination. Two main settings for the usage of selection criteria are relevant. First, you specify the relevant selection groups for the profile. Optionally, select the Apply Selection Group Only to Additional Bus Volume Tables indicator for a selection group. The function of this feature is explained below. Second, you assign selection groups to the additional business volume tables. Make sure that the selection groups assigned to additional business volume tables match with the relevant selection groups that you specify for the profile. If you create a condition contract with a condition contract type for which you have maintained selection groups for the assigned profile, an additional column Selection Group becomes visible in the Business Volume Selection Criteria table on the tab page with the same name and the field help for the selection group shows the selection groups maintained for the relevant profile. When you specify a selection group for a line in the Business Volume Selection Criteria table then the system proceeds as follows: it determines the business volume from the main table of the profile unless you have selected the Apply Selection Group Only to Additional Bus Volume Tables indicator for this selection group. Additionally, the system determines the business volume from those business volume tables – as part of the specified business volume table group to which this selection group has been assigned. You can also specify for an additional business volume table that the system applies it for the business volume determination only when an entry for the business volume selection criteria exists in the condition contract header for which a selection group is specified. You can configure that an additional business volume table is applied when you specify any selection group for business volume selection criteria or that you have to specify a selection group that you have assigned to the additional business volume table. You use the If Any Selection Group is Specified configuration to distinguish between a condition contract scenario without any selection group and a scenario where you specify certain selection groups either for the main business volume table or for additional business volume tables. Typically, in the scenario without any selection groups the business volume determination results in the same business volume base for the relevant business volume tables. So, in this scenario you want to exclude the redundant access for a certain business volume table with this indicator.

CUSTOMER

22


Specify Settlement Calendars In a condition contract type, you make settings for the creation of the settlement calendar for a specific condition contract. The calendars specified in the condition contract type are defaults and can be overwritten in the actual condition contract. Prerequisites You have created the factory calendars that you want to use as settlement calendars. To define factory calendars, choose Customizing activity Calendar .

SAP NetWeaver

General settings

Maintain

S pecify s etting s for the settlement calendar for the conditi on contract types Choose Customizing activity


.

Specify a calendar for final and partial settlement in the Settlement Calendar group box. Specify whether the partial settlements shall be performed cumulative or separately. If you want to perform a delta settlement for final settlements, specify a calendar for delta settlement and enter the (maximum) number of delta settlements. Instead of a calendar, you can also specify a creation date. Enter the number of days after the final settlement, on which the delta settlement shall occur. If you want to specify a deviating time interval for the business volume determination for a specific settlement date, choose the required value from the dropdown list of the Deviating Business Volume Dates Active parameter. If you want to allow extension of a condition contract, enter a calendar for contract extension. If you want to allow that dates for the settlement of delta accruals may coincide with dates for partial settlement or partial and final settlement, select 1 Partial Settlement with Delta Accruals Allowed or 2 Partial and Final Settlement with Delta Accruals Allowed for the Multiple Settlements on Same Date indicator. If you want to enable manual creation of settlement calendar entries, select the Manual Changes Allowed indicator. If you want that the system checks that a settlement date exists with the valid-to date of the condition contract, select the Check Settlement Date w/ Valid-To Exists indicator.

Configure Settlement Document Creation and Settlement Amount Calculation The configuration of the settlement document creation and the settlement amount calculation are treated together in this section as the pricing procedure determination depends on the settlement document type of the settlement document. Prerequisites You have made all the required configuration settings for the settlement documents in Settlement Management .

CUSTOMER

23


Specify settlement document creation for the condition contract types Choose Customizing activity


.

The configuration of the settlement document creation comprises four steps: Step 1: Specify the condition contract settlement type in the Contract Control group box. Choose 1 Supplier Contract Settlement or 2 Customer Contract Settlement when you want to create settlement documents towards a supplier or a customer, respectively. Step 2: Specify the settlement type supplier or the settlement type customer in the Settlement group box according to the selected condition contract settlement type of step 1. Example: You have to specify the settlement type supplier when you have selected 1 Supplier Contract Settlement for the condition contract settlement type. Step 3: Specify the settlement process type and optionally the settlement document type for the settlement document. Make these settings according to the selected condition contract settlement type and the related settlement type supplier/customer. Note: If you do not specify the settlement document type for the settlement document, the system will use the settlement document type that you have assigned to the settlement process type for the settlement document creation. Example 1: You have selected 1 Supplier Contract Settlement for the condition contract settlement type and as Accounts Payable for the Settlement Type Supplier field. Accordingly, you specify the required settlement process type for the Settlement Proc. Type (Accounts Payable) field and optionally the settlement document type for the Settlement Doc. Type (Accounts Payable) field within the Supplier Settlement group box. Example 2: You have selected 2 Customer Contract Settlement for the condition contract settlement type and Proforma as Accounts Receivable for the Settlement Type Customer field. Accordingly, you specify the required settlement process type for the Settlement Proc. Type (Accounts Receiv.) field and optionally the settlement document type for the Settlement Doc. Type (Accounts Receiv.) field within the Proforma Settlement group box as part of the Customer Settlement group box. Step 4: Make further settings for the settlement document creation in the Settlement group box.

CUSTOMER

24


Specify settlement amount calculation & data transfer from settlement program Configuring the pricing for a settlement document is part of the Customizing of Settlement Management . However, we repeat important configuration steps here to facilitate your implementation work. In addition, you have to specify how data determined in the settlement are to be transferred to the pricing procedure. Prerequisites You have created required condition types as described in section Other Conditions of chapter Configure Condition Contract Conditions. Settlement Amount Calculation To make the required Customizing settings for this part of the pricing configuration for settlement documents, in Customizing choose Logistics - General Settlement Management Basic Settings Pricing . First, you have to define suitable pricing procedures. Figure 6 sketches the main elements. The first step contains the condition type, here BUVO, for the business volume amount, the second step the rebate condition RS01, the third step the already settled rebate amount for a cumulative partial settlement and the final settlement. The following subtotal line contains the actual rebate amount of the settlement run for which you calculated the tax amount. The last step concerns the determined amount for the accruals reversal.

Note The system automatically sets a negative sign for the already settled rebate amount in the calculation. You do not have to consider this in the condition type definition.

Figure 6: Settlement amount calculation

CUSTOMER

25


To define required pricing procedures, choose Materials Management (MM)

Define Pricing Procedures

.

Next, you make settings for the pricing procedure determination. The pricing procedure determination depends on four parameters: the schema group for purchasing organizations, the document schema group for settlement documents, the schema group for suppliers, and, in the case of customer-sided pricing procedures, the customer classification for pricing procedure determination. You define these parameters and then you assign these parameters to the respective business objects. To define schema groups for suppliers and purchasing organizations, choose Define Schema Groups and choose either sub activity Define Schema Groups for Suppliers or Define Schema Groups for Purchasing Organizations. Choose sub activity Assign Schema Groups to Purchasing Organizations to assign defined schema groups for purchasing organizations to purchasing organizations. You assign schema groups for suppliers to a supplier within the Vendor business role. Choose the Purchasing view, specify the relevant purchasing organization, and specify the schema group on tab page Purchasing Data in group box Additional Purchasing Data. To define document schema groups, choose Define Document Schema Groups for Settlement Document Types and define the schema groups with a suitable text. To assign document schema groups to settlement document types, choose Logistics - General Settlement Management Settlement Documents Settlement Documents Types All Document Types . Select the relevant settlement document type and assign the document schema group in group box Pricing . To configure the pricing procedure determination, choose Pricing Procedure Determination required entries.

and maintain

Data Transfer to Pricing Procedure To make the required Customizing settings for this part of the pricing configuration for settlement documents, in Customizing choose Logistics - General Settlement Management Condition Contract Management Condition Contract Settlement . The following settings are relevant To transfer the determined business volume amount, choose Customizing activity Define and Configure Profiles for Business Volume Determination , select the relevant profile and choose dialog structure Amount Fields, and specify the target condition type for the business volume amount fields. To specify the condition type for settled rebates, choose Customizing activity Specify Settlement Settings for Condition Contract Types , select the relevant condition contract type and specify the condition type in the Condition Type Reverse Partial Settlemnt field of group box Settlement . The data transfer for accruals is described in the chapter Specify Posting and Reversal of Accruals below.

CUSTOMER

26


Granularity of the settlement For the central financial purpose of the settlement run, that is the creation of the amounts receivable and payable in Financial Accounting, it would be sufficient to work with aggregated data for the business volume and the calculated settlement amount. However, often you want to see more information - that is for which business objects the condition contract has been applied. For example, in the settlement of a condition contract for a supplier rebate you not only want to see the overall rebate amount but also the rebate amount of relevant material groups or materials. To enable this finer granularity for the condition contract settlement, you define so called split criteria in the profile for the business volume determination. You can specify split criteria on header level leading to separate settlement documents for different values of the split criterion and split criteria on item level leading to separate items in the settlement document. To configure split criteria you enter field names of the business volume table. When you use customerspecific fields make sure that these fields are also available in the database table of the settlement document. To define split criteria for the settlement document creation in profiles for business volume determination, choose Customizing activity Define and Configure Profiles for Business Volume Determination , select the relevant profile, choose dialog structure Split Criteria for Settlement , and specify the field name of the business volume table, the level for the split (Head or Item),and the target field in the settlement document.

Note In the condition contract type, you can also activate the fiscal year as split criterion. Choose Customizing activity Specify Settlement Settings for Condition Contract Types , select the relevant condition contract type and select the Split Settlement Items by Fiscal Year checkbox in group box Settlement .

Specify Posting and Reversal of Accruals You usually want to post accruals to consider future financial commitments from condition contracts in Financial Accounting. During the condition contract settlement you want to reverse the accrual postings and replace them with the correct financial commitments for the business partners of a condition contract. Accordingly, the configuration includes two steps:  

Posting of accruals in FI Reversal of accruals in condition contract settlement

Steps for the Posting of Accruals The configuration for the posting of accruals for condition contracts contains steps within and outside the configuration of Condition Contract Management .

CUSTOMER

27


Prerequisites i) You have defined purchasing or sales condition types groups with condition types for accruals as described in section Configuring Condition Contract Conditions. Accordingly, you can maintain values for accrual conditions during condition contract maintenance. ii) You have made configuration settings for the account determination for accrual postings in Financial Accounting in the usual way (see below).

Pos ting of accr uals i n the s ource document You have to include condition types for accruals in the pricing procedure of the source documents. Additionally, you have to configure the posting of accruals in Financial Accounting. To maintain condition types for accruals in the pricing procedure for purchase orders, choose Customizing activity Materials Management Purchasing Conditions Define Price Determination Process Define Pricing Procedures . For the posting of accruals in Financial Accounting, enter a suitable account key in the Account Key Accruals column in the line for your accrual condition type. For the account determination, you have made setting in activity Materials Management Valuation and Account Assignment Account Determination , particular for activity Configure Automatic Postings. To define condition types for accruals in the pricing procedure for sales orders, choose Customizing activity Sales and Distribution Basic Functions Pricing Pricing Control Define And Assign Pricing Procedures , step Maintain pricing procedures. For the posting of accruals in Financial Accounting, enter a suitable account key in the Account Key Accruals column in the line for your accrual condition type. For the account determination, you have made the usual settings in Functions Account Assignment/Costing .

Sales and Distribution

Basic

A ctivate track ing of acc ruals conditi ons As the accruals reversal process is based on table WCOCOF Usage of Condition Contract Conditions you have to activate the data transfer of accruals conditions from the source document to this table. Choose Customizing activity Specify Settlement Settings for Condition Contract Types , select the relevant condition contract type and select the Accruals from Purchasing , Accruals from Sales, or the Accruals from Settlement Management checkbox depending on the type of source document for the condition contract.

CUSTOMER

28


Steps for the Reversal of Accruals The condition contract settlement program does not read the FI documents for the reversal of accrual postings. Instead, it uses the solution specific b uffer or index table WCOCOF Usage of Condition Contract Conditions as basis for the accrual reversal for condition contracts. Figure 7 sketches the main elements of the accruals reversal. As mentioned above, the pricing procedure of the source document contains the condition types for accruals. When you save the source document the system not only posts accruals in Financial Accounting. It also saves an index of the document conditions for the accrual condition types in table WCOCOF. The settlement program reads the indices related a condition contract for which you run the settlement, calculates the accruals amounts and transfers the values to so called target condition types from the pricing procedure of the settlement document. When the system saves the settlement document, the accruals account in Financial Accounting is cleared.

Figure 7: Elements of the accruals reversal posting

Prerequisites i) You have to define condition types that will adopt the accruals reversal amount in the pricing procedure of the settlement document. To define such condition types for a purchase-sided (application M Purchasing ) pricing procedure of the settlement document, choose Customizing activity Logistics - General Settlement Management Basic Settings Pricing Materials Management (MM) Define Condition Types . To define such condition types for a sales-sided (application V Sales/Distribution) pricing procedure of the settlement document, choose Customizing activity Logistics - General Settlement Management Basic Settings Pricing Sales (SD) Define Condition Types .

CUSTOMER

29


ii) You have to include a condition type for accruals reversal in the pricing procedure of the settlement document. To maintain accrual condition types in purchasing-sided pricing procedures for settlement documents, choose Customizing activity Logistics - General Settlement Management Basic Settings Pricing Materials Management (MM) Define Pricing Procedures . To maintain accrual condition types in (sales-sided) pricing procedures for settlement documents, choose Customizing activity Logistics - General Settlement Management Basic Settings Pricing Sales (SD) Define Pricing Procedures . For the posting of accruals in Financial Accounting, enter a suitable account key in the Account Key Accruals column in the line for your accrual condition type. iii) You have to make configuration settings for the account determination for accrual postings in Financial Accounting in the usual way. For the account determination in the context of purchasing-sided pricing procedures for settlement documents, you have made setting in activity Materials Management Valuation and Account Assignment Account Determination , particular for activity Configure Automatic Postings. For the account determination in the context of sales-sided pricing procedures for settlement documents, you have made settings in activity Sales and Distribution Basic Functions Account Assignment/Costing .

R evers al of accruals in the condition contract settlement prog ram You have to make settings to identify the right accrual conditions in the settlement program. In addition, you make settings, how you want to post the accruals reversal. You maintain these settings in the condition type groups for accruals which you then assign to condition contract types. Note: The settings for the accrual reversal have to be consistent with settings for posting accruals in Financial Accounting when saving a source document. Choose Customizing activity Define and Configure Condition Type Groups for Accruals condition type groups for accruals.

to define

For each accrual condition type of the group, specify the target condition type that you use in relevant pricing procedures for settlement documents to adopt the accruals reversal amount determined in the settlement run. In figure 6, you can see the target condition type CCSA for the accruals reversal in the sketched pricing procedure. Compare section Configure Settlement Document Creation and Settlement Amount Calculation of this chapter for more information about the settlement document creation. Choose Customizing activity Specify Settlement Settings for Condition Contract Types condition type groups for accruals to condition contract types.

to assign

Specify the condition type group for accruals in the Accruals group box.

CUSTOMER

30


G ranulari ty of accr uals revers al Similar to the split criteria for the settlement – see section Granularity of the settlement above – you can also configure the granularity for the accruals reversal. Again, you specify field names, now for the accruals reversal splitting, in the profile for the business volume determination. There are two technical concepts to enable the accruals reversal splitting: 



Split information is determined directly from entries in table WCOCOF Split information is determined dynamically from source documents during the settlement run using a CDS view

In the first concept, table WCOCOF contains the specified fields for the split. This means that the splitting is already considered when accruals condition data is transferred to this table. To avoid data redundancy, table WCOCOF does not contain many business related fields that can serve as split criteria for the accruals reversal. That means that you (usually) have to extend this table with the fields you want to use. For this extension you use include structure WB2_WCOCOF Rebates: Additional fields for Accruals. In the delivered standard, there are already three business related fields: include structure WB2_WCOCOF contains the fields WERKS Plant and BUKRS Company Code; in addition, you can use field GJAHR Fiscal Year by selecting the Split Settlement Items by Fiscal Year indicator for the relevant condition contract type.

Note Usually, you add a field nam e to include structure WB2_WCOCOF that is also included in the source document with the same name. Then the system fills this field automatically when creating the WCOCOF index entry. This holds for standard fields of the source document but also for customer-specific (Z-) fields. When you add a field name to WB2_WCOCOF that is not available in the source document with this name you have to implement the relevant method of business add-in WB2_ACCRUALS_BEFORE_UPDATE BAdI: Change Accruals Data before Update. For the second concept, you specify field names with suffix _CDS such as MATNR_CDS, EKORG_CDS and so on. When processing the accruals reversal in the settlement run, the system relates the WCOCOF index entry to the business information (material, purchasing organization etc.) from the source document specified with the _CDS split criteria and performs the accruals reversal split amount determination accordingly. Technically, business information is retrieved from source documents using CDS view WB2_CDS_CCS_ACCRUALS_REVERSAL . All possible ‘dynamic’ fields with suffix _CDS are contained in structure WB2_S_CCS_FLOW_DOC_DYN Fields for Dynamic Determination of Accruals Reversal Splits.

Note You cannot extend the logic of this second concept as structure WB2_S_CCS_FLOW_DOC_DYN cannot be extended. You can also make use of both concepts. This means that you can specify field names from table WCOCOF and field names with suffix _CDS as split criteria. When you do not use field names with suffix _CDS the CDS view will not be called.

CUSTOMER

31


Note If you make use of both concepts you also have to enhance CDS view WB2_CDS_CCS_ACCRUALS_REVERSAL using an extension view. Here you use association _CCS_FLOW_ENH to declare in the CDS view the fields that you have added to include structure WB2_WCOCOF . This holds for standard fields of the source document but also for customer-specific (Z-) fields. To define split criteria for the accruals reversal in profiles for business volume determination, choose Customizing activity Define and Configure Profiles for Business Volume Determination , select the relevant profile, choose dialog structure Split Criteria for Settlement , and specify field names in the Field Name for Accruals Split column.

Enhancements Using Business Add-Ins SAP provides a series of Business Add-Ins to change or enhance the processing behavior for the settlement of condition contracts. In Customizing for Condition Contract Management , choose Enhancements Using Business Add-Ins Condition Contract Settlement .

Additional Settings for the Settlement Run Beside the central configuration for the condition contract settlement as described above there are additional configuration settings to control the settlement run. Settlement Material For the settlement documents created in the settlement run you often want to use a settlement material. You can enter the settlement document in the condition contract but in Customizing you can specify a default for the settlement material per condition contract type. Make sure that you use C Material-Related for the Entry Category for Logistics Data parameter for relevant settlement process types when you create settlement documents with a settlement material. To specify a default for the settlement material, choose Customizing activity Settings for Condition Contract Types .

Specify Local Settlement

Additional Checks for Settlement Run The system performs several standard checks and checks based on configuration settings whether a settlement can be performed for a condition contract, for the specified settlement date, and the settlement type. Examples for simple checks are that a condition contract must have status Released , it may not have a settlement lock and the condition contract has yet not been settled for a specific settlement date. An example for a configuration setting is parameter Requirement Next Settlement Allowed of the condition contract type that controls which status the settlement documents for previous settlement dates need to have, so that the settlement run for the next settlement date can be performed. With the Check Manager tool you can configure additional checks whether a settlement run is allowed.

CUSTOMER

32


Prerequisite You have to create global ABAP classes in the class pool which implement the additional checks. To specify additional checks in the Check Manager tool, choose Customizing activity Checks for Settlement Run in the Check Manager .

Specify Additional

User-Specific Message Control The user-specific message control concerns the creation of the settlement documents during a settlement run. You can find the corresponding Customizing activity also beneath the Basic Settings node for Settlement Management . The relevant application area for messages is WS Supplier Billing Documents. Note that not all of the message contained in application area WS are relevant for the condition contract settlement. To specify user-specific message control, choose Customizing activity Control .

Specify User-Specific Message

General Settings The Customizing activity for general settings is designated for the maintenance of general parameters for the Condition Contract Settlement process step independent of the condition contract type. Currently, this Customizing activity is used only to make settings for the statistics reporting and for side panel CHIPs. You specify subtotal fields of the pricing schemas used for supplier and customer condition contracts in order to identify the accruals reversal a mount, the partial settlement reversal amount, and the business volume amount.

To make these settings for the statistics reporting and for side panel CHIPs choose Customizing activity Specify General Settings . PMR Inbound In the Promotion Management Retail (PMR) solution you cannot specify all data required for condition contract maintenance and settlement. Accordingly, you have to specify missing data in Customizing. To specify required data for condition contracts created out of the PMR solution, choose Customizing activity Specify Settings for PMR Inbound .

Result You have made the required Customizing settings to perform the condition contract settlement including the reversal of accruals in the Condition Contract Management solution.

CUSTOMER

33

03 CCM Configuration en V1 3

Recommend Documents