How about Rebate performance improvement ?
It is known that that table VBOX can with 1000 customer can become impressively huge: Up to 3 Terabyte, and up to 40 Billion records (i.e., 40.000.000.000) in total. This table can make up to 20% of the whole database size.
Do you wonder if you can provide a better performance for Rebate processing and even SD reports ? If so, I wrote text below to help you on your decision.
As of SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA, you can use the business functions available for SD, Replacement of Rebate Index ( LOG_SD_REBATE_INDEX) and also for Sales reports ( LOG_SD_REPORT_OPT ) .
VBOX contains all potentially relevant billing documents for all condition types, even if the condition record itself does not yet exist!
So how performance weights over VBOX table ?
Well, VBOX is needed for:
• Payment for retroactive settlement
• Drill down list in old rebate procedure
And VBOX is build if:
• Sales organisation is rebate relevant
• Payer is rebate relevant
• Billing type is rebate relevant
• Invoice is no rebate document
As reported in note 456458, transaction VBOF performs a pricing with pricing type 'I' in order to (re)determine the rebate conditions in all
potentially billing documents (it updates VBOX table). The reason is that if you create a rebate agreement retroactively, the corresponding rebate condition cannot exist yet in existing billing documents because Rebate Agreement did not exist yet at the time of billing. I meant Rebate document was created after billing doc creations.
By enabling LOG_SD_REBATE_INDEX (in SFW5 tcode) in The redundant status of the rebate-relevant billing documents are no longer required in table VBOX. Once the business function has been activated, no new data is entered in table VBOX.
The note below explains in details how rebate determine billing documents without an index table:
1764868- LOG_SD_REBATE_INDEX: Determination of billing document without sales index
The note below contains information on a similar business function with some differences explained:
1899128- LOG_SD_REBATE_INDEX_SBS: Replacement of rebate index VBOX as side-by-side solution
For further information on SAP HANA on ERP SD there are available the following notes:
1768031- SAP EHP 6 for SAP ERP 6.0, version for SAP HANA
1905137- FAQ: SAP HANA - Obsolete tables (It includes SD, FI and CO component areas)
1835008- Activate Additional Database Performance Optimizations for SAP ERP
Switching on Business Functions (SAP Library - Switch Framework)
Blog: Suite Optimization: SD Rebate Processing | SAP HANA