Scrapping due to Best-Before Date/Shelf-Life Expiration Date
SAP Extended Warehouse Management (SAP EWM) Rapid-Deployment Solution V2
Scrapping due to BBD/SLED
Physical Activity
Step 1
Create posting changes
and WOs (EWM)
System Activity
A warehouse clerk select quants
with old BBD/SLED and creates
posting changes
The system creates WOs to the
scrapping zone
The system prints the WOs (paper
only) or assigns the WOs to
queues (RF only)
Step 2
Move the goods to the
scrapping zone (EWM)
A warehouse worker logs on as a
resource (RF only)
The system proposes the next WO
in the queue to be processed
(RF only)
The warehouse worker picks the
goods and moves them to the
scrapping zone
A warehouse clerk (paper only) or
the warehouse worker (RF only)
confirms the WO
Step 3
Empty the scrapping zone
(EWM)
Step 4
A truck arrives and takes the
scrap away
©
2011 SAP AG. All rights reserved.
The system empties the scrapping
zone regularly by a background
job
A truck arrives and picks up the
scrapping container
2
Purpose
In this process you scrap regularly stock with expired best-before
date or shelf-life expiration date. The scrapping process is triggered
in SAP EWM. You change the stock type of the expired stock so that it
is not available for sale anymore. You use a warehouse order to move
the stock to a scrap container in the scrap zone. The warehouse order
is executed using a mobile device or a printed document. A
background job runs regularly to empty the scrap zone in SAP EWM
and update the inventory balance in SAP ERP. After the job run, the
stock in the scrap container is not managed in the system anymore.
When a truck arrives to fetch the scrap container, no step is
necessary in the system.
You can also use this process to scrap stock damaged stock
detected by accident in the warehouse.
©
2011 SAP AG. All rights reserved.
3
Prerequisites
•You
have integrated SAP EWM with SAP ERP.
•You
have configured the warehouse structure and master data.
•You
have configured your systems for this process.
•For
scrapping triggered by expired BBD/SLED, you must have stock
with expired best-before date or shelf life expiration date in your
warehouse.
©
2011 SAP AG. All rights reserved.
4
Process Step
Create posting changes and warehouse orders (SAP EWM)
Variant A: In case of scrapping due to BBD/SLED, the
warehouse clerk selects expired stock in the SAP EWM
monitor first, and navigates then to the posting change
transaction to create a posting change document . With the
creation of the posting change documents, the system
changes the stock from unrestricted-use stock to scrapping
stock so that it is not available for sale anymore, and creates
warehouse tasks (WT) and warehouse orders (WO) to move
the stock to the scrapping zone at the same time. In case of
RF based scrapping, the system sends the WOs to an RF
queue. In case of paper-based scrapping, the system prints
the WOs automatically.
Variant B: A warehouse clerk gets the information about
damaged stock in a certain bin from his or her coworkers or
from a picking supervisor. He or she selects the stock for the
products on that bin and creates posting change documents.
©
2011 SAP AG. All rights reserved.
5
Process Step
Move the goods to the scrapping zone (SAP EWM) – Part 1
In case of RF based scrapping, a warehouse worker takes a
vehicle and logs on as a resource that is assigned to the
scrapping queue. The system guides the warehouse worker to
the source bin of the first WT. The warehouse worker picks
the requested quantity of the product and puts the product
onto his or her vehicle. He or she scans the source bin for
verification purposes and enters the quantity. After all fields
on the source screen have been verified, the warehouse
worker is prompted to bring the picked goods to the
scrapping zone. When he or she arrives at the scrapping
zone, he or she scans the destination bin for verification
purposes again and confirms the scrapping WT in the system.
If the warehouse worker finds a quantity smaller than the
requested quantity in the storage bin, he or she enters an
exception code in his or her mobile device, and records the
quantity difference in the WT by entering the quantity he or
she has actually picked. With the confirmation, the system
reduces the scrapping stock on the current bin by the
difference quantity.
©
2011 SAP AG. All rights reserved.
6
Process Step
Move the goods to the scrapping zone (SAP EWM) – Part 2
After the confirmation of the WT, the warehouse worker
proceeds with the execution of the next WT displayed on his
or her mobile device.
In case of paper based scrapping, a warehouse worker goes
to the internal office and picks up the printouts of the WOs.
He or she goes to the bin where the product is to be picked.
The warehouse worker moves the product to the scrapping
zone. If the warehouse worker finds a quantity smaller than
the requested quantity in the storage bin, he or she makes
annotations on the printout. After the physical move of the
product, the warehouse worker brings the printout of the WOs
with the annotations to the internal office. A warehouse clerk
confirms the WOs in the system.
©
2011 SAP AG. All rights reserved.
7
Process Step
Empty the scrapping zone (SAP EWM)
A background job regularly runs to empty the scrapping zone
in the system. The system communicates the goods issue to
SAP ERP.
As an alternative, it is also possible to manage the stock in
the scrapping zone in the system until the scrapping
container is picked up. In this case, you do not plan a regular
background job to empty the scrapping zone. You empty the
scrapping zone manually in the next step.
©
2011 SAP AG. All rights reserved.
8
Process Step
A truck arrives and takes the scrap away
A truck arrives and picks up the scrapping container.
©
2011 SAP AG. All rights reserved.
9
[DR1]is
there a word missing, or what's the meaning of "by" here?
Process Monitoring
Process
Step
1
Objects To Be Monitored
Activities
Stock with expired BBD /
SLED
On the SAP Easy Access screen, choose Extended
Warehouse Management → Monitoring → Warehouse
Management Monitor → Stock and Bin → BBD/SLED
Overview.
2
Open WTs for scrapping
All
Scrap stock in the warehouse
or on the scrapping zone
Select expired stock.
On the SAP Easy Access screen, choose Extended
Warehouse Management → Monitoring → Warehouse
Management Monitor → Documents → Warehouse Task.
Select the open WT by warehouse process type .
On the SAP Easy Access screen, choose Extended
Warehouse Management → Monitoring → Warehouse
Management Monitor → Stock and Bin → Physical Stock.
For selecting the open WTs for replenishment in the selection
screen /SCWM/SAPLWO_TO_MON use warehouse process
type P420 in field Whse Proc. Type.
©
2011 SAP AG. All rights reserved.
10
More Information
For more information, see SAP Library for SAP
Extended Warehouse Management on the SAP Help
Portal at http://help.sap.com.
©
2011 SAP AG. All rights reserved.
11
© 2011 SAP AG. All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
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 Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase 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.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any
other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP® product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind,
either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct,
special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any
warranty whatsoever relating to third-party Web pages.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, 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.
©
2011 SAP AG. All rights reserved.
12