Sap Wm Best Practices

Embed Size (px)

Citation preview

Warehouse and DC Management (Lean WM)SAP Best Practices for Retail (India)

SAP Best Practices

Scenario Overview 1/2Purpose and Benefits:Purpose

This scenario describes the processing of merchandise in the distribution center with inventory management done at the level of storage location Lean Warehouse Management.

Benefits

Since storage procedures depend on space limitations, organization and the type of merchandise being stored, this scenario should be seen as one example of an implementation. However, this example can be easily adjusted to fit the warehouse of SAP customer.

Key process flows covered

Goods Receipt Processing Return Deliveries Goods Issue Processing Warehouse Physical Inventory Tools and Workbenches

Scenario Overview 2/2SAP Applications Required:Required

SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows

Retail Warehouse Clerk Retail Sales Person Retail Warehouse Manager

Process Flow Diagram (1/3)Goods Receipt Processing

3.2.1 Create Purchase Order

3.2.2 Create Inbound Delivery

3.2.3 Appointment Planning (Optional)

3.3.1 Posting Rough Goods Receipt

kr e C es uoher a Wi a e R l l t

3.3.2 Entering Actual Appointment (Optional)

3.3.3 Goods Receipt with Reference to Rough Goods Receipt

er o Sli a e R t t

Process Flow Diagram (2/3) Return Deliveries (Optional)

4.2.1 Search of Article Document of the Goods Receipt

4.2.2 Create Return Delivery

4.2.3 Output of Article Document as Goods Issue Slip

kr e C es uoher a Wi a e R l l t

Process Flow Diagram (3/3)Goods Issue Processing

5.2 Create Outbound Delivery

5.3.1 Create Transfer Order as Picking Document

5.3.2 Process Picking

5.4 Post Goods Issue

5.5.2.1 Capacity-driven Automatic Generation of Wave Picks

Variant: Mass Processing of Variant: Mass Processing of Alternative 1 Alternative 1 Outbound Deliveries Outbound Deliveries

5.5.4 Confirm Transfer Orders by Multiple Processing

5.5.3 Create Transfer Orders by Multiple Processing

5.5.2 5.5.2 Create Wave Picks Create Wave Picks

5.5.1 Create Outbound Delivery with Planned Picking Time

kr e C es uoher a Wi a e R l l t

5.5.2.2 Create Wave Pick manually

Alternative Alternative 2 2

5.5.5 Subsequent Delivery Split

5.5.6 Multiple Processing of Goods Issue

Document Flow in the WarehousePO Inb. Delivery Rough GR

GOODS RECEIPT

l PUTAWAY na o TRANSFER ORDER pti oThere is no stock keeping in Lean-WM, but just recording of movements using transfer orders.

FIXED STORAGE BINOutb. Del.

GOODS ISSUE

t op

PICKING al TRANSFER ORDER ion

Inventory Management - IM vs. WM

Inventory Management on article level Fixed storage bin can be maintained in the article master (text field)

Site Storage Location

Whose number Storage type

No additional level of stock keeping below IM. Warehouse number and type are just used for the recording of stock movements using the transfer order, but no stock posting is triggered when moving merchandise at this level.

Using Lean WM

When you implement Lean WM, inventory management takes place solely at storage location level. The system does not update the stock data at storage bin level using the quants like the Warehouse-Management-System (WMS) . You use Lean WM solely for processing goods receipts and goods issues. Using Lean WM, you process the warehouse movements in basically the same way as if using the Warehouse Management System: you work with deliveries, and you create transfer orders for these deliveries. These transfer orders serve as pick lists. The use of transfer orders in Lean WM provides the following advantages:

You can reprint transfer orders at any time. You can split transfer orders and thus distribute the workload better among the staff in your warehouse. You can use mass processing functions based on the transfer order (for example wave picks).

Mass Processing of Deliveries

Delivery Delivery Delivery Delivery Delivery Delivery Delivery

Manual creation in the outbound delivery monitor using selection by:Shipping point Picking date Route, carrier ... Free selection

Automatic generation using selection by:

Picking date / time Additional filter by several criteria (e.g. route, shipping point, ship-to-party ...)

Considering capacity restrictions:Group of Outbound Deliveries or Wave PickWeight, volume Maximum items on the picking list Working time ...

Mass Processing of Deliveries

Delivery Delivery Delivery Delivery Delivery Delivery Delivery

Collective Follow-On-Processing:

Create transfer order Confirm transfer order Post goods issue

Group of Outbound Deliveries or Wave Pick

Rough Workload EstimatePlanned Goods IssueDelivery Delivery Delivery Delivery Delivery

Calculation of workload using:

Logistics Load Category Unit of Measure Whse no. / storage type Warehouse process

Estimated Workload in:

Quantity Weight Volume Execution time

Information on:

needed manpower needed transport capacity

Copyright 2009 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.