Posting Date Issue for Internal Batch Job (Adjust Cost - Item Entries)
navuser1
Member Posts: 1,334
Dear Sir,
The End Users are restricted through Allow Posting From & Allow Posting To in User Setup Table. The Automatic Cost Posting is ticked in Inventory Setup Master Table. For this reason (?) sometimes Users are facing the error message like ...06-06-2019 is not within the range of posting dates for your company. while posting any Item related Transaction.
The System is trying to post any cost but can't do the same due to Allow Posting From & Allow Posting To restrictions in User Setup Table.
I just want that system should allow those transactions (backdated) which are happening internally (system generated entries).
How to avoid this type of issues in the future?
Please suggest your best!
Thanks,
Navuser1
The End Users are restricted through Allow Posting From & Allow Posting To in User Setup Table. The Automatic Cost Posting is ticked in Inventory Setup Master Table. For this reason (?) sometimes Users are facing the error message like ...06-06-2019 is not within the range of posting dates for your company. while posting any Item related Transaction.
The System is trying to post any cost but can't do the same due to Allow Posting From & Allow Posting To restrictions in User Setup Table.
I just want that system should allow those transactions (backdated) which are happening internally (system generated entries).
How to avoid this type of issues in the future?
Please suggest your best!
Thanks,
Navuser1
Now or Never
0
Answers
-
I don't know if the accountants will be happy when they find out that GL entries have been created in a closed year. But I know what you mean. On the other hand, you want the entries to be date wise as close as possible to the entries they result from. I remember writing code once that used the first allowed posting date (user wise) when the posting date was too far in the past. We used a NAS user to process the job.1
-
I don't know if the accountants will be happy when they find out that GL entries have been created in a closed year. But I know what you mean. On the other hand, you want the entries to be date wise as close as possible to the entries they result from. I remember writing code once that used the first allowed posting date (user wise) when the posting date was too far in the past. We used a NAS user to process the job.
Thanks for your reply.
I will provide sufficient date range in the User Setup table if the User is executing the NAV Batch Job in NAS so that he can not fall in trouble in this kind of situation.
But my situation is different.Now or Never0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
