Views:

Applies to Product - Dynamics 365 Finance
 

What’s happening?
An error message stating "XXXX period does not exist for the associated business date YYYY" occurs during retail transactions and financial postings, despite the fiscal calendar being available.
 

Reason:
Caching in Batch does not pick up the latest record, leading to the incorrect belief that there is no target record for the fiscal period.
 

Resolution:
To resolve the error regarding the fiscal period:

  1. Validate that a fiscal period is set up for the period being used by going to General ledger> Ledger setup> Ledger> Ledger calendar and check periods in corresponding legal entity. Additionally you can execute the following SQL query if you prefer: sql select p.* from FISCALCALENDARPERIOD p join FISCALCALENDAR c on c.RECID = p.FISCALCALENDAR join FISCALCALENDARYEAR y on y.RECID = p.FISCALCALENDARYEAR where c.CALENDARID = 'CALENDAR_ID' and y.name = 'YEAR_NAME'
  2. If a period does exist, the issue is likely due to caching in Batch. Restart the batch server to ensure the latest records are picked up. Here you can find more details: Batch processing and batch servers - Finance & Operations | Dynamics 365 | Microsoft Learn
  3. If a period does not exist, the error is expected and must be addressed by configuring the fiscal periods before posting. For that, go to General ledger> Ledger calendars> Fiscal calendars. Select the calendar defined in Ledger page and click on +New year button to create new fiscal year. Additional details at Fiscal calendars, fiscal years, and periods - Finance | Dynamics 365 | Microsoft Learn