They're all workarounds, but I found lot management a handy one: use one lot
nr for each packing size.  You can do discrete allocations if you want a
specifice packing, you know the packaging when you do inventory, you can
(must) keep the unit the same,...

since default locations a controlled wartehouse is not a drawback,



----- Original Message ----- 
From: "Jeff Snyder" <jeffreygsnyder@xxxxxxxxxxx>
To: <mapics-l@xxxxxxxxxxxx>
Sent: Tuesday, February 20, 2007 3:41 AM
Subject: [MAPICS-L] hey group


   I am working with a customer that has a pkg situation.   they sell the
   same item no. in various pkgs, ie 1 ml, 5 ml, 10, ml etc....    they
also
   have lot control and are using all 10 characters,  any ideas of how we
can
   defferientiate the pkg size would be appreciated....additional part
number
   is not an option....we'd like to avoid using locations as pkg
info......

   any ideas would be welcome...an integrator solutions with a tag along
file
   to SLQNTY  sounds like a lot of wrap code, we'd like to avoid....

   If you have solved this or have ideas, we'd like to hear from you....


   thanks


   Jeff snyder,  CPIM
   Guide technologies, LLC



     ---------------------------------------------------------------------
-

   Want a degree but can't afford to quit? Top school degrees online - in
as
   fast as 1 year
_______________________________________________
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2022 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.