742_bpp_en_us

96
EHP3 for SAP ERP 6.0 September 2008 English 742: Warehouse and DC Management (WM) SAP AG Business Process Documentation

Upload: saranpc

Post on 10-Dec-2015

7 views

Category:

Documents


3 download

DESCRIPTION

SAP WM and DC Mgmt BP

TRANSCRIPT

Page 1: 742_BPP_EN_US

EHP3 for SAP ERP 6.0

September 2008

English

742: Warehouse and DC Management (WM)

SAP AGDietmar-Hopp-Allee 16D-69190 WalldorfGermany

Business Process Documentation

Page 2: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Copyright

© Copyright 2008 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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, xApps, xApp, 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 in several other countries all over the world. 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 AG Page 2 of 74

Page 3: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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 74

Page 4: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Contents

1 Purpose.................................................................................................................................. 6

1.1 Overview......................................................................................................................... 6

1.2 Procedure....................................................................................................................... 7

1.3 Overview of the Required Master Data.........................................................................10

2 Prerequisites........................................................................................................................ 12

2.1 Article............................................................................................................................ 12

2.2 Stocks........................................................................................................................... 12

2.3 Using Mobile Terminals (Radio Frequency – RF).........................................................14

2.4 Scenario Menu and Basic Path.....................................................................................14

2.5 Additional Tools and Workbenches...............................................................................15

3 Process Flow and Overview.................................................................................................16

3.1 Process Overview Table...............................................................................................16

4 Goods Receipt Processing...................................................................................................23

4.1 Preliminary Phase to Goods Receipt............................................................................23

4.1.1 Create Purchase Order..........................................................................................23

4.1.2 Create Inbound Delivery........................................................................................26

4.1.3 Appointment Planning............................................................................................26

4.2 Receipt of Incoming Goods...........................................................................................27

4.2.1 Post Rough Goods Receipt...................................................................................28

4.2.2 Enter Actual Appointment......................................................................................28

4.2.3 Goods Receipt with Reference to Rough Goods Receipt......................................29

4.3 Put away Preparation....................................................................................................30

4.4 Carry Out Putaway........................................................................................................32

4.4.1 Alternative 1: Asynchronous Warehouse Management.........................................32

4.4.2 Alternative 2: Synchronous Warehouse Management...........................................34

5 Return Deliveries.................................................................................................................. 36

5.1 Prepare Return Deliveries.............................................................................................37

5.1.1 Search for Article Document for Goods Receipt....................................................37

5.1.2 Create a Return Delivery.......................................................................................38

5.1.3 Prepare for Collection............................................................................................39

5.1.4 Goods Collection...................................................................................................42

6 Internal Warehouse Replenishment.....................................................................................42

6.1 Replenishment Planning...............................................................................................43

6.2 Carry Out Replenishment.............................................................................................44

6.2.1 Create a Transfer Order.........................................................................................44

6.2.2 Confirm Transfer Order..........................................................................................45

© SAP AG Page 4 of 74

Page 5: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

7 Goods Issue Processing......................................................................................................45

7.1 Create Outbound Delivery............................................................................................46

7.2 Stock Removal/Picking.................................................................................................47

7.2.1 Create Transfer Order as a Picking Document......................................................47

7.2.2 Carry Out Picking...................................................................................................49

7.3 Posting Goods Issue.....................................................................................................53

7.4 Variant: Mass Processing of Deliveries.........................................................................54

7.4.1 Create Deliveries with Planned Picking Time........................................................54

7.4.2 Create Wave Picks................................................................................................56

7.4.3 Create Transfer Orders in Collective Processing...................................................59

7.4.4 Confirm Transfer Orders in Collective Processing.................................................60

7.4.5 Subsequent Delivery Split......................................................................................61

7.4.6 Goods Issue in Collective Processing....................................................................61

8 Warehouse Physical Inventory.............................................................................................62

8.1 Create a Physical Inventory Document.........................................................................62

8.2 Perform Physical Inventory...........................................................................................63

8.2.1 Enter Inventory Count Results...............................................................................63

8.2.2 Trigger Inventory Recount.....................................................................................65

8.2.3 Carry Out Inventory Recount.................................................................................66

8.3 Processing Differences.................................................................................................67

8.3.1 Post Differences in Warehouse Management........................................................67

8.3.2 Post Differences in Inventory Management...........................................................68

8.4 Inventory Evaluation.....................................................................................................68

8.4.1 Difference Statistics...............................................................................................68

8.4.2 Determine Inventory Status...................................................................................69

9 Appendix: Tools and Workbenches......................................................................................70

9.1 Warehouse Activity Monitor..........................................................................................70

9.2 Outbound Delivery Monitor...........................................................................................71

9.3 Wave Pick Monitor........................................................................................................72

9.4 Rough Workload Estimate for Goods Issue..................................................................72

9.4.1 Rough Workload Estimate After Creation of Outbound Deliveries.........................73

9.4.2 Rough Workload Estimate After Goods Issue........................................................74

© SAP AG Page 5 of 74

Page 6: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Warehouse and DC Management (WM)

1 PurposeThis scenario describes the processing procedure for retail goods in a distribution center, using a warehouse management system with inventory management at storage bin level. In this scenario, distribution center will refer to a warehouse that is supplied by vendors, that stores the merchandise and then prepares it to be shipped to customers or stores. As warehouse processes depend greatly on the amount of space available, the organization of the warehouse and the merchandise stored there, this scenario should be viewed simply as an example for implementation purposes. However, with very little effort, this example can be adapted to fit any customer-specific situation.

1.1 Overview

IntroductionTo summarize, warehouse stocks are carried in Inventory Management (IM) in SAP R/3 at storage location level. When stockkeeping for large-scale storage is more complex, for example, 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) should 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. In warehouse management the main object is the quant, the stock of an article in one storage bin, possibly with additional separating characteristics like the storage unit or the batch. The main document in warehouse management is the transfer order (TO). One item in the transfer order describes the transportation of one quant from one storage bin to another. Upon confirmation, the system receives notification of a correctly processed transfer order.

As IM and WM are completely integrated, the warehouse processes cannot usually be viewed in isolation. For instance, a prerequisite of putaway is that the goods receipt has been posted. In the same way, stock removal is usually triggered by a corresponding shipping document and is concluded once the goods issue has been posted.

We mapped a common retail warehouse structure for this scenario. Following goods receipt, merchandise is first placed in a reserve storage area on pallets. After this it can be moved to the picking bin whenever it is needed. Whether the reserve storage area and the picking area are separated spatially (for example, in separated halls) or simply in organizational terms (for example, reserve bins at shelf level above the picking bins) is of no importance here. For merchandise with particular storage requirements (for example, hanging, frozen or bulky goods) special warehouse types are set up that are not separated into picking spots and reserve bins, with the result that no replenishment is required. The shipping of merchandise takes place at the same time, using a central shipping point.

The scenario is divided into individual processes that display the complete movement of the merchandise through the distribution center for the whole process. In addition, periodical processes such as the physical inventory are displayed.

© SAP AG Page 6 of 74

Page 7: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

1.2 Procedure

© SAP AG Page 7 of 74

Page 8: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

© SAP AG Page 8 of 74

Page 9: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

© SAP AG Page 9 of 74

Page 10: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

1.3 Overview of the Required Master DataTo execute the scenarios, use the master data listed for your installation of the preconfigured system. For the relevant identifiers, see the following table:

© SAP AG Page 10 of 74

Page 11: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

FASHION HARD GOODS FOOD

VENDOR PCS-V141 PCS-V431 PCS-V321

ARTICLE 1 PCS-06-ART141001 PCS-06-ART431 PCS-06-ART323

ARTICLE 2 PCS-06-ART111001 PCS-06-ART432 PCS-06-ART321

GENERIC ARTICLE

PCS-06-ART141

PO QUANTITY 40 (per Variant) 40 8 (Article 1)

40 (Article 2)

OUN CAR CAR CAR

MINIMUM QUANTITY

10 30 200

GI QUANTITY 10 20 10

GI UNIT OF MEASURE

EA EA CT

STORAGE TYPE

H01 B01 F01

STORE RETAILING WHOLESALE

DELIVERY TYPE

UL LO

DISTRI-BUTION CHANNEL

30 20

SHIP-TO PARTY M001 PCS-C301

© SAP AG Page 11 of 74

Page 12: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

2 Prerequisites

2.1 ArticleThe articles provided are taken from category 06 and, in line with the Customizing settings supplied, they are moved into storage location 1003 using storage condition “WM”, with the connected warehouse number “PC1”.

In the article master, the warehouse management view within the “Logistics DC” view, without which no putaway can take place in warehouse management, is also maintained for this article.

2.2 Stocks

ProcedureCarry out a stock check. You can reach the stock overview (preferably in a second session) using the following paths:

IM Stock Overview:

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise Logistics Inventory management Environment Stock Stock overview

Transaction Code RWBE

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_STOREMANAGER-E (Retail Store Manager)

Business role menu In-store Inventory Management Inventory Lookup Stock Overview

2. On the Stock Overview screen, make the following entries:

Field name Description User action and values Comment

Article PCS-06-ART141001

(Fashion)

PCS-06-ART141

(Fashion)

Site VZ01

Storage location X Choose tab “List display”

3. Choose Execute.

4. Double-click Line“VZ01....“ Stock is displayed for each storage location

5. Choose a storage location stock line, choose item WM Stocks from menu Environment to display WM stock overview.

WM Stock Overview:

© SAP AG Page 12 of 74

Page 13: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Bins and Stock Display Total Stock per Article (Warehouse Management)

Transaction Code LS26

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Stocks & Bins Warehouse stocks per article

2. On the Stock Overview screen, make the following entries:

Field name Description User action and values Comment

Warehouse Number PC1

Article PCS-06-ART141001

(Fashion)

PCS-06-ART111001

(Fashion)

PCS-06-ART321

(Food)

PCS-06-ART323

(Food)

PCS-06-ART432

(Hard Goods)

Site VZ01

3. Choose Enter

4. Double click Line ‘VZ01 1003 …’ Stock is displayed for each storage bin.

5. Choose F3 and return back to Stock Overview screen, then choose MM stock figures to display IM Stock Overview.

You should note that certain steps in the process can only be carried out in certain stock situations. For example, stock removal is only possible if sufficient stock is available in the picking area. The processes in this scenario have been devised in such a way that in an initially empty warehouse the correct stock situation is produced for each process. However, if stock is already present in the warehouse or if processes are to be carried out separately, stock may have to be adjusted using goods receipts, goods issues, manual transfer posting or the physical inventory.

2.3 Using Mobile Terminals (Radio Frequency – RF)

Use© SAP AG Page 13 of 74

Page 14: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

If you want to use the RF functionality (radio frequency) to process shipments within the warehouse (see 4.4.2), the warehouse worker’s user (user currently in use) must be assigned to a queue (queue for transfer orders to be processed) in Customizing. The user currently in use must be assigned once to a queue in Customizing.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu SAP menuToolsCustomizingIMGProject AdministrationButton SAP Reference IMG

Transaction Code SPRO

IMG Menu Logistics Execution Mobile Data Entry RF Queue Management

2. Double-click Assign Processor to Queues

3. Choose New Entries

4. Make the following entries:

Field name Description User action and values Comment

Warehouse Number PC1

User Your User ID

Queue IN_PCS Choose with F4

Status selected

Screen format 8X40 Choose with F4

Main menu MAIN

5. Choose Enter

6. Choose Save

7. Choose Exit

2.4 Scenario Menu and Basic PathThe following basic path is the basis for all other paths in the process documentation. As an alternative to the SAP menu, you can use the process menu for navigational purposes. You can access this using the [Other menu] button in the SAP Easy Access menu.

SAP ECC menu Logistics Retailing

Transaction Code W10T

2.5 Additional Tools and WorkbenchesA large number of documents are processed every day, particularly in logistics. To provide a structured procedure and constant monitoring for this mass processing, a few support tools are available in the logistics area:

Warehouse Activity Monitor

Outbound Delivery Monitor

Rough Workload Estimate

© SAP AG Page 14 of 74

Page 15: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

These are introduced in more detail at the end of this scenario.

© SAP AG Page 15 of 74

Page 16: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

3 Process Flow and Overview

3.1 Process Overview TableStep Step Name External

Process Reference

Business Condition

Role Transaction Code

Expected Results

4.1.1.1 Create Purchase Order for Single Article

Retail Warehouse Clerk

ME21N

4.1.1.2 Create Purchase Order for Generic Article

Retail Warehouse Clerk

ME21N

4.1.2 Create Inbound Delivery Retail Warehouse Clerk

VL31N

4.1.3 Appointment Planning Retail Warehouse Clerk

WAP2

4.2 Receipt of Incoming Goods

4.2.1 Post Rough Goods Receipt Retail Warehouse Clerk

VL41

4.2.2 Enter an Actual Appointment Retail Warehouse Clerk

WAP2

4.2.3 Goods Receipt with Reference to the Rough Goods Receipt

Retail Sales

MB0A

© SAP AG Page 16 of 74

Page 17: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Step Step Name External Process Reference

Business Condition

Role Transaction Code

Expected Results

Person

4.3 Put away Preparation Retail Warehouse Clerk

LT06

4.4.1 Alternative 1: Asynchronous Warehouse Management

Alternative 1: Confirm without difference

Retail Warehouse Clerk

LT12

Alternative 2: Confirm with difference

Retail Warehouse Clerk

LT12

4.4.2.1 Resource Planning with the RF Monitor

Retail Warehouse Manager

LRF1

4.4.2.2 Log-on to the Terminal Retail Warehouse Clerk

LM00

4.4.2.3 Putaway Processing Retail Warehouse Manager

LRF1

5.1.1 Search for the Article Document for Goods Receipt

Retail Warehouse Clerk

MB03

5.1.2 Create a Return Delivery Retail Warehouse

MBRL

© SAP AG Page 17 of 74

Page 18: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Step Step Name External Process Reference

Business Condition

Role Transaction Code

Expected Results

Clerk

5.1.3.1 Issuing the Article Document as Goods Issue/Receipt Slip

Retail Warehouse Clerk

MB02

5.1.3.2 Create a Transfer Order in the Warehouse

Retail Warehouse Clerk

LB12

5.1.4 Goods Collection Retail Warehouse Clerk

LT12

6.1 Replenishment Planning Retail Warehouse Clerk

LP21

6.2.1 Create a Transfer Order Retail Warehouse Clerk

LB10

6.2.2 Confirm Transfer Order Retail Warehouse Clerk

LT12

7.1 Create an Outbound Delivery Retail Warehouse Clerk

VL01NO

7.2.1 Create Transfer Order as a Picking Document

Retail Warehouse Clerk

LT03

7.2.2.1 Alternative 1: Asynchronous

© SAP AG Page 18 of 74

Page 19: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Step Step Name External Process Reference

Business Condition

Role Transaction Code

Expected Results

Warehouse Management

Alternative 1: Confirm without difference

Retail Warehouse Clerk

LT12

Alternative 2: Confirm with difference

Retail Warehouse Clerk

LT12

7.2.2.2.1 Resource Planning in the Monitor for Mobile Data Entry

Retail Warehouse Manager

LRF1

7.2.2.2.2 Log-on to the Terminal Retail Warehouse Clerk

LM00

7.2.2.2.4 Monitor from Mobile Data Entry Monitor

Retail Warehouse Manager

LRF1

7.3 Post Goods Issue Retail Warehouse Clerk

VL02N

7.4.1 Create Deliveries with Planned Picking Time

7.4.1.1 Alternative 1: Manual Creation Retail Warehouse Clerk

VL01NO

7.4.2 Creating Wave Picks

7.4.2.1 Alternative 1: Automatic Retail VL35

© SAP AG Page 19 of 74

Page 20: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Step Step Name External Process Reference

Business Condition

Role Transaction Code

Expected Results

Capacity-Driven Creation of Wave Picks

Warehouse Clerk

7.4.2.2 Alternative 2: Creating Wave Picks Manually

Retail Warehouse Clerk

VL06P

7.4.3 Create Transfer Orders in Collective Processing

Retail Warehouse Clerk

LT42

7.4.4 Confirm Transfer Orders in Collective Processing

Retail Warehouse Clerk

LT25N

7.4.5 Subsequent Delivery Split Retail Warehouse Clerk

VLSP

7.4.6 Goods Issue in Collective Processing

Retail Warehouse Clerk

VL06G

8.1 Create a Physical Inventory Document

Retail Warehouse Clerk

LX16

8.2.1 Manual Entry Retail Warehouse Clerk

LI11N

8.2.2 Trigger Inventory Recount Retail Warehouse Clerk

LI14

© SAP AG Page 20 of 74

Page 21: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Step Step Name External Process Reference

Business Condition

Role Transaction Code

Expected Results

8.2.3 Carry Out Inventory Recount Retail Warehouse Clerk

LI11N

8.3.1 Post Differences in Warehouse Management

Retail Warehouse Clerk

LI20

8.3.2 Post Differences in Inventory Management

Retail Warehouse Clerk

LI21

8.4.1 Difference Statistics Retail Warehouse Clerk

LX18

8.4.2 Determine Inventory Status Retail Warehouse Clerk

LX25

9.1 Warehouse Activity Monitor Retail Warehouse Clerk

LL01

9.2 Outbound Delivery Monitor Retail Warehouse Clerk

VL06O

9.3 Wave Pick Monitor Retail Warehouse Clerk

VL37

9.4.1 Rough Workload Estimate After Creation of Outbound Deliveries

Retail Warehouse Manager

VLLG

© SAP AG Page 21 of 74

Page 22: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Step Step Name External Process Reference

Business Condition

Role Transaction Code

Expected Results

9.4.2 Rough Workload Estimate After Goods Issue

Retail Warehouse Manager

VLLG

© SAP AG Page 22 of 74

Page 23: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

4 Goods Receipt ProcessingThe goods receipt process is linked to ordering and displays the planning and execution of the receipt of warehouse merchandise. The basis for this is the purchase order, which is the first reference for follow-on documents in the flow of goods. In the simplest case, a goods receipt can be posted immediately for this purchase order. However, in a more complex process, steps such as inbound delivery (shipping notification) and rough goods receipt are added, to enable faster, more precise work in physical goods receipt.

Appointment planning is carried out in parallel to this document flow. Using this tool the planned and current capacity of the goods receipt store can be followed.

Following goods receipt, the physical putaway to a storage bin is carried out. This is necessary because of the warehouse management system (SAP R/3 WM) linked to storage location 1003. In goods receipt, incoming goods are checked, counted and then prepared for putaway. This always takes place, by the pallet, in storage locations with multi-bin location stockkeeping. The warehouse worker receives their operational method sheet in the form of a transfer order. They confirm this has been processed using the confirmation function (depending on the process variant, paper-based followed by creation in the warehouse office or directly online in the system using mobile data entry).

4.1 Preliminary Phase to Goods Receipt

4.1.1 Create Purchase Order

4.1.1.1 Create Purchase Order for Single Article

UseA purchase order is usually the end result of a complex procurement process. The scenario distribution center logistics can also use existing purchase orders from procurement scenarios if the articles used there have the necessary settings.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Store Retailing Purchasing Purchase Order Create Vendor Known

Transaction Code ME21N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Returns to Vendor Create Purchase Order

2. On the Create Purchase Order screen, make the following entries:

Field name Description User action and values Comment

Order type NB Standard PO

Vendor PCS-V321 (Food)

© SAP AG Page 23 of 74

Page 24: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

PCS-V431 (Hard goods)

Doc.date <Current date>

3. Choose Expand Header, then choose the Org.data tab.

4. On the Org.data tab, make the following entries:

Field name Description User action and values Comment

Purchasing Org. 1000

Purch. Group 100

Company Code 1000

5. Choose Expand Items, then choose Default Values

6. The Item Default Values dialog box appears, make the following entries:

Field name Description User action and values Comment

Site VZ01

7. Choose Save

8. In the Create Purchase Order screen area, make the following entries:

Field name Description User action and values Comment

Article PCS-06-ART323

(Food)

PO Quantity 8

Oun CAR

Article PCS-06-ART431

(Hard Goods)

PO Quantity 40

Oun CAR

9. Choose Enter.

10. Choose Save.

On the Save Document window dialog box, choose Save. Then you can see the message “Standard PO created under the number…” appears in the status bar.

4.1.1.2 Create Purchase Order for Generic Article

UseA purchase order is usually the end result of a complex procurement process. The scenario distribution center logistics can also use existing purchase orders from procurement scenarios if the articles used there have the necessary settings.

Procedure

1. Access the transaction choosing one of the following navigation options:

© SAP AG Page 24 of 74

Page 25: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

SAP ECC menu Logistics Store Retailing Purchasing Purchase Order Create Vendor Known

Transaction Code ME21N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Returns to Vendor Create Purchase Order

2. On the Create Purchase Order screen, make the following entries:

Field name Description User action and values Comment

Order type NB Standard PO

Vendor PCS-V141 (Fashion)

Doc.date <Current date>

3. Choose Expand Header, then choose the Org.data tab.

4. On the Org.data tab, make the following entries:

Field name Description User action and values Comment

Purchasing Org. 1000

Purch. Group 100

Company Code 1000

5. Choose Expand Items, then choose Default Values

6. The Item Default Values dialog box appears, make the following entries:

Field name Description User action and values Comment

Site VZ01

7. Choose Save

8. In the Create Purchase Order screen area, make the following entries:

Field name Description User action and values Comment

Article PCS-06-ART141

PO Quantity 40 (per Variant)

Oun CAR

9. Choose Enter.

10. Choose Save.

On the Save Document dialog box, choose Save. Then you can see the message “Standard PO created under the number…” appears in the status bar.

© SAP AG Page 25 of 74

Page 26: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

4.1.2 Create Inbound Delivery

UseUsing an inbound delivery the vendor announces the delivery of articles. An inbound delivery is a notification made using articles, quantities and dates (shipping notification). If this notification is sent using EDI the inbound delivery is automatically created in the system, otherwise it must be created manually.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Goods receipt Inbound Delivery Create

Transaction Code VL31N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing - Inbound Create Inbound Delivery

2. Input the purchase order number

3. Choose Enter

4. Input the Delivery date (Today’s date)

5. Choose Enter

6. Choose Save

7. The message “Inbound Delivery…has been saved”, note inbound delivery number

8. Choose Exit

4.1.3 Appointment Planning For the vendor’s notified inbound delivery the expected appointment for the receipt of goods is planned. Appointment dates can be defaulted automatically, however, the delivered algorithm does not take the time in the inbound delivery into consideration as many vendors are unable to transfer this. Your own appointment strategies can be implemented using the user exit.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Goods receipt Appointment Change Appointments

Transaction Code WAP2

© SAP AG Page 26 of 74

Page 27: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Receiving Change Appointments

2. In the Create Purchase Order screen area, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Door -

3. Choose Execute,

4. From menu “Go to” , choose Worklist

5. Select inbound delivery

6. Choose Propose Appointment Data(Door and appointment length are determined automatically)

7. make the following entries:

Field name Description User action and values Comment

Time from Now+1h

Time to Now+2h

8. Choose Adopt ( Field appears RED for the expected time)

9. Choose Save (The field appears PURPLE after saving)

10. Choose Back

11. Choose Exit

4.2 Receipt of Incoming GoodsIn goods receipt two different procedures are possible: goods receipt for purchase order (using transaction MB0A or MIGO) and goods receipt for inbound delivery (using transaction VL32N or delivery monitor). The two procedures should not be mixed up as otherwise the document flow to be updated is not error-free (see Note 199703). In Best Practices for Retail the first method is used. However, in some cases the second method might be better suited to mapping requirements.

Additional point:If you would like to use the goods receipt process for inbound delivery you can change this by making a few settings in the system. The goods receipt process would then take place using the process chain Create Inbound Delivery Putaway for Inbound Delivery Goods Receipt for Inbound Delivery. In this case the main tool used to mass process documents is the Inbound Delivery Monitor. The goods receipt for inbound delivery is highly recommended when the logistics processes in the LES components are to be viewed in isolation from the other processes in the retailing system, for example, if components are to be physically or logically separated.

For more details on goods receipt for inbound delivery see the SAP online documentation under Logistics Logistics Execution (LE) Goods Receipt Process for Inbound Delivery.

© SAP AG Page 27 of 74

Page 28: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

4.2.1 Post Rough Goods ReceiptUsing the rough goods receipt, preparatory work can be done for the actual physical goods receipt processing. The delivery note data is entered (usually in the office where the goods are accepted) and the reference to the order items is created. This serves to separate the individual steps in goods receipt processing and to reduce the time taken for the physical acceptance of goods.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Goods receipt Rough GR Create

Transaction Code VL41

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Receiving Create Rough GR

2. On the Create Rough Goods Receipt make the following entries:

Field name Description User action and values

Comment

Site VZ01

Inbound Delivery Create before

Check deliv. Date and change it necessary.

3. Choose Enter

4. Check data and change if necessary

5. Choose Save

6. The message “ Rough GR…has been saved”, note down number

7. Choose Exit

4.2.2 Enter Actual Appointment The driver reaches the agreed gate and announces that the goods are ready to be unloaded. The employee dealing with the goods receipt enters the actual arrival and departure time in the appointment document.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Goods receipt Appointment Change Appointments

Transaction Code WAP2

© SAP AG Page 28 of 74

Page 29: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Receiving Change Appointments

2. On the Appointments: Change screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Door

3. Choose Execute

4. Choose Maintain

5. Click appointment (Purple field, detail of appointment is displayed)

6. Choose Register (Next to field ‘Actual Time from’)

7. Choose Continue

8. Choose Adjust to Actual Time (The display of the door assignment is adjusted to the arrival time)

9. Choose Refresh

10. Choose Maintain ( Now the departure of the truck is registered (Door release))

11. Click door assignment (Yellow field) '

12. Choose Register (Next to field 'Actual Time to)

13. Choose Continue

14. Choose Adjust to Actual Time (The display of the door assignment is adjusted to the departure time)

15. Choose Refresh

16. Choose Save

17. Choose Back twice

4.2.3 Goods Receipt with Reference to Rough Goods ReceiptThe actual goods receipt is now posted, on the basis of the rough goods receipt, and the actual quantity received is entered.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Inventory management Goods movement Goods receipt For purchase order For purchase order PO number unknown

Transaction Code MB0A

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_STOREMANAGER-E (Retail Store Manager)

© SAP AG Page 29 of 74

Page 30: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Business role menu In-store Inventory Management Receiving with and without Reference Doc. Post Goods Receipt for other reference

2. On the Goods Receipt – PO Unknown: Initial Screen, make the following entries:

Field name Description User action and values Comment

Movement Type 101

Site VZ01

Storage Location 1003

Rough GR Created before

3. Choose Enter

4. Choose Post

Only for food articles where the minimum remaining shelf life has been maintained:

1. The message “ Enter the shelf life expiration date” appears,

2. Input the Exp.Dt (Date that is at least 100 days in the future, If shortfall of remaining shelf life (100 days) the goods receipt is rejected.)

3. Choose Enter.

4. The message “Quantity in order price unit is set automatically” appears.

5. Choose Enter

6. The message “Document ... posted” appears.( Note down GR number)

7. Choose Exit

4.3 Put away PreparationAs a result of the goods receipt, a transfer requirement (TR) and a quant were automatically created in the goods receipt area. From the transport requirement, a transfer order (TO) must now be created describing the put away for the quant within the warehouse. A storage bin is found for every quant, based on the customized strategies.

ProcedureThis step is usually automated in productive operation.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Inbound Process Goods Receipt for Purchase Order, Order, Other Transactions Putaway Create Transfer Order For Article Document

Transaction Code LT06

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

© SAP AG Page 30 of 74

Page 31: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Create TO for Article Document

2. On the Create Transfer Order for Article Document: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Article Document Created before

Article Doc. Year Current year

Warehouse Number blank

Foreground/Background blank

For non-mixed pallets, automatic palletization can be used, based on the system proposal (food, hard goods):

3. Choose Enter.

4. Choose Palletization.

5. Choose Enter (Palletization proposal is accepted).

6. Choose Putaway foreground.

7. The message Check your entries appears. The storage bin can be changed manually.

8. From menu Environment, choose Stor.bin search log (Location determination can be reproduced).

9. Choose Enter to confirm the data.

10. Choose Post.

11. The message Transfer order 0000000XXX created appears, note down document number.

12. Choose Exit.

13. Popup window Active items exist appear, choose Yes to confirm.

If mixed pallets are put away in the reserve storage area, the system must be informed what form the palletization will take. All variants of the generic article are delivered on one pallet and put away like that in the warehouse (fashion):

14. Choose Enter.

15. Choose CREATE SU (SINGLE).

16. Input E1 into the Storage Unit Type field.

17. Choose Create TRANS.Order.

© SAP AG Page 31 of 74

Page 32: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

18. Choose Create.

19. Choose Post.

20. The message Transfer order 0000000XXX created. Note down document number.

21. Choose Exit.

4.4 Carry Out PutawayWhen carrying out putaway, a difference can be made between different forms of warehouse organization.

When asynchronous processing is used, the transfer order is printed in the form of a putaway document and transferred to a subsystem (PDC). After the putaway has been carried out, the item is confirmed either by the creation of the putaway document, the reply to a warehouse terminal or by recording over PDC data.

With synchronous processing the warehouse worker is permanently supplied with putaway orders by a radio-frequency terminal. Confirmation takes place directly online in the destination storage bin, using the radio-frequency terminal in SAP R/3.

4.4.1 Alternative 1: Asynchronous Warehouse ManagementAfter the transfer to the storage bin is completed the transfer order must be confirmed. The result of this is that the quant is finally posted to the storage bin. You can choose to confirm with or without a quantity difference. Confirmation can take place in automated warehouses using radio-controlled PDC units, either online in SAP R/3 or using the RF functionality or using separate systems.

ProcedureAlternative 1: Confirm without difference

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm Transfer Order Single Document In One Step

Transaction Code LT12

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Confirm transfer order

2. On the Confirm Transfer Order: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Transfer Order No. Created before

Warehouse Number PC1

Foreground/ 'Background'

© SAP AG Page 32 of 74

Page 33: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Background

3. Choose Enter

4. The message “Transfer order ... confirmed” appears.

5. Choose Back, choose Save.

Alternative 2: Confirm with difference

This is the case when it is discovered in put away that there is a difference between the goods receipt quantity or when part of the merchandise is damaged during transfer to the storage location.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm Transfer Order Single Document In One Step

Transaction Code LT12

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Confirm transfer order

2. On the Confirm Transfer Order: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Transfer Order No. Created before

Warehouse Number PC1

Foreground /Background

'Foreground‘

3. Choose Enter

4. On the Confirm Transfer Order make the following entries:

Field name Description User action and values

Comment

Actual qty (first item). blank

Aun EA; EA; CT

Difference qty 1 A unit was damaged during putaway.

D on the right side in the position

Set flag

5. Choose Save

6. The message” Act.quantities and diff.quantities are not target quantities. Check entry” appears,

© SAP AG Page 33 of 74

Page 34: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

7. Choose Enter

8. The message” Act.quantities and diff.quantities are not target quantities. Check entry”

9. Input C field with” U ”

10. Choose Enter

11. The message" Check the difference posting” appears.

12. Choose CONFIRM DIFFERENCE, Difference is “put away” in difference storage type 999.

13. The message “Transfer order 000... confirmed ” appears.

By confirming with difference, the missing quantity is posted to the difference storage type. All known difference quantities of an article are collected there and as a result counterbalance one another. Goods that have been damaged or have disappeared are first corrected in the IM stocks, in terms of value and quantity, using inventory adjustment posting. However, usually this does not take place immediately but rather after several difference quantities have been collected, for example, once a day.

4.4.2 Alternative 2: Synchronous Warehouse Management

Procedure

This variant displays the putaway process from the point of view of the warehouse worker, using mobile SAP R/3 Frontends via radio frequency (RF). To do this the user makes use of special transactions in SAP R/3 (as opposed to using a separate system) that are processed in the mobile terminals by a special GUI (SAPConsole), but can also be displayed using the standard GUI.

4.4.2.1 Resource Planning with the RF MonitorIn the warehouse office, the warehouse worker is assigned to the goods receipt queue.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Mobile Data Entry Monitor Mobile Data Entry

Transaction Code LRF1

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-E (Retail Warehouse Manager)

Business role menu Warehouse Management Warehouse Controlling RF- Monitor, Active

2. On the RF Monitor screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1 only if transaction is used the first time

© SAP AG Page 34 of 74

Page 35: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

3. Choose Enter

4. Completely expand the controlling tree in the left subscreen.

In the subscreen ‘User’ (bottom right) the user currently in use should now be displayed (if not, see section on preconditions). In the subscreen ‘Transfer orders’ (top right) the entire worklist of stock movement is listed.

To the left of the subscreen the individual queues are displayed with their transfer orders and the processors assigned to them.

If the current user is not assigned to the goods receipt queue (IN_PCS), this must take place now:

1. Select ‘processor’ from the line with <current user> in the subtree

2. Drag & Drop the highlighted line to the queue ‘IN_PCS’, The current user is entered under IN_PCS as the processor

4.4.2.2 Log-on to the TerminalAt the beginning of the process the warehouse worker logs on to the radio-frequency terminal. It is best if you call this transaction in a new session.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Mobile Data Entry Mobile Data Entry

Transaction Code LM00

The radio-frequency terminal starts this transaction immediately after you have logged on to the system (no path required).

2. Choose Save

4.4.2.3 Putaway ProcessingIn the next stage transfer orders are taken by the system from the goods receipt queue, item by item, for processing. Alternatively you can make a selection, for example, by scanning a storage unit in goods receipt.

1. Choose INBOUND PROCESS

2. Choose PUTAWAY

3. Choose PUTAWAY BY TRANSFER ORDER

4. Choose Save, The agent goes to the source bin (GR zone), takes the required quantity and confirms processing of the item

5. Choose Next, Destination bin is displayed and the agent moves the merchandise there.

6. The putaway bin is checked by scanning, here this is simulated by making manual entries

7. Empty field to the right of the defaulted storage bin (verification field). Storage bin number without letters or hyphens> For example ’010203’ at bin ’01-02-03’

8. Choose Save, The agent puts the goods away and confirms the item

© SAP AG Page 35 of 74

Page 36: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Repeat these processing steps for all items, until no more items are proposed.

4.4.2.4 Monitor with RF MonitorThe work in progress is now controlled in the first session from the point of view of the supervision of the warehouse.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Mobile Data Entry Monitor Mobile Data Entry

Transaction Code LRF1

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-E (Retail Warehouse Manager)

Business role menu Warehouse Management Warehouse Controlling RF- Monitor, Active

2. On the RF Monitor screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1 only if transaction is used the first time

3. Choose Enter

4. Completely expand the controlling tree in the left subscreen, The transfer order is removed from the goods receipt queue (IN_PCS).

5 Return DeliveriesIn return deliveries, goods that are already in the warehouse are sent back to the vendor. The reason for a return delivery can, for example, be a callback campaign by the vendor or the return of store or customer returns or promotional merchandise. No return delivery is made if, for example, goods were already rejected at the point of goods receipt because they did not meet the required quality standard or the minimum shelf-life.

There are two standard ways of triggering a return delivery.

You create a return item in a purchase order and in doing so you inform the vendor of the return delivery. This return item then produces a negative stock posting in the goods receipt for the purchase order. However, if you use this procedure the reference to the original goods receipt and the purchase price at that particular point in time is lost. This is because the returns order item refers to the current purchase conditions.

If the original goods receipt document for the merchandise can still be retrieved it is advisable to create a return delivery with reference to this document, the original valuation is then retained. This is the procedure used here to carry out a return delivery.

In both cases a corresponding negative quant is created in the goods receipt zone of the warehouse, where it is offset against the quant of the article that is ready for collection (manual

© SAP AG Page 36 of 74

Page 37: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

stock transfer from the stock transfer to the GR zone). It is also possible to collect the merchandise once the negative goods receipt has been posted and then clear the negative quant afterwards.

The system creates an article document for the system that you can print out as a return delivery document. As the return delivery has to be valuated, the system creates an accounting document. The system cancels all the stock and G/L account updates that it has posted in the goods receipt posting. The system also cancels the updates posted with the goods receipt. The quantity returned increases the open purchase order quantity.

In Customizing for the stock movement types, the return delivery item can also be moved to other storage types, for example, to the goods receipt zone or a special return zone.

5.1 Prepare Return Deliveries

5.1.1 Search for Article Document for Goods ReceiptIf you no longer have the number of the original goods receipt document you can find this out by using various criteria in the F4 help in transaction MB03, for example, vendor, article number, date, transaction type and delivery note (reference). The obvious thing is to use the field ‘Reference’ for a search, as an article can be delivered several times in one day, with the result that the date is not a precise selection criterion. However, the date and delivery note, in addition to specifying the article and the vendor, should be sufficient to be able to find the exact goods receipt document and then the exact storage bin.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise Logistics Inventory management Article document Display

Transaction Code MB03

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Article documents Display Article Document (MB03)

2. On the Display Article Document: Initial Screen , make the following entries:

Field name Description User action and values Comment

Artic. Doc. Year current year

3. Place the cursor in ‘Article Document’

4. Choose F4

5. On the Article Document List screen, make the following entries:

Field name Description User action and values Comment

Article PCS-06-ART141001

(Fashion)

PCS-06-ART323

Important: Do not select generic article

© SAP AG Page 37 of 74

Page 38: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Field name Description User action and values Comment

(Food)

PCS-06-ART431

(Hard Goods)

Site VZ01

Storage Location 1003

Vendor PCS-V141 (Fashion)

PCS-V321 (Food)

PCS-V431 (Hard Goods)

6. Choose Execute

The list should display the goods receipt document from 4.2.3 which is used to return the goods in the next section.

5.1.2 Create a Return DeliveryThe return delivery is carried out with reference to the goods receipt document. By doing this, goods receipt items can be proposed and then changed, that is to say adopted, adopted with a quantity change or deleted. Selected or changed items are canceled. This means that stock postings for each article are corrected again using this transaction. This transaction is the equivalent of canceling a goods receipt document, with the option of making changes to data.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menun Logistics Retailing Merchandise logistics Inventory management Article document Return delivery

Transaction Code MBRL

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Outbound Return Delivery for Artl Document

2. On the Enter Return Delivery: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Article Doc. Created before

Artic. Doc. Year This year

Reason for Mvmt '0003'

(Movement type '122')

Flag: Create Delivery blank

Flag: Print x

3. Choose Print Version ' Indiv.Slip w.Inspect.Text '

© SAP AG Page 38 of 74

Page 39: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

4. Choose Enter

5. Input the quantity, (50% of the amount per item (half palettes also possible!))

6. Choose Post

7. The message “Document...posted “ appears, note document number.

8. Choose Back.

From this point the quantity is booked out of inventory management (IM).

5.1.3 Prepare for Collection

5.1.3.1 Issue Article Document as Goods Issue/Receipt SlipYou can use the article document when you need to specify a document relating to the goods return procedure for the vendor. This can, for example, also be attached to the merchandise if it is to be left in a separate storage zone until the next time the vendor comes. Before goods can be issued, message records have to be maintained in Customizing. Regardless of how the message record has been maintained, the article document is printed

as soon as the goods movement is saved or

after the corresponding report has been triggered or

with an application-specific transaction.

The printout is set up here (see Customizing) so that the article document is printed using the application-specific transaction. The message is created automatically in the available message record when the document is saved and is then displayed as described below.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Inventory management Article document Change

Transaction Code MB02

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Article documents Change Article Document

2. the Change Article Document: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Article Doc. Created before

3. Choose Enter

4. Double-click on one of the items for output

5. Choose Messages

If the message has already been processed in Customizing the message record is displayed. According to your settings the ‘traffic light’ will either be yellow, if the message has not yet been

© SAP AG Page 39 of 74

Page 40: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

printed, or green, if it was printed when the goods movement was saved, (flag [Print] in transaction MBRL).

If no printer is set up, you can view the printed message in the system:

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Inventory management Article document Print/transmit

Transaction Code MB90

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Article Documents Output Processing for Art.Documents

2. On the Output from Good Movements screen, make the following entries:

Field name Description User action and values Comment

Output Type WE01

Transmission Medium 1

Processing mode 2

Article document Created before

3. Choose Execute

4. The message “…output (has been) selected …”

5. Select the required item

6. Choose Print Preview

7. Choose Back ( to last view )

8. Choose Process (to print it out)

5.1.3.2 Create a Transfer Order in the WarehouseAfter you have created a return delivery the goods are identified in the warehouse and put aside for the return delivery.

A transfer requirement was automatically created for the article document for the return delivery. At this point it is now converted to a transfer order so that the goods in the warehouse are no longer available to anyone else.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Transfer Requirement Display For Article Document

Transaction Code LB12

© SAP AG Page 40 of 74

Page 41: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Article documents TRs and Posting Change for Art. Doc.

2. On the Process Article Document: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Article Document Created before

Article Doc. Year current year

3. Choose Enter

4. Choose TO in Foregr.

5. On the screen, make the following entries:

Field name Description User action and values

Comment

Storage type K01

R01

H01

B01

F01

6. Choose STOCK FIGURES

You will see an overview of removable stock. The goods receipt document for the storage unit is listed in the column ‘GR Number’. Look for items with the GR number from 5.1.1 or 4.2.3 and enter the quantity to be returned for each storage unit.

1. Selected quantity, If necessary, in several items until the quantity displayed in the field ‘open quantity’ has been reached.

2. Choose STOCK REMOVAL FOREGROUND

For each storage unit to be moved:

1. Check your entries.

2. Choose Enter.

Choose GENERATE + NEXT ART. If there are several articles or variants of a generic article, repeat the process until no items remain in the worklist.

Choose Post

The message “Transfer order ... created” appears, Note transfer order number.

Choose Back

© SAP AG Page 41 of 74

Page 42: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

By doing this the merchandise is reserved by the transfer order and is no longer available for picking or for internal warehouse replenishment.

5.1.4 Goods CollectionWhen the vendor collects the goods they are taken directly from the storage bin to the truck. Once the transfer order is confirmed the process is concluded.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Stock Transfer Confirm Transfer Order Single Document In One Step

Transaction Code LT12

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Confirm transfer order

2. On the Confirm Transfer Order: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Transfer Order No. Created before

Warehouse Number PC1

Foreground/Background Background

3. Choose Enter

4. The message “Transfer order ... confirmed” appears.

5. Choose Back.

6 Internal Warehouse Replenishment This process shows how you can automatically check and replenish the stock in the picking area. For this the picking area is organized as a fixed storage area. This means that every article always has a fixed storage bin. These picking areas are continually supplied from a reserve storage area (for example, a high rack storage area). In the article master data both the fixed bin in the picking area and the replenishment parameters are maintained. If the minimum quantity is not met, then the bin is filled to the maximum quantity. This means the quantity being replenished can always be rounded up to a defined replenishment quantity (or to a multiple of it).

Another replenishment procedure exists that enables you to take open outbound deliveries into account. This procedure can run at the end of the day to determine which fixed storage bins must be filled up for picking on the following day. The system creates the transfer requirements necessary for this day. In addition, it is possible to trigger replenishment planning for a storage bin immediately after confirmation of an outbound delivery transfer order for this storage bin. In this case a transfer order is created immediately, without a transfer requirement having been created first.

© SAP AG Page 42 of 74

Page 43: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Usually many of the processes described here take place automatically in the background, so that apart from confirming a goods movement no manual intervention is required.

Carrying out internal warehouse replenishment depends on your choice of article. Internal warehouse replenishment must be carried out for >ARTICLE 1. There is a difference here between a stock placement bin and a stock removal bin. If you have chosen >ARTICLE 2 carry on from unit 5. For >ARTICLE 2 the stock placement and stock removal bin are identical and internal warehouse replenishment is not possible.

6.1 Replenishment PlanningTo trigger replenishment in the picking area, the stock available there must fall below the replenishment quantity (>MINIMUM QUANTITY). To be able to carry out replenishment the corresponding quantity of stock must be available in the reserve storage area.

If the correct stock situation exists the replenishment requirement is shown as having been triggered. In productive operation it is helpful to periodically schedule the programs (in this case, RLLNACH1, or alternatively RLLNACH2 or RLLNACH4) to automate the procedure.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Stock Transfer Planning of Replenishments According to Bin Situation

Transaction Code LP21

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Replenishment WM replenishment for fixed bins

2. On the Replenishment for Fixed Bins in WM screen, make the following entries:

Field name Description User action and values

Comment

Site VZ01

Storage location 1003

Warehouse number PC1

Storage type K01

3. Choose Execute, All storage bins to be filled up are displayed with article and replenishment quantity.

4. Select the required items

5. Choose Detail, The calculated replenishment quantity for the selected item is displayed.

6. Choose Back

7. Choose Article Staging

© SAP AG Page 43 of 74

Page 44: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

8. The message “Staging of articles processed without errors “appears.

9. Choose Save

10. The message “Picking requests created in required quantity “appears.

6.2 Carry Out Replenishment

6.2.1 Create a Transfer Order

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Stock Transfer Create Transfer Order By Replenishment For Storage Type

Transaction Code LB10

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Replenishment TRs for Storage Type

2. On the Display Transfer Requirement: List for Storage Type screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Source Storage Type blank

Dest. Storage Type K01

3. Choose Enter.

4. The message “Select the created replenishment TRs “

5. Choose To In BackGR

6. The message “Transfer order 000...created “ appears, Note document number

If an error occurs at this point (“Storage bin could not be found”) this is because there is insufficient stock available in the reserve storage area. Carry out a goods receipt with putaway for this article and at the end repeat the creation process for the transfer order.

If you plan program RLLAUTA10 as a batch job, the transfer requirements that are linked to a certain movement type (in this case movement type 320) are converted into transfer orders. The result of this is that the process step can be automated.

© SAP AG Page 44 of 74

Page 45: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

6.2.2 Confirm Transfer OrderOnce the transfer order is confirmed, the warehouse worker announces the successful transfer of goods from the reserve storage area to the picking area. The stock is booked into the corresponding storage bin and is available for picking.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm Transfer Order Single Document In One Step

Transaction Code LT12

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Confirm transfer order

2. On the Confirm Transfer Order: Initial Screen , make the following entries:

Field name Description User action and values

Comment

Transfer Order No. Created before

Warehouse Number PC1

Foreground/ Background

'Background'

3. Choose Enter

4. The message “Transfer order ... confirmed.” Appears.

As in 4.4, you can confirm a transfer order using a mobile terminal or you can confirm with a difference.

7 Goods Issue ProcessingWith stock removal, picking documents (transfer orders) are created using the outbound deliveries due to be delivered (depending on the process variant, individually using the delivery number, in collective processing using the Outbound Delivery Monitor or on a time period basis by forming wave picks. The picker confirms the processing again using confirmation (paper-based with individual entry, paper-based with collective processing or using mobile data entry). Finally the goods receipt is posted (individually for each outbound delivery or collectively).

For a complete demonstration of the preconfigured functionality, goods issue processing can be carried out in several variants. An easy version highlights the document flow and the main process procedure. A more complex variant displays the procedure when using mass processing and monitoring functions. A third variant demonstrates the functionality of the mobile data entry from the perspective of the warehouse worker.

© SAP AG Page 45 of 74

Page 46: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

7.1 Create Outbound DeliveryAs a precondition of stock removal of merchandise an outbound delivery is created in the following section. In the simplest case the outbound delivery is created as an individual document without reference, although usually it is done using the worklist of the existing store purchase order or sales orders. You can also process sales orders, purchase orders and deliveries created in other scenarios, if the articles used have the correct settings for the logistical processing.

When you create a delivery you have to select either the retail or the wholesale variant. Logistical processing is similar. However, the variants of the outbound delivery document are different.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Create Single Document Without Order Reference

Transaction Code VL01NO

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Shipping Create Outbound Dlv. w/o Order Ref.

2. On the Create Outbound Delivery Without Order Reference screen, make the following entries:

Field name Description User action and values

Comment

Shipping Point VS01

Delivery Type UL (Retail)

LO (Wholesale)

Sales Organization 1000

Distribution Channel 30(Retail)

20 (Wholesale)

Division 10

3. Choose Enter

4. On the Del .for Stock Trans. Create: Overview screen, make the following entries:

Field name Description User action and values

Comment

Ship-To Party M001(Retail)

PCS-C301 (Wholesale)

Planned GI Today

© SAP AG Page 46 of 74

Page 47: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Field name Description User action and values

Comment

Article (first item) PCS-06-ART141001 (Fashion)

PCS-06-ART323 (Food)

PCS-06-ART431 (Hard Goods)

Delivery quantity (first item)

10

Un (first item) EA

CAR

EA

5. Choose Enter

6. Mark item 10

7. Choose Item Details (lower left)

8. Choose the 'Picking' tab.

9. Make the following entries:

Field name Description User action and values Comment

Site VZ01

Storage Location 1003 Monitor values

12. Choose Save.

13. The message “Del. … has been saved” appears, note document number.

14. Choose Exit.

7.2 Stock Removal/Picking

7.2.1 Create Transfer Order as a Picking DocumentYou subsequently create a transfer order as an instruction for stock removal or as a picking document with reference to the outbound delivery.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Picking Create Transfer Order Single Document

Transaction Code LT03

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

© SAP AG Page 47 of 74

Page 48: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Create TO for Delivery

2. On the Create Transfer Order for Delivery Note: Initial Screen , make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Delivery Created before

Foreground/ Background

'System-Guided'

Adopt pick.quantity Blank

3. Choose Enter

4. On the Create TO for Delivery 80000XXX 000XXX: Prepare for Stock Removal screen, make the following entries:

Field name Description User action and values

Note

Storage Type R01 H01 B01 F01 Search Scope

5. Choose Stock Figures. Article stock in picking bin is displayed.

6. Choose Back.

7. Choose Stock Removal Foreground. A storage bin is automatically found, based on the stock removal strategy.

8. Choose Stock Figures, article stock in picking bin is displayed.

9. Choose Stock Removal Foreground, A storage bin is automatically found, based on the stock removal strategy.

10. The message “Check your entries “ appears

11. From the menu “Environment “, choose Stor.bin search log, location determination can be reproduced. The storage bin can be changed manually.

12. Choose Back

13. Choose Enter, possibly several times if the total quantity covers several quants.

Proceed as follows if there are other items awaiting stock removal:

Choose Generate + Next Art., repeat the procedure for the other items using Stock Removal Foreground.

Choose Post

The message “ Transfer order 000…created “, note document number.

Choose Exit.

© SAP AG Page 48 of 74

Page 49: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

7.2.2 Carry Out PickingWith the confirmation of the transfer order, picking is also confirmed and the goods are posted from the store location to the goods issue zone. As in 4.4 there are various alternative procedures.

7.2.2.1 Alternative 1: Asynchronous Warehouse ManagementAlternative 1: Confirm without difference

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm Transfer Order Single Document In One Step

Transaction Code LT12

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Confirm transfer order

2. On the Confirm Transfer Order: Initial Screen , make the following entries:

Field name Description User action and values

Comment

Transfer Order No. Created before

Warehouse Number PC1

Foreground/Background 'Background'

3. Choose Enter

4. The message “Transfer order 000...confirmed” appears.

Alternative 2: Confirm with difference

This is the case when a missing quantity is discovered during picking or when some of the goods are damaged during transfer to goods issue.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm Transfer Order Single Document In One Step

Transaction Code LT12

© SAP AG Page 49 of 74

Page 50: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing Inbound Confirm transfer order

2. On the Confirm Transfer Order: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Transfer Order No. Created before

Warehouse Number PC1

Foreground/Background 'Foreground'

Adopt pick.quantity blank

3. Choose Enter

4. Input D (for 1st item) (scroll screen to extreme right), check flag

5. Choose Post

6. Make the following entries:

Field name Description User action and values

Comment

C S

Actual quantity 9

7. Choose Enter (Quantity difference is calculated automatically. Alternative: enter quantity difference to calculate actual quantity.

8. The message “Check the difference posting” appears.

9. Choose CONFIRM DIFFERENCE

10. The message “Transfer order ... confirmed.” Appears.

By confirming with difference, the missing quantity is posted to the difference storage type. All known difference quantities of an article are collected there and as a result they balance themselves out. Goods that have been damaged or have disappeared are first corrected by value and quantity in Inventory Management using inventory adjustment posting (see 8.3.2). However, usually this does not take place immediately but rather after several difference quantities have been collected, for example, once a day.

7.2.2.2 Synchronous Warehouse Management

7.2.2.2.1 Resource Planning in the Monitor for Mobile Data Entry

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Mobile Data Entry Monitor Mobile Data Entry

© SAP AG Page 50 of 74

Page 51: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Transaction Code LRF1

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-E (Retail Warehouse Manager)

Business role menu Warehouse Management Warehouse Controlling RF- Monitor, Active

2. On the RF Monitor screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1 only if transaction is used the first time

3. Choose Enter

4. Completely expand the controlling tree in the left subscreen.

In subscreen ’User’ (bottom right) the current user is displayed. In subscreen ’Transfer Orders’ (top right) the entire worklist of stock movements is listed.

In the subscreen on the left the individual queues are displayed with their transfer orders and the processors assigned to them.

If the current user is not assigned to the goods issue queue (OUT_PCS), this must take place now:

1. Highlight ‘processor’ from the line with <current user> in the subtree

2. Drag&Drop the highlighted line to the queue ‘OUT_PCS’, the current user is entered under OUT_PCS as the processor.

7.2.2.2.2 Log-on to the TerminalAt the beginning of the process the warehouse worker logs on to the radio-frequency terminal. It is best if you call this transaction in a new session.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Internal Whse Processes Mobile Data Entry Mobile Data Entry

Transaction Code LM00

The radio-frequency terminal starts this transaction immediately after you have logged on to the system (no path required).

2. Choose Save.

7.2.2.2.3 Stock Removal ProcessingIn the next stage, transfer orders are taken by the system for processing from the goods receipt queue, item by item.

1. Choose Outbound process.

2. Choose Picking/Replenishment.

© SAP AG Page 51 of 74

Page 52: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

3. Choose Picking by Transfer Order.

Key in Transfer Order 0000000XXX generated in last step.

4. Choose F4, TO item is proposed (source bin ), The storage bin and the storage unit are both scanned for verification purposes.

5. On the RF menu screen, make the following entries:

Field name Description User action and values

Comment

Source Bin (3. field) For example, “04002” at KOM-04-002.

Source SU Enter the storage unit numbers as displayed in field to the left of the verification field.

Alternative 1: Confirmation without quantity difference

Choose Save

Choose F4-NXT (next)

Choose Save

Alternative 2: Confirmation with quantity difference

1. Choose F6 DIFF, The item is confirmed with the difference.

2. On the RF menu screen, make the following entries:

Field name Description User action and values

Comment

Dest.diff. qty 1 1 unit was damaged during picking

3. Choose F1 CONF, Processor confirms difference and processing of the item

4. Choose SAVE

5. Choose F4 NXT(next), Destination bin is displayed and the processor transfers the goods there.

6. Choose F1 SAVE, The processor stores the goods in the goods issue area and confirms all the items at the same time.

If there are other items to be processed repeat the above procedure accordingly.

1. Choose F3 BACK

2. Choose F8 LOff (log off) , Session is closed

3. Choose 3x [F3] (back), Session stays open.

7.2.2.2.4 Monitor from Mobile Data Entry MonitorThe work in progress is now controlled in the first session from the point of view of the supervision of the warehouse.

1. Access the transaction choosing one of the following navigation options:

© SAP AG Page 52 of 74

Page 53: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

SAP ECC menu Logistics RetailingMerchandise logistics Logistics execution Internal Whse Processes Mobile Data Entry Monitor Mobile Data Entry

Transaction Code LRF1

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name)

SAP_BP_RT_WAREHOUSESPECIAL-E (Retail Warehouse Manager)

Business role menu Warehouse Management Warehouse Controlling RF- Monitor, Active

2. On the RF Monitor screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1 only if transaction is used the first time

3. Choose Enter

4. Completely expand the controlling tree in the left subscreen.

The goods issue queue (OUT_PCS) should now be empty

7.3 Posting Goods IssueTo reduce stock from an inventory management viewpoint, a goods issue must now be posted. If a difference was discovered at the point of picking, the outbound delivery is only partially picked. In this case the remaining quantity must first be picked (repeat procedure in 7.2) or the delivery quantity must be changed. In addition, during picking it was already clear that the delivery quantity could be adjusted to meet any possible differences.

Changing the delivery quantity (only with partially picked outbound deliveries):

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Post Goods Issue Outbound Delivery Single Document

Transaction Code VL02N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name)

SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Shipping Change Outbound Delivery

© SAP AG Page 53 of 74

Page 54: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

2. On the Change Outbound Delivery screen, make the following entries:

Field name Description User action and values Comment

Outbound Delivery Created before

3. Choose Enter

4. Choose the 'Picking' tab.

5. Input Delivery quantity (for incomplete items): Quantity from field ‘Pick Quantity’

6. Choose Enter

7. Choose Save

8. The message “Del. … has been saved.” Appears.

Posting the goods issue:

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Post Goods Issue Outbound Delivery Single Document

Transaction Code VL02N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name)

SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Shipping Change Outbound Delivery

9. On the Change Outbound Delivery screen, make the following entries:

Field name Description User action and values Comment

Outbound Delivery Created before

2. Choose Post Goods Issue

3. The message “Del. … has been saved.” Appears

7.4 Variant: Mass Processing of Deliveries

7.4.1 Create Deliveries with Planned Picking TimeIn the following section several deliveries with picking date, transportation planning date, loading date, planned goods issue date and delivery date will be created. One of these dates is used as a criterion for forming wave picks. In our example the picking date is the criterion we have used.

For demonstration purposes at least three outbound deliveries, with three items each (the same article can be used), should be created. So that there is no overlapping with other processes when you are processing outbound deliveries, when you create the outbound deliveries you should use a date in the future. This should be established once and then used as a setting in all “<DATE>” fields. Here you must remember that only as many articles can be delivered as are available in the warehouse (small number of pieces in the items).

© SAP AG Page 54 of 74

Page 55: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

The outbound deliveries should be created in such a way that the picking date of both the first and second outbound deliveries falls into the second time slot and the picking date for the third outbound delivery falls into the third time slot.

7.4.1.1 Alternative 1: Manual Creation

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Create Single Document Without Order Reference

Transaction Code VL01NO

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Shipping Create Outbound Dlv. w/o Order Ref.

2. On the Create Outbound Delivery Without Order Reference screen, make the following entries:

Field name Description User action and values Comment

Shipping Point VS01

Delivery Type UL (Retail)

LO (Wholesale)

Sales Organization 1000

Distribution Channel 30 (Retail)

20 (Wholesale)

Division 10

3. Choose Enter

4. On the Del.for Stock Trans. Create: Overview screen, make the following entries:

Field name Description User action and values Comment

Ship-To Party M001

PCS-C301

Planned GI <DATE>

Article (1st item) PCS-06-ART141001 (Fashion)

PCS-06-ART321 (Food)

PCS-06-ART431 (Hard Goods)

Goods issue quantity (first item)

5

SU (1st item) EA

© SAP AG Page 55 of 74

Page 56: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Field name Description User action and values Comment

CAR

Enter a further two items with identical data.

5. Choose Enter

6. If message Result of item scheduling is goods issue date YYYY.MM.DD appears. Choose Continue. Planned goods issue is overwritten.

7. Mark item 10

8. Choose Item Details

9. Choose the Picking' tab.

10. Make the following entries:

Field name Description User action and values Comment

Site VZ01

Storage Location 1003 Monitor values

11. From the menu Go to, choose Header, choose Processing

12. Make the following entries:

Field name Description User action and values Comment

Picking Enter the following values as picking dates:

1. Delivery: 09:20(for the others, see times below).

13. Choose Save

14. The message “Del. … has been saved” appears. Note down document number

Repeat the procedure twice so that altogether you create three outbound deliveries. The picking times you should enter are 09:20, 10:20 and 13:20.

7.4.2 Create Wave PicksTo allow for mass processing, deliveries are formed into groups and wave picks. These groups or wave picks can either be created automatically, with account being taken of capacity restrictions, or they can be created manually.

If you do not wish to use wave picks you can use the Outbound Delivery Monitor to steer a large number of deliveries through the steps of the picking process (see 9.2).

7.4.2.1 Alternative 1: Automatic Capacity-Driven Creation of Wave PicksTime slots have been entered for the distribution center (VZ01) that are used to represent the normal working times of a picker.

Time slot 1 from the start of work at 06:00 until the breakfast break at 09:00.

Time slot 2 from the end of the break at 09:15 until the lunch break at 12:15.

Time slot 3 from the end of the lunch break at 13:00 until the end of the shift at 16:00.

© SAP AG Page 56 of 74

Page 57: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

If the planned goods issue date (other dates are possible as well, for example the picking date) for several deliveries falls into one of these time slots the deliveries are then grouped into wave picks. Time slots for different workdays can be stored in wave pick grids.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Wave Picks Create According to Delivery Time

Transaction Code VL35

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Create Wave Picks: Delivery/Time

2. On the Create Picking Waves According to Delivery Compare Times screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Reference date DATE

Time slot grp WRA1

Time slot blank

Display waves before saving

x

3. Choose Execute (The planned waves are displayed. A traffic light shows whether the capacity restrictions have been observed or not.)

4. Set the cursor on one of the waves

5. Choose Choose Detail (Details of wave pick are shown, esp. capacity restrictions.)

6. Choose Continue (in the dialog box)

7. Expand all waves, The assigned outbound deliveries are displayed

8. Place the cursor on the delivery line, Outbound deliveries that exceed the capacity of the wave are highlighted in red.

9. Choose Detail, Details of the outbound delivery are displayed

10. Choose Continue in the dialog box. Details of the outbound delivery are displayed

If the deliveries have been created exactly as described, there will be two outbound deliveries with a total of 6 items in the first wave pick ($1), and in the second wave ($2) there will be one outbound delivery with 3 items.

One of the outbound deliveries in '$1' exceeds the set restriction of a maximum of 5 delivery items. In the next step this is moved into the second wave (max. 7 items). It makes sense if the delivery that is moved is the one with the latest picking time.

© SAP AG Page 57 of 74

Page 58: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Select one delivery in the first wave ($1)(Mouse click on outbound delivery number), line turns yellow

Choose target wave pick, Outbound delivery is moved (symbol for this is a green cross in a circle). After this the traffic lights for both waves should be green. (Click on the header button ‘$x’ or place cursor to the right of the line and press [MOVE SELECTED DELIVERIES IN WAVES])

Choose Save, (NOTE: not [SAVE LAYOUT])

The message “Picking waves saved as groups... - ….”appears, Note group numbers.

Only wave picks that do not exceed their capacity (green light) are saved. The created wave picks are given a reference number that is used to process the group of deliveries at the same time in the next step.

In this example the number of delivery items for each wave pick has been restricted. It is, however, also possible to restrict, for example, the volume or the weight of all outbound deliveries. Instead of moving the outbound delivery you would be able to call it up and change it, for example, by canceling corresponding items or by changing the time for the whole outbound delivery.

7.4.2.2 Alternative 2: Create Wave Picks ManuallyIn the next step a wave pick is created manually using the Outbound Delivery Monitor.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Wave Picks Create Via Outbound Delivery Monitor

Transaction Code VL06P

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Inbound deliveries for putaway

2. On the Outbound Deliveries for Picking screen, make the following entries:

Field name Description User action and values

Comment

Shipping Point / Receiving Pt

VS01

Picking Date Delivery Date

3. Choose Execute

4. Select deliveries from 7.4.1

5. From menu Subsequent functions, choose Group, choose Wave pick.

6. On the Create Picking Wave screen, make the following entries:

Field name Description User action and values

Comment

Description <Description>, for example ‘Day’s workload

© SAP AG Page 58 of 74

Page 59: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

<Today’s date>'

Warehouse number PC1

7. Choose Continue

8. The message “Group 2000... with reference to WM saved “ appears, make a note of number.

7.4.3 Create Transfer Orders in Collective ProcessingCollective processing allows you to bundle together several outbound deliveries for transfer order processing and goods issue. Alternatively you can use the Wave Pick Monitor for subsequent processing (see 9.3).

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Create Transfer Order Collective Processing

Transaction Code LT42

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Create TOs by Mult.Processing

2. On the Create TOs by Mult. Processing: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Group blank

Foreground/ Background

Background

3. Choose START MULTIPLE PROC (Available groups are displayed.)

4. Mark line(s)

5. Choose EXECUTE MULT. PROC.

6. The message “… Transfer orders created.” Appears.

7. Mark line(s)

8. Choose RELEASE/PRINT

9. The message “You are exiting the list. Exit processing anyway?” appears.

10. Choose Yes.

If errors occur when you are creating the transfer orders, this is usually because too little stock is available in the picking storage area. According to the stock situation, carry out the goods receipt process and/or the replenishment process for the article you are using.

© SAP AG Page 59 of 74

Page 60: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

7.4.4 Confirm Transfer Orders in Collective ProcessingConfirmation can also be carried out in collective processing. To do this all the transfer orders with differences are processed individually (as for confirmation in the foreground) and the remaining transfer orders are then confirmed in collective processing (in the background).

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm transfer order Collective Processing

Transaction Code LT25N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Confirm Transfer Order/Group

2. On the Transfer Orders for Each Group screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Group Created before

Only open TO items ‘x’

Adopt pick.quantity '1' this means the pick quantity is adopted by the delivery.

3. Choose Execute

4. Mark any item, By positioning cursor

5. Choose CONF. ITM IN FOREGR, One item is confirmed with a picking difference.

6. Make the following entries:

Field name Description User action and values

Comment

C U

Difference qty 1

7. Choose Enter

8. The message “Check the difference posting”

9. Choose CONFIRM DIFFERENCE

10. The message “Transfer order ... has been confirmed” appears.

11. Choose CONFIRM REM. ITEMS, The remaining items are confirmed without difference in collective processing.

12. The message “Transfer order … confirmed “appears.

13. Choose 2 x BACK

© SAP AG Page 60 of 74

Page 61: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

7.4.5 Subsequent Delivery Split If at the point of goods issue it is discovered, for example, that the transport capacity of a truck is exceeded, an outbound delivery may have to be divided up subsequently so that separate delivery notes and transfer papers are kept.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Loading Outbound Delivery Split

Transaction Code VLSP

Option 2: SAP NetWeaver Business Client (SAP NWBC)

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Subsequent Outbound-Delivery Split

2. On the Subsequent Outbound-Delivery Split screen, make the following entries:

Field name Description User action and values

Comment

Outbound Delivery Created before

Split Profile '0002' (Shp. Cmpltn on the load. ramp)

3. Choose Execute

4. On the Subsequent Outbound-Delivery Split screen, make the following entries:

Leading Checkbox Split Quantity Note

X For 1st item, it means it will be split off completely

2 Only part of the second item is split off

5. Choose Simulate split, and then choose Save split.

The message “2 deliveries saved; of these 1 original delivery(ies) changed”, Both outbound deliveries are displayed now and the items split off get a new delivery number.

It is worth noting that the new outbound delivery is put into the wave pick for the outbound delivery. Unfortunately the outbound delivery cannot be deleted from the wave pick. This means that the goods issue is posted for both deliveries (including the one for which there is no room in the truck). However, the outbound delivery can be taken out manually when the goods issue is posted using the Outbound Delivery Monitor.

7.4.6 Goods Issue in Collective ProcessingA group of outbound deliveries can also be processed at the same time, at the point of goods issue.

1. Access the transaction choosing one of the following navigation options:

© SAP AG Page 61 of 74

Page 62: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

SAP ECC menu Merchandise logistics C Logistics execution Outbound Process Goods Issue for Outbound Delivery Post Goods Issue Collective Processing Via Outbound Delivery Monitor

Transaction Code VL06G

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Outbound List of Dlvs for Goods Issue

2. On the Outbound Deliveries for Goods Issue screen, make the following entries:

Field name Description User action and values

Comment

Pland gds mvmnt date blank

Group Created before

3. Choose Execute, choose Select All, choose Post Goods Issue, Choose Continue (in the dialog box).

4. The message “... successful and ... incorrect goods movements” appears.

8 Warehouse Physical Inventory At a set point in time the warehouse stock is entered into the physical inventory. For this the physical stocks (actual stocks) are determined by weighing, counting and by updating the book balance.

This process involves the physical inventory of a WM-managed warehouse. The inventory count result is not included on an article basis but is rather storage bin-based. This means that it is not the stock of one article throughout the warehouse that is selected but rather the entire stock in one storage bin.

In large warehouses the amount of work involved in physical inventory is considerable and it is therefore virtually impossible to count the total stock on one designated day. For this reason this process uses a periodic inventory where physical inventory work takes place in stages throughout the entire year. This means that on days when there is not much to do in the warehouse, an inventory of certain subareas can be carried out. SAP R/3 supports the warehouse supervision with permanent inventory monitoring and, for example, conducts an overview of the inventory status of each individual storage bin.

8.1 Create a Physical Inventory Document Inventory documents in the warehouse office are stored using a selection of storage bins. A preselection is made using the selection screen. After this individual bins can be selected or removed. The document can be transferred to separate systems as an IDoc where it can be processed further.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logisticsLogistics execution Internal Whse Processes Physical Inventory In Warehouse Management Physical Inventory Document Create Continuous

© SAP AG Page 62 of 74

Page 63: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Inventory

Transaction Code LX16

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory Selection of Bins for Continuous Inv

2. On the Carry out Continuous Inventory screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Storage type R01

Storage bin blank

Only bins not yet counted

Do not set flag(only in a test case, usually you only want to count bins once during each period)

Name of counter Your user name

3. Choose Execute

4. Choose Sort By Storage Sec.

5. Choose Deselect All

6. Select some Storage bins.

7. Choose Activate

8. The message “Inventory number … activated “,Note document number

9. Choose 2*Back

8.2 Perform Physical Inventory

8.2.1 Enter Inventory Count ResultsThe inventory count results can be entered on paper, using external PDC units (separate system) or using radio frequency terminals directly in the system. In the first case, all that is required is a printout of the physical inventory document as an entry list. The results of this are then transferred directly from the lists to the system. It is possible to enter a count using radio frequency, but because of the nature of storage unit management (all SU numbers must be looked for in the bin status report and entered in the count screen) this is difficult to demonstrate.

Note the following procedure: to be able to display posted differences at least one item with difference must be counted in the next step.

8.2.1.1 Manual Entry

© SAP AG Page 63 of 74

Page 64: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logisticsLogistics execution Internal Whse Processes Physical Inventory In Warehouse Management Count Results Enter

Transaction Code LI11N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory

Enter Inventory Count

2. On the Enter Inventory Count: Initial Screen , make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Inventory record Created before

Count date Today

3. Choose Enter

4. Make the following entries:

Field name Description User action and values

Comment

For empty bins:Zero

Set flag

Or for bins with stock:Article

defaulted

Counted quantity <quantity>

5. Choose Save

Only when differences compared to book balance:

5a. The message “Difference compared to book quantity-…% “ or Book quantity is greater than 0 “ appears.

5b. Choose Enter.

6. The message “Inventory count added for inventory…”

If you have to enter a quantity that according to the book balance is not carried in the storage bin (the system does not default articles), a screen appears in which you must complete the quant information.

1. Make the following entries:

© SAP AG Page 64 of 74

Page 65: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Field name Description User action and values

Comment

Stor. Unit Type E1

Article PCS-06-ART111001 (Fashion)

PCS-06-ART141001 (Fashion)

PCS-06-ART321 (Food)

PCS-06-ART323 (Food)

PCS-06-ART431 (Hard Goods)

PCS-06-ART432 (Hard Goods)

Site VZ01

GR Date Date in the past

2. Choose Enter

3. Choose Save

4. The message “Inventory count added for inventory… “

5. Choose Back

8.2.2 Trigger Inventory RecountIf, after a stock comparison, the system determines that the differences between the book balances and the counted stock are too large, you can create corresponding difference lists that will allow you to carry out an inventory recount as often as you wish.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise Logistics Logistics Execution nternal Whse Processes Physical Inventory In Warehouse Management Count Results Recount

Transaction Code LI14

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory

Start Inventory Recount

2. On the Start Recount: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Inventory record Created before

© SAP AG Page 65 of 74

Page 66: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Deviation 5%

3. Choose Enter, physical inventory document is displayed and items with differences greater than the threshold value are flagged for recount.

4. Select or deselect items according to your requirements

5. Choose Initiatel Recount.

6. The message “Recount 01 initiated for inventory…” appears

7. Choose Exit.

8.2.3 Carry Out Inventory RecountThe results of the recount are then entered.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics RetailingMerchandise logisticsLogistics execution Internal Whse Processes Physical Inventory In Warehouse Management Count Results Enter

Transaction Code LI11N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory

Enter Inventory Count

2. On the Enter Inventory Count: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Inventory record Created before

Count date Today

3. Choose Enter

4. Make the following entries:

Field name Description User action and values

Comment

For empty bins:Zero

Set flag

Or for bins with stock:Article

defaulted

Counted quantity <quantity>

5. Choose Save

6. The message “Difference compared to book quantity - ...% “ appears, Only if deviation

7. Choose Enter, only if deviation.

© SAP AG Page 66 of 74

Page 67: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

8. The message “Inventory count added for inventory…” appears.

8.3 Processing DifferencesExisting differences are cleared for each document. Processing can be done for either an entire document or for differences for only certain items in a document.

8.3.1 Post Differences in Warehouse ManagementInitially, the differences are only cleared within warehouse management in a virtual storage type (999). Here, differences that are based on a mix-up with storage bins (for example, incorrect putaway) balance themselves out, therefore avoiding any value-based postings being made.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logisticsLogistics execution Internal Whse Processes Physical Inventory In Warehouse Management Clear Differences Warehouse Management

Transaction Code LI20

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory

Clear Inventory Differences WM

2. On the Clear Differences in VM: Initial Screen make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Inventory record Created before

Deviation 2%

Foreground/ Background

Foreground

3. Choose Display List, Physical inventory document is displayed and items with differences less than the threshold value are flagged to be cleared.

4. Select all items

5. Choose Write off

6. The message “... bins cleared” appears.

7. Choose Exit

© SAP AG Page 67 of 74

Page 68: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

8.3.2 Post Differences in Inventory ManagementDifferences cumulated in storage type 999 are cleared from inventory management and on a value basis from accounting.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logisticsLogistics execution Internal Whse Processes Physical Inventory In Warehouse Management Clear Differences Inventory Management

Transaction Code LI21

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BR_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory

Clear Inventory Differences in MM-IM

2. On the Clearing of differences in Inventory Management screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Storage type 999

3. Choose Execute

4. Choose Deselect All

5. Select storage bin, Storage bin with document number of the processed physical inventory (see 8.1)

6. Choose Write off

7. The message “... quant(s) were cleared, 0 of them with errors “ appears

8. Double click Article document number, Article document is displayed.

9. Choose 4* Back

8.4 Inventory Evaluation

8.4.1 Difference StatisticsThe difference statistics provide an overview of the inventories (continuous) carried out in the individual storage types. If necessary, the statistics can be provided at bin level, for example, by aisle.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logisticsLogistics execution Information System Warehouse Physical Inventory with Bin Inventory Management Difference Statistics per Storage Type

Transaction Code LX18

© SAP AG Page 68 of 74

Page 69: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory Statistics for Inventory Differences

2. On the Statistics for Inventory Differences screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Storage type 'A' to 'Z'

3. Choose Execute, Statistics are displayed

4. Choose 2*Exit

8.4.2 Determine Inventory StatusThe inventory status provides an overview for each storage type of the progress of the continuous inventory in the warehouse. Using this list the warehouse manager can determine the bins for which an inventory still has to be carried out and can therefore also check whether the inventory status corresponds with the planned figures.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Information System Warehouse Physical Inventory with Bin Inventory Management Inventory status

Transaction Code LX25

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing phys. Inventory Inventory Status

2. On the Inventory status screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

Storage type 'A' to 'Z'

Inventory time period defaulted

3. Choose Execute

4. Select Line ‘Inv. executed during selection period’, An overview is displayed of all the bins for this item

5. Choose 2*Exit

© SAP AG Page 69 of 74

Page 70: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

9 Appendix: Tools and Workbenches

9.1 Warehouse Activity MonitorThe Warehouse Activity Monitor is a controlling tool for those in positions of responsibility within the warehouse. Its main purpose is to provide an overview of critical warehouse processes:

non-confirmed transfer orders

open transfer requirements

open posting change notices

critical (open) deliveries

negative stocks

interface stocks (GI zone, GR zone) without movement.

The above processes are executed when the Warehouse Activity Monitor is called. If these processes are still within the permitted time period they are marked with a green traffic light symbol. However, if they are critical, in other words if the permitted time has been exceeded, a red traffic light appears. Critical processes can be processed further, directly from the display screen.

If no programs are updating in the background, the relevant items must be selected with the mouse and reevaluated using [SHIFT]+[F5].

It is advisable to use the Warehouse Activity Monitor in a separate session and to watch it while the warehouse processes are being carried out.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Merchandise logistics Logistics execution Information System Warehouse Warehouse Activity Monitor

Transaction Code LL01

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehouse Controlling Warehouse Activity Monitor

2. On the Warehouse Activity Monitor: Call up Monitor Report with Variant screen, make the following entries:

Field name Description User action and values

Comment

Warehouse number PC1

3. Choose 2*Execute

All the critical processes are now displayed in a controlling tree. The following step is an example of how to deal with open transfer orders. In theory all warehouse processes can be controlled by the Warehouse Activity Monitor.

1. Select the line ’Unconfirmed transfer orders’

2. From the menu Edit, choose Determine data again

© SAP AG Page 70 of 74

Page 71: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

3. The message “Determining data again will take up time. Continue anyway? “ appears.

4. Choose Yes

5. The message “The data for ... were determined again “ appears, After the TO has been entered the traffic light should be red but turn green once the TO has been confirmed

6. Completely expand the first line of the controlling tree.

7. Double click the lowest level, Critical TOs are displayed.

To demonstrate how the Warehouse Activity Monitor functions, you should call it before and after creating transfer orders (TO) and after confirming TOs. If necessary, further processing can be done directly from the Warehouse Activity Monitor.

9.2 Outbound Delivery MonitorThe Outbound Delivery Monitor makes it easier to have an overview of the working load expected in goods issue and provides a central overview for outbound delivery processing. By defining list variants this tool can be adapted to the needs of the user.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Lists and Logs Outbound Delivery Monitor

Transaction Code VL06O

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Shipping Outbound Delivery Monitor

2. Choose For Picking

3. On the Outbound Deliveries for Picking screen, make the following entries:

Field name Description User action and values

Comment

Shipping Point / Receiving Pt

VS01

Picking Date to Period of time

4. Choose Execute, (All outbound deliveries in the given period of time with no transfer order created for picking are listed grouped by days.)

5. Further centrally controlled processing of deliveries can also be performed from here, for example:

Mark outbound delivery(ies)

From Subsequent functions, choose Create transfer order

© SAP AG Page 71 of 74

Page 72: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

9.3 Wave Pick MonitorLike the Outbound Delivery Monitor, the Wave Pick Monitor is used to follow and control processing of wave picks centrally. To be able to use it you have to have created wave picks, as described in 7.4.2. Further processing can be carried out directly from the monitor.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Picking Wave Picks Monitor

Transaction Code VL37

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Warehousing – Outbound Wave Pick Monitor

2. On the Wave Pick Monitor screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Created on Creation date of waves

3. Choose Execute, Wave picks for this date are displayed

4. Input Expand whole he entire tree, Outbound deliveries are displayed with picking status and goods movement status.

For example, subsequent processing; creating transfer orders in collective processing

1. Select picking waves

2. From Subseq. Processing, then Choose Transfer order, The Transaction code is LT42.

9.4 Rough Workload Estimate for Goods IssueUsing the rough workload estimate you can gain a clearer overview of the time needed for procedures in the warehouse and of the weight and volume to be processed. The warehouse manager can use this tool to gain not only an idea of the working hours required for goods issues at a certain point in time, but also of the corresponding volume and weight that will be involved. By doing this they can plan for sufficient workers (for example, part-time workers) and trucks to be available or to reduce the workload for a particular day by rescheduling deliveries to other dates.

The rough workload estimate can be used for both goods receipt and goods issue. The following step looks at the rough workload estimate for goods issue. The process flow is as follows:

Create delivery Workload is entered for the day of the goods issue

Post goods issue Workload is canceled

To create outbound deliveries see 7.1 and 7.4.1, and for subsequent processing see 7.2.

© SAP AG Page 72 of 74

Page 73: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

9.4.1 Rough Workload Estimate After Creation of Outbound Deliveries

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Information System Warehouse Rough Workload Estimate General Overview

Transaction Code VLLG

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-E (Retail Warehouse Manager)

Business role menu Warehouse Management Warehouse Controlling RWE: Analyze Complete Overview

2. On the Rough Workload Estimate: Total Overview: Selection screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Day Goods issue date of outbound delivery

Exception blank

3. Choose Execute

4. Double click on a row (other than row header), Provides all key figures for a date.

5. Choose Continue

6. Double click on the row header, Navigate down the standard drill-down (key figure hierarchy).

7. Choose Exit

8. The message “ (...) Do you want to save the analysis first? “ appears

9. Choose No

The processing time for quantity in hours provides the total workload entered for one working day. This is the information of most interest to the warehouse manager, as this value is proportional to the required number of warehouse workers. They can divide this value by the working time for each shift and worker and from that they can see how many workers will be needed on a certain day in the future.

The weight of the quantity is the total of all the weights of the document items that form a workload when added together. The same applies to the volume for quantity. Both values are important for planning the transport capacity that will be required on a particular day.

The unit of measure load category is used in the rough workload estimate to calculate the workload. It separates the work by processing certain units of measure. For example, picking one box takes less time than picking a pallet that requires the use of a forklift.

© SAP AG Page 73 of 74

Page 74: 742_BPP_EN_US

SAP Best Practices 742: Warehouse and DC Management (WM): BPD

9.4.2 Rough Workload Estimate After Goods IssueAfter the goods issue of the outbound delivery has been posted the workload is canceled.

1. Access the transaction choosing one of the following navigation options:

SAP ECC menu Merchandise logistics Logistics execution Information System Warehouse Rough Workload Estimate General Overview

Transaction Code VLLG

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-E (Retail Warehouse Manager)

Business role menu Warehouse Management Warehouse Controlling RWE: Analyze Complete Overview

2. On the Rough Workload Estimate: Total Overview: Selection screen, make the following entries:

Field name Description User action and values

Comment

Warehouse Number PC1

Analysis period Day of goods issue according to outbound delivery

Exception blank

3. Choose Execute.

4. Double click on any line (except header line), Provides all key figures for a date.

5. Double click on the header line, Navigate down in the standard drilldown (key figure hierarchy).

6. Choose Exit.

7. The message “ (...) Do you want to save the analysis first? “ appears.

Choose No.

© SAP AG Page 74 of 74