Introduction

This document will give a structured view of how orders in CRM are archived and reloaded back into the database. The techniques explained here can be replicated to perform archiving and reloading of data corresponding to other CRM business objects with minor modifications. The business objects covered in this document correspond to sales, service, complaint and lead transactions.

Issues related to huge data volumes Today even the most modern and technologically advanced database systems can suffer from performance bottlenecks caused by large data volumes. On the application side these bottlenecks manifest themselves in the form of poor system performance and on the administration side in the form of an increased use of resources. High data volumes can also have a considerable effect on the Total Cost of Ownership of a system, in spite of falling storage prices. To avoid the negative effects of large data volumes on costs, performance and system availability, business complete data, which is data no longer needed in everyday business processes, should be removed from the database. However, simply deleting this data is not a useful option in most cases, because often times the data still needs to be available for read accesses. Therefore the data needs to be removed from the database and stored in such a way that it can still be read-accessed later.

Benefits of Data Archiving

Greater System Availability Improved Performance and Response Times Save Costs by Optimizing Your Available Resources

STEPS IN CRM ORDERS ARCHIVING 1. 2. 3. 4. Pre processing Writing to archive file Deletion from tables Reading the archived data

BASIS steps involved. Separate file system needs to setup by Basis team, Specifying Logical file name and file path File names and file paths can be client-specific (transaction FILE) or cross-client (transaction SF01). Logical file path is ARCHIVE_GLOBAL_PATH and logical file name is ARCHIVE_DATA_FILE Assign the Logical file name to Archiving object IDOC(AOBJ)

Archiving objects :Sales transaction : CRM_SALDOC Service transaction : CRM_SERORD Complaints : CRM_COMP Lead : CRM_LEAD

Use the SARA transaction, select the archiving object and click on customising. Select technical settings in the pop up window.

In the next screen select the logical file name and other options

Pre processing:For CRM order archiving the pre processing step is vital . The Pre processing involves the following steps :Step 1 : Identify the orders that are to be archived according to the business requirement. Step 2 : Fill the field Verify_date of the order with a timestamp value ( IMP : this field can never be left blank ) . Step 3 : The statuses Can be archived and Can be deleted need to be set in CRM_JEST for the orders. Use the function module CRM_ARC_SET_STATUS for this purpose as :LS_GUID-OBJ_GUID = WA_CRMD_H-GUID. LS_GUID-FLAG_ARCHIVABLE = 'X'. APPEND LS_GUID TO IT_GUID. CALL FUNCTION 'CRM_ARC_SET_STATUS' TABLES PT_OBJGUIDS = IT_GUID.

The selected orders are now ready to be written to archive file.

Both of these steps along with some necessary functionality is provided by the report Z_ORDER_ARCH_PREPROCESS .

Writing to archive file :Goto SARA (T-code) -> Enter the archiving object -> Click on Write button. Enter a Variant name and click on maintain.

Set the input values such as Transaction Type(s), Transaction Number(s), Changed at date range etc.

Save, go back. Maintain start date, time and spool parameters and Execute. This schedules a background job which can be seen by clicking on the Job button.

Go back to the initial Archive administration screen and click on Management button. The archive session would be generated in incomplete state.

Deletion. Goto SARA (T-code) -> Enter the archiving object -> Click on Delete button. In the Archive Selection select the archived package to be deleted. Maintain start date, time and spool parameters and Execute. This schedules a background job which can be seen by clicking on the Job button.

Go back to the initial Archive administration screen and click on Management button. The archive session would now be completed. Read