Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006955 | Openbravo ERP | 03. Procurement management | public | 2009-01-16 16:25 | 2009-02-26 11:24 |
|
| Reporter | RenateNieuwkoop | |
| Assigned To | gorkaion | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.40 | |
| Target Version | | Fixed in Version | 2.50beta | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0006955: Requisition: can enter negative quantities |
| Description | Procurement Management || Transactions || Requisition || Header >> Lines
When entering a Requisition you can enter a negative amount. This doesn't make sense to me, why would you want a negative amount on a document that is just used internal in the company.
On a Purchase Order you can enter a negative amount also, but not sure if that's used to indicate return shipment to a Vendor?
|
| Steps To Reproduce | 2.40 community version |
| Proposed Solution | Change so that only positive amounts can be entered on a Requisition |
| Additional Information | |
| Tags | commsup_sprint6 |
| Relationships | | depends on | backport | 0006988 | | closed | gorkaion | Requisition: can enter negative quantities | | related to | defect | 0007698 | | closed | gmauleon | We are able to enter negative value in "Safety Lead Time" & "Time Horizon" fields | | related to | defect | 0009135 | | closed | harikrishnan | A requisition can be created with quantity 0 |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-01-16 16:25 | RenateNieuwkoop | New Issue | |
| 2009-01-16 16:25 | RenateNieuwkoop | Assigned To | => rafaroda |
| 2009-01-16 16:25 | RenateNieuwkoop | sf_bug_id | 0 => 2513496 |
| 2009-01-19 12:32 | psarobe | Status | new => scheduled |
| 2009-01-19 12:32 | psarobe | Assigned To | rafaroda => gorkaion |
| 2009-01-19 12:32 | psarobe | fix_in_branch | => trunk |
| 2009-02-16 16:57 | svnbot | Checkin | |
| 2009-02-16 16:57 | svnbot | Note Added: 0013537 | |
| 2009-02-16 16:57 | svnbot | Status | scheduled => resolved |
| 2009-02-16 16:57 | svnbot | Resolution | open => fixed |
| 2009-02-16 16:57 | svnbot | svn_revision | => 13237 |
| 2009-02-19 12:52 | gorkaion | Tag Attached: commsup_sprint6 | |
| 2009-02-20 10:05 | sureshbabu | Status | resolved => new |
| 2009-02-20 10:05 | sureshbabu | Resolution | fixed => open |
| 2009-02-20 10:05 | sureshbabu | Note Added: 0013807 | |
| 2009-02-23 11:54 | gorkaion | Status | new => scheduled |
| 2009-02-23 11:55 | gorkaion | Status | scheduled => resolved |
| 2009-02-23 11:55 | gorkaion | Resolution | open => fixed |
| 2009-02-23 11:55 | gorkaion | Note Added: 0013911 | |
| 2009-02-23 18:04 | jpabloae | Note Deleted: 0013911 | |
| 2009-02-23 18:05 | gorkaion | Note Added: 0013967 | |
| 2009-02-24 12:16 | rafaroda | Relationship added | related to 0007698 |
| 2009-02-26 11:24 | sureshbabu | Regression testing | => No |
| 2009-02-26 11:24 | sureshbabu | Status | resolved => closed |
| 2009-02-26 11:24 | sureshbabu | Note Added: 0014088 | |
| 2009-02-26 11:24 | sureshbabu | Fixed in Version | => trunk |
| 2009-05-25 10:08 | rafaroda | Relationship added | related to 0009135 |
|
Notes |
|
|
(0013537)
|
|
svnbot
|
|
2009-02-16 16:57
|
|
Repository: openbravo
Revision: 13237
Author: gorkaion
Date: 2009-02-16 16:56:57 +0100 (Mon, 16 Feb 2009)
Fixed bug 6955. Modified the column definition in the application dictionary to set a minimum value of 0 to the quantity and quantity order.
---
U trunk/src-db/database/sourcedata/AD_COLUMN.xml
U trunk/src-db/database/sourcedata/AD_FIELD.xml
---
https://dev.openbravo.com/websvn/openbravo/?rev=13237&sc=1 [^]
|
|
|
|
|
|
Instead of validating it on page level, it's better to validate it in field level (lost focus) |
|
|
|
|
The issue is correctly fixed.
Please log a new Feature request asking to enable the validation of numeric ranges in the field. |
|
|
|
|
|