Transcript Warehouse Enhancements NAV

Warehouse Enhancements NAV 2013
Philippe Jacobsen, Senior Program Manager
2013: Focus on Integration
Base work – Enhancement of
Integration to Manufacturing
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)
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
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
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”
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
Defaulted Bin Structure
 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.
Output from Production NAV 2009
 Location with WMS (directed Put-away & Pick)
 Simplicity...
Output from Production NAV 2013
 Location with WMS (directed Put-away & Pick)
 Flexibility...
 Combination of manual update and/or default setup
DEMO
New Areas – Assembly and Service
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
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.
Integration with Assembly
 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.
 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 ToAssembly bin will be grabbed
first by the create pick
algoritm without creating a
pick (a mini overpick scope).
Integration with Service (& Job)
Integration with service
 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)
Other Efforts
First let’s start by some Refactoring
 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.
 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
Visibility – Fact boxes
 FactBox for Warehouse Pick, Put-Away, etc
‒ Lot Quantity per Bin, using query
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
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
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.
Automated Data Capture System
(ADCS)
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
NAV 2009 Implementation
User setup
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.
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
Setup ADCS users
Summary
Create Invt. Movement – Summary
Location with Invt. Pick (Bin + Pick)
Source Documents to Invt. Pick:
 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]
Source Documents to Invt.
Movement:
 Rel. Production Order/Comp.
Lines [new]
 Rel. Asmb. Order/Asmb. Order
Lines (ATS & ATO) [new]
 Rel. To Pick Service Order/Lines
[V8 candidate]
Create Pick – Summary
Location with WMS (directed Put-away & Pick)
Source Documents to Whse.
Shipment:
 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]
Documents acting as Whse. Source
Document:
 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
Functionality
Bin
Bin
+ Pick/Puta
Refactoring, Qty available to Pick
Bin
+ whse Ship/Rec.
+ whse Pick/Put-a.
WMS
Directed Put-a.
& Pick
Yes
Yes
Inventory Movement and Internal Movement
Yes
Yes
Dedicated Bin
Yes
Yes
Default bin in production and outbound flow
Comp.Lines/RPO lines-MC-WC-Location
Yes
Yes
Release-to-Ship Serv. O. Lines
Integration with Asmb. Order
Yes
Yes
Yes
Yes
Visualization of Lot per Bin factbox using query
Yes
Yes
Yes
Yes
Refurbishment ADCS (Web Services, NAS on NST, user setup)
Yes
Candidate for V8
”Flushing” components for Asmb. Order
V8
V8
V8
Release-to-Move Serv.O.Lines
V8
V8
V8
Invt. movement for Serv.O.Lines
V8
V8
N/A
Integration to Job
V8
V8
V8
Additional Item Tracking Scenarios
* Counting
V8
V8
V8
Questions?
[email protected]
Thank You!
© 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.