Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0012071Openbravo ERP09. Financial managementpublic2010-01-26 18:202010-02-01 17:53
dalsasua 
rajagopal 
urgentmajoralways
closedfixed 
20Ubuntu 9.04
pi 
pi2.50MP12 
Core
No
0012071: Opening/closing period actions according to multi-org restrictions
In the multi-org project a new feature was set: avoid the possibility of having open periods in a year, if all previous years haven't got all its periods closed as well.
For example, if the user wants to close January-2010 but some of the periods of 2009 are still open, ERP should prevent the user doing so.

This was implemented checking that in order to close a period, previous year must be closed as well.

This measure is ok, but not enough, as it is not taking into account the possibility of opening periods again. See steps to reproduce.
-Go to Financial Management || Accounting || Transactions || Open/Close Period Control.
-Process this record: Until: Dec-06, Action: Close Period.
-Process this record: Until: Jan-07, Action: Close Period.
-Process this record: Until: Dec-06, Action: Open Period.
-Go to General Setup || Enterprise || Organization || Organization >> Period Control.
-Realize that all periods in 2006 are open, and January 2007 is closed. This must not be the case.
Modify the C_PERIOD_PROCESS function, so it checks that a period can only be open if none of the periods of future years is closed.
No tags attached.
related to defect 00118132.50MP10 closed rajagopal It is not possible to close January period 
related to defect 0010087pi closed jayakumar User shouldn't be able to close a year, if the previous one is not closed as well 
Issue History
2010-01-26 18:20dalsasuaNew Issue
2010-01-26 18:20dalsasuaAssigned To => rajagopal
2010-01-26 18:20dalsasuaRelationship addedrelated to 0011813
2010-01-26 18:21dalsasuaRelationship addedrelated to 0010087
2010-01-26 18:32dalsasuaNote Added: 0023813
2010-01-27 09:54rajagopalStatusnew => acknowledged
2010-01-27 09:54rajagopalStatusacknowledged => scheduled
2010-01-27 09:54rajagopalfix_in_branch => pi
2010-01-27 12:32hgbotCheckin
2010-01-27 12:32hgbotNote Added: 0023821
2010-01-27 12:32hgbotStatusscheduled => resolved
2010-01-27 12:32hgbotResolutionopen => fixed
2010-01-27 12:32hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/54a4f104b26b58135090a5c6ccb718f44aa4338c [^]
2010-01-28 07:11arunkumarNote Added: 0023842
2010-01-28 07:11arunkumarStatusresolved => closed
2010-01-28 07:11arunkumarFixed in Version => 2.50MP12
2010-01-29 00:00anonymoussf_bug_id0 => 2941883
2010-02-01 17:53hudsonbotCheckin
2010-02-01 17:53hudsonbotNote Added: 0023893

Notes
(0023813)
dalsasua   
2010-01-26 18:32   
Hi Rajagopal,

Please, kindly refer to the fix of the related issues in order to get introduced to the topic, and oriented in the approach to follow to fix the issue.

Thanks. Regards.
(0023821)
hgbot   
2010-01-27 12:32   
Repository: erp/devel/pi
Changeset: 54a4f104b26b58135090a5c6ccb718f44aa4338c
Author: Rajagopal Baskaran <rajagopal.baskaran <at> openbravo.com>
Date: Wed Jan 27 17:01:13 2010 +0530
URL: http://code.openbravo.com/erp/devel/pi/rev/54a4f104b26b58135090a5c6ccb718f44aa4338c [^]

Fixes issue 12071 Opening/closing period actions according to multi-org restrictions

---
M src-db/database/model/functions/C_PERIOD_PROCESS.xml
M src-db/database/sourcedata/AD_MESSAGE.xml
---
(0023842)
arunkumar   
2010-01-28 07:11   
Tested & Working fine
(0023893)
hudsonbot   
2010-02-01 17:53   
A changeset related to this issue has been promoted to main after passing a series of tests and an OBX has been generated:

Changeset: http://code.openbravo.com/erp/devel/main/rev/54a4f104b26b [^]
Merge Changeset: http://code.openbravo.com/erp/devel/main/rev/3d5bd712a24b [^]
Tests: http://builds.openbravo.com/view/devel-int/ [^]
OBX: http://builds.openbravo.com/erp/core/obx/OpenbravoERP-2.50CI.16007.obx [^]