"The greater the obstacle, the more glory in overcoming it."
-Moliere
|
|
|
|
April 29, 2009
Issue 22
Greetings!
We are getting closer to releasing Component Exchange. It will be the best service of its kind. It will help you sell excess inventory and find additional low cost sources and hard-to find components.
I want thank everyone who submitted a list of components to sell. If you haven't yet, its not too late, we are still accepting lists for the BETA release. If you have excess inventory to sell, please email me your lists as soon as possible.
This issue of ManEx Minute is hopefully the first of many when we get to present the suggestions and writings of others. Paul Laskow from Advanced Business Advisors prepared the article for this week. It addresses an issue I have been asked many times. I hope you find it very informative and helpful. If you would like to publish an article, please submit your idea for review.
As always, we look forward to your participation and feedback as you gain new insights and become a more effective provider of Electronic Manufacturing Services.
Sincerely,
David Sharp
ManEx, Inc.
|
 Guest Article - Inventory Management
|
|
Customers using different part numbers to identify the same part
|
BY Paul Laskow
Often, different engineers within a company will use the same part for different designs, but rather than use an existing part number, they create a new and unique part number each time.
To keep MRP and purchasing clean and accurate, ManEx allows one customer part number for each customer under each internal part number.
What is the best way to keep inventory records clean and concise?
|
Business Case Solutions
|
Many systems require users to create a new internal part number to cross reference back to the customer part number. This increases the part number count and doesn't add significant functionality.
Others use the note field to include the cross reference information, but no database information is created and the data cannot be sorted or searched. |
ManEx Case Solution
|
Although there is more than one way to address this problem in ManEx. This article describes my recommended solution:
|
|
|
|
