Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0012071 | Openbravo ERP | 09. Financial management | public | 2010-01-26 18:20 | 2010-02-01 17:53 |
|
Reporter | dalsasua | |
Assigned To | rajagopal | |
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 20 | OS Version | Ubuntu 9.04 |
Product Version | pi | |
Target Version | pi | Fixed in Version | 2.50MP12 | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | No |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0012071: Opening/closing period actions according to multi-org restrictions |
Description | 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. |
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. |
Proposed Solution | 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. |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0011813 | 2.50MP10 | closed | rajagopal | It is not possible to close January period | related to | defect | 0010087 | pi | closed | jayakumar | User shouldn't be able to close a year, if the previous one is not closed as well |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2010-01-26 18:20 | dalsasua | New Issue | |
2010-01-26 18:20 | dalsasua | Assigned To | => rajagopal |
2010-01-26 18:20 | dalsasua | OBNetwork customer | => No |
2010-01-26 18:20 | dalsasua | Relationship added | related to 0011813 |
2010-01-26 18:21 | dalsasua | Relationship added | related to 0010087 |
2010-01-26 18:32 | dalsasua | Note Added: 0023813 | |
2010-01-27 09:54 | rajagopal | Status | new => acknowledged |
2010-01-27 09:54 | rajagopal | Status | acknowledged => scheduled |
2010-01-27 09:54 | rajagopal | fix_in_branch | => pi |
2010-01-27 12:32 | hgbot | Checkin | |
2010-01-27 12:32 | hgbot | Note Added: 0023821 | |
2010-01-27 12:32 | hgbot | Status | scheduled => resolved |
2010-01-27 12:32 | hgbot | Resolution | open => fixed |
2010-01-27 12:32 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/54a4f104b26b58135090a5c6ccb718f44aa4338c [^] |
2010-01-28 07:11 | arunkumar | Note Added: 0023842 | |
2010-01-28 07:11 | arunkumar | Status | resolved => closed |
2010-01-28 07:11 | arunkumar | Fixed in Version | => 2.50MP12 |
2010-01-29 00:00 | anonymous | sf_bug_id | 0 => 2941883 |
2010-02-01 17:53 | hudsonbot | Checkin | |
2010-02-01 17:53 | hudsonbot | Note Added: 0023893 | |