Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0035447Openbravo ERP03. Procurement managementpublic2017-03-07 13:512017-03-15 20:22
Reporteraferraz 
Assigned Tomcobas 
PriorityimmediateSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS30OS VersionProfessional Appliance
Product Version 
Target Version3.0PR17Q2Fixed in Version3.0PR17Q2 
Merge Request Status
Review Assigned Tomarkmm82
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression levelPackaging and release
Regression date2016-12-02
Regression introduced in releasemain
Regression introduced by commithttp://code.openbravo.com/erp/devel/pi/rev/5c95279a6932 [^]
Triggers an Emergency PackNo
Summary0035447: Not possible to create an Order from a Requisition using Requisition To Order
DescriptionNot possible to create an Order from a Requisition using Requisition To Order
Steps To ReproduceUsing F&B Admin:

- Create a Requisition for Bebidas Alegres partner
- Add a line for Agua sin Gas product and set a net unit price of 3
- Complete the requisition
- Create an order from the requisition using Requisition To Order window
- Check you get the following error: You have filled in Quantity order without selecting a corresponding UOM order , or viceversa. Fill in both fields, or leave them empty

Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 00354913.0PR17Q1 closed mcobas Not possible to create an Order from a Requisition using Requisition To Order 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-03-07 13:51aferrazNew Issue
2017-03-07 13:51aferrazAssigned To => Triage Finance
2017-03-07 13:51aferrazOBNetwork customer => No
2017-03-07 13:51aferrazModules => Core
2017-03-07 13:51aferrazRegression level => Packaging and release
2017-03-07 13:51aferrazTriggers an Emergency Pack => No
2017-03-07 13:52aferrazRegression introduced in release => main
2017-03-07 14:23markmm82Assigned ToTriage Finance => mcobas
2017-03-12 17:12markmm82Regression date => 2016-12-02
2017-03-12 17:12markmm82Regression introduced by commit => http://code.openbravo.com/erp/devel/pi/rev/5c95279a6932 [^]
2017-03-12 17:14markmm82Statusnew => scheduled
2017-03-13 01:11hgbotCheckin
2017-03-13 01:11hgbotNote Added: 0094964
2017-03-13 01:11hgbotStatusscheduled => resolved
2017-03-13 01:11hgbotResolutionopen => fixed
2017-03-13 01:11hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/123bf7a64512b73324040553df9dab7831f54c2b [^]
2017-03-13 01:13markmm82Review Assigned To => markmm82
2017-03-13 01:13markmm82Note Added: 0094967
2017-03-13 01:13markmm82Statusresolved => closed
2017-03-13 01:13markmm82Fixed in Version => 3.0PR17Q2
2017-03-15 20:22hudsonbotCheckin
2017-03-15 20:22hudsonbotNote Added: 0095292

Notes
(0094964)
hgbot   
2017-03-13 01:11   
Repository: erp/devel/pi
Changeset: 123bf7a64512b73324040553df9dab7831f54c2b
Author: Miguel <martencobasmiguel <at> gmail.com>
Date: Fri Mar 10 11:11:58 2017 -0500
URL: http://code.openbravo.com/erp/devel/pi/rev/123bf7a64512b73324040553df9dab7831f54c2b [^]

Fixes issue 35447:Error creating an Order from a Requisition To Order.

In AUM project the Constraint c_orderline_check1 was modified, to only allow creation
of order lines whith QUANTITYORDER and M_PRODUCT_UOM_ID values null or not null at same time.
When they were created from the Requisition to Order process, the Order line's QUANTITYORDER
was created with 0 in the case it had a NULL value, instead of maintain the value as NULL.
Because of it the constraint was failing because a QUANTITYORDER=0 and a M_PRODUCT_UOM_ID=NULL.

To solve this problem was modified the linesToOrder query in RequisitionToOrder_data.xsql, to
retrieve the correct value of QUANTITYORDER, including NULL if there are no qty in the second
UOM.

---
M src/org/openbravo/erpCommon/ad_forms/RequisitionToOrder_data.xsql
---
(0094967)
markmm82   
2017-03-13 01:13   
Code review + Testing OK
(0095292)
hudsonbot   
2017-03-15 20:22   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/54e102bef53e [^]
Maturity status: Test