Description
This program simulates update for one correction order (complaint orreturn) and creates an update log.
The program does not check whether the key figures for the selectedcorrection order have already been taken into account in the statisticsdatabases, and this is also not technically possible since it cannot beseen from the order. However, this is unimportant in a simulation;processing takes place as if the selected order had been created in thesystem.
The function can be used for the following purposes:

• To check your customizing settings for updating an existing correction
order

• To check why a correction order did not trigger an update

Note
Existing update logs will be overwritten.

Output
The program outputs the new update log. The log contains a list of allupdates (with information structure / update group) triggered by thecorrection order.
To analyze a particular update, position the cursor on the appropriateline and choose 'Details'. This function displays all data relevant tothe business transaction.
According to your definition of the update rules, the program displaysan overview of the key figures that were to be updated from thedocument. The following information is displayed for each key figure:


• Content (updated value of key figure):

'No update' means that no update took place, for example because arequirement was not met. In this case, the details screen provides youwith a further analysis option: Position the cursor on the line youwant to analyze and choose 'Key figure' or 'Features'. The details scre
en contains information on the source data of the document for update.

• O/N stands for Old/New and indicates whether the update procedure is
creating or changing data.
If a document is created in the application, new update transactionsare created.
If a document is changed, the update triggered by creation must becorrected. In a first step, the update triggered is posted negatively.This posting is marked as 'Old' in the overview. In a second step, thenew constellation is updated in the transaction as with creation andmarked as 'New' in the overview.

• The next column displays the hierarchy level of the document that
triggered the update (e.g. item, schedule line).