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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0012412
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 03. Procurement managementminoralways2010-02-23 12:082010-05-11 18:20
ReporternetworkbView Statuspublic 
Assigned Todalsasua 
PriorityurgentResolutionfixedFixed in Version2.50MP17
StatusclosedFix in branchFixed in SCM revision01e5e323655b
ProjectionnoneETAnoneTarget Version2.50MP17
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP11SCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0012412: Error in Matched Invoice when you void a Good Receipt

DescriptionWhen you have a purhase invoice and you generate a good receipt from this invoice. When you complete the good receipt, a line is created on Matched Invoice.

If you void this Good Receipt on Matched Invoice there is not change.
Steps To Reproduce-As Openbravo Admin go to Procurement Management || Transactions || Purchase Invoice.
-Create a new record, create a new line and complete.
-Go to Procurement Management || Transactions || Goods Receipt.
-Create a new record from the invoice created using Create Lines From.
-Complete.

-Go to Procurement Management || Transactions || Matched Invoices
-Realize that a line has been created.

-Go back to Procurement Management || Transactions || Goods Receipt.
-Select the good receipt created.
-Click close
-Choose void in the combo
-Click ok

-Go to Go to Procurement Management || Transactions || Matched Invoices
-Realize that there are not changes.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 00126732.50MP17 closeddalsasua Uncorrect link to good receipts when an invoice is shipped in several good receipts 

-  Notes
(0024852)
dalsasua (viewer)
2010-02-26 10:37

When in steps to reproduce says "-Click Close.", is it correct? should say "-Click void."?
(0024854)
networkb (viewer)
2010-02-26 10:51

David,

the button is 'Close' and there is only an action: Void
(0024855)
dalsasua (viewer)
2010-02-26 11:02

Then I should go for:
-Click close
-Choose void in the combo
-Click ok
(0024856)
networkb (viewer)
2010-02-26 11:05

Yes, these are the steps.
(0024893)
psarobe (viewer)
2010-03-01 10:32

Solution:

It has to insert as many lines as you void in the table M_MATCHINV but with negative qty
(0025110)
dalsasua (viewer)
2010-03-08 10:04

The provided scenario shouldn't happen, in my opinion. The bug is that system allows user to void a good receipt that has been already invoiced, because:

1) The new, voided, goods receipt document will not be available anymore for being invoiced, so a material that has been returned to provider will not appear as pending in the system.

2) The flow of voiding invoice <-> void order regarding matched invoices documents and accounting becomes really complex.

My proposal is: allow user to void a good receipt only if:

a) it has not been invoiced (no impact in Matched Invoices documents)
b) it has been invoiced, but the invoice/s where this material was invoiced, has/have been previously voided as well.
c) if user wants to return a material already invoiced without voiding the associated invoice/s, will create a negative good receipt document, valid to be invoiced again.

Regards.
(0025657)
dmitry_mezentsev (viewer)
2010-03-22 21:01

Hello All,

This issue is going "hot", expiring in 15 days so I suggest to make a decision here.

I agree with a David proposal.
Point c) is the business flow we agreed on and which we now use for return of materials in Quick Start and it is described in the corresponding documentation.
(0025887)
dalsasua (viewer)
2010-04-06 09:41

A solution has been provided to QA and Support teams. Pending their approval to push the changeset to Pi repository.
(0026174)
psarobe (viewer)
2010-04-14 12:49

Still in testing phase. Several issues have been found. Pending to be fixed
(0026235)
adrianromero (viewer)
2010-04-15 11:00

Agreed with the client to provide the fix for 2.50MP16
(0026884)
dalsasua (viewer)
2010-05-03 17:40

Provided a solution to QA for testing
(0027104)
psarobe (viewer)
2010-05-10 16:48

Tested working fine

- Issue History
Date Modified Username Field Change
2010-02-23 12:08 networkb New Issue
2010-02-23 12:08 networkb Assigned To => adrianromero
2010-02-23 12:08 networkb OBNetwork customer => Yes
2010-02-23 13:43 adrianromero Status new => scheduled
2010-02-23 13:43 adrianromero fix_in_branch => pi
2010-02-26 10:37 dalsasua Note Added: 0024852
2010-02-26 10:37 dalsasua Status scheduled => feedback
2010-02-26 10:51 networkb Note Added: 0024854
2010-02-26 10:51 networkb Status feedback => new
2010-02-26 10:51 networkb fix_in_branch pi =>
2010-02-26 11:02 dalsasua Note Added: 0024855
2010-02-26 11:05 networkb Note Added: 0024856
2010-02-26 11:05 networkb Steps to Reproduce Updated View Revisions
2010-02-26 11:06 adrianromero Assigned To adrianromero => dalsasua
2010-02-26 16:28 networkb Priority urgent => immediate
2010-03-01 10:03 psarobe Status new => scheduled
2010-03-01 10:03 psarobe Assigned To dalsasua => adrianromero
2010-03-01 10:03 psarobe fix_in_branch => pi
2010-03-01 10:32 psarobe Note Added: 0024893
2010-03-02 17:40 dalsasua Assigned To adrianromero => dalsasua
2010-03-08 10:04 dalsasua Note Added: 0025110
2010-03-08 10:04 dalsasua Status scheduled => feedback
2010-03-08 16:05 jpabloae Target Version 2.50MP13 => 2.50MP14
2010-03-22 21:01 dmitry_mezentsev Note Added: 0025657
2010-03-23 09:49 adrianromero Relationship added related to 0012673
2010-04-06 09:38 dalsasua Status feedback => scheduled
2010-04-06 09:41 dalsasua Note Added: 0025887
2010-04-06 09:41 dalsasua Status scheduled => resolved
2010-04-06 09:41 dalsasua Fixed in SCM revision => 5ff0aba4d250
2010-04-06 09:41 dalsasua Resolution open => fixed
2010-04-14 12:48 psarobe Status resolved => new
2010-04-14 12:48 psarobe Resolution fixed => open
2010-04-14 12:48 psarobe Status new => scheduled
2010-04-14 12:49 psarobe Note Added: 0026174
2010-04-15 11:00 adrianromero Note Added: 0026235
2010-04-15 11:00 adrianromero Severity major => minor
2010-04-15 11:00 adrianromero Target Version 2.50MP14 => 2.50MP16
2010-04-15 11:00 adrianromero fix_in_branch pi =>
2010-04-19 11:19 adrianromero Priority immediate => urgent
2010-05-03 17:40 dalsasua Note Added: 0026884
2010-05-03 17:40 dalsasua Status scheduled => resolved
2010-05-03 17:40 dalsasua Fixed in Version => pi
2010-05-03 17:40 dalsasua Fixed in SCM revision 5ff0aba4d250 => 01e5e323655b
2010-05-03 17:40 dalsasua Resolution open => fixed
2010-05-10 16:48 psarobe Note Added: 0027104
2010-05-10 16:48 psarobe Status resolved => closed
2010-05-10 16:48 psarobe Fixed in Version pi => 2.50MP16
2010-05-11 00:00 anonymous sf_bug_id 0 => 2999637
2010-05-11 18:19 jpabloae Target Version 2.50MP16 => 2.50MP17
2010-05-11 18:20 jpabloae Fixed in Version 2.50MP16 => 2.50MP17


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker