Period mapping is not populating correctly after creating a Planning module application

Summary: Period mapping is not populating correctly after creating a Planning module application

Content (required):

We have created a new Planning Module application, with First Month of Fiscal Year as January and Start & End year as 2017 and 2032. (Refer to the below screenshot.) Post application creation, when we checked the Period mapping in Data Integration, for Jan-16 it was populated wrongly as FY17. Ideally, it should be populated as FY16.

We have also validated the Oracle documentation and found it to be aligned. I am curious whether we created anything wrongly.

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):