Y39_BPP_EN_DE

July 18, 2017 | Author: Pankaj Sehgal | Category: Computing, Technology, Software, Business (General), Computing And Information Technology
Share Embed Donate


Short Description

ok...

Description

SAP EWM 7.01 November 2011 English

Periodic Physical Inventory (Y39) Business Process Documentation

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Periodic Physical Inventory (Y39): 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 AG

Page 2 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

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 3 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): 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, pushbuttons 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.

© SAP AG

F2)

or the

Page 4 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

Contents 1 Purpose ........................................................................................................................................... 6 2 Prerequisites..................................................................................................................................... 6 2.1 Master Data and Organizational Data........................................................................................ 6 2.2 Business Conditions .................................................................................................................. 8 2.3 Preliminary Steps....................................................................................................................... 9 3 Process Overview Table................................................................................................................. 11 4 Process Steps................................................................................................................................. 14 4.1 Variant 1: Paper based Variant................................................................................................14 4.2 RF Based Variant..................................................................................................................... 21

© SAP AG

Page 5 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

Periodic Physical Inventory 1 Purpose You use this business process to control the stock of your warehouse and to meet legal requirements. In this 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 do the counting by 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 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.

2 Prerequisites 2.1 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

Products Number

EWMPROD-S05

Small part, slow-moving 05

Products Number

EWMPROD-S06

Small part, slow-moving 06

Products Number

EWMPROD-M01

Medium part 01

Products Number

EWMPROD-M02

Medium part 02

© SAP AG

Comments

Page 6 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

Master Data

Value

Master Data Details

Products Number

EWMPROD-M03

Medium part 03

Products Number

EWMPROD-L01

Large part 01

Products Number

EWMPROD-L02

Large part 02

Products Number

EWMPROD-L03

Large part 03

Comments

Physical Inventory Procedures Physical Inventory procedure

Description

AL

Annual Physical Inventory (Storage-Bin-Specific)

AS

Annual Physical Inventory (Product-Specific)

PL

Putaway Physical Inventory (Storage-Bin-Specific)

NL

Low Stock Physical Inventory (Storage-Bin-Specific)

HL

Ad-hoc Physical Inventory (Storage-Bin-Specific)

HS

Ad-hoc Physical Inventory (Product-Specific)

EWM-Organizational Data Master / Org. Data EWM Warehouse Number

Value

Master / Org. Data Details

Comments

YEWM

Warehouse-specific structure Org. Data

Value

Org. Data Details

Storage Type

T020

Storage type for small parts; it is divided into 2 sections: 0001 (slow moving part) and 0002 (fast moving part); Number of bins: 480 1 Europallet per bin

Storage Type

T050

Storage type for large parts; Fixed bins are used; Number of bins: 48 3 Europallets per bin

Storage Type

T010

Rack for pallets Standard storage type S001: Total Section Number of bins: 64 3 Europallets per bin

© SAP AG

Comments

Page 7 of 27

SAP Best Practices Org. Data

Periodic Physical Inventory (Y39): BPD Value

Org. Data Details

Storage Type

T051

Rack for all-size parts Standard storage type Three Storage Sections: S001:Small Parts” S002: Medium Parts S003:Large Parts Number of bins: 192 for small parts, 64 bins for medium parts, 48 for large parts

Storage Type

T970

Floor area Staging area group S001: Total Section Bins: STAGE-O02, STAGE-O03 Storage bin type F101 (Floor Ground – Size 6*10)

Activity Area

PIA1

Physical Inventory Area 1

Activity Area

PIAC

PI Area C: Clarification Zone

Comments

.

2.2 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



Implementation of SAP Note 1550675



Implementation of SAP Note 1559241

© SAP AG

Page 8 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

2.3 Preliminary Steps 2.3.1

Creating User Settings for the Difference Analyzer Transaction

Use In this step, you set up user settings that are necessary for the Difference Analyzer transaction.

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

Extended Warehouse Management → Physical Inventory → Difference Analyzer

Transaction Code

/N/SCWM/DIFF_ANALYZER

2. On the Difference Analyzer – Warehouse YEWM screen, choose Default Values. 3. A dialog box appears. In the dialog box, enter YEWM in the Warehouse No. field, and select Phys. Inv. Diff. 4. Choose Enter.

Result You have created the user settings necessary for the Difference Analyzer transaction.

2.3.2

Determining and Setting Prices from SAP ERP

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

Extended Warehouse Management → Physical Inventory → Periodic Processing → Determine and Set Prices from ERP

Transaction Code

/N/SCWM/VALUATION_SET

2. On the Determine and Set Prices screen, enter the warehouse number, for which you have to carry out periodic physical inventory, in the Warehouse Number field. 3. Choose Execute (F8). 4. A new screen appears displaying all the products pertaining to the warehouse number. 5. Select all products and choose Overtake values (F8).

Result The prices for all products are available in SAP EWM.

© SAP AG

Page 9 of 27

SAP Best Practices

2.3.3

Periodic Physical Inventory (Y39): BPD

Assigning Users to Tolerance Groups for the Difference Analyzer

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

Extended Warehouse Management → Settings → Physical Inventory → Assign User to Tolerance Group for Recount/Clearing

Transaction Code

/N/SCWM/PI_USER_DIFF

2. On the Display View “Assignment of User Tolerance Group Difference Analyzer”: Overview screen, choose Display → Change. 3. Choose New Entries. 4. On the New Entries: Overview of Added Entries screen, make the following entries: Field

User Action and Values

Comment

User



UserID of the supervisor

Tolerance Group Difference Analyzer



For example SUPERVISOR

5. Choose Save.

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

2.3.4

Assign Users to Tolerance Groups for Recount/Clearing

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

Extended Warehouse Management → Settings → Physical Inventory

Transaction Code

/N/SCWM/PI_USER

2. On the Display View “Assignment of User Tolerance Group Posting and Recounting”: Overview screen, choose Display → Change. 3. Choose New Entries. 4. On the New Entries: Overview of Added Entries screen, make the following entries:

Field User Name

© SAP AG

User Action and Values

Comment UserID of the

Page 10 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

Field

User Action and Values

Comment supervisor

Activity Area



For example PIA1

Tolerance Group Posting



For example SUPERVISOR

Tolerance Group Recounting



For example WORKER

5. Choose Save.

Result The assignment of users to the tolerance group posting and recounting is completed.

3 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 by using two different variants: 1. Variant 1: Counting by using paper Process Step

Business Condition

Business Role

Transaction Code

Expected Results

Check physical inventory progress

Physical inventory over the year

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

Select bins or products and create PI documents



Warehouse Clerk

/N/SCWM/PI_DOC_CREATE

PI documents are created

Print PI documents within the warehouse management monitor



Warehouse Clerk

/N/SCWM/MON

PI count documents are printed

Enter the count result

Counting completed and PI

Warehouse Clerk

/N/SCWM/PI_COUNT

1. PI documents have the status

© SAP AG

Page 11 of 27

SAP Best Practices Process Step

Periodic Physical Inventory (Y39): BPD

Business Condition

Business Role

Transaction Code

papers were brought to the office

Expected Results POSTED (POST), no differences; 2. PI documents have the status Counted (COUN), and differences have been calculated; 3. PI documents have the status Recounted (RECO), and a new PI document has been created

Review recounted documents within the warehouse management monitor and print the newly created PI Documents

_

Warehouse Clerk

/N/SCWM/MON

PI documents reviewed

Post the differences in 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

Post the differences to ERP

_

Background User

/N/SCWM/WM_ADJUST

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

Review remaining (high-value)

_

Warehouse Clerk

/N/SCWM/DIFF_ANALYZER

All differences are posted to ERP

© SAP AG

Page 12 of 27

SAP Best Practices Process Step

Periodic Physical Inventory (Y39): BPD

Business Condition

Business Role

Transaction Code

Expected Results

differences and post them to ERP within the Difference Analyzer 2. Variant 2: Counting by using a RF (Radio Frequency) device Process Step

Business Condition

Business Role

Transaction Code

Expected Results

Check Physical Inventory Progress

Physical inventory over the year

Warehouse Clerk

/N/SCWM/MON

Check the field Number of open objects 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 the count result using RF(Radio Frequency) device

-

Counter

/N/SCWM/RFUI

1. PI documents have the status POSTED (POST), no differences; 2. PI documents have the status Counted (COUN), and differences have been calculated; 3. PI documents have the status Recounted (RECO), and a new PI document has been created

Review recounted documents within the warehouse management

_

Warehouse Clerk

/N/SCWM/MON

PI documents reviewed

© SAP AG

Page 13 of 27

SAP Best Practices Process Step

Periodic Physical Inventory (Y39): BPD

Business Condition

Business Role

Transaction Code

Expected Results

monitor Post the differences in 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

Post the differences to ERP

_

Background User

/N/SCWM/WM_ADJUST

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

Review remaining (high-value) differences and post them to ERP within the Difference Analyzer

_

Warehouse Clerk

/N/SCWM/DIFF_ANALYZER

All differences are posted to ERP

4 Process Steps 4.1 Variant 1: Paper based Variant 4.1.1

Checking the Periodic Physical Inventory Progress

Use As a part of the periodic physical inventory procedure, you can check the ongoing progress of PI according to the storage bins or products through the warehouse management monitor.

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

© SAP AG

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Page 14 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

Transaction Code

/N/SCWM/MON

2. On the Warehouse Management Monitor SAP – Warehouse Number screen, choose Proposed values. A dialog box appears. 3. In the dialog box, make the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

For example YEWM

Monitor

< Monitor >

For example SAP

4. Choose Execute (F8). 5. Choose Physical Inventory → Physical Inventory Progress. 6. To check the PI progress according to the storage bin, choose Storage Bin. 7. Choose Activity Area and choose Execute. 8. Select the line item appearing on the left-hand section of the warehouse monitor. Then choose Open Bins.

Result The warehouse monitor displays all the open objects, for which you can perform physical inventory counting.

4.1.2

Creating PI Documents

Use You create PI documents for the selected number of bins or products.

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

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/PI_DOC_CREATE

2. On the Create Physical Inventory Documents screen, enter the current date in the Count Date field. 3. In the Physical Inventory Procedure field enter, for example, AL. 4. Select Active PI Document. 5. Enter the storage bins, for which you have to perform the inventory counting in the Storage Bin field. This is applicable only in case of Storage Bin-specific PI procedures like AL.

© SAP AG

Page 15 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

6. Enter the warehouse number in the Warehouse Number field (for example YEWM). 7. Enter the activity area in the Activity Area field (for example PIA1). 8. Choose Execute (F8). 9. Select the line item and choose Create.

You can also carry out the product-specific periodic physical inventory. In this case, you can use inventory procedures like AS and HS. For the product-specific periodic physical inventory procedure, 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 You have created the PI documents for the objects, for which you want to perform the periodic physical inventory counting.

4.1.3

Printing PI Documents (Paper-Driven PI only)

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

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Transaction Code

/N/SCWM/MON

2. On the Warehouse Management Monitor SAP – Warehouse Number screen, choose Proposed values. A dialog box appears. 3. In the dialog box, make the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

for example YEWM

Monitor

< Monitor >

for example SAP

4. Choose Execute. 5. Choose Physical Inventory → Physical Inventory Documents. 6. Choose Physical Inventory Documents, enter the following selection criteria, and choose Execute: Field Activity Area

© SAP AG

User Action and Values < Activity Area >

Comment For example PIA1

Page 16 of 27

SAP Best Practices Field

Periodic Physical Inventory (Y39): BPD User Action and Values

Phys. Inventory Doc

< Phys. Inventory Doc >

Document Year

< Document Year>

Comment The PI document number generated in previous step

7. Select the line item appearing on the left-hand section of the warehouse monitor, and choose More Methods. 8. Choose Print PI Doc.

Result The PI documents are printed and ready to use.

4.1.4 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 enters the count results into the system with the help of the PI count documents.

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

Extended Warehouse Management → Physical Inventory → Enter Count Results

Transaction Code

/N/SCWM/PI_COUNT

2. On the Create Count Results for Physical Inventory screen, create the following entries: Field Phys. Inv. Doc.

User Action and Values

Comment

< PI Doc >

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

User Action and Values

Counter

< Counter Name >

for example Name of the Counter

Count date



for example Counting Date

7. Choose Enter.

© SAP AG

Page 17 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

8. Enter the Handling Unit in the HU field, in case the HU is found in the storage bin 9. In the Qty in Alt. Un field, enter the count results (quantity and unit of measure), and choose Enter. 10. 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 the differences have been calculated.



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

4.1.5 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 base 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 triggers again the count process if necessary by printing the new PI document.

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

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Transaction Code

/N/SCWM/MON

2. On the SAP screen, create the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

For example YEWM

Monitor

< Monitor >

For example SAP

3. Choose Execute. 4. Choose Physical Inventory → Physical Inventory Documents. 5. Use the following selection criteria and choose Execute: Field Activity Area

© SAP AG

User Action and Values < Activity Area >

Comment for example PIA1

Page 18 of 27

SAP Best Practices Field

Periodic Physical Inventory (Y39): BPD User Action and Values

Comment

Physical Inventory Status

RECO

Recounted

Creation Date

< current date >

The date on which recounted doc has been crated.

6. For the selected PI documents, note down the referenced PI document number (DOC_NUMBER_REF field). 7. With the help of the new PI document number, you can enter new counting results with the same procedure mentioned in the Enter Count Results Using RF Device section 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.

4.1.6 Posting Differences in SAP EWM within the Warehouse Management Monitor Use At the end of the count process, the warehouse clerk posts all the counted PI documents. In each case, the system checks 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. The supervisor has to do it. During the posting of the PI documents, the system adapts the book inventory 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 one of the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Transaction Code

/N/SCWM/MON

2. On the Warehouse Management Monitor SAP – Warehouse Number screen, choose Proposed values. A dialog box appears. 3. In the dialog box, make the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

For example YEWM

Monitor

< Monitor >

For example SAP

4. Choose Execute 5. Choose Physical Inventory → Physical Inventory Documents. 6. Use the following selection criteria, and choose Execute:

© SAP AG

Page 19 of 27

SAP Best Practices Field

Periodic Physical Inventory (Y39): BPD User Action and Values

Activity Area

< Activity Area >

Physical Inventory Status

COUN

Creation Date

< current date >

Comment For example PIA1

The date on which recounted doc has been created

7. Select all lines and choose More Methods, and choose Post PI Doc.

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

4.1.7

Posting the Differences to SAP ERP (in the Background)

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 one of the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/WM_ADJUST

2. On the Automatic Posting of Differences screen, proceed as follows: 1. Enter the warehouse number in the Warehouse Number field (for example YEWM). 2. Select Physical Inventory Difference in the Difference Category screen area. 3. Select Post on Item Level in the Settings screen area. 4. Choose Execute

Result The differences are automatically posted to SAP ERP.

4.1.8 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

© SAP AG

Page 20 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

example, they analyze the movements of the product and may decide that a new PI is necessary. After the review, they manually.post these differences to SAP ERP.

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

Extended Warehouse Management → Physical Inventory →Difference Analyzer

Transaction Code

/N/SCWM/DIFF_ANALYZER

2. On the Difference Analyzer – Warehouse YEWM screen, choose Product in the Find field, and enter the product number, for example EWMPROD-S01, in the adjacent field. 3. Choose Execute. 4. Select the line item and choose Post.

Result You posted all differences to SAP ERP.

4.2 RF Based Variant 4.2.1

Checking the Periodic Physical Inventory Progress

Use As a part of the periodic physical inventory procedure, you can check the ongoing progress of PI according to the storage bins or products through the warehouse management monitor.

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

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Transaction Code

/N/SCWM/MON

2. On the Warehouse Management Monitor SAP – Warehouse Number screen, choose Proposed values. A dialog box appears. 3. In the dialog box, make the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

For example YEWM

Monitor

< Monitor >

For example SAP

4. Choose Execute (F8). 5. Choose Physical Inventory → Physical Inventory Progress.

© SAP AG

Page 21 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

6. To check the PI progress according to the storage bin, choose Storage Bin. 7. Choose Activity Area and choose Execute. 8. Select the line item appearing on the left-hand section of the warehouse monitor. Then choose Open Bins.

Result The warehouse monitor displays all the open objects, for which you can perform physical inventory counting.

4.2.2

Creating PI Documents

Use You create PI documents for the selected number of bins or products.

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

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/PI_DOC_CREATE

2. On the Create Physical Inventory Documents screen, enter the current date in the Count Date field. 3. In the Physical Inventory Procedure field, enter, for example, AL. 4. Choose Active PI Document. 5. Enter the storage bins, for which you have to perform the inventory counting in the Storage Bin field. This is applicable only in case of Storage Bin-specific PI procedures like AL. 6. Enter the warehouse number in the Warehouse Number field (for example YEWM). 7. Enter the activity area in the Activity Area field (for example PIA1). 8. Choose Execute (F8). 9. Select the line item and choose Create.

You can also carry out the product-specific periodic physical inventory. In this case, you can use inventory procedures like AS and HS. For the product-specific periodic physical inventory procedure, 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 © SAP AG

Page 22 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

You have created the PI documents for the objects, for which you want to perform the periodic physical inventory counting.

4.2.3 Entering Count Results Using RF Devices (RF-Driven PI Only) Use In case of radio-frequency-driven (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. 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 bin-specific PI procedure), he or she records it and enters the quantity counted. When the counter finishes the counting of this bin, the system guides him or her to the next bin.

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

Extended Warehouse Management → Execution → Log On to RF Environment

Transaction Code

/N/SCWM/RFUI

2. On the SAP screen, make the following entries: Field

User Action and Values

Comment

Warehouse No.

< Warehouse Number >

For example YEWM

Resource

< Monitor >

For example CNT1

DefPresDvc

< DefPresDvc>

For example PD01, that is Mobile Device PD01

3. Choose Enter. 4. Choose 05 Internal Processes → 01 Inventory Counting → 01 Inventory Counting Guided. 5. 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. 6. Enter the HU (Handling Unit) found in the storage bin during the counting the bin and choose Enter. In case the HU is empty, you can choose F1 HUEmp after step 6, and choose Save. In case the HU is complete along with the product associated with it, you can choose F3 HUCmp, and choose Save after step 6. 7. Choose Enter.

© SAP AG

Page 23 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

8. Copy the product description proposed by the system next to the Product Description, and choose Enter. 9. Enter the count result for the product next to the Product Description. 10. Choose Save (F11).

Result The following inventory counts status are possible: •

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

4.2.4 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 base 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 triggers again the count process again.

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

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Transaction Code

/N/SCWM/MON

2. On the SAP screen, create the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

For example YEWM

Monitor

< Monitor >

For example SAP

3. Choose Execute. 4. Choose Physical Inventory → Physical Inventory Documents. 5. Use the following selection criteria, and choose Execute: Field

User Action and Values

Comment

Activity Area

< Activity Area >

For example PIA1

Physical Inventory Status

RECO

Recounted

© SAP AG

Page 24 of 27

SAP Best Practices Field Creation Date

Periodic Physical Inventory (Y39): BPD User Action and Values < current date >

Comment The date on which the recounted document has been crated.

6. For the selected PI documents, note down the referenced PI document number (DOC_NUMBER_REF field). 7. With the help of the new PI document number, you can enter new counting results with the same procedure mentioned in Enter Count Results Using RF Device 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.

4.2.5 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. In each case, the system checks 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. The supervisor has to do it. During the posting of the PI documents, the system adapts the book inventory 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 one of the following navigation options: SAP Menu

Extended Warehouse Management → Monitoring → Warehouse Management Monitor

Transaction Code

/N/SCWM/MON

2. On the Warehouse Management Monitor SAP – Warehouse Number screen, choose Proposed values. A dialog box appears. 3. In the dialog box, make the following entries: Field

User Action and Values

Comment

Warehouse Number

< Warehouse Number >

For example YEWM

Monitor

< Monitor >

For example SAP

4. Choose Execute. 5. Choose Physical Inventory → Physical Inventory Documents. 6. Use the following selection criteria and choose Execute: Field Activity Area

© SAP AG

User Action and Values < Activity Area >

Comment For example PIA1

Page 25 of 27

SAP Best Practices Field

Periodic Physical Inventory (Y39): BPD User Action and Values

Physical Inventory Status

COUN

Creation Date

< current date >

Comment

The date on which the recounted document has been created

7. Select all lines, and choose More Methods, and choose Post PI Doc.

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

4.2.6

Posting the Differences to SAP ERP (in the Background)

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 one of the following navigation options: SAP Menu

Extended Warehouse Management → Physical Inventory → Periodic Processing

Transaction Code

/N/SCWM/WM_ADJUST

2. On the Automatic Posting of Differences screen, proceed as follows: 1. Enter the warehouse number in the warehouse number field (for example YEWM). 2. Select Physical Inventory Difference in the Difference Category screen area. 3. Select Post on Item Level in the Settings screen area. 4. Choose Execute.

Result The differences are automatically posted to SAP ERP.

4.2.7 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 ERP manually.

© SAP AG

Page 26 of 27

SAP Best Practices

Periodic Physical Inventory (Y39): BPD

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

Extended Warehouse Management → Physical Inventory →Difference Analyzer

Transaction Code

/N/SCWM/DIFF_ANALYZER

2. On the Difference Analyzer – Warehouse YEWM screen, select Product in the Find field, and enter the product number, for example EWMPROD-S01, in the adjacent field. 3. Choose Execute. 4. Select the line item and choose Post.

Result You posted all differences to SAP ERP.

© SAP AG

Page 27 of 27

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF