Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] A. Platformminoralways2020-03-10 22:022023-07-04 12:35
ReportergsuarezView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0043473: Allows decimal quantity when standard precision in UOM set to 0

DescriptionUOM for a product used in sales order is defined as UNIT and standard precision of that is set as 0 therefore the desired output is that the system allow saving the record in decimal quantity.

We have understanding that standard precision in the unit of measure window defines the logic which allows the use of the decimal number in for sale/purchase and return process.
Steps To Reproduce1- Set any UOM with standard precision to 0.
2- Choose any product with same UOM.
3- Create a sales order.
4- Create a sales order line.
5- Select that product with standard precision in UOM set to 0.
6- Set quantity with decimal, for example 1.3
7- Save the record and see that nothing error happened
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
inigo_lerga (reporter)
2020-03-18 16:21

--Test Plan Mantis--
As the F&B International Group Admin role:
  - Go to the Sales Order window and create a new record
    with any Business Partner desired.
  - Go to the Lines Tab and create a new Line with any product
    with Units as its Unit of Measure. Set the Ordered Quantity
    as 8.6
  - Save the record, Press the Book button and OK in the popup
  #Now the Ordered Quantity is saved as 9#
dmiguelez (developer)
2020-03-20 11:20

This issue has been moved to Design Defect.

It is possible, in Openbravo, to specify the number of decimal positions that should be shown in the application.
However, this can not be done per Unit of Measure.

Also, when saving the data introduced by the user in the database, there is no validation to check the number of decimal positions based on the UOM.

Solving this problem, from a Product point of view, requires a generic solution that performs this validation for any column associated with a UOM.

It would be possible to do a custom fix for a particular window, but solving this issue requires a more generic approach.

A proposal could be a new column type in Application Dictionary, that should trigger this validation.

- Issue History
Date Modified Username Field Change
2020-03-10 22:02 gsuarez New Issue
2020-03-10 22:02 gsuarez Assigned To => Triage Finance
2020-03-10 22:02 gsuarez Modules => Core
2020-03-10 22:02 gsuarez Resolution time => 1585605600
2020-03-10 22:02 gsuarez Triggers an Emergency Pack => No
2020-03-11 10:06 dmiguelez Assigned To Triage Finance => inigo_lerga
2020-03-17 08:57 inigo_lerga Status new => scheduled
2020-03-18 16:21 inigo_lerga Note Added: 0118679
2020-03-20 11:20 dmiguelez Note Added: 0118699
2020-03-20 11:20 dmiguelez Type defect => design defect
2020-03-23 09:19 inigo_lerga Assigned To inigo_lerga => platform
2020-03-23 09:19 inigo_lerga Priority high => normal
2020-03-23 09:19 inigo_lerga Severity major => minor
2020-03-23 09:19 inigo_lerga Category 07. Sales management => A. Platform
2022-02-01 08:07 alostale Assigned To platform => Triage Platform Base

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker