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
--
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/mapics-l.
--
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/mapics-l.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com
______________________________________________________________________
midrange.com
