Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013600ModulesBooking controlpublic2010-06-10 09:132010-12-31 09:51
Reporterrafaroda 
Assigned Tovmromanos 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionopen 
PlatformOS20OS VersionCommunity Appliance
Product Version 
Target VersionFixed in Version1.0.1 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customerNo
Regression introduced in release
Summary0013600: "Valid to Date" field in Tax Rates, Financial Accounts and Business Partners
DescriptionThere is a need for a "Valid to Date" field in Tax Rates, Financial Accounts and Business Partners.

The rationale behind this is:
   1. Tax Rates: Tax rates might become invalid by changes of law.
   2. Financial Accounts: At the time a company changes VAT-timing the transitory account of VAT becomes invalid.
   3. Business Partners: A company changes their contracts and from a certain time they purchase their goods from another business partner.
Steps To Reproduce
Proposed Solution1) A "Valid to Date" mandatory field needs to be included in (see screenshots):
* Tax Rate window
* Account Tree window, Element Value tab
* Business Partner window
"On create default" value will be '31-12-9999' [1]

2) Booking Control process has to check these 3 "Valid to Date" values before completing an action. This means that Accounting Date <= Valid to Date for each of the 3 Valid to Date values (Tax Rate, Account Element Value and Business Partner) before posting.

[1] http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/How_to_define_an_oncreatedefault [^]
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng ValidToTaxRate.png (89,580) 2010-06-10 09:13
https://issues.openbravo.com/file_download.php?file_id=2659&type=bug
png

png ValidToAccount.png (60,318) 2010-06-10 09:14
https://issues.openbravo.com/file_download.php?file_id=2660&type=bug
png

png ValidToBP.png (71,261) 2010-06-10 09:14
https://issues.openbravo.com/file_download.php?file_id=2661&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2010-06-10 09:13rafarodaNew Issue
2010-06-10 09:13rafarodaAssigned To => sathiyan
2010-06-10 09:13rafarodaOBNetwork customer => No
2010-06-10 09:13rafarodaFile Added: ValidToTaxRate.png
2010-06-10 09:14rafarodaFile Added: ValidToAccount.png
2010-06-10 09:14rafarodaFile Added: ValidToBP.png
2010-06-10 09:29rafarodaProposed Solution updated
2010-06-10 11:58rafarodaProposed Solution updated
2010-11-17 17:05psanjuanNote Added: 0032677
2010-11-17 17:05psanjuanAssigned Tosathiyan => dalsasua
2010-12-13 16:23psanjuanNote Added: 0033137
2010-12-13 16:28psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1311
2010-12-13 16:28psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1312
2010-12-13 16:29psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1313
2010-12-13 16:30psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1314
2010-12-13 16:35psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1317
2010-12-13 16:45psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1318
2010-12-13 19:09psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1322
2010-12-14 12:51psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1325
2010-12-14 12:52psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1326
2010-12-14 13:00psanjuanAssigned Todalsasua => vmromanos
2010-12-16 12:06psanjuanNote Added: 0033231
2010-12-20 12:33psanjuanNote Edited: 0033137bug_revision_view_page.php?bugnote_id=0033137#r1365
2010-12-31 09:46psanjuanStatusnew => scheduled
2010-12-31 09:47psanjuanStatusscheduled => resolved
2010-12-31 09:47psanjuanStatusresolved => closed
2010-12-31 09:47psanjuanFixed in SCM revision => http://forge.openbravo.com/projects/validto [^]
2010-12-31 09:51psanjuanNote Added: 0033495
2010-12-31 09:51psanjuanFixed in Version => 1.0.1

Notes
(0032677)
psanjuan   
2010-11-17 17:05   
Must be done as the application of this data must be conditional on the date. For example, a tax rate may be active in the current year, and not active in a past year (or vice versa). The use of the tax rate is therefore conditional on the "Valid to date".
(0033137)
psanjuan   
2010-12-13 16:23   
(edited on: 2010-12-20 12:33)
This note is meant to be a detailed explanation of the way this feature is going to be implemented:

1) A "Valid To Date" field must be created in the application paths detailed below:

1.a) Financial Management || Accounting || Setup || Tax Rate || Tax tab.
Valid To Date should be next to existing "Valid From date".

1.b) Financial Management || Accounting || Setup || Account Tree || Element >> Element Value tab
Valid To Date should be next to existing "Search key" field.

1.c) Master Data Management || Business Partner || Business Partner tab
Valid To Date should be next to existing "Search key" field.

2) All of above "Valid To Dates" must NOT be mandatory.

3) Empty "Valid to dates" means that there is no a valid to date to take into account, there is no an expiration date

4) "Valid To dates" must be filled-in in case an entity (tax rate, BP or account) has a specific Valid to Date.

5) The booking control process must check these 3 valid to dates before booking/posting.

6) Booking will only take place in case below 3 validations are positive/true

Accounting date <= Tax Rate Valid To Date
Accounting date <= Element Value Valid To Date
Accounting date <= Business Partner Valid To Date

7) Above validations will take place while posting any document which can be posted/booked in the System, and only in case the Booking Control accounting process is set up and active for the accounting schema.
(0033231)
psanjuan   
2010-12-16 12:06   
13600 ready to go according to Michael email
(0033495)
psanjuan   
2010-12-31 09:51   
feature working