Fiscal quarters crossing calendar years

Hi all,

We have a unique requirement here in Ethiopia. We have 13 months with the first 12 having 30 days each and the 13th one having 5 or 6 depending on leap year. Since data about the 13th month is moved to the first month of the next year (even when collected manually), we did not face any problems regarding that.

But we are facing a challenge in defining quarters. The fiscal year of Ethiopia starts in month 11 of the last year, effectively making quarter I happen in two different years. However, DHIS2 does not handle such quarters.

Have any of you faced these kind of challenges in other implementations in other countries? If so, how did you handle it?

Your comments and suggestions are appreciated.

Regards,

Seid,

1 Like

Seid,

The DHIS2 analytics engine only caters for a limited set of relatively common data periods, as you know - including the more common financial quarters (same as standard quarters, but different names) and financial years (again combinations of standard quarters).

What you need is, as u say, a unique requirement - and the logical way of handling such unique requirements is to set them up as relative user-defined periods.

The problem with that up to now is that DHIS2 has not had what I usually call the “anchor” period concept - i.e. the ability to specify a certain “anchor date period point” that in turn will determine a range of other relative user-defined periods.

There are at least to usage scenarios for such anchor dates:

either you can use them simply as an offset to cater for the timelag between the end of a data capture reporting period and when the data is available for analysis. We have that scenario in many/most countries: if you are running a report for the relative period “last six months” on September 3rd, you do not want a report for April-May-June-July-Aug-Sep because you don’t yet have data for e.g. July and Aug and Sep - so in that case you specify an anchor date of e.g. 30th June - which will result in the “last 6 months” report giving you data for Jan-June (where you have data for all months).

OR you can use them to specify a “fixed” anchor date that conforms to your financial year/quarters, and then define a range of relative periods based on that (“current fin quarter”, “previous fin quarter” etc).

Lars is working on an “anchor date” construct for 2.21 - I have no other details, but I suspect you might be able to somehow panel-beat that construct into something that would work.

That said - a more generic solution for all kinds of “financial” periods, where the financial year in theory can start at any month, would be that you use generic names for such financial years/quarters for processing BUT where the start of the financial year is a relative period offset specified for each database (for Ethiopia +11 or -2) and the fin period names are user-defined (displayName). Not sure if that’s ever been considered.

Regards
Calle

···

On 3 September 2015 at 16:19, Seid Hussein seid.hisp@gmail.com wrote:

Hi all,

We have a unique requirement here in Ethiopia. We have 13 months with the first 12 having 30 days each and the 13th one having 5 or 6 depending on leap year. Since data about the 13th month is moved to the first month of the next year (even when collected manually), we did not face any problems regarding that.

But we are facing a challenge in defining quarters. The fiscal year of Ethiopia starts in month 11 of the last year, effectively making quarter I happen in two different years. However, DHIS2 does not handle such quarters.

Have any of you faced these kind of challenges in other implementations in other countries? If so, how did you handle it?

Your comments and suggestions are appreciated.

Regards,

Seid,


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19119

Email: calle.hedberg@gmail.com

Skype: calle_hedberg


There are Java based libraries out there that deal with atypical calendars Buddhist, Coptic, Ethiopic, Gregorian etc, See: http://www.joda.org/joda-time/ which is super-interesting if you’re fascinated by date systems. But this would probably a significant feature request for developers.

S

···

On Thu, Sep 3, 2015 at 3:19 PM, Seid Hussein seid.hisp@gmail.com wrote:

Hi all,

We have a unique requirement here in Ethiopia. We have 13 months with the first 12 having 30 days each and the 13th one having 5 or 6 depending on leap year. Since data about the 13th month is moved to the first month of the next year (even when collected manually), we did not face any problems regarding that.

But we are facing a challenge in defining quarters. The fiscal year of Ethiopia starts in month 11 of the last year, effectively making quarter I happen in two different years. However, DHIS2 does not handle such quarters.

Have any of you faced these kind of challenges in other implementations in other countries? If so, how did you handle it?

Your comments and suggestions are appreciated.

Regards,

Seid,


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Steven Uggowitzer

eSHIfT Partner Network, Entuura Ventures Ltd

Tel: +41 22 366 1920

Mob: +41 79 719 4180

Skype: fendant123

LinkedIn: http://ch.linkedin.com/in/stevenuggowitzer

1 Like

Good morning Seid,

I don’t have to much experience with DHIS2 itself, but would it be a solution for you to use your own attributes for reporting periods when entering data?

I have seen this in other BI systems, where they’d think of a reporting period not as something that has to be derived from a specific date-attribute during aggregaton, but rather as a hierarchy of periods, which is defined by the customer (I have seen financial years with 16 months for overlapping quarters …). During data entry you would then enter the reporting period rather than the date. During aggregation later on on you would aggregate on your hierarchies of your custom period attribute as on any other attribute, bypassing the DHIS2 date-functions. As an example this could be distinct fields for each level of your hierarchy of reporting periods (e.g year = {2015, 2016 …}, quarter = {Q1, Q2, …}, month = {13, 01,02 … 12}, since DHIS2 only provides hierarchies on the OrgUnit. You could use validation rules, to ensure, that only valid combinations are entered.

Not sure, whether this is practical with DHIS2 - I’m proposing this also because I want to hear from others if it is :slight_smile:

Greetings,

Uwe

···

On 3 September 2015 at 16:19, Seid Hussein seid.hisp@gmail.com wrote:

Hi all,

We have a unique requirement here in Ethiopia. We have 13 months with the first 12 having 30 days each and the 13th one having 5 or 6 depending on leap year. Since data about the 13th month is moved to the first month of the next year (even when collected manually), we did not face any problems regarding that.

But we are facing a challenge in defining quarters. The fiscal year of Ethiopia starts in month 11 of the last year, effectively making quarter I happen in two different years. However, DHIS2 does not handle such quarters.

Have any of you faced these kind of challenges in other implementations in other countries? If so, how did you handle it?

Your comments and suggestions are appreciated.

Regards,

Seid,


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp


Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19119

Email: calle.hedberg@gmail.com

Skype: calle_hedberg


1 Like