Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Bob Bergman]

 

 

 

When posting a Dynamics NAV consumption journal I occasionally get the unexpected error  “Posting Date is not within the allowed date range”.  Journal batch = ‘blank’ and line = ‘0000’.

 

Automatic Cost Posting = TRUE

Adjust Cost = Always

 

The only work around is to set the User date range to Allow Posting From = ‘blank’

 

Has anyone else experienced this error?  Do you know of a Hotfix?

 

 Bob

——————————
Bob Bergman
President
REB Dynamics Consulting
Port Charlotte FL
——————————

[Bob Bergman]

Should have mentioned that I am running NAV 2016

——————————
Bob Bergman
President
REB Dynamics Consulting
Port Charlotte FL
——————————
——————————————-

[Joe Shields]

After you run the transaction with the user posting dated set to blank, what is the date of your posted transaction? is it outside if the dates that are set and you have to remove?

Maybe you can try using the debugger next time you get this to see what date it is trying to use.

——————————
Joe Shields
Advanced Media Technologies
——————————
——————————————-

[Bob Bergman]

Hi,

I have tried the debugger with no success.  I have also run the Item Journal Line table to make sure there were no ‘blank’ records there.

——————————
Bob Bergman
President
REB Dynamics Consulting
Port Charlotte FL
——————————
——————————————-

[Jon Long]

Hey Bob,

I can’t resist attempting to help you resolve an issue. you are usually the one helping me. 🙂

It looks like a phantom journal line is either created, or perhaps accidentally entered? That explains why ‘blank’ works in setup, since blank implies infinity, which may also allow a blank date on the line itself. Not sure.

——————————
Jon Long
Developer and Tech Lead for Upgrades
ArcherPoint Inc.
GA
——————————
——————————————-

[Bob Bergman]

The resulting posting dates are correct when posted.

——————————
Bob Bergman
President
REB Dynamics Consulting
Port Charlotte FL
——————————
——————————————-

[Bob Bergman]

——————————
Bob Bergman
President
REB Dynamics Consulting
Port Charlotte FL
——————————
——————————————-

[Ian Ray]

I’m not sure if this directly relates to your situation, but I have had this exact error message if the G/L Setup posting range is larger than the User Setup posting range and Adjust Cost is on.

Example:

G/L Setup posting range = 3/1/17 to 4/30/17
User Setup posting range = 4/1/17 to 4/30/17

User tries to post some inventory transaction: “Posting Date is not within your range of allowed posting dates in Item Journal line Journal Template Name=”,Journal Batch Name=”,Line No.=’0′

The only ways I have found around this are

• Move User Setup posting range back
• Move G/L Setup posting range forward
• Turn off Adjust Cost

——————————
Ian Ray
Cypress Grove
Arcata CA
——————————
——————————————-

[Meenakshi Singh]

Hi Bob,

If user posting date range is limited then it might be trying to post some entries behind the scenes in the wider date range that will generate this error. I have usually seen it happening during adjust cost posting which on my setup is also turned on as – Always.

So, try increasing the posting date range for the user and that should take care of the error. You might (I haven’t had success always in finding the culprit on this but most of the time it works) be able to figure out which entry was causing the date error for you after navigating the posted entry for cost adjustments.

Good luck, Meenakshi

——————————
Meenakshi Singh
Manager of Business Applications
Home Market Foods, Inc.
Norwood MA
——————————
——————————————-

[Thomas (Tom) Blaisdell]

Hi Bob and all,

Sorry for not posting sooner. I was out with family on school spring break.  Everyone has hit on the key challenges here.  The Allow Posting From and To Date in General Ledger Setup must be within all of the user date ranges – i.e. it must be a narrower range than the users – if Automatic Cost Adjustment is set to anything other than Never.  If Auto Cost Adjustment is Never and Adjust Cost Item Entries batch job is run, then the date range for the user running the process will need to be broader than the General Ledger Setup.

Typically, the biggest challenge comes from a couple of scenarios that I see most often –

1 – Post a Purchase Invoice at a different Direct Cost after Receipt was posted in an earlier period. The Purchase Receipt quantity has been applied against Sales/Consumption/Negative Adj.  Automatic Cost Adjustment will result in Adjust Cost processing adjusting the negative entries based on the change in Purchase Cost on the Invoice Posting Date. However, the User Posting Date Range, if it is narrower than General Posting Setup Date Range, will cause the error because the User doesn’t have the open period available in their date range where cost adjustments are generated.

2 – Much more subtle and a bit more challenging. A user is posting a Sales/Consumption/Neg. Adj. that closes a FIFO/LIFO positive quantity  layer.  A rounding residual balance of pennies is left on the layer, so cost adjustment will push a Rounding Value Entry back to the Purchase (or other Positive Qty. Layer).  If the General Ledger Setup Posting Date range is broader than the user posting the entry with Automatic Cost Adjustment enabled, then you will see error like this.

These are not meant to be all inclusive reasons, but these are two of the more common issues I see.

The best practice is – if Automatic Cost Adjustment in Inventory Setup is enabled with a setting other than Never, then User Posting Date Ranges must be broader than the General Setup Posting Date Range.

Thanks
Tom

——————————
Tom Blaisdell
Sr. Support Escalation Engineer
Microsoft
Alpharetta GA
——————————
——————————————-

[Jason Wilder]

Ian and Meenakshi are correct.  You need to increase the range of the user running adjust cost to at least include the same range as the General Ledger Setup Allow Posting From and To range.

Adjust Cost posts based on the original transaction so there could easily be a date older than you might expect.  Adjust Cost has some code (Table 98 General Ledger Setup Function FirstAllowedPostingDate) that forces the earliest date that it can post based on the General Ledger Allow Posting From field.  This way Adjust Cost is able to post entries that normally would fall into a closed period.  The problem you are most likely experiencing is that it is allowable for your company but not for the specific user. 

An example I ran into the other day was:
General Ledger Setup 03/01/17 to 04/03/17
User running Adjust Cost 03/31/17 to 04/30/17

Error:

So I fixed this by changing General Ledger Setup from 04/01/17 to 04/30/17 (now the User encompasses more than General Ledger Setup)

Please note though that by changing the General Ledger Setup side of things there would have been an entry that would have posting before 03/31/17 that now is forced to a new date of 04/01/17 (see bold comment above).

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————
——————————————-