Subsequent Settlement: Retrospective Business Volume Update

Subsequent Settlement: Retrospective Business Volume Update

Use

If you have entered arrangements or conditions retrospectively (see Subsequent Settlement: Retrospective Creation of Arrangements), you must retrospectively update the values for business volume achieved, so that the system takes all business volume into account during settlement accounting.

Business volume can be updated subsequently with this function.

Prerequisites

All the relevant documents must be included in the document index (LIS information structure S111). You can check this as follows in the Data Browser (Tools ® ABAP Workbench, then Overview ® Data Browser):

Enter table S111 and choose Table contents.

In field BLTYP (document category), enter value 01 (purchase order/scheduling agreement), 30 (vendor billing document) or 40 (settlement request), and in field VRSIO (version), enter LIS version 000.

Enter the document item you wish to examine in the fields BELNR (Document number) and POSNR (document item) fields and choose Execute.

This function can only process the document if the system displays several table entries. For information on how you recompile the document index, see Subsequent Settlement: Retrospective Compilation of a Document Index.

Features

The system updates the information structures of Subsequent Settlement, that is, all information structures for which active update rules exist for the update group 000029. In the standard SAP system, these are the information structures

- S074

Operative view (business volumes and income used for settlement accounting purposes)

- S015

Standard information structure for analysis (standard analysis, planning, etc., if activated by you)

You can initially carry out a test run in order to view any error messages that may be generated and correct any errors.
You can specify that the execution of the program is terminated or interrupted by a certain point in time.
If required, the system issues a log containing the business volumes that have been updated for the arrangement, and any error messages that occurred.
An analysis function enables you to generate a list output of all document items, any associated follow-on documents, and one or more notes on the course of the updating process. Among other things, this shows you which document items are contained in the document index (S111) and why updating was or was not carried out.

Activities

For information on how to carry out retrospective updating, please see Subsequent Settlement: Carrying Out Retrospective Business Volume Update.

Constraints

Because this function does not redetermine prices, does not carry out a new valuation, and does not make any changes to the document items, the following functional constraints exist:

Condition exclusions may not be processed correctly. You should therefore not work with condition exclusions if you are using this function.
The valuation of the document remains unchanged. In particular, the system does not post any provisions for accrued income.

The following examples illustrate the problems may liable to occur:

A rebate at corporate group level has been entered against condition type A001 (rebate arrangement 1), which is designed to take precedence over a condition requiring subsequent settlement belonging to condition type A002 (rebate arrangement 2) of the procuring regional purchasing organization. Since no adjustment of the document conditions takes place (in particular, no price determination) the exclusion cannot be taken into account.

The condition record A002 (rebate arrangement 2, regional incentive rebate) is included in the document conditions. A condition record belonging to condition type A001 (rebate arrangement 1, incentive rebate at corporate group level) is now subsequently determined. The business volume update for the condition record belonging to condition type A002 ought to be canceled due to the condition exclusion. It may also be necessary to reverse any posting to provisions for accrued income, re-valuate the purchasing document, and post appropriate follow-on documents. However, none of this occurs. The update remains effective despite the infringement of the condition exclusion.

The immediate vendor discount RL01 should only be valid if no subsequent rebate is granted. If such a rebate is determined retrospectively, the vendor discount ought to be canceled (new valuation, follow-on documents). The ensuing changes in the subtotals could have far-reaching effects. The vendor discount therefore remains unchanged.