This blog is the next part of a multi-part blog series by our very own Nathan Clouse detailing some preparatory tasks that you can perform ahead of doing a database upgrade to reduce upgrade time. This information is particularly useful when preparing to upgrade from Dynamics AX 2012 to Dynamics 365 for Finance and Operations, as database size increases time needed to move files between environments and perform the upgrade steps. Look for additional releases in this series in the coming weeks!
Inventory journals clean-up
Over time, the amount of inventory posted inventory journals can grow quite large. There is typically no value in keeping these journals around for closed years. Once a year is closed, I would expect that its inventory never changes. There is a way to clean up posted journals.
Where is this in AX 2012
In Inventory Management > Periodic > Clean up, look for Inventory Journals Cleanup. This will let you clean up posted journals by type. This will first delete posted journals by type (InventJournalTable), skipping business logic and delete actions. Next, it will identify journal lines (InventJournalTrans) that don’t have journals any longer and delete those, skipping business logic and delete actions. Next, if Tag journals were deleted, it will cleanup related records in the Tag counting table (inventJournalTrans_Tag). Finally, if BOM journals were deleted, it will delete all Inventory batch merge (InventBatchJournal) records skipping business logic. I suggest you run this in batch. Note: This functionality doesn’t have a date or age filter as part of it so it will delete all inventory journals that have been posted. Run this in a test environment before trying it in Production.
Where is this in Dynamics 365 for Finance and Supply Chain
This works the same as AX 2012 and can be found in the same place.