We assigned our own part numbers to those weld nuts (and other nuts and bolts). Then, we chose to use a UD table to create a Customer Raw Material PN Cross-reference for all those nuts and bolts for which each customer has their own part number.
Then we created a Quick Search on the PartNum field of this UD table so that during MOM/BOM entry, we can enter the customer part number for the nut and our part number will populate the PartNum field.
We are on 8.03.404. I don't know if this works on 6.1.
Then we created a Quick Search on the PartNum field of this UD table so that during MOM/BOM entry, we can enter the customer part number for the nut and our part number will populate the PartNum field.
We are on 8.03.404. I don't know if this works on 6.1.
--- In vantage@yahoogroups.com, Ed Garbowski <egarbowski@...> wrote:
>
> We chose to assign our own internal part numbers to all parts and enter the individual customer part numbers in the customer cross-reference table (CustXPrt), thereby allowing demand to work properly. We are on 8.03 and unfortunately do not know if this capability exists in 6.1, but if it is available, works quite well.
>
> Thanks,
> Ed
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of wendorff1
> Sent: Thursday, March 12, 2009 7:52 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Purchase hardware, multiple part numbers for one part
>
>
> Vantage 6.1
>
> Several of our customers call out identical hardware on their prints/BOMS. We may have 3 customer parts numbers for the same purchased weld nut. Is there a way to roll the demand into one part number for purchasing?
>
> Thanks,
>
> Kelly
>
>
> ________________________________
> The information contained in this message is intended solely for the individual to whom it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the contents of this information, is strictly prohibited.
> We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>
> [Non-text portions of this message have been removed]
>