Purpose
With the adjustment run for event-based deferred revenues, you canreport realised revenues if the operational system has not reportedthem.

Integration
The adjustment run creates events that are then processed by the nexttransfer run for event-based deferred revenues. (See SAP Easy Accessscreen Periodic Processing -> Closing Preparation ->Receivable/Revenue Adjustment -> Event-Based Deferred Revenues ->Transfer Run.)
We recommend that you execute the adjustment run immediately afterprocessing the transfer posting run.

Features
The adjustment run offers the following options in event 1146 for eachselected header entry:

• Report the amount still to be transferred

An entry is created in DFKKDEFREV_TRIG.

• Adjust the check date

An entry is created in DFKKDEFREV_TRIGE.

• Process manually

The user decides, for each header entry, if a new check date is set orif the amount still to be transferred is reported. You should only usethis function for test purposes; it is not suitable for processing massdata.

Example
The end of a header entry for an assignment key (DFKKDEFREV_HEAD-ENDIN ='X') is reached or the check date (DFKKDEFREV_HEAD-CHCKD) is past. Theremaining amount that is still to be transferred (DFKKDEFREV_HEAD-BETRA)is not zero.
If, for example, the amount to be transferred is reported viva theadjustment run, the remaining revenue in the 'Deferred Revenues' accountis realized with the next transfer run. If the operational system thenreported further revenue realizations in the subsequent time, thesewould be noted for documentational reasons, but these events would notlead to further transfer postings. For each assignment key, the SAPsystem prevents the total realized revenues being larger than the totalof the original deferred revenues.