Picking logic
generic
Member Posts: 511
Hello
Can somebody explain to me the Picking logic for NAV. Especially when you have reservation. The code looks ugly/complicated. Is there a document on this? Does it look at ILE only or warehouse entry as well? What if they are out of sync?
Thanks.
Can somebody explain to me the Picking logic for NAV. Especially when you have reservation. The code looks ugly/complicated. Is there a document on this? Does it look at ILE only or warehouse entry as well? What if they are out of sync?
Thanks.
0
Comments
-
The ILE and Warehouse Entry should always be in sync. The ILE does not carry warehouse location (Zone/Bin) information, therefore is not applicable to the picking process. The exact logic sequence of the picking process is dependent on your system setup and feature implemented. The picking is based on the Bin Contents table with appropriate filters applied. The Bin Contents table uses flowfields to various tables (Warehouse Entry, Warehouse Document Lines, etc.) to calculate available quantity for picking. The ILE table is not used. The logic runs thru the filtered set until an appropriate quantity is found or the end is reached.There are no bugs - only undocumented features.0
-
I have to disagree with you. If you are using reservation.
Lets say sales order has qty 20. you've reserved 10 only. And you do a positive warehouse journal adjustment 10, and then try to create a pick
Nav will create only 10. Even when you do sync ILE with warehouse entry, it still creates a pick for 10.
Is there a documentation on this?0 -
What does the positive journal adjustment have to do with the reservation? The ILE and warehouse entry are still (and should be) in sync. Let's say I have 1000 cases in stock. The ILE will tell me what locations they are in, and how many, and cost. The warehouse entry will tell me what bins they are in. If I apply the same filter set to both tables I should get the same quantity results. The only exception would be if I'm in the middle of a physical inventory. But that difference would be offset by the adjustments bin.There are no bugs - only undocumented features.0
Categories
- All Categories
- 73 General
- 73 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
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 333 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