Our guide will share which questions you need to ask at each stage of the ERP search and evaluation process, from which partner to choose to what to prepare for during and after implementation to how your industry impacts your decision.
Improving Microsoft Dynamics Performance: Cleanup Jobs
Cleanup jobs in Dynamics AX 2012 can help delete old data that is not needed anymore, and this reduction in database size can improve performance.
In Dynamics AX 2012, cleanup jobs are available across various modules to run manually or in a batch mode. It is important to note that these jobs should be run after enough analysis determines that the business doesn’t need this data in the future. Please be sure to discuss with business management before deleting old data used in transactions that is not required any longer.
Dynamics AX 2012 adds data to various tables for staging/intermediate purpose and this staging/intermediate data can be deleted once the transaction has been posted such as Sales update history, Purchase update history data.
Here is the list of cleanup jobs available in Dynamics AX 2012 along with brief descriptions. All of these cleanup jobs are available in module > Periodic > Cleanup section
|General Ledger||Clean up ledger journals||It deletes general ledger, accounts receivable, and accounts payable journals that have been posted. When you delete a posted ledger journal, all information that’s related to the original transaction is removed. You should delete this information only if you’re sure that you won’t have to reverse the ledger journal transactions.|
|Procurement and sourcing||Purchase update history cleanup||It deletes all updates of confirmations, picking lists, product receipts, and invoices generate update history transactions|
|Procurement and sourcing||Delete requests for quotations||It deletes requests for quotation (RFQs) and RFQ replies. The corresponding RFQ journals are not deleted, but remain as a record in the system.|
|Production control||Clean up registrations||Registrations can accumulate in AX over time, and can reduce the performance of the application. Therefore, it is recommended to clean up old registrations periodically. The clean-up function does not delete data that is not processed. Make sure that you do not delete registrations that may be required later for documentation purposes.
Old registrations can be removed in the following ways:
· These can be deleted.
· These can be exported to a file.
· These can be transferred to an archive table.
|Production control||Archive future registrations||It is used to remove future registrations from the raw registrations table.|
|Production control||Production journals cleanup||It is useful to delete old or unused journals to reduce demand on system resources and improve performance|
|Production control||Production orders cleanup||It deletes production orders that are ended. Last date can be selected until production orders are ended.|
|Warehouse management||Work creation history purge||This is used to delete work creation history records from WHSWorkCreateHistory table based on number of days to keep the history provided on dialog|
|Warehouse management||Containerization history purge||This is used to delete containerization history from WHSContainerizationHistory table based on number of days to keep the history provided on dialog|
|Warehouse management||Wave batch cleanup||This is used to clean up batch job history records related to Wave processing batch group|
|Warehouse management||Cycle count plan cleanup||This is used to clean up batch job history records related to Cycle count plan configurations|
|Warehouse management||Mobile device activity log cleanup||This is used to delete mobile device activity log records from WHSMobileDeviceActivityLog table based on number of days to keep the history provided on dialog|
|Warehouse management||Work user session log cleanup||This is used to delete work user session records from WHSWorkUserSessionLog table based on number of hours to keep provided on dialog|
|Sales and marketing||Delete orders||It is used to delete selected sales orders|
|Sales and marketing||Delete quotations||It is used to delete selected quotations|
|Sales and marketing||Delete return orders||It is used to delete selected return orders|
|Sales and marketing||Sales update history cleanup||It is used to delete old update history transactions. All updates of confirmations, picking lists, packing slips, and invoices generate update history transactions. These transactions ca be viewed in the History on update form. History transactions can be deleted that are generated with or without errors.|
|Call center||Delete orders||It is used to delete selected sales orders|
|Call center||Delete quotations||It is used to delete selected quotations|
|Call center||Delete return orders||It is used to delete selected return orders|
|Call center||Sales update history cleanup||It is used to delete old update history transactions. All updates of confirmations, picking lists, packing slips, and invoices generate update history transactions. These transactions ca be viewed in the History on update form. History transactions can be deleted that are generated with or without errors.|
|Call center||Sales order purge||It is used to delete outdated sales orders created in call center. It deletes invoiced or canceled sales orders based on selected customer and last invoice date or created date provided on the dialog|
|Data import export framework||Staging cleanup||Data gets inserted in staging tables when running data migration using Data import export framework. Once data migration is completed then this data can be deleted using this Staging cleanup job|
|Inventory and warehouse management||Summation of load adjustments||WMSLocationLoad table is used in tracking weight and volume of items and pallets. Summation of load adjustments job can be run to reduce the number of records in the WMSLocationLoad table and improve performance|
|Inventory and warehouse management||Inventory journals cleanup||It is used to delete posted inventory journals|
|Inventory and warehouse management||Inventory settlements cleanup||It is used to group closed inventory transactions or delete canceled inventory settlements. Cleaning up closed or deleted inventory settlements can help free system resources.
Do not group or delete inventory settlements too close to the current date or fiscal year, because part of the transaction information for the settlements is lost.
Closed inventory transactions cannot be changed after they have been grouped, because the transaction information for the settlements is lost.
Canceled inventory settlements cannot be reconciled with finance transactions if canceled inventory settlements are deleted.
|Inventory and warehouse management||Inventory dimensions cleanup||This is used to maintain the InventDim table. To maintain the table, delete unused inventory dimension combination records that are not referenced by any transaction or master data. The records are deleted regardless of whether the transaction is open or closed.
Inventory dimension combination record that is still referenced cannot be deleted because when an InventDim record is deleted, related transactions cannot be reopened.
|Inventory and warehouse management||Dimension inconsistency cleanup||This is used to resolve dimension inconsistencies on inventory transactions that have been financially updated and closed. Inconsistencies might be introduced when the multisite functionality was activated during the upgrade process from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2012, or before the upgrade process from Microsoft Dynamics AX 2009 to Microsoft Dynamics AX 2012.
Use this batch job only to clean up the transactions that were closed before the multisite functionality was activated. Do not use this batch job periodically.
|Inventory and warehouse management||On-hand entries cleanup||This is used to delete closed and unused entries for on-hand inventory that is assigned to one or more tracking dimensions. Closed transactions contain the value of zero for all quantities and cost values, and are marked as closed. Deleting these transactions can improve the performance of queries for on-hand inventory. Transactions will not be deleted for on-hand inventory that is not assigned to tracking dimensions.|
Have more questions on how to improve Dynamics AX 2012 performance? Click here to contact someone on the Hitachi Solutions team today.