NAV 2018 - Expiration Date Reclassification Creates Inconsistencies Between Tables
lesanchez
Member Posts: 2
Hello.
NAV 2018 offers the possibility to change the expiration date of items using the Warehouse Reclassification Journal, which performs an outbound and inbound movement of the item, allowing the date to be updated.
However, this feature cannot be used in the current scenario for two main reasons:
- Multiple expiration dates recorded: When performing the reclassification, the system records different expiration dates for the same lot in the Item Ledger Entry table, which prevents invoicing.
- Inconsistency in Warehouse Movement: The Warehouse Entry table is not updated with the new expiration date, resulting in discrepancies between records.
Has anyone faced this issue?
Is there any way to adjust this without causing inconsistencies between the tables?
What would be the best practice to resolve this situation?
0
Answers
-
[color=#FF0000][Topic moved from 'General Chat' forum to 'NAV Three Tier' forum][/color]
Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K 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
- 326 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