Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
Options
G/L Entry Already Exist
navuser1
Member Posts: 1,329
Dear Sir,
I have received the error message "G/L Entry Already Exist" in NAV 2013 R2 IN Version Database.
I assume that the error occurs when two user (or more) are posting Sales Invoice constantly.
Scenario
User A manually creates Sales Invoice & post them. User B (me) is using Batch Posting process to post the Sales Invoices.
User B faces some times the error message " G/L Entry Already Exist ".
Posting routings are modified, but I believe that modifications are not responsible for that type of error message.
Kindly help me.
I have received the error message "G/L Entry Already Exist" in NAV 2013 R2 IN Version Database.
I assume that the error occurs when two user (or more) are posting Sales Invoice constantly.
Scenario
User A manually creates Sales Invoice & post them. User B (me) is using Batch Posting process to post the Sales Invoices.
User B faces some times the error message " G/L Entry Already Exist ".
Posting routings are modified, but I believe that modifications are not responsible for that type of error message.
Kindly help me.
Now or Never
0
Comments
assuming that the standard IN release doesn't have this error and it's not something from W1, then the modifications in CU12 most certainly are responsible for this error. W1 appears to be pretty safe and doesn't produce this error. My money would be on the changes in CU12.
with best regards
Jens
with best regards
Jens
What is important: If you don't feel up to the task, get help from an experienced NAV developer. Make a review of the code changes you want to introduce. CU12 is sensitive stuff, errors can have real consequences to the accounting of the customer.
with best regards
Jens