Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0028492
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 03. Procurement managementminoralways2014-12-26 13:452015-06-29 12:41
ReporterVictorVillarView Statuspublic 
Assigned ToTriage Omni OMS 
PriorityhighResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0028492: Inconsistent behaviour between Manage Requisitions and Requisitions to Order

DescriptionInconsistent behaviour between Manage Requisitions and Requisitions to Order
Steps To ReproduceAs 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.

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0028961 newTriage Omni OMS Price list must be selected according to the vendor when creating orders from requisitions 

-  Notes
(0074627)
reinaldoguerra (developer)
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 (manager)
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.

- Issue History
Date Modified Username Field Change
2014-12-26 13:45 VictorVillar New Issue
2014-12-26 13:45 VictorVillar Assigned To => dmiguelez
2014-12-26 13:45 VictorVillar Modules => Core
2014-12-26 13:45 VictorVillar Resolution time => 1393801200
2014-12-26 13:45 VictorVillar Triggers an Emergency Pack => No
2014-12-26 13:45 VictorVillar Assigned To dmiguelez => AtulOpenbravo
2014-12-26 13:46 VictorVillar Issue Monitored: networkb
2015-01-12 09:52 VictorVillar Resolution time 1393801200 => 1425337200
2015-02-13 17:39 reinaldoguerra Assigned To AtulOpenbravo => reinaldoguerra
2015-02-13 17:39 reinaldoguerra Status new => scheduled
2015-02-16 18:55 reinaldoguerra Relationship added related to 0028961
2015-02-19 00:40 reinaldoguerra Note Added: 0074627
2015-02-23 13:30 jonalegriaesarte Target Version 3.0PR15Q2 => 3.0PR15Q3
2015-06-01 18:11 VictorVillar Resolution time 1425337200 =>
2015-06-03 18:02 vmromanos Note Added: 0078032
2015-06-03 18:02 vmromanos Type defect => design defect
2015-06-03 18:04 vmromanos Assigned To reinaldoguerra => Triage Finance
2015-06-03 18:04 vmromanos Status scheduled => acknowledged
2015-06-29 12:41 vmromanos Target Version 3.0PR15Q3 =>


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker