Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0028492Openbravo ERP03. Procurement managementpublic2014-12-26 13:452015-06-29 12:41
VictorVillar 
Triage Omni OMS 
highminoralways
acknowledgedopen 
5
pi 
 
Core
No
0028492: Inconsistent behaviour between Manage Requisitions and Requisitions to Order
Inconsistent behaviour between Manage Requisitions and Requisitions to Order
As group Admin role,
Go to Product window,
   create a new one:
        Org: España
        name: test
  Price List: Tarifa Bebidas Alegres
  Purchasing tab: Bebidas alegres vendor
Go to Manage Requisitions window,
  create one for España
  Business Partner: blank
  Price list: blank
 Lines: Product test
    qty:1
 Complete it and Create Purchase Orders.
       Business Partner: blank
       Price List: blank
Realise that the Business Partner is not mandatory.
click on OK button --> a new Purchase order is created for the Business Partner defined in the Purchasing tab of the product selected (advance feature). If you do not have any business partner defined in the Purchansing tab, you will not be able to create the Purchase Order because you have not selected the business partner.

Create a new Requisition:
    Go to Manage Requisitions window,
  create one for España
  Business Partner: blank
  Price list: blank
 Lines: Product test
    qty:1
 Complete it.

Go to Requisition to Order window,
   search the requisition created before, filtering by this product.
add the line populated.
select it and click on Create button.
  Realise that the Business Partner is mandatory and none is populated.

No tags attached.
related to defect 0028961 new Triage Omni OMS Price list must be selected according to the vendor when creating orders from requisitions 
Issue History
2014-12-26 13:45VictorVillarNew Issue
2014-12-26 13:45VictorVillarAssigned To => dmiguelez
2014-12-26 13:45VictorVillarModules => Core
2014-12-26 13:45VictorVillarResolution time => 1393801200
2014-12-26 13:45VictorVillarTriggers an Emergency Pack => No
2014-12-26 13:45VictorVillarAssigned Todmiguelez => AtulOpenbravo
2014-12-26 13:46VictorVillarIssue Monitored: networkb
2015-01-12 09:52VictorVillarResolution time1393801200 => 1425337200
2015-02-13 17:39reinaldoguerraAssigned ToAtulOpenbravo => reinaldoguerra
2015-02-13 17:39reinaldoguerraStatusnew => scheduled
2015-02-16 18:55reinaldoguerraRelationship addedrelated to 0028961
2015-02-19 00:40reinaldoguerraNote Added: 0074627
2015-02-23 13:30jonalegriaesarteTarget Version3.0PR15Q2 => 3.0PR15Q3
2015-06-01 18:11VictorVillarResolution time1425337200 =>
2015-06-03 18:02vmromanosNote Added: 0078032
2015-06-03 18:02vmromanosTypedefect => design defect
2015-06-03 18:04vmromanosAssigned Toreinaldoguerra => Triage Finance
2015-06-03 18:04vmromanosStatusscheduled => acknowledged
2015-06-29 12:41vmromanosTarget Version3.0PR15Q3 =>

Notes
(0074627)
reinaldoguerra   
2015-02-19 00:40   
Test plan used:
As group Admin role,
Go to Product window,
   create a new one:
        Org: España
        name: test
  Price List: Tarifa Bebidas Alegres
Go to Purchasing tab, create a new record and select Bebidas alegres vendor
Go to Manage Requisitions window,
  create one for España
  Business Partner: blank
  Price list: blank
 Lines: Product test
    qty:1
 Complete it and click on Create Purchase Orders button.
Realize that now Business Partner is selected as the product has it defined on its Purchasing tab. Also Price List is shown according to the selected business partner. Both fields are now mandatory.

Go to Manage Requisitions window again,
  create one for España
  Business Partner: blank
  Price list: blank
 Lines: Product test
    qty:1
 Complete it.

Go to Requisition to Order window,
   search the requisition created before, filtering by this product.
add the line populated.
select it and click on Create button.
  Realize that the Business Partner is mandatory and it is populated with the vendor defined in product's purchasing tab.
  
Now there are not inconsistents between Manage Requisitions and Requisitions to Order windows.
(0078032)
vmromanos   
2015-06-03 18:02   
Moved to design defect:

The right solution would be to change Requisition to order to accept not mandatory BP and implement a similar logic to the Manage Requisition window.

The problem here is that both processes don't share the same code (one of them is developed in Java and the other one in PL/SQL). Ideally we should try to merge both codes into one (Java) to manage both flows.