Skip to end of metadata
Go to start of metadata

 The following article gives the description of all the fields one comes across while creating a rebate agreement type. The path to be followed to get to the said screen is:

IMG --> Sales & Distribution --> Billing à Rebate processing --> Rebate Agreements --> Rebate Agreement types --> Define Agreement Types

Sl. No.





Proposed Valid from Dates

  • Specifies the beginning validity date that the system automatically proposes when you create a rebate agreement of this type.
  • If you want the system to propose the current date, leave the field blank. Otherwise, enter one of the values predefined for your system.



Proposed Valid to dates

  • Proposed value for how long a condition should remain valid.
  • The system proposes this value for the Valid to date when you create condition records.



Payment Method

  • Assign the payment method that is going to be used for rebate settlement.
  • Cash, check etc.


Default Status

  • Specifies the default status that the system automatically proposes when you create a new rebate agreement.
  • If, for example, you want to pre-release all your rebate agreements so that they can be processed in batch after their validity periods expire, you can assign the status "B" as the default. The agreements need not be released individually released for settlement.
  • If, on the other hand, you want to check each rebate agreement before it is settled, then you can leave the field blank


Condition Type Group

  • Specifies a grouping of condition types and condition tables for use during rebate processing.
  • As a rule, the condition type group consists of only one rebate condition type. However, if your rebate processing requires it, you have the following possibilities:
    i) You can assign more than one condition type to a group
    ii) You can enter the same condition type in a group more than once and use different condition tables, or key combinations, for each instance
  • This allows you to break down the rebate settlement within an agreement. Using more than one condition type within a group would allow you to post, for example, part of a rebate settlement to an account for advertising costs and part to an account for administrative costs.



Verification Level

  • The value of this field specifies how the rebate agreements totals should be displayed



Different Validity Periods

  • Controls whether condition records within a rebate agreement must have exactly the same validity period as the agreement itself.
  • If we need to vary we check this field



Manual Accruals Order Type

  • Assign Sales document type that system automatically proposes when the user performs manual posting for accruals.
  • If the business agreed to pay Rs. 2000/- to the customer for displaying the product in the showcase within specified period, then the business has to post manual accruals in rebate agreement screen. Then the system automatically creates credit memo request by using document type R4/B4 which was assigned here.
  • R4/B4 - Rebate Req. for Manual Accruals.


Manual Accruals

  • This indicator specifies that manual accruals can be posted for this agreement type.
  • It is useful to be able to post accruals manually in the following situations:
    i) Lump sum payment processing
    ii) Manual accruals correction
  • The manual accruals function allows you to carry out the following for a particular condition record in a rebate agreement:
    i) Build accruals
    ii) Reverse accruals partially or in full
  • If you want manual accruals then we check this field.



Arrangement calendar

  • The arrangement calendar defines the end of the validity period of rebate arrangements and controls their extension



Payment procedure

-          The value of this field specifies whether manual payments are allowed or not allowed for these agreement types, if they are allowed then to which extent manual payment should be allowed.
-          When manual payment is carried out, the system automatically creates a credit memo request for the specified amounts. When the system carries out final settlement, all partial payments are taken into account.




Partial Settlement

  • Assign sales document type that the system automatically uses for partial settlement.
  • The customer requests partial settlement of a rebate agreement. You specify the amounts to be paid on the manual payment screen in the rebate agreement. The system then creates a credit memo request for these amounts using the document type specified here. The request must be approved before the actual credit memo can be created.
  • R3/B3 - Partial rebate settlement request.


Reverse Accruals

  • This indicator allows the system to reverse accruals automatically at the time of settlement.
  • The system reverses accruals for the amount of the manual payment. If the cumulative accruals are not sufficient, the system reverses the accruals amount which exists.



Settlement Periods

  • Define factory calendar in which the periodic settlements can be defined and assigned to the rebate agreement.



Final Settlement

  • Assign the sales document type that the system automatically proposes for final settlement.
  • B1 - Rebate Credit memo request.


Minimum Status

  • Set the minimum status for rebate agreement for final settlement by which the system or user can understand the status of the rebate agreement.
  • Minimum value of the rebate agreement for final settlement
  • Specifies the minimum status that a rebate agreement must have before the settlement can be calculated.
  • During the processing of a final settlement, the system checks whether the rebate agreement is assigned the minimum status.
  • B - Agreement Released for Settlement.



-          Assign Sales Document type that the system automatically uses for correcting rebates.

  • B2 - Rebate Correction request