Number of decimals

zuccoa

Active Member
By the way of the number of decimals.

During the WorldSoftware implementation ( we moved away from BPCS a bit
more than one year ago ) we have been told by the JDE Business Partner that
supported us that the Data Dictionary links every field to a "field class"
(or something like that) and therefore the number of decimals that we
should have chosen for the "field class" (amounts, quantities, etc.) would
have applied to EVERY similar field (belonging to the same "class") in the
database.

We have chosen 4 decimals for some very accurate and little quantities that
we use in manufacturing but now we are (hardly) working with many screens
full of useless zeros and in some cases the most significant figures get
truncated !!!

My users have, at the end, more or less accepted this situation but,
honestly, I've always been wondering how a big system like WS can have such
a horrible limitation ???

Andrea Zucconi
IS Manager
TUBILUX PHARMA SPA

----------
Da: scott parker[SMTP:[email protected]]
Risposta a: [email protected]
Inviato: lunedi 6 novembre 2000 14.12
A: [email protected]
Oggetto: Re: (no text) ~~502:505

If increasing the number of decimals is what you plan on doing then make
sure that you do a where used on that field. If it is stored in any files
you will have to do a conversion.


--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Numb
er=505
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
What do you mean about:
"in some cases the most significant figures get truncated"
Which figures do you get truncated?
Could you tell me it?
there is the field class, but do you think that all the fields with tha same
'field class'have to have the same number of decimals?
Thanks,
Oriol.




!!!
 
In the Data Dictionary, if you look up the field QTYA (just an example)
you will see that it belongs to the Data Item Class of "QTYINV". Yes all
Fields that belong to this Data Item class should be defined the same.

Type . P Size . 15 Data File Decimals 00
Display Decimals . 0

JDE has a "White" paper that talks about how to go about Changing the
Display Decimals of a "Data Item Class" (QTYINV in particular)

At least that is my understanding of how Pristine JDE is.

Scott Parker
Grote Industries, LLC
mailto:[email protected]
 
Hi Andrea

The big problem with all of this is that the unit price UPRC and unit cost
UNCS fields are not redefinable as they do not belong to data item class
QTYINV or any other - instead they are fixed as 4 decimals. I guess this was
felt adequate for USD values when the software was first developed years ago
and has not changed as the product has become more internationally used. Any
changes to data items in the QTYINV class or the CURRENCY class need to take
this into account in order to get results without unacceptable rounding
errors.

Similarly field sizes on screens were defined initially to be acceptable for
USD values and so a number of leading digits were truncated, which are
however relevant for currencies such as lira and pesos. Although you are
stuck with this in standard World you can overcome it third party GUI
frontends, such as JWalk from Seagull.

Regards
Nanda

>
 
Those fields are not "Stuck" as 4 decimals. You can change them but in
order to do so you must make sure you do some data conversions. In the code
JDE (98% of the time) will move a field into a 29 digit field that has 9
decimal places before they do any math that could have a decimal place. You
do also need to watch out for custom code that does not use the JDE standard
of doing this.

Scott Parker
Grote Industries, LLC
mailto:[email protected]
 
R:Number of decimals

Many thanks to everybody for the clarifications.

Nanda, I think I'll take a look to JWalk.

Thanks again.

----------
Da: nanda[SMTP:[email protected]]
Risposta a: [email protected]
Inviato: martedi 7 novembre 2000 12.03
A: [email protected]
Oggetto: RE: Number of decimals ~~517:572

Hi Andrea

The big problem with all of this is that the unit price UPRC and unit cost
UNCS fields are not redefinable as they do not belong to data item class
QTYINV or any other - instead they are fixed as 4 decimals. I guess this was
felt adequate for USD values when the software was first developed years ago
and has not changed as the product has become more internationally used. Any
changes to data items in the QTYINV class or the CURRENCY class need to take
this into account in order to get results without unacceptable rounding
errors.

Similarly field sizes on screens were defined initially to be acceptable for
USD values and so a number of leading digits were truncated, which are
however relevant for currencies such as lira and pesos. Although you are
stuck with this in standard World you can overcome it third party GUI
frontends, such as JWalk from Seagull.

Regards
Nanda

>


--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=572
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Back
Top