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
- 304 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
Problem with stuck transfer order
Kisu
Member Posts: 381
Our client made a transfer order and it seemed that they accidentally deleted the shipment. (Drilled down on the shipped quantity and deleted)
The shipped quantity stayed on the transfer order lines but when you drill down on it it does not show the shipment anymore..
Changing the shipped quantity to zero, deleting the transfer order is not a solution as the inventory value stays and the Lot No is still attached to the Item No.
Fixing this around with item journal does not seems to work, it gives error about item variations.
Nav build is 6.00.32012, does anyone know if there is hotfix for this issue and hopefully a good solution to get this fixed.
br
K.S.
The shipped quantity stayed on the transfer order lines but when you drill down on it it does not show the shipment anymore..
Changing the shipped quantity to zero, deleting the transfer order is not a solution as the inventory value stays and the Lot No is still attached to the Item No.
Fixing this around with item journal does not seems to work, it gives error about item variations.
Nav build is 6.00.32012, does anyone know if there is hotfix for this issue and hopefully a good solution to get this fixed.
br
K.S.
K.S.
0