Item Key Change with existing stock

Question

Helllo, 
 I performed a key change on an item that had existing stock not realizing that key change does not affect stock. I have looked around in SQL and still see the old item code in STOCK, Neither code in ITMCOST, both codes in ITMMVT, and the new code in STOJOU. Where else should I look? Are there any sugeestions on correcting the stock info to the new item code? 
 Thank you 
 TJ

tj9000 · Answer

Fortunately, we had migrated a new test environement moments be fore performing the key change. So I was able to use that today and dig a little deeper. I exported all the IT, ST, SO and SI tables that had the item in them. Ran the key change in the test environment, and found the old code in ITMMVT, STOCK, and STOJOUVAL. Everthing else was changed to the new code. 
 >>in SQL and still see the old item code in STOCK What is the status of that old record and does the new record exist? Can you still bring either record in the user interface? >>The old record still shows in STOCK with the qtys that were there before the keychange. The new record does not show in STOCK at all. I cannot bring the old record into the user interface. X3 acts as though it does not exist. I can bring the new record, it shows no stock, but otherwise works as expected. 
 >> Neither code in ITMCOST So it didn't exist before and doesn't exist after, so that's okay? >>Correct, it did not exist before. I wasn't sure until I ran it again today in the test server. I believe that table is fine. 
 >> both codes in ITMMVT That one puzzled me most. Are the old movement records somehow inactive? >>In the controlled test, only the old code is still in the ITMMVT table. In the live system, I suspect it showed both from the before and after the key change. So it seems to work for everything except stock. If there is no stock in the item changing codes, then probably nothing to worry about. The question now is how do I get around it. I have two ideas, neither I am thrilled about, I'd rather there was something native. I'm certainly open to other ideas as well. 
 1) Do a micellanious receipt to remove all the inventory in the old code, run the key change and then do a miscellaneous receipt to put the inventory into the new code or 2) Use in lines to copy all the old code records into the new code and then delete the old code records. (I like this idea better, but it's probably riskier)

j.rodriguez · Answer

Hi, 
 I had the same issue recently, but i just look into the atabzon for the tables who have a field with the ITM/ITS/ITP datatype and checked if the values in that tables were fine. 
 I think just the stojouval table was not ok.

Sage X3

Item Key Change with existing stock

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING