Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007974Openbravo ERPJ. Demo datapublic2009-03-05 15:062010-11-09 22:46
Reporterrafaroda 
Assigned Topsarobe 
PriorityhighSeveritytrivialReproducibilityalways
StatusclosedResolutionout of date 
PlatformOS20OS VersionrPath Linux
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0007974: Create an invoice ready for Payment Aging Balance reporting
DescriptionCreate an invoice ready for Payment Aging Balance reporting.
Steps To Reproduce1) With current demo data (BigBazaar.xml), navigate to: '''Financial Management > Receivables & Payables > Analysis Tools > Payment Aging Balance'''.
2) Select the ''California'' '''Organization'''.
3) Select the '''Receivable''' radio button.
4) In the '''Business Partner''' field, select the ''CUS1011'' clicking in the Add button.
5) Click the '''HTML Format''' button.

Data have to be shown: http://wiki.openbravo.com/wiki/images/f/f3/Op01-Step1.PNG [^]
Proposed Solution1) Create a new invoice, with Organization: California, Transaction Document: AR Invoice, date 1/03/2009, Business Partner 01Demo, save.
2) Create 3 payments:
* Date: 25/3/2009 amount 1200
* Date: 10/4/2009 amount 2000
* Date: 15/4/2009 amount 1000
3) Create one line with amount 4750 (or 5000 without discount)
4) Complete the invoice, it generates 550, or 800 without discount.
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0007976 acknowledged psarobe Make a Script to update all the demo data transaction dates 
related to defect 0007975 closed AinhoaPagola Remove discounts for business partner Demo Customer 01 
blocks feature request 0008071 closed psarobe Create a DemoBazaar data set 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-03-05 15:06rafarodaNew Issue
2009-03-05 15:06rafarodaAssigned To => pheenan
2009-03-05 15:06rafarodaRegression testing => No
2009-03-05 15:06rafarodaStatusnew => scheduled
2009-03-05 15:13rafarodaProposed Solution updated
2009-03-05 15:13rafarodaSteps to Reproduce Updated
2009-03-05 15:17rafarodaRelationship addedrelated to 0007975
2009-03-05 15:52rafarodaRelationship addedrelated to 0007976
2009-03-05 15:53rafarodaNote Added: 0014440
2009-03-06 15:50rafarodaAssigned Topheenan => AinhoaPagola
2009-03-11 15:28rafarodaAssigned ToAinhoaPagola => rafaroda
2009-03-11 15:28rafarodaStatusscheduled => acknowledged
2009-03-11 15:28rafarodaTypedefect => feature request
2009-03-11 15:29rafarodaRelationship addedblocks 0008071
2009-03-17 16:29rafarodaAssigned Torafaroda => gorkaion
2010-11-03 11:30gorkaionAssigned Togorkaion => psarobe
2010-11-08 09:38psarobeStatusacknowledged => scheduled
2010-11-08 09:38psarobefix_in_branch => pi
2010-11-08 09:38psarobeNote Added: 0032461
2010-11-08 09:38psarobeStatusscheduled => closed
2010-11-08 09:38psarobeResolutionopen => out of date
2010-11-09 22:46anonymoussf_bug_id0 => 3106253

Notes
(0014440)
rafaroda   
2009-03-05 15:53   
To be able to report correctly along the time, this defect will be complemented with feature request 0007976
(0032461)
psarobe   
2010-11-08 09:38   
New demo data works with the new payment flow