Online Tutorials & Training Materials | STechies.com
Register Login

SD Rebate Processing Interview Questions and Answers

|| 0

SD Rebate Processing Interview Questions and Answers
Stechies

FAQ on R/3 SD Rebate Processing.

1) Which important user exits exist for rebate?

Answer: The most important user exit for the volume-based rebate is user exit RV60AFZZ. This user exit is used within billing too; however, there is more information available, than during the use of the user exit within rebate processing. Thus, this user exist is run when drill-down is displayed or during the settlement of a  created rebate agreement (old rebate procedure). 

External PERFORM calls should be avoided in this user exit.

2) What do I have to know on archiving?

Answer: Depending on the number of documents to be processed or on the individual system requirements it can be necessary to archive the corresponding documents.

The following key aspect applies to the rebate processing:

No documents which are relevant for agreements which should still be settled may be archived!
Even after a successful settlement it can still be necessary to have the relevant documents in the system.Here you have to level out whether you should archive the documents at a certain time.

Why do you need the documents?

- If the agreement was set retroactively, the documents are needed to settle the agreement.
- In the old rebate procedure the drill-down is always determined using the source documents.

3) What do I have to take into account on the EURO changeover?

Answer: As of January 1st, 2002 all currencies which belong to the European Monetary Union were converted to euro. This means that rebate agreements too must be converted to Euro.If, from the validity date on, you create an agreement in an old currency (for example DEM or FFR) after January 1st, 2002, the customer will receive an error message.

What will happen with agreements that have already been created in a currency still valid (for example DEM or FFR) and that are supposed to be effective after January 1st, 2002?

For this purpose, you should use report RV15C006 to convert the agreement currency to euro.Make sure that you have implemented Notes 380512 and 397568 beforehand.After running the report the agreements are in the rebate agreement currency (Euro) and the settlement is now also carried out in Euro.

You do not change the condition master records by this procedure.They still exist in the old currency.This is necessary since otherwise the source documents and the statistic file too would have to be converted, which would lead to great efforts, as for example a release upgrade of a release 3.x to 4.x.

You do not need to change the original billing documents and the rebate documents when selecting this procedure.The statistical records also keep the old statistics currency and they are maintained with this currency.

4) How can I change a rebate credit memo for a finally settled agreement? Changing agreement?

Answer: If a final settlement shows an incorrect value you can indeed cancel the credit memo and reject the credit memo request, but the agreement gets the status 'final settlement effected' and cannot be changed anymore. In this case you only have the option to set the value of the credit memo request to zero and to generate a credit memo with the value zero.Then you can copy the old agreement and thereby create a new agreement.You create it as a rebate agreement with retrospective effect.You can now change and settle again this agreement.

B) Old rebate procedure

1) Why can sales volume display and drill-down be different?

Answer: Especially in the old rebate procedure the drill-down may differ from the sales volume displayed.

The following reasons may cause this behavior:

1) The agreement has retrospective effect.
2) User exit RV60AFZZ is used incorrectly.
3) There are different validity periods.
4) You used an improper pricing type.
5) You fully settled the agreement too early.

2) What does pricing type for volume-based rebate mean?

Answer: The billing documents are the basis for rebate processing. It is indeed possible, to determine the rebate conditions in the order, however, these orders must also be invoiced so that they become effective for rebate agreements.

You set a pricing type using the copying control.Note to always select the pricing type in that way that the rebate conditions are redefined when creating the billing document.

Otherwise, as with pricing type 'D' for example, data is copied from the sales order, but nevertheless the date FBUDA relevant for rebate is redetermined, since this date is also used for example by the tax determination. This can result in hardly comprehensible inconsistencies in the agreement, since conditions may incorrectly exist or not exist. In order to avoid this common problem, during the transfer of a billing document to accounting the system always calls pricing with pricing type I which redetermines all rebate conditions.

3) Can I cancel a rebate-relevant billing document of a finally settled agreement?

Answer: Yes, sometimes a billing document belonging to a rebate agreement is cancelled after the final settlement. In this case, the credit memo already created (and maybe already cleared) for the customer is - under the business point of view - no longer correct.

For this purpose, a control run was implemented for the old rebate procedure as of Release 4.0A.The control run causes a new final settlement under these conditions.This final settlement is compared with the existing settlement.In case of deviation, the system generates a new final settlement.

C) How can I activate the new rebate procedure?

Answer: As of Release 4.5B a new type of rebate processing was implemented.You can activate this procedure using the Customizing settings.The old procedure however still works in Releases 4.5* and higher. 

D) What are the differences between the 'Old' and the 'New' rebate procedure?

Answer:One of the main issues of the old rebate procedure were rebate agreements with retrospective effect, in particular problems with the performance and with the memory requirements for bulk data.

If you created the rebate agreements in the old procedure with retrospective effect, the relevant settlement data was always taken from the rebate initiating billing documents.This means a large performance loss compared to the option of determining the settlement data directly from the statistics in a cumulative form.

Especially the stage of the settlement is very performance-critical, since often not only one but a great number of agreements must be settled in a short period of time.

The new rebate procedure tries to make "normal" agreements from rebate agreements with retrospective effect.For this purpose, the system carries out a pricing for the billing documents that existed before the creation of the agreement.This new pricing is only called for the rebate conditions and must not result in any new net value of the billing document as these billing documents have already been transferred to accounting.

Additionally an update to the billing document is made for the documents which have been changed due to the new pricing, statistical data is updated and FI documents are created.Thereby all billing documents contain the information of the agreement and "normal" agreements are made of agreements with retrospective effect.In turn, this agreements then can be settled in less time using the statistics.

The new procedure can be activated using the Customizing settings.


Related Articles