Distribution, Manufacturing, and Internet Modules

[obm]

We have a lot of old inventory items we would like to delete in Item Maintenance.  Because the item codes are not sequential, the utility to delete would be difficult.  Every year we purge old transactions, but the system writes an "IX" transaction when we do this.....this transaction is keeping us from deleting the item.....If you are purging old transactions, why do you write another transaction?  How can we get rid of the IX transactions?  This is a huge problem for us.

thanks for your help!

[Kerry]

I am not sure, but if you go to Inventory Setup and choose Inventory Utilies, then choose Delete/Renumber/Merge, you will be able to delete the items including those with transaction history.  However, this can only be done when Purchase Order Returns and Purchase Order Receipts and Invoicing has been updated.    

If this does not work, then one idea would be to merge all the unwanted item numbers into one item number, then delete that one item number when you can.

Hope that works...

Kerry

[BigLouie]

Most users import the listing of items they want to delete using VI and then update. If you do not own VI you can work with your reseller. They can import in their system and then copy the files to your system and you can update.

[obm]

The problem with delete and merge process is that it will delete  ALL within a range with and without transactions.  I would have to work through 18,000 items to pick and choose....tough job

[BigLouie]

*sigh* let me explain again. You build an Excel file listing all of the inventory items you want deleted. Save the file as a CSV file. Import the file into the Renumber/Merge/Delete files with the item number being BOTH the start and end number so you do not range. Then after all postings in Invoice Data Entry and PO Receipt Entry are updated you can update the utility.  It is best to work with your reseller on this since even a minor mistake in this process can totally ruin your inventory files.

[lydiadud]

I am having trouble after the upgrade to 4.4 ...it won't let you go into Delete/Change and delete anything with a history.  I have spoken with our reseller and they don't know a way around it yet??  Has anyway experienced or tried to delete once upgraded to 4.4.  It is now Delete/Change and the renumber is gone..............Any ideas????

[Heather]

Welcome to the forums!

Have you tried to access this when no one else is logged into MAS90?

I'm not using 4.4 yet, but I think I saw another post where someone was complaining about no longer being able to access Delete/Change entry while others are accessing inventory-related files in MAS90. 

I'm also guessing that "Change" is just the new name for "Renumber" & "Merge".

[Kerry]

Heather,

You are correct in your assumption.  If you choose the "Change" option and the number you are changing to already exists, then the items are merged together.  At least that is the way 4.3 works.    Also, if you use VI as Big Louie suggested for "change", then the "new item number"  will not import if it already exists and those have to be entered into the Item Renumber / Change manually.  Again, that is the way it is working in 4.3 and I've heard that 4.4 does the same.  

My 2 cents...

Kerry

** Can you tell that I've been this item merge/change route recently? 

[Kerry]

OOops ... disregard my post above.   That was with customers Delete/Change/Merge.  I am doing both inventory and customers this month-end.   My bad...

Kerry

[SPyle]

On 4.4, you cannot import into the delete/merge/change file.  Also, you have never been able to delete an item that has transaction or warehouse history.  You also cannot delete anything with a balance on hand, even if it is an obsolete you have no hope of converting to cash.

The solution to most of the above is to create a delete item.  I chose zzz-delete so it is the absolute last item in the inventory file.  I merge items that cannot be deleted into this record.  If any balance accumulates, I just inventory issue into our obsolete inventory GL account.

We've talked with Sage about the inability to import and they are supposed to be correcting that, hopefully with this or the next release.