Good Day Lissette ( nice name):
Do they want to "rename" the Part#, or the Description?
If you change the Part#, you will loose all its history - usage,
PO's, BOM's, vendors, etc.
Why? Any chance you can accomplish what they want another way?
Does it have to appear that way everywhere or just a few reports
that could be rewritten?
Is it really ALL parts or just some?
M2K had fields like: Synonym and Supersede, etc - putting in that
number causes the original to come up. Could that system be used?
Is there an existing field ( Extended description, long part#, etc),
or a user_Defined_field, that could be used to store the information?
If they just want to put in groups, then use a Group code in some
field.
len.hartka@...
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of liss_c
Sent: Wednesday, December 23, 2009 1:30 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Reimplement purchased parts
I am having the same problem on our end. We set up all our parts and new
managemenet is needing to rename the parts, which means we have to
inactivate the parts and create new ones.I've heard from Epicor we could
use their Service Connect and transfer new data into the system but
that's not a cost effective alternative. I am currently requesting a
quote to see if we will purchase service connect for 18K or just use the
service one time for this purpose.
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"mmcwilliams22" <mmcwilliams22@...> wrote:
& they would like to completly change the part number scheme.
[Non-text portions of this message have been removed]
Do they want to "rename" the Part#, or the Description?
If you change the Part#, you will loose all its history - usage,
PO's, BOM's, vendors, etc.
Why? Any chance you can accomplish what they want another way?
Does it have to appear that way everywhere or just a few reports
that could be rewritten?
Is it really ALL parts or just some?
M2K had fields like: Synonym and Supersede, etc - putting in that
number causes the original to come up. Could that system be used?
Is there an existing field ( Extended description, long part#, etc),
or a user_Defined_field, that could be used to store the information?
If they just want to put in groups, then use a Group code in some
field.
len.hartka@...
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of liss_c
Sent: Wednesday, December 23, 2009 1:30 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Reimplement purchased parts
I am having the same problem on our end. We set up all our parts and new
managemenet is needing to rename the parts, which means we have to
inactivate the parts and create new ones.I've heard from Epicor we could
use their Service Connect and transfer new data into the system but
that's not a cost effective alternative. I am currently requesting a
quote to see if we will purchase service connect for 18K or just use the
service one time for this purpose.
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"mmcwilliams22" <mmcwilliams22@...> wrote:
>Controller set up our parts. Now we have a new people in both positions
> When Vantage was set up originally our Purchasing Manager, &
& they would like to completly change the part number scheme.
> I know we can inactivate the old parts & create new ones, but is therea cleaner way to change all the old numbers to new ones?
>This e-mail and any attachments may contain proprietary and/or confidential information. If you are not the intended recipient, please notify the sender immediately by reply e-mail or at 410-472-2900 and then delete the message without using, disseminating, or copying this message or any portion thereof. With e-mail communications you are urged to protect against viruses.
[Non-text portions of this message have been removed]