You are on page 1of 53

EHP3 for SAP ERP

6.0
December 2009
English

742: Warehouse and DC


Management (WM)
Building Block Configuration Guide

SAP AG
Dietmarr-Hopp-Allee 16
69190 Walldorf
Germany
Copyright
© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10,
System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400,
S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5,
POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2
Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli
and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web Consortium,
Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a
registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other
countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in
this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products
and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description


Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.

Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

© SAP AG Page 3 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Contents

1 Introduction............................................................................................................................................ 6
2 Preparation............................................................................................................................................ 6
3 Master Data........................................................................................................................................... 6
4 Customizing........................................................................................................................................... 6
4.1 Warehouse Structure................................................................................................................... 6
4.1.1 Copy Warehouse Number....................................................................................................... 6
4.1.2 Create Picking Storage Type................................................................................................... 7
4.1.3 Define Picking Areas............................................................................................................... 8
4.1.4 Create Reserve Storage Type................................................................................................. 9
4.1.5 Create Hanging Goods Storage Type (Fashion)...................................................................10
4.1.6 Create Frozen Storage Type (Food)......................................................................................11
4.1.7 Create Bulk Goods Storage Type (Hardgoods).....................................................................12
4.1.8 Define Doors......................................................................................................................... 13
4.1.9 Define Article Staging Areas.................................................................................................14
4.1.10 Define Storage Bin Types...................................................................................................... 14
4.1.11 Define Storage Bin Structure and Create Bins......................................................................16
4.1.12 Generate Interim Storage Bins..............................................................................................17
4.1.13 Maintain Field Selection for Generic Article Storage Bins....................................................17
4.2 Warehouse Procedures............................................................................................................. 19
4.2.1 Activate Storage Type Search...............................................................................................19
4.2.2 Activate Storage Section Search.......................................................................................... 21
4.2.3 Activate Storage Bin Type Search........................................................................................22
4.2.4 Define Strategy for Expiration Date......................................................................................22
4.2.5 Define Print Control............................................................................................................... 23
4.2.6 Create Replenishment for Fixed Bins...................................................................................24
4.3 Goods receipt............................................................................................................................ 25
4.3.1 Maintain and Assign Door Usage Profile...............................................................................25
4.3.2 Reasons for Date Variance.................................................................................................... 25
4.3.3 Set Expiration Date Check in Goods Receipt (Food Only)...................................................26
4.3.4 Create and Assign Partner Scheme Rough Goods Receipt..................................................26
4.4 Return Deliveries....................................................................................................................... 27
4.4.1 Check Print Indicator for the Movement Type.......................................................................27
4.5 Wave Picks (Optional)............................................................................................................... 28
4.5.1 Maintain Time of Comparison for Forming Wave Picks........................................................28
4.5.2 Maintain Wave Picks Profile.................................................................................................28

© SAP AG Page 4 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.5.3 Maintain Timeslots for Wave Picks.......................................................................................29


4.5.4 Maintain Timeslot Group for Wave Pick................................................................................30
4.5.5 Activate the Update of Info Structure for Wave Picks..........................................................30
4.6 Shipping.................................................................................................................................... 32
4.6.1 Define Item Category Determination in Outbound Deliveries...............................................32
4.6.2 Maintain Working Hours........................................................................................................ 32
4.6.3 Maintain Shipping Point........................................................................................................ 33
4.6.4 Maintain Profile for Subsequent Delivery Split.....................................................................34
4.7 Physical inventory..................................................................................................................... 36
4.7.1 Define Default Values for Physical Inventory........................................................................36
4.7.2 Define Physical Inventory Types per Storage Type...............................................................37
4.7.3 Define Bar Code Types for Physical Inventory......................................................................37
4.8 Mobile Data Entry (Optional)..................................................................................................... 39
4.8.1 Maintain RF Queue Management.........................................................................................39
4.8.2 Define Menu Management for RF......................................................................................... 40
4.9 Warehouse Activity Monitor (Optional)......................................................................................41
4.9.1 Activate Warehouse Activity Monitor Objects.......................................................................41
4.9.2 Define Critical Parameters.................................................................................................... 41
4.10 Rough Workload Estimate (Optional)........................................................................................43
4.10.1 Maintain Logistics Load Categories......................................................................................43
4.10.2 Maintain Unit-of-Measure Load Categories...........................................................................43
4.10.3 Maintain and Assign Warehouse Operations........................................................................44
4.10.4 Maintain Warehouse Workloads...........................................................................................45
4.10.5 Control Update of Workload Data.........................................................................................46
4.11 Connecting the Warehouse to a DC (Site)................................................................................48
4.11.1 Define Storage Location for WM in the DC...........................................................................48
4.11.2 Assign Warehouse Number to Site/Storage Location...........................................................48
4.11.3 Define Standard Storage Location........................................................................................ 49
4.11.4 Assign Shipping Points and Shipping Point Determination...................................................50
4.11.5 Define Storage Conditions.................................................................................................... 51
4.11.6 Define Rules for Picking Location Determination..................................................................51
4.11.7 Picking Location Determination (MALA)...............................................................................52
4.11.8 Storage Location Determination with Situation (RETA)........................................................53

© SAP AG Page 5 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

1 Introduction
Stock figures are stored in Inventory Management (IM) at storage location level. When stock keeping for
larger warehouses storage is chaotic, that means, when the same articles are stored in several places in
the warehouse and different strategies are used throughout the warehouse, the enhanced functionality of
the Warehouse Management module (WM) has to be used.
The WM module is situated underneath inventory management at storage location level and manages
stocks at storage bin level. It enables you to map complex warehouse structures, with several storage
bins for each article and different putaway and stock removal strategies, within one warehouse.
The scenario of distribution center logistics with warehouse management is based on a completely
installed WM warehouse structure, which is connected to inventory management at storage location level.
This document lists all necessary settings as well additional settings made in the article master, site
master and customizing. Unless stated otherwise, the guide settings for master data sets of
HARDGOODS, FASHION and FOOD. Differences specific to each master data set are noted at the
appropriate points in the guide.

2 Preparation
Before you start installing this building block, you must install prerequisite building blocks. For more
information, see the Building Block Prerequisites Matrix for SAP Best Practices Baseline Package.

3 Master Data
The setup of the Master Data required for the Warehouse Management Best Practice scenarios is
described in the following documents :
Generic: Configuration Guide 780
Fashion Configuration Guide 781
Food Configuration Guide 782
Hard Goods Configuration Guide 783
These documents detail the settings for the Sites (Distribution Centres), Customers, Vendors, and
Articles.
The creation of the Storage Bin master data, and an Output Condition record required for the Return
Delivery scenario, is also outlined in these documents.

4 Customizing
4.1 Warehouse Structure
4.1.1 Copy Warehouse Number
Procedure

© SAP AG Page 6 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

1. Access the activity using one of the following navigation options:


IMG Menu Enterprise Structure  Definition  Logistics Execution  Define,
Copy, Delete, Check Warehouse Number Copy/delete/check
warehouse number
Menu IMG Estrutura do empreendimento  Definição  Logistics Execution
 Definir, copiar, eliminar, verificar nº do depósito  Copiar,
eliminar, verificar nº do depósito
Transaction Code EC09

2. Choose Copy
3. Check/enter your settings.
4. In From Warehouse no. enter '001'
5. In To Warehouse no. enter PC1'

Background:
The copied warehouse number forms the foundation for the definition of an own warehouse. Building onto
a copied warehouse number is less complex than the creation of a new warehouse.

Remarks:
Subsequently the description of the warehouse number should be changed.
IMG  Enterprise Structure  Definition  Logistics Execution  Define, Copy, Delete, Check
Warehouse Number Define warehouse number
Warehouse number description 'PC1': 'Central whse PCS (WM)'
Also change the Region code if required.
IMG  Logistics Execution  Warehouse management  Hazardous materials  Master data  Define
Region Codes
IMG  Logistics Execution  Warehouse management  Hazardous materials  Strategies  Activate
Hazardous material management
Button [Warehouse number]
Assign a region code to the Warehouse

4.1.2 Create Picking Storage Type


Prerequisites
PCS warehouse number exists

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master data
 Define Storage Type
Logistics Execution  Warehouse Management  Master data 
Define Storage Sections

© SAP AG Page 7 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Menu IMG Logistics Execution  Administração de depósitos  Dados


mestre  Definir tipo de depósito
Logistics Execution  Administração de depósitos  Dados mestre
 Definir zonas de armazenagem
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

Storage type: K01


Description: Picking Storage PCS
SU mgmt active flag
SUT check active flag
Mixed Storage X
Stck removal strategy P

WhN Typ S... Storage area name


PC1 K01 001 Fast-moving items
PC1 K01 002 Slow-moving items

Background:
K01 maps a picking area with flat goods. The characteristic value is individual (for example, shelf). Per
bin, multiple articles or variants of a generic article can be stored (Mixed storage). Putaway is according
to fixed bin; pick according to expiry date (food) or FIFO.
Storage sections allow for division of a storage type into multiple areas. For example, dividing the picking
area in a fast turnaround area (easy to reach bins / short paths) and slow turnaround area (hard to reach
bins / long paths). During the creation of the storage bins, they must be assigned a storage section.
Therefore, even if the storage type is not to be divided, a storage section ‘entire section’ must be created.

Remarks:
Additional storage types can be created in an analogous way.

4.1.3 Define Picking Areas


Prerequisites
PCS warehouse numbers and PCS storage types must exist

Procedure

© SAP AG Page 8 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

1. Access the activity using one of the following navigation options:


IMG Menu Logistics Execution  Warehouse Management  Master Data 
Define Picking Areas

Menu IMG Logistics Execution  Administração de depósitos  Dados mestre


 Definir áreas de picking

Transaction Code SPRO


2. Choose New Entries or copy existing
3. Check/enter your settings.
PC1 K01 001 Picking Area 1
PC1 K01 002 Picking Area 2
PC1 K01 003 Picking Area 3

Background:
Picking areas are used when a delivery is to be processed by various pickers who work in specific areas
of the picking warehouse (for example, one passage). Picking areas are one of the criteria for sorting and
splitting of transport orders.

4.1.4 Create Reserve Storage Type


Prerequisites
PCS warehouse number exists.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master data 
Define Storage Type
Logistics Execution  Warehouse Management  Master data 
Define Storage Sections
Menu IMG Logistics Execution  Administração de depósitos  Dados
mestre  Definir tipo de depósito
Logistics Execution  Administração de depósitos  Dados mestre 
Definir zonas de armazenagem
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

1.
Storage type: R01
Description: Reserve Storage PCS
SU mgmt active: flag

© SAP AG Page 9 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Mixed storage: X
Capacity check method: '2'
Full stk rmvl reqmt act.: unflag
Return stock to same storage bin: unflag
Stck rmvl strategy: 'H'
2.
WhN Typ S... Storage area name
PC1 R01 001 Fast-moving items
PC1 R01 002 Slow-moving items

Background:
'R01' is a reserve warehouse with palette places (for example, high rack warehouse). If needed, goods
can be moved to the picking area K01. A pallet assembled as much as possible from one article in goods
receipt is put away here completely (Mixed storage is possible so that variants of generic articles can be
stored). The putaway is done according to the “free space” strategy; pick according to expiry date (food)
or FIFO.
Storage sections allow for division of a storage type into multiple areas. For example, dividing the picking
area in a fast turnaround area (easy to reach bins / short paths) and slow turnaround area (hard to reach
bins / long paths). During the creation of the storage bins, they must be assigned a storage section.
Therefore, even if the storage type is not to be divided, a storage section ‘entire section’ must be created.

Remarks:
Additional storage types can be created in an analogous way.

4.1.5 Create Hanging Goods Storage Type (Fashion)


Prerequisites
PCS warehouse number exists.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master data
 Define Storage Type
Logistics Execution  Warehouse Management  Master data 
Define Storage Sections
Menu IMG Logistics Execution  Administração de depósitos  Dados
mestre  Definir tipo de depósito
Logistics Execution  Administração de depósitos  Dados mestre
 Definir zonas de armazenagem
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

© SAP AG Page 10 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Storage type: H01


Description: Hanging Goods Storage PCS
Dst bin ch. During confirm '1'

WhN Typ S... Storage area name


PC1 H01 001 Fast-moving items

Background:
Hanging goods with direct put away and pick. The goods are posted to a dummy bin by the system during
put away; during the confirmation of the put away, the bins actually used can be entered. The bin
selection is up to the employee (basically manual put away). Bins can be mixed as needed; there is no
capacity check.
Storage sections allow for division of a storage type into multiple areas. During the creation of the storage
bins, they must be assigned a storage section. Therefore, even if the storage type is not to be divided, a
storage section ‘entire section’ must be created.

Remarks:
Additional storage types can be created in an analogous way.

4.1.6 Create Frozen Storage Type (Food)


Prerequisites
PCS warehouse number exists

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master data 
Define Storage Type
Logistics Execution  Warehouse Management  Master data 
Define Storage Sections
Menu IMG Logistics Execution  Administração de depósitos  Dados
mestre  Definir tipo de depósito
Logistics Execution  Administração de depósitos  Dados mestre 
Definir zonas de armazenagem
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

1. Storage type: 'F01'


Description: 'Frozen Goods Storage PCS'
SU mgmt active: flag

© SAP AG Page 11 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

SUT check active: flag


Mixed storage: 'X'
Stck rmvl strategy: 'H'

WhN Typ S... Storage area name

PC1 F01 001 Total section

Background:
Frozen storage with direct putaway and pick. Putaway according to fixed bin; pick according to expiry
date.
Storage sections allow for division of a storage type into multiple areas. During the creation of the storage
bins, they must be assigned a storage section. Therefore, even if the storage type is not to be divided, a
storage section ‘entire section’ must be created.

Remarks:
Additional storage types can be created in an analogous way.

4.1.7 Create Bulk Goods Storage Type (Hardgoods)


Prerequisites
PCS warehouse number exists.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master data
 Define Storage Type
Logistics Execution  Warehouse Management  Master data 
Define Storage Sections
Menu IMG Logistics Execution  Administração de depósitos  Dados
mestre  Definir tipo de depósito
Logistics Execution  Administração de depósitos  Dados mestre
 Definir zonas de armazenagem
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

Storage type: B01


Description: Bulk Goods Storage PCS
Dst bin ch. During confirm '1'

© SAP AG Page 12 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

WhN Typ S... Storage area name


PC1 B01 001 Total section

Background:
Large goods storage for bulky goods with direct putaway and pick. Storage sections allow for division of a
storage type into multiple areas. During the creation of the storage bins, they must be assigned a storage
section. Therefore, even if the storage type is not to be divided, a storage section ‘entire section’ must be
created.
Storage sections allow for division of a storage type into multiple areas. During the creation of the storage
bins, they must be assigned a storage section. Therefore, even if the storage type is not to be divided, a
storage section ‘entire section’ must be created.

Remarks:
Additional storage types can be created in an analogous way.

4.1.8 Define Doors


Prerequisites
PCS warehouse numbers and PCS storage types must exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master Data 
Define Doors
Menu IMG Logistics Execution  Administração de depósitos  Dados mestre 
Definir portões

Transaction Code SPRO

2. Select New Entries or Select existing entry and Copy as …

Whse Door Text for Door Artl staging area GI GR CD ind FT ind
no ind. ind.
PC1 T01 Gate 1 (GR) x
PC1 T02 Gate 2 (GR) x
PC1 T03 Gate 3 (GI) x
PC1 T04 Gate 4 (GI) x
3. Check/enter your settings.

Background:
Example structure for the creation of doors.
A door and staging area determination has not been implemented in PCS.

© SAP AG Page 13 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.1.9 Define Article Staging Areas


Prerequisites
PCS warehouse numbers and doors must exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master Data 
Define Article Staging Areas
Menu IMG Logistics Execution  Administração de depósitos  Dados mestre 
Definir zonas de disponibilização
Transaction Code SPRO

2. Select New Entries or Select existing entry and Copy as …

Whse no. Artl staging area Text Door


PC1 Z01 Zone 01 (GR) T01
PC1 Z02 Zone 02 (GR) T02
PC1 Z03 Zone 03 (GI) T03
PC1 Z04 Zone 04 (GI) T04
3. Check/enter your settings.

Background:
Example structure for the creation of article staging areas.
A door and staging area determination has not been implemented in PCS.

4.1.10 Define Storage Bin Types


Prerequisites
PCS warehouse number must exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master Data 
Storage Bins  Define Storage Bin Types
Menu IMG Logistics Execution  Administração de depósitos  Dados mestre 
Posições no depósito  Definir tipos de posição no depósito
Transaction Code SPRO

© SAP AG Page 14 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

2. Select New Entries or Select existing entry and Copy as …


3. Choose enter
4. Check/enter your settings.
Whse no Stor.Bin Type Descr.
PC1 B1 Block size 1
PC1 B2 Block size 2

PC1 E1 Bin height 1 meter


PC1 E2 Bin height 2 meters
PC1 P1 Bin height 3 meters

Background:
You can divide your storage bins into groups (for example, large storage bins, small storage bins, and so
on). A suitable storage bin is proposed by the system during stock placement in combination with the
storage unit type.

© SAP AG Page 15 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.1.11 Define Storage Bin Structure and Create Bins


Prerequisites
PCS warehouse number, -types, -sections and picking areas must exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Master Data  Storage
Bins  Define Storage Bin Structure
Menu IMG Logistics Execution  Administração de depósitos  Dados mestre 
Posições no depósito  Definir estrutura das posições no depósito
Transaction Code LS10
2. Choose Create Structure
3. Select New Entries or copy existing structure
4. Choose new structure and Choose Detail
5. Specify storage area, picking area and area type
6. Choose Create storage bin areas
7. (in detail view of area structure) Menu: Choose Environment  Create bins
8. Choose Create Online
9. Check/enter your settings.
WhN Typ. SqNo Template Structure Start Val. End Value Increment

PC1 001 001 CCCNNCNNCC AA BB 01-01-01 01-10-10 01-01-01


PC1 001 002 CCCNNCNNCC AA BB 02-01-01 02-10-10 02-01-01
PC1 B01 001 NNCNNNCCCC AA BBB 01-001 20-020 01-001
PC1 F01 001 NNCNNNCCCC AA BBB 01-001 20-020 01-001
PC1 H01 001 NNCNNNCCCC AA BBB 01-001 20-020 01-001
PC1 K01 001 CCCCNNCNNN AA BBB KOM-01- KOM-07-020 KOM-01-001
001
PC1 K01 002 CCCCNNCNNN AA BBB KOM-01- KOM-07-050 KOM-01-001
021
PC1 K01 003 CCCCNNCNNN AA BBB KOM-08- KOM-14-050 KOM-01-001
021
PC1 K01 004 CCCCNNCNNN AA BBB KOM-08- KOM-14-020 KOM-01-001
001
PC1 K01 005 CCCCNNCNNN AA BBB KOM-15- KOM-21-020 KOM-01-001
001
PC1 K01 006 CCCCNNCNNN AA BBB KOM-15- KOM-21-050 KOM-01-001
021
PC1 R01 001 NNCNNCNNCC AA BB CC 01-01-01 04-10-10 01-01-01
PC1 R01 002 NNCNNCNNCC AA BB CC 05-01-01 10-10-10 01-01-01

© SAP AG Page 16 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Background:
The storage bin structure specifies the structure of the numbering of the storage bins, for example,
sequential numbering, passage/level, 3D coordinates, etc. During creation all the bins defined within the
structure are created automatically. Single bins may be deleted as long as they are not occupied by
merchandise.

4.1.12 Generate Interim Storage Bins


Prerequisites
PCS warehouse number and storage types must exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse management  Interfaces 
Inventory Management  Generate Interim Storage Bins
Menu IMG Logistics Execution  Administração de depósitos  Interfaces 
Administração de estoques  Gerar posições no depósito interface
Transaction Code LX20

2. Generate interim storage bins for warehouse number 'PC1'.


3. In the warehouse number, enter 'PC1'

Background:
Some interface storage types do not use dynamic storage locations or cannot create these when goods
movements without references are posted. For this a interim storage bin has to be created to take up the
moved quants.
Example: Storage bin IN-ZONE of storage type 902 (GR area external rcpts) takes up inbound goods
which where created without reference to an order (Movement type 501).

Remarks:
The names of the interface storage types are defined in the WM movement type.
IMG  Logistics Execution  Warehouse management  Activities  Transfers  Define Movement
Types  Button [Detail]

4.1.13 Maintain Field Selection for Generic Article Storage Bins


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics - General à Material Master à Field Selection à Assign
Fields to Field Selection Groups
Menu IMG Logística geral à Mestre de materiais à Seleção de campos à
Atribuir campos a grupos de seleção de campos
Transaction Code OMSR

© SAP AG Page 17 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

2. Choose field name,


3. Choose Details
4. Check/enter your settings.
5. For field enter, 'MLGT-LGPLA' (Storage Bin) maintain the following settings:
6. In Propose field cont, enter 'X'
7. In Restrict artl cat,.enter Default only for variants'
8. Copy field content, enter 'X'

Background:
These settings mean that a storage bin maintained for the header article will be copied to the variants of a
generic article.
In this way, all variants of a generic article are in the same picking bin at first.

© SAP AG Page 18 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.2 Warehouse Procedures


4.2.1 Activate Storage Type Search
4.2.1.1 Define the Storage Type Indicator
Prerequisites
PCS warehouse number and storage types exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Strategies  Activate
Storage Type Search
Menu IMG Logistics Execution  Administração de depósitos  Estratégias  Ativar
determinação tipo depósito
Transaction Code OMLY
2. Choose Storage type ind. [Define]
3. Select New Entries or select existing entry and [Copy as …]
4. Check/enter your settings.

WhN StorageTypeInd. Description


PC1 RES Reserve Storage
PC1 KOM Picking Storage
PC1 HNG Hanging Goods Storage (only Fashion)
PC1 FRZ Deep Freeze Storage (only Food)
PC1 BLK Bulk Goods Storage (only Hardgoods)

Background:
Storage type indicators are assigned in the article master and control the storage type search during put
away and pick of the article; ithat is, which storage type is put into or picked out of.

© SAP AG Page 19 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.2.1.2 Determine Search Sequence


Prerequisites
PCS warehouse number and storage types exist

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Strategies 
Activate Storage Type Search
Menu IMG Logistics Execution  Administração de depósitos  Estratégias 
Ativar determinação tipo depósito

Transaction Code OMLY

2. Choose Stor ty. Search Determine search sequence


3. Select New Entries or select existing entry and Copy as …
4. Check/enter your settings.
WhN Operat TypInd …W … Ref … Storage Types
PC1 A 0 0 K01 ***
PC1 A RES 0 0 R01 K01
PC1 A KOM 0 0 K01
PC1 E 0 0 R01
PC1 E RES 0 0 R01 K01
PC1 E KOM 0 0 K01 R01
PC1 A BLK 0 0 B01 (only Hardgoods)

PC1 E BLK 0 0 B01 (only Hardgoods)


PC1 A HNG 0 0 H01 (only Fashion)
PC1 E HNG 0 0 H01 (only Fashion)
PC1 A FRZ 0 0 F01 (only Food)
PC1 E FRZ 0 0 F01 (only Food)

Background:
The entries here mean that articles without a type indicator are putaway into 'R01' and picked out of 'K01',
or when not there, out of every other storage type (***).
With TypKz 'RES', 'R01' is used for putaway and pick, and when this is not successful ('R01' full during
putaway or empty during pick) 'K01' is used.
TypKz 'KOM' means that, that putaway is done into in 'K01', if 'R01' is full and pick is done out of 'K01'. If
'K01' is empty; pick is not done out of 'R01' but warehouse-internal replenishment is waited for (pick type
remains 'K01').

© SAP AG Page 20 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

'BLK' means pick and Putaway out of/into 'B01' (bulky goods).
'HNG' means pick and Putaway out of /into 'H01' (hanging goods).
'FRZ' means pick and Putaway out of /into 'F01' (frozen goods).

4.2.2 Activate Storage Section Search


Prerequisites
Warehouse number, storage types and sections exist

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Strategies 
Storage Section Search
Menu IMG Logistics Execution  Administração de depósitos  Estratégias
 Ativar determinação zona de armazenagem
Transaction Code OMLZ
2. In Storage section ind.choose Define
3. Select New Entries or select existing entry and[Copy as …
4. In Stor. section search Determine search sequence
5. Select New Entries or select existing entry and Copy as …
6. Stor. section check Activate
7. Check/enter your settings.
8. ad 1.: Maintain Storage sections '001', 'Fast moving Items' and '002' – 'Slow moving items' for
Warehouse number 'PC1'
9. ad 2.: add the following entries:
WhN Typ SecIn WPC Storage
sections
10. Ad
PC1 R01 0 001 002 3.:
PC1 R01 001 0 001 002
PC1 R01 002 0 002 001
Enter an 'X' in row 'PC1' - 'R01' in the column 'Section Check active'.

Background:
Storage section indicators are entered in the article master and control (here) the putaway of fast-selling
and slow-selling goods in the appropriate storage sections. Without an indicator or with indicator '001', a
bin in the fast turnaround area is sought; with the indicator '002', the article is slow-seller. If there is no
space in the intended area, a bin is sought in the other storage section.

Remarks:
A similar procedure would be possible for the storage type K01, but since here fixed bins are assigned per
article, a storage section check during Putaway would not be sensible.

© SAP AG Page 21 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.2.3 Activate Storage Bin Type Search


Prerequisites
Warehouse number and storage types exist

Procedure:
1. Access the activity using one of the following navigation options:
IMG Menu Execution  Warehouse Management  Strategies  Activate
Storage Bin Type Search
Menu IMG Execution  Administração de depósitos  Estratégias  Ativar
determinação tipo de posição no depósito

Transaction Code OMM1


2. Choose Definitions Storage bin types
3. Choose Definitions Storage unit type
4. Choose Assignments Storage unit types Storage type
5. Choose Assignments Storage unit types[Storage bin types

Parameters - Settings:
Maintain all settings for warehouse number 'PC1':
ad 1.: can delete storage bin types 'B1', 'B2' and 'P1' (keep pallet bin types 'E1', 'E2')
create new bin types according to storage possibilities
ad 2.: can delete storage unit type 'IP', create new SUTs as needed.
enter UM type 'C' for 'E1', 'E2' und 'GB' (for workload calculation)
ad 3.: assign the storage types 'R01', 'K01' and 'F01' (Food) to the SUT 'E1' and 'E2'.
ad 4.: maintain the following entries:
WhNo SUT Storage bin types
PC1 E1 E1 E2
PC1 E2 E2
PC1 GB E1 E2

Background:
The storage bin type search and check means that storage units are only put away into bins that can
contain them. In the example, the storage units 'GB' and 'E1' (assumed: both have a height of 1 meter)
and 'E2' (height 2m) are created. The storage bin types are 'E1' (Height 1m) and 'E2' (Height 2m). With
the storage bin type search, it must be taken care of that no 2m high storage units are put into 1m high
storage bins.

Remarks:
Examples must be adjusted to the customer specifics in the project.

4.2.4 Define Strategy for Expiration Date


Prerequisites
Warehouse number must exist

© SAP AG Page 22 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Strategies 
Stock Removal Strategies  Define Strategy for Expiration Date
Menu IMG Logistics Execution  Administração de depósitos  Estratégias
 Estratégias para saída do depósito  Definir estratégia data do
vencimento
Transaction Code OMKW
2. Expiration date management per warehouse number, Choose Activate.
3. For warehouse number 'PC1' set flag 'SLED mgmt active'

Background:
Only if the expiry date management has been activated here, the expiry date will be taken into the quant
data, which will ensure proper processing of the picking strategy function.

4.2.5 Define Print Control


Prerequisites
Warehouse number created.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Activities 
Define print control
Menu IMG Logistics Execution  Administração de depósitos  Operações 
Definir controle de impressão
Transaction Code OMLV
2. Choose Assignments Printer Warehouse movement,
3. Select New Entries or change existing entries, apply changes.
4. Choose Print control Multiple processing
5. Select New Entries or change existing entries, apply changes.
6. Check/enter your settings.
7. for 1.: maintain following entry
PC1 *** *** LP01
8. for 2.: maintain following entries
PC1 B 2 RLKOMM40 21 LP01
PC1 L 2 RLKOMM40 21 LP01

Background:
Some basic print control has to be maintained in order to run warehouse processes. All printouts are
directed to the standard printer LP01. If the printout is needed on paper, the printer LP01 has to be
defined correctly (transaction SPAD).

© SAP AG Page 23 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Remarks:
Usually, customer projects need by far more (but very specific) settings.

4.2.6 Create Replenishment for Fixed Bins


Prerequisites
Warehouse number and storage types are defined

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Activities 
Transfers  Define Stock Transfers and Replenishment Control
Menu IMG Logistics Execution  Administração de depósitos  Operações
 Transporte  Definir transferências de estoque e controle
reabastecimento
Transaction Code SPRO
2. Maintain WM Movement Types
3. Define Replenishment Control for Storage Type
4. Check/enter your settings.

Parameters - Settings:
1.:
existing entry: 'PC1' '319' 'Replen. for production'
copy as: 'PC1' '320' 'Replen. picking bin PCS'
enter following parameters: (Button [Details])
From-Type 'R01'
To-Type 'K01' set flag 'FxdBn'
Shipment Type 'A' (Pick)
Requirement Type blank
2.:
For warehouse number ‘PC1' and storage type 'K01' assign the newly created movement type '320'.

Background:
The new movement type controls the warehouse-internal replenishment of the picking bins.

Remarks:
Movement type 319 can subsequently be deleted (no production).

© SAP AG Page 24 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.3 Goods receipt


4.3.1 Maintain and Assign Door Usage Profile
Prerequisites
Doors are defined and warehouse number is defined.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Activities 
Docks  Maintain Appointment (Door Usage) Profile
Logistics Execution  Warehouse Management  Activities 
Docks  Assignment of Profile to Warehouse Number
Menu IMG Logistics Execution  Administração de depósitos  Operações
 Ocupação dos portões  Atualizar perfil de ocupação dos
portões
Logistics Execution  Administração de depósitos  Operações
 Ocupação dos portões  Atribuição perfil a sistema de
depósito
Transaction Code SPRO
2. Select New Entries or select existing entry and Copy as …
3. Choose Create Door Usage Profile 'PCS' as copy of '001'.
4. In the detail view in the sub-screen 'Possible transactions in goods receipt', set the flags 'Inb. Dlv.'
and 'Rough GR'.
5. Enter the Door Usage Profile 'PCS' for the warehouse number ‘PC1'.

Background:
The door usage should be possible not only with reference to an order, but also to a shipping notification
or rough GR.

4.3.2 Reasons for Date Variance


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Activities  Docks
 Reasons for date variance
Menu IMG Logistics Execution  Administração de depósitos  Operações 
Ocupação dos portões  Motivos de desvio da data

Transaction Code SPRO

2. Select New Entries


3. Check/enter your settings.

© SAP AG Page 25 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Deviation reason Description Party resp. Description


01 Truck late C Vendor
(Vendor)
02 Gate Busy A Own company
03 Truck late (truck) B Service agent
04 Truck too early B Service agent
Background:
Reasons for variance can be stored in the door usage planning for documentation purposes.

4.3.3 Set Expiration Date Check in Goods Receipt (Food Only)


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management  Inventory Management and Physical
Inventory  Goods Receipt  Set Expiration Date Check
Menu IMG Administração de materiais  Administração de estoques e
inventário  Entrada de mercadorias  Definir parâmetros para
verificação do prazo de vencimento
Transaction Code OMJ5
2. Choose Movement type

Parameters - Settings:
For the relevant movement types in goods receipt, set the value '1' (enter and check) in the field ‘Check
SLExpDate'. This definitely makes sense for the movement types '101' and '501'.

Background:
A expiration date check takes place in GR when 3 conditions are met:
- The exp. date entry and check must be activated for the movement type.
- The exp. date check must be activated for the site
- The article must have a remaining shelf life (from article master or purchase order)

4.3.4 Create and Assign Partner Scheme Rough Goods Receipt


Background:
Partner scheme EG is assigned to delivery type EG in delivery customizing, but not created in the
system. Therefore no rough goods receipt can be created without this setting.

© SAP AG Page 26 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.4 Return Deliveries


4.4.1 Check Print Indicator for the Movement Type
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management  Inventory Management and Physical
Inventory  Movement Types  Copy, Change Movement Types
Menu IMG Administração de materiais  Administração de estoques e
inventário  Tipos movimento  Copiar, modificar tipos de
movimento
Transaction Code OMJJ
2. A Dialog box appears 'Field Selection'
3. Check a Flag on 'Movement Type',
4. Choose Enter
5. A Dialog box appears 'Determine Work Area: Entry':
6. In Movement Type, enter '122',
7. Choose Enter
8. Choose Subscreen:'Entry Control'
9. The Field:‘Print Item': must be '2'

Background:
The indicator must correspond to the indicator in the output condition record, or the indicator set here
must be used for the output condition record

© SAP AG Page 27 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.5 Wave Picks (Optional)


4.5.1 Maintain Time of Comparison for Forming Wave Picks
Prerequisites
Warehouse number must be maintained.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Wave Picks 
Maintain Time of Comparison for Forming Wave Picks
Menu IMG Logistics Execution  Expedição  Picking  Pacotes de picking
 Atualizar o quadro de pacotes de picking
Transaction Code SPRO
2. Maintain entries
3. Check/enter your settings.
Warehouse No. Pick wave comp. time Description
PC1 1 Picking time

Background:
By means of the time of comparison set here the shipments are allocated to wave picks. It is also
possible to use the load or planned goods shipment time.

4.5.2 Maintain Wave Picks Profile


Prerequisites
Warehouse number must be maintained.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Wave Picks  Maintain
Wave Picks Profile
Menu IMG Logistics Execution  Expedição  Picking  Pacotes de picking 
Atualizar o perfil do pacote de picking
Transaction Code SPRO
2. Select New Entries or copy existing,
3. Choose DETAIL to branch into the detail view
4. Check/enter your settings.
Wh. No. Pick. waves Description Max. picking Cap. limit. Creat.
prfl items type

© SAP AG Page 28 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

PC1 PCS001 low Cap. (3 items) 3 x 1


PC1 PCS002 med. Cap. (5 items) 5 x 1
PC1 PCS003 high Cap. (7 items) 7 x 1

5. With all entries except 'picking items' set to high value (999999...).

Background:
In the wave picks profile the properties of a wave pick are summarized, especially the capacity
limitations. The profile is then allocated to the timeslots. As many profiles are needed as different capacity
situations occur in the warehouse.
The “Creat. type” means that outbound deliveries are bundled in waves whose compare times are within
a timeslot of the planned timeslot group.

Remarks:
The settings of 3-7 pick items per wave are selected for demo purposes and will need to be set to realistic
values in the customer project. Other restrictions (according to weight, value, etc.) or combinations
thereof can also be selected.

4.5.3 Maintain Timeslots for Wave Picks


Prerequisites
Warehouse number and wave picks profile must be maintained.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Wave Picks 
Maintain Timeslots
Menu IMG Logistics Execution  Expedição  Picking  Pacotes de picking
 Atualizar as faixas de tempo
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.
Timeslot End Date Description Start Finish Picking waves
prfl
ZS01 31.12.9999 Morning 06:00:00 09:00:00 PCS001
ZS02 31.12.9999 Late Morning 09:15:00 12:15:00 PCS002
ZS03 31.12.9999 Afternoon 13:00:00 16:00:00 PCS003

Background:
A timeslot is time period in which outbound deliveries (whose compare times must be within the timeslot)
can be combined into a wave pick. In this way, one wave pick is formed per timeslot (if there are any
outbound deliveries within the timeslot).

© SAP AG Page 29 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

By allocating a wave pick profile to a timeslot it is possible to model capacity restrictions.

Remarks:
A number of timeslots will afterwards be combined into wave pick lines.

4.5.4 Maintain Timeslot Group for Wave Pick


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Wave Picks 
Maintain Timeslot Group for Wave Pick
Menu IMG Logistics Execution  Expedição  Picking  Pacotes de picking
 Atualizar o quadro de pacotes de picking
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

Slot grp Timesl no Description Timeslot Start Finish


day 1
WRA1 1 Standard work ZS01 06:00:00 09:00:00
day
WRA1 2 Standard work ZS02 09:15:00 12:15:00
day
WRA1 3 Standard work ZS03 13:00:00 16:00:00
day
Background:
In a wave pick line, timeslots are grouped such that they depict a working day. Here a normal working day
contains 3 timeslots. Thus a maximum of 3 wave picks per day are formed.

Remarks:
The wave pick profile, timeslots and wave lines will certainly have to be reworked in a customer project.

4.5.5 Activate the Update of Info Structure for Wave Picks


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Wave Picks 
Control Update of Workload Data
Menu IMG Logistics Execution  Expedição  Picking  Pacotes de picking
 Controle da atualização de cargas
Transaction Code VLLV
2. Choose CONTROL...
3. Select Subscreen 'Update Wave Picks'
4. Choose UPDATE GROUP: ASSIGN HEADER (Register 'Delivery')

© SAP AG Page 30 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

5. Choose UPDATE GROUP: ASSIGN ITEM (Register 'Delivery')


6. Check/enter your settings.

Parameters-Settings:
for 1.: in subscreen 'Update Wave Picks' asynchronous update must be activated
for 2.:maintain the following entries:
SOrg. D. Div. Ctl.Cust.Ctl.Doc. Upd.Grp/Description
Wholesale:
1000 20 10 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 2 2 SIS: Returns, Rtns Deliv., Credit Memo
1000 20 10 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
Retail:
1000 30 10 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 30 10 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
for 3.:maintain the following entries:
SOrg. D. Div. C.Cu. C.Ma. C.Do. C.lt. Upd.Grp/Description
Wholesale:
1000 20 10 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 1 2 2 SIS: Returns, Rtns Deliv., Credit Memo
1000 20 10 2 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 2 2 2 SIS: Returns, Rtns Deliv., Credit Memo
1000 20 10 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 + 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 1 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
Retail:
1000 30 10 + 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 30 10 1 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.

Background:
Activating the update is a precondition for building wave picks. It must be made certain that the correct
update group is found. This is what the entries 2. and 3. are for.

Remarks:
The statistic group ‘1’ must be entered in the 'additional sales data' view of the article as well as the 'sales'
view in the debtor record of the customer.
The rough workload estimate requires the same settings (see below).

© SAP AG Page 31 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.6 Shipping
4.6.1 Define Item Category Determination in Outbound Deliveries
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Deliveries  Define Item
Category Determination in Deliveries
Menu IMG Logistics Execution  Expedição  Fornecimentos  Definir
tipos de item para fornecimentos
Transaction Code SPRO
2. Select NEW ENTRIES or copy existing
3. Check/enter your settings.
DlvT ItCG ItmC
LO SAMM DLN
UL SAMM ULN

Background:
In this menu option, you define the item category determination for outbound deliveries. The item
category ('DLN' or 'ULN') is determined according to the following categories:

 Item category group ('SAMM') of the article.

 Sales document type ('LO' or 'UL').

4.6.2 Maintain Working Hours


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Basic Shipping functions 
Scheduling  Delivery scheduling and Transportation scheduling
 Maintain working hours
Menu IMG Logistics Execution  Expedição  Bases Programação
Programação da expedição e do transporte Atualizar as horas
de trabalho
Transaction Code SPRO
2. Select folder in ‘Dialog structure’ pane
3. Choose Shift Definitions
4. Choose Shift sequences
5. Choose Working times

© SAP AG Page 32 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Parameters – Settings:
1. Shift Definitions
Shift Shift def.text Start date End date Start Finish
AFTE Afternoon shift 01.01.1990 31.12.9999 14:00:00 22:00:00
DAY Day shift 01.01.1990 31.12.9999 08:00:00 18:00:00
MORN Morning shift 01.01.1990 31.12.9999 06:00:00 14:00:00
STD Normal shift 01.01.0001 31.12.9999 08:00:00 17:00:00

2. Shift sequences
Shift Seq. Counter Description Mon Tues Wed Thurs Fri Sat Sun
1-SH 1 1-shift DAY DAY DAY DAY DAY
1SHI 1 1-shift STD STD STD STD STD
2-SH 1 2-shift afternoon MORN MORN MORN MORN MORN
2-SH 2 2-shift afternoon AFTE AFTE AFTE AFTE AFTE
2SHI 1 2-shift late MORN MORN MORN MORN MORN MORN
2SHI 2 2-shift late AFTE AFTE AFTE AFTE

3. Working times
Category Work.time Cal. Shift seq. TmZn Text +
TS 1-SHIFT GB 1-SH 1-shift 1-shift working times
TS 2-SHIFT GB 2-SH 1-shift 2-shift working times

Background:
The shipping point is the top level in the organization for shipping.

4.6.3 Maintain Shipping Point


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Enterprise Structure  Definition  Logistics Execution  Define,
copy, delete, check shipping point  Define shipping point
Menu IMG Estrutura do empreendimento Definição Logistics Execution
 Definir, copiar, eliminar, verificar local de expedição Definir
local de expedição
Transaction Code SPRO
2. Choose existing entry '0001' and Copy as...
3. In Shipping Point, enter '1000'

© SAP AG Page 33 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4. In Description enter, 'Shipping Point PCS'


5. In Country, enter US
6. In Departure zone, enter US00050000
7. In Logistics calendar, enter US
8. In Working times enter, 1-SHIFT
9. In Determine Loading time, enter C (Default from Shipping point)
10. In Loading time – working hours, enter 4:00
11. In Determine Pick/Pack time enter, C (Default from Shipping point)
12. In Pick/Pack time – working hours enter, 6:00
13. In Output type, enter EK00
14. In Message language, enter EN

Background:
The shipping point is the top level in the organization for shipping.

4.6.4 Maintain Profile for Subsequent Delivery Split


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Deliveries  Subsequent
Delivery Split
Menu IMG Logistics Execution  Expedição Fornecimentos Partição de
remessa posterior

Transaction Code OVDSP

2. Choose split profile,


3. Choose sub-tree 'per delivery type',
4. Choose existing entry,
5. Select New Entries or copy existing
6. Check/enter your settings.
SpltPro Text Deliv.type DelZeroltm WholeDelGr
0001 Planning UL x x
0002 Shp. cmpltn on UL x x
the load. ramp

Background:
The subsequent delivery split must be possible for 'UL', as this delivery type is used in the warehouse
processes (outbound delivery without reference). Therefore, a split profile must be assigned. This
designates the business process for which the delivery split is executed.

© SAP AG Page 34 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

If an item with the quantity ‘0’ were to result from the subsequent delivery split, this item should be
deleted. Complete delivery groups cannot by split.

© SAP AG Page 35 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.7 Physical inventory


4.7.1 Define Default Values for Physical Inventory
Prerequisites
Warehouse number and storage types are defined

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Activities 
Physical Inventory  Define Default Values
Menu IMG Logistics Execution  Administração de depósitos  Operações 
Inventário físico  Definir valores propostos
Transaction Code SPRO

2. Choose existing entries and COPY AS..

Parameters - Settings:
Entry '001 – 001' copy to 'PC1 – R01'
Entry '001 – 005' copy to 'PC1 – K01'
Hardgoods:
Entry '001 – 005' copy to 'PC1 – B01'
Fashion:
Entry '001 – 005' copy to 'PC1 – H01'
Food:
Entry '001 – 005' copy to 'PC1 – F01'

Background:
The printing of the physical inventory document can be controlled here. In addition, a critical inventory
variance (in percent) is maintained per storage type. If a variance reaches this percentage during physical
inventory counting, the system will provide a warning and suggest re-counting the stock.

© SAP AG Page 36 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.7.2 Define Physical Inventory Types per Storage Type


Prerequisites
Warehouse number and storage types are defined.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Activities 
Physical Inventory  Define Types per Storage Type
Menu IMG Logistics Execution  Administração de depósitos Operações 
Inventário físico Definir tipos por tipo de depósito
Transaction Code OMNK

Parameters - Settings:
For the newly created storage types 'R01', 'K01', 'B01' (Hardgoods), 'H01' (Fashion) and 'F01' (Food), set
'PZ' ('Continuous inventory') as the physical inventory type.
In storage type 'R01', delete the flags 'ZeroCkIn' and 'ZeroCheck'. This is however only necessary for use
as a demo system, so that Zero Checks are not constantly needed during picking. In actual operation,
these flag settings can be desirable.

Background:
It can be set per storage type which physical inventory type should be used.
The use of Zero Checks in high-rack warehouses makes sense since a bin is always empty when an
entire pallet is picked.

4.7.3 Define Bar Code Types for Physical Inventory


Prerequisites
Warehouse number is defined

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Mobile Data Entry  Bar Code  Assign
Bar Code Types to Warehouse Numbers
Menu IMG Logistics Execution  Entrada de dados com terminal portátil 
Código de barras  Atribuir tipos de códigos de barras a nºs de
depósito
Transaction Code SPRO

Parameters - Settings:
For the warehouse number, 'PC1' in the column 'Bin AppID', delete the existing assignment EAN-128.

© SAP AG Page 37 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Background:
Since the verification of the storage bin is done by manual entry for the demonstration of this process, the
EAN type must be deleted, otherwise a check of the entry is done against the EAN-128 Code.

Remarks:
If this functionality is used in the actual site later, the EAN type that is used must be entered here.

© SAP AG Page 38 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.8 Mobile Data Entry (Optional)


4.8.1 Maintain RF Queue Management
Prerequisites
Warehouse number and storage types have been created. Default user for RF (here 'PRECONF') exists.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Mobile Data Entry  RF Queue
Management
Menu IMG Logistics Execution  Entrada de dados com terminal portátil 
Administração de fila RF
Transaction Code OMKW

2. Choose Define Queues:


3. Select New Entries,
4. Maintain entries
5. Assign Areas and Activities to Queues:
6. Select New Entries,
7. Maintain entries

Parameter – Settings:
1.: Maintain following entries:
PC1 IN_PCS Inbound PCS 20.000 40.000
PC1 OUT_PCS Outbound PCS 20.000 40.000
2.: Maintain following entries:
PC1 Prep ... placement into stock E R01 *** *** IN_PCS
PC1 Prep ... placement into stock E F01 *** *** IN_PCS
PC1 Prep ... placement into stock E B01 *** *** IN_PCS
PC1 Prep ... placement into stock E H01 *** IN_PCS
PC1 Prep ... stock removal A F01 *** ***
OUT_PCS
PC1 Prep ... stock removal A K01 *** ***
OUT_PCS
PC1 Prep ... stock removal A B01 *** ***
OUT_PCS
PC1 Prep ... stock removal A H01 *** ***
OUT_PCS

Background:
1: One queue is maintained for goods receipt and on for goods issue. When there are more than 20
transfer orders per worker, the traffic light changes to red; when there are more than 40 per worker,
it changes to red.

© SAP AG Page 39 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

2: The queues are to be filled with putaways (IN_PCS) in R01, F01, B01, H01 and picks out of K01,
F01, B01, H01 (OUT_PCS).

4.8.2 Define Menu Management for RF


Prerequisites
Warehouse number has been created

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Mobile Data Entry  Define Menu
Management
Menu IMG Logistics Execution  Entrada de dados com terminal portátil 
Definir administração de menu
Transaction Code SPRO

2. Choose all data records,


3. Choose COPY AS ...,
4. Choose change record,
5. Choose Enter

Parameters - Settings:
Copy all data records from warehouse number '001' to warehouse number 'PC1'.
Change the transaction in the following entries
(LM52/LM53 is no longer supported, cf. note 392212):
W... Dyn.menu S... Menu Text Menu/Trns type Menu/trns Short text
PC1 INV00 1 Bin Count 2 LM51 Bin Count
PC1 INV00 2 Bin Count Guided 2 LM50 Bin Cnt. Guid.
Delete following entries:
PC1 INV00 3 ...
PC1 INV00 4 ...

Background:
In the menu management, the structure of the menu for mobile data entry is determined. One menu point
always has a further menu or a transaction assigned to it.

Remarks:
The menu texts should be changed in German and in English.
Individual menu points can be inserted or deleted as necessary.

© SAP AG Page 40 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.9 Warehouse Activity Monitor (Optional)


4.9.1 Activate Warehouse Activity Monitor Objects
Prerequisites
Warehouse number must exist.

Procedure:
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Planning and
Monitoring  Warehouse Activity Monitor  Activate Warehouse
Activity Monitor Objects
Menu IMG Logistics Execution  Administração de depósitos  Planejamento
e supervisão Estação de controle de depósito  Ativar objetos de
estação de controle de depósito
Transaction Code SPRO

2. Copy existing entries


3. Copy entries of warehouse monitor objects (MOb) 01-06 for warehouse number '001' to
warehouse number 'PC1'

Background:
By these entries the updating of the warehouse monitor object is activated and the display variant per
object is fixed.

4.9.2 Define Critical Parameters


Prerequisites
Warehouse number must be maintained

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Planning and
Monitoring  Warehouse Activity Monitor  Define Critical
Parameters
Menu IMG Logistics Execution  Administração de depósitos Planejamento
e supervisão  Estação de controle de depósito Definir
parâmetros críticos
Transaction Code SPRO
2. Maintain critical durations for all warehouse monitor objects (01-06)
for the relevant movement types. For this it is advised to copy and
change data from warehouse number 001.

Parameters - Settings:
© SAP AG Page 41 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

For all monitor objects (select in tree structure)


Copy the entries of movement type 101, 501, 601 and 999 resp. all warehouse types from warehouse
number '001' onto 'PC1'.
Reduce all durations to 1 sec.

Background:
Only after the critical duration period the process is displayed in the warehouse monitor. These
durations are to be redefined in the project according to customer requirements. For demo
purposes these durations have been reduced to 1 sec. so that the objects become critical immediately
after creation and thus appear in the warehouse monitor.
In the customer project it is advised to maintain critical durations for all further movement types.

© SAP AG Page 42 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.10 Rough Workload Estimate (Optional)


4.10.1 Maintain Logistics Load Categories
Prerequisites
Warehouse number must be maintained.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Planning and
Monitoring Rough Workload Estimate  Calculate Workload 
Maintain Logistics Load Category
Menu IMG Logistics Execution  Administração de depósitos  Planejamento e
supervisão  Previsão global da carga Cálculo da carga de
trabalho  Atualização grupo de tratamento logístico
Transaction Code SPRO

2. Select New Entries or copy existing

Log. handling group Description


NORM Normal
Hardgoods BULK Bulk Goods
Fashion HANG Hanging Clothes
3. Check/enter your settings.

Background:
The logistics load category is determined in the article master data and controls the load calculation
together with other parameters.

4.10.2 Maintain Unit-of-Measure Load Categories


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu IMG  Logistics Execution  Warehouse Management  Planning
and Monitoring Rough Workload Estimate  Calculate Workload 
Maintain Unit-of-Measure Load Category
IMG  Logistics Execution  Warehouse Management  Planning
and Monitoring Rough Workload Estimate  Calculate Workload 
Assign Units of Measure to Unit-of-Measure Load Category
Menu IMG IMG  Logistics Execution  Administração de depósitos
Planejamento e supervisão  Previsão global da carga  Cálculo da
carga de trabalho Atualização grupo de cargas UM
IMG  Logistics Execution  Administração de depósitos

© SAP AG Page 43 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Planejamento e supervisão  Previsão global da carga  Cálculo da


carga de trabalho Atribuição de unid.medida ao grupo cargas da
unid.medida
Transaction Code SPRO
2. Select New Entries or copy existing

Parameters-settings:
for 1.: maintain the following entries:
Un load category Description
A Small load per UoM
B Medium load per UoM
C High load per UoM

for 2.: maintain the following entries:


Int. meas. unit Measuremt unit text Un load cat.
EA each A
CT Carton B
CRT Crate B
PAL Pallet C

Background:
The Unit-of-Measure Load Category ('A', 'B' und 'C') serves to calculate the load according to unit of
measure. For example, the handling of a palette in the warehouse results in a larger load than the
handling of a carton, a crate or a single piece.

4.10.3 Maintain and Assign Warehouse Operations


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Planning and
Monitoring Rough Workload Estimate  Calculate Workload 
Maintain Warehouse Operations
Logistics Execution  Warehouse Management  Planning and
Monitoring Rough Workload Estimate  Calculate Workload 
Maintain Warehouse Processes
Menu IMG Logistics Execution  Administração de depósitos Planejamento
e supervisão  Previsão global da carga  Cálculo da carga de
trabalho Atualizar operações de depósito
IMG  Logistics Execution  Administração de depósitos
Planejamento e supervisão  Previsão global da carga  Cálculo
da carga de trabalho Atualizar processos de depósito
Transaction Code SPRO
2. Select New Entries or copy existing

© SAP AG Page 44 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Parameters-Settings:
for 1.: maintain the following entries:
Whse operation Description
E1 Unload
E2 GR Check
E3 Putaway
K1 Pick
K2 Load

for 2.: maintain the following entries:


Warehouse proc. Description Sequence Number
Whse operation
1 Goods receipt / putaway 1 E1
1 Goods receipt / putaway 2 E2
1 Goods receipt / putaway 3 E3
2 Picking / goods issue 1 K1
2 Picking / goods issue 2 K2

Background:
For the calculation of the warehouse load the individual warehouse processes can be split into operations
to determine work durations. These are to be maintained here.
Subsequently, the (customer-specific) warehouse transactions are assigned to the (fixed coded)
warehouse processes.

Remarks:
These settings serve as example and have to be adapted to the customer requirements.

4.10.4 Maintain Warehouse Workloads


Prerequisites
Warehouse operations and processes must be maintained

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Planning and
Monitoring Rough Workload Estimate  Calculate Workload 
Maintain Warehouse Workload
Menu IMG IMG  Logistics Execution  Administração de depósitos
Planejamento e supervisão  Previsão global da carga  Cálculo
da carga de trabalho Atualização cargas do depósito
Transaction Code SPRO
2. Select New Entries or copy existing
3. Check/enter your settings.

© SAP AG Page 45 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Whse Stge Whse UnLoad Log. h... Constant Variable


No. Type operation time/sec. time/sec.
PC1 001 K1 A NORM 20.000 5.000
PC1 001 K1 B NORM 30.000 10.000
PC1 001 K1 C NORM 60.000 60.000
PC1 001 K2 A NORM 10.000 10.000
PC1 001 K2 B NORM 10.000 10.000
PC1 001 K2 C NORM 60.000 60.000
PC1 001 K1 A BULK 20.000 5.000
PC1 001 K1 B BULK 30.000 10.000
PC1 001 K1 C BULK 60.000 60.000
PC1 001 K2 A BULK 10.000 10.000
PC1 001 K2 B BULK 10.000 10.000
PC1 001 K2 C BULK 60.000 60.000

Background:
The workload table is the central reference for the rough workload estimate.
Here a variable load per UoM and a fixed load per item have to be maintained in work seconds for each
combination of warehouse number, storage type, warehouse operation, Unit-of-measure load category
and logistic load category.

Remarks:
The values maintained here are incomplete in terms of logistic load category and are only maintained for
the outbound processes. The selected durations are arbitrary and the maintained data thus serve as an
example only. If the rough workload estimate is to be used in a customer project the complete expansion
and completion of the entries has to take place.

4.10.5 Control Update of Workload Data


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Planning and
Monitoring Rough Workload Estimate  Control Update of
Workload Data
Menu IMG Logistics Execution  Administração de depósitos  Planejamento
e supervisão  Previsão global da carga  Controle da atualização
de cargas
Transaction Code VLLV
2. Choose DISPLAY -> CHANGE,
3. Choose CONTROL…

© SAP AG Page 46 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

1) Activate update in the left part of the screen (subscreen 'Rough Workload Estimate')
2) Choose UPDATE GROUP: ASSIGN HEADER (Register 'Delivery')
3) Choose UPDATE GROUP: ASSIGN ITEM (Register 'Delivery')
4. Check/enter your settings.

Parameters-Settings:
for 1.: in subscreen 'Rough Workload Estimate': activate the ‘asynchronous update’ for the general
overview as well as for all single processes (4 Tabs).
for 2.:maintain the following entries:
SOrg. D. Div. C.Cu. C.Do. Upd.Grp./Description
Wholesale:
1000 20 10 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 2 2 SIS: Returns, Rtns Deliv., Credit Memo
1000 20 10 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
Retail:
1000 30 10 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 30 10 1 1 SIS: Sales Doc., Delivery, Billing Doc.
for 3.: maintain the following entries:
SOrg. D. Div. C.Cu. C.Ma. C.Do. C.lt. Upd.Grp./Description
Wholesale:
1000 20 10 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 1 2 2 SIS: Returns, Rtns Deliv., Credit Memo
1000 20 10 2 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 2 2 2 SIS: Returns, Rtns Deliv., Credit Memo
1000 20 10 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 + 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 20 10 1 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.

Retail:
1000 30 10 + 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.
1000 30 10 1 1 1 1 1 SIS: Sales Doc., Delivery, Billing Doc.

Background:
To activate the rough workload estimate the respective info structures ('S150', 'S152') have to be updated.
It has to be ensured that the correct update group is found both on header and item level.

Remarks:
The statistic group ‘1’ must be entered in the 'additional sales data' view of the article as well as the 'sales'
view in the debtor record of the DC.
Similar settings are needed for wave picks (see above).

© SAP AG Page 47 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.11 Connecting the Warehouse to a DC (Site)


4.11.1 Define Storage Location for WM in the DC
Prerequisites
At least reference DC (R100) must have been created

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Enterprise Structure  Definition  Materials Management 
Maintain Storage Location
Menu IMG Estrutura do empreendimento  Definição  Administração de
materiais  Atualizar depósito
Transaction Code OX09

2. Choose Site,
3. Choose Enter,
4. Create new storage locations or delete storage locations
5. Check/enter your settings.
6. For DC (R100) create the following storage location: 0003 'PCS Whse (WM)

Background:
The warehouse number is found via the combination site/storage location. Further storage locations serve
to split stock for inventory management.

Remarks:
Customizing of the reference DC (R100) needs to be completed before creating further sites. Alternatively
settings have to be also maintained manually for VZ01. This customizing setting is copied from the
reference site when creating sites.

4.11.2 Assign Warehouse Number to Site/Storage Location


Prerequisites
Warehouse number and reference site must have been created.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Enterprise Structure  Assignment  Logistics Execution 
Assign Warehouse Number to Plant/Storage Location
Menu IMG Estrutura do empreendimento  Atribuição  Logistics Execution
 Atribuir nº do depósito ao centro/depósito
Transaction Code SPRO

© SAP AG Page 48 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

2. Select New Entries


3. Check/enter your settings.
4.For site R100 assign: Storage location '0003' to warehouse number 'PC1'

Background:
A full WM storage number (PC1) is connected to storage location '0003'.

Remarks:
Customizing of the reference DC (R100) needs to be completed before creating further sites. Alternatively
settings have to be also maintained manually for VZ01. This customizing setting is copied from the
reference site when creating sites.

4.11.3 Define Standard Storage Location


Prerequisites
Warehouse number, reference site and the assignment between them must have been created

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Warehouse Management  Interfaces 
Inventory Management  Define storage location control  Control
of Assignment "Site / Stor.Loc. - Whse Number"
Menu IMG Logistics Execution  Administração de depósitos  Interfaces 
Administração de estoques  Definir controle de depósitos 
Controle p/atribuição "centro/depósito - nº depósito"
Transaction Code SPRO
2. Choose entry,
3. Choose Detail, make changes
4. Choose entry for site 'R100', storage location '0003', warehouse number 'PC1'
5. In the detail screen set the flag 'Standard SLoc'.
6. Check/enter your settings.

Background:
This flag is only needed if a warehouse number is assigned to a site more than once via multiple storage
locations. In this case, the flag will determine the storage location used, when only a site and the
warehouse number are given.

Remarks:
Customizing of the reference DC (R100) needs to be completed before creating further sites. Alternatively
settings have to be also maintained manually for VZ01. This customizing setting is copied from the
reference site when creating sites.

© SAP AG Page 49 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.11.4 Assign Shipping Points and Shipping Point Determination


Prerequisites
Reference sites and shipping points have been created

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Enterprise Structure  Assignment  Logistics Execution  Assign
shipping point to site
Logistics Execution  Shipping  Basic Shipping Functions 
Shipping Point and Goods Receiving Point Determination  Assign
Shipping Points
Menu IMG Estrutura do empreendimento  Atribuição  Logistics Execution 
Atribuir local de expedição - centro
Logistics Execution  Expedição  Bases  Determinação de
local de expedição/dpto.entrada mercadorias  Atribuir locais de
expedição
Transaction Code OVXC, SPRO
2. Choose site,
3. Choose ASSIGN,
4. Choose shipping point,
5. Choose COPY
6. Select New Entries or copy existing ones
7. Check/enter your settings.
8. Assign shipping point 'VS01' to site 'R100'.
9. Insert following entries:
SC LGrp Site PrShP
0001 R100 VS01
0002 R100 VS01
01 0001 R100 VS01
01 0002 R100 VS01
02 0001 R100 VS01
02 0002 R100 VS01

Remarks:
Customizing of the reference DC (R100) needs to be completed before creating further sites. Alternatively
settings have to be also maintained manually for VZ01. This customizing setting is copied from the
reference site when creating sites.

© SAP AG Page 50 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

4.11.5 Define Storage Conditions


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Determine Picking
Location  Define storage conditions
Menu IMG Logistics Execution  Expedição  Determin.depósito de picking
 Definir condições de estocagem
Transaction Code SPRO
2. Select New Entries
3. Check/enter your settings.
4. Maintain the following entry: WM Warehouse Management

Background:
The storage condition is assigned to the article in the article master data. It serves to allow the
determination of different storage locations under otherwise same parameters.

4.11.6 Define Rules for Picking Location Determination


Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Determine Picking
Location  Define rules for picking location determination
Menu IMG Logistics Execution  Expedição  Picking  Determin.depósito de
picking  Definir regras para determinação de depósitos de picking
Transaction Code SPRO

2. Check or change existing entries


3. Check/enter your settings.

DlcTy Rule Determ. StLoc

YFDT MALA
LF RETA
UL RETA
LO RETA

© SAP AG Page 51 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Background:
For each delivery type a rule for determination of picking storage locations is assigned. With rule 'MALA'
the storage location is determined by the key site/shipping point/storage condition, with 'RETA' the key is
site/situation/storage condition.

4.11.7 Picking Location Determination (MALA)


Prerequisites
Storage conditions, shipping point and reference sites must exist

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Determine Picking
Location  Assign picking locations
Menu IMG Logistics Execution  Expedição  Picking  Determin.depósito de
picking  Atribuir depósitos de picking
Transaction Code SPRO
2. Maintain respective storage locations for combinations of shipping
point, site and storage conditions
3. ShPt. Site SC SLoc Che
ck/e
VS01 R100 0001 nter
your
VS01 R100 WM 0003
settings.

Background:
Currently picking in the DC takes place via two separate storage locations, 0001 for lean WM and 0003
for full WM. For articles that need to be managed in the full WM the storage condition ‘WM‘ has to be
maintained in the article master. These settings are only used when 'MALA' is set as a rule for picking
determination

Remarks:
Customizing of the reference DC (R100) needs to be completed before creating further sites. Alternatively
settings have to be also maintained manually for VZ01. This customizing setting is copied from the
reference site when creating sites.

4.11.8 Storage Location Determination with Situation (RETA)


Prerequisites
Storage conditions and reference sites must exist.

Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Logistics Execution  Shipping  Picking  Determine Picking

© SAP AG Page 52 of 53
SAP Best Practices 742: Warehouse and DC Management (WM): Configuration Guide

Location  Storage location determination with situation


Menu IMG Logistics Execution  Expedição  Picking  Determin.depósito de
picking  Determinação depósito com situação
Transaction Code SPRO
2. In reference distribution center, enter R100,
3. Choose Enter
4. Select New Entries
5. Check/enter your settings.
Site Situation Storage conditions Storage location

R100 01 WM 0003 PCS Whse (WM)

Background:
For the normal situation (01) articles without storage condition are picked in storage location '0001' (and
via this in warehouse number 'PC0' set as lean WM) and articles with storage condition 'WM' are picked
in storage location '0003' (and via this in warehouse number 'PC1' set as full WM).

Remarks:
Customizing of the reference DC (R100) needs to be completed before creating further sites. Alternatively
settings have to be also maintained manually for VZ01. This customizing setting is copied from the
reference site when creating sites.

© SAP AG Page 53 of 53