Consolidate inventory transactions
Over time, the Inventory transaction table grows exponentially and consumes storage space, which gradually results in performance issues when you run queries against the table. To avoid these performance issues, you can use the optional feature from Supply Chain Management that consolidates inventory transaction data. When you consolidate the transactions, the system moves inventory issue and inventory receipt transaction data to separate summarized tables.
Before you consolidate inventory transactions, you should consider the following business scenarios because they're affected by the operation:
When you audit inventory transactions from related documents, such as purchase order lines, the system consolidates the transactions. To access the consolidated transactions, go to Inventory management > Periodic tasks > Clean up > Inventory transactions consolidation.
You can't cancel inventory closing for consolidated periods. Before you can cancel an inventory closing, you must reverse the relevant period's inventory transaction consolidation.
You can't run standard cost conversion for consolidated periods. Before you can do standard cost conversion, you must reverse the inventory transaction consolidation for the relevant period.
Inventory reports that are sourced from inventory transactions are affected when you consolidate inventory transactions. These reports include the inventory aging report and inventory value reports.
Inventory forecasts might be affected if you run them during the time horizon of consolidated periods.
After you turn on the Inventory transaction consolidation feature in the Feature management workspace, you need to meet the following criteria before you consolidate transactions:
The ledger period must be closed.
You must run inventory closing on or after the to-period date of the consolidation.
The period must be at least one year before the from-period date of the consolidation.
No existing inventory recalculations should occur.
To consolidate inventory transactions, follow these steps:
Go to Inventory management > Periodic tasks > Clean up > Inventory transaction consolidation. The Inventory transactions consolidation page appears and shows a list of consolidated process records.
On the Action Pane, select Inventory transactions consolidation to create an inventory transaction consolidation.
In the Inventory transactions consolidation dialog, on the Parameters FastTab, set the following fields:
From date in closed ledger period - Select the earliest transaction date to include in the consolidation.
To date in closed ledger period - Select the latest transaction date to include in the consolidation.
Note
Only periods that meet the prerequisites are available for selection.
On the Run in the background FastTab, set up batch processing details as you require. Follow the usual steps for batch jobs in Supply Chain Management. For more information, see Set up batch jobs in finance and operations apps.
Select OK. You receive a message that prompts you to confirm that you want to continue.
Read the message carefully, and then select Yes if you want to continue.
A message appears, stating that your inventory transactions consolidation job is added to the batch queue. Now, the job starts to consolidate inventory transactions from the selected period.
For more information, see Consolidate inventory transactions.
Archive inventory transactions
Your organization also can archive inventory transactions. Over time, your organization will accumulate a significant number of inventory transaction records. While these records aren't necessary for daily operations, they can be important for activities such as historical reporting, auditing, and machine learning. However, storing these records within the active working environment can lead to higher storage costs and negatively impact system performance and usability.
This feature allows your organization to use an archival framework to archive this historical inventory transaction records based on specific rules. Once archived, the records are removed from the active environment and stored in a data lake managed by Dataverse. This helps improve system performance and reduces operating costs. Despite being archived, the records remain accessible in a read-only format, ensuring they're still available for reporting, auditing, and other purposes when needed.
Administrators can define logical rules to manage when and how records are archived, ensuring that only the necessary data is moved out of the active environment. These archived records continue to be available for long-term needs, such as legal claims, historical analysis, and machine learning, while maintaining the efficiency of the system's day-to-day operations.