Customer Item Cross Reference and Engineering Changes -- MAPICS-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Customer Item Cross Reference and Engineering Changes
From: Bonnie_Lokenvitz@xxxxxxxxxxxxxx
Date: Wed, 9 Jan 2002 10:59:55 -0600
List-archive: <http://archive.midrange.com/mapics-l/>
List-help: <mailto:mapics-l-request@midrange.com?subject=help>
List-id: MAPICS ERP System Discussion <mapics-l.midrange.com>
List-post: <mailto:mapics-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/mapics-l>,<mailto:mapics-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/mapics-l>,<mailto:mapics-l-request@midrange.com?subject=unsubscribe>


How are others handling this situation?

Our customer has an item number 78-1234 with an EC level of A.  Our item
number is 0123001
The engineering level changes to B.  We create a new item 0123002 for
various reasons (on hand/on order for
prior EC,material change,etc.).

The Customer Item Cross Reference (file MBBIREP) is keyed unique on
Company, Customer # and  Customer Item Number (field BIHJTX)  which hasn't
changed in the above scenario.

Currently industrial engineering tech enters a second record into MBBIREP
with the Customer Item Number plus
an extension to create a unique key.

Our problem is when our EDI inbound orders and outbound invoices pick up
the customer's part number we don't
have match or we send an incorrect  customer part number.

The customer service staff review the incoming orders but we have had some
bounced 810's.

Suggestions welcomed!
Thanks,
Bonnie Lokenvitz

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.