Howdy, Stranger!
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
- 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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Item Ledger Entry XXXX Already Exists Error
davisj
Member Posts: 38
We are running Navision 2.6F database and clients in a manufacturing environment and recently had some modifications made to two consumption posting programs by our Solution Center. After these modifications went into production we started to receive "already exists errors" in the posting of item ledger entries. The error messages are "Item Application Entry Entry No. 1234567 Already Exists" and "Item Ledger Entry Entry No. 1234567 Already Exist". Our Solution Center is working on the problem but we wanted to know if anyone had information about how best to research and solve this issue. The basic concept or assumption is that one Navision client is getting the sequence number for the Item Ledger Entry No. (Key) and this Key is not getting updated before another client is getting the same number. Is there something special that has to be set in the form or some variable that has to be set so the act of acquiring the sequence number for the Key will bump the sequence immediately preventing the next client from getting the same sequence number and thus giving the "already exists error"?
We have been working with our Solution Center for 2 days now and any help/thoughts would be greatly appreciated.
We have been working with our Solution Center for 2 days now and any help/thoughts would be greatly appreciated.
0
Comments
I believe that your NSC is experienced enough to find bugs and solve them.
A hint. If this happens only when two or more clients are posting at the same time, then maybe locking of proper tables before getting last record should be checked.
And it has nothing to do with some settings on form or vars...
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
There is only one area you can check that is code. Check the chages you have doen to posting. If you have written a code to create item ledger entry or item application entry then you might not have incremented the Entry no porperly. Chances are you might be using same variable in increment entry No in existing code as well as the new code written by the your developers.
Let us know if you have sorted the problem.