Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0010087Openbravo ERP09. Financial managementpublic2009-07-28 13:252009-10-22 00:00
dalsasua 
jayakumar 
highmajoralways
closedfixed 
20Ubuntu 8.04Hardy
pi 
pi2.50MP7 
Core
No
0010087: User shouldn't be able to close a year, if the previous one is not closed as well
In order to close a year, all the previous ones must be closed. Otherwise, when closing those, accounting data may not be correct. For example:
A system with years 2008 and 2009 created, all of them still open.
2009 is closed.
More documents are posted in 2008.
2008 is closed.
The accounting data related to the last documents posted in 2008 will not be taken into account in the closing of 2009 and so in the opening of 2010.
Go to finan.mgmt>accounting>setup>fiscal calendar
create years 2008 and 2009
close 2009
systems lets you do it with no error or warning
Add a check in the CREATE_REG_FACT_ACCT process, so a year cannot be closed if previous one is not closed as well.
No tags attached.
related to defect 00118132.50MP10 closed rajagopal It is not possible to close January period 
related to defect 0012071pi closed rajagopal Opening/closing period actions according to multi-org restrictions 
Issue History
2009-07-28 13:25dalsasuaNew Issue
2009-07-28 13:25dalsasuaAssigned To => dalsasua
2009-08-31 13:47rafarodaAssigned Todalsasua => vmromanos
2009-08-31 13:47rafarodaPrioritynormal => high
2009-08-31 13:47rafarodaStatusnew => scheduled
2009-10-06 15:28rajagopalNote Added: 0020788
2009-10-06 16:22dalsasuaNote Added: 0020790
2009-10-12 08:47jayakumarAssigned Tovmromanos => jayakumar
2009-10-13 11:52hgbotCheckin
2009-10-13 11:52hgbotNote Added: 0020980
2009-10-13 11:52hgbotStatusscheduled => resolved
2009-10-13 11:52hgbotResolutionopen => fixed
2009-10-13 11:52hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/57c162c684726322e5b5ecf78cecf3fb8e1faf87 [^]
2009-10-14 07:22hgbotCheckin
2009-10-14 07:22hgbotNote Added: 0020993
2009-10-14 07:22hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/devel/pi/rev/57c162c684726322e5b5ecf78cecf3fb8e1faf87 [^] => http://code.openbravo.com/erp/devel/pi/rev/4ca31e7f8a75b20663381854efa07e00b3591d17 [^]
2009-10-21 12:28arunkumarStatusresolved => closed
2009-10-21 12:28arunkumarNote Added: 0021261
2009-10-21 12:28arunkumarFixed in Version => 2.50MP7
2009-10-22 00:00anonymoussf_bug_id0 => 2883555
2009-12-28 09:55vmromanosRelationship addedrelated to 0011813
2010-01-26 18:21dalsasuaRelationship addedrelated to 0012071

Notes
(0020788)
rajagopal   
2009-10-06 15:28   
Hi David,

The error should be shown if the previous year is not closed is ok.

Do we need to check whether the previous year is "Permanently Closed Period" or just "Close Period" ?

Thanks,
B.Rajagopal
(0020790)
dalsasua   
2009-10-06 16:22   
Hi,

Just closed is ok.

Regards.
(0020980)
hgbot   
2009-10-13 11:52   
Repository: erp/devel/pi
Changeset: 57c162c684726322e5b5ecf78cecf3fb8e1faf87
Author: Jayakumar Kasinathan <jayakumar.kasinathan <at> openbravo.com>
Date: Tue Oct 13 15:21:58 2009 +0530
URL: http://code.openbravo.com/erp/devel/pi/rev/57c162c684726322e5b5ecf78cecf3fb8e1faf87 [^]

Fixed 10087 User shouldn't be able to close a year, if the previous one is not closed as well.

---
M src-db/database/model/functions/C_PERIOD_PROCESS.xml
M src-db/database/sourcedata/AD_MESSAGE.xml
---
(0020993)
hgbot   
2009-10-14 07:22   
Repository: erp/devel/pi
Changeset: 4ca31e7f8a75b20663381854efa07e00b3591d17
Author: Jayakumar Kasinathan <jayakumar.kasinathan <at> openbravo.com>
Date: Wed Oct 14 10:51:22 2009 +0530
URL: http://code.openbravo.com/erp/devel/pi/rev/4ca31e7f8a75b20663381854efa07e00b3591d17 [^]

Fixed 10087 license issue fixed

---
M src-db/database/model/functions/C_PERIOD_PROCESS.xml
---
(0021261)
arunkumar   
2009-10-21 12:28   
Tested & Working fine.

Now the user should not be able to close a year if the previous year is open.