Y39 Scen Overview en De

8/12/2019 Y39 Scen Overview en De

http://slidepdf.com/reader/full/y39-scen-overview-en-de 1/15

Periodic Physical Inventory

SAP Extended Warehouse Management (SAP EWM) Rapid-Deployment Solution V2



© 2011 SAP AG. All rights reserved. 2

Physical Activity System Activity

Step 3 – exceptional caseCreate recount documentsand carry out the recounting(EWM)

Step 1Create PI documentsand WOs (EWM)

Step 2 Count the bins or products(EWM)

A counter logs on as a resource(RF only )

The counter counts the bin or product

A warehouse clerk checks the recountdocument creation

Step 4 Post the PI documents (EWM)

Step 5 Set completeness (EWM)

Periodic Physical Inventory

The system creates PI documents ( variantB)

The warehouse clerk prints the WOs( paper only )

The system assigns the WOs to a queue(RF only )

The system proposes the next product orbin to be counted

(RF only )

A warehouse clerk ( paper only ) or thecounter ( RF only ) enters the count results

The system creates recount documents

The counter carries out the recounting(repeating step 2 )

The system posts the PI documentsdepending on tolerances

The supervisor posts the remaining PIdocuments

The system sets completeness

Step 6 Post the differences (EWM)

The system posts the differencesdepending on tolerances

The supervisor reviews and posts theremaining differences

A warehouse clerk checks the PI progressand creates PI documents ( variant A )

The system creates WOs




Purpose

You use this warehouse process of periodic physical inventory (PI) tocontrol the stock of your warehouse and to meet legal requirements.Within this process you create PI documents for a selected number ofstorage bins or products on a regular basis to spread the workloadfor PI over the year. You execute the counting using a mobile deviceor paper. By posting the PI documents you adjust the book inventoryin SAP Extended Warehouse Management (SAP EWM). By posting the

differences to SAP Enterprise Resource Planning (SAP ERP) youbalance the stock accounts.

You can monitor the progress of your PI by using the warehousemanagement monitor.




Prerequisites

• You have integrated SAP ERP with SAP EWM.

• You have configured the warehouse structure and master data.

• You have configured your systems for this process.




Process StepCreate PI documents and WOs (EWM)

Variant A : In SAP EWM, the warehouse clerk monitors the PIprogress of all bins or products in the warehouse andcalculates how many bins or products have to be counted inthe given period. He then creates PI documents for thecalculated number of bins or products.

Variant B : With help of a background job the system createsPI documents automatically for a number of bins or productsto be counted. In regular intervals (for example, monthly) thewarehouse clerk monitors the PI progress and verifies thenumber of bins or products still to be counted to adjust thebackground job accordingly if necessary. The systemautomatically creates one or several warehouse orders (WOs)with a predefined maximum number of PI document items.Within a WO, the bins to be counted are sorted according toan optimized path in the warehouse. In case of an RF-basedPI, the system sends the WOs to a PI-specific RF queue. Incase of paper-based PI, the warehouse clerk prints the PIdocuments and lays them out in the office.


http://slidepdf.com/reader/full/y39-scen-overview-en-de 7/15© 2011 SAP AG. All rights reserved. 7

Process StepCount the bins or products (EWM) – Part 2

A warehouse clerk takes the printouts and enters the name ofthe counter, the count date, and the count results into thesystem.

If the counter finds a product not proposed by the system (incase of a bin-specific PI process), he brings it physically(without creating any WOs) to the clarification zone. In theclarification zone, an inventory specialist records the productby an ad hoc PI document and moves it to an appropriate binwith help of an ad hoc WO.

Recommendation:

If you use paper for PI: Moving products from or to the binduring the counting may lead to unexpected results.Therefore we recommend forbidding movements during the PIprocess by selecting the Phys . Invento ry Bloc king Indica tor checkbox when you create PI documents in step 1. Otherwise,it might happen that the system triggers a recount more often

than expected.



Process StepCount the bins or products (EWM) – Part 3

When you save the count results, the system calculates thedifferences on the basis of count results and the bookinventory.



Process StepCreate recount documents and carry out the recounting (EWM)

If a difference exceeds the predefined, counter-dependentthresholds for recounting, the system automatically creates arecount document. A warehouse clerk monitors the creationof recount documents and asks a counter to recount the binsor products.



Process StepPost the PI documents (EWM)

When you save the count results, the system posts the PIdocuments automatically if the differences do not exceed thethresholds for posting assigned to the counter (using RF) orassigned to the warehouse clerk (using paper). The systemadapts the book inventory in the bins and posts thedifferences to the Difference Analyzer.

At the end of the count process the supervisor checks theremaining PI documents that are not posted yet due toexceeded thresholds, and posts them manually.



Process StepSet completeness (EWM)

This step is necessary only in case of product-specific PI.

With help of a background job, the system checks if a productis completely counted. If so, the system sets its status tocomplete.

Recommendation:

We recommend running this background job once a day.



Process StepPost the differences (EWM)

To adjust the stock accounts and the Available-to-Promise(ATP) quantity in a timely manner, the system posts alldifferences up to a certain value to SAP ERP automaticallywith help of a background job. The value threshold is definedin the tolerance group assigned to the background user. Thesupervisor reviews the remaining, bigger differences in theDifference Analyzer. He blocks the differences for posting anddefines follow-on actions, such as the analysis of themovements or even the creation of a new PI document for theproduct. After review and clarification he posts all differencesto SAP ERP manually.



Process Monitoring – Part 1

ProcessStep

Objects To Be Monitored Activities

1 and 5 PI progress On the SAP Easy Access screen, chooseExtended Warehouse Management ->Monitoring -> Warehouse ManagementMonitor -> Physical Inventory -> PhysicalInventory Documents .

Select Physical Inventory Documents byactivity area.

1 Warehouse orders and PI documents tobe counted

2 Counted PI documents3 Recounted PI documents … 4 Counted PI documents to be posted6 Differences in the Difference Analyzer On the SAP Easy Access screen, choose

Extended Warehouse Management ->Physical Inventory -> Difference Analyzer



More Information

For more information, see SAP Library for SAPExtended Warehouse Management on the SAP HelpPortal at http://help.sap.com .

http://help.sap.com/

http://help.sap.com/



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

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

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 registeredtrademarks 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 orregistered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.

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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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 fortechnology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, and other SAP products and services mentioned herein as well as t heirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase, Inc. Sybase is an SAP company.

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

The information in this document is proprietary to SAP. No part of this document may bereproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or anyother 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 anyparticular course of business, product strategy, and/or development. Please note that thisdocument 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 notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained 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 ofmerchantability, 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 nocontrol over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third -party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.

Y39 Scen Overview en De

Documents

Transcript of Y39 Scen Overview en De