Item Ledger dimension not carrying through to sales order
Noeline
Member Posts: 54
Hello fellow navvers
In Navision classic version 5 when a serialized item is brought into stock, the dimensions are automatically carried over on the entry when the stock goes out. This is not happening on NAV 2017. So items come in with all their dimensions specified on the entry, but when they are shipped, the dimensions need to be entered AGAIN. Problem is the user shipping, has no idea what those dimensions were/are.
Is this a setup issue? Could it be something I am doing wrong, or has this changed in NAV 2017?
Any inputs highly appreciated.
Regards - Noeline
In Navision classic version 5 when a serialized item is brought into stock, the dimensions are automatically carried over on the entry when the stock goes out. This is not happening on NAV 2017. So items come in with all their dimensions specified on the entry, but when they are shipped, the dimensions need to be entered AGAIN. Problem is the user shipping, has no idea what those dimensions were/are.
Is this a setup issue? Could it be something I am doing wrong, or has this changed in NAV 2017?
Any inputs highly appreciated.
Regards - Noeline
0
Answers
-
You mean to say Default dimensions of Items?0
-
When the item is brought into stock the dimension value is entered for that entry, and will vary from one entry to the next, for the same item. When the item goes out, I need it to use the same values as when it came in.0
-
It is not standard functionality (and in NAV 5 was not too). Generally, shipment can be applied to several inbound entries with different dimensions0
-
These items are serialized, and it IS currently working that way in NAV 5. When a pallet comes in it is assigned dimension values, which is the vessel trip number, and when it goes out, NAV uses those same values again.
It may have something to do with the fact the the NAV 5 is using warehouse entries as well. Will check that out.0 -
In standard NAV usin warehouse entries does not deal with applying by dimensions. You probably have some customization to apply by dimensions. You have to reinvent this functionality because it can coincide with FIFO/LIFO approach.0
-
0
-
@hopesuresh
We have a client on NAV 5 that carries serialized pallets in the warehouse. Costing method is Specific. When the pallets are brought in to inventory, they are assigned a 'trip no' dimension. When they are sold or removed, the system automatically carries that same dimension value over to the sale/journal entry. There is no customization to update or assign the dimension. It just happens that way. Based on that I relied on NAV 2017 working the same way for a different customer also with serialized pallets, but it does not.
I don't know if it is a setting, or if NAV 2017 just behaves differently. I suspect it's the latter.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 611 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions