Purpose
You can use this report to define background jobs that perform specificactivities in the rebate due list. Enter the data and time at which youwant the system to perform the job. You can also decide how many jobsthe worklist can be distrubted between and which server the system uses.
You can also use the parallel processing criterion to determine thenumber of rebate due list headers allowed per individual job. If thisnumber is exceeded, then the job is split.
The following activities are available for the rebate due list:

• Revenue display


• Partial settlement


• Final settlement


• Manual accruals


• Correction


• Retroactive settlement

You can then use the selection fields to restrict the records to beprocessed.

Integration
If, for example, you have created a rebate agreement, then all theinformation needed for this agreement is stored in the rebate due list.Changes to the agreement are also forwarded to the due list. In the sameway, during final settlement the agreement status is updated from therebate due list.

Prerequisites
For an agreement to be settled, it must be released without any errors.Unreleased agreements are automatically excluded from processing duringsettlement. If the agreement contains errors, this is generallyindicated in the error log together with the other messages issuedduring processing. The revenue display option also displays incorrect orunreleased settlement records.

Features
You can choose from the following processing types:


• Revenue display: The system displays all the records that meet
the selection criteria. Unlike the other processing types, the resultslist includes incorrect and blocked records. The payment amounts and andsales revenues displayed are determined according to the rules for finalsettlement.

• Partial settlement: The system selects all error-free and
released records that meet the selection criteria. The payment amountsare determined according to the rules on partial settlement. Negativeamounts indicate amounts paid out. Positive amounts indicate amountsclaimed back from the rebate recipient.

• Final settlement: The system selects all error-free and fully
released (for final settlement, complete with/without claim back,flagged for deletion) records that meet the selection criteria. Thepayment amounts are determined as follows:
for records released for final settlement, the payment value isdetermined according to the rules for final settlement
for records with status 'Complete without claim back', the payment valueis assumed to be zero
for records with status 'Complete with claim back', all payments alreadymade are claimed back
for records that are flagged for deletion, the payment value is zero.
Negative amounts mean that a payment has been made, positive amounts areclaimed back from the rebate recipient. During final settlement, thesystem always processes all records for the same agreement number. It isnot possible to perform a partial final settlement for an agreement. Allopen accruals are resolved.

• Manual accruals: The system selects all error-free and released
records that meet the selection criteria. The proposed accruals amountsare calculated as the difference between the existing accruals and thefinal settlement amount reached so far. A negative amount means thataccruals are being created. A positive amount means that accruals arebeing reduced.

• Correction: The system selects all error-free and released
records that meet the selection criteria. Because the system does notdetermine proposed values and requires manual input, correction cannotbe performed in a batch job.

• Retroactive settlement: The system selects all completed
recordsthat meet the selection criteria. The payment value isrecalculated in the same way as in final settlement and any remainingaccruals are resolved.

Selection
In the default data, you define what you want the system to do with theselected records. You can choose between different processing types asdescribed above.
The flag 'entire agreements' ensures that the system will processagreements with an "all or nothing" approach (i.e. it will eitherprocess all the records for an agreement, or none of them).
The date to be entered has different functions depending on theprocessing type
in partial settlement, this date is used to determine the settlementdate. If, for example, you have saved a settlement calendar thatschedules monthly settlements, and you enter 04.12.2005, then the systemdetermines the last valid settlement date for the agreement - in thiscase, 03.31.2005. The settlement date can also be used to determinewhich sales revenues were included in the settlement. The systemconsiders the sales revenues for cumulation periods that are completedon the settlement date.
when posting accruals or corrections, the date entered determines thedate on which the corresponding values are to be cumulated in therevenues.
You can use the selection variables to limit the results for yourselection.