Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0013600
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Modules] Booking controlmajoralways2010-06-10 09:132010-12-31 09:51
ReporterrafarodaView Statuspublic 
Assigned Tovmromanos 
PriorityhighResolutionopenFixed in Version1.0.1
StatusclosedFix in branchFixed in SCM revisionvalidto
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionCommunity ApplianceDatabase version8.3.9Ant version1.7.1
Product VersionSCM revision 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customerNo
Regression introduced in release
Summary

0013600: "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.
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 [^]
TagsNo tags attached.
Attached Filespng file icon ValidToTaxRate.png [^] (89,580 bytes) 2010-06-10 09:13


png file icon ValidToAccount.png [^] (60,318 bytes) 2010-06-10 09:14


png file icon ValidToBP.png [^] (71,261 bytes) 2010-06-10 09:14

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0032677)
psanjuan (viewer)
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 (viewer)
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 (viewer)
2010-12-16 12:06

 13600 ready to go according to Michael email
(0033495)
psanjuan (viewer)
2010-12-31 09:51

 feature working

- Issue History
Date Modified Username Field Change
2010-06-10 09:13 rafaroda New Issue
2010-06-10 09:13 rafaroda Assigned To => sathiyan
2010-06-10 09:13 rafaroda OBNetwork customer => No
2010-06-10 09:13 rafaroda File Added: ValidToTaxRate.png
2010-06-10 09:14 rafaroda File Added: ValidToAccount.png
2010-06-10 09:14 rafaroda File Added: ValidToBP.png
2010-06-10 09:29 rafaroda Proposed Solution updated
2010-06-10 11:58 rafaroda Proposed Solution updated
2010-11-17 17:05 psanjuan Note Added: 0032677
2010-11-17 17:05 psanjuan Assigned To sathiyan => dalsasua
2010-12-13 16:23 psanjuan Note Added: 0033137
2010-12-13 16:28 psanjuan Note Edited: 0033137 View Revisions
2010-12-13 16:28 psanjuan Note Edited: 0033137 View Revisions
2010-12-13 16:29 psanjuan Note Edited: 0033137 View Revisions
2010-12-13 16:30 psanjuan Note Edited: 0033137 View Revisions
2010-12-13 16:35 psanjuan Note Edited: 0033137 View Revisions
2010-12-13 16:45 psanjuan Note Edited: 0033137 View Revisions
2010-12-13 19:09 psanjuan Note Edited: 0033137 View Revisions
2010-12-14 12:51 psanjuan Note Edited: 0033137 View Revisions
2010-12-14 12:52 psanjuan Note Edited: 0033137 View Revisions
2010-12-14 13:00 psanjuan Assigned To dalsasua => vmromanos
2010-12-16 12:06 psanjuan Note Added: 0033231
2010-12-20 12:33 psanjuan Note Edited: 0033137 View Revisions
2010-12-31 09:46 psanjuan Status new => scheduled
2010-12-31 09:47 psanjuan Status scheduled => resolved
2010-12-31 09:47 psanjuan Status resolved => closed
2010-12-31 09:47 psanjuan Fixed in SCM revision => http://forge.openbravo.com/projects/validto [^]
2010-12-31 09:51 psanjuan Note Added: 0033495
2010-12-31 09:51 psanjuan Fixed in Version => 1.0.1

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker