FYI.
EC may use this file too, but it is also used by COM to provide alternate
item reference numbers by industry class, which is how we use the file.
(It is maintainable in COM.)
................................................................................................
Roger Blocher
Vice President of Information Systems
TECH International
P.O. Box 486
Johnstown, Ohio 43031-0486
P: 740-966-8009
F: 740-966-8090
http://www.tech-international.com
From: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>,
Date: 07/24/2013 10:57 AM
Subject: Re: [MAPICS-L] ITEMASA and PartSmart (or other Electronic
Parts Catalogs)
Sent by: mapics-l-bounces@xxxxxxxxxxxx
We don't use EC so perhaps we could use the file for our own purposes.
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of DGowen@xxxxxxxxxxxxxxxxx
Sent: Wednesday, July 24, 2013 9:52 AM
To: MAPICS ERP System Discussion
Subject: Re: [MAPICS-L] ITEMASA and PartSmart (or other Electronic Parts
Catalogs)
Item/Industry cross reference is used by Electronic Commerce if you use
that module.
From: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
Date: 07/24/2013 09:49 AM
Subject: Re: [MAPICS-L] ITEMASA and PartSmart (or other Electronic
Parts Catalogs)
Sent by: mapics-l-bounces@xxxxxxxxxxxx
Wasn't aware of the Item/Indstrusy Xref file (MBB6CPP) file, but just
looked at it and it looks promising.
We've always used the PITD1 field (Extended purchase item desc. first 40
positions) in ITEMASC as an extension for item descriptions, but the
problem at hand is we need to pare down the descriptions for PartSmart,
not append to them.
Thanks Tom.
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tom E Stieger
Sent: Wednesday, July 24, 2013 9:34 AM
To: MAPICS ERP System Discussion
Subject: Re: [MAPICS-L] ITEMASA and PartSmart (or other Electronic Parts
Catalogs)
I haven't used the Item/Indstrusy Xref file (MBB6CPP). But it seems like
that could be used for this.
Have you thought about creating an extension file through IDF with
specific PARTSMART data and relating that to the Item Master?
-Tom Stieger
IT Manager
California Fine Wire
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Burns, Bryan
Sent: Wednesday, July 24, 2013 7:13 AM
To: mapics-l@xxxxxxxxxxxx
Subject: [MAPICS-L] ITEMASA and PartSmart (or other Electronic Parts
Catalogs)
As a manufacturer, we deliver some 50,000 ITEMASA descriptions for service
parts to electronic parts catalog integrators (ARI, Pathfinders, etc.) but
the ITEMASA descriptions don't always fit into the context of the parts
catalog and its "Where Used" function. Therefore our PartSmart
administrator has to tweak them and, as a result, he would like me to
tailor all our 50,000 service part item descriptions specifically for
PartSmart, using the most generic descriptions possible.
For example, let's say we have an ITEMASA ITDSC of "HANDLE, 225 SERIES"
but it was also used on a discontinued low volume 224 series unit. A
"where used" in PARTSMART will show both usages and there'd be confusion
as to whether it's the right handle.
I get that, but on the MAPICS side of things, having just "HANDLE" show up
on a report when we could have 400 handles doesn't tell user the much.
To exaggerate this example, we could just describe everything as "PART" to
make it easy for the PartSmart administrator.
If you faced this type of thing before and have some suggestions, I'd
really like to hear them.
Thanks in advance.
Bryan Burns
midrange.com
