Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0028035 | Openbravo ERP | 03. Procurement management | public | 2014-10-30 18:11 | 2015-03-10 04:27 |
|
Reporter | ngarcia | |
Assigned To | AtulOpenbravo | |
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | 3.0PR15Q2 | Fixed in Version | pi | |
Merge Request Status | |
Review Assigned To | umartirena |
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 | 0028035: Cannot pay a purchase order if it is invoiced with more orders and then reactivated and booked again |
Description | Cannot pay a purchase order if it is invoiced with more orders and then reactivated and booked again |
Steps To Reproduce | As group admin role:
Create two purchase orders and book them
Include them in the same invoice and complete it
Reactivate and book one of them
Check one of them cannot be paid as it does not have payment plan detail (FIN_PAYMENT_SCHEDULEDETAIL)
If the invoice was included in a reactivated payment proposal, if it is processed again it won't be possible to reactivate it |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0033500 | | closed | AtulOpenbravo | Wrong payment schedule details when return to vendor document is invoiced using credit a memo invoice |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2014-10-30 18:11 | ngarcia | New Issue | |
2014-10-30 18:11 | ngarcia | Assigned To | => AtulOpenbravo |
2014-10-30 18:11 | ngarcia | Modules | => Core |
2014-10-30 18:11 | ngarcia | Resolution time | => 1417388400 |
2014-10-30 18:11 | ngarcia | Triggers an Emergency Pack | => No |
2014-10-30 18:17 | ngarcia | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=6925#r6925 |
2014-10-30 18:25 | ngarcia | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=6926#r6926 |
2014-12-22 12:33 | vmromanos | Target Version | 3.0PR15Q1 => 3.0PR15Q2 |
2015-01-14 15:35 | AtulOpenbravo | Status | new => scheduled |
2015-01-14 15:35 | AtulOpenbravo | fix_in_branch | => pi |
2015-02-26 08:45 | Sandrahuguet | Review Assigned To | => umartirena |
2015-02-26 08:45 | Sandrahuguet | fix_in_branch | pi => |
2015-03-09 19:50 | hgbot | Checkin | |
2015-03-09 19:50 | hgbot | Note Added: 0075345 | |
2015-03-09 19:50 | hgbot | Status | scheduled => resolved |
2015-03-09 19:50 | hgbot | Resolution | open => fixed |
2015-03-09 19:50 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/7de1f5e692f97505b8e45a798b455b558859d77b [^] |
2015-03-09 19:53 | umartirena | Note Added: 0075346 | |
2015-03-09 19:53 | umartirena | Status | resolved => closed |
2015-03-09 19:53 | umartirena | Fixed in Version | => pi |
2015-03-10 04:27 | hudsonbot | Checkin | |
2015-03-10 04:27 | hudsonbot | Note Added: 0075357 | |
2016-08-10 14:28 | aferraz | Relationship added | related to 0033500 |
Notes |
|
(0075345)
|
hgbot
|
2015-03-09 19:50
|
|
Repository: erp/devel/pi
Changeset: 7de1f5e692f97505b8e45a798b455b558859d77b
Author: Atul Gaware <atul.gaware <at> openbravo.com>
Date: Tue Feb 17 01:11:53 2015 +0530
URL: http://code.openbravo.com/erp/devel/pi/rev/7de1f5e692f97505b8e45a798b455b558859d77b [^]
Fixes Issue 28035:Cannot pay a purchase order if it is invoiced with more
orders and then reactivated and booked again
Fin_Payment_Scheduledetails are updated with fin_payment_schedule_order
only when found null. And only such schedule detail amounts are used to
calculate pending amount.
---
M modules/org.openbravo.advpaymentmngt/src-db/database/model/functions/APRM_GEN_PAYMENTSCHEDULE_ORD.xml
---
|
|
|
(0075346)
|
umartirena
|
2015-03-09 19:53
|
|
Code Review + Testing OK
After talking with Eduardo and Dmitry not to add a modulescript has been decided, as does not seem to be a common case to happen. If it is needed to fix data, an script will be created for it. |
|
|
|
|