Introduction

Logistic processes in Exact Globe generate MRP planning records. Examples of logistic processes are sales orders, blanket sales orders, return to merchant authorization (RMA) orders, purchase orders, blanket purchase orders, return to vendor (RTV) orders, interbranch transfers, and quotations.

Over the years, as customers’ databases become larger with logistic transactions, the database actions on these records become slower. Historical records such as completed sales or purchase orders may be considered obsolete after the completion of the logistic processes over a certain period of time. In order to enhance the performance of the administration, these obsolete logistics and planning records are best deleted.

Menu path

• System/Checks/Cleanup/Logistics MRP
• System/HR & Security/User rights

What has been changed

The following changes are applicable to completed sales orders, blanket sales orders, RMA orders, purchase orders, blanket purchase orders, RTV orders, interbranch transfers, and quotations:

• The System/Checks/Cleanup/Logistics MRP menu path is added and will be  available if you have the Logistics MRP menu right.
• Correspondingly, the Logistics MRP menu right is added to the System menu rights. For more information, see Overview of User Rights.
• At System/Checks/Cleanup/Logistics MRP, you can execute the tool to clean up the records and budget entries of completed sales orders, blanket sales orders, RMA orders, purchase orders, blanket purchase orders, RTV orders, interbranch transfers, and quotations.
• Before you can start cleaning up the records and entries, you need to ensure that the prerequisites are met.
• Once the cleaning up process is successful, the records and budget entries of the completed sales orders, blanket sales orders, RMA orders, purchase orders, blanket purchase orders, RTV orders, quotations, and interbranch transfers which are generated until the specified year will be cleaned up and cannot be recovered.
  
  Note: After the clean up process, it is advisable to shrink the size of the database using Microsoft SQL Server Management Studio or Microsoft SQL Server Enterprise Manager.
  
  
• Prior to performing the clean up process, you are urged to take note of and understand the consequences that will take place when the cleaning up process is completed, as listed in the related document.
• A few functionalities are enhanced accordingly and will take effect once the cleanup process is completed.

Note: For more information about the prerequisites, cleanup tool, and the list of functionalities that are affected by the cleaning up process, see How-to: Cleaning Up Obsolete Logistic Records and Budget Entries.

Related document

• How-to: Cleaning Up Obsolete Logistic Records and Budget Entries
• Overview of User Rights