One of the things we noticed is that if a write-in, where parts are added to the inventory count in MMS301, is added during a recount then it re-uses already approved inventory count line numbers. Although atypical for things that include cyclic counting, I believe it is normal as a warehouse person to find a part that needs to be added to the existing inventory count during the second, third.. round of counting.

We created a standardized process where controllers are  Read more...hand-in-hand working with each branch's manager to solve each time this occurs. Does anyone else have this issue? It feels like the process is slowed a great deal when M3 wipes variance report records.

I created ER ID 114130 to address this issue.

Simplified version of reproduction steps:

1. Create inventory count with multiple lines. The line number is determined by the numbering series.
2. Let's say during the first count - lines 10,20,30 were not approved-status 3 but line 40 was.
3. During the second count line 10,20,30 needs to be recounted. However, an additional manually added part was added to the count. This recreates line 40 but with a new item-bin location.
4. If line 40 variance is updated during the second count, the first line 40 is wiped away permanently.

In order to prevent this our controllers extract MMS307 in between each variance report and compile a list at the end of each count. This is then handed to the auditors. I will also add that there is no issue in MWS070 and MWS068. Transactions and balance ID is updating just fine despite the overlapping count line number. However, this makes it a lot more work for our controllers the entire count process whom would've looked for a unique line number per inventory count record.

A workaround is review and save each MMS303 and MMS304 output or run a report against MITTRA-MWS070. Show less...