Basic Settings For SAP EWM in SAP S - 4HANA 1709 - SAP Blogs

12/28/2018 Basic Settings for SAP EWM in SAP S/4HANA 1709 | SAP Blogs
Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner
About
About
Ask a Question Write a Blog Post
Former Member
January 8, 2018 13 minute read
Basic Settings for SAP EWM in SAP S/4HANA 1709
Follow RSS feed
10 Likes 12,251 Views 13 Comments
Use Cases
1. If you use a SAP S/4HANA 1709 or 1610 system with Best Practice activated but without using the SAP
EWM in S/4HANA, and you want to add the Best Practice for the SAP EWM in SAP S/4HANA to an
existing plant, this blog lists all the required Best Practice Org data and guides you to expedite the Basic
Settings process so that you don’t need to research for the input data.
2. If you use a SAP S/4HANA 1709 or 1610 system, and you want to add the SAP EWM in SAP S/4HANA
to a new or an existing plant, you replace the Best Practice Org Structure in this blog with your own and
complete the basic settings by following the example.
https://blogs.sap.com/2018/01/08/basic-settings-for-sap-ewm-in-sap-s4hana-1709/ 1/31
1 Basic Settings for SAP EWM in SAP

S/4HANA
SAP provides a copy of “Getting Started Guide – Basic Settings for SAP EWM in SAP S/4HANA” in the
attachment of SAP Note 2494704 – SAP S/4HANA 1709: Release information and restrictions for EWM in
SAP S/4HANA, and SAP Note 2347770 –
SAP S/4HANA 1610: Release information and restrictions for EWM in SAP S/4HANA. Both SAP Notes
have the same version of le “BasicSettings_EWMinS4_V01.pdf”.
This blog provides step-by-step screenshots based on the guide and the Best Practice Org structure.
SAP EWM in SAP S/4HANA Best Practices

SAP EWM in SAP S/4HANA provides the following 11 scope items in the Best Practice content, and this blog
shows the basic settings needed for these Best Practices. For each scope item, more functional related
con gurations are needed. Refer to the Prerequisites Matrix for the required Building Blocks for each scope
item.
EWM Scope Item Delivered License

in
1FS: Basic Warehouse Inbound Processing from Supplier 1610 Basic
1FU: Initial Stock Upload for Warehouse 1610 Basic
1FW: Physical Inventory in Warehouse 1610 Basic
1FY: Replenishment in Warehouse 1610 Basic
1G0: Scrapping in Warehouse 1610 Basic
1G2: Basic Warehouse Outbound Processing to Customer 1610 Basic
1V5: Warehouse Inbound Processing from Supplier with Batch Management 1709 Basic
1V7: Warehouse Outbound Processing to Customer with Batch Management 1709 Basic
1V9: Basic Warehouse Inbound Processing from Supplier with Quality 1709 Basic
Management
1VB: Production Integration – Component Consumption and Receipt in 1709 Basic

Warehouse
1VD: Advanced Warehouse Outbound Processing to Customer 1709 Advanced
NOTE:
For easy cross reference, the following paragraphs use the same paragraph numbers as in
the BasicSettings_EWMinS4_V01.pdf le.
2 Con guration of qRFC Communication

2.1 Background Information About System
Landscape Settings
The system landscape entities in the following table is based on a single SAP S/4HANA sandbox system,
which has system ID BES and Client 300. If you need to setup the system landscape for a distributed
system landscape, e.g., with customizing, test, and production system, see Section 2.1 in the guide pdf le.
System Landscape Entity Example Comments
RFC Destination BESCLNT300 Exists in your SAP S/4HANA system

already, see Section 2.2 below
Logical Systems BESCLNT300 Exists in your SAP S/4HANA system and

assigned to Client 300 already
Dummy Logical System BESEWM300 To be created by the Implementation Tool

for System Connection, see Section 2.4.
Business System Group BG1 BG1 To be created by the Implementation Tool

Business System S4H_001 BES_300 To be created by the Implementation Tool

2.2 Technical Prerequisites for qRFC

Communication
The RFC Destination and RFC Connection BESCLNT300 should be in the existing SAP S/4HANA system
already. You need to test the RFC Connection to con rm that the connection is working via transaction
SM59 by clicking on the Connection Test button.
2.3 Creating Dummy Logical System Manually

The Dummy Logical System for EWM will be created automatically by the “Implementation Tool for
System Connection” in Section 2.4.
2.4 Con guring qRFC Communication and Client

Settings
You use this procedure to con gure the following data with the help of the “Implementation Tool for
System Connection” in SAP EWM in SAP S/4HANA:
· System landscape settings for qRFC communication.

· Basic number ranges (on client level) in SAP EWM including packaging speci cations and shipping
and receiving activities
· Warehouse-independent basic settings using BC Set activation within the tool
You follow the following steps to use the “Implementation Tool for System Connection”.
1. In Customizing for Extended Warehouse Management, choose Interfaces → ERP Integration → Tool-
Based ERP Integration → Implementation Tool for System Connection, click on the IMG node execution
icon.
2. The following pop-up window opens.
3. Select “Display Quick Help” to display input eld information.
4. Enter a Data Set name and its Description. The system uses the name of the data set to store your
data input.
5. Select an existing transport Request/Task or create a new one to store all the con gurations made
during the Activation step.
6. Click on the “Next >” button to go to Step 2 “Use Cases”, and select the “Con guration EWM in the
current system” radio button.
7. Click on the “Next >” button to go to Step 3 “System Settings”, review the system proposed entries,
and enter new values if the elds are blank.
8. Click on the “Next >” button to go to Step 4 “Number Ranges”, if you need to setup your own number
ranges, select “Skip creation of number ranges”.
The number ranges will be created by the system in this blog.
9. Click on the “Next >” button to go to Step 5 “Activation”. Enter the Request/Task, and click on
“Activate” button. You could export the details of the activation content by clicking the Export button.
10. The activation is executed in the background.
11. Click on the “Next >” button to go to Step 6 “Activation Logs” after the completion of Activation.
Check the logs for any error messages. The same log could be found in transaction SLG1 under object
/SCWM/WME and sub-object IMPL_TOOL.
12. You have successfully executed the Implementation Tool for System Connection.
3 Warehouse Creation and Integration

into the Enterprise Structure
3.1 Background Information About Warehouse
Integration
The Best Practices for US Localization version for SAP EWM in SAP S/4HANA requires the following org
structure. For other country localization, replace the 17 pre x by your country number. For example, instead
of Plant 1710 for US, use 1010 for Germany, 2910 for Canada, 1310 for China, 3010 for Australia, etc.
Org. Master Data Value Master Data Description Comments
Company Code 1710 Company Code 1710 S/4HANA Object
Purchasing Organization 1710 Purch. Org. 1710 S/4HANA Object
Plant 1710 Plant 1 US (or your S/4HANA Object

description)
Storage Location 171D EWM ROD S/4HANA Object
Storage Location 171S EWM AFS S/4HANA Object
Org. Master Data Value Master Data Description Comments
ERP Warehouse Number 171 171 WM Warehouse for EWM S/4HANA Object
(or your description)
Receiving Point 1710 Shipping Point 1710 S/4HANA Object
Supply Chain Unit YWAREHOUSE- SCU Warehouse 1710 EWM Speci c

1710 Objects in
S/4HANA
EWM Warehouse Number 1710 EWM 1710 EWM Speci c

Objects in
S/4HANA
Custodian BP1710 BP1710 S/4HANA Object
Entitled to Dispose BP1710 BP1710 S/4HANA Object
Goods Receipt O ce YWAREHOUSE- SCU for Warehouse 1710 EWM Speci c

1710 Objects in
S/4HANA
Shipping O ce YWAREHOUSE- SCU for Warehouse 1710 EWM Speci c

1710 Objects in
S/4HANA
3.2 Prerequisites for Warehouse Integration

Plant 1710 should have been already created in your system and an active material ledger for the valuation
area has been assigned to Plant 1710.
If your plant doesn’t exist, create it and set active material ledger for your plant, see Section 3.2 in
le “BasicSettings_EWMinS4_V01.pdf”.
You have to perform the following manual con guration before you could use the automated con guration
tool in Section 3.4.
1. Create storage locations 171D and 171S in plant 1710.

Customizing Path:
Enterprise Structure → De nition → Materials Management → Maintain storage location.
2. Create a business partner BP1710 with prede ned roles FLCU00 (FI Customer) and FLCU01
(Customer)Transaction BP
Select create Organization icon, and enter name, Country, Language, and Save
To add the FLCU00 BP role under the change mode, select the FLCU00 BP role, enter address, and Save.
To add the FLCU01 BP role, under Change mode, select the FLCU01 BP role and save.
You need to link the customer BP1710 to Plant 1710 via Customizing Path:

Materials Management → Purchasing → Purchase Order → Set up Stock Transport Order → De ne
Shipping Data for Plants.
Enter BP1710 in the Customer No. – Plant eld.
3. Add FLVN00 (FI Vendor) and FLVN01 (Vendor) to BP1710

Use transaction Code BP to change BP1710.
Add FLVN00 BP role to Business Partner BP1710, and save.
Add FLVN01 BP role to Business Partner BP1710, and save.
You need to link BP1710 as the supplier to Plant 1710.

In the BP transaction change mode, select the FLVN01 Supplier role, under the “Vendor – General Data”
tab, enter plant 1710 in the Additional General Data section.
The customizing for shipping point/goods receiving point assignment, posting period settings, and cost
center assignment, see Section 3.2 Page 11 in the document “BasicSettings_EWMinS4_V01.pdf”, have been
set in the SAP S/4HANA con guration already.
3.3 Creating Organizational Units for the Warehouse

You need to make the following con guration in SAP S/4HANA.
1. De ne a warehouse on the SAP S/4HANA side (WM warehouse)

Customizing Path:
Enterprise Structure → choose De nition → Logistics Execution → De ne,
copy, delete, check warehouse number, and choose the activity De ne warehouse
number.
Click on “New Entries” to add the warehouse 171.
NOTE: Do not use copy warehouse function.
Click New Entries and enter

WhN: 171
Warehouse no. description: 171 WM warehouse for EWM
2. Assign the warehouse 171 to the plant 1710 and storage locations 171D and 171C
Customizing Path:
Enterprise Structure → Assignment → Logistics Execution → Assign warehouse number to plant/storage
location.
Click on New Entries and make the following assignments.
3. Maintain EWM-speci c parameters for the warehouse

Customizing Path:
Logistics Execution → Extended Warehouse Management Integration → Basic Setup of Connectivity →
Con gure SAP EWM Speci c Parameters.
Enter
Ext. WM: E (ERP with Extended Warehouse Management)
Comm. WM: Q (Queued and Serialized Asynchronous RFC)
Dist. Mode: Distribution Immediately at Document Creation
3.4 Creating and Integrating a SAP EWM Warehouse

SAP provides the “Implementation Tool for Warehouse Integration” to con gure the following objects in SAP
EWM in SAP S/4HANA for you:
· SAP EWM warehouse de nition and assignment to the Logistics Execution warehouse
· Supply chain unit (SCU) of the warehouse, which is also used as shipping o ce and receiving o ce
· Assignment of Custodian, Parties Entitled to Dispose (Plants), and Default Party Entitled to Dispose
(optional) to the SAP EWM warehouse:
· Assignment of SAP EWM stock types to the corresponding plants and storage locations by means
of availability groups
· Warehouse-dependent and warehouse-independent number ranges (optional)
· Plus other con gurations made by the BC Sets included in the tool, see the list of the BC Sets at the end of
Sec. 3.4.
You will nd the “Implementation Tool for Warehouse Integration” in the following customizing Path:
SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP

Integration → Tool-Based ERP Integration → Implementation Tool for Warehouse Integration.
1. Click on the IMG node “Implementation Tool for Warehouse Integration”.

2. Enter a Data Set name and its Description. The system uses the name of the data set to store your
data input. And select an existing transport Request/Task or create a new one to store all the
con gurations made by the tool.
3. Click on the “Next >” button to go to Step 2 “System Selection”, keep the proposed Own Logical
System setting – BESCLNT300, and select the BESEWM300 from the Logical Systems list.
4. Click on the “Next >” button to go to Step 3 “Warehouse De nitions”.

Enter Warehouse Number 1710 and your description.
Use the input help drop down to select the ERP Warehouse number 171.
If the ERP warehouse number is not found in the list, check the RFC connection in Sec. 2.2.
5. Click on the “Next >” button to go to Step 4 “Organizational Units”.

Enter the following settings used in the Best Practice:
Supply Chain Unit: YWAREHOUSE-1710
Custodian: BP1710
Default Party Entitled to Dispose: BP1710
6. Click on the “Next >” button to go to Step 5 “Availability Groups”.
Select the rst line, Storage Location 171D, choose the Availability Group 001 and select the EWM stock
type F1, Q3, B5, R7 and S5 as below. The selected values are automatically populated in the 171D line
above.
Select the next line, Storage Location 171S, select Availability 002, and populate the Stock Types F2, Q4,
B6, R8 and S6 as below:
7. Click on the “Next >” button to go to Step 6 “Number Ranges”.

If you want to use the default number ranges, select “Create All Standard Number Ranges”. Otherwise,
de ne your own number range after the activation.
8. Click on the “Next >” button to go to Step 7 “Activation”

Enter an existing Request/Task or create a new one.
You could export the activation list by clicking the “Export” button.
Click the “Activate” button to start the con guration in the background.
9. Click on the “Next >” button to go to Step 8 “Activation Logs” after the completion of Activation.
Check the logs for any error messages. The same log could be found in transaction SLG1 under object
/SCWM/WME and sub-object IMPL_TOOL.
Additional Info
The “Implementation Tool for Warehouse Integration” activates the following BC Sets. You could check their
content using transaction code SCPR3.
BC Set ID Description
/SCWM/PRC_10_10_S4 Basic Settings (Client) – 10 – S/4
/SCWM/PRC_20_10 Basic Settings (Warehouse) – 10
/SCWM/PRC_20_20_S4 Basic Settings (Warehouse) – 20 – S/4
/SCWM/PRC_20_30 Basic Settings (Warehouse) – 30
/SCWM/EXCEPTION Exception Handling
/SCWM/PRC_10_20 Basic Settings (Client) – 20
/SCWM/PRC_10_30 Basic Settings (Client) – 30
/SCWM/PRC_11_9A Assignment Number Range Intervals for Basic

Settings
/SCWM/BASIC_LIME LIME Basic Settings for EWM
3.5 Aligning HU Numbering

SAP Best Practice creates the following HU number ranges.
Application Internal Ranges External Ranges
Logistics Execution 1000000000 – 8000000000 – 9999999999 (10

7999999999 digits)
(10 digits)
EWM (Warehouse 800000000 – 899999999 None (all numbers outside the

speci c) (9 digits)
1710
internal number ranges allowed)
1000000 – 1999999 (7
digits)
If your customer needs di erent HU number ranges, Section 3.5 in the pdf document,
BasicSettings_EWMinS4_V01.pdf, provides setup guidelines.
3.6 Activating Transaction Data Transfer

SAP S/4HANA transfers the transaction data (inbound deliveries, outbound deliveries, and production
material requests) to SAP EWM in SAP S/4HANA using queued remote function call (qRFC).
You need to allow the split of delivery so that the deliveries are split for EWM and non-EWM warehouse if an
order contains items from di erent warehouses.
You con gure De ne delivery split by warehouse under customizing Path:

Logistics Execution → Shipping → Deliveries → De ne Split Criteria for Deliveries → Delivery Split by
Warehouse Number → De ne delivery split per delivery type
Select the Delivery Split checkbox for all delivery types you use in your EWM warehouse, e.g., EL, LF, LR, etc.
In Delivery Split by Warehouse Number, choose the activity Determine delivery split per warehouse number,
and select the checkbox.
For qRFC transaction data transfer, you need to generate the distribution model for the Logistics Execution
warehouse:
Customizing Path:
Logistics Execution → SAP EWM Integration → Basic Setup of Connectivity → Generate Distribution Model
from SAP S/4HANA to SAP EWM.
Enter data in the following elds:

Warehouse Number: 171
Logical System of SAP EWM: BESEWM300
Distribution Model View: EWM (not in the help drop down list)
In the Objects screen area, select All.
In the Action screen area, select Create Entries.
Execute.
Select Yes in the following popup window.
Click the green check icon to continue the generation of the distribution model.
Assigned tags
SAP S/4HANA | EWM - Basis |
Related Blogs
How To Use Maintenance Planner for SAP S/4HANA 1709

By Van Vi , Jan 12, 2018
Strategy and roadmap for SAP S/4HANA and SAP Extended Warehouse Management (SAP EWM)
By Emma Zhou , Sep 10, 2015
FAQ document Available on Strategy and roadmap for SAP S/4HANA and SAP Extended Warehouse Management (SAP EWM)
– Update in July 2016
By Emma Zhou , Jul 25, 2016
End of SAP EWM in SAP S/4HANA

Related Questions
Basic Settings
JIT Processing S/4HANA 1709 Restriction note - 2492542
By Rui Almeida , Nov 27, 2018
Availability of 1709 release for Customer and trial
By Mrinal Kanti Roy , Sep 08, 2017
Congratulations! You have nished the basic settings for SAP EWM in SAP S/4HANA. This completes the
S4 upgrade - SAP S/4HANA 1610 vs. v1709
technical and organization unit integration between SAP EWM in SAP S/4HANA and SAP S/4HANA 1709.
By Former Member , Jan 18, 2018
Before you could use the Best Practice business processes, you need to make the required con guration in
the Building Blocks given in the Prerequisites Matrix for each scope item. I plan to provide an example in a
separate blog.
13 Comments
Former Member
January 13, 2018 at 1:27 pm

Like Alert Moderator
Hi Michael,
Thank you for your practical sharing for SAP EWM 1709.
Best Regards,
Howard Tsai
SAP EWM Consultant, Taiwan
howardtsai48@hotmail.com
Like (0) Reply
Bruno viol
January 23, 2018 at 8:54 pm

Hi Michael, Thank you!
I have been searching for any information about this tools wizard steps!
I was run these tools and created my Warehouse systems, but I have a question!
How can I do with my landscape environment? (development environment, quality environment, and

production environment). This tool will create a customizing request and some con gurations client
depend, for example, RFC names, Business Group names, and logical system names.
Actually, in our project, we (EWM and BASIS team) needed open environments to run all tools wizard, after
that, we deleted requests because in development environment no hasn’t all names for all
environments and clients ( RFC names, Business Group names, and logical system names). Is it correctly?
Thanks!
Like (0) Reply
Former Member | Post author
January 29, 2018 at 3:57 am

Hi Bruno,
Thanks for your feedback.
About the Distributed System Landscape scenario, the BasicSettings_EWMinS4_V01.pdf le only states
“You transport the data set created by the implementation tool to the test system and production system”
(In Section 2.1, page 6). That means you need to create a new transport request when you create the Data
Set so that you could transport the Data Set separately.
The following screenshot could help you understand the transport of the data set approach with an example
in an ERP distributed system landscape with EWM as Add-On. It shows that you con gure all the Logical
Systems and Business Systems in the Data Set and transport them to the Test System and Production
System. Only the Logical System linked to the Test or Production Client (TA SCC4) is active in the Test or
Production system. You don’t need to delete the extra entries in the Test or Production system. You could
use this approach even without using the Implementation Tool for System Connection.
Like (1) Reply
Former Member
January 31, 2018 at 3:32 am

Hi Michael,
Thanks a lot for the helpful sharing.
BR,
Bruce Huang
Like (0) Reply
shailesh mishra
February 2, 2018 at 10:28 am
Hello Michael,
Appreciate your hard e orts in bringing a very complex topic in an explicit way. It will de nitely bene t
consultants to understand and follow the standard process to migrate from SAP business suit to S/4 Hana
versions.
Thanks a lot.
Best regards
Shailesh Mishra
Like (0) Reply
Former Member
February 12, 2018 at 3:53 pm

Hello Michel
Good day
Greate Job, I use the tool as indicated for Distributed System Landscape scenario,but my question is how to
import/transport the creted DATA SET ? to test and production system.
Looking forward to hear from you
My best regads
Fernando Soliz
Like (0) Reply
Former Member | Post author

Hi Fernando,
After the activation in the customizing (DEV) system (Step 7), you transport the transport requests created
in Step 1 (for data set) and Step 7 (for customizing content) to the test systems and the production system.
When you have imported the data set and the customizing content that you created from the data set into
the test and production systems, you can activate the data set in these system. The Implementation Tool
creates the entries that are not included in the transport.
Like (0) Reply
Former Member

Hi Mr Foo,
Thank you very much for this sharing, it’s really helpful.
You always lead us in the new area just like 7 years ago. Very happy to meet and follow you.
Best regards,
Danica (Xing) Hua
Like (0) Reply
Former Member
February 22, 2018 at 8:40 am

Hi Mr Foo,
also from my side – Thank you for your e ort!
Nevertheless I have a question (or problem). We also have used the implementation tool for the system
connection. If we create a data set for our own logical system everythings works ne so far.
If we create a data set for a system landscape we got a problem (dump) during the activation in the
destination system (e. g. Test system). The error says “Unsupported customizing object
/SPE/V_WME_QUEUE, type V”. After analyzing (debug) I found out that the implementation tool execute
some checks on the di erent customizing objects (Table OBJH – Tx SOBJ) if the destination system is setup
as a test or productive system (Tx SCC4). I have compared the settings of the customizing object with other
systems and the settings are all the same. But this standard settings leads to the error (It seems that the
parameters “OBJTRANSP” = 2 and “CURSETTING = “” are not valid in this case).
Does anyone have similar problems?
Does anyone execute the implementation tool in a system landscape successfully?
Maybe we have (only) some wrong settings on the destination system !?
Thanks in advance for every hint.
Regards
Ralf
Like (0) Reply
Former Member
March 13, 2018 at 2:55 am

Thanks so much for the sharing Michael!
It is very helpful!
Regards,
Karl
Like (0) Reply
Mehmet Ozgur Unal
March 15, 2018 at 2:39 pm

Hello Former Member ;
Waiting your new blog to implement Best Practise in S/4 Hana 1709.
M.Ozgur Unal
Like (0) Reply
Former Member
March 20, 2018 at 12:58 am

Hello Former Member ;
Any idea if QI/Counting work center is working in the Complex inbound process in 1709 version? I am seeing
a new transaction code /SCWM/QINSP_S4 is added. But it doesn’t seem to be working.
Balasubramanian Meenakshi Sundaram
Like (0) Reply
Claudio Nizzo
May 22, 2018 at 7:58 am

Hello
I am having problems with the indicated con guration, because when
Click on the IMG node “Implementation Tool for Warehouse Integration”, the message “Error 500 internal
server error” is displayed.
Can someone tell me the possible causes and solutions, please
Like (0) Reply
Add Comment
Share & Follow
Privacy Terms of Use
Legal Disclosure Copyright
Trademark Cookie Preferences
Sitemap Newsletter

Basic Settings For SAP EWM in SAP S - 4HANA 1709 - SAP Blogs

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Basic Settings For SAP EWM in SAP S - 4HANA 1709 - SAP Blogs

Caricato da

Copyright:

Formati disponibili

12/28/2018 Basic Settings for SAP EWM in SAP S/4HANA 1709 | SAP Blogs

Ask a Question Write a Blog Post

Basic Settings for SAP EWM in SAP S/4HANA 1709

Follow RSS feed

10 Likes 12,251 Views 13 Comments

1 Basic Settings for SAP EWM in SAP

SAP EWM in SAP S/4HANA Best Practices

EWM Scope Item Delivered License

1FS: Basic Warehouse Inbound Processing from Supplier 1610 Basic

1FU: Initial Stock Upload for Warehouse 1610 Basic

1FW: Physical Inventory in Warehouse 1610 Basic

1FY: Replenishment in Warehouse 1610 Basic

1G0: Scrapping in Warehouse 1610 Basic

1G2: Basic Warehouse Outbound Processing to Customer 1610 Basic

1VB: Production Integration – Component Consumption and Receipt in 1709 Basic

1VD: Advanced Warehouse Outbound Processing to Customer 1709 Advanced

2 Con guration of qRFC Communication

System Landscape Entity Example Comments

RFC Destination BESCLNT300 Exists in your SAP S/4HANA system

Logical Systems BESCLNT300 Exists in your SAP S/4HANA system and

Dummy Logical System BESEWM300 To be created by the Implementation Tool

Business System Group BG1 BG1 To be created by the Implementation Tool

Business System S4H_001 BES_300 To be created by the Implementation Tool

2.2 Technical Prerequisites for qRFC

2.3 Creating Dummy Logical System Manually

2.4 Con guring qRFC Communication and Client

· System landscape settings for qRFC communication.

2. The following pop-up window opens.

3. Select “Display Quick Help” to display input eld information.

10. The activation is executed in the background.

3 Warehouse Creation and Integration

Org. Master Data Value Master Data Description Comments

Company Code 1710 Company Code 1710 S/4HANA Object

Purchasing Organization 1710 Purch. Org. 1710 S/4HANA Object

Plant 1710 Plant 1 US (or your S/4HANA Object

Storage Location 171D EWM ROD S/4HANA Object

Storage Location 171S EWM AFS S/4HANA Object

Org. Master Data Value Master Data Description Comments

Receiving Point 1710 Shipping Point 1710 S/4HANA Object

Supply Chain Unit YWAREHOUSE- SCU Warehouse 1710 EWM Speci c

EWM Warehouse Number 1710 EWM 1710 EWM Speci c

Custodian BP1710 BP1710 S/4HANA Object

Entitled to Dispose BP1710 BP1710 S/4HANA Object

Goods Receipt O ce YWAREHOUSE- SCU for Warehouse 1710 EWM Speci c

Shipping O ce YWAREHOUSE- SCU for Warehouse 1710 EWM Speci c

3.2 Prerequisites for Warehouse Integration

1. Create storage locations 171D and 171S in plant 1710.

Enterprise Structure → De nition → Materials Management → Maintain storage location.

You need to link the customer BP1710 to Plant 1710 via Customizing Path:

Enter BP1710 in the Customer No. – Plant eld.

3. Add FLVN00 (FI Vendor) and FLVN01 (Vendor) to BP1710

You need to link BP1710 as the supplier to Plant 1710.

3.3 Creating Organizational Units for the Warehouse

1. De ne a warehouse on the SAP S/4HANA side (WM warehouse)

Click New Entries and enter

Warehouse no. description: 171 WM warehouse for EWM

3. Maintain EWM-speci c parameters for the warehouse

3.4 Creating and Integrating a SAP EWM Warehouse

· Warehouse-dependent and warehouse-independent number ranges (optional)

SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP

1. Click on the IMG node “Implementation Tool for Warehouse Integration”.

4. Click on the “Next >” button to go to Step 3 “Warehouse De nitions”.

5. Click on the “Next >” button to go to Step 4 “Organizational Units”.