Techniques to Help Improve SAP CRM Middleware Load Performance
- by Karthik Kuppuswamy, Deloitte Consulting LLP
- May 31, 2011
Techniques applied to your SAP CRM middleware can help improve the performance of your system during a conversion cutover, including conversion of data between SAP systems. Find out ways to fine tune the hardware resources and use them efficiently.
When SAP CRM exchanges data with SAP ERP, middleware performance improvement can be critical for issue-free data replication. Extraction of data in the source system, posting of data in the target system, and hardware resources should be fined tuned to achieve this. If the data exchange is not handled appropriately, cutover time can be increased and system resources can be under or over utilized.
The many hurdles potentially posed by a conversion cutover include conversion of data between SAP systems in the landscape. When SAP CRM is in the landscape, SAP CRM middleware can be widely used for the exchange of data between SAP CRM and the other connected SAP systems such as SAP ERP Central Component (SAP ECC), SAP NetWeaver BW, SAP Supply Chain Management (SAP SCM), and mobile devices.
The focus of this article is on optimizing SAP CRM middleware data exchange between SAP ECC and SAP CRM systems, which if handled properly can significantly reduce the time that SAP CRM middleware replication consumes. Henceforth, in this article, SAP CRM middleware is referred to as middleware.
Middleware is used to exchange customizing, conditional, master, and transactional data between SAP ECC and SAP CRM. Customizing data (e.g., for taxes, divisions, and business partner roles customization) and conditional data (e.g., pricing conditions) are usually lower in volume and consume much less time to exchange. Usually master and transactional data such as business partners, materials, and sales documents are very high in terms of volume (in millions) and consume a large amount of cutover time.
Middleware performance issues can occur during the initial load or due to mass changes in the system. An example of a mass change when the system is live could be: A new role was added to the existing business partners in SAP CRM based on some business rule through a custom batch program that triggered replication of the business partners from SAP CRM to SAP ECC.
The performance bottleneck could possibly occur in both systems and at multiple places depending on various factors that can be broadly classified as:
Would you like to see this full item?