× 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.



Until now - we have had in the Customer Master ACR100 - the field Allow Cust X-Reference set to a 2 - must use Cust X-Ref.

The reason for wanting to use the EIX cross reference - even if numbers the same - Description - the IIM Item Master has our internal Description used for various internal and external reports - while the Description fields in the EIX Cross Reference can be Customer and Ship to location specific and set to what the customer requests or requires to see - (Labels, Invoicing, etc.)

What surprises me is when the Customer Master ACR100 Allow Cust X-Reference was set to a 2 - it lets you enter an exact part match in EIX Cross Reference. But when you go to enter and order in ORD700 - then tells you it cannot find the part in Cross Reference and will not let you continue. If it is going to error out in ORD - why did it let me enter it without a warning in EIX?

Also I don't understand why, when entering ORD - program wise - first look to see if record is in EIX and if not then go to the IIM -- why does it look at IIM first?

For a stop gap - this one Customer we are trying switching the ACR100 field to a 1 to allow either IIM or EIX and changing for now our Internal IIM description of the parts.

The Include Exclude stuff is a little confusing - is worded one way in ACR100 and the opposite way in EIX - but we've confirmed we're going the right direction with them.

The ACR100 being set to a 2 for all the customers was one of those fields when BPCS was set up - said to fill in that way and over the years no one had questioned it or even noticed it - just on the instructions for Customer set up to fill in that way. I'm sure there are many settings that way.

Wendy Bunch
Cost Accountant
Wabash Technologies
This is an e-mail from Wabash Technologies, Incorporated.
It is confidential to the ordinary user of the above e-mail address.
It may contain copyright and/or legally privileged information.
No other person may read, print, store, copy, forward,
or act in reliance on it or its attachments. If you received this in error, please e-mail to humanresources@xxxxxxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.