ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Items >> Changing Cycle Codes
http://www.istechforum.com/YaBB.pl?num=1297139244

Message started by newline on 02/07/11 at 21:27:24

Title: Changing Cycle Codes
Post by newline on 02/07/11 at 21:27:24

I've used UT-K-B to do a global replace on cycle codes to make them all blank as we want to assign completely new codes.

In maintain database the Cycle field in MTIMCSTR is now showing blank on everything as I woul expect.

But in Inventory Inquiry and Enter Inventory screens I can still see the old codes in the 'Cycle Code' field.

If I go in through Enter Inventory and change the code it comes out correctly.

Do I need to do a global replace somewhere else as well to blank them all out?

Help!

(Using EVO update 1/22/10, PSQL10)

Title: Re: Changing Cycle Codes
Post by Lynn_Pantic on 02/08/11 at 18:47:00

The Cycle code is now stored in MTICMSTR file, MTIC.PROD.VEND[8]. It was moved when we changed from 1 to 4 character.

Title: Re: Changing Cycle Codes
Post by newline on 02/08/11 at 21:06:32

:) Thanks - that worked

Title: Re: Changing Cycle Codes
Post by newline on 02/13/11 at 14:25:34

OK - so now I've got all the old cycle codes out:

Is there any quick way to load the new ones?

I can't see that the field MTIC.PROD.VEND[8] is avavilable for me to override if importing inventory (System Manager DE-B)

I can see all 12 fields for specifications but not 8 for vendor.

Is there a way to import the MTICMSTR (or MTICEMTR and then transfer) file from a CSV file that will include this MTIC.PROD.VEND[8] filed or do I have to load them all manually?

(Using EVO update 1/22/10, PSQL10)

Title: Re: Changing Cycle Codes
Post by GasGiant on 02/14/11 at 05:57:07

We imported all new cycle codes in July using DE-B. Has this been broken by an update since then? I thought the move from 1 to 4 characters was further back.

Title: Re: Changing Cycle Codes
Post by newline on 02/16/11 at 13:27:39

My DE-B runs bkdeb.run.

Is there a T6 or T7 file it should be calling instead?

Is this why I can't see any fields that relate to MTIC.PROD.VEND [8] ?

Title: Re: Changing Cycle Codes
Post by dameng on 02/16/11 at 18:17:36

using DE-B you utilize the Cycle Code field reference to your import. the programmer should have already fixed this program to have that data then be stored in the MTIC.PROD.VEND[8] field.

you could as a back up, if you are not using #3 Vendor Part# is put your cycle codes there, and then run a SQL statement, to copy those values into their proper place.

but i do believe, the DE-B will already have the Cycle Code field going to the Vend[8] field for you and you don't need to do anything different.

hth

Title: Re: Changing Cycle Codes
Post by GasGiant on 02/17/11 at 05:44:39

DE-B is still calling BKDEB.RUN here and the import of cycle codes went to the right place back in July.

We do weekly cycle counts and have it split into A, B, C over 48 weeks. Our 3-digit codes (A01 - A12, B01 - B24, C01 - C48) were imported for over 1000 items in early July when we were on the Spring update, one version back from where we are, now.

Title: Re: Changing Cycle Codes
Post by newline on 02/17/11 at 13:36:03

Now I get it - if I'd just used DE-B to update the whole lot (including blanks) instead of wiping them all out in the first place I would never have even realised it was stored in VEND[8] rather than the cycle code field and I would've been less confused.

So now, when I get a chance to get everyone out of EVO, I will just carry on with DE-B to do the update (putting the cycle code in what appears to be the cycle code field in DE-B but really will update VEND[8]) and all will be right with the world.

Thanks for all your help :)