Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0018896 | Openbravo ERP | 09. Financial management | public | 2011-09-28 16:02 | 2011-11-04 12:49 | |||||||
Reporter | mirurita | |||||||||||
Assigned To | mirurita | |||||||||||
Priority | normal | Severity | minor | Reproducibility | always | |||||||
Status | closed | Resolution | fixed | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | ||||||||||||
Target Version | Fixed in Version | |||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | ||||||||||||
OBNetwork customer | ||||||||||||
Web browser | ||||||||||||
Modules | Advanced Payables and Receivables Mngmt | |||||||||||
Support ticket | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0018896: Invoice's Reference for Payment Description configured at org level not taking in account sales/purchase flows | |||||||||||
Description | 'Invoice's Reference for Payment Description' is configured at organization level. It allows to select whether the invoice document number or supplier reference number will be used for creating the payment description. It is used also when generating the bank instructions when processing the remittance. If you select for example 'Supplier reference' for a specific organization when you create a payment using this organization this payment will include the supplier reference although you are in sales flow. Related issues: 17756, 18579, 17991 | |||||||||||
Steps To Reproduce | 1) Go to Organization window and select F&B US, Inc. 2) Go to Information tab 3) Select in Invoice's Reference for Payment Description combo Supplier reference and save. 4) Create a new Sales Invoice for F&B US, Inc. organization. 5) Create a Cuaderno 19 remittance. 6) Include previously created invoice. 7) Process the remittance (no grouping). 8) See created line in Instructions tab Realize that for a sales invoice the reference number is used in the description. does not make sense in sales flow. | |||||||||||
Proposed Solution | Two possible solutions: 1) Create separate fields in Organization || Information tab: one for sales an other for purchase. 2) Assume that in sales flow that always the Document Number is the 'reference' which drives the flow. Change FIN_Utility.getDesiredDocumentNo method. If we go for the second option, I think the label of the field should change: 'Purchase Invoice's Reference for Payment Description' | |||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2011-10-27 12:08 | mirurita | Type | defect => backport | |||||||||
2011-10-27 12:08 | mirurita | fix_in_branch | => 2.50 | |||||||||
2011-10-27 13:06 | hgbot | Checkin | ||||||||||
2011-10-27 13:06 | hgbot | Note Added: 0042151 | ||||||||||
2011-10-27 13:06 | hgbot | Status | scheduled => resolved | |||||||||
2011-10-27 13:06 | hgbot | Resolution | open => fixed | |||||||||
2011-10-27 13:06 | hgbot | Fixed in SCM revision | http://code.openbravo.com/erp/devel/pi/rev/0dea693db7648a85859ae1bc3d859a06e68b633e [^] => http://code.openbravo.com/erp/pmods/org.openbravo.advpaymentmngt/rev/69b660d2cc272cdfe38cda2d8b757554e09c6313 [^] | |||||||||
2011-11-04 12:49 | maite | Note Added: 0042537 | ||||||||||
2011-11-04 12:49 | maite | Status | resolved => closed |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|