Subsequent Updating of Business Volumes (SAP Library

Subsequent Updating of Business Volumes

Use

If you have entered arrangements or conditions retrospectively (see Subsequent Settlement: Retrospective Entry 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.

Prerequisites

A prerequisite for the subsequent update of business volumes is that the Subsequent settlement index indicator is set for all vendors concerned. If this indicator is not set, business volumes can only be compiled for documents for which an update has been carried out in the past ( Recompilation of Business Volume Data and Incomes).

In order to carry out the retrospective update of business volumes, the system must be able to efficiently access all documents that may be relevant to a retrospectively entered condition record. This is done using LIS information structure S111, the "Document index".

In the data browser (Tools ® ABAP Workbench ® Overview ® Data browser), you can check which documents are contained in the document index. Use the following procedure:

Enter table S111 and choose Table contents.

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

Enter the document number and the document item you want to look at and choose Execute.

Only if the information structure for this document contains several entries can you use reports RWMBON08, RWMBON38 and RWMBON12 to updated subsequent business volume data.

For further information on the document index, see Document Index for Retrospective Business Volume Update.

Features

There are two ways of carrying out the subsequent update of business volumes, and three reports can be used:

Subsequent business volume update using reports RWMBON08 and RWMBON38 (compile business volume data).

You use these reports to process intervals of rebate arrangements. You must process vendor and customer rebate arrangements separately using two different reports.

Subsequent business volume update using report RWMBON12 (process worklist)

You can use this report to process any number of vendor and customer rebate arrangements simultaneously. You can carry out sequential processing or, to speed up the process, parallel processing. However, if you carry out parallel processing, you need the relevant hardware resources (application servers, processors, and so on).

With all three reports, 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 system, this relates to the following information structures:

S074

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

S015

Information structure for evaluation (standard analyses, planning, and so on)

For information on how the individual reports work, see Compiling Business Volume Data (Report) and Processing a Worklist (Report).

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 likely to occur:

Example

A rebate at corporate group level has been entered for 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.

Example

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.

Example

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.