"Save Failed:  Ambiguous Fiscal Year" Message

CBISA™ active fiscal years are set with a calendar year as the default.  Therefore, if your active fiscal year starting and ending dates are not equal to a calendar year, you will have overlapping months from one year to the next.  If you receive the following message you should align your fiscal year dates- "Save Failed": Ambiguous Fiscal Year.  To correct the misaligned fiscal dates, follow the steps below.
 
1.  Change the active fiscal year from the dropdown in the upper right hand corner to the previous year (i.e., if you were entering data in 2016 when you received the error, activate 2015).
2.  Access the reporting unit financial default screen (Options/Org Defaults/Reporting Unit/Financial).  You may also select the appropriate year from the financial default screen.
3.  Update the beginning and ending fiscal dates for the activated year. Save your changes and close out of Org Defaults
4.  Reactivate your current active fiscal year, and re-enter the information on the dated record.
5.  All future years will automatically be correctly aligned.
 
As an example, your fiscal year runs from July to June.  You are entering information into CBISA™ for the first time in active year 2016.  You have correctly set your 2016 fiscal year dates to 7/1/2015 (beginning) to 6/30/2016 (ending).  You try to save an occurrence record with a date of 7/31/2015 and you receive the "Save Failed": Ambiguous Fiscal Year error.  To properly align the fiscal years and remove the overlapping 2015 dates, you first set the active year to 2015 (or select 2015 from the reporting unit financial screen), then edit the financial screen to show the correct fiscal dates 7/1/2014 (beginning) to 6/30/2015 (ending) thus removing the overlapping date range.  You are now able to save the occurrence with the date of 7/31/2015 without error.