Picking Strategy in WM
Picking Strategy in WM
Table of Contents
Table of Contents
Application
Putaway Strategies:
B - Bulk storage
C - Open storage
F - Fixed bins
Removal Strategies:
Customising:
Technical:
Useful Hints:
Provide the most efficient search technique for storage bins in the
warehouse.
Control indicators: defined for putaway and picking per storage type in
order to provide specific putaway or removal control per storage type.
Putaway Strategies:
- Manual stock placement
No strategy is used.
You cannot use mixed storage without Storage Unit management for bulk
storage.
You can indicate in the Storage type control screen whether partial
pallets are allowed to be placed in the storage type.
Please note, for cases where partial pallet management is not allowed, you
must define a pick point storage type in the stock removal storage type for
the remaining quantities. Pick point storage types cannot be bulk storage
types; they must have putaway strategy Q
(See below for more details).
For cases where bulk storage is defined with mixed storage indicator
X partial pallet management must also be allowed.
Block Structures: For bulk storage types you can define Block
Structures in the Strategy for bulk storage customizing transaction.
For bulk storage with storage units, you need to define:
How many storage units will fit into a block (or row).
C - Open storage
The mixed storage indicator should be used for all open storage types.
Usually, one or more open storage sections are defined for open
storage type. Then one mixed storage bin is defined per section.
F - Fixed bins
Defined in the material master and for all putaways of this material the
system determines the fixed bin.
The user can override the fixed bin determination and enter a manual
bin.
The addition to stock indicator must be flagged so that quants can be added
to.
If a user tries to add a material without a fixed storage bin into a fixed
storage bin, the system will issue an error message.
System will search firstly for a storage bin where the material can be
added to an existing quant.
If there are no bins in the storage type with the same material or
enough capacity, then the system will switch to strategy Next Empty Bin
(see below).
Material must be exactly the same as the material in the bin in order to be
added to the quant, for example, If the material is batch managed, the
material to be added, must be from the same batch as the material which
already exists in the bin. (See SAP help on Definition of a quant)
Its not recommended to use addition to stock if you want a First in First out
principle in the warehouse, as FIFO requires that you keep track of Goods
Receipt dates.
The Goods Receipt date field is stored on the Quant (LQUA) table, with
addition to stock you are adding new stock all the time to the quant, so the
goods receipt date will not be unique to each movement.
It important with this strategy that the storage bin structure is correct.
The system will first try to search for the nearest bin in the column
(stack) where the fixed bin is located, working from the bottom up, if no bin
is found here, then the system will search to the right of the bin and then to
the left (rows).
The system will search within the storage type for the next empty bin.
With this putaway strategy, you can section off the storage type for
different SUTs.
It is important define capacity checks and storage bin types and also
check the SUT check flag in the control indicators for the strategy.
You can define bin sections in the customizing transaction for strategy
P.
When creating storage bins, you must also define the storage bin type. When
setting up bin sectioning each section will have a key (usually A, B, C for
example) you can define more than one SUT for each key, thus allowing
different type of pallets to be stored in one bin. The following illustrates this:
Each time stock is moved to the storage type a dynamic bin (using the
quant number with leading zeros) is created.
For this reason its mostly used in conjunction with a relevant ID point
storage type.
Removal Strategies:
- No stock removal strategy (Stringent FIFO across all storage
types)
You can leave the entry for stock removal strategy blank and
additionally add the wildcard characters *** to the relevant storage type
search which will allow the system to search for the oldest quant in the entire
warehouse.
Standard storage unit types must be used for stock placement (i.e.
where a specific number per pallet has been defined in the material master
WM tab).
The partial quantity in a storage unit must be less than the standard storage
unit quantity.
defined in the palletisation data for the defined for the standard
relevant storage unit type storage unit type
Situations where quants exist which contain more stock than the standard
storage unit type should not occur.
With this stock removal type, 4 specific rules are followed in order to ensure
optimum management of stock in the storage type:
required If no required No partial storage
quantity in standard quantity in unit quantities are
the transfer storage the transfer available
order is the units are order is < the
=> quantity available quantity of
of a standard the standard
storage unit storage unit
System will propose the oldest quant in the storage type for picking
(using the GR date to define the oldest quant).
every goods receipt posting from IM the goods receipt date will be
adopted by the transfer requirement, at transfer order creation this field is
copied to the quant table (LQUA) and stored with the quant.
Each time new stock is added to a quant the GR Date is updated, so
this picking strategy alone may not be suitable for perishable goods.
Works from the same general principle as FIFO except that instead of
the GR date used to identify the oldest quant, a SLED (Shelf Life Expiration
Date) is used instead.
There are 2 ways that the SLED date is retrieved for the transfer order
creation providing the requirements above are fulfilled.
From the batch record For materials which are batch managed the
SLED date is kept in the batch record and cannot be changed in WM.
Also use the SLED for stringent FIFO. In customizing you define that the
system should search for the oldest quant by SLED in the entire warehouse.
Cases you can have a storage type with fast-moving and slow-moving
items in the storage bins (same or different materials).
The fast moving items are stored on top of already stored slow-moving
items and will be required first. For this situation the LIFO (Last In First Out)
storage strategy is used.
The last quant placed in storage will be proposed for picking for the
next transfer order.
M - Large/small quantities included (Cascading Storage)
If the material can be sold in pallets, boxes and pairs and all are stored
in the same warehouse, it may make sense to use this strategy.
So, using the example above, you could set up 3 different storage
types one each for Large, Medium and Small quantities.
The illustration below shows an example of this strategy using two storage
types:
System will propose the fixed bin storage type if the quantity to be picked is
less than or equal to the control quantity in the material master.
A fixed bin, which has been maintained for a storage type in the
warehouse, is defined in the material master as the picking storage bin.
Each time this material is to be picked the system will propose this
storage bin. As with the placement strategy, users can override the proposal
and enter a different bin.
Customising:
Customising for stock placement and stock removal strategies is added at
storage type level. Whatever strategy has been defined here is applicable to
all bins in that particular storage type.
The relevant customising menu paths are as follows:
> Menu-path for storage type definition:
IMG > Logistics Execution Warehouse Management > Master Data >
Storage Type Definition
> Menu-path for storage type search:
IMG > Logistics Execution > Warehouse Management > Strategies >
Activate Storage Type Search
> Menu-path for material master:
Logistics > Logistics Execution > Master Date > Material > Material >
Display
In here on the WM1 tab, you can view if specific stock placement or removal
indicators have been added which will further influence the storage type
search strategy used.
Technical:
LQUA Quant table
LAGP Storage bin table
T331 Storage type control table
T331B Storage type control for bulk storage
T331L Storage classes allowed per storage type
Useful Hints:
During TO creation, after the system has proposed a bin, you can see how
the system came to the proposal by going to the top menu bar and selecting
option:
Environment
This menu path can only be accessed during TO creation not during TO
display (LT21) or TO confirm/cancel (LT12, LT11, LT15).
Putaway:
Implementation Options
The putaway process includes putting goods away in storage bins in the
warehouse. There are putaway strategies in the Warehouse Management
(WM) system that simplify the search for appropriate storage bins.
Regardless of how your company executes the putaway process, you can
make settings in the system so that goods are put away:
Automatically when you create inbound deliveries
Routinely at certain times
Manually according to overviews of the day's workload that a co-worker has
requested
A putaway status is recorded in each delivery item for the purpose of
scheduling and monitoring the putaway process. This status indicates what
stage the item is at in the putaway process (putaway has started for item A,
for instance).
Prerequisites
In the system standard settings, it is a prerequisite for goods receipt to be
posted before the item relevant for putaway can be put away completely.
This means that the delivery quantity must be the same as the putaway
quantity in the inbound delivery.
The Warehouse Management system (WMS) module is fully integrated in
Logistics Execution (LE). For example, you can create a WM transfer order
directly from the inbound delivery. The current status of the warehouse
management process can also be monitored from the delivery, for instance.
Process flow
Putaway with Warehouse Management allows you to use the transfer order
as a putaway order.
This is possible in the following scenarios:
Lean-WM
Implementation of the basic functions of the Warehouse Management
module (WM) in simply structured warehouses with no stock management at
storage bin level.
Implementation of all functions in Warehouse Management (WM)
The use of the WM transfer order as a putaway order offers you the following
advantages:
Determination of target data for transfer orders
Splitting transfer orders according to target data
Printing transfer orders or transmitting them in IDoc format
Creation of actual data from the putaway
Confirming transfer orders
Picking :
Implementation Options
The picking process involves taking goods from a storage location and
staging the right quantity in a picking area where the goods will be prepared
for shipping.
Range of Functions
Regardless of how your company executes the picking process, you can
make settings in the system so that picking is carried out
Automatically during Outbound Delivery Creation
Routinely at certain times
Manually according to overviews of the day's workload that an employee has
requested
A Picking Status is recorded in each delivery item for the purpose of
scheduling and monitoring the picking process. This status indicates where
the item is in the picking procedure (picking has started for item A, for
instance).
In the system standard settings, it is a prerequisite for goods issue to be
posted before the item relevant for picking can be picked completely.
Therefore, delivery quantity and picking quantity (picked quantity) in the
outbound delivery must be equal.
The Warehouse Management System (WMS) module is fully integrated in
Logistics Execution (LE). For example, you can create a WM transfer order
directly from the outbound delivery. The current status of the warehouse
management process can also be monitored from the delivery, for instance.
You can transfer all data relevant for picking and verification of picking data
to a subsystem by using the Delivery Interface.
By using message control, data can be transferred to a subsystem that is
being used for picking (see also: Delivery Interface).
Depending on the picking procedure being used, you can either determine
delivery-relevant data before picking or wait until after picking is completed
to record it. Delivery-relevant data may be made up of the following:
Which batches a material is picked from
Which serial numbers are picked
Which valuation types the stock is taken from