Data for completed transactions can be deleted from the system without being archived if you do not require the data for further analyses. The areas listed below result in data being generated that does not have to be archived.

How often you run the deletion program depends on the volume of data you want to delete in the individual areas. If you have a large number of articles and stores, the volume of data generated can be very high in the Allocation, Merchandise Distribution, POS Interface and Replenishment areas in particular.

Notes:

• Programs for which no transaction is given can be executed by choosing System ® Services ® Reporting.
• For transactions belonging to a module pool, there is no information in the program column, as a module pool is not a program that can be executed.
• If it is not possible to select several objects, you delete the objects individually online.

You should re-organize (note 16083) the following data at regular intervals. When doing so, use the following job names as they can be used to check if the jobs have already been active in your system:

• Administration Data for Background Jobs
  Program: RSBTCDEL
  Re-organized tables: BTC*
  Path for accessing files: /usr/sap/SID/SYS/global/<client>JOBLG
  Job scheduling: Daily (with variants)
  Recommended job name: SAP_REORG_JOBS
• Spool Data and Administration Data for Spool Jobs
  Program: RSPO0041
  Re-organized tables: TSP*
  Path for accessing files: /usr/sap/SID/<instance>/data
  Job scheduling: Daily (with variants)
  Recommended job name: SAP_REORG_SPOOL
• Administration Data for Batch Input
  Program: RSBDCREO
  Re-organized tables: BDC* and APQ*
  Path for accessing files: /usr/sap/SID/SYS/global
  Job scheduling: Daily (with variants)
  Recommended job name: SAP_REORG_BATCHINPUT

• Runtime Statistics for Background Jobs
  Program: RSBPSTDE
  Re-organized tables: BTCJSTAT*
  Path for accessing files: Not specified
  Job scheduling: Weekly (with variants)
  Recommended job name: SAP_REORG_JOBSTATISTIC