ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Items >> Inventory Screen vs Inventory Transaction Report
http://www.istechforum.com/YaBB.pl?num=1435759977

Message started by podell on 07/01/15 at 07:12:57

Title: Inventory Screen vs Inventory Transaction Report
Post by podell on 07/01/15 at 07:12:57

OK - the on hand inventory shown on the screen states 26 pieces(which is incorrect)....run the inventory transaction report - states quantity 8 pieces (correct count). We had to void an invoice for 4 pieces which would bring the correct on hand inventory to 12 - the inventory screen still shows 26...We have run rebuild stock status report - what else can we do to correct.

thank you

DBA Version 2004.1 with IS Tech Support Update 2015.1
Pervasive PSQL 11.3
EVO Version 2015.1 Build 2/9/15

Title: Re: Inventory Screen vs Inventory Transaction Repo
Post by Kelloggs on 07/02/15 at 15:09:45

What about IN-K? It will create a Inv Tran........

You can use T7JSQL.RWN to adjust the UOH with a sql script
but there is a number of tables involved

MTICMSTR
BKICMSTR

Do you use location?
Because you will have to change the quantities on BKICLOC as well.

Easier to contact isthechsupport

have fun....
Happy 4 of July,

:P

Kelloggs

Title: Re: Inventory Screen vs Inventory Transaction Repo
Post by ddlong on 07/07/15 at 07:28:36

When we have a mismatch between units on hand and inventory transaction balance, we run SMJ-C (Reconcile Inventory On-Hand) and choose whether to make UOH match current UOH or net units calculated from inventory transactions. You do have to have other users out of DBA/EVO to run SMJ-C, but it can be run in report mode at any time.

Darla Long

Title: Re: Inventory Screen vs Inventory Transaction Repo
Post by Vman on 07/09/15 at 14:00:31

Because EVO uses two different database files for inventory, they do get out of synch. SMJ-C can be used to fix this most of the time. The master level recon is similar to running Rebuild Stock Status, but does more. The transaction level one only allows you change O/H to match transactions or transactions to match O/H. This is nice if all your inventory mismatches are the same, but that's not always the case. I usually run both in report only first and see what the programs want to do. In the case of the transaction level, you can run it for one part.
In my case, there are few people who use EVO, so we don't get a lot of mismatches.