Distribution, Manufacturing, and Internet Modules

[BShockley]

So in 4.4, you cannot import into the old delete, renumber, merge files?

Wow, that's not good.

[Kerry]

i can identify with Steve's views on this subject.   I have never understood the logic of why Sage would LOCK the user out of the data entry portion of the Item Renumber/Delete/Merge utility or the A/R customer Renumber/Delete/Merge or the A/P Vendor Delete/Change.   In my humble opinion, it is more logical to allow the entry of these areas (the Data Entry portion) but lock them out of UPDATING until all users are out of the system.     In my case, every quarter I have a list of Vendors and/or Customers and/or Items that need to be renumbered or deleted or merged.  My present employer is no exception as I had the same situation with my previous 2 employers as well (but it was much easier in the earlier 3.71 versions).   As it stands now, when Month-Ends or Quarter Ends happen, I end up having to work the weekend to get these areas entered in as well as updating. It would save a lot of time if I could have already entered them in previous days.

Just my 2 cents.

Kerry

[SPyle]

BS,

I don't know about importing into the OLD files, but on 4.4 there are no Renumber files to open for VI import. 

Dawn mentioned BOI, but I don't even have that option on any of my menus.

[clfisk]

I see two issues here.

One (I'm not a VI expert but) you should be able to use VI to populate the IM_DeleteChangeItems table (I do not see it as blocked).

Two - send a request to Customer Support to have the Delete Change Programs modified so the File Locks happen on the Proceed section so you can enter data and save it to be run at your convenience (it is a simple fix).

[SPyle]

Cletis,

One:  Can you tell me the file name to import into?  When I start a VI job (new name) and try to select a file, I cannot find one that starts with IM and contains the words "DeleteChangeItems".  I do see two files that fit these paramaters in DFDM.

     If I type that file name into the VI File field, I get an error "Unable to find Business Object ........"  This error occurs for the IM_DeleteChangeItems.M4T and the associated work files.

Two-  I've discussed this at length during the CR Trial and their response was "working as designed" and "design didn't change", so we're not changing it.

I'm not pushing rocks uphill any longer, just warning others of lost functionality.

[clfisk]

Just checked and the VI issue was in 4.40 but is being corrected in Product Update.

Not sure who told you the lock could not be changed.  I say it can. The requests just has to be made.

Business Reason - So data can be setup and saved beforehand and executed during off hours.

[DFeller]

What he is saying is to use the link in my signature.  I added the idea to the feedback area; you can go there and vote on it, as well as add comments to the idea to give Sage reasons why this is important.

Dawn

[thebottomline]

Which product update is the Renumber/Delete/Merge VI issue being corrected in?  Are we going to see it in July?  I reported this issue during beta testing last January and my beta client has been waiting patiently(?) since then for this fix!  As I was told back then, they would have to key all 400 changes manually if they couldn't wait.  They will carefully consider the benefits of beta testing the next time.

[SAGEMAS90CONSULT]

Here is an update to this post, since Sage has released the product updates to allow the import of data into the IM_DeleteChangeItems table in VI. Following are the relative PU's:

Visual Integrator

New in:

Product Update 4.40.0.2

22. In Visual Integrator Import Job Maintenance, the IM_DeleteChangeItems is now available for selection.

DE 91547 PER 108867 Resolution ID 520149

Product Update 4.40.0.6

6. Visual Integrator Import Job IM_DeleteChangeItems now imports successfully without error.

DE 95653 PER 110408 Resolution ID 527467

Product Update 4.40.0.8

1. New inventory items are now imported into Inventory Delete and Change Utility when the new item is the ALIAS of the original item.

DE 96934 PER 112225 Resolution ID 537508

I just completed several VI imports into this table and processed them, and they work fine.

It must have been painful for some waiting for this, especially login name "SPyle." I felt your pain, brother. Unfortunately, the way I discovered that the table wasn't available to import into any longer, was when I was conducting a remote demonstration with a client showing them how great the VI module was and how we were going to be able to change their entire inventory item numbering system painlessly with the VI tool. To my dismay and embarrassment, as I was creating the VI job, I searched in vain for the IM_DeleteChangeItems table that was there the last time I looked in earlier versions!

I and others were very relieved to see that it was included in PU2 and working correctly in PU6.