End of Day Statement Posting Error

haseeb1812
Member Posts: 8
We are using NAV Classic Client with LS Retail Integration.
"Posting Date is not within your range of allowed posting dates in Item Journal Line Journal Template Name='',Journal Batch Name='',Line No.='0'."
I was getting this message on posting one End of Day statement.Every thing seem normal but nothing was normal.I searched for the solution,could not find one write answer for my case.
I struggled a lot to find the solution on my own and wanted to help people who has same problem.
The problem was the transaction from POS replaced the old transactions in HO database,you may be wondering how is this possible.
Yes !!! it is ,In LS Retail POS- functionality profile if you are using Back Date transaction 'ON' and setting Number of days transaction exist,then you need to be very careful for this.If a POS is not used for long time the old transactions gets purged and the Transaction No.Counter sets to 1 and again when you start using the same POS the transactions replaces the old transactions in HO database.
In my case the old sales transaction was replaced by Tender declaration transaction and tables Trans.Sales Entry,Trans.payment entry which has the same transaction no.will be searching for the header and already the transaction was posted with the same no. before.
Best Regards,
Abdul Haseeb.
"Posting Date is not within your range of allowed posting dates in Item Journal Line Journal Template Name='',Journal Batch Name='',Line No.='0'."
I was getting this message on posting one End of Day statement.Every thing seem normal but nothing was normal.I searched for the solution,could not find one write answer for my case.
I struggled a lot to find the solution on my own and wanted to help people who has same problem.
The problem was the transaction from POS replaced the old transactions in HO database,you may be wondering how is this possible.
Yes !!! it is ,In LS Retail POS- functionality profile if you are using Back Date transaction 'ON' and setting Number of days transaction exist,then you need to be very careful for this.If a POS is not used for long time the old transactions gets purged and the Transaction No.Counter sets to 1 and again when you start using the same POS the transactions replaces the old transactions in HO database.
In my case the old sales transaction was replaced by Tender declaration transaction and tables Trans.Sales Entry,Trans.payment entry which has the same transaction no.will be searching for the header and already the transaction was posted with the same no. before.
Best Regards,
Abdul Haseeb.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions