5
We have the situation that we have up to hundred containers with each up to 50 lines that get closed at the same time. Within the time of container closing there are very big blockings in “on-hand related tables” because the process of closing containers creates very long transactions.
Because we are using “Container release policy = Make available at final shipping location” the code that we want to move out of the transaction is in method WHSContainerTable.pickContainerToOrder(…).
Our current implementation is that we “disabled” the method WHSContainerTable.pickContainerToOrder(…) by overlayering and implemented CoC on WHSContainerTable::closeContainer(…) to execute the same logic as in WHSContainerTable.pickContainerToOrder(…) after closing the container.
In addition to this, we execute WHSShipmentStatusUpdater and WHSLoadStatusUpdater after moving the inventory to the final shipping location.
Because we are using “Container release policy = Make available at final shipping location” the code that we want to move out of the transaction is in method WHSContainerTable.pickContainerToOrder(…).
Our current implementation is that we “disabled” the method WHSContainerTable.pickContainerToOrder(…) by overlayering and implemented CoC on WHSContainerTable::closeContainer(…) to execute the same logic as in WHSContainerTable.pickContainerToOrder(…) after closing the container.
In addition to this, we execute WHSShipmentStatusUpdater and WHSLoadStatusUpdater after moving the inventory to the final shipping location.
STATUS DETAILS
Needs Votes