problem with differences in data and real item number

Aug 13, 2009 3 Replies

Hi



Did anyone experienced followind problem:



History of transfers does not match while comparing to number of items, For instance:



We had in database (quantity) 3 items. 3 items were sold (this data is in database - if I remember correctly tabel inventory trasfer log). However in table Item (quantity) there is still 1 item (and should be



0).

Have you met simillar problem? Perhaps hot fix could resolve that if it is combined with software.



Thank you for help in advance


Use the Item - Movement report to find the model history. Remove the date filter, and add model number or ILCode. The report will show sum of movement change that should match the current stock level, if not, change the quantity with a sql statement like:

update item set quantity=x where itemlookupcode='y'

"Adam" wrote:

Thank you for help. Unfortunately movement report shows that sum of movement does not match current stock level. Obviously the solution is updating row in database. I think this should not be done in system this way. I would like to check if there is any hotfix providing patch for this problem.

Regards

Adam

Hi,

I have met similar problem. Especially with the client who has connection from POS to the database server working over WAN. When there occurs a network problem during the transaction saving process the saved data may be inconsistent. A sales transaction must update transaction, transactionentry, taxentry, tenderentry etc tables and also change item table quantity. I've seen that in case of connection problems only some information was saved. This is also answer to "Offline Transactions - duplicated" question

18.08.2009 - RMS has problem with data consistency check. Sorry Microsoft, but seems that RMS programmers do not follow SQL Server basic rule - ACID: the ACID (Atomicity, Consistency, Isolation, and Durability) properties are a core requirement for SQL Server and other transactional, reliable database products.

Regards, Koit Lahesoo

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required