Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015521 | Openbravo ERP | 03. Procurement management | public | 2010-12-24 11:06 | 2011-03-29 13:48 |
|
| Reporter | malsasua | |
| Assigned To | dalsasua | |
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 20 | OS Version | Community Appliance |
| Product Version | 2.50MP24 | |
| Target Version | 2.50MP26 | Fixed in Version | 2.50MP26 | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0015521: invoice date in the void invoice should be updatable |
| Description | when you void a purchase invoice, a new invoice is created to void the initial invoice.
The invoice date of the new invoice is the date when it is voided, and this field is not updateable.
it should be updatable because this date normally is not the day that the invoice is voided |
| Steps To Reproduce | . create and process a new purchase invoice with date 01/07/2010
. void it
|
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | depends on | defect | 0015611 | | closed | adrianromero | invoice date in the void invoice should be updatable | | related to | backport | 0016533 | 2.50MP30 | closed | adrianromero | the invoice date, when the invoice is voided, should be updatable |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2010-12-24 11:06 | malsasua | New Issue | |
| 2010-12-24 11:06 | malsasua | Assigned To | => adrianromero |
| 2010-12-24 11:06 | malsasua | Modules | => Core |
| 2011-01-11 12:35 | adrianromero | Note Added: 0033586 | |
| 2011-01-11 13:09 | adrianromero | Status | new => scheduled |
| 2011-01-11 13:09 | adrianromero | fix_in_branch | => pi |
| 2011-01-11 13:09 | adrianromero | Type | defect => backport |
| 2011-01-11 13:09 | adrianromero | fix_in_branch | pi => |
| 2011-01-11 13:09 | adrianromero | Issue cloned | 0015611 |
| 2011-01-11 13:09 | adrianromero | Relationship added | depends on 0015611 |
| 2011-01-17 09:23 | dalsasua | Assigned To | adrianromero => dalsasua |
| 2011-01-17 09:24 | dalsasua | Note Added: 0033669 | |
| 2011-01-17 14:55 | dalsasua | Note Edited: 0033669 | bug_revision_view_page.php?bugnote_id=0033669#r1427 |
| 2011-01-17 15:06 | dalsasua | Note Added: 0033689 | |
| 2011-01-17 16:19 | dalsasua | fix_in_branch | => 2.50 |
| 2011-01-18 11:52 | hgbot | Checkin | |
| 2011-01-18 11:52 | hgbot | Note Added: 0033706 | |
| 2011-01-18 11:52 | hgbot | Status | scheduled => resolved |
| 2011-01-18 11:52 | hgbot | Resolution | open => fixed |
| 2011-01-18 11:52 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/stable/2.50/rev/855a6f9145b21a01fc1193862aa6801368324bfc [^] |
| 2011-01-27 18:22 | psarobe | Note Added: 0033934 | |
| 2011-01-27 18:22 | psarobe | Status | resolved => closed |
| 2011-01-27 18:22 | psarobe | Fixed in Version | => 2.50MP26 |
| 2011-05-02 17:05 | adrianromero | Relationship added | related to 0016533 |
|
Notes |
|
|
|
It has to be updatable the invoice date and the accounting date of purchase void invoices only as a display logic in the field and in the trigger too.
It has to be documented too that if the invoice date or accounting date of a purchase void invoice is modified it has to be re-executed the accounting for the invoice. |
|
|
|
(0033669)
|
|
dalsasua
|
2011-01-17 09:24
(edited on: 2011-01-17 14:55) |
|
It must, also, be tested whether the invoice can be un-posted or not, if in void status. <- Tested; it's possible.
|
|
|
|
|
This is the way I'm gonna fix it: please notice that we have, in the current scenario, two invoices involved:
- Original invoice (O), created by the user, and voided by the user manually.
- Reversal invoice (R), created automatically by the system, when the O invoice was voided.
The behavior of the system regarding the O invoice will continue to be the same: if processed, invoice date will not be modifiable; if posted, accounting date will not be modifiable (yes will be modifiable if the invoice is not posted); if voided (as if processed) invoice date will not be modifiable.
Regarding the R invoice, the behavior of the system will be: it will be created in void status (and will not be possible to un-process it) -as system behaves nowadays-; if the invoice is not posted, accounting date will be modifiable -as nowadays-; invoice date will be modifiable if it's not posted -this is new behavior-; if the invoice is posted, nor invoice date, nor accounting date will be modifiable -as nowadays-.
Please let me know if this behavior is not correct. Otherwise, I will go for that approach. |
|
|
|
(0033706)
|
|
hgbot
|
|
2011-01-18 11:52
|
|
Repository: erp/stable/2.50
Changeset: 855a6f9145b21a01fc1193862aa6801368324bfc
Author: David Alsasua <david.alsasua <at> openbravo.com>
Date: Mon Jan 17 16:20:30 2011 +0100
URL: http://code.openbravo.com/erp/stable/2.50/rev/855a6f9145b21a01fc1193862aa6801368324bfc [^]
Fixes issue 15521: invoice date in the void invoice should be updatable
The invoiced date field in purchase invoice and sales invoice windows is not read only when the invoice was created automatically by the void invoice process
---
M src-db/database/model/triggers/C_INVOICE_TRG.xml
M src-db/database/sourcedata/AD_AUXILIARINPUT.xml
M src-db/database/sourcedata/AD_COLUMN.xml
---
|
|
|
|
|
|