A condition contract can be used, for example, to manage rebates granted for meeting quantity or value targets for sales or purchase volumes in a defined period. It is used to enter conditions that refer to one or more suppliers or customers, or business partner, or one or more materials. The condition contract combines all information relevant to the agreement, such as the condition granter or owner of the condition contract, and special conditions such as rebates or prices. A condition contract can for example also be used to settle vendor funds from SAP Promotion Management for Retail.
The condition contract maintenance function WCOCO - or SAP Fiori app Maintain Contract - Condition Contracts - is the single point of entry for maintaining contract data and contract related conditions.
A condition contract is structured in the following way:
Condition Contract Header:
The condition contract header contains information such as the owner of the condition contract, a validity period, the document status, currency information, exchange rate, terms of payment, purchasing organization, and sales area.
Furthermore, there is the relevant settlement information, such as settlement type and settlement calendar. In addition, the business volume base to define the documents to be selected - for example, Vendor, Vendor/Article, or Vendor/Site level. Furthermore, it is possible to exclude single entries.
Besides the validity of the condition contract, the document status determines how the document can be changed and archived. The status is determined by means of standard SAP status management. Among other things, this supports definition of a user-defined status.
Conditions:
The conditions to be processed in the condition contract are stored in Customizing as condition tables that must each contain the condition contract number in the access sequence.
Condition records can be entered for each condition table, which was assigned to a condition contract. A condition record key consists of the condition type, access fields (dependent on the condition table), and the validity period. The condition value can be a currency amount, or a percentage value. After you made an entry, only the validity period and the value can be changed.
Accruals are maintained as separate condition records in a condition contract.
It is also possible to display the complete document flow and/or the condition usage within the condition contract transaction.
This example shows a condition contract with supplier R1TV05##, valid for the period October-December. The condition is scaled, and a monthly settlement calendar applies. This means partial settlement runs are scheduled accordingly at the end of each month. The business volume in October does not reach the minimum scale of 500 USD, so there is no settlement amount. The 2% accruals posted during October for the 400 USD business volume are cleared.
At the end of November, the business volume amounts to 8.400 USD: 400 USD from October, plus 8.000 USD from November. This means the settlement run calculates a bonus of 168 USD (2% for 8.400 USD). The accruals amount is updated accordingly. At the end of December, with an overall business volume of 28.400 USD, the second scale level is reached. This means the overall bonus is 1.136 USD (4% of 28.400 USD). For the final payment, the system deducts the amount(s) received so far, which is in our example 1.136 USD - 168 USD = 968 USD.
You can display the business volume for your contract using transaction WB2R_BUSVOL, or SAP Fiori app Display Business Volume - Condition Contracts. With the output level you can determine the aggregation level for the data display. To execute the settlement run, use transaction WB2R_SV, or SAP Fiori app Settle Condition Contracts - Supplier Contracts.