Distribution, Manufacturing, and Internet Modules

[VVB]

I want to just change change a part number. Not a copy of the old part number but just replace it with the new. Can this be done? Or will it cause problems reprinting old invoices, work orders, etc?

[jnelsonut]

Under Inventory Management, Setup, Inventory Management Utilities, Item Delete/Renumber/Merge.  Do a backup first, there is no undoing this once it's done.

Welcome to the forums

Joe

Edited: You want to merge the old part number with the new.

[rgaviria]

So does this affect open sale orders and work orders?

[VVB]

What about open sales orders and BOMs?

[Heather]

I haven't done a renumber in years, but I believe it changes everything. 

Here's a suggestion -- make yourself a test company & try the renumber process there.  Check out the results & make sure you're happy with them before running this in your live company. 

Even then, still make yourself a back up first.  There are many a horror story of people accidentally merging all their items into one.  If you do that, restoring from a backup is you're only hope.

[SPyle]

It should replace all of them.  There is a report that prints that lists all of the files it updates.

I do recall it might have skipped customer last purchase history.  Not sure if that was delete, renumber or both.  (V4.05)

Whatever you want to do, work it through before you get to 4.4.  It is almost impossible to use in 4.4. because it locks the SO and PO files, so the company basically needs to be shut down just to load the file.  Also, you cannot load this file with VI which makes it more frustrating because each entry takes a couple of seconds to enter.

I'm amassing hundreds of discontinued/deleted items or changed numbers (a new fad with my suppliers) and I'll probably be looking for new software in the next year as Sage doesn't think this is an issue.

[DFeller]

Steve,

As I understand the import into delete/renumber doesn't work in 4.40?  Haven't had any customers have this issue yet.  If it doesn't work in VI, can you use BOI against it?

Dawn

[SPyle]

No, the import doesn't work because the file is not available to VI.

To clarify for the Sage monitors:  earlier versions wouldn't allow you to start the utility if others were active, but when I opened the file before they arrived to work, I could keep the file open and add items as needed.  The SO and PO files were not locked for this portion of the routine.

I haven't graduated to BOI and don't have the time to figure it out.  All this IT is just one small part of my job running my company.

[clfisk]

The only file that is locked during IM DeleteChangeItems in v4.40 is the Item Master File (CI_Item). You cannot delete/renumber items if someone is maintaining that file. It also has a Delayed start feature so it can be scheduled to run when there are no other users on the system.

I believe VI is still possible but why go to all the trouble to build the information when the main program does it.

Refer to the Help for what tables are updated via IM DeleteChangeItems.

[SPyle]

I would use VI because I have over well over 250 items to load.  Typing in an item number and waiting for MAS to add it to the file is painfully slow - like clicking on vendor from within Inventory maintenance.  Trying to type in that many items individually with the delays would probably cause me to go postal on myself.

Perhaps you don't get the delays I do because your test companies are so small.  I have over 60,000 inventory records and just opening the search window is over 15 seconds.

Locking the CI_Item file effectively locks out PO and SO, if I recall my tests.  Perhaps it was changed since the 4.4 testing?  Locking those two modules effective shuts down my company so delete/renumber is deferred.

As I said, on 4.05 and earlier, I was able to load the file as long as I logged in before others.  I could not open del/renum if others were already in SO or PO, or items were posted to receipt of goods/invoice or so invoices.  I can accept that.  And I wouldn't actually run the file until after hours because it is now a very lengthy run compared to 4.05.  I cannot see the reason to open CI_Item as LOCK to build the files; READ should be sufficient, with locking the file upon execution.  I also cannot see the reason to not allow for VI into this file.

I've thought - very briefly - of building the file through DFDM, but I don't know what support files also need to be built so caution in this regard gets the better of me.

VI is NOT possible because the file is not available when you enter VI create new import.