Administration Guide For SAP Warehouse

PUBLIC
Document Version: 2305 – 2023-05-20
Administration Guide for SAP Warehouse

Robotics
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Technical Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 Additional Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Browsers and Browser Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Supported Data Centers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4 Onboarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5 Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
5.1 Connecting to SAP EWM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional Requirements in SAP EWM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

6.1 Defining and Bundling Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2 Adding Roles to a Role Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3 Assigning Role Collections to Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
7 Business Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1 Configure Your Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
General Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuration Steps for Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
8.1 User Administration, Authentication, and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.2 Session Security Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.3 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.4 Data Storage Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Administration Guide for SAP Warehouse Robotics

2 PUBLIC Content
1 Document History
Provides details about the changes made in each version of this document.
Document Version Date Comment
1.0 2022-05-21 Initial version
1.1 2023-02-18 Minor corrections
1.2 2023-05-20 Minor corrections

Document History PUBLIC 3
2 Overview
About This Guide
This administration guide describes the steps you need to perform as an administrator to set up and run SAP
Warehouse Robotics. It covers application-specific information only.
This guide addresses the following target audience:
• Business configuration experts

• Key users
About SAP Warehouse Robotics
Depending on how you integrate your robots with SAP Warehouse Robotics, the following two integration
scenarios are available:

4 PUBLIC Overview
For more information about using the functions and features provided by SAP Warehouse Robotics, see
the product assistance on the SAP Help Portal at help.sap.com/wr. Under the Use tab, choose the relevant
documents.

Overview PUBLIC 5
3 Technical Prerequisites
Before you start to use SAP Warehouse Robotics, check the requirements and recommendations in this
section.
3.1 Additional Software
If you want to connect your application to an on-premise system, you must have installed and configured the
Cloud Connector. For more information, see Cloud Connector.
3.2 Browsers and Browser Settings
For the UIs of SAP Warehouse Robotics, the following browsers are supported on Microsoft Windows PCs and,
where mentioned below, on macOS:
Browser Versions
Microsoft Edge Latest version
Mozilla Firefox Extended Support Release (ESR) and latest version
Google Chrome Latest version
Safari Latest version (for macOS only)
We highly recommend that you use the Google Chrome browser.
3.3 Supported Data Centers
SAP Warehouse Robotics supports the use of the following data centers:
Region Infrastructure Provider Region Host
Europe (Frankfurt) Amazon Web Services (AWS) eu10.hana.ondemand.com

6 PUBLIC Technical Prerequisites
Region Infrastructure Provider Region Host
US West (WA) Microsoft Azure us20.hana.ondemand.com
China (Shanghai) Alibaba Cloud cn40.apps.platform.sapcloud.cn
 Note
This data center is only available
for the integration with non-SAP
fleet management systems
We recommend that you choose the data center closest to where most users of the application are located.

Technical Prerequisites PUBLIC 7
4 Onboarding
Prerequisites
• You have set up your global account and subaccount. For more information, see Managing Global Accounts
Using the Cockpit and Managing Subaccounts Using the Cockpit.
• You are assigned the Administrator role for the global account.
For more information about the onboarding process, see the SAP BTP documentation under Subscribe to
Multitenant Applications Using the Cockpit.
For more information about the onboarding process for SAP Warehouse Robotics, see the relevant how-to
guide in SAP Note 3198030 .

8 PUBLIC Onboarding
5 Connectivity
You can connect SAP Warehouse Robotics to SAP Extended Warehouse Management (SAP EWM).
For more information about connectivity, see the SAP BTP documentation under Connectivity in the Cloud
Foundry Environment.
5.1 Connecting to SAP EWM
You can connect SAP Warehouse Robotics to SAP Extended Warehouse Management (SAP EWM) as a
standalone product, decentralized EWM based on SAP S/4HANA or EWM embedded in SAP S/4HANA. To
be brief on the product names, SAP EWM is used for references to these deployments in this guide.
Prerequisites
OData Service
OData is a standardized protocol for exposing and accessing information from various sources. OData is based
on core protocols, including HTTP, AtomPub (Atom Publishing Protocol), XML, and JSON (Java Script Object
Notation).
Ensure that you have activated the OData service /SCWM/WAREHOUSE_ROBOTICS for SAP Warehouse
Robotics.
For more information about activating OData services, see Activating OData Services.
Procedures
You need to perform the following actions to set up and operate the connections to the on-premise system:
• SAP Cloud Connector

Configure SAP Cloud Connector in the on-premise landscape.
 Note
When you edit a resource, select the Path and All Sub-Paths access policy.
For more information, see Cloud Connector.

• Destinations
Set up HTTP destinations in SAP BTP.

Connectivity PUBLIC 9
 Note
When you configure a destination, select the OnPremise proxy type and the BasicAuthentication
authentication.
The URL in the destination is a virtual host and a port that you have configured in your cloud connector.
For example, if you defined a virtual host my-virtual-host and port 8080, enter the URL http://
my-virtual-host:8080.
HTTP destinations are relevant for the destination service. For more information, see Managing
Destinations.
If you want to specify the client of the SAP EWM system, please create an additional property with the
property name sap-client. The value should be the SAP client from which you publish the SAP Gateway
Service. If you don’t create the sap-client property, the default client will be used for the integration.
Integrated SAP EWM Releases
You can connect to the following release:
• SAP EWM 9.5
 Note
For support packages lower than SP11 for SAP EWM 9.5, implement the SAP Note 3147663 and
3247030 .
• EWM as part of SAP S/4HANA (SAP S/4HANA 2021 or higher) with the following deployment options:
• Decentralized EWM based on SAP S/4HANA
• EWM embedded in SAP S/4HANA
 Note
For support packages lower than SP03 for SAP S/4HANA 2021, implement the SAP Note 3147663
and 3247030 .
5.1.1 Additional Requirements in SAP EWM
In this section, you can find some additional settings in SAP EWM that you need to define before robots can
process warehouse orders in SAP Warehouse Robotics.
Requirements for Resources
Ensure that the resources in SAP EWM can meet the following requirements:

10 PUBLIC Connectivity
• 1 to 1 relationship
Assign a robot to a single resource in SAP EWM.
For robots integrated via integration services for SAP EWM, a robot processes the warehouse orders
and tasks based on the configuration of the mapped resource in SAP EWM. SAP Warehouse Robotics
determines the queues for the resource that is assigned to a robot based on the queue sequence of the
resource group.
For robots integrated via fleet management systems, SAP Warehouse Robotics determines the queues
from the resource groups selected in a robot process.
• Resource type and group
Define resource types and groups for resources that are mapped to robots.
• No radio frequency (RF) logon
Don't log on to RF devices for resources of the resource types that are mapped to robots.
 Note
SAP Warehouse Robotics assigns warehouse orders to a robot regardless of the logon or logoff status of
the mapped resource in SAP EWM. We recommend that you keep your robot resources logged on.
For robots integrated via integration services, if you want to stop a robot from processing warehouse
orders, disable the robot for use in the Monitor Robots app.
Requirements for Warehouse Tasks
Robots can only process handling unit (HU) warehouse tasks.
Requirements for Warehouse Orders
Ensure that the warehouse orders in SAP EWM can meet the following requirements:
• One HU warehouse task per warehouse order

Ensure that a warehouse order for a robot to process contains only one HU warehouse task.
• Queue of the warehouse orders is only for the use of SAP Warehouse Robotics
• No manual activities required for warehouse order processing
Ensure that warehouse orders in queues are qualified for robots to process. There is no need for manual
activities.
• No changes to warehouse orders
After you've created warehouse orders for robots, avoid updating these warehouse orders.
 Note
If you update a warehouse order in SAP EWM after it is retrieved by SAP Warehouse Robotics, the
system can't synchronize the changes to SAP Warehouse Robotics.
But depending on the type of changes, the results can be different. See the following details:
• If you change the latest starting date or processor, or remove the warehouse order from the queue,
such changes won't affect the processing of warehouse orders by a robot.

• If you change the resource or status of a warehouse order, for example, to cancel a warehouse
order, such changes can cause errors when SAP Warehouse Robotics tries doing the following
actions in SAP EWM:
• Set the warehouse order status to In Process
• Assign a robot resource to the warehouse order
• Confirm the warehouse task or warehouse order
For robots integrated via integration services, you can find the error details in the Monitor Robots
app. You can handle the errors manually in SAP EWM.
Requirements for Exception Handling
Provide a dedicated queue for each warehouse in SAP EWM for exception handling for robots.
For robots integrated via integration services for SAP EWM, if you want to handle the exception for destination
bin errors, ensure that you have defined the following settings in SAP EWM:
• Exception code CHBD (Change Destination Bin)

• Execution step A0 (Data Verification in Background)
• At least one of the following business contexts:
• TIM (Confirm Warehouse Task (Internal Movement))
• TPT (Confirm Warehouse Task (Putaway))
• TPI (Confirm Warehouse Task (Stock Removal))
Requirements for Storage Bins
Ensure that the robots can access the physical source and destination bins of the warehouse orders. Consider
the physical characteristics of your robots.
Requirements for HUs
For robots integrated via fleet management systems, you want to use the robots to move HUs, for example,
carts, totes, and so on. When an HU becomes empty in the storage bins planned to be accessed by robots,
do not delete the empty HU. To stop the system from deleting the empty HUs automatically after unpacking,
deselect the Deleted checkbox in Customizing for Extended Warehouse Management under Goods Receipt
Process Slotting Influencing Parameters Packaging Material Determination Define Packaging Material
Types .
If you want to unpack an HU, we recommend that you first move the HU and the stock to a storage bin that
can’t be accessed by robots. If you really need to unpack the HU in a storage bin that’s accessible to robots,
ensure that SAP EWM creates warehouse tasks for moving the empty HU.
If you physically change the position of an HU, or you let the robot of your fleet management system change
the postion using a robot task not from SAP Warehouse Robotics, ensure that you update the correct stock

12 PUBLIC Connectivity
information in SAP EWM. Otherwise, it can happen that the robot can't find the HU, or it might also cause robot
collisions.

6 User Management
This section describes how to configure user management for your application. As a prerequisite, you have
created business users and user groups in your identity provider (IdP). SAP ID service is configured as the
default IdP, but you can also add your instance of SAP Cloud Identity Services - Identity Authentication or a
different IdP.
If you use the Identity Authentication service, you can find more information in the SAP BTP documentation
under Manually Establish Trust and Federation Between UAA and Identity Authentication.
If you use a different IdP, you can find more information under Establish Trust and Federation with UAA Using
Any SAML Identity Provider.
6.1 Defining and Bundling Roles
SAP Warehouse Robotics provides the following role templates:
Tiles on SAP Fiori Launch

Role Template Description Available Attributes pad
ROBOT_ADMIN • Assigned users can de Not applicable Onboard Robots - Integration
fine robots and set up Services, Onboard Robots -
the connections among Fleet Management
robots, edge nodes,
and SAP Warehouse
Robotics.
• Assigned users can de
fine robots and set
up the connection be
tween fleet manage
ment systems and SAP
Warehouse Robotics .
CONFIGURATION _EXPERT Assigned users can create Not applicable Configure Your Solution
warehouse numbers, upload
warehouse data, connect to
SAP EWM, and define facili
ties for robots.

14 PUBLIC User Management
Tiles on SAP Fiori Launch
Role Template Description Available Attributes pad
WAREHOUSE_ CLERK Assigned users can define Not applicable Define Robot Settings
settings for robots and mon - Integration Services,
itor robot operations in a Monitor Robots, Define
warehouse. Robot Processes - Fleet
Management
WAREHOUSE_ACCESS Assigned users can have ac WAREHOUSE_NAME Not applicable
cess to specific warehouse

 Note
numbers.
If you want a business
role to have access to all
warehouse numbers, en
ter an asterisk (*) for this
attribute value.
If the role template doesn't have any attributes, then the corresponding roles are identical to the role templates
and are created automatically. If the role template has one or more attributes, you must create roles based on
the role templates and provide the attribute values.
You use the ROBOT_ADMIN, CONFIGURATION _EXPERT, and WAREHOUSE_ CLERK role templates to create
roles. Then you use the WAREHOUSE_ACCESS role template to give authorizations to these roles.
As a prerequisite for assigning roles to IdP users or user groups, you also need to configure role collections.
A role collection consists of one or more roles from one or more applications and can be used to bundle
authorizations within and across applications.
For more information about how to create roles and how to bundle them in role collections using the SAP BTP
cockpit, see Building Roles and Role Collections for Applications.
6.2 Adding Roles to a Role Collection
In the SAP BTP cockpit, you must define a role collection and add roles that are derived from role templates to
the role collection.
For more information about the existing role templates for SAP Warehouse Robotics, see Defining and Bundling
Roles [page 14].
For more information about adding roles to a role collection in the SAP BTP cockpit, see Add Roles to a Role
Collection.

User Management PUBLIC 15
6.3 Assigning Role Collections to Users
In the SAP BTP cockpit, you must assign role collections to IdP users or user groups. As a prerequisite, users
and user groups must have been created in the Identity Authentication service or another IdP.
 Note
If you use the SAP ID service, you assign role collections to individual users. If you use the Identity
Authentication service or another IdP, you assign them either to individual users or to user groups.
For more information about how to assign role collections to users or user groups using the SAP BTP cockpit,
see Assigning Role Collections.

16 PUBLIC User Management
7 Business Configuration
A business configuration expert can define required settings before a warehouse clerk can use SAP Warehouse
Robotics.
7.1 Configure Your Solution
With this app, you can make settings relevant to warehouse master data for robots.
For the integration via fleet management, you use the following configuration steps:
• Manage Warehouses [page 17]

• Define EWM Integration Settings [page 18]
• Upload Warehouse Data [page 19]
For integration services for SAP Warehouse Robotics, you use the following configuration steps:
• Manage Warehouses [page 17]

• Define EWM Integration Settings [page 18]
• Upload Warehouse Data [page 19]
• Define Robot Facilities [page 23]
7.1.1 General Configuration Steps
7.1.1.1 Manage Warehouses
With this configuration step, you can create, edit, and delete warehouse numbers.
Procedure
To create a warehouse number, perform the following actions:
1. Choose Create Warehouse Number.

2. Enter a warehouse number and description.
3. Select a time zone.
All time displayed for a warehouse number is based on the time zone that you specified here. For example,
the date selection for dispatched robot tasks in the Monitor Robots app.

Business Configuration PUBLIC 17
4. Enter the unit of length for the entire warehouse.
5. Save your entries.
 Note
If you purchased a test and demo license for SAP Warehouse Robotics, you can have a maximum of five
warehouse numbers.
7.1.1.2 Define EWM Integration Settings
With this configuration step, you can integrate SAP Warehouse Robotics with SAP Extended Warehouse
Management (SAP EWM) systems.
After a successful integration, SAP Warehouse Robotics can read and write relevant warehouse data from SAP
EWM.
Prerequisites
You’ve created a warehouse number using the Manage Warehouses configuration step.
Procedure
To integrate with a destination system, perform the following actions:
1. Edit an existing entry for a warehouse number.

2. Select a destination system that you configured in the SAP BTP cockpit.
3. Enter a destination warehouse number, for example, an SAP EWM warehouse number. A warehouse in SAP
Warehouse Robotics can map to only one warehouse in SAP EWM.
4. Specify a logical system in the destination system.
5. Save your entries.
6. Check the integration status.
For this entry, choose Check to test whether SAP Warehouse Robotics and the destination system are
integrated successfully.
 Note
The integration check doesn't include the integration with a logical system.
7. Define a time interval between data synchronizations. Specify the time frequency for SAP Warehouse
Robotics to retrieve open warehouse orders from SAP EWM. The time interval falls between five seconds
and 600 seconds.
 Note
This step is only applicable for robots integrated via fleet management systems.

18 PUBLIC Business Configuration
Additional Information
Integration Check
If the integration status check isn't successful, there can be the following reasons for an unsuccessful
integration:
• The destination system can't be connected.

• The destination warehouse number doesn't exist.
• The essential OData services aren't configured for a destination system.
7.1.1.3 Upload Warehouse Data
With this configuration step, you can upload essential warehouse data for robots.
Prerequisites
Ensure that you’ve performed the following actions:
• You’ve created a warehouse number using the Manage Warehouses configuration step.
• You have downloaded CSV files from the destination system, for example, SAP EWM. To download these
files from SAP EWM, implement the SAP Note 3200063 .
Procedure
To upload data for a warehouse number, perform the following actions:
1. Choose a warehouse number.

2. Upload data.
Choose the off-line CSV files that you downloaded from SAP EWM.
Additional Information
File Names
You can use the following files from a destination warehouse management system, for example, an SAP EWM
system.

File Name Description
LAGP Storage Bins
RSRC Resources
T303 Storage Bin Types
T331 Storage Type Control
T333 Warehouse Process Type
T346 Queue Definitions
TBIN_AT Bin Access Types
TBIN_AT_PR Bin Access Type Priority per Resource Type
TDC_EDGE Edges for Travel Distance Calculation
TDC_EDGE_R Excluded Resource Type per Edge
TGWLOBJ GWL: Objects
THU_GRP_PR Handling Unit Group Priority per Resource Type
TRSGR_Q_SQ Sequenced Queues per Resource Group
TRSRC_GRP Resource Groups
TRSRC_TYP Resource Types
 Note
Pay attention to the following points:
• The uploaded files must contain the same file names listed above.
• You can view reports for upload details. If an upload is unsuccessful, you can view the error messages.
• If you upload warehouse data again for a warehouse number, the system overwrites the data with
duplicated keys and appends the data with new keys.
If there are keys that exist in the previous upload but not in the current upload, the system still keeps
these keys. If you want to start a new upload, first clear the history data of the previous upload.
Some files above aren’t mandatory, for example, the files TGWLOBJ, TDC_EDGE_R, TBIN_AT, and TBIN_AT_PR.
However, to improve data consistency, we highly recommend that you upload these files.
Required File Settings
To upload files successfully, you must make sure that the following file settings are satisfied:
• The file contains all required fields.

• The file contains a header.
• The file uses commas "," as separators
• The file is less than 500 MB (megabytes) in size.
Required Fields
The following table lists the required fields for the corresponding CSV files:

File Name Required Field Field Name
Storage Bins (LAGP) LGNUM Warehouse Number
LGPLA Storage Bin
LGTYP Storage Type
LGBER Storage Section
LPTYP Storage Bin Type
AISLE Storage Bin Aisle
X_CORD X Coordinate
Y_CORD Y Coordinate
Z_CORD Z Coordinate
STACK Storage Bin Stack
LVL_V Storage Bin Level
ANGLE Angle for Alignment of a Storage Bin

(Degrees)
BIN_AT Bin Access Type
Edges for Travel Distance Calculation LGNUM Warehouse Number

(TDC_EDGE)
LGTYP Storage Type
EDGE_ID Identification of an Edge
NODE_ID_START Identification of Start Node
NODE_ID_END Identification of End Node
X_CORD_START X Coordinate of Edge Start Node
X_CORD_END X Coordinate of Edge End Node
Y_CORD_START Y Coordinate of Edge Start Node
Y_CORD_END Y Coordinate of Edge End Node
DIRECTION Edge Direction
AISLE Storage Bin Aisle
Excluded Resource Type per Edge LGNUM Warehouse Number

(TDC_EDGE_R)
EDGE_ID Identification of an Edge
RSRC_TYPE Resource Type
Resources (RSRC) LGNUM Warehouse Number
RSRC Resource (Means of Transportation or

User)
RSRC_GRP Resource Group
QUEUE Queue
ACTUAL_BIN Current Storage Bin of a Resource

Resource Types (TRSRC_TYP) LGNUM Warehouse Number
VELOCITY Resource Type Velocity in m/s
Storage Bin Types (T303) LGNUM Warehouse Number
LPTYP Storage Bin Type
MAX_LENGTH Length
MAX_WIDTH Width
MAX_HEIGHT Height
Storage Type Control (T331) LGNUM Warehouse Number
LGTYP Storage Type
STGTYP_LVL Level of Storage Type
GWL: Objects (TGWLOBJ) LGNUM Warehouse Number
OBJID Unique Identifier for a GWL Object
OBJCAT Graphical Warehouse Layout Object

Category
X0 X Coordinate of Lower Left Corner
Y0 Y Coordinate of Lower Left Corner
X1 X Coordinate of Lower Right Corner
Y1 Y Coordinate of Lower Right Corner
X2 X Coordinate of Upper Right Corner
Y2 Y Coordinate of Upper Right Corner
X3 X Coordinate of Upper Left Corner
Y3 Y Coordinate of Upper Left Corner
STGTYP_LVL Level of Storage Type
Resource Groups (TRSRC_GRP) LGNUM Warehouse Number
Queue Definitions (T346) LGNUM Warehouse Number
QUEUE Queue
Sequenced Queues per Resource LGNUM Warehouse Number

Group (TRSGR_Q_SQ)
SEQNO Sequence Number
QUEUE Queue
Bin Access Types (TBIN_AT) LGNUM Warehouse Number

Bin Access Type Priority per Resource LGNUM Warehouse Number

Type (TBIN_AT_PR)
PRIORITY Priority
Warehouse Process Type (T333) PROCTY Warehouse Process Type
TRART Warehouse Process Category
ACT_TYPE Activity
Handling Unit Group Priority per Re LGNUM Warehouse Number

source Type (THU_GRP_PR)
HUT_GRP Handling Unit Type Group
PRIORITY Priority
7.1.2 Configuration Steps for Integration Services
7.1.2.1 Define Robot Facilities
With this configuration step, you can create charging point types and charging points.
 Note
This step is only applicable for robots integrated via integration services for SAP Warehouse Robotics.
Activities
Charging Point Types
If you create a charging point type and specify dedicated robot types, only the specified robot types can use
the charging points of the charging point type.
Charging Points
You can create charging points and group them under different charging point types. Note that you must create
the same number of charging points as the number of robots.

8 Security
Security has always been an important element for the complete product life cycle of all SAP products,
including product development, planning, and quality assurance. Like the other SAP products, SAP Warehouse
Robotics was designed to fulfill the highest security standards which guarantee the safety of your data from
attacks.
 Note
There is no personal data stored in SAP Warehouse Robotics.
For more information about security on SAP BTP, see the SAP BTP documentation under Security.
8.1 User Administration, Authentication, and

Authorizations
SAP Warehouse Robotics microservices use the User Account and Authentication (UAA) service for user
authentication and authorization provided in the Cloud Foundry environment by SAP BTP.
SAP Warehouse Robotics microservices are enabled for the OAuth 2.0 client credentials grant flow. OAuth 2.0
is a widely-adopted security protocol for the protection of resources over the Internet. It allows an application
to request authentication on behalf of users with third-party user accounts without requiring the users to grant
their credentials to the application themselves. Based on the OAuth 2.0 client credential grant specification,
the UAA service issues an access token based on client credentials without any user interaction. For more
information, see Authorization and Trust Management Overview.
Appropriate authorization is required for access to SAP Warehouse Robotics microservices and APIs.
8.2 Session Security Protection
APIs and services of SAP Warehouse Robotics are protected by the OAuth 2.0 authorization framework which
defines an authorization protocol for protected API resources. The supported credential type is the client
credentials grant.
The OAuth 2.0 authorization protocol focuses on simplicity by providing security through tokens. It uses
short-lived and specific bearer tokens, and longer-lived refresh tokens which are used to obtain bearer tokens.
Session security is ensured through the validation of these tokens in the APIs and services of SAP Warehouse
Robotics.

24 PUBLIC Security
8.3 Network and Communication Security
Your network infrastructure plays an important role in protecting your system. It supports the communication
necessary for your business needs and prevents unauthorized access to your resources. A well-defined
network topology eliminates many security threats based on software flaws (at operating system level and
application level) or network attacks, such as eavesdropping.
The network topology of SAP Warehouse Robotics is based on the topology used by SAP Cloud Foundry and
SAP BTP. Therefore, the security guidelines and recommendations described in the security guide of SAP BTP
also apply to SAP Warehouse Robotics.
For more information, see Security for SAP BTP.
8.4 Data Storage Security
Data storage security is about how SAP Warehouse Robotics protects its own database. Date storage security
is ensured by the isolated tenant that each customer receives. In SAP Warehouse Robotics, the customer data
isolation is based on database's schema level. Only tenant-specific requests can access the tenant data.

Security PUBLIC 25
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

26 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 27
www.sap.com/contactsap
© 2023 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
affiliate 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

informational 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 warranty 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 companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Administration Guide For SAP Warehouse

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

Administration Guide For SAP Warehouse

Uploaded by

Copyright:

Available Formats

PUBLIC

Document Version: 2305 – 2023-05-20

Administration Guide for SAP Warehouse

THE BEST RUN

6 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Administration Guide for SAP Warehouse Robotics

Document Version Date Comment

1.0 2022-05-21 Initial version

1.1 2023-02-18 Minor corrections

1.2 2023-05-20 Minor corrections

Administration Guide for SAP Warehouse Robotics

About This Guide

This guide addresses the following target audience:

• Business configuration experts

About SAP Warehouse Robotics

Administration Guide for SAP Warehouse Robotics

Administration Guide for SAP Warehouse Robotics

3.1 Additional Software

3.2 Browsers and Browser Settings

Microsoft Edge Latest version

Mozilla Firefox Extended Support Release (ESR) and latest version

Google Chrome Latest version

Safari Latest version (for macOS only)

We highly recommend that you use the Google Chrome browser.

3.3 Supported Data Centers

Region Infrastructure Provider Region Host

Europe (Frankfurt) Amazon Web Services (AWS) eu10.hana.ondemand.com

Administration Guide for SAP Warehouse Robotics

US West (WA) Microsoft Azure us20.hana.ondemand.com

China (Shanghai) Alibaba Cloud cn40.apps.platform.sapcloud.cn

Administration Guide for SAP Warehouse Robotics

Administration Guide for SAP Warehouse Robotics

5.1 Connecting to SAP EWM

• SAP Cloud Connector

For more information, see Cloud Connector.

Administration Guide for SAP Warehouse Robotics

Integrated SAP EWM Releases

You can connect to the following release:

• SAP EWM 9.5

5.1.1 Additional Requirements in SAP EWM

Requirements for Resources

Administration Guide for SAP Warehouse Robotics

Requirements for Warehouse Tasks

Robots can only process handling unit (HU) warehouse tasks.

Requirements for Warehouse Orders

• One HU warehouse task per warehouse order

Administration Guide for SAP Warehouse Robotics

Requirements for Exception Handling

• Exception code CHBD (Change Destination Bin)

Requirements for Storage Bins

Requirements for HUs

Administration Guide for SAP Warehouse Robotics

Administration Guide for SAP Warehouse Robotics

6.1 Defining and Bundling Roles

SAP Warehouse Robotics provides the following role templates:

Tiles on SAP Fiori Launch­

Administration Guide for SAP Warehouse Robotics

WAREHOUSE_ACCESS Assigned users can have ac­ WAREHOUSE_NAME Not applicable

cess to specific warehouse

6.2 Adding Roles to a Role Collection

Administration Guide for SAP Warehouse Robotics

Administration Guide for SAP Warehouse Robotics

7.1 Configure Your Solution

Tiles on SAP Fiori Launch

WAREHOUSE_ACCESS Assigned users can have ac WAREHOUSE_NAME Not applicable