Fiscal Calendar Coverage¶

New in 5.66.1. Applies to companies whose fiscal years are defined year by year in Company Settings → Calendar...**

Two fiscal years ahead¶

The fiscal date columns (Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year) cover two fiscal years either side of the year that holds the Pulse date. Before 5.66.1 they reached one year ahead, so a date in the year after next had no fiscal period and showed blank in reports.

Years the calendar does not define¶

When a report reaches a fiscal year that Calendar Settings does not define, PULSE Dashboard estimates it by continuing the pattern of the nearest defined year: the same number of periods, with the same lengths, starting the day after the previous year ends. A calendar whose periods are calendar months is continued in calendar months. A 4-4-5 or thirteen-period calendar is continued by the same numbers of days. Estimates reach up to 10 fiscal years past the last defined year, and are never saved into the calendar.

Before 5.66.1 a missing year was treated as January to December. The days between the end of the last defined year and the following 1 January belonged to no fiscal period, and calendar months were labeled as fiscal periods, so on a 4-4-5 calendar 2027-08 meant August rather than fiscal period 8.

A year missing from between two defined years is not estimated, because an estimate would overlap the years on either side. Dates in that year have no fiscal period, and show blank in reports, until the year is added.

When a refresh uses an estimated year¶

A refresh that used an estimated year says so on the status bar when it finishes, for example:

Refresh complete. Fiscal year 2028 is not defined in Calendar Settings and has been estimated - figures covering those dates are provisional. Add the year in Calendar Settings.

An alert titled Calendar horizon reached names the years as well, and closes by itself after 20 seconds. It is not a message box, so a refresh run by the Pulse Scheduler never stops to wait for a click.

Calendar Settings shows its coverage¶

Below the years, Calendar Settings shows:

Covered: the dates the defined years cover
the fiscal years reports use, and the year that holds the Pulse date
Not defined: years in that range the calendar lacks, which PULSE Dashboard will estimate
Missing between defined years: years that cannot be estimated

OK checks the calendar before saving. Duplicate years, a year with no year number or no periods, years with different numbers of periods, and gaps or overlaps between periods or years are listed, and the calendar is not saved until they are fixed. A calendar that is only short of the range reports use asks whether to save anyway.

The check that required the two previous calendar years to be defined has been removed. It read the workstation's clock and compared calendar years with fiscal year numbers.

Keep the next two fiscal years defined

Add each fiscal year in Calendar Settings before the Pulse date comes within two years of it, so reports never depend on an estimate.

Two calendar fixes were issued in the same revision; see Bug Fixes:

the quarter of periods 10 to 13 in a thirteen-period year
the months on the On-time Shipping Graph