What is the InventSumDelta table for?

[Justin Biggs]

In trying to resolve a problem with a modification done to our 3.0 system
(reserving stock at the warehouse level instead of the location level), I've
come across a problem with this table.

In class InventUpd_Reservation's updateReserveMore method (which has
undergone significant sys-level changes in the new version), there is a
boolean value called mustIncludeInventSumDelta. If this gets set to true,
and I don't know the reason for this, it includes a join statement to the
inventSum query that returns the quantity on hand available for reservation.
Without this join, the inventDim record for warehouse reservations is
included in the inventSum query. When it is joined with InventSumDelta, the
reservations made against the warehouse are not found.

What is the purpose behind InventSumDelta? Can I ignore it safely in this
case? What criteria determines if the flag "mustIncludeInventSumDelta" is
set to true?

--
Best Regards,
Justin

[Haugland]

The purpose of the InventSumDelta table is to avoid locking on the InventSum
table. During a transaction all inventory movements will be recorded in the
InventSumDelta table (i.e. when InventTrans is inserted or updated). When the
transaction is to be commited the method Application::ttsNotifyPreCommit is
called and the contents of InventSumDelta is added to the relevant InventSum
records. This replaces the IMTS in Ax 3.0 and 2.5 (sp?)

This avoids locking InventSum until the very last moment.

So, in answer to your question: You should use InventSumDelta whenever the
on-hand may be changed in the same transaction as the calling code.

[Justin Biggs]

Thanks Haugland, that helps a lot. I was able to figure out that the
information I needed was contained in both the inventSumSelect and
inventSumDeltaSelect. Once I figured that out, I was able to finish coding
what I needed.

--
Best Regards,
Justin