|
The neatest way according to me is using is EPDM and using implementation status. If you do not like it for some reason then in descending order I would use alternatives like: user fields (PDM+), e-mail (screenless), user fields with programming (green screen) Integrator (comment file,...) a combination of the above (you don't have this only for the item type (item class, buyer, cost,..) do you?) And I will not mention the more exotic possibilities, Good luck ----- Original Message ----- From: "Bonnie Cameron" <bonnie.cameron@polarisind.com> To: <MAPICS-L@midrange.com> Sent: Wednesday, 10 July, 2002 07:47 PM Subject: Item Master Item Types > We often have the situation where the item type of a new part number is > uncertain at the time of its creation. However, Mapics requires item type > to create the new record. One of the solutions we are considering is > writing the record with a generic, unused item type....and then maintaining > it later in the release process when it is confirmed. > > Does anyone know what ramifications we could encounter by doing this -- from > a requirements, structure, etc. standpoint? > Also, does anyone know the file for Item Type in Mapics and how to maintain > -- or is it programmatically defined? > > Thank you in advance for your help! > > Bonnie Cameron > Polaris Industries > 218.463.4094 > bonnie.cameron@polarisind.com > > > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list > To post a message email: MAPICS-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mapics-l. > >
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.