1.

Test Script CUSTOMER

SAP EWM 9.3
May 2016
English
Inbound of Batch-Managed Products from
Vendor
ID: 1DB

Table of Contents

Document History 3

1 Test Description 4

2 Prerequisites 5
2.1 Master Data and Organizational Data 5
2.2 Business Conditions 7
2.3 Preliminary Steps 8
2.3.1 Creating User Settings for the Transaction /SCWM/GRPE 8
2.3.2 Creating User Settings for the Transaction /SCWM/MON 9
2.3.3 Maintaining User (for RFUI Processing) 10
2.3.4 Checking/Closing Period for Material Master Records 11
2.3.5 Create User Settings for Transaction ME21N 12
2.4 Template for ID Sheet 13

3 Overview Table 15

4 Test Procedures 16
4.1 Create a Purchase Order 16
4.2 Maintenance of Expected Goods Receipt 18
4.3 Create an Inbound Delivery with Reference to EGR 20
4.4 Process the Goods Receipt 22
4.5 Check Physical Stock 25
4.6 Check Warehouse Orders 26
4.7 Putaway Products to the High Rack Storage (Lower Levels) 27
4.8 Check the Inbound Delivery in the SAP S/4HANA System 28

5 Appendix 30
5.1 Create EGR Document in the SAP EWM System 30
5.2 Warehouse Management Monitor Handling 31

Typographic Conventions 33
Document History
Revision Change Date Description

0 March 5 2016 Published version

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 3
1 Test Description
This document describes the inbound processing of batch-managed products from a vendor.
In this process batch-managed products are put away into the high rack of the EWM Cross Industries Warehouse. To keep the process simple, we assume
batch-managed products are stored in the lower level bins of the storage so the handover point of the high rack is not used.
The use of handover points for this storage is shown in the business process documentation 1CP Inbound from Vendor to High Rack with Bin Sectioning.
There are two batch-managed products: EWM-20 for inbound testing and EWM-21 for outbound testing.
Both products are identical and work for both inbound as for outbound processes. Note that testing the business process documentation for the outbound
process is easier if you have your own product with a stable and predictable stock situation independent of other tester’s data.
Based on the classification of the product as "heavy parts", the system determines to directly route handling units into the storage type (Y031) representing
the High Rack with Pick Point storage.
For the putaway control of the products, the system uses the corresponding "Putaway Control Indicator" (PACI) representing heavy parts.
As in other inbound scenarios, parts with no PACI are routed to the Clarification Zone.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 4
2 Prerequisites

2.1 Master Data and Organizational Data

Default Values
The organizational structure and master data of your company was created in an S/4HANA system during implementation. The organizational structure
reflects the structure of an example company. The master data represents materials, customers, and vendors, for example, depending on the operational
focus of the demonstrated processes.
The business process is enabled with this organization-specific master data.
The example process uses the following master data in the process steps.

Product Master Data

We provide two identical products, but the description is only for the first one (EWM-20). The second one (EWM-21) works exactly in the same way. It is
useful, if you want to test outbound independently from inbound products: The tester of outbound products can create a stock situation for EWM-21 to their
needs.

Data Sample Value Details Comments

Product number EWM-20 EWM Prod.20,Heavy Part,Fast 1 PAL= 6 EA

Mov.,Batch EAN = 9781937585648 (EA)
Use this material for testing outbound directly
after inbound.

Product number EWM-21 EWM Prod.21,Heavy Part,Fast 1 PAL= 6 EA

Mov.,Batch EAN = 9781592294152 (EA)
Additional material for independent outbound
tests.

Packaging Material Master Data

Data Sample Value Details Comments

Packaging product EWM-PAL00 EWM Default Palette with SSCC Bin sectioning results in 3 sub-bins
number generation

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 5
Vendor Master Data

Data Sample Value Details Comments

Vendor EWM-VEND01 EWM Vendor 01 (Domestic)

Organizational Master Data in the SAP S/4HANA System

Data Sample Value Details Comments

Company Code ##10 ## represents country code, see
conversion table below

Purchasing ##10 ## represents country code, see

Organization conversion table below

Purchasing Group 001

Plant ##10 ## represents country code, see

conversion table below

Storage Location YROD Received on Dock

ERP Warehouse YN2

Number

Receiving Point ##10 ## represents country code, see

conversion table below

Organizational Master Data in the SAP EWM System

Data Sample Value Details Comments

Supply Chain Unit YWAREHOUSE-01

EWM Warehouse YER2

Number

Custodian PL##10 ## represents country code, see

conversion table below

Entitled to Dispose PL##10 ## represents country code, see

conversion table below

Goods Receipt Office YWAREHOUSE-01

## represents for the two-digit country code. Country codes ## naming conversion is as follows:

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 6
 Country ## Comments

DE 10 Germany

US 17 United States

CN 13 China

RU 16 Russia

BR 14 Brazil

Warehouse-Specific Master Data

Data Sample Value Details Comments

Storage Type Y002 High Rack Pick Point The Pick Point is not used in inbound processing

Storage Type Y003 Handover Point High Rack with Not used by the batch-managed products.
Pick Point

Storage Type Y031 High Rack (with Bin Sectioning,

Pick Point and Handover Point)

Storage Type Y910 Inbound Staging Area

Storage Type Y930 Doors

Storage Type Y970 Clarification Zone Not actively shown in this document

2.2 Business Conditions

The business process described in this Business Process Documentation is part of a larger chain of integrated business processes or scope items. As a result,
you must have completed the following processes and fulfilled the following business conditions before you can start any activities in this scope item:

Business Condition Comment

1 There is no specific business condition.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 7
2.3 Preliminary Steps

2.3.1 Creating User Settings for the Transaction /SCWM/GRPE

Use

In this step, you set up user settings that are necessary for transaction /SCWM/GRPE.

Procedure

1. Access the activity as follows:

Transaction Code /SCWM/GRPE

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse Management → Delivery Processing →
Inbound Delivery → GR Preparation – External Procurement
(SAP EWM)
2. In the Maintain Default Values dialog box, make the following entries:

Field Name Description User Action and Values Comment

Warehouse Number YER2

Goods Receipt Office YWAREHOUSE-01

Entitled to Dispose PL##10

TU Assignment today Other Assignment Period

Assgmt in Past (Hrs) Only relevant if TU is

used → not here

Future assgmt (Hrs) See above

Select Expected GR X

Sel. Inb. Deliveries X

Without TU X The inbound processing

does not use TUs

3. Choose Continue (Enter).

If the dialog box does not appear, you may choose Default Values (F5) and create or check the above entries.
4. Choose Continue.
Inbound of Batch-Managed Products from Vendor CUSTOMER
Document History Error: Reference source not found 8
5. Choose Exit.

2.3.2 Creating User Settings for the Transaction /SCWM/MON

Use

In this step, you set up user settings that are necessary for transaction /SCWM/MON.

Procedure

1. Access the activity as follows:

Transaction Code /SCWM/MON

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse Management → Monitoring → Warehouse
Management Monitor
(SAP EWM)
2. In the dialog box, make the following entries.

Field Name Description User Action and Values Comment

Warehouse Number YER2

Monitor YE01

3. Choose Execute (F8).

4. If the dialog box does not appear, you may choose Default Values (F5) and create or check the above entries.
5. Choose Execute.
6. Choose Exit.

2.3.3 Maintaining User (for RFUI Processing)

Use

With this setting you can assign your logon user to a resource used in the RF (Radio Frequency) processing. By doing this, you do not need to make entries in
the input fields in transaction /SCWM/RFUI every time you access the RF processing. You can easily change the resource if the process requires it.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 9
Procedure

1. Access the activity as follows:

Transaction Code /SCWM/USER

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse Management → Master Data → Resource
Management → Maintain Users
(SAP EWM)
2. In the “Display View “Users”: Overview screen, choose Change/Display Ctrl. F1 to switch to the edit mode.
3. On the “Change View “Users”: Overview screen, choose New Entries.
4. On the New Entries: Overview of Added Entries screen, enter the following data:

Field Name Description User Action and Values Comment

User <…>

Data Entry

Prsn.Prof. **

Warehouse Number YER2

Resource <Y…-#>

Auto Logon [ ]

Note
User: Choose your logon user.
Resource: Choose the resource you mainly use or the resource with which you usually start your processes. Apart from the process-step specific
resource documented in every process step, all RF-based process steps work with the “generic” YALL-1 resource.
5. Choose Save.
6. Choose Exit.

2.3.4 Checking/Closing Period for Material Master Records

Use

To make sure that stock postings replicated back from the EWM system to the S/4HANA system you need to make sure that the current period is set.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 10
Procedure

1. Access the activity as follows:

Transaction Code MMPV

Easy Access Menu Logistics → Materials Management → Material Master → Other → Close Period
(SAP S/4HANA)
2. On the Close Period for Material Master Records screen, enter:

Field Name Description User Action and Values Comment

From company code ##10

Date <Current Date> Open the input

help and choose
Continue.

Check period only [X]

3. Choose Execute
4. On the Close Period for Material Master Records screen, read the log:
The current period (month/year) of the control record is <072015> (for example).
5. Note that period, for example: Period 07, Fiscal year 2015.
6. Choose Back.
7. On the Close Period for Material Master Records screen, enter:

Field Name Description User Action and Values Comment

From company code ##10

To company code ##10

Period <required month> The next period after the actual system
period,
for example, 07 + 1 = 08

Fiscal year <required month> The current system fiscal year.

Date Delete the content

Check and close period [X]

8. Choose Execute.
9. Confirm the following system message: The specified year #### is not the current calendar year.
10. The log should display the new system period:

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 11
11.
Period entered (month/year):<xx xxxx>
Company code <##10> converted
Period closing complete; log issued.
12.
Now the system period has been updated, for example, to period 04.
13. Choose Back.
14. Repeat steps 8 to 11 until all old periods are closed.
The new system period should be the current month of the current year.
15. Choose Back.
16. Choose Exit.

Result

The system period is up-to date. Logistic postings go to the current period.

2.3.5 Create User Settings for Transaction ME21N

Procedure

1. Access the activity as follows:

Transaction Code ME21N

Easy Access Menu Logistics → Materials Management → Purchasing → Purchase

Order → Create → Vendor/Supplying Plant Known
(SAP S/4HANA)

2. On the Create Purchase Order screen, below the Item Overview table, choose Default Values. (If there is no Item Overview table, choose Expand
Items.)
3. In the Item Default Values dialog box, enter:

Field Name Description User Action and Values Comment

Plant ##10

Always Propose [X] In the same row as "Plant"

Storage Location YROD

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 12
 Field Name Description User Action and Values Comment
Always Propose [X] In the same row as "Storage Location"

4. Choose Save.
5. Back on the Create Purchase Order screen, choose Exit.
If the following system message appears: Do you want to save the document first?, choose No.

2.4 Template for ID Sheet

Use

In order to facilitate working through the process steps, you can print the following table and note down all IDs you create:

Object Value

Purchase Order to Vendor

4.1 Purchase Order ID 450000 _ _ _ _

Inbound Delivery
4.3 ASN Number/Vendor’s Delivery Note ASN-45- _ _ _ _

4.3 Inbound Delivery ID (EWM) _ _ _

Handling Units
4.4 Handling Unit ID (Internal numbering) of the 11234567800000 _ _ _ _
1st delivery item

4.4 Handling Unit ID (Internal numbering) of the 11234567800000 _ _ _ _

2nd delivery item

4.4 Handling Unit ID (Internal numbering) of the 11234567800000 _ _ _ _

3rd delivery item

Note
You can also use the Warehouse Management Monitor to find the HU IDs. See chapter "5.2 Warehouse Management Monitor Handling" in the
Appendix.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 13
3 Overview Table
The steps in the system, especially the transaction codes with additional explanations are listed below:

Process Step Business Condition Business Role Transaction Expected Results

Create a purchase Goods in insufficient Purchaser ME21N Purchase order created and distributed to Vendor.
order quantity have to be
(S/4HANA System) purchased

Maintenance of Purchaser /SPE/EGR An EGR is created in the SAP EWM system.

expected goods
receipt (EGR)

Create an inbound The GR clerk finds the Receiving Office /SCWM/GRPE The inbound delivery is created with reference to the EGR.
delivery with corresponding EGR in
reference to EGR the system and creates
(EWM System) Inbound delivery with
reference to it.

Processing the The goods are Warehouse Worker /SCWM/RFUI The goods receipt is posted by function "Receiving of Handling
goods receipt delivered to the Units by ASN".
warehouse and HUs are created for the delivery items. Therefore, the user enters
unloading is done with a HU ID (from preprinted labels) and the packaging material. The
no system support. quantity is entered during goods receipt.
Goods receipt is then booked and distributed to S/4HANA.

Display and check Warehouse Manager /SCWM/MON Check the WO assignment to Inbound RF queues.
warehouse orders
(WOs)

Put away products to Goods are received and Warehouse Worker /SCWM/RFUI Putaway WTs are confirmed in RF and System Guidance by Queue
the high rack reside at the inbound is used for putaway.
storage (lower staging area.
Levels)

Check the Inbound All process steps of the Warehouse Manager VL33N All inbound delivery items should have been updated documenting
Delivery in the inbound processing are a correct stock posting situation.
S/4HANA system completed In addition, you can check the stock situation with transaction
MMBE.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 14
4 Test Procedures

4.1 Create a Purchase Order

Procedure

1. Access the activity as follows:

Transaction Code ME21N

Easy Access Menu Logistics → Materials Management → Purchasing → Purchase

Order → Create → Vendor/Supplying Plant Known
(SAP S/4HANA)
2. On the Create Purchase Order screen, enter:

Field Name Description User Action and Values Comment

Order Type NB Standard PO Default (drop-down near Shopping Cart)

Vendor EWM-VEND01

Doc.date <Current date> Default

If there are no tabs at all, choose Expand Header.

3. On the Org. Data tab, enter:

Field Name Description User Action and Values Comment

Purch. Org. ##10

Purch. Group 002 Purchase order with purchase group 002 is

not required to go through release
procedure.

Company Code ##10

If there is no Item Overview table on the Org. Data tab, choose Expand Items.
4. Enter three identical items, as we want three separate items in the SAP EWM system:

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 15
 Material PO OUn Deliv. Date Plant Stor. Comment
Quantity Location
EWM-20 6 EA <Default: Next ##10 YROD In EWM, the country of
working day.> origin will be USA (US) for
the first item.
EWM-20 6 EA <Default: Next ##10 YROD In EWM, the country of
working day.> origin will be Germany
(DE) for the second item.
EWM-20 6 EA <Default: Next ##10 YROD In EWM, the country of
working day.> origin will be Antarctica
(AQ) for the third item.

5. Choose Enter.
6. If you receive message Can delivery date be met?, choose Enter for each item (three times).
7. If you receive message The effective price is <...>, the material price is <…>, choose Enter.
8. All items are automatically completed:

Field Name Description User Action and Values Comment

Status Yellow status works fine.

Itm 10 Items 20 and 30 are identical.

Material EWM-20

Short Text WM Prod.20,Heavy Part,Fast

Mov.,Batch

PO Quantity 6

OUn EA

C D

Deliv. Date <Date> Next working day, e.g. 14.07.2015.

Net Price 1,350.00

Currency USD

Per 100

OPU EA

Matl Group Material group 1

Plnt Plant 1 Text of ##10

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 16
 Field Name Description User Action and Values Comment
Stor. Location EWM Rec. on Dock Text of YROD

Info Rec. <53000000XX> Your info record ID.

9. Choose Save.
10. On the dialog box "System messages issued Do you want to save document or process data?", choose Save.
11. You receive message Standard PO created under the number <4500000XXX>
Take a note of the Purchase Order on the ID sheet.
12. Choose Exit.

Result

The purchase order has been created.

4.2 Maintenance of Expected Goods Receipt

Use

In this process, the expected goods receipt functionality is used for PO based creation of inbound deliveries in EWM. The EGR is created in the SAP S/4HANA
system.

Note
Alternatively, the EGR document can be created in the SAP EWM system. If you choose to do so, refer to chapter "5.1 Create EGR Document in the
SAP EWM System" in the Appendix.
In productive systems, this job is scheduled as a background job. For more information, see the Solution Operation Guide for SAP EWM in the SAP
Help Portal.

Procedure

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

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 17
 Transaction Code /SPE/EGR

Easy Access Menu Logistics → Logistics Execution → Inbound Process → Goods

Receipt For Inbound Delivery → Extended Inbound Delivery
(SAP EWM)
Processing → Subsequent Functions → Maintenance Of
Expected Goods Receipt

2. On the Maintenance of Expected Goods Receipt screen, in the EWM parameters section, enter the following data:

Field Name Description User Action and Values Comment

Warehouse Number YN2

Create Expected Goods X To update the EGR, choose Update

Receipts Expected Goods Receipt.

Test mode X For the first time, run this transaction in

Test Mode.

3. In the Delivery Date/ Scheduled Finish Date Time Range section enter the following data:

Field Name Description User Action and Values Comment

Start Date / Time <Delivery date or earlier Date that is before or equal to the delivery
day> date in the PO items

End Date / Time <Delivery date or later Date that is after or equal to the delivery
day> date in the PO items

4. In the Selection area for PO/SA section, enter the following values:

Field Name Description User Action and Values Comment

Purchasing Document <Purchase Order Number> To create an EGR document, you need to
refer to the PO created in previous step.
Ideally, simply take the PO of your test
example.

Activate PO/SA [X]

selection

5. Choose Execute.
6. On the Messages screen, check that everything is OK. The first row should be: The number of the error free EGR doc. for PO or SA is 1
7. Choose Back.
8. On the Maintenance of Expected Goods Receipt screen, in the EWM parameters section, enter the following data:

Field Name Description User Action and Values Comment

Test mode Remove the Test mode check.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 18
9. Choose Execute.
10. Confirm the following system message: Check that the EGR documents from previous runs are deleted.

Note
In a productive system environment, there is usually a background job continuously creating EGR in the connected EWM system.
11. Choose Back.
12. Choose Exit.

Result

The SAP S/4HANA system selects the Purchase Orders and initiates the creation of the EGR document in the connected SAP EWM based on the purchase
order data.

4.3 Create an Inbound Delivery with Reference to EGR

Use

Upon arrival of the goods, an employee of the Receiving Office searches for Advanced Shipping Notification (ASN) data which might have been transferred
electronically (B2B or EDI communication) by the vendor. The main reference for this search is the vendor’s delivery note number which is printed on the
physical delivery note.
If no ASN data exists in the EWM system which could directly be used for the EWM inbound delivery document, the EWM inbound delivery is now created with
reference to the EGR information.

Prerequisites

EGR documents based on the S/4HANA purchase orders exist in your EWM system.

Procedure

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

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 19
 Transaction Code /SCWM/GRPE

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse

Management → Delivery Processing → Inbound Delivery → GR
(SAP EWM)
Preparation – External Procurement

2. On the GR Preparation: External Procurement (Warehouse No. YER2) screen, in the Search Requests section, enter the following data:

Field Name Description User Action and Values Comment

Find REFDOCNO_PO_I Purchase <45########> Enter the purchase order number.
Order

3. Choose Execute Search.

The system displays the three purchase orders in the left screen area.
4. Choose Select All.
5. Choose Copying Flag. The selected EGR items are flagged for copying.
6. Choose Copy Flagged Items.
7. In the GR Preparation: External Procurement (Warehouse No.YER2) dialog box, enter:

Field Name Description User Action and Values Comment

ASN <ASN-45-####> In this example, we use prefix "ASN-45-"
and add the last four digits of the
corresponding Purchase Order ID. This way,
the ASN is unique.

8. Note the ASN on the ID sheet.

9. Choose Continue.
10. Confirm the following system message: Product <EWM-20> subject to batch management requirement.
11. Back on the GR Preparation: External Procurement (Warehouse No. YER2) screen, the EGR item has been copied to the table of inbound delivery items in
the lower right screen area.
12. In the table of inbound delivery items, choose Select All.
13. Choose Switch to Form View.
14. In the Inbound Delivery Item section, check that you are working on Item 10:
15. In the Product and Shipping Conditions section, check the following data (or enter the data if not filled already):

Field Name Description User Action and Values Comment

Quantity 6 EA

Batch

Count. of Orig. US

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 20
 Field Name Description User Action and Values Comment
Expiration

Remark: Enter US as country of origin, if not already prefilled by the system.

16. Choose Move Line Downwards.

17. Confirm the following system message: Product <EWM-20> subject to batch management requirement.
18. In the Inbound Delivery Item section, check that you are working on Item 20:
19. In the Inbound Delivery Item section, in the Product and Shipping Conditions section, enter the following data:

Field Name Description User Action and Values Comment

Quantity 6 EA

Batch

Count. of Orig. DE

Expiration

20. Choose Move Line Downwards.

21. I Confirm the following system message: Product <EWM-20> subject to batch management requirement.
22. In the Inbound Delivery Item section, check that you are working on Item 30:
23. In the Inbound Delivery Item section, in the Product and Shipping Conditions section, enter the following data:

Field Name Description User Action and Values Comment

Quantity 6 EA

Batch

Count. of Orig. AQ

Expiration

24. Optional: In the Transaction Data section, check the following settings (for each of the items):

Field Name Description User Action and Values Comment

Whse Proc. Type Y114 Putaway In One Step

Goods Mvt Bin GR-YDI1

25. Choose Save.

You receive the following system message: Inbound Delivery <###> created
26. Take a note of the ID of the Inbound Delivery (EWM) on the ID sheet.
27. Choose Exit.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 21
Result

You have created the inbound delivery in the SAP EWM system based on an EGR document and the system replicated it back to the SAP S/4HANA system.
You can check the inbound delivery created in the SAP S/4HANA system in transaction VL33n. Use the selection option “External delivery number of vendor”
and search via the ASN number you have entered above.

4.4 Process the Goods Receipt

Use

The warehouse operators at the inbound staging area are equipped with:
 an RF / mobile data entry device
 a roll of pre-printed and barcoded HU labels
They are responsible for labeling and – if necessary – for repacking the items (in real life but not supported by system functions), then posting goods receipt
and creating subsequent putaway warehouse tasks in the system.

Procedure

1. Access the transaction using the following navigation options:

Transaction Code /SCWM/RFUI

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse

Management → Execution → Log On To RF Environment
(SAP EWM)
2. On the SAP screen, make the following entries:

Field Name Description User Action and Values Comment

Whse No Warehouse Number YER2

Resource YREC-1

DefPresDvc Presentation device YE00

3. Choose Enter.
4. Choose 03 Inbound Processes → 04 Receiving of Handling Units → 04 Rec. HU by ASN.
5. On the SAP screen, make the following entries:

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 22
 Field Name Description User Action and Values Comment
ASN <ASN-45-####> ASN number from chapter 4.3.

6. Choose Enter. The Delivery ID <####> is displayed.

7. Choose Enter.
8. Choose F2 NewHU.
9. On the SAP screen, make the following entries:

Field Name Description User Action and Values Comment

Prod. EWM-20 Alternatively, instead of the product ID, you
could enter the EAN number
9781937585648.

10. Choose Enter after you have entered the EAN or product ID before you enter the other fields (a real mobile device would do this automatically):

Field Name Description User Action and Values Comment

ActQty 6

UoM EA Right to the ActQty field.

Batch <Batch ID> Assign a batch ID beginning with a letter.

For example, B2015/06 -"B" and
<Year>/<Month> of the best before date
(field below). In a real-life situation, the ID
could come from another rule or a coil of
numbered labels.

BBD <Date> <Date > = Current date plus twelve

months. e.g. 06/20/2016
In a real-life situation, it would be on the
product. The RF UI only accepts this date
format independent of your user settings.

Note
If your assigned batch ID already exists for this product, the BBD you have entered has to match the BBD of the batch. Also, the country of origin of
the delivery item has to match the origin of an existing batch.
If the batch ID you have entered does not exist for your product, it will be created after the next step. The origin is copied from the delivery item; the
BBD is taken from your input in the BBD field.

Note
To avoid conflicts with existing batches during testing, shift the BBD one month to the future for each received item.
11. Choose F1 Next.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 23
12. Enter the packaging material:

Field Name Description User Action and Values Comment

New P.Mat. EWM-PAL00 The packaging material’s HU Type (YN01)
leads (storage type Y031) to a bin
sectioning with 3 sub-bins in the High Rack.

13. Choose Enter.

14. Note the HU on the ID sheet.
15. Choose Enter.
16. Choose F2 PGr.The Goods Receipt is now posted:

Field Name Description User Action and Values Comment

Unloaded [X] Automatic Selection Because Of Goods
Receipt.

GR Posted [X] Automatic Selection Because Of Goods

Receipt.

17. Press key F3 CrWT. The Putaway Warehouse Task is created:

Field Name Description User Action and Values Comment

WT Created [X] Automatic Selection Because Of WT
Creation.

Note
You could continue directly with the warehouse task confirmation dialog using F4 Conf, but in this example process, the assumption is that this is
done separately in the next process step by another warehouse operator/resource.
18. Press key F7 to go back to the HU Creation.
19. Repeat Step 8 to 18 for the second and third delivery item.
20. Press key F7 to go back to the delivery display.
Press key F7 to go back to the ASN selection.
Press key F7 to go back to the button menu.
21. Press key F1 to log off.
Press key F1 to save.

Result

All three items have been packed (HU created), unloaded and received (GR posted).

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 24
4.5 Check Physical Stock

Use

At this point of time, all HU are physically located in the GR zone / inbound staging area. You can display this status.

Procedure

1. Access the activity using one of the following navigation options:

Transaction Code /SCWM/MON

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse

Management → Monitoring → Warehouse Management Monitor
(SAP EWM)
2. In Warehouse Management Monitor dialog box, enter:

Field Name Description User Action and Values Comment

Warehouse Number <Warehouse number> For example, YER2

Monitor YE01 Specialized Monitor for the RDS package;

copied and adapted from SAP Standard
Monitor

3. Choose Execute.
4. On the Warehouse Management Monitor YE01 - Warehouse Number YER2 screen, double-click folder Stock and Bin and double-click folder Physical
Stock
5. In the dialog box, enter the following data:

Field Name Description User Action and Values Comment

Product EWM-20

Stock Type F1

Look for the three HU IDs and check the following data:

Field Name Description User Action and Values Comment

Storage Bin GR-YDI# A bin in the inbound staging area

Batch <...> Your batch ID

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 25
 Field Name Description User Action and Values Comment
Description of Stock Unrestricted-Use in Putaway The putaway is in progress.
Type

4.6 Check Warehouse Orders

Use

At this stage of the process, the Goods Receipt has been posted and the warehouse orders and tasks have been created to move Handling Units to the High
Rack’s lower level bins.
A supervisor may check the destinations of the HUs for an overview of the open workload.

Procedure

For details, refer to chapter "5.2 Warehouse Management Monitor Handling" in the appendix.

4.7 Putaway Products to the High Rack Storage (Lower Levels)

Use

An operator with an RF device picks up the HU from the GR zone and directly moves them to a bin in the lower levels (01 or 02) of the High Rack as the
section indicator of products EWM-20 and EWM-21 sends them there.
The corresponding RF queues are YI-910-HL3 and YI-910-HL4.
We assume that the low-level truck driver scans a random HU in the inbound staging area and puts it away in the lower levels of the storage until there are
no more HU in the inbound staging area.

Procedure

1. Access the transaction using the following navigation options:

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 26
 Transaction Code /SCWM/RFUI

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse

Management → Execution → Log On To RF Environment
(SAP EWM)
2. On the SAP screen, make the following entries:

Field Name Description User Action and Values Comment

Whse No Warehouse Number YER2

Resource YLLTR-1 Low-level truck

DefPresDvc Presentation device YE00 Default RF device

3. Choose Enter.
4. Choose 03 Inbound Processes → 03 Putaway → 01 Putaway by HU.

Note
Alternatively, you could use 01 System Guided → 02 System-guided by Queue and search for open warehouse tasks in RF queues YI-910-HL3 and YI-
910-HL4.
5. On the SAP screen, enter the following data:

Field Name Description User Action and Values Comment

HU 112345678######### HU number from ID sheet.

6. Choose Enter.
7. On the SAP screen, copy the Storage Bin into the Verification field:

Field Name Description User Action and Values Comment

DstBin <031.##.##.##/a,B,C>

Storage Type Y031

Storage Section YS01

Verification Field <031.##.##.##/a,B,C>

8. Choose Enter.
9. Press key F7 to go back.
10. Repeat steps 7 to 9 for the second and third HU.
11. Press key F1 to log off.
Press key F1 to save.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 27
Result

The warehouse tasks for moving HUs with product EWM-20 from the goods receipt area to the final storage bin are now confirmed in the system.
The system automatically changes the stock type for this stock from "Unrestricted-Use in Putaway" (F1) to "Unrestricted-Use Warehouse" (F2).

4.8 Check the Inbound Delivery in the SAP S/4HANA System

Use

In this step, you check the (S/4HANA) inbound deliveries which have got a "Goods Receipt" posting.

Procedure

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

Transaction Code VL33N

Easy Access Menu Logistics → Logistics Execution → Inbound Process → Goods

Receipt For Inbound Delivery → Inbound Delivery → Display →
(SAP S/4HANA)
Single Document

2. On the Display Inbound Delivery screen, press F4 (Matchcode Search).

3. In the Delivery (1) dialog box, on External delivery number of vendor tab, enter the following:

Field Name Description User Action and Values Comment

External Delivery ID < ASN # > Enter the ASN/Vendor Delivery Note ID you
entered in section 4.3 Create an Inbound
Delivery with Reference to EGR

4. Choose Start Search.

The system displays your inbound delivery.
5. Double-click the inbound delivery.
6. On the Display Inbound Delivery screen, choose Enter.
7. On the Inbound Delivery <...> Display: Overview screen, on the Status Overview tab, in the Overall Status - Delivery section, check the following data:

Field Name Description User Action and Values Comment

GM Total Goods Movement Status C

8. In the Delivery Item Status (All Items) section, check the following data:
Inbound of Batch-Managed Products from Vendor CUSTOMER
Document History Error: Reference source not found 28
 Field Name Description User Action and Values Comment
GS Goods Movement Status (Item) C

Note
You can also check the stock in the S/4HANA system using transaction MMBE:

Field Name Description User Action and Values Comment

Material EWM-20

Plant ##10

Storage Location YAFS

For batch-managed products, the stock overview shows stock data for each batch ID individually.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 29
5 Appendix

5.1 Create EGR Document in the SAP EWM System

Use

The expected goods receipt functionality is used for PO-based creation of inbound deliveries in EWM. The EGR creation can be initiated in the SAP EWM
system by the below described procedure.

Procedure

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

Transaction Code /SCWM/ERP_EGR_DELETE

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse

Management → Delivery Processing → Inbound Delivery →
(SAP EWM)
Expected Goods Receipt → Generate Or Delete Expected Goods
Receipt

2. On the Deletion/Creation of Expected Goods Receipt screen, make the following entries:

Field Name Description User Action and Values Comment

ERP Warehouse Number <ERP Warehouse Number> For example, YN2

Purchase Order <Purchase order number> To create an EGR document, you need to
refer to an existing purchasing document.

Free Interval X

Selection Time Period <date, time> to <date, Make sure the delivery date in the PO lies
time> within the period.

Program Mode Delete and Create

3. Choose Execute.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 30
Result

You have created an EGR document in the EWM system with which you can create an inbound delivery document.

5.2 Warehouse Management Monitor Handling

Use

The Warehouse Management Monitor is a central tool for the management staff in the warehouse to stay up-to-date with the current situation in the
warehouse. It provides a wide range of queues with which historical and current data can be displayed. Within the monitor, it is also easy to navigate to
transactions, assign tasks and warehouse resources and so on.
In this example, you search for the HU numbers, Warehouse Order and Warehouse task numbers specific to an inbound delivery in the Warehouse
Management Monitor to facilitate the goods receipt and putaway warehouse task execution in the RF environment.

Procedure

1. Access the activity using one of the following navigation options:

Transaction Code /SCWM/MON

Easy Access Menu SCM Extended Warehouse Management → Extended Warehouse

Management → Monitoring → Warehouse Management Monitor
(SAP EWM)
2. In the dialog box, make the following entries:

Field Name Description User Action and Values Comment

Warehouse Number <Warehouse number> For example, YER2

Monitor YE01 Specialized Monitor for this solution

package; copied and adapted from the SAP
Standard Monitor

3. In the hierarchy in the left screen area, choose Inbound → Documents → Inbound Delivery.
A dialog box appears.
4. In the dialog box, enter the inbound delivery number and choose Execute.
The system displays the inbound delivery in the right screen area.
5. Select the inbound delivery, and choose Warehouse Order.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 31
 The system displays the corresponding WO numbers to this inbound delivery document. If you choose the WO number, you navigate to the Warehouse
Order display screen with further detailed information, such as the Warehouse Tasks that are contained in the Warehouse Order, the source & destination
HU numbers and so on.
6. Choose Warehouse Task to display the WTs associated with the inbound delivery.
7. Choose Handling Unit to display the HUs associated with the inbound delivery.

Result

In the Warehouse Monitor, a user can display all relevant data (for example, warehouse orders, warehouse tasks, HUs and so on) linked to a particular
inbound delivery This is an efficient way to monitor the progress of the related process.

Inbound of Batch-Managed Products from Vendor CUSTOMER

Document History Error: Reference source not found 32
Typographic Conventions
Type Description
Style

Example Words or characters quoted from the screen. These include field names, screen titles,
www.sap.com/contactsap
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

© 2015 SAP SE or an SAP affiliate company. All rights
EXAMPLE Technical names of system objects. These include report names, program names, transaction reserved.
codes, table names, and key concepts of a programming language when they are surrounded No part of this publication may be reproduced or transmitted
by body text, for example, SELECT and INCLUDE. in any form or for any purpose without the express
permission of SAP SE or an SAP affiliate company.
Example Output on the screen. This includes file and directory names and their paths, messages, names SAP and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered
of variables and parameters, source text, and names of installation, upgrade and database
trademarks of SAP SE (or an SAP affiliate company) in
tools. Germany and other countries. Please see
http://global.sap.com/corporate-en/legal/copyright/index.epx
Example Exact user entry. These are words or characters that you enter in the system exactly as they #trademark for additional trademark information and notices.
appear in the documentation. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other
<Example Variable user entry. Angle brackets indicate that you replace these words and characters with software vendors.
> National product specifications may vary.
appropriate entries to make entries in the system.
These materials are provided by SAP SE or an SAP affiliate
company for informational purposes only, without
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP SE
or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no
obligation to pursue any course of business outlined in this
document or any related presentation, or to develop or
release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments,
products, and/or platform directions and functionality are all
subject to change and may be changed by SAP SE or its
affiliated companies at any time for any reason without
notice. The information in this document is not a
commitment, promise, or legal obligation to deliver any
material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that
could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue
reliance on these forward-looking statements, which speak
Inbound of Batch-Managed Products from Vendor only as of their dates, and they should notCUSTOMER
be relied upon in
Document History making purchasing Error: Reference source not found
decisions. 33