Updating of Business Volume Retrospectively
Procedure
If you want to update business volumes retrospectively, you must update all information structures. Under no circumstances enter a restriction.
If you do not select the indicator, the system writes the update data created to the information structures. At the same time, the system records the successfully processed document items in an index log.
You cannot carry out a business volume update for these document items again unless you carry out a complete recompilation of business volumes for the arrangement (see
For test purposes, you can first enter a version that starts with the two characters &(. You can enter any character as the third character. You enter version 000 as the operative version.
The user parameter MCR allows you to directly access the data of this version in all list functions for business volumes (business volumes, statement of statistical data, standard analysis). To achieve this, enter the value 000 for the parameter MCR under System
You can also write the program directly to version 000. If errors occurred during processing of arrangements, these document items can be reprocessed in another program run once the errors have been corrected. Multiple updates are not possible in the case of business volumes updated retrospectively.
If documents are found to be missing, they are usually purchase orders, goods receipts, invoices, vendor billing documents, or settlement requests for which price determination was carried out before the rebate arrangement was created. In exceptional cases, the updating of business volume may not be carried out as intended. In this case, you can deselect the indicator Only retrospectively entered rebate arrangements. The system then processes all the selected arrangements.
A rebate arrangement is regarded as having been created retrospectively if its creation date is later than or the same as the valid-from date.
If this happens, the system logs the already processed rebate arrangements under the run name, so that you can continue the processing with the next rebate arrangement.
To continue an interrupted run, delete the New run indicator and enter the name of the interrupted run. Refer to the value help for the Run name field for information on any interrupted runs.
If a run is terminated prematurely, only the rebate arrangement numbers are recorded. So that you can continue the run with the same selection parameters (condition granter, for example), you should save the selection parameters in a variant.
Results
Once the program has run in full, you can obtain a log that contains the updated business volumes, and any messages that occurred, for each rebate arrangement. You can specify that the log should only contain the messages that occurred, and also define which messages are to be issued (only warnings, for example).
The analysis function enables you to evaluate the results easily. This enables you to generate a list output of all document items plus any associated follow-on documents, together with one or more notes on the course of the updating process. The list shows you which document items are contained in the document index (S111) and why updating was or was not carried out. You can also invoke the analysis function from within the list output of the Details statement function.
You can choose whether to view all documents, and their condition records, that are relevant to the rebate arrangement or only those document items for which updating has not yet been carried out. The latter are precisely those document items for which an error message has been issued or which, although they are included in the document index, are not relevant to the concrete condition record (if a requirement is infringed, for example).
If you wish to analyze the document items for which updating has just been successfully completed (no test run), choose All documents, since you have just carried out the updating for these document items.