• Subject: RE: Unit of measure conversions..
  • From: Brad Cork <BCork@xxxxxxxxxxxx>
  • Date: Mon, 22 Dec 1997 06:31:42 +1000

We have a similar problem.  

I think it partly revolves around the problem that you can't define a
unit of measure as a discrete unit.  

For example in the steel industry our purchase units are in Tonnes but
the others are in Sheets.  For us, you can never sell part of a sheet,
it must always be a whole number.  If you could tell it that sheets must
always be a whole number it would help a lot.

We have the same problem when we invoice as well (especially if selling
in sheets and invoicing in Tonnes or vice-versa).


   *
   /\    Thanks,
  //\\   Have a great day,
 ///\\\  Brad Cork.
////\\\\ I.T. Manager
  ||||   Sheet Metal Supplies
        Merry Christmas .....

Phone:  02 9709 5000  
Fax:            02 9707 9196
Mobile:         0412 250 142

"I.T. - Making your life easier."



> -----Original Message-----
> From: Rob Rogerson [SMTP:rogerson@interlog.com]
> Sent: Saturday, December 20, 1997 10:54 PM
> Subject:      Unit of measure conversions..
> 
> I wondered if any one else was experiencing the same problem with
> conversions as us.
> 
> It is not unusual to have the following situation:
> Purchasing unit of measure is dozens.
> Stocking unit of measure is eaches.
> Issuing unit of measure is 3's(hereby called P3's).
> 
> In the parts file (INP35) these units of measures are entered along
> with their conversion factors.
> Item     Purchase Unit  Stck->purch  Stock Unit  Issue Unit
> Issue->Stock 
> PNUM35   PUNT35         SPCF35       SUOM35      ISCF35      ISCF35 
> -------  -------------  -----------  ----------  ----------
> ------------ 
> 2135P3   DZ             12.00000     P1          P3          .33333  
> 
> This causes the following problem to exist.  If there are 3 eaches in
> stock then how many P3's do we have.
> 3 * .33333 =   0.99999
> 
> JBA usually tracks quantities to 3 or 5 decimal places.  This causes a
> problem because then conversion does not work out to a whole number.
> In purchasing, where items are normally ordered in dozens but received
> in eaches, this causes major havoc since the receiver always is
> receiving a whole number yet the system is telling him that he must
> account for a fraction of a whole number.
> 
> We have fixed these problems at our sight but since we are upgrading
> to 3.5 -> 3.5.1 we will have to fix these problems again.  Is there
> any one else out there with the same issues?  I have tried to convince
> JBA that if you have 3 eaches of an item it follows that you have 1 of
> the item if sold in 3s but JBA still contends that the system is
> correct and really there are only  0.99999 of the item.
> 
> One of JBA problems I have found is that the software is being
> designed by programmers not business analyst.  What works great for a
> programmer may not be a realist business practice.
> 
> 
> Robert A. Rogerson            
>               
> IS Software Ltd.              
> 41 - 180 Forum Drive, Phone:  (905)507-1089
> Mississauga, Ontario, Canada  Fax:    (905)507-9351
> L4Z 3Y2       Email:  rogerson@interlog.com
> 
> +---
> | This is the JBA Software Users Mailing List!
> | To submit a new message send your mail to "JBAUSERS-L@midrange.com".
> | To unsubscribe from this list send email to
> JBAUSERS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: doug333@aol.com.
> +---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to "JBAUSERS-L@midrange.com".
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---


This thread ...


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

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