| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 81.1 | Cost/price field size will be increased in Release 1.2 | SHOTIM::COPDEV61 | Karen Underkofler DTN 269-2286 | Mon Oct 31 1988 12:14 | 9 |
|
Asterisks are displayed when a numeric field does not fit into the
screen field. The field on the database is correct - it's only
the display format that's off.
In Release 1.2, the cost/price fields have been increased to
15 digits. Figures up to $999,999,999.99 will be displayed.
|
| 81.2 | MORE THEN A SCREEN | CINEMX::COPUSER76 | Ken Segur | Mon Oct 31 1988 14:24 | 20 |
| KAREN,
I WENT ON THE BK10 AND TYPED IN THE FOLLOWING:
PART ID : 889CBAT DISTRICT CODE :
PASS DATE: AUG-1988 PLANNING GROUP:
LEVEL : SD GEOGRAPHIC AREA:
UNITS/DOLLARS: U
RESULTS,
TOTAL BACKLOG UNITS : 4
THEN USED THE SAME AS ABOVE EXCEPT UNITS/DOLLARS: D
RESULTS,
TOTAL BACKLOG $ IN THOUSANDS : 0
THIS COULD BE MORE THEN A SCREEN ISSUE.
|
| 81.3 | The MLP is retrieved from the order and its value was 0 | SHOTIM::COPDEV61 | Karen Underkofler DTN 269-2286 | Mon Oct 31 1988 15:24 | 11 |
| At the saleable level, the MLP is retrieved directly from the order
(ie the SRC backbone record). In the case you outlined, the value
for MLP was 0. The screens calculate the total units and multiply
them by the MLP contained on the record (this is so that you don't
use a value from a previous date).
You should let Judy Marino know about this problem. There may be
other cases where the MLP was loaded as zero.
|