When we performed our month-end inventory close, it was processing for more than 4 hours. We are accustomed to completing this process in about 2 hours. Because of this expectation, a user cancelled the job after about 4 hours and began running a reversal. The reversal did not complete before the user stopped it due to it slowing-down the system to an unacceptable level. We were able to ultimately run the reversal and it appears to be successful. This month-end close was conducted just after performing a 6-month inventory count, which would naturally add more inventory transactions.
Upon doing some research, we found an article discussing the table InventSumLogTts. According to the post, this table can have a big effect on how long an inventory close takes to process. It also states that the only way to maintain this file (using standard functionality) is to run MRP before performing the close.
I am wondering two things: First, is this table truely the likely cause of our slowdown? Second, is there a better way to manage the size of this table? It doesn't make sense to me that the system would require MRP to run prior to performing an inventory close. Practically speaking, we would want to run MRP after closing inventory not before because then we have a more accurate count.
Does anyone have any guidance on this matter? Thanks in advance.
Andrew
