Wednesday 17 February 2016

Warehouse Terminology

What is Bin?

A bin is a storage device designed to contain discrete parts. It is the smallest container unit in Microsoft Dynamics NAV.

What is Bin Content?

Item quantities in bins are referred to as bin content. A lookup from the Item field or Bin Code field on any warehouse-related document line displays the calculated availability of the item in the bin.

A bin content can be given a property of Fixed, Dedicated, or Default to define how the bin content can be used. Bins with none of these properties are referred to as floating bins.

What dose Fixed Bin means?

A fixed bin holds items that are assigned to the bin code.

The Fixed bin property ensures that even if the bin content is momentarily emptied, the bin content does not disappear, and the bin is therefore selected again as soon as it has been replenished.

What dose Dedicated Bin means?

A dedicated bin holds bin content that can only be picked for the dedicated resource, such as a machine center, that uses the bin.

Other non-pick content, such as quantities outbound on a shipment posting, can still be consumed from a dedicated bin.

Only bin content considered by the Create Pick algorithm is protected in a dedicated bin.

What are Default Bins?

The Default bin property is used by the system to suggest bins for warehouse activities. At WMS locations, the Default bin property is not used.

At locations where bins are required, the property is used in inbound flows to specify where to place items. In outbound flows, the property is used to specify where to take items from.

Rule for Bin preference

If the outbound items are placed in several bins, then items are first taken from the non-default bins, to empty that bin content, and then the remaining items are taken from the default bin. There can only be one default bin per item per location.

What are the Bin Types?

You can restrict the warehouse activities that are allowed for a bin by assigning a bin type to it.

Below are the bin types in Navision:































Type Description
RECEIVEItems posted as received but not yet put away.
SHIPItems picked for warehouse shipment lines but not yet posted as shipped.
PUT AWAYTypically, items are stored in large units of measure but you do not want to access for picking purposes.

These bins are not used for picking, either for production orders or shipments, this bin type could be useful if you have purchased a large quantity of items.

Use of these type of bin might be limited.

Bins of this type should always have a low bin-ranking, so that when received items are put away, other higher-ranking PUTPICK bins fixed to the item are put away first.

These type of bins should regularly perform bin replenishment so that the items stored in these bins are also available in PUTPICK or PICK type bins.
PICKUsed for picking only.

The replenishment of these bins can only be made by movement, not by put-away.
PUTPICKBins that are suggested for both the put-away and pick functions.

Bins of this type probably have different bin rankings.

You can set up your bulk storage bins as this type of bin with low bin rankings compared to your ordinary pick bins or forward picking area bins.
QCThis bin is used for inventory adjustments if specified on the location card in the Adjustment Bin Code field.

You can also set up bins of this type for defective items and items being inspected.

You can move items to this type of bin if you want to make them inaccessible to the usual item flow.

The QC bin type has none of the item handling check boxes selected by default.

Any content you place in a QC bin is excluded from item flows.

For all bin types, except PICK, PUTPICK, and PUTAWAY, no other activity is allowed for the bin than what is defined by its bin type.

Only movement can be made to bins of type RECEIVE and QC. Similarly, only movements can be made from bins of type SHIP and QC.

What dose Bin Ranking means?

In advanced warehousing, you can automate and optimize how items are collected in put-away and pick worksheets by ranking bins so that items are suggested taken or placed according to rank criteria to use warehouse space optimally.

  • Put-away processes are optimized according to bin ranking by suggesting higher-ranking bins before lower-ranking bins.

  • Pick processes are optimized by first suggesting items from bin content with high bin ranking.

  • Bin replenishments are suggested from lower-ranking bins to higher-ranking bins.


Bin ranking together with bin content information are the basic properties that allow users to slot items in the warehouse.

How are Bin Setup?

Bins can be set up with capacity values, such as quantity, total cubage, and weight to control which and how items are stored in the bin.

On each item card, you can assign a unit of measure (UOM) for the item, such as pieces, pallets, liters, grams, or boxes.

If you want to set a maximum quantity of a specific item to be stored in an individual bin and the item has more than one UOM, then you must set the maximum quantity for every UOM that exists on the item card.

If an item has been set up to be handled in pieces and pallets, then the Max. Qty. field in the Bin Content window for that item must also be in pieces and pallets.

Allowed quantity for that bin is not calculated correctly if above rule is not followed.

In order to set capacity restrictions for bin contents on a bin, UOM and dimensions of the item must be set up on the item card.

What is Zone?

In advanced warehousing, bins can be grouped in zones to manage how the workflow of warehouse activities is directed.

A zone could be a receiving zone or a stocking zone, and each zone can consist of one or several bins.

Most properties assigned to a zone will by default assigned to the bin that is created from that zone.

What are Classes?

In advanced warehousing, you can assign warehouse class codes to items, bins, and zones to control where different item classes are stored, such as frozen goods.

You can divide a zone into several warehouse classes.

When you work with warehouse classes and a default receiving/shipping bin, you must manually fill in the appropriate bins in the warehouse receipt and shipment lines.

In inbound flows, the class code is only highlighted on inbound lines where the item class code does not match the default receiving bin. If the correct default bins are not assigned, then the quantity cannot be received.

What does Location refer to?

A location is a physical structure or place where inventory is received, stored, and shipped, potentially organized in bins. A location can be a warehouse, service car, showroom, plant, or an area in a plant.

What is First Expired First Out setup?

If you select the Pick According to FEFO check box on the Bin Policies FastTab on the location card, then item-tracked items are picked according to their expiration date. Below rule applies while picking the item:

  • The items with the earliest expiration dates are picked first.

  • Warehouse activities in all pick and movement documents are sorted according to FEFO, unless the items already have serial/lot numbers assigned.

  • If only a part of the quantity on the line already has serial/lot numbers assigned, then the remaining quantity to be picked is sorted according to FEFO.

  • When picking by FEFO, the available items that expire first are gathered in a temporary item tracking list based on the expiration date.

  • If two items have the same expiration date, then the item with the lowest lot or serial number is picked first.

  • If the lot or serial numbers are the same, then the item that was registered first is selected first.


What is Put-away Template?

The put-away template can be assigned to an item and to a location.

The put-away template specifies a set of prioritized rules that must be respected when creating put-aways.

Monday 15 February 2016

Warehouse Overview

One of my reader have demanded a Warehouse related query, before jumping to the solution I thought to have a brief overview regarding this topic. As I have not covered this topic in my past posts, so I will be posting couple of posts on this series as and when I get some time and the answer will be in these couple of posts.

Each transactions performed using warehouse is stored in a Warehouse Register.

For each transaction or movement in the warehouse is recorded in Warehouse Entry table.

Warehouse Documents and Warehouse Journal are used to register item movements in the warehouse.

Whenever an item in the warehouse is moved, received, put away, picked, shipped, or adjusted, Warehouse Entries are registered to store the physical information about zone, bin, and quantity

The Bin Content table is used to handle all the different dimensions of the contents of a bin per item, such as unit of measure, maximum quantity, and minimum quantity.

Below is the typical Warehouse Flow:

Flow Diagram

Basic UI Documents

  • Inventory Put-away

  • Inventory Pick

  • Inventory Movement

  • Item Journal

  • Item Reclassification Journal


Advanced UI Documents

  • Warehouse Receipt

  • Put-away Worksheet

  • Warehouse Put-away

  • Pick Worksheet

  • Warehouse Pick

  • Movement Worksheet

  • Warehouse Movement

  • Internal Whse. Pick

  • Internal Whse. Put-away

  • Bin Creation Worksheet

  • Bin Content Creation Worksheet

  • Whse. Item Journal

  • Whse. Item Reclass. Journal


 

Below are the warehouse-related granules in Navision:

  • Basic Inventory (4010)

  • Bin (4170)

  • Put Away (4180)

  • Warehouse Receipt (4190)

  • Pick (4200)

  • Warehouse Shipment (4210)

  • Warehouse Management Systems (4620)

  • Internal Picks and Put-aways (4630)

  • Automated Data Capture System (4640)

  • Bin Setup (4660)


 

Granules Vs  UI Documents:

The following table shows which granules are required to define different warehouse complexity levels, which UI documents support each level.













































Complexity level Description UI document Minimum granule requirement
1No dedicated warehouse activity.

Receive/ship posting from orders.
OrderBasic Inventory
2No dedicated warehouse activity.

Receive/ship posting from orders.

Bin code is required.
Order, with bin codeBasic Inventory/Bin
3Basic warehouse activity, order-by-order.

Receive/ship posting from inventory put-away/pick documents.

Bin code is required.
Inventory Put-away/Inventory Movement/Inventory Pick, with bin codeBasic Inventory/Bin/

Put Away/Pick
4Advanced warehouse activity, for multiple orders.

Consolidated receive/ship posting based on warehouse put-away/pick registrations.
Warehouse Receipt/Warehouse Put-away/Warehouse Pick/Warehouse Shipment/Pick WorksheetBasic Inventory/

Warehouse Receipt/

Put Away/

Pick/

Warehouse Shipment
5Advanced warehouse activity, for multiple orders.

Consolidated receive/ship posting based on warehouse put-away/pick registrations.

Bin code is required.
Warehouse Receipt/Warehouse Put-away/Warehouse Pick/Warehouse Shipment/Pick Worksheet/Put-away Worksheet, with bin codeBasic Inventory/Bin/

Warehouse Receipt/

Put Away/Pick/

Warehouse Shipment
6

This level is referred to as “WMS”, since it requires the most advanced granule, Warehouse Management Systems.
Advanced warehouse activity, for multiple orders.

Consolidated receive/ship posting based on warehouse put-away/pick registrations.

Bin code is required.

Zone/class code is optional.

Warehouse workers directed by workflow.

Bin replenishment planning.

Bin ranking.

Bin setup by capacity.

Slotting.

Hand-help device integration.
Warehouse Receipt/Warehouse Put-away/Warehouse Pick/Warehouse Shipment/Warehouse Movement/Pick Worksheet/Put-away Worksheet/Internal Whse. Pick/Internal Warehouse Put-away, with bin/class/zone code

Various worksheets for bin management

ADCS screens
Basic Inventory/Bin/

Put Away/

Warehouse Receipt/

Pick/

Warehouse Shipment/

Warehouse Management Systems/

Internal Picks and Put-aways/

Bin Setup/

Automated Date Capture System/

Bin Setup

I will come up with more details in my next post.

Tuesday 9 February 2016

Cumulative Update 4 for Microsoft Dynamics NAV 2016 has been released on 5th Feb 2016

Cumulative Update 4 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2016.

 

Additional Information


For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2016 Cumulative Update.

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2016.

 

You can check for complete details here : https://blogs.msdn.microsoft.com/nav/2016/02/05/cumulative-update-4-for-microsoft-dynamics-nav-2016-has-been-released/

Cumulative Update 16 for Microsoft Dynamics NAV 2015 has been released on 5th Feb 2016

Cumulative Update 16 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015.

 

Additional Information


For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2015 Cumulative Update.

For information about how to work around a recent process change, see How to Get Back the ‘Hotfix Directories’ from NAV 2015 Cumulative Update 1.

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2015.

 

You can check for complete details here : https://blogs.msdn.microsoft.com/nav/2016/02/05/cumulative-update-16-for-microsoft-dynamics-nav-2015-has-been-released/

Cumulative Update 28 for Microsoft Dynamics NAV 2013 R2 has been released on 5th Feb 2016

Cumulative Update 28 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2.

 

Additional Information

For more information about cumulative updates for this version, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2013 R2.

For a list of all hotfixes included in cumulative updates for this version, see the following CustomerSource and PartnerSource pages:

CustomerSource:

PartnerSource

 

 

You can check for complete details here : https://blogs.msdn.microsoft.com/nav/2016/02/05/cumulative-update-28-for-microsoft-dynamics-nav-2013-r2-has-been-released/

Cumulative Update 35 for Microsoft Dynamics NAV 2013 has been released on 5th Feb 2016

Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013Cumulative Update 35 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013.

Additional Information

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2013.

For a list of all hotfixes included in cumulative updates for this version, see the following CustomerSource and PartnerSource pages:

CustomerSource:

PartnerSource:

You can check for complete details here : https://blogs.msdn.microsoft.com/nav/2016/02/05/cumulative-update-35-for-microsoft-dynamics-nav-2013-has-been-released/