Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0012673Openbravo ERP03. Procurement managementpublic2010-03-12 17:432010-05-11 18:20
networkb 
dalsasua 
urgentminoralways
closedfixed 
5
2.50MP13 
2.50MP172.50MP17 
OBPS
Core
No
0012673: Uncorrect link to good receipts when an invoice is shipped in several good receipts
A purchase is created. IE, quantity: 100.
A good receipt is created (using "Create lines from") with 25 quantity.
Other one, is created with the rest (75). This ones are not linked to the invoice (there is no record in m_matchinv).
Go to Procurement management > Transactions > Purchase Invoice.
Create a new record.
Fill all required fields.
Go to Line tab.
Create a new one. Select one product, and as Invoiced quantity, enter 100.
Go back to Header, process it.
Go to Procurement management > Transactions > Good Receipts.
Create a new record with same BP.
Press "Create lines from". Select the invoice created.
Check it.
Edit quantity, and fill 25. Select a storage bin.
Press OK.
Complete it.
Create a new record with same BP.
Press "Create lines from". Select the invoice created.
Check it.
Edit quantity, and fill 75. Select a storage bin.
Press OK.
Complete it.
Go to Matched Invoice.
No tags attached.
related to defect 00124122.50MP17 closed dalsasua Error in Matched Invoice when you void a Good Receipt 
Issue History
2010-03-12 17:43networkbNew Issue
2010-03-12 17:43networkbAssigned To => adrianromero
2010-03-12 17:43networkbOBNetwork customer => Yes
2010-03-16 15:52adrianromeroStatusnew => scheduled
2010-03-16 15:52adrianromerofix_in_branch => pi
2010-03-18 18:03adrianromeroAssigned Toadrianromero => psarobe
2010-03-23 09:49adrianromeroRelationship addedrelated to 0012412
2010-04-06 09:42dalsasuaNote Added: 0025889
2010-04-06 09:42dalsasuaStatusscheduled => resolved
2010-04-06 09:42dalsasuaFixed in SCM revision => 5ff0aba4d250
2010-04-06 09:42dalsasuaResolutionopen => fixed
2010-04-13 10:13psarobeNote Added: 0026094
2010-04-13 10:13psarobeStatusresolved => new
2010-04-13 10:13psarobeResolutionfixed => open
2010-04-13 10:13psarobeStatusnew => scheduled
2010-04-13 10:13psarobeAssigned Topsarobe => dalsasua
2010-04-15 10:59adrianromeroNote Added: 0026234
2010-04-15 10:59adrianromeroSeveritymajor => minor
2010-04-15 10:59adrianromeroTarget Version2.50MP14 => 2.50MP16
2010-04-15 10:59adrianromerofix_in_branchpi =>
2010-04-19 11:20adrianromeroPriorityimmediate => urgent
2010-05-03 17:40dalsasuaNote Added: 0026885
2010-05-03 17:40dalsasuaStatusscheduled => resolved
2010-05-03 17:40dalsasuaFixed in Version => pi
2010-05-03 17:40dalsasuaFixed in SCM revision5ff0aba4d250 => 01e5e323655b
2010-05-03 17:40dalsasuaResolutionopen => fixed
2010-05-10 16:49psarobeNote Added: 0027105
2010-05-10 16:49psarobeStatusresolved => closed
2010-05-10 16:49psarobeFixed in Versionpi => 2.50MP16
2010-05-11 00:00anonymoussf_bug_id0 => 2999639
2010-05-11 18:19jpabloaeTarget Version2.50MP16 => 2.50MP17
2010-05-11 18:20jpabloaeFixed in Version2.50MP16 => 2.50MP17

Notes
(0025889)
dalsasua   
2010-04-06 09:42   
A solution was provided to QA and Support departments. Waiting for their approval to push code to Pi repository.
(0026094)
psarobe   
2010-04-13 10:13   
Still in testing phase. Several issues has been sent to David that blocks other test cases.

Change the status to Schedule since in real is not Resolved
(0026234)
adrianromero   
2010-04-15 10:59   
Agreed with the client to provide the fix for 2.50MP16
(0026885)
dalsasua   
2010-05-03 17:40   
Provided a solution to QA for testing
(0027105)
psarobe   
2010-05-10 16:49   
Tested working fine