Data Archiving in SAP CRM? Absolutely!

Archiving data from SAP environments has become standard operating procedure at a large percentage of companies today. Usually, however, the systems that become candidates for data archiving are typically SAP Enterprise Resource Planning (ERP) and SAP Business Warehouse (BW). Few think beyond that to SAP systems such as Customer Relationship Management (CRM), Supplier Relationship Management (SRM) and Financial Supply Chain Management (FSCM). One of the reasons is that, for example, CRM interfaces with other SAP systems such as ERP and BW. While all of these systems experience a buildup of data, much of CRM data becomes duplicated when it goes to ERP and BW and therefore is thought to be maintained as part of this environment. However, it is important to maintain historical data in its system of origin, the CRM solution, because the complete history detailing customer relationships reside there as well as all of the supporting information. In additional, not all CRM users have ERP access. As the data grows, the same rules apply: archive or move older data out of the production database to keep up performance and provide access to the archived data. Sales, Marketing and Service are the primary business modules that make up the SAP CRM system. The Marketing module includes campaign management.  Sales and Service track myriad business transactions such as sales orders, service requests, repairs and returns, service and sales contracts, leads, activities, and quotations. Billing may also take place through this system or in the ERP system.  All CRM modules produce data that can be deemed warm or cold as the data ages.  Every system is different and needs to be analyzed to identify large tables and appropriate archive objects; however, in most cases the sales order business transaction tables need to be managed as the central index table can grow very quickly as well as the schedule lines of the items. CRM business document message flow and middleware trace tables can also show rapid growth.  These tables are not archived but instead are deleted as a housekeeping function.  Jobs need to be run on a daily basis to keep growth under control.  An example of this housekeeping is to reorganize the middleware tables using report SM06_REORG2, and the recommendation here is that it should be scheduled daily. With all of the activity in the CRM system, it is no wonder it produces voluminous amounts of data such as IDOCs, WORKITEMs, and others, which can adversely affect system performance.  Again, best practices points to archiving the data that needs to be preserved and run a data clean up on that which is duplicated elsewhere or generally not needed again. Best practices also recommends archiving the data to control database growth and to add a solution to gain transparent access to data that may be needed for business or audit purposes in the future.  Migrating the data to an archive repository not only prevents performance bottlenecks but also supports retention and compliance policies. For more information, send an email to contact@dolphnin-corp.com or go to www.dolphin-corp.com.  

Back to Blog

Data Archiving in SAP CRM? Absolutely!

Archiving data from SAP environments has become standard operating procedure at a large percentage of companies today. Usually, however, the systems that become candidates for data archiving are typically SAP Enterprise Resource Planning (ERP) and SAP Business Warehouse (BW). Few think beyond that to SAP systems such as Customer Relationship Management (CRM), Supplier Relationship Management (SRM) and Financial Supply Chain Management (FSCM).

One of the reasons is that, for example, CRM interfaces with other SAP systems such as ERP and BW. While all of these systems experience a buildup of data, much of CRM data becomes duplicated when it goes to ERP and BW and therefore is thought to be maintained as part of this environment. However, it is important to maintain historical data in its system of origin, the CRM solution, because the complete history detailing customer relationships reside there as well as all of the supporting information. In additional, not all CRM users have ERP access. As the data grows, the same rules apply: archive or move older data out of the production database to keep up performance and provide access to the archived data.

Sales, Marketing and Service are the primary business modules that make up the SAP CRM system. The Marketing module includes campaign management.  Sales and Service track myriad business transactions such as sales orders, service requests, repairs and returns, service and sales contracts, leads, activities, and quotations. Billing may also take place through this system or in the ERP system.  All CRM modules produce data that can be deemed warm or cold as the data ages.  Every system is different and needs to be analyzed to identify large tables and appropriate archive objects; however, in most cases the sales order business transaction tables need to be managed as the central index table can grow very quickly as well as the schedule lines of the items.

CRM business document message flow and middleware trace tables can also show rapid growth.  These tables are not archived but instead are deleted as a housekeeping function.  Jobs need to be run on a daily basis to keep growth under control.  An example of this housekeeping is to reorganize the middleware tables using report SM06_REORG2, and the recommendation here is that it should be scheduled daily.

With all of the activity in the CRM system, it is no wonder it produces voluminous amounts of data such as IDOCs, WORKITEMs, and others, which can adversely affect system performance.  Again, best practices points to archiving the data that needs to be preserved and run a data clean up on that which is duplicated elsewhere or generally not needed again.

Best practices also recommends archiving the data to control database growth and to add a solution to gain transparent access to data that may be needed for business or audit purposes in the future.  Migrating the data to an archive repository not only prevents performance bottlenecks but also supports retention and compliance policies.

For more information, send an email to contact@dolphnin-corp.com or go to www.dolphin-corp.com.