Data Management
Summary
Period table in Data Management - non-calendar year applicationsContent
Has anyone else had this issue? We have an application with a fiscal year of July-June. When Data Management created the period table, it mapped all the periods to the incorrect year.
Example
July 2017 through June 2018 should map to FY18, but the period table has the target period as FY17. This is consistent for all years. We have to manually correct everything which is time consuming since the app was set up with 20 years of periods.
Screen shot shows July 22 - June 23 mapping to FY22
Tagged:
0