3BX S4CLD2402 BPD en PT

Test Script
SAP S/4HANA Cloud - 23-12-23
Warehouse Physical Inventory (3BX_PT)
PUBLIC
Table of Contents
1 Purpose
2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 Additional Manual Configuration
2.5 Business Conditions
2.6 Preliminary Steps
2.6.1 Define Default Values for Warehouse Clerk (WM)
2.6.2 Define Default Values for Warehouse Operative (WM)
2.6.3 Assign User to Tolerance Group for Clearing
2.6.4 Assign User to Tolerance Group for Difference Analyzer
2.6.5 Define Cycle Counting Indicator
2.6.6 Assign Cycle Counting Indicator
3 Overview Table
4 Test Procedures
4.1 Variant 1: Create and Print Cycle Counting Document
4.2 Variant 2: Create and Print Counting Document
4.3 Variant 3: Create Counting Document with Radio Frequency
4.4 Enter Count Result
4.4.1 Variant 1: With Fiori App
4.4.2 Variant 2: With Radio Frequency Devices
4.5 Confirm Inventory Count Results
4.6 Analyze Differences
Test Procedures PUBLIC 2
1 Purpose
Overview
In this scope item, you can plan, conduct, and confirm regular counts of actual product quantities in the warehouse and compare the physical stock to the data in the system. You first create physical
inventory documents for a chosen number of storage bins or products or based on cycle counting indicators. The cycle counting method is used to count products at regular intervals during a year.
You can set up counting intervals based on cycle count indicators. After the documents are created and printed, you count the stock in the warehouse. You enter the count result in the system and re-
view discrepancies in the system quantities. By posting the PI documents, you adjust the book inventory in the storage bins to align it with the physical inventory counts. The inventory may be re-
counted until final counts are accepted. Finally, inventory differences are posted to reconcile stocks in the SAP S/4HANA Cloud system.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.
Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different notation, enter values as appropri-
ate.

2 Prerequisites
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.
2.1 System Access
System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.
2.2 Roles
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role from a Template in the product assistance for SAP S/4HANA Cloud.
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
Template) On
Warehouse Clerk SAP_BR_WAREHOUSE_ Warehouse Office SAP_BR_WAREHOUSE_CLERK_EWM

(EWM) CLERK_EWM
Warehouse Op- SAP_BR_WAREHOUSE_ Warehouse Floor SAP_BR_WAREHOUSE_OPERATIVE_EWM

erative (EWM) OPERATIVE_EWM
Master Data SAP_BR_PRODMAS- Master Data - Products SAP_BR_PRODMASTER_SPECIALIST

Specialist - Prod- TER_SPECIALIST
uct Data
Configuration SAP_BR_BPC_EXPERT Business Process Configuration / Business Configuration - Feature Manage- SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC /
Expert - Busi- ment / Business Process Configuration - Workflow / Manage your Solution / SAP_CA_SPT_BPC_WORKFLOW_PC / SAP_CA_SPT_IC_LND_BASE_PC /
ness Process Business Process Configuration - Extensibility Explorer / Business Process SAP_EI_SPT_BPC_EXT_PC / SAP_FIN_SPT_BPC_EXPERT_PC /
Configuration Configuration - Finance / Business Process Configuration - Procurement / Busi- SAP_MM_SPT_BIZ_PROC_CONFIGN_PC / SAP_TM_SPT_TRANSPCFG_PC
ness Configuration - Transportation

2.3 Master Data, Organizational Data, and Other Data
The organizational structure and master data of your company have been created in your system during activation. The organizational structure reflects the structure of your company. The master
data represents materials, customers, and suppliers, for example, depending on the operational focus of your company.
Use your own master data or the following sample data to go through the test procedure.
Data Sample Value Details Comments
Material TG11 Trad.Good 11,PD,Reg.Trading Storage
Material TG12 Trad.Good 12,Reorder Point,Reg.Trad. Fixed Bin Storage
Material TG21 Trad.Good 21,Reorder Point,Batch-FIFO Bulk Storage
Material TG0011 Trading Good 0011,PD,Regular Proc. General Storage
Material TG0013 Trading Good 0013,PD,Regular Proc. General Storage
Company Code 3510
Purchase Organization 3510
Plant 3510
Storage Location 355W
Organizational Master Data in Warehouse:
Warehouse 3550
Custodian 35413510
Entitled to Dispose 35413510
Warehouse-Specific Master Data:
Storage Type S001 Storage
Storage Type SF01 Fixed Bin Storage

Storage Type SB01 Bulk Storage
Storage Type SG01 General Storage
Storage Type S970 Clarification Zone
You can find general information on how to create master data objects in the following Master Data Scripts (MDS) :
MDS Description
BNF Create Product Master of Type "Trading Good"
3KQ Create Warehouse Attributes for Material/Product Master
3KR Create Warehouse Storage Bins and Fixed Bin Assignments
2.4 Additional Manual Configuration

Before you can test this scope item, you must have completed the additional configuration steps that are described in the Set-Up Instructions for this scope item. These configuration steps are specific
for your implementation and include mandatory settings that are not delivered by SAP and must be created by you. For more information, follow the link to the document:
Link to Set-Up Instructions
Before you start the testing, please make sure that the steps in the Warehouse Management Setup Guide.docx (Public) published on SAP Activate Roadmap Viewer have been completed.
If you are working with a radio frequency device, carry out the steps described in Mobile RF Devices in Warehousing (63V).
2.5 Business Conditions

Before you can test this scope item, the following business conditions must be met.
Scope Item ID Business Condition
BNZ - Create New Open MM Posting Period You have completed the procedure in the Create New Open MM Posting Period test script.
3BR - Warehouse Inbound Processing or You have completed the procedure in the Warehouse Inbound Processing test script or in the Data Migration to SAP S/4HANA from Staging test script.
2Q2 - Data Migration to SAP S/4HANA from Staging

2.6 Preliminary Steps
2.6.1 Define Default Values for Warehouse Clerk (WM)
Purpose
In this step, you can define the default warehouse number for the Warehouse Clerk (EWM).
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Log On Log on to the SAP Fiori Launchpad as a Warehouse Clerk (EWM).
2 Choose Avatar Choose your avatar.

Then, choose Settings.
3 Enter Default Value Choose Default Values.

Enter the following data:
Warehouse Number: 3550.
Choose Save.
2.6.2 Define Default Values for Warehouse Operative (WM)
Purpose
In this step, you can define the default warehouse number for the Warehouse Operative (EWM).

Procedure
1 Log On Log on to the SAP Fiori launchpad as a Warehouse Operative (EWM). The Fiori launchpad is displayed.
2 Choose Avatar Choose your avatar.

Then, choose Settings.
3 Enter Default Value Choose Default Values.

In the Material Management section, enter the following data:
Choose Save.
2.6.3 Assign User to Tolerance Group for Clearing
Purpose
Here, you assign individual logon users to tolerance groups which have previously been defined in the system.
Generally, the assignment of users to tolerance groups determines whether a logon user can post differences or enter values within the tolerance boundaries.
Procedure
1 Log On Log on to the SAP Fiori Launchpad as a Warehouse Clerk (EWM). The SAP Fiori launchpad is displayed.
2 Access App Open Assign Tolerance Group - Count Confirmation (/SCWM/PI_USER).
3 Close Warning Message If there’s a warning message for the initial value, choose Continue to confirm it.
4 Switch to Edit Mode Choose Edit.
5 Assign to Tolerance Group Choose New Entries and make the following entries:
User: <User>.

AA:
Tolerance Group: STOLCHECK.
Note Choose STOLCHECK if you want to have the tolerance check, otherwise choose SNOTOLCHECK.
Choose Save.
2.6.4 Assign User to Tolerance Group for Difference Analyzer
Purpose
In this transaction, you assign individual logon users to tolerance groups which have previously been defined in the system configuration.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Log On Log on to the SAP Fiori Launchpad as a Warehouse Clerk (EWM). The SAP Fiori
launchpad is dis-
played
2 Access App Open Assign Tolerance Group - Differences (/SCWM/PI_USER_DIFF).
3 Close Warning If there is a warning message for the initial value, choose Continue to confirm it.
Message
4 Switch to Edit Choose Edit.

Mode
5 Assign Tolerance Choose New Entries to create entries as needed. Here, you need to make assignments to real users that you use in your system. Therefore, the following
Group (Original) users given in angle brackets (<>) are only examples.
If you log on as a background job user, enter the following data:

Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment
User: <User>
Tolerance Group: SNOTOLCHECK
Note Choose STOLCHECK if you want to have the tolerance check. Otherwise, choose SNOTOLCHECK.
Choose Save.
Note If you choose SNOTOLCHECKs on company code level, there's still a maximum value limitation by default. If a physical inventory document
exceeds value 100,000 on header level or 10,000 on item level, the user is not allowed to post any inventory differences for this document. However,
the maximum value can be adjusted via the Maintain Physical Inventory Tolerance configuration step.
2.6.5 Define Cycle Counting Indicator
Purpose
In this step, you define the sample counting indicator. For each indicator, you define
● the interval in work days after which a new physical inventory should be performed.
● the buffer time in work days.
Procedure
1 Log On Log on to the SAP Fiori Launchpad as Configuration Expert - Business Process Configuration.
2 Choose App Open Manage Your Solution (F1241).
3 Choose Option Choose Configure Your Solution.

Search for Configure Cycle Counting.

4 Navigate to the Configuration Step Choose the configuration item and navigate to the Configure Cycle Counting step, then choose Configure.
5 Enter Data Choose New Entries and enter the following data:
1st Entry:
CC Option: A .
Interval: 60.
Buffer: 5.
2nd Entry:
CC Option: B .
Interval: 120.
Buffer: 5.
3rd Entry:
CC Option: C .
Interval: 240.
Buffer: 5.
Choose Save.
Note Depending on your configuration environment, configuration steps can be accessed unter Configure Your Solution in the SAP Fiori launchpad or via the configuration activity in the Prod-
uct-Specific Configuration phase in the project experience of SAP Central Business Configuration.
2.6.6 Assign Cycle Counting Indicator
Purpose
In this step, you assign the cycle counting indicator to the product master. The maintenance of the cycle counting indicator is also supported in data migration of warehouse products (see the Data
Migration to SAP S/4HANA from Staging (2Q2) scope item).

Procedure
1 Log On Log on to the SAP Fiori Launchpad as Master Data Specialist - Product Data.
2 Choose App Open Manage Product Master Data (F1602).
3 Enter Selection Data Maintain the following selection value:

Product: TG12.
Choose Go.
4 Select Product Choose the entry of the product.
5 Choose Tab Choose the Warehouse Management tab and then the Warehouse subtab.
6 Choose Warehouse Choose the row for warehouse number 3550.
7 Enter Data Maintain the following value:

Cycle Counting Indicator: A.
Note Depending on the counting interval for the product, you assign different cycle counting indicators.
Choose Apply.
8 Save Data Choose Save.

3 Overview Table
This scope item consists of several process steps provided in the table below.
Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Process Step Business Role App/Transaction Expected Results
Variant 1: Create and Print Cycle Counting Document Warehouse Operative Create Inventory Documents - Cycle Counting (/SCWM/ You have created a physical inventory document.
[page ] 14 (EWM) PI_CC_CREATE)
Variant 2: Create and Print Counting Document [page ] Warehouse Operative Create Inventory Documents - Physical Inventory (/SCWM/ You have created and printed the counting documents.
15 (EWM) PI_DOC_CREATE)
Enter Count Result [page ] 18 Warehouse Operative Count Physical Inventory - Paper-Driven Counting (F3340) You have entered the count result.
(EWM)
Confirm Inventory Count Results [page ] 20 Warehouse Clerk (EWM) Confirm Inventory Count Results (/SCWM/MONNAV_PI_CONF) You have checked and confirmed the inventory count re-
sults.
Analyze Differences [page ] 21 Warehouse Clerk (EWM) Analyze Differences (/SCWM/DIFF_ANALYZER) You have cleared all differences and a material document is
created.

4 Test Procedures
4.1 Variant 1: Create and Print Cycle Counting Document
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Testing Date:
Tester Name: Duration:
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
The Warehouse Operative (EWM) creates a physical inventory document for inventory counting.
Procedure
1 Log On Log on to the SAP Fiori Launchpad as Warehouse Operative (EWM). The SAP Fiori Launchpad is displayed.
2 Access App Open Create Inventory Documents - Cycle Counting (/SCWM/PI_CC_CREATE).
3 Enter Selection Data Maintain the following entries: The PI document is created.
Cycle Counting Indicator: A.
Count Date: <Current date or date in the future>.
Print PI Document: X.
You can enter other selection data such as activity area, products, and storage bins.
Choose Execute.

4 Create Physical Inventory Document Select the line(s) for which a physical inventory should be processed.
Choose Create.
Note down the physical inventory document number.
4.2 Variant 2: Create and Print Counting Document
Test Administration
Purpose
The warehouse operative creates the physical inventory document for inventory counting.
Procedure
1 Log On Log on to the SAP Fiori Launchpad as a Warehouse Operative (EWM). The SAP Fiori Launchpad is dis-
played.
2 Access App Open Create Inventory Documents - Physical Inventory (/SCWM/PI_DOC_CREATE).
3 Enter Selection Data Maintain the following entries: The PI document is created.

Physical Inventory Procedure: AL (Annual Physical Inventory (Storage-Bin-Spe-

cific))
Note You can choose another physical inventory procedure, for example, HL, HS, or AS, according to your
requirement.
Count Date: <Current date or date in the future>

Print PI Document: X
You can enter other selection data such as activity area, products, and storage bins.
Choose Execute.
4 Create Physical Inventory Docu- Select the lines for which a physical inventory should be processed.
ment Choose Create.
Note down the physical inventory document number.
4.3 Variant 3: Create Counting Document with Radio Frequency
Test Administration
Purpose
The Warehouse Operative (EWM) creates the ad-hoc physical inventory document for inventory counting with the mobile Radio Frequency device.
Note For working with mobile RF devices, make sure all the steps as described in the setup instruction guide for scope item 63V - Mobile RF Devices in Warehousing have been performed.

Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail /
# Comment
1. Log on Log on to the SAP Fiori launchpad as a Warehouse Operative (EWM) . The SAP Fiori Launchpad is
displayed.
2. Access the SAP Fiori Open the SAP Fiori app Test RF Environment (/SCWM/RFUI).
App
3 Enter Data for RFUI Whse No: 3550

Resource: SCNT-1
DefPresDvc: SE01
Choose Enter.
4 Choose Menu Choose 05 Internal Process > 01 Inventory Counting > Adhoc Inv. Creation .
5 Enter Data for PI Doc- Make the following entries:

ument Stor.Bin: <Enter Storage Bin for which you want to count>
Product: < Enter Product >
Note If you just enter storage bin data, the Ad-hoc bin specific PI document with HL procedure is created.
If you enter both storage bin and product data, the Ad-hoc product specific PI document with HS procedure will be created.
6 Set Block Indicator Choose SetBlk, if required.

(Optional)
Note This indicator is used to block the storage bin, if a physical inventory document is created for bin-specific physical inven-
tory or to block product movement for product-specific physical inventory.
7 Create Counting Docu- Choose CrPI.

ment The Adhoc PI document was created.

4.4 Enter Count Result
4.4.1 Variant 1: With Fiori App
Test Administration
Purpose
The Warehouse Operative (EWM) enters the count result in the system.
Procedure
1 Log On Log on to the SAP Fiori Launchpad as a Warehouse Operative (EWM).
2 Access App Open Count Physical Inventory - Paper-Driven Counting (F3340).
3 Select Physical Inventory Document Maintain the following selection values:

Document Year: <Current Year>.
Physical Inventory Document: <PI document created before>.
Choose Go.
Choose the PI document and choose Count.
4 Enter Count Results Enter Counter.

Enter Count Date and Time.

If the count date is equal to the current date, you can leave the field blank as it is filled automatically.
Enter Quantity and UoM.
If the bin is empty, check 'Bin Empty'.
5 Save Your Changes Choose Save.
4.4.2 Variant 2: With Radio Frequency Devices
Test Administration
Purpose
The Warehouse Operative (EWM) enters the count result via mobile radio frequency device.
Note For working with mobile RF devices, make sure all the steps as described in the set-up instruction guide for scope item 63V - Mobile RF Devices in Warehousing have been performed.
Procedure
1. Log on Log on to the SAP Fiori launchpad as a Warehouse Operative (EWM). The SAP Fiori Launchpad is displayed.
2. Access the SAP Fiori App Open the SAP Fiori app Test RF Environment (/SCWM/RFUI)

3 Enter Data for RFUI Whse No: 3550

Resource :SCNT-1
DefPresDvc :SE01
Choose Enter.
4 Choose Menu Choose 01 System-Guided > 02 SystemGuided Queue .
5 Enter Queue Name In the Queue field, enter SP-001, SP-F01,SP-B01 or SP-G01
6 Verify Storage Bin Verify the Stor.Bin (Storage Bin).
7 Enter Count Result Depending on the stock situation, you will need to enter HU or product for counting.
8 Enter HU for Counting If you enter HU for counting, choose Enter. The corresponding HU is selected.
If the HU is empty, choose HUEmp.
If the HU is complete, choose HUCmp
Choose Enter to count the product within the HU. Enter Product , Quantity and UoM.
Once the products in the HU are counted, choose Back.
9 Enter Product for Counting You verify the product for counting.
Enter Quantity and UoM for the product.
10 Save Counting Result Choose Save. Scroll the screen to right if you cannot find the button.
11 Repeat Steps Repeat steps 6 to 10 until no suitable warehouse orders are found.
4.5 Confirm Inventory Count Results
Test Administration

Purpose
The Warehouse Clerk (EWM) checks the counting result and posts the difference. In case that the difference is outside tolerance, he or she can trigger the recounting.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail /
# Comment
1 Log On Log on to the SAP Fiori launchpad as a Warehouse Clerk (EWM).
2 Access App Open Confirm Inventory Count Results (/SCWM/MONNAV_PI_CONF).
3 Search PI Docu- Choose Set Selection Criteria.

ment Search for the counted PI documents using the following data:
Physical Inventory Status: COUN.
Count Date: <Count Date you entered before>.
Choose Execute.
4 Post PI Docu- Choose the selected PI document. If the count difference is under the posting tolerance, the PI document is
ment Choose More methods > Post Phys. Inv. Document. posted. Otherwise, the status remains COUN.
Select the PI document, check the count result, and choose Post.
5 Trigger Recount If the selected PI document is not posted in the previous step, choose More methods > Re- The status of the PI documentchanges to RECO. A new PI document is cre-
count Phys. Inv. Document to trigger the recounting. ated for recounting.
4.6 Analyze Differences
Test Administration

Purpose
The Warehouse Clerk (EWM) posts the differences to the ERP to align the stock figures.
Note It is not possible to post the serial number differences on item level as this leads to problems upon lost and found of a serial number. See more details in note 2871065
Procedure
Test Step Test Step Instruction Expected Result Pass / Fail / Com-
# Name ment
1 Log On Log on the SAP Fiori Launchpad as a Warehouse Clerk (EWM). The SAP Fiori launchpad is displayed.
2 Access App Open Analyze Differences (/SCWM/DIFF_ANALYZER).
3 Set Default Choose Default Values and make the following entries:
Values Warehouse No.: 3550.
Phys. Inv. Diff.: X.
WT Difference: X.
Choose Continue.
4 Post Differ- Search for the product for which physical inventory was processed or maintained, for example Party Entitled to Dispose, by All differences are cleared and a material
ences choosing Open Advanced Search and process the search. document is created.
Select an entry and choose Post.
Choose Yes to confirm posting the differences.

Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names,
menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions. www.sap.com/contactsap
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and
key concepts of a programming language when they are surrounded by body text, for example, SELECT and IN-
CLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parame-
ters, source text, and names of installation, upgrade and database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documenta-
tion.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
© 2024 SAP SE or an SAP affiliate company. 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 SE or an SAP affili-
ate company. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in the express war-
ranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.
See www.sap.com/copyright for additional trademark informa-

Warehouse Physical Inventory (3BX_PT) tion and notices.

3BX S4CLD2402 BPD en PT

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3BX S4CLD2402 BPD en PT

Uploaded by

Copyright:

Available Formats

Test Script

SAP S/4HANA Cloud - 23-12-23

Warehouse Physical Inventory (3BX_PT)

Warehouse Physical Inventory (3BX_PT)

2.1 System Access

Warehouse Clerk SAP_BR_WAREHOUSE_ Warehouse Office SAP_BR_WAREHOUSE_CLERK_EWM

Warehouse Op- SAP_BR_WAREHOUSE_ Warehouse Floor SAP_BR_WAREHOUSE_OPERATIVE_EWM

Master Data SAP_BR_PRODMAS- Master Data - Products SAP_BR_PRODMASTER_SPECIALIST

Warehouse Physical Inventory (3BX_PT)

Data Sample Value Details Comments

Material TG11 Trad.Good 11,PD,Reg.Trading Storage

Material TG12 Trad.Good 12,Reorder Point,Reg.Trad. Fixed Bin Storage

Material TG21 Trad.Good 21,Reorder Point,Batch-FIFO Bulk Storage

Material TG0011 Trading Good 0011,PD,Regular Proc. General Storage

Material TG0013 Trading Good 0013,PD,Regular Proc. General Storage

Company Code 3510

Purchase Organization 3510

Storage Location 355W

Organizational Master Data in Warehouse:

Data Sample Value Details Comments

Entitled to Dispose 35413510

Warehouse-Specific Master Data:

Data Sample Value Details Comments

Storage Type S001 Storage

Storage Type SF01 Fixed Bin Storage

Warehouse Physical Inventory (3BX_PT)

Storage Type SB01 Bulk Storage

Storage Type SG01 General Storage

Storage Type S970 Clarification Zone

BNF Create Product Master of Type "Trading Good"

3KQ Create Warehouse Attributes for Material/Product Master

3KR Create Warehouse Storage Bins and Fixed Bin Assignments

2.4 Additional Manual Configuration

2.5 Business Conditions

Scope Item ID Business Condition

Warehouse Physical Inventory (3BX_PT)

2.6.1 Define Default Values for Warehouse Clerk (WM)

1 Log On Log on to the SAP Fiori Launchpad as a Warehouse Clerk (EWM).

2 Choose Avatar Choose your avatar.

3 Enter Default Value Choose Default Values.

2.6.2 Define Default Values for Warehouse Operative (WM)

Warehouse Physical Inventory (3BX_PT)

2 Choose Avatar Choose your avatar.

3 Enter Default Value Choose Default Values.

2.6.3 Assign User to Tolerance Group for Clearing

2 Access App Open Assign Tolerance Group - Count Confirmation (/SCWM/PI_USER).

4 Switch to Edit Mode Choose Edit.

Warehouse Physical Inventory (3BX_PT)

2.6.4 Assign User to Tolerance Group for Difference Analyzer

Test Test Step Name Instruction Expected Result Pass / Fail /

2 Access App Open Assign Tolerance Group - Differences (/SCWM/PI_USER_DIFF).

4 Switch to Edit Choose Edit.

Warehouse Physical Inventory (3BX_PT)

2.6.5 Define Cycle Counting Indicator

2 Choose App Open Manage Your Solution (F1241).

3 Choose Option Choose Configure Your Solution.

Warehouse Physical Inventory (3BX_PT)

2.6.6 Assign Cycle Counting Indicator

Warehouse Physical Inventory (3BX_PT)

2 Choose App Open Manage Product Master Data (F1602).

3 Enter Selection Data Maintain the following selection value:

4 Select Product Choose the entry of the product.

6 Choose Warehouse Choose the row for warehouse number 3550.