1. Warehouse Enhancements NAV 2013 Philippe Jacobsen, Senior Program Manager

2. 2013: Focus on Integration Base work – Enhancement of Integration to Manufacturing

3. Pick to production - …-2009 R2
Location with Bin and Inventory Pick/Put-A.
Mix of roles: Warehouse posts production consumption or Production registers warehouse activities
Not able to set aside items for dedicated activities
Not able to have a document for movements (use reclass. jnl)

4. Pick or move to production NAV 2013
Location with Bin and Inventory Pick/Put-A.
 No mix of roles;  Ability to set aside items for dedicated activities
Invt. Movement document available for planning and handling
Process with existing Inventory pick ”co-exists”
 Requires separate posting of Consumption Journal

5. 4/11/2017 5:14 PM
Pick to Production ….. – 2009 R2
Location with WMS (directed Put-away & Pick)
 No mix of roles
Ability to set aside items for dedicated activities (POC lines)
Bin Type Code (QA) takes items out of ”Qty Available to Pick”
Not able to over-pick and set aside
MICROSOFT CONFIDENTIAL. Distribution Only to Partners Under Nondisclosure. Microsoft makes no warranties, express or implied. ©2009 Microsoft Corporation."

6. Pick or move to production NAV 2013
Location with Bin and Inventory Pick/Put-A.
Dedicated: bin content is not available for pick
 Dedicated Bin boolean added to Bin and Bin Content
 Bin content is available for posting, e.g. Sales posting remove item from any dedicated bin...
 You can reserve items on a dedicated Bin...
NB: WMS – existing functionality: Bin Type Code takes items out of ”Available to Pick Qty”

7. 4/11/2017 5:14 PM
Pick to Production ….. – 2009 R2
Location with WMS (directed Put-away & Pick)
 No mix of roles
Ability to set aside items for dedicated activities (POC lines)
Bin Type Code (QA) takes items out of ”Qty Available to Pick”
Not able to over-pick and set aside
MICROSOFT CONFIDENTIAL. Distribution Only to Partners Under Nondisclosure. Microsoft makes no warranties, express or implied. ©2009 Microsoft Corporation."

8. Defaulted Bin Structure
4/11/2017 5:14 PM
Default: to fill the POC lines with indication to where place goods
 Prioritized default for POC lines: Machine Center, Work Center, Location Card.
 For each Machine or Work Center a ”To-Production”, ”From-Production”, and an ”Open Shop Floor Bin” can be assigned.
 Integration with routings: To-Production bin is for first operation, From-Production is for last operation, OSFB is for all automatic flushing and respects the Routing Link Code.
MICROSOFT CONFIDENTIAL. Distribution Only to Partners Under Nondisclosure. Microsoft makes no warranties, express or implied. ©2009 Microsoft Corporation."

9. Output from Production NAV 2009
4/11/2017 5:14 PM
Output from Production NAV 2009
Location with WMS (directed Put-away & Pick)
 Simplicity...
MICROSOFT CONFIDENTIAL. Distribution Only to Partners Under Nondisclosure. Microsoft makes no warranties, express or implied. ©2009 Microsoft Corporation."

10. Output from Production NAV 2013
4/11/2017 5:14 PM
Output from Production NAV 2013
Location with WMS (directed Put-away & Pick)
Flexibility...
Combination of manual update and/or default setup
MICROSOFT CONFIDENTIAL. Distribution Only to Partners Under Nondisclosure. Microsoft makes no warranties, express or implied. ©2009 Microsoft Corporation."

11. DEMO

12. New Areas – Assembly and Service

13. Integration with Manufacturing
Summary
Inventory Movement document
Allow for stage bin for inventory pick lovations
Establish a more flexible defaulting system
Flexible Outbound flow – back to warehouse

14. Integration with Assembly
All warehouse configurations supported
ATS flow, easy:
To Assembly: Invt. movement, Warehouse pick
From Assembly: Post Assembly to a default bin, warehouse processes pick it up from there
ATO flow, more difficult:
Only one posting - this implies that components are available prior ”auto-consuming”
Default bins widely used
To-Assembly Bin: Inventory movement, Asmb lines bin code
From-Assembly Bin: Default per location card or change on Asmb. Header.

15. Integration with Assembly
Known limitations – Candidate for V8
No flow like Open Shop Floor Bin are suported – a pick needs to be registered for every assembly BOM item.
Solution concept: Items moved to the default To- Assembly bin will be grabbed first by the create pick algoritm without creating a pick (a mini overpick scope).
Mixed ATS and ATO flow, difficult:
Designed so that both flows are defined on one sales order line. This meets customer requirements for efficient sales order tracking and price calculation and limitations of ERP solutions (like create two lines one ATS and one ATO) does not surface.
The solution includes certain rules about the sequence of operation, e.g. to ship the ATO quantity before the inventory quantity.

16. Integration with Service (& Job)
Service order Lines is now a source doc for the warehousing system (similar to Production Order Component lines)
Only Release-to-Ship functionality
Only for WMS
Service and Job – Candidates for V8
Release-to-Move functionality no whse shipment but whse pick to dedicated service bin (WMS)
Inventory movement to dedicated service bin (Invt. Pick locations)
Start up on integration with Job (V8)

17. Other Efforts

18. First let’s start by some Refactoring
Location ”Orange” – White without Directed Put-Away and Pick
Added default bins and made some adjustments to avoid errors when two bins are equal on take and place lines.
Added to all tests
Refactoring of integration between Reservation and Quantity available to Pick.
”Reserved Pick and Ship Qty.” field replaced by a function
Clarification of concepts with ”Qty. available to Reserve” and ”Qty. Allocated in Warehouse”
”Qty. Available to Pick” has been thoroughly tested.

19. Visibility – Fact boxes
FactBox for Warehouse Pick, Put-Away, etc
Lot Quantity per Bin, using query

20. Item Tracking Item Tracing
” Your team did a great job! The time is so much faster, the report so much cleaner.” a partner
” Exponential redundant records are fixed.  Awesome Job!!!” Escalation Engineer Scenario with transfers and production, Before: Item Trace No Components = 831 lines Item Trace with ALL Components = 5,480 lines After: Private Fix No Components = 52 lines Private Fix with ALL Components = 60 lines

21. Item Tracking - Reservation
One critical scenario with deletion of Whse. pick
Sales Order has no IT
Whse. Ship created, no IT,
Whse. Pick created, IT gets specified, register
IT synchronized with Sales Order
Delete Whse Shipment and possible partial Whse Pick, IT sticks to the new Whse Shipment
2013: possibility to delete IT populated by pick from sales order.
Ability to remove reservations before creating negative adjustments
Several bug fixes

22. Profiles Yet to come all work related to creating profiles.
This has a big impact for WMS stakeholders that don’t have to change the default settings at each installation or upgrade.

23. Automated Data Capture System (ADCS)

24. Reasons to technical change
Platform changes that impacted the ADCS solution
No Com support on the Server
Socketbus adapter, ComCom
Discontinued Database Users
Classic Application server => NAS on NST
Goals for refactoring:
Simplifying installation
Performance

25. NAV 2009 Implementation
User setup

26. NAV 7 Implementation
True Queue optimization: tasks gets assigned to first available NST, not like 2009 Round Robin implementation where tasks are sloted and might wait for a time out if waiting for a long task.

27. Installation and Setup
Install the additional ADCS components – VT100
VT100 changes
web.config file – specifies the location of the web service
Multiple Service tiers setup in the Web.config file
Changed Queue-mechanism to central queue
Create and publish ADCS Web Service – exposing Code Unit 7714
Create the users that needs access through the handheld device
Setup the warehouse employee needs to be set for using ADCS
All other NAV specific settings are as usual
Still not supporting Warehouse scenarios with dialog boxes that requires user interaction such as warnings if the Bin Capacity Policy is set to Prohibit more than Max Capacity
Note Upgrade path :Upgrade steps
Uninstall old – and install new components (Vt100)
Existing warehouse users are upgraded
New ADCS users needs to linked to the warehouse users
Expose the webservie
And they are up and running

28. Setup ADCS users

29. Summary

30. Create Invt. Movement – Summary Location with Invt. Pick (Bin + Pick)
Source Documents to Invt. Pick:
Source Documents to Invt. Movement:
Rel. Sales Order
Rel. Transfer Order
Neg Qty on Rel. Purchase Order
Rel. Return Purchase Order
Rel. Sales Order with Asmb. Order (ATO) [new]
Rel. To Ship Service Order [V8 Candidate]
Rel. Production Order/Comp. Lines [new]
Rel. Asmb. Order/Asmb. Order Lines (ATS & ATO) [new]
Rel. To Pick Service Order/Lines [V8 candidate]

31. Create Pick – Summary Location with WMS (directed Put-away & Pick)
Source Documents to Whse. Shipment:
Documents acting as Whse. Source Document:
Rel. Sales Order
Rel. Transfer Order
Neg Qty on Rel. Purchase Order
Rel. Return Purchase Order
Rel. Sales Order with Asmb. Order (ATO) [new]
Rel. To Ship Service Order [new]
Rel. Whse. Shipment (including ATO lines)
Rel. Production Order/Comp. Lines
Rel. Asmb. Order/Asmb. Order Lines (ATS & ATO) [new]
Rel. To Pick Service Order/Lines [V8 candidate]
Visible for Pick Worksheet

32. Bin + whse Ship/Rec. + whse Pick/Put-a. WMS Directed Put-a. & Pick
Functionality
Bin
Bin + Pick/Put-a
Bin + whse Ship/Rec. + whse Pick/Put-a.
WMS Directed Put-a. & Pick
Refactoring, Qty available to Pick
Yes
Inventory Movement and Internal Movement
Dedicated Bin
Default bin in production and outbound flow Comp.Lines/RPO lines-MC-WC-Location
Release-to-Ship Serv. O. Lines
Integration with Asmb. Order
 Yes
Visualization of Lot per Bin factbox using query
Refurbishment ADCS (Web Services, NAS on NST, user setup)
Candidate for V8
”Flushing” components for Asmb. Order V8
Release-to-Move Serv.O.Lines
Invt. movement for Serv.O.Lines
N/A
Integration to Job
Additional Item Tracking Scenarios * Counting

33. Questions? pjacobse@microsoft.com

34. Thank You!

35. © 2011 Microsoft Corporation. All rights reserved
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Microsoft Dynamics, and the Microsoft Dynamics logo are trademarks of the Microsoft group of companies. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.