Re: Zero X One = 0.001 ?

[Kevin_Catlin@xxxxxxxxxxxx]

     CYTEC Industries V6.0.02 MM Nov cume
     
     We discovered this long ago.  The field SIL/ILREV which is used to 
     populate the G/L sales account is calculated using stocking units 
     times stocking price.  We have items that we sell in metric tons and 
     stock in pounds.  The conversion from selling to stocking sometimes 
     results in truncation of significant digits for stocking units and 
     stocking price (the working storage fields do not have enough decimal 
     places).  When one or two of these factors is truncated, the result is 
     a different product than was achieved with selling units multiplied by 
     selling price.  Thus, the invoice does not match the G/L amount.  As 
     Al rightly indicates below, the larger the conversion factor between 
     selling and stocking, the greater the error.  For some large quantity 
     invoices we saw errors greater than $100.
     
     We looked at a couple of BMRs (49229, 48972) and none fixed the 
     problem.  We sent detailed proof of the calculation error and SSA 
     never acknowledged the flaw.  We resorted to re-calculating invoice 
     amount during our G/L interface.  This was reported to SSA on incident 
     566481.
     
     Kevin Catlin

______________________________ Reply Separator _________________________________
Subject: Zero X One = 0.001 ?
Author:  BPCS-L@midrange.com at Internet
Date:    08/29/2000 1:09 AM


Al Macintyre  c¿c
MIS Manager Green Screen Programmer & Computer Janitor of BPCS 405 CD Rel-02 
running on AS/400 mixed mode V4R3 http://www.cen-elec.com Central Industries 
of Indiana--->Quality manufacturer of wire harnesses and electrical 
sub-assemblies
     
Sharing an SSA bug discovery = ROUNDING ERROR
     
We have multiple cases of plus or minus 0.001 0.002 0.00001 0.00002 that are 
inexplicable & we just had another hit, where we had sufficient audit trails 
to catch the before & after.  By mistake, billing price was zero & this fact 
was on a listing that we do before invoicing, showing details on all that was 
shipped today, but our Invoicing showed a bad price of 0.001 ... where did 
the 0.001 come from?
     
Well inside Billing program BIL522 it multiplies 
shipping net price BNET (zero in this case)
in a field 13.5 (00000000.00000) 
times
unit of measure sales conversion WKUMCN (one in this case) 
in a field 11.5 (000001.00000)
to get unit price for invoice WNET (should have been zero) 
ub a field 13.5 (00000000.00000) 
but to do this math correctly we need 24.10 work area 
(00000000000000.0000000000)
except while RPG/400 goes to 30 digits, decimals only go to 9 places.
     
This is a rounding error, compounded by numbers with absudly high # digits.
     
When my time permits I plan to look in some costing update programs to see if 
this scenario explains where they are getting these invalid fractions. 
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com. 
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner: dasmussen@aol.com
+---
Received: from unknown-27-151.cytec.com. ([204.48.27.204]) by stnt01.cytec.com
with SMTP
  (IMA Internet Exchange 3.12) id 002F54F6; Tue, 29 Aug 2000 01:46:20 -0400
Received: from mail02-ewr.pilot.net (localhost [127.0.0.1]) by
unknown-27-151.cytec.com. with ESMTP id BAA05854; Tue, 29 Aug 2000 01:42:16
-0400 (EDT)
Received: from uucphost.mcs.net (Kitten2.mcs.com [192.160.127.90]) by
mail02-ewr.pilot.net with ESMTP id BAA17040; Tue, 29 Aug 2000 01:42:16 -0400
(EDT)
Received: (from 66@localhost)
        by uucphost.mcs.net (8.9.3/8.9.3) with UUCP id AAA65688;
        Tue, 29 Aug 2000 00:32:26 -0500 (CDT)
        (envelope-from bpcs-l-owner)
X-Authentication-Warning: Kitten.mcs.net: 66 set sender to bpcs-l-owner using -f
Received: (from majordom@localhost)
        by linux.midrange.com (8.9.3/8.8.7) id AAA16355
        for bpcs-l-outgoing; Tue, 29 Aug 2000 00:10:06 -0500
Received: (from uucp@localhost)
        by linux.midrange.com (8.9.3/8.8.7) with UUCP id AAA16344
        for BPCS-L@midrange.com; Tue, 29 Aug 2000 00:10:04 -0500
From: MacWheel99@aol.com
Received: from imo-d08.mx.aol.com (imo-d08.mx.aol.com [205.188.157.40])
        by uucphost.mcs.net (8.9.3/8.9.3) with ESMTP id AAA63427
        for <BPCS-L@midrange.com>; Tue, 29 Aug 2000 00:09:53 -0500 (CDT)
        (envelope-from MacWheel99@aol.com)
Received: from MacWheel99@aol.com
        by imo-d08.mx.aol.com (mail_out_v28.15.) id i.9b.9b0be2a (17080)
         for <BPCS-L@midrange.com>; Tue, 29 Aug 2000 01:09:12 -0400 (EDT)
Message-ID: <9b.9b0be2a.26dc9f77@aol.com>
Date: Tue, 29 Aug 2000 01:09:11 EDT
Subject: Zero X One = 0.001 ?
To: BPCS-L@midrange.com (BPCS Users Discussion Group)
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: AOL 5.0 for Windows sub 120
X-MIME-Autoconverted: from quoted-printable to 8bit by linux.midrange.com id
AAB16344
Sender: owner-bpcs-l@midrange.com
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by unknown-27-151.cytec.com.
id BAA05854