Optimize MM Performance with Data Management Best Practices

  • by Kehinde Eseyin, Security Architect
  • January 14, 2010
Learn how you can increase the performance of your materials management (MM) processes and consequently the SAP ERP Central Component (SAP ECC) 6.0 system by adopting data management strategies based on best practices and performance-driven configuration settings in the areas of purchase order management; reservation and dependent requirements; and logistics information structure (S033 information structure).
Key Concept
Effective data management strategies (data prevention [avoiding updates of database tables], data deletion, data archiving, and data reorganization) play an important role in the optimization of the performance of core materials management (MM) processes and the SAP ERP Central Component (SAP ECC) 6.0 system as a whole. The goal is to ensure that database tables do not grow to the extent that performance is affected. Appropriate configuration settings can also be used to control the update of database tables with unnecessary data.

The processing of transactions in materials management (MM) generates a large volume of data and updates different database tables in the SAP system. If the growth of affected database tables is not well managed, it can lead to performance bottlenecks in terms of system slowness, prolonged response time, background job termination, or even system downtime. This can have serious implications for the business processes of an organization and possibly affect the profitability of an enterprise in the long run. You can adopt some clear-cut strategies to effectively manage data growth of database tables that are related to MM concepts such as purchase order, reservation and dependent requirements, and S033 information structure.

Purchase Order Management 

The purchase order is an important document in the procurement process. Users can create purchase orders manually or the system can create them automatically. When creating purchase orders, it is possible to copy data from preceding documents, such as a purchase requisition. When a purchase order is created, the system updates a number of database objects including tables EKKO, EKPO, EKBE, and EKKN. Tables EKKO and EKPO act as a repository for the header and item information in a purchase order. The purchase order document basically consists of the header part and the item part. The header part contains data that relates to the entire purchase order such as document number, vendor, payment terms, document date, currency, and exchange rate. The item part contains data that is specific to a particular material or service ordered such as material number, quantity ordered, price unit, material group, and delivery date.

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.