Y40_BPP_EN_DE

SAP EWM 7.01 November 2011 English

Cycle Counting (Y40) Business Process Documentation

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Cycle Counting (Y40): BPD

Copyright © Copyright 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Icons Icon

Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice

Typographic Conventions Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushs 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 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.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

F2)

or the

© SAP AG Page 3 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Content Purpose .............................................................................................................................................. 5 Prerequisites........................................................................................................................................ 5 Master Data and Organizational Data.............................................................................................. 5 Business Conditions ........................................................................................................................ 6 Preliminary Steps............................................................................................................................. 7 Creating User Settings for the Transaction of Difference Analyzer...............................................7 Determining and Setting Prices from SAP ERP............................................................................7 Assigning Users to Tolerance Groups for the Difference Analyzer...............................................8 Assigning Users to Tolerance Groups for Recounting/Clearing....................................................8 Process Overview Table...................................................................................................................... 9 Process Steps.................................................................................................................................... 12 Variant 1: Paper Based Cycle Count Inventory..............................................................................12 Checking the Periodic Physical Inventory Progress ...................................................................12 Creating PI documents............................................................................................................... 13 Printing PI Documents (Paper-Driven PI Only)...........................................................................13 Transferring Count Results from the PI Count Document to the System (Paper-Driven PI Only) ................................................................................................................................................... 14 Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents).......................................................................................................... 15 Posting Differences in SAP EWM within the Warehouse Management Monitor.........................16 Setting the Completeness Indicator for Products, which Are Completely Counted (Background Job)............................................................................................................................................. 17 Posting the Differences to SAP ERP (Background Job).............................................................18 Reviewing Remaining (High-Value) Differences and posting them to SAP ERP within the Difference Analyzer.................................................................................................................... 18 Variant 2: Cycle Counting Using RF Based Devices......................................................................19 Checking the Periodic Physical Inventory Progress ...................................................................19 Creating PI documents............................................................................................................... 20 Entering Count Results Using RF Devices (RF-Driven PI Only).................................................20 Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents).......................................................................................................... 21 Post differences in EWM within the Warehouse Management Monitor......................................22 Setting the Completeness Indicator for Products, which Are Completely Counted (Background Job)............................................................................................................................................. 23 Posting the Differences to SAP ERP (Background Job).............................................................24 Reviewing the Remaining (High-Value) Differences and Posting them to SAP ERP within the Difference Analyzer.................................................................................................................... 24

© SAP AG Page 4 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Cycle Counting Purpose Cycle Counting is a product-specific physical inventory (PI) procedure that you perform at regular intervals to ensure inventory accuracy within your warehouse and to meet legal requirements. These intervals depend on the cycle counting indicator that you set for all products you want to perform cycle counting. The cycle counting indicator reflects the classification of your products according to their impact on operations and finance. The classification of the products and the assignment of the indicator to the products can be done automatically with the help of an ABC analysis, for example. Within the process you create PI documents for all cycle counting relevant products, which are due to be counted. You do the counting using a mobile device or paper. By posting the PI documents you adjust the book inventory in SAP Extended Warehouse Management (EWM). By posting the differences to SAP ERP, you balance the stock accounts. Along with this process, you monitor the progress of your physical inventory within the warehouse monitor. •

If you primarily work with product-specific PI procedures, it is advisable to make use of the putaway PI and low-stock PI within your warehouse processing to reduce the effort for counting.

•

If you use the bin-specific PI procedures, you can carry out the PI for handling units (HU). For example, you can set an HU to complete, empty or missing without counting the packed products.

Prerequisites Master Data and Organizational Data Use the following master data in the process steps described in this document: Material/Vendor Master Data Master Data

Value

Master Data Details

Products Number

EWMPROD-S01

Small part, fast-moving 01

Products Number

EWMPROD-S02

Small part, fast-moving 02

Products Number

EWMPROD-S03

Small part, fast-moving 03

Products Number

EWMPROD-S04

Small part, fast-moving 04

Comments

SAP EWM-Organizational Data Master / Org. Data

Value

EWM warehouse Number

YEWM

Master / Org. Data Details

Comments

© SAP AG Page 5 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Warehouse-specific structure Org. Data

Value

Org. Data Details

Comments

Storage Type

T020

Storage type for small parts. It is divided into 2 section: 0001 –slow moving part and 0002- fast moving part: Maximum bin weight is 40 kg; Putaway Rule: Empty bin

Activity Area

PIA2

Logical area of the warehouse, which groups storage bins together with regards to specific warehouse activities

Physical Inventory Procedures: Physical Inventory procedure

Description

CC

CC Cycle Counting Physical Inventory (Product-Specific)

Cycle Count Indicators: Warehouse Number

CC Indicator

Interval of Phys. Inventories in Workdays

Buffer Time in Workdays

YEWM

A

20

0

YEWM

B

60

0

YEWM

C

120

0

Business Conditions The business process described in this Business Process Documentation is part of a larger chain of integrated business processes or scenarios. As a result, you must have completed the following processes and fulfilled the following business conditions before you can start any activities in this scenario: The following prerequisites must be implemented: •

ERP-EWM Integration Guide (Y31)

•

The process-specific warehouse structure (warehouse number, storage types, activity areas, storage sections) (Y32)

•

Master Data (Y33)

•

Resource Management (Y34)

•

Periodic Physical Inventory (Y39)

•

A fiscal year variant has been created (transaction OB29) in SAP Extended Warehouse Management (EWM) as a prerequisite for defining the PI year

•

Implementation of SAP Note 1516253

© SAP AG Page 6 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

•

Implementation of SAP Note 1550675

•

Implementation of SAP Note 1559241

Preliminary Steps Creating User Settings for the Transaction of Difference Analyzer Use In this step, you set up user settings that are necessary for the transaction of Difference Analyzer.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory

Transaction Code

/N/SCWM/DIFF_ANALYZER

2. Select Settings → Default Values, and create the following entries: Field Name

User Action and Values

Warehouse number

YEWM

Physical Inv Difference

Check (Select)

Result You have created the user settings necessary for the difference analyzer transaction.

Determining and Setting Prices from SAP ERP Use In this step, you check whether prices for all products are available in SAP EWM.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/VALUATION_SET

2. Create the following entries: Field

User Action and Values

Comment

Warehouse Number



Enter the warehouse number for which you have carried out periodic physical inventory.

3. Choose Execute. © SAP AG Page 7 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

4. Select all rows, and choose Execute.

Result Prices for all products are available in SAP EWM.

Assigning Users to Tolerance Groups for the Difference Analyzer Use In this step, you check whether prices for all products are available in SAP EWM.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Settings → Physical Inventory

Transaction Code

/N/SCWM/PI_USER_DIFF

2. Choose Change to go to the Change mode. 3. Choose New Entries. 4. Create the following entries: Field

User Action and Values

Comment

User Name



UserID of the supervisor

Tolerance Group Difference Analyzer



for example SUPERVISOR

5. Choose Save.

Result The assignment of the user to the tolerance group difference analyzer is completed.

Assigning Users to Tolerance Groups for Recounting/Clearing Use In this step, you check whether prices for all products are available in SAP EWM.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Settings → Physical Inventory

Transaction Code

/N/SCWM/PI_USER

© SAP AG Page 8 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

2. Choose Change to go to the change mode. 3. Choose New Entries. 4. Create the following entries:

Field

User Action and Values

Comment

User Name



UserID of the supervisor

Activity Area



for example PIA2

Tolerance Group Posting



for example SUPERVISOR

Tolerance Group Recounting



for example WORKER

5. Choose Save.

Result The assignment of users to tolerance groups for posting and recounting is completed.

Process Overview Table In the periodic physical inventory process, you create physical inventory (PI) documents for a selected number of storage bins or products on a regular base to spread the workload for physical inventory over the year. You perform the counting using the following two variants: 1. Variant 1: Counting using paper Process Step

Business Condition

Business Role

Transaction Code

Expected Results

Check Physical Inventory Progress

Cycle Counting Inventory

Warehouse clerk

/N/SCWM/MON

Check the Number of open objects field to calculate the number of bins to be counted at the current date

Create PI documents for the calculated number of products

–

Warehouse Clerk

/N/SCWM/PI_CC_CREATE

PI documents are created

Print PI documents within the warehouse management monitor

–

Warehouse Clerk

/N/SCWM/MON

PI count documents are printed

© SAP AG Page 9 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Process Step

Business Condition

Business Role

Transaction Code

Expected Results

Transfer Count result

Counting completed and PI papers brought to the office

Warehouse Clerk

/N/SCWM/PI_COUNT

PI document has the status Posted (POST), no differences; PI document has the status Counted (COUN), and the differences have been calculated; PI document has the status Recounted (RECO), and a new PI document has been created

Review recounted documents within warehouse management monitor

_

Warehouse Clerk

/N/SCWM/MON

PI documents have been reviewed

Post the differences in SAP EWM within the warehouse management monitor

_

Warehouse Clerk

/N/SCWM/MON

PI documents have the status Posted (POST), book quantities on the bins are adjusted, differences are posted to the difference analyzer

Set completeness indicator for products, which are counted completely

_

Background user

/N/SCWM/PI_COMPL_CHECK

Completeness indicator is set for all products, which are completely counted

Post the differences to SAP ERP

_

Background user

/N/SCWM/WM_ADJUST

All differences with a value lower than the threshold value are posted to SAP ERP

Review remaining (highvalue) differences and post them to SAP ERP within the Difference Analyzer

_

Warehouse Clerk

/N/SCWM/DIFF_ANALYZER

All differences are posted to SAP ERP

© SAP AG Page 10 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

2. Variant 2: Counting using an RF (Radio frequency) device Process Step

Business Condition

Business Role

Transaction Code

Expected Results

Check Physical Inventory Progress

Cycle Counting Inventory

warehouse clerk

/N/SCWM/MON

Check the Number of open objects field to calculate the number of bins to be counted at the current date

Selects Bins or Products and create PI documents

–

Warehouse Clerk

/N/SCWM/PI_DOC_CREATE

PI documents are created

Enter Count result using RF device

-

Counter

/N/SCWM/RFUI

PI document has the status Posted (POST), no differences; PI document has the status Counted (COUN), and differences have been calculated; PI document has the status Recounted (RECO), and a new PI document has been created

Review recounted documents within warehouse management monitor

_

Warehouse Clerk

/N/SCWM/MON

PI documents have been reviewed

Post the differences in SAP EWM within the warehouse management monitor

_

Warehouse Clerk

/N/SCWM/MON

PI documents have the status Posted (POST), book quantities on the bins are adjusted, differences are posted to the difference analyzer

Set completeness indicator for products, which are counted completely

_

Background user

Post the differences to SAP ERP

_

Background user

/N/SCWM/PI_COMPL_CHECK

/N/SCWM/WM_ADJUST

Completeness indicator is set for all products, which are counted completely All differences with value lower than the

© SAP AG Page 11 of 25

SAP Best Practices Process Step

Cycle Counting (Y40): BPD

Business Condition

Business Role

Transaction Code

Expected Results threshold value are posted to SAP ERP

Review remaining (highvalue) differences and post them to SAP ERP within the Difference Analyzer

_

Warehouse Clerk

/N/SCWM/DIFF_ANALYZER

All differences are posted to SAP ERP

Process Steps Variant 1: Paper Based Cycle Count Inventory Checking the Periodic Physical Inventory Progress Use As a part of the cycle counting inventory procedure, you can check the ongoing progress of Cycle counting through the warehouse management monitor.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring

Transaction Code

/N/SCWM/MON - Warehouse Management Monitor

2. Make the following entries, and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

3. Choose the following navigation options: Physical Inventory→ Physical Inventory Progress. 4. Choose Cycle Counting as criteria if you want to check the PI progress of cycle counting inventory 5. Choose Activity Area for the simple search, enter the (for example PIA2), and execute. 6. Select the line item appearing on the right-hand section of the warehouse monitor, and choose All Products. © SAP AG Page 12 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Result The warehouse monitor displays all the open objects for which the physical inventory is to be counted.

Creating PI documents Use PI documents are created for the selected number of bins or products.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/PI_CC_CREATE

2. Enter the count date: . 3. Select Active PI Document, and enter the warehouse number: (for example YEWM). 4. Enter the activity area: < activity area> (for example PIA2). 5. Enter the product number: < Product Number >. 6. Choose Execute (F8). 7. Select all the line items and choose Create. You can restrict the number of storage bins to be counted per PI document by entering the number of bins in the Maximum Number of Items field, for example 10.

Result PI documents are created for the objects for which the periodic physical inventory counting is to be carried out.

Printing PI Documents (Paper-Driven PI Only) Use In case of paper-driven PI, the warehouse clerk prints the PI count documents for calculating the number of bins or products, and lays them out in the office. The system automatically creates one or several warehouse orders for the PI documents.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring

© SAP AG Page 13 of 25

SAP Best Practices Transaction Code

Cycle Counting (Y40): BPD /N/SCWM/MON

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for exampleSAP

3. Choose the following navigation options Physical Inventory → Count Overview 4. Make the following entries and choose Execute: Field

User Action and Values

Comment

Activity Area

< Activity Area >

for example PIA2

Phys. Inventory Doc

< Phys. Inventory Doc >

The PI doc. Number generated in previous step

Document Year

< Document Year>

5. Select the line item appearing on the left-hand section of the warehouse monitor, and choose Total. 6. Select the line item appearing on the bottom left-hand section of the warehouse monitor, and choose More Methods. 7. Choose button More Method then Print PI Doc. from .

Result PI documents are printed and are ready to use.

Transferring Count Results from the PI Count Document to the System (Paper-Driven PI Only) Use In case of paper-driven PI, the warehouse clerk takes the PI count documents, and enters the count results into the system.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory

Transaction Code

/N/SCWM/PI_COUNT

2. Make the following entries and choose Execute: © SAP AG Page 14 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Field

User Action and Values

Phys. Inv. Doc.

< PI Doc >

Comment

3. Select the line item, and choose Switch to Form View. 4. Choose Count. 5. Make the following entries: Field

User Action and Values

Counter

< Counter Name >

for example Name of the Counter

Count date



for example Counting Date

6. Choose Enter. 7. Enter the Handling Unit in the HU field in case the HU is found in the storage bin. 8. In the Qty in Alt. Un field, enter the count results (quantity and unit of measure), and choose Enter. 9. Select the line item, and choose Save. In case the bin is empty, you can choose Check in the SBin Empty field on the Count Items screen.

Result •

PI document has the status Posted (POST) in case of no differences.

•

PI document has the status Counted (COUN), and differences have been calculated.

•

PI document has the status Recounted (RECO), and a new PI document has been created.

Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents) Use After the input of the count results, the system calculates the differences on the basis of count results and book inventory. If a difference exceeds the predefined, counter-dependent thresholds for recounting, the system automatically creates a recount document. The warehouse clerk monitors the recounted PI documents and retriggers the count process if necessary.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring

Transaction Code

/N/SCWM/MON

2. Make the following entries and choose Execute:

© SAP AG Page 15 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

3. Choose the following navigation options: Physical Inventory → Physical Inventory Documents. 4. Make the following entries and choose Execute: Field

User Action and Values

Comment

Activity Area

< Activity Area >

for example PIA2

Physical Inventory Status

RECO

Recounted

Creation Date

< current date >

The date on which the recounted document has been created.

5. For the selected PI documents, note the referenced PI document number in the DOC_NUMBER_REF field. 6. With the help of the new PI document number, you can enter new counting results with the same procedure mentioned in Entering Count Results Using RF Devices in case of RF-driven PI counting, and with the procedure mentioned in Transferring Count Results from the PI Count Document to the System in case of paper-driven PI.

Posting Differences in SAP EWM within the Warehouse Management Monitor Use At the end of the count process, the warehouse clerk posts all counted PI documents. The system checks in each case if a difference exceeds the thresholds for posting assigned to the warehouse clerk. If so, the warehouse clerk is not allowed to post the corresponding PI document. It must be done by the supervisor. During the posting of the PI documents, the system adapts the book inventory on the bins and posts the differences to the difference analyzer. Additionally, the system checks if a product is counted completely. If so, the system sets the completeness indicator.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring

Transaction Code

/N/SCWM/MON

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

3. Choose the following navigation options: Physical Inventory → Physical Inventory Documents. © SAP AG Page 16 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

4. Make the following entries and choose Execute: Field

User Action and Values

Comment

Activity Area

< Activity Area >

for example PIA2

Physical Inventory Status

COUN

Creation Date

< current date >

The date on which the recounted document has been created.

5. After the selection, select all lines and choose “More Methods”Post PI Doc.

Result PI documents have the status Posted (POST), book quantities on the bins are adjusted, differences are posted to the difference analyzer.

Setting the Completeness Indicator for Products, which Are Completely Counted (Background Job) Use With the help of a background job, the system checks if a product is counted completely. If so, the system sets the completeness indicator.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/PI_COMPL_CHECK

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Activity Area

< Activity Area>

for example PIA2

Product



for example EWMPROD-S01 to EWMPROD-S04

3. Select Current Fiscal Year, and choose Execute (F11). 4. Check whether the completeness indicator is set for all products, which are completely counted.

Result The completeness indicator is set for all products, which are completely counted.

© SAP AG Page 17 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Posting the Differences to SAP ERP (Background Job) Use With the help of a background job, most of the differences are automatically posted to SAP ERP by the background user.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/WM_ADJUST

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Difference category

Physical Inventory Difference

Settings

Post on Item Level

3. Choose Save.

Result Differences are automatically posted to SAP ERP.

Reviewing Remaining (High-Value) Differences and posting them to SAP ERP within the Difference Analyzer Use With the help of a background job, most of the differences are automatically posted to SAP ERP. If the value of some differences violates the tolerances assigned to the background user, the warehouse clerk or the supervisor has to review these differences in the difference analyzer, for example, they analyze the movements of the product and may decide that a new PI is necessary. After the review, they post these differences to SAP ERP manually.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory

Transaction Code

/N/SCWM/DIFF_ANALYZER

2. Select the Find category for the difference analyzer 3. Make the following entries and choose Execute: Field

User Action and Values

Comment

Product

< Product Number >

for example EWMPROD-S01

© SAP AG Page 18 of 25

SAP Best Practices Field

Cycle Counting (Y40): BPD User Action and Values

Comment

4. Select the line item, and choose Post.

Result All differences are posted to SAP ERP.

Variant 2: Cycle Counting Using RF Based Devices Checking the Periodic Physical Inventory Progress Use As a part of the cycle counting inventory procedure, you can check the ongoing progress of Cycle counting through the warehouse management monitor .

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring

Transaction Code

/N/SCWM/MON

2. Make the following entries, and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

3. Choose the following navigation options: Physical Inventory→ Physical Inventory Progress. 4. Choose Cycle Counting as criteria if you want to check the progress of cycle counting. 5. Choose Activity Area for the simple search, enter the (for example PIA2) and execute. 6. Select the line item on the left-hand section of the warehouse monitor, and choose All Products.

Result The warehouse monitor displays all the open objects, for which physical inventory is to be counted.

© SAP AG Page 19 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Creating PI documents Use PI documents are created for the selected number of bins or products.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/PI_CC_CREATE

2. Enter the Count date: . 3. Select Active PI Document, and enter the warehouse number: (for example YEWM). 4. Enter the activity area < activity area > (for example PIA2). 5. Enter the product number: < Product Number >. 6. Choose Execute (F8). 7. Select all the line items, and choose Create. You can restrict the number of storage bins to be counted per PI document by entering the number of bins in the Maximum Number of Items field, for example 10.

Result PI documents are created for the objects for which the periodic physical inventory counting is to be carried out.

Entering Count Results Using RF Devices (RF-Driven PI Only) Use In case of RF-driven PI, the counter takes a mobile device, and logs on as a resource, which is assigned to the PI queue. The system guides the counter to the first bin. Standing in front of it, the counter verifies the bin, the HU, and the product proposed by the system. Then he or she counts the product, and enters the quantity. If he or she finds a product not proposed by the system (in case of the bin-specific PI procedure), he or she records it, and enters the counted quantity. When the counter finished the counting of this bin, the system guides him or her to the next bin.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Execution → Log On to RF Environment

© SAP AG Page 20 of 25

SAP Best Practices Transaction Code

Cycle Counting (Y40): BPD /N/SCWM/RFUI

2. Make the following entries and choose Enter: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Resource

< Monitor >

for example CNT1

DefPresDvc

< DefPresDvc >

for example PRES

3. Choose the following navigation options: 05 Internal Processes → 01 Inventory Counting → 01 Inventory Counting Guided. 4. Copy the bin proposed by the system next to the bin description, and choose Enter. In case the bin is empty, you can choose F1 BnEmp. 5. Enter the handling unit (HU) found in the storage bin during the counting of the bin, and choose Enter. In case the HU is empty, you can choose F1 HUEmp, and choose Save after step 5. In case the HU is complete along with the product associated with it, you can choose F3 HUCmp, and choose Save after step 5. 6. Choose Enter. 7. Copy the product description proposed by the system next to the Product Description, and choose Enter. 8. Enter the count result for the product next to the Product Description. 9.

Choose Save (F11).

Result Inventory counts are entered with the help of RF devices. The PI document has the status Posted (POST) in case of no differences. The PI document has the status Counted (COUN), and differences have been calculated. The PI document has the status Recounted (RECO), and a new PI document has been created.

Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents) Use After the input of the count results, the system calculates the differences on the basis of count results and book inventory. If a difference exceeds the predefined, counter-dependent thresholds for recounting, the system automatically creates a recount document. The warehouse clerk monitors the recounted PI documents and retriggers the count process if necessary.

© SAP AG Page 21 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring

Transaction Code

/N/SCWM/MON

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

3. Choose the following navigation options Physical Inventory → Physical Inventory Documents 4. Make the following entries and choose Execute: Field

User Action and Values

Comment

Activity Area

< Activity Area >

for example PIA2

Physical Inventory Status

RECO

Recounted

Creation Date

< current date >

The date on which recounted doc has been crated.

5. For the selected PI documents, note the referenced PI document number in the DOC_NUMBER_REF field. 6. With the help of the new PI document number, you can enter new counting results with the same procedure mentioned in Entering Count Results Using RF Devices in case of RF-driven PI counting, and with the procedure mentioned in Transferring Count Results from the PI Count Document to the System in case of paper-driven PI.

Post differences in EWM within the Warehouse Management Monitor Use At the end of the count process, the warehouse clerk posts all counted PI documents. The system checks in each case if a difference exceeds the thresholds for posting assigned to the warehouse clerk. If so, the warehouse clerk is not allowed to post the corresponding PI document. It must be done by the supervisor. During the posting of the PI documents, the system adapts the book inventory on the bins, and posts the differences to the difference analyzer. Additionally, the system checks if a product is completely counted. If so, the system sets the completeness indicator.

Procedure 1. Access the transaction using the following navigation options:

© SAP AG Page 22 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

SAP Menu

Extended Warehouse Management → Monitoring

Transaction Code

/N/SCWM/MON

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

3. Choose the following navigation options: Physical Inventory → Physical Inventory Documents. 4. Make the following entries and choose Execute: Field

User Action and Values

Comment

Activity Area

< Activity Area >

for example PIA2

Physical Inventory Status

COUN

Creation Date

< current date >

The date on which the recounted document has been created.

5. After the selection, select all lines and choose Post PI Doc.

Result PI documents have the status Posted (POST), book quantities on the bins are adjusted, differences are posted to the difference analyzer.

Setting the Completeness Indicator for Products, which Are Completely Counted (Background Job) Use With the help of a background job, the system checks if a product is completely counted. If so, the system sets the completeness indicator.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/PI_COMPL_CHECK

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Activity Area

< Activity Area >

for example PIA2

Product



for example EWMPROD-S01 to

© SAP AG Page 23 of 25

SAP Best Practices Field

Cycle Counting (Y40): BPD User Action and Values

Comment EWMPROD-S04

3. Select Current Fiscal Year, and choose Execute (F11). 4. Check whether the completeness indicator is set for all products, which are completely counted.

Result The completeness indicator is set for all products, which are completely counted.

Posting the Differences to SAP ERP (Background Job) Use With the help of a background job, most of the differences are automatically posted to SAP ERP by the background user.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/WM_ADJUST

2. Make the following entries and choose Execute: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Difference category

Physical Inventory Difference

Settings

Post on Item Level

3. Choose Save.

Result Differences are automatically posted to SAP ERP.

Reviewing the Remaining (High-Value) Differences and Posting them to SAP ERP within the Difference Analyzer Use With the help of a background job, most of the differences are automatically posted to SAP ERP. If the value of differences violates the tolerances assigned to the background user, the warehouse © SAP AG Page 24 of 25

SAP Best Practices

Cycle Counting (Y40): BPD

clerk or the supervisor has to review these differences in the difference analyzer, for example they analyze the movements of the product, and may decide that a new PI is necessary. After the review, they post these differences to ERP manually.

Procedure 1. Access the transaction using the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory

Transaction Code

/N/SCWM/DIFF_ANALYZER

2. Select the Find category for the difference analyzer. 3. Make the following entries and choose Execute: Field

User Action and Values

Comment

Product

< Product Number >

for example EWMPROD-S01

4. Select the line item, and choose Post.

Result All differences are posted to SAP ERP.

© SAP AG Page 25 of 25