Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0019296Openbravo ERP09. Financial managementpublic2011-12-14 09:532015-03-11 14:47
Reportermaite 
Assigned Todmiguelez 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket13565
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0019296: Not Posted Transaction Report does not take into account Remittance elements
DescriptionNot Posted Transaction Report does not take into account Remittance elements: remittance, remittance_cancel and remittance_return
Steps To Reproduce0. install remittance module and apply dataset
1. install cuaderno 58 module and apply dataset
2. create remittance for any date and adding any line. Process
3. from "settle/protest remittance" form, select remittance's line and "settle" it
4. go to remittance window, settle tab and verify that line is not posted
5. execute "not posted transactions" report for specific period of time and realize that remittance cancelled line does not appear

same happens with remittances and returned lines
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0017795 closed eduardo_Argal Not Posted Transaction Report 
depends on design defect 0019297 closed dmiguelez Not Posted Transaction Report does not take into account Remittance elements 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-12-14 09:53maiteNew Issue
2011-12-14 09:53maiteAssigned To => jonalegriaesarte
2011-12-14 09:53maiteModules => Core
2011-12-14 09:53maiteOBNetwork customer => Yes
2011-12-14 09:53maiteSupport ticket => 13565
2011-12-14 09:54maiteRelationship addedrelated to 0017795
2011-12-14 09:54maiteStatusnew => scheduled
2011-12-14 09:54maitefix_in_branch => pi
2011-12-14 09:54maiteTarget Version3.0MP7 => 2.50MP38
2011-12-14 09:54maitefix_in_branchpi =>
2011-12-14 09:56maiteTypedefect => backport
2011-12-14 09:57maiteTypebackport => defect
2011-12-14 09:57maiteTarget Version2.50MP38 => 3.0MP7
2011-12-30 10:25jonalegriaesarteTarget Version3.0MP7 => 3.0MP8
2012-01-10 19:04jonalegriaesarteAssigned Tojonalegriaesarte => ioritzCia
2012-01-13 14:03jonalegriaesarteTypedefect => design defect
2012-01-30 17:17jonalegriaesarteTarget Version3.0MP8 => 3.0MP9
2012-03-01 13:45ioritzCiaTarget Version3.0MP9 => 3.0MP10
2012-03-29 16:12jonalegriaesarteTarget Version3.0MP10 =>
2012-09-13 10:42jonalegriaesarteAssigned ToioritzCia => dmiguelez
2013-03-21 11:30jonalegriaesarteNote Added: 0057354
2013-04-29 17:25ngarciaIssue Monitored: ngarcia
2015-03-11 14:47jonalegriaesarteNote Added: 0075449
2015-03-11 14:47jonalegriaesarteStatusscheduled => closed
2015-03-11 14:47jonalegriaesarteResolutionopen => no change required

Notes
(0057354)
jonalegriaesarte   
2013-03-21 11:30   
The report should take into consideration all the elements that can be posted:
production, bom, physical inventory, goods movements,...
The report shows as pending to be posted transactions with amount 0, that does not make sense, because those transactions can not be posted.
(0075449)
jonalegriaesarte   
2015-03-11 14:47   
Fixed in new module:
http://centralrepository.openbravo.com/openbravo/org.openbravo.forge.ui/ForgeModuleDetail/Not-Posted-Transactions [^]