How to Use Data Management Techniques to Turbo-Charge SD Processes

  • by Kehinde Eseyin, Security Architect
  • October 26, 2010
Learn how to enhance the performance of your sales and distribution processes along with your SAP ERP system by adopting effective data management tips and tricks based on performance- driven configuration settings in rebate processing, sales document flow, and collective processing runs.
Key Concept

Data avoidance, data deletion, and data archiving are data management techniques designed to reduce data volume, free up table space, and increase system performance without incurring unnecessary costs for additional system resources.

Transaction processing in sales and distribution (SD) generates large volumes of data that in turn automatically update database tables in the SAP ERP system, thereby making the tables too large after a period of productive use. It is important that the growth of SD tables is well controlled to prevent performance impairments associated with large data volume, such as system slowness, prolonged response time, background job termination, or system downtime.

The techniques I’ll discuss apply to all versions of SAP systems. I discuss clear-cut tips and tricks that can aid in the effective management of the database table growth as it relates to transaction processing in the following SD processes, which I chose because of the volume of data they generate:

  • Rebate processing
  • Sales document flow
  • Collective processing run

Rebate Processing [subhead 1]

Rebate processing SD allows you to give a discount to a customer based on a defined sales volume. One table that is susceptible to high data growth as it relates to rebate processing is table VBOX (SD Document: Billing Document: Rebate Index). Uncontrolled growth of this table can lead to performance degradation (e.g., slow response and system slowdown) of rebate processing functions such as billing update and rebate index recompilation. Elements such as document types, sales organizations, and customers can be defined as relevant for rebate processing, and these definitions influence how a rebate is calculated. For example, if you define that a particular billing document (such as an invoice or down payment request) is relevant for rebate processing, the system uses the value on the billing documents to adjust the sales revenue accruable to the customer. Therefore, the sales revenue is used in the calculation of the rebate for the customer.

Document items that may be relevant for a rebate condition are determined with the VBOX table. Table VBOX is updated when a billing document is released to accounting regardless of the existence of rebate conditions for the document item. This is because the SAP system supports retroactive rebate processing, which allows you to create rebate agreements for which the validity start date lies in the past.

A good data prevention strategy to control the number of entries in table VBOX is to appropriately configure the setting for the relevance of volume-based rebates for document types, sales organizations, and customers. When rebate processing is not needed, this functionality should not be activated. To activate or deactivate rebate processing, use transaction OVB0 (Billing Documents Types Overview) and check or uncheck the boxes in the Relevant for rebate column (Figure 1). 

Kehinde Eseyin

Kehinde Eseyin is a security architect. He holds a bachelor’s degree in computer science. He has about 12 years of IT security, governance framework, IS risk, and compliance experience gained by working in numerous global organizations. Over the years, he has demonstrated competencies in security design, information assurance, cyber security, data privacy, threat and vulnerability management, penetration testing, business architecture, project management, IT audit, IS controls framework, and identity and access management.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.