An alternative to a special database might be creating a "dummy" bill of
material in the ERP system that calls out one of the duplicate part nimbers
as the source for the other duplicates.  For example the BOM for part 123
would call for 1 each of part 789, part 456 would call for part 789, etc.
This would allow the MRP program to consolidate the demands while providing
a means of distributing the parts to the required kits without having to ECO
all of the drawings and schematics.

Don Vischulis
-----Original Message-----
From: TechNet [mailto:[log in to unmask]]On Behalf Of Genny Gibbard
Sent: Thursday, August 29, 2002 1:12 PM
To: [log in to unmask]
Subject: Re: [TN] Part Consolidation


Could you develop some sort of cross-reference database table that you could
interface with your system, so that part numbers 123, 456, and 789 all refer
to new part number xyz?
I am not familiar with the workings of Oracle, but our internally developed
MRP system uses a cross-reference table.

---------------------------------------------------------------------------------
Technet Mail List provided as a free service by IPC using LISTSERV 1.8e
To unsubscribe, send a message to [log in to unmask] with following text in
the BODY (NOT the subject field): SIGNOFF Technet
To temporarily halt or (re-start) delivery of Technet send e-mail to [log in to unmask]: SET Technet NOMAIL or (MAIL)
To receive ONE mailing per day of all the posts: send e-mail to [log in to unmask]: SET Technet Digest
Search the archives of previous posts at: http://listserv.ipc.org/archives
Please visit IPC web site http://www.ipc.org/html/forum.htm for additional
information, or contact Keach Sasamori at [log in to unmask] or 847-509-9700 ext.5315
---------------------------------------------------------------------------------