Cleanup routines in Dynamics 365 Finance and Dynamics 365 Supply Chain Management

This cleanup routine is used to periodically delete records from the EventInbox and EventInboxData tables.

Recommendation: If you don't use alert functionality, turn off the alert from the batch job.

This cleanup routine lets you delete database logs as you require. You can delete logs for specific tables, delete specific types of database logs, or delete logs based on the date and time when they were created.

Note: Records that have been electronically signed can't be deleted from logs.

By default, job history entries and related staging table data that are older than 90 days are automatically deleted (starting September 2023). To configure a job history retention period of less than 90 days, use the Execution history cleanup feature in Data management. It replaces the earlier Staging cleanup routine, which is now obsolete (deprecated).

The following tables are cleaned up:

• All staging tables
• DMFSTAGINGVALIDATIONLOG
• DMFSTAGINGEXECUTIONERRORS
• DMFSTAGINGLOGDETAIL
• DMFSTAGINGLOG
• DMFDEFINITIONGROUPEXECUTIONHISTORY
• DMFEXECUTION
• DMFDEFINITIONGROUPEXECUTION
• DMFDEFINITIONGROUPEXECUTIONPROGRESS

This cleanup routine deletes General ledger, Accounts receivable, and Accounts payable journals that have been posted. When you delete a posted ledger journal, all information that is related to the original transaction is removed.

Note: You should delete this information only if you're sure that you won't have to reverse the ledger journal transactions.

This cleanup routine sets up a batch job to clean up the email notification logs.

This cleanup routine groups closed inventory transactions or deletes canceled inventory settlements. By cleaning up closed or deleted inventory settlements, you can help free up system resources.

Don't group or delete inventory settlements that are too close to the current date or fiscal year, because part of the transaction information for the settlements are lost.

Closed inventory transactions can't be changed after they're grouped, because the transaction information for the settlements is lost.

If canceled inventory settlements are deleted, they can't be reconciled with finance transactions.

The dialog for setting up this job provides the following optional settings:

• Group settlements posted before – Enter the date before which the closed inventory transactions settlements will be grouped.
• Delete canceled settlements posted before – Enter the date before which the settlements were canceled and will be deleted.

This cleanup routine maintains the InventDim table. It deletes all existing inventory dimensions that are defined but not used in the current company. All unused inventory dimensions are permanently deleted regardless of whether the transaction is open or closed.

This cleanup routine verifies whether each InventDim record is being used in any purchase order lines, sales order lines, inventory transactions, and/or on-hand inventory records. If a reference exists to InventDim, it's checked. If it's not used, it's deleted. If the same combination of dimensions is used later, the system creates a new InventDim record with a new InventDimId value and uses this instead.

Inventory dimension combination records that are still referenced can't be deleted because when an InventDim record is deleted, related transactions can't be reopened.

Warning: This job deletes all inventory dimensions that were created during the targeted date range and which are defined but not used in the current company. Unused inventory dimensions are deleted permanently. No alert or database log is created during the process. Don't run this job without a good reason. Be sure to schedule this process to run outside of business hours.

This cleanup routine deletes closed and unused entries for on-hand inventory that is assigned to one or more tracking dimensions. Closed transactions are marked as closed and contain a value of 0 (zero) for all quantities and cost values. By deleting these transactions, you can help improve the performance of queries for on-hand inventory. Transactions won't be deleted for on-hand inventory that isn't assigned to tracking dimensions.

The dialog for setting up this job provides the following setting:

• Delete if not updated for this many days – Closed on-hand entries that haven't been updated for this number of days will be deleted (default is 7). Entries that have been changed during this period aren't deleted

This cleanup routine aggregates InventSum rows that have a quantity of 0 (zero) and cleans up records where Closed is set to True.

This routine handles scenarios where there are no more quantities in the InventSum table for a combination of inventory dimensions, but there's still a value. Although these values disappear in some cases, the current design occasionally allows values to remain.

For example, if you use batch numbers, each batch number (and the combined site, warehouse, and so on) creates a new record in the InventSum table. When the batch number is sold, quantity fields are set to 0 (zero). In most cases, the Financial cost amount and Physical cost amount fields are also set to 0 (zero). However, in standard cost revaluation and other scenarios, the field might still show some amount. This behavior is valid, and reflects the way that the system handles costs at the financial inventory level (for example, the site level).

Inventory value is determined by records in the InventSum table. In some cases, when inventory values in the past are reported, value is determined by inventory transactions (the InventTrans table). Therefore, when you run inventory value reports, the system initially looks at the InventSum table, aggregates all records to the site level, and reports the value for the item per site.

The data from the individual records at the batch-number level are never used. Therefore, this routine goes through all InventSum records, finds the records where there's no more quantity (that is, where No open quantities is set to True). Because there's no reason to keep these records, the system finds the InventSum record for the same item that has the same site, copies the values from the batch-number level to the site level, and deletes the record. Then, when you run inventory value reports, the system still finds the same correct values. Therefore, this routine reduces number of InventSum records, significantly in some cases, and can have a positive impact on the performance of any function that queries that table.

This cleanup routine deletes on-hand storage data for reports that were executed before a specific date.

The dialog for setting up this job provides the following setting:

• Delete inventory on-hand report executed before – Enter the newest date for which to keep report data. Data for reports that are older than this will be deleted.

This cleanup routine fixes inconsistent data and corrects unexpected quantities that are related to transfer orders.

The dialog for setting up this job provides the following settings:

• Recalculate transfer-related quantities – Set to Yes to recalculate and correct shipped quantity, ship remaining quantity, and receive remaining quantity values.
• Recalculate inventory transactions – Set to Yes to fix corrupted inventory transactions, such as received transfer orders that still have ordered transactions and transfer orders that are linked to completed output orders.
• Recalculate header status – Set to Yes to correct transfer orders' header status values based on their line status values.
• Recover header – Set to Yes to recover transfer orders that were unexpectedly removed even though they weren't fully received, related order lines still exist, or related inventory transactions still exist.

This cleanup routine deletes all on-order or ordered inventory transactions that link to posted or nonexistent inventory journals in the current company. You can choose whether or not to clean up orphan unposted inventory transactions without journal lines.

Warning: The inventory transactions are deleted permanently. No alert or database log is created during the process. Don't run this process without a good reason, and be sure test carefully before running it in production environment.

We recommend that you periodically clean up registrations. This cleanup routine deletes only data that has been processed.

Note: Make sure that you don't delete registrations that might be required later for documentation purposes.

Same as Production control > Periodic tasks > Clean up > Production orders cleanup.

This cleanup routine is used to delete production orders that have ended.