Thursday 3 March 2016

Date Deviates from Permissible Range SAP Business One

In running our business we face problems just like you do when using SAP Business One. Just today, fresh from creating posting periods for next year, our financial people were asking about the error "Date Deviates from Permissible Range" when adding a document. These documents had a due date of next year, so we were in essence using the freshly created posting periods for 2014.
The problem lies with the due dates and the default settings for creating posting periods. Very often you will have documents that require a due date that crosses the year threshold. For example in November you need to create an A/R invoice to bill a customer in January of the next year with 90 day terms.
The solution is changing the current years posting periods to be allowed to post outside of their year. This typically only affects the months of November and December and sometimes October too. So we will have to dig in and change those posting periods.
Posting Period Settings
Navigate on the main menu to:Administration -> System Initialization -> Posting Periods. Click on the yellow arrow next to the posting period of November of your current year. You'll see that the due date expressly allows up to 12/31/2013. If your customer has 60+ day payment terms this will prevent documents being added to the system while giving the "Date Deviates from Permissible Range" error.
Fixed Posting Period
To fix this issue, as a matter of course, change the "Due Date From" ending date in the months of November and December in all years. We recommend setting the date to at least March of the following year to prevent problems. With the posting period now fixed, you will be able to add documents with due dates that push into the next year.
Also, keep in mind that posting periods cannot be removed once transactions have been posted to them. If you have created posting periods with the idea of going back later to fix some things, please make sure you do this before you allow any postings into the next year.

No comments:

Post a Comment