We are almost a year post go-live with Microsoft Dynamics AX, 2012-R2. We are required to do monthly full physicals reporting. As we progress each month with running the count journals, we are experiencing count journal create times getting longer and longer. I expected this to some degree. Some information:
1) There is no modification to AX 2012 surrounding the cycle count journals.
2) We have run it both via a batch job directly on the server and via user session. Both takes awhile.
3) We do not include any 0 inventory lines, and we do include reserved material.
4) We run the journal for all items at once; do not use count groups or break it down by any other methodology.
5) Run the count journals by the on-hand option, not by item or expired batches.
6) Report is now taking >2 hours to complete; which is expected because the number of batches and transactions increases every month
My question comes to, is there any parameters to check to decrease this time frame or has anyone done any code modifications to address an issue similar? We have a SQL report that we have developed that mimics the on-hand report in AX (just with more information). A wide open run of this report doesn't take longer than 20 minutes and has the same information that is in a count journal. I would expect a count journal to work closer to 20 minutes than greater than 2 hours.
Thanks to anyone in advance that can help or provide any kind of recommendations!
