Split demand replenishment work from create pick work step
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| End users by admins, makers, or analysts |  Apr 1, 2019 |
Jan 27, 2020 |
Business value
This feature allows for future performance enhancements of each of the transactions. It also intrinsically reduces the impact of a potential lock, by reducing the transaction size.
Feature details
In the version 7.1 timeframe, we improved the allocation step of waving by introducing multithreading. The remainder of the steps are not currently multithreaded and run in a single long database transaction. One of the issues with optimizing the long transaction that creation of pick work represents is the fact that demand replenishment is created within that transaction. For future performance optimization purposes, we are separating the replenishment work creation step into its own thread that has its own transaction.