Transaction OVB3 - Rebate

[Former Member]

Hi all,

Can anyone let me know the purpose of using the Transaction OVB3 in Rebate Processing in Detail

Regards

Babu

[Former Member · Accepted solution]

hi viswatr,

this OVB3 t.code is used for updating the table called VBOX which contains fields like:

Client/Application/Table/Var.key/Serv.rendered date/sales Document/Item

this fields will get updated if you run OVB3.

OVB3 will be used for rebate index:

it is used settling retrospective rebate agreements created on a different date.

balajia

[Former Member]

Answered

[Former Member]

Hello Babu,

T Code OVB3 - Rebate is used to Reorganize of Billing Index.

The rebate index is used internally in order to settle rebate agreements that have been created retrospectively and in order to display the drill-downs, i.e. the relevant billing documents, for rebate agreements.

PRECONDITION

The rebate index should be reorganized if you change one of the following rebate processing factors:

1. Creation of new accesses for rebate processing

2. New rebate relevance of sales organizations

3. New rebate relevance of billing types

4. New rebate relevance of sold-to parties

RV15B001 is a standard ABAP report available within SAP system to create New Index for Rebate Processing.

Regards,

Rajendra

[Former Member]

f) Rebate index recompilation

I. General information

Basically, the system uses the rebate index (table VBOX) to

determine any document items that may be relevant for a rebate

condition. The index is updated when a billing document is

released to Accounting. Here, it does not matter whether a

billing document contains a rebate condition or not. The

possibility that at some point a rebate condition may exist,

which might be relevant for this document item, is the

determining factor. This behavior is necessary because the system

supports retroactive rebate arrangements. Moreover, the rebate

index is required for the drill-down.

II. When should a rebate index be recompiled?

You should only recompile the rebate index if at least one of the

following settings has changed:

- Relevance to rebate of a sales organization

- Relevance to rebate of a document type

- Relevance to rebate of a payer

- Access sequences for rebate conditions

Of course, recompilation is only necessary if the system already

contains billing documents affected by these changes.

Recompilation may also be necessary if you implement program

corrections (corrections in a note) or changes to customer

modifications (user exits, user-defined fields, requirements).

III. Handling

You can use the RV15B001 report (or Transaction OVB3) to

recompile the rebate index.

If you want to run the report in a productive system, schedule it

at a time with a lower system load (for example, at night). Since

recompilation can take a very long time, the report is configured

so that it suspends processing after a predefined maximum time

and automatically reschedules processing for the following day.

*****************************************

Notice that execution of OVB3 makes ALL the existing rebate agreements retroactive (KSPAE = 'X'), no matter the selection criteria.

This makes necessary perform VBOF for all existing rebate agreements !

This could have big impact in the production system.