Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Purchase Invoice #### already exists
Ms10Key
Member Posts: 13
Hi All,
My client (v5.0 SQL) receives the following error while posting a Purchase Journal, "Purchase Invoice #### already exists". I have reviewed the G/L Entry Table and the Purchase Invoice Header Table and did NOT find the related Document No. I also reviewed the No. Series which recorded the Last No. Used as 2 numbers BEFORE the number that errored. Also, we are using a Posting No. Series on the batches because multiple users have their own journals. Because the batch lines were each in balance, the batch posted up to the line with the error and then stopper. There are a few lines remaining in the journal. Other clients have complained about similar issues and we were not able to replicate the issue. Any ideas? Thanks for you assistance. ](*,)
My client (v5.0 SQL) receives the following error while posting a Purchase Journal, "Purchase Invoice #### already exists". I have reviewed the G/L Entry Table and the Purchase Invoice Header Table and did NOT find the related Document No. I also reviewed the No. Series which recorded the Last No. Used as 2 numbers BEFORE the number that errored. Also, we are using a Posting No. Series on the batches because multiple users have their own journals. Because the batch lines were each in balance, the batch posted up to the line with the error and then stopper. There are a few lines remaining in the journal. Other clients have complained about similar issues and we were not able to replicate the issue. Any ideas? Thanks for you assistance. ](*,)
0
Comments
1. Some modifications in the code
2. Check the External Document No field for duplicates.
If the user deletes their ZUP does the issue go away ?