ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> System Manager >> SM-J-C Benefits feed back
http://www.istechforum.com/YaBB.pl?num=1203797052

Message started by Dawn on 02/23/08 at 13:04:09

Title: SM-J-C Benefits feed back
Post by Dawn on 02/23/08 at 13:04:09

I'm trying to understand what benefits running SM-J-C will do for me. I have created multiple copies of my current company and run several different combinations of the Master and Transaction A & B to see what would happen. In all cases it changed my current on hand inventory so drastically that I have come to the conclusion that I won't run it for fear of making my inventory counts off. We do monthly cycle counting and make adjustments based on that.

What do you use it for?

Title: Re: SM-J-C Benefits feed back
Post by gtladmin on 02/25/08 at 10:42:46

Dawn,

Mostly our finance dept uses it to reconcile inventory transactions that went really goofy. They'll also use it as a sort of diagnostic tool (report mode) to see what will happen with a given issue. Of course, running in report only takes just as long as running the real deal, so they resort to this util only when nothing else will fix the problem since they basically have to kick everyone out while they run the util.

Val

Title: Re: SM-J-C Benefits feed back
Post by lmk223a on 02/26/08 at 06:59:59

Dawn wrote:

What do you use it for?

There are times when a transaction does not process completely due to a record lock or some other abnormality (i.e. power failure) or changing an item's product class from "R" to "N" where inventory count should be zero.

This results in a difference in qty between IOH (IN-A) and Inventory transactions file (IN-E). I use SM-J-C to reconcile the two.

The only downfall is that all users must be out to reconcile.

Title: Re: SM-J-C Benefits feed back
Post by Vman on 02/28/08 at 06:48:26

We have used it here when we have had some thingsgo awry with inventory. I would recommend always running it in report only mode first and then examine what it wants to change. When you try to run if for a single item or range, it still seems to grind through the whole inventory files.
Also, we had a situation once where after running it in 'make the changes' mode, it created inventory entries in locations that we had previously consolidated and deleted (i.e., querying a indivdual inventory item showed more than one location, but the location did not exist in the location master file).