Description
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 Screen output. Keys on the keyboard. table names. Cross-references to other documentation. © SAP AG Page 3 of 25 . This includes file and directory names and their paths. source code. Names of elements in the system. These are words or characters that you enter in the system exactly as they appear in the documentation.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 Example text Description Words or characters that appear on the screen. for example. for example. transaction codes. messages. function keys (such as ENTER key. paths and options. screen titles. Emphasized words or phrases in body text. F2) Example text EXAMPLE TEXT Example text EXAMPLE TEXT or the Example text <Example text> Exact user entry. when surrounded by body text. names of variables and parameters as well as names of installation. Pointed brackets indicate that you replace these words and characters with appropriate entries. titles of graphics and tables. program names. Variable user entry. pushs as well as menu names. These include report names. These include field names. upgrade and database tools. SELECT and INCLUDE. and individual key words of a programming language. which Are Completely Counted (Background Job)...................................................................................... 13 Printing PI Documents (Paper-Driven PI Only).................................................................................................................................... 12 Variant 1: Paper Based Cycle Count Inventory................................................................................................................................. 14 Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents).......................................................................................................................................................................... 21 Post differences in EWM within the Warehouse Management Monitor..... 5 Prerequisites.....................................................................7 Assigning Users to Tolerance Groups for the Difference Analyzer......................................................................................................... 18 Variant 2: Cycle Counting Using RF Based Devices............................... 15 Posting Differences in SAP EWM within the Warehouse Management Monitor...........................22 Setting the Completeness Indicator for Products........................................................................19 Creating PI documents.........................................................................................................................................................................................................................8 Assigning Users to Tolerance Groups for Recounting/Clearing....................................8 Process Overview Table.......................................................................................................................................................................................................19 Checking the Periodic Physical Inventory Progress .............................................................. 7 Creating User Settings for the Transaction of Difference Analyzer......................... 23 Posting the Differences to SAP ERP (Background Job)....................................................................................................................................................................................................... 5 Business Conditions ..................... 5 Master Data and Organizational Data..............................................18 Reviewing Remaining (High-Value) Differences and posting them to SAP ERP within the Difference Analyzer................. 9 Process Steps.................................................................................................................16 Setting the Completeness Indicator for Products...........................20 Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents)........................................................................................... which Are Completely Counted (Background Job)........................................................................................................................................................................................................7 Determining and Setting Prices from SAP ERP.. 17 Posting the Differences to SAP ERP (Background Job)............................................................................................................................................... 6 Preliminary Steps...............12 Checking the Periodic Physical Inventory Progress .............................................................................................................................................................................................................................................. 20 Entering Count Results Using RF Devices (RF-Driven PI Only)............................................................................................................................................... 24 © SAP AG Page 4 of 25 ....................13 Transferring Count Results from the PI Count Document to the System (Paper-Driven PI Only) ...............................SAP Best Practices Cycle Counting (Y40): BPD Content Purpose ..................................................................24 Reviewing the Remaining (High-Value) Differences and Posting them to SAP ERP within the Difference Analyzer..........................12 Creating PI documents............... If you use the bin-specific PI procedures. you monitor the progress of your physical inventory within the warehouse monitor. fast-moving 04 Comments SAP EWM-Organizational Data Master / Org. Along with this process. you can carry out the PI for handling units (HU). fast-moving 01 Small part. The cycle counting indicator reflects the classification of your products according to their impact on operations and finance. For example. • 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 Products Number Products Number Products Number Products Number Value EWMPROD-S01 EWMPROD-S02 EWMPROD-S03 EWMPROD-S04 Master Data Details Small part. empty or missing without counting the packed products. You do the counting using a mobile device or paper. Data EWM warehouse Number Value YEWM Master / Org. Within the process you create PI documents for all cycle counting relevant products. which are due to be counted. • If you primarily work with product-specific PI procedures. 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. fast-moving 02 Small part. for example.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. By posting the differences to SAP ERP. it is advisable to make use of the putaway PI and low-stock PI within your warehouse processing to reduce the effort for counting. you balance the stock accounts. These intervals depend on the cycle counting indicator that you set for all products you want to perform cycle counting. Data Details Comments © SAP AG Page 5 of 25 . By posting the PI documents you adjust the book inventory in SAP Extended Warehouse Management (EWM). you can set an HU to complete. fast-moving 03 Small part. storage types.fast moving part: Maximum bin weight is 40 kg. Data Details Storage type for small parts. Putaway Rule: Empty bin Logical area of the warehouse.SAP Best Practices Cycle Counting (Y40): BPD Warehouse-specific structure Org. Inventories in Workdays 20 60 120 Buffer Time in Workdays 0 0 0 Description CC Cycle Counting Physical Inventory (Product-Specific) Business Conditions The business process described in this Business Process Documentation is part of a larger chain of integrated business processes or scenarios. 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 . As a result. Data Storage Type Value T020 Org. activity areas. It is divided into 2 section: 0001 –slow moving part and 0002. which groups storage bins together with regards to specific warehouse activities Comments Activity Area PIA2 Physical Inventory Procedures: Physical Inventory procedure CC Cycle Count Indicators: Warehouse Number YEWM YEWM YEWM CC Indicator A B C Interval of Phys. 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. and create the following entries: Field Name Warehouse number Physical Inv Difference User Action and Values YEWM 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.SAP Best Practices • • Implementation of SAP Note 1550675 Implementation of SAP Note 1559241 Cycle Counting (Y40): BPD 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. Select Settings → Default Values. Choose Execute. Create the following entries: Field Warehouse Number 3. Procedure 1. you check whether prices for all products are available in SAP EWM. . Procedure 1. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory /N/SCWM/DIFF_ANALYZER 2. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/VALUATION_SET 2. © SAP AG Page 7 of 25 User Action and Values <Warehouse Number> Comment Enter the warehouse number for which you have carried out periodic physical inventory. 3. Assigning Users to Tolerance Groups for the Difference Analyzer Use In this step. User Action and Values <UserID> <Tol group for Diff Analyser> Comment UserID of the supervisor for example SUPERVISOR Result The assignment of the user to the tolerance group difference analyzer is completed. you check whether prices for all products are available in SAP EWM. Assigning Users to Tolerance Groups for Recounting/Clearing Use In this step. Choose Change to go to the Change mode. and choose Execute. Procedure 1. you check whether prices for all products are available in SAP EWM. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Settings → Physical Inventory /N/SCWM/PI_USER_DIFF 2. Result Prices for all products are available in SAP EWM. Create the following entries: Field User Name Tolerance Group Difference Analyzer 5. Choose Save. Procedure 1. Choose New Entries. Select all rows.SAP Best Practices Cycle Counting (Y40): BPD 4. 4. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Settings → Physical Inventory /N/SCWM/PI_USER © SAP AG Page 8 of 25 . Variant 1: Counting using paper Process Step Check Physical Inventory Progress Business Condition Cycle Counting Inventory Business Role Warehouse clerk Transaction Code /N/SCWM/MON Expected Results Check the Number of open objects field to calculate the number of bins to be counted at the current date PI documents are created Create PI documents for the calculated number of products Print PI documents within the warehouse management monitor – Warehouse Clerk /N/SCWM/PI_CC_CREATE – Warehouse Clerk /N/SCWM/MON PI count documents are printed © SAP AG Page 9 of 25 . 4. Create the following entries: Cycle Counting (Y40): BPD Field User Name Activity Area Tolerance Group Posting Tolerance Group Recounting 5.SAP Best Practices 2. Process Overview Table In the periodic physical inventory process. You perform the counting using the following two variants: 1. 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. Choose New Entries. Choose Save. Choose Change to go to the change mode. 3. User Action and Values <UserID> <Activity Area> <Tol group for Posting > <Tol group for Recounting > Comment UserID of the supervisor for example PIA2 for example SUPERVISOR for example WORKER Result The assignment of users to tolerance groups for posting and recounting is completed. book quantities on the bins are adjusted. PI document has the status Recounted (RECO).SAP Best Practices Process Step Transfer Count result Cycle Counting (Y40): BPD Business Role Warehouse Clerk Transaction Code /N/SCWM/PI_COUNT Expected Results PI document has the status Posted (POST). no differences. and a new PI document has been created PI documents have been reviewed Business Condition Counting completed and PI papers brought to the office Review recounted documents within warehouse management monitor Post the differences in SAP EWM within the warehouse management monitor _ Warehouse Clerk /N/SCWM/MON _ Warehouse Clerk /N/SCWM/MON PI documents have the status Posted (POST). which are counted completely Post the differences to SAP ERP _ Background user /N/SCWM/PI_COMPL_CHECK _ Background user /N/SCWM/WM_ADJUST Review remaining (highvalue) differences and post them to SAP ERP within the Difference Analyzer _ Warehouse Clerk /N/SCWM/DIFF_ANALYZER © SAP AG Page 10 of 25 . PI document has the status Counted (COUN). differences are posted to the difference analyzer Completeness indicator is set for all products. which are completely counted All differences with a value lower than the threshold value are posted to SAP ERP All differences are posted to SAP ERP Set completeness indicator for products. and the differences have been calculated. and differences have been calculated. which are counted completely Post the differences to SAP ERP _ Background user /N/SCWM/PI_COMPL_CHECK _ Background user /N/SCWM/WM_ADJUST © SAP AG Page 11 of 25 . book quantities on the bins are adjusted. differences are posted to the difference analyzer Completeness indicator is set for all products. PI document has the status Recounted (RECO). which are counted completely All differences with value lower than the Set completeness indicator for products.SAP Best Practices Cycle Counting (Y40): BPD 2. PI document has the status Counted (COUN). and a new PI document has been created PI documents have been reviewed Review recounted documents within warehouse management monitor Post the differences in SAP EWM within the warehouse management monitor _ Warehouse Clerk /N/SCWM/MON _ Warehouse Clerk /N/SCWM/MON PI documents have the status Posted (POST). Variant 2: Counting using an RF (Radio frequency) device Process Step Check Physical Inventory Progress Business Condition Cycle Counting Inventory Business Role warehouse clerk Transaction Code /N/SCWM/MON Expected Results Check the Number of open objects field to calculate the number of bins to be counted at the current date PI documents are created Selects Bins or Products and create PI documents Enter Count result using RF device – Warehouse Clerk /N/SCWM/PI_DOC_CREATE - Counter /N/SCWM/RFUI PI document has the status Posted (POST). no differences. Choose Cycle Counting as criteria if you want to check the PI progress of cycle counting inventory 5. © SAP AG Page 12 of 25 . Choose Activity Area for the simple search. Select the line item appearing on the right-hand section of the warehouse monitor. enter the <activity area> (for example PIA2). and choose All Products. and execute.Warehouse Management Monitor 2. Procedure 1.SAP Best Practices Process Step Business Condition Business Role Cycle Counting (Y40): BPD 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. Make the following entries. and choose Execute: Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Comment for example YEWM for example SAP 3. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Monitoring /N/SCWM/MON . 6. Choose the following navigation options: Physical Inventory→ Physical Inventory Progress. 4. Enter the product number: < Product Number >. Result PI documents are created for the objects for which the periodic physical inventory counting is to be carried out. 3. Select all the line items and choose Create. Enter the activity area: < activity area> (for example PIA2). Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/PI_CC_CREATE 2. and enter the warehouse number: <warehouse number> (for example YEWM). Enter the count date: <current date>. and lays them out in the office. Choose Execute (F8). 4. 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. The system automatically creates one or several warehouse orders for the PI documents.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. for example 10. the warehouse clerk prints the PI count documents for calculating the number of bins or products. Procedure 1. Access the transaction using the following navigation options: SAP Menu © SAP AG Page 13 of 25 Extended Warehouse Management → Monitoring . Printing PI Documents (Paper-Driven PI Only) Use In case of paper-driven PI. Creating PI documents Use PI documents are created for the selected number of bins or products. 6. 7. 5. Select Active PI Document. Procedure 1. Inventory Doc > < Document Year> Comment for example PIA2 The PI doc. Result PI documents are printed and are ready to use. Make the following entries and choose Execute: © SAP AG Page 14 of 25 . and enters the count results into the system. Transferring Count Results from the PI Count Document to the System (Paper-Driven PI Only) Use In case of paper-driven PI. Choose button More Method then Print PI Doc. Make the following entries and choose Execute: Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Comment for example YEWM for exampleSAP 3. Select the line item appearing on the bottom left-hand section of the warehouse monitor. Inventory Doc Document Year User Action and Values < Activity Area > < Phys. Make the following entries and choose Execute: Field Activity Area Phys. the warehouse clerk takes the PI count documents. from .SAP Best Practices Transaction Code /N/SCWM/MON Cycle Counting (Y40): BPD 2. 7. and choose More Methods. Select the line item appearing on the left-hand section of the warehouse monitor. Choose the following navigation options Physical Inventory → Count Overview 4. 6. and choose Total. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory /N/SCWM/PI_COUNT 2. Number generated in previous step 5. Procedure 1. you can choose Check in the SBin Empty field on the Count Items screen. PI document has the status Counted (COUN). If a difference exceeds the predefined. 9. Doc. Select the line item. counter-dependent thresholds for recounting. 4. 8. User Action and Values < Counter Name > <date> for example Name of the Counter for example Counting Date Result • • • PI document has the status Posted (POST) in case of no differences. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Monitoring /N/SCWM/MON 2. In the Qty in Alt. The warehouse clerk monitors the recounted PI documents and retriggers the count process if necessary. and choose Enter. 5. Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents) Use After the input of the count results. Choose Count. and choose Save. the system automatically creates a recount document. Un field. In case the bin is empty. Choose Enter. and a new PI document has been created. Procedure 1. Make the following entries: Field Counter Count date 6. User Action and Values < PI Doc > Cycle Counting (Y40): BPD Comment 3. 7. Inv.SAP Best Practices Field Phys. Select the line item. and choose Switch to Form View. enter the count results (quantity and unit of measure). Enter the Handling Unit in the HU field in case the HU is found in the storage bin. and differences have been calculated. the system calculates the differences on the basis of count results and book inventory. Make the following entries and choose Execute: © SAP AG Page 15 of 25 . PI document has the status Recounted (RECO). For the selected PI documents. 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. It must be done by the supervisor. note the referenced PI document number in the DOC_NUMBER_REF field. During the posting of the PI documents. Choose the following navigation options: Physical Inventory → Physical Inventory Documents. the warehouse clerk is not allowed to post the corresponding PI document. With the help of the new PI document number. the warehouse clerk posts all counted PI documents. and with the procedure mentioned in Transferring Count Results from the PI Count Document to the System in case of paper-driven PI. 4. The system checks in each case if a difference exceeds the thresholds for posting assigned to the warehouse clerk.SAP Best Practices Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Cycle Counting (Y40): BPD Comment for example YEWM for example SAP 3. © SAP AG Page 16 of 25 . Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Monitoring /N/SCWM/MON 2. Additionally. If so. Posting Differences in SAP EWM within the Warehouse Management Monitor Use At the end of the count process. Make the following entries and choose Execute: Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Comment for example YEWM for example SAP 3. the system sets the completeness indicator. the system adapts the book inventory on the bins and posts the differences to the difference analyzer. 6. Choose the following navigation options: Physical Inventory → Physical Inventory Documents. If so. 5. the system checks if a product is counted completely. Procedure 1. Make the following entries and choose Execute: Field Activity Area Physical Inventory Status Creation Date User Action and Values < Activity Area > RECO < current date > Comment for example PIA2 Recounted The date on which the recounted document has been created. Check whether the completeness indicator is set for all products. © SAP AG Page 17 of 25 . Make the following entries and choose Execute: Field Warehouse Number Activity Area Product User Action and Values < Warehouse Number > < Activity Area> <Product> Comment for example YEWM for example PIA2 for example EWMPROD-S01 to EWMPROD-S04 3.SAP Best Practices 4. 4. the system checks if a product is counted completely. Select Current Fiscal Year. 5. select all lines and choose “More Methods”Post PI Doc. Result PI documents have the status Posted (POST). If so. Procedure 1. After the selection. which Are Completely Counted (Background Job) Use With the help of a background job. the system sets the completeness indicator. and choose Execute (F11). which are completely counted. Result The completeness indicator is set for all products. differences are posted to the difference analyzer. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/PI_COMPL_CHECK 2. which are completely counted. book quantities on the bins are adjusted. Make the following entries and choose Execute: Field Activity Area Physical Inventory Status Creation Date User Action and Values < Activity Area > COUN < current date > Cycle Counting (Y40): BPD Comment for example PIA2 The date on which the recounted document has been created. Setting the Completeness Indicator for Products. they post these differences to SAP ERP manually.SAP Best Practices Cycle Counting (Y40): BPD Posting the Differences to SAP ERP (Background Job) Use With the help of a background job. Make the following entries and choose Execute: Field Warehouse Number Difference category Settings 3. Make the following entries and choose Execute: Field Product © SAP AG Page 18 of 25 User Action and Values < Product Number > Comment for example EWMPROD-S01 . they analyze the movements of the product and may decide that a new PI is necessary. If the value of some differences violates the tolerances assigned to the background user. Procedure 1. the warehouse clerk or the supervisor has to review these differences in the difference analyzer. 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 by the background user. for example. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/WM_ADJUST 2. Choose Save. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory /N/SCWM/DIFF_ANALYZER 2. most of the differences are automatically posted to SAP ERP. Procedure 1. After the review. Select the Find category for the difference analyzer 3. User Action and Values < Warehouse Number > Physical Inventory Difference Post on Item Level Comment for example YEWM Result Differences are automatically posted to SAP ERP. Result The warehouse monitor displays all the open objects. © SAP AG Page 19 of 25 . you can check the ongoing progress of Cycle counting through the warehouse management monitor . Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Monitoring /N/SCWM/MON 2. 5. Select the line item on the left-hand section of the warehouse monitor. Select the line item. Procedure 1. and choose Post. and choose Execute: Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Comment for example YEWM for example SAP 3. Choose the following navigation options: Physical Inventory→ Physical Inventory Progress. enter the <activity area> (for example PIA2) and execute. Result All differences are posted to SAP ERP. and choose All Products. Variant 2: Cycle Counting Using RF Based Devices Checking the Periodic Physical Inventory Progress Use As a part of the cycle counting inventory procedure. Make the following entries. 4. Choose Activity Area for the simple search. 6. Choose Cycle Counting as criteria if you want to check the progress of cycle counting. for which physical inventory is to be counted.SAP Best Practices Field User Action and Values Cycle Counting (Y40): BPD Comment 4. Enter the product number: < Product Number >.SAP Best Practices Cycle Counting (Y40): BPD Creating PI documents Use PI documents are created for the selected number of bins or products. for example 10. the counter takes a mobile device. the HU. Entering Count Results Using RF Devices (RF-Driven PI Only) Use In case of RF-driven PI. and logs on as a resource. When the counter finished the counting of this bin. 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 . and choose Create. 4. Select Active PI Document. Select all the line items. 6. Result PI documents are created for the objects for which the periodic physical inventory counting is to be carried out. The system guides the counter to the first bin. 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. and enters the counted quantity. which is assigned to the PI queue. 5. If he or she finds a product not proposed by the system (in case of the bin-specific PI procedure). the system guides him or her to the next bin. Then he or she counts the product. he or she records it. the counter verifies the bin. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/PI_CC_CREATE 2. and enter the warehouse number: <warehouse number> (for example YEWM). Enter the Count date: <current date>. Procedure 1. Choose Execute (F8). and the product proposed by the system. Procedure 1. 7. Enter the activity area < activity area > (for example PIA2). and enters the quantity. Standing in front of it. 3. Enter the handling unit (HU) found in the storage bin during the counting of the bin. counter-dependent thresholds for recounting. Make the following entries and choose Enter: Field Warehouse Number Resource DefPresDvc User Action and Values < Warehouse Number > < Monitor > < DefPresDvc > Comment for example YEWM for example CNT1 for example PRES 3. © SAP AG Page 21 of 25 . Choose Enter. If a difference exceeds the predefined. the system automatically creates a recount document. the system calculates the differences on the basis of count results and book inventory. 5. and choose Enter. and choose Enter.SAP Best Practices Transaction Code /N/SCWM/RFUI Cycle Counting (Y40): BPD 2. and choose Enter. and choose Save after step 5. In case the HU is complete along with the product associated with it. Reviewing Recounted Documents within the Warehouse Management Monitor (Only for Recounted PI Documents) Use After the input of the count results. you can choose F3 HUCmp. The PI document has the status Posted (POST) in case of no differences. Result Inventory counts are entered with the help of RF device s. Choose the following navigation options: 05 Internal Processes → 01 Inventory Counting → 01 Inventory Counting Guided. In case the bin is empty. 9. you can choose F1 BnEmp. you can choose F1 HUEmp. The warehouse clerk monitors the recounted PI documents and retriggers the count process if necessary. In case the HU is empty. Enter the count result for the product next to the Product Description. Copy the bin proposed by the system next to the bin description. and differences have been calculated. 6. 8. Choose Save (F11). and choose Save after step 5. The PI document has the status Counted (COUN). and a new PI document has been created. 4. 7. Copy the product description proposed by the system next to the Product Description. The PI document has the status Recounted (RECO). 5. Post differences in EWM within the Warehouse Management Monitor Use At the end of the count process. note the referenced PI document number in the DOC_NUMBER_REF field. It must be done by the supervisor. the warehouse clerk posts all counted PI documents. Access the transaction using the following navigation options: © SAP AG Page 22 of 25 . During the posting of the PI documents. If so. the warehouse clerk is not allowed to post the corresponding PI document. The system checks in each case if a difference exceeds the thresholds for posting assigned to the warehouse clerk. the system checks if a product is completely counted. If so. With the help of the new PI document number. 6. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Monitoring /N/SCWM/MON 2. and with the procedure mentioned in Transferring Count Results from the PI Count Document to the System in case of paper-driven PI. the system sets the completeness indicator. and posts the differences to the difference analyzer. For the selected PI documents. Make the following entries and choose Execute: Field Activity Area Physical Inventory Status Creation Date User Action and Values < Activity Area > RECO < current date > Comment for example PIA2 Recounted The date on which recounted doc has been crated. Procedure 1. Choose the following navigation options Physical Inventory → Physical Inventory Documents 4.SAP Best Practices Cycle Counting (Y40): BPD Procedure 1. 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. Additionally. Make the following entries and choose Execute: Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Comment for example YEWM for example SAP 3. the system adapts the book inventory on the bins. Make the following entries and choose Execute: Field Activity Area Physical Inventory Status Creation Date User Action and Values < Activity Area > COUN < current date > The date on which the recounted document has been created. After the selection. select all lines and choose Post PI Doc. Result PI documents have the status Posted (POST). Make the following entries and choose Execute: Field Warehouse Number Monitor User Action and Values < Warehouse Number > < Monitor > Comment for example YEWM for example SAP 3. 4. If so. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/PI_COMPL_CHECK 2. the system sets the completeness indicator. differences are posted to the difference analyzer. Comment for example PIA2 5. Make the following entries and choose Execute: Field Warehouse Number Activity Area Product © SAP AG Page 23 of 25 User Action and Values < Warehouse Number > < Activity Area > <Product> Comment for example YEWM for example PIA2 for example EWMPROD-S01 to . Choose the following navigation options: Physical Inventory → Physical Inventory Documents. Procedure 1. the system checks if a product is completely counted. which Are Completely Counted (Background Job) Use With the help of a background job. Setting the Completeness Indicator for Products. book quantities on the bins are adjusted.SAP Best Practices SAP Menu Transaction Code Cycle Counting (Y40): BPD Extended Warehouse Management → Monitoring /N/SCWM/MON 2. which are completely counted. Procedure 1. most of the differences are automatically posted to SAP ERP by the background user. Check whether the completeness indicator is set for all products. Select Current Fiscal Year. Make the following entries and choose Execute: Field Warehouse Number Difference category Settings 3. which are completely counted. Result The completeness indicator is set for all products. Reviewing the Remaining (High-Value) Differences and Posting them to SAP ERP within the Difference Analyzer Use With the help of a background job.SAP Best Practices Field User Action and Values Cycle Counting (Y40): BPD Comment EWMPROD-S04 3. the warehouse © SAP AG Page 24 of 25 . Posting the Differences to SAP ERP (Background Job) Use With the help of a background job. 4. If the value of differences violates the tolerances assigned to the background user. User Action and Values < Warehouse Number > Physical Inventory Difference Post on Item Level Comment for example YEWM Result Differences are automatically posted to SAP ERP. Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory → Periodic Processing /N/SCWM/WM_ADJUST 2. most of the differences are automatically posted to SAP ERP. and choose Execute (F11). Choose Save. © SAP AG Page 25 of 25 . Access the transaction using the following navigation options: SAP Menu Transaction Code Extended Warehouse Management → Physical Inventory /N/SCWM/DIFF_ANALYZER 2. Result All differences are posted to SAP ERP. and may decide that a new PI is necessary. Procedure 1. and choose Post. Select the line item. After the review.SAP Best Practices Cycle Counting (Y40): BPD clerk or the supervisor has to review these differences in the difference analyzer. they post these differences to ERP manually. Select the Find category for the difference analyzer. for example they analyze the movements of the product. 3. Make the following entries and choose Execute: Field Product User Action and Values < Product Number > Comment for example EWMPROD-S01 4.
Copyright © 2024 DOKUMEN.SITE Inc.