SAP S/4HANA Cloud Product Web Ordering and Reporting

Extensibility Guide | PUBLIC

SAP S/4HANA Cloud Product Web Ordering and Reporting

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Business Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 Extension Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Implementation Steps for Example 1 (Ordering Scenario). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83.1 Implementation Steps in the SAP S/4HANA Cloud System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Add Custom Field to Master Product Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Adapt the Custom Field to the Manage Product Master Data Standard App. . . . . . . . . . . . . . . . . .9

Create a Custom Business Object for Customer Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Implementation Steps on SAP Business Technology Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Download the Sample Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Create a Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Adapt the Application Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Build the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Deploy the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.3 Run and Test the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4 Implementation Steps for Example 2 (Sales Geo Report Scenario). . . . . . . . . . . . . . . . . . . . . .304.1 Implementation Steps on SAP Business Technology Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configure Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Download the Sample Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Create a Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Adapt the Application Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Build the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Deploy the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.2 Run and Test the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5 Add a Custom Tile to the SAP Fiori Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.1 Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6.2 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2 PUBLICSAP S/4HANA Cloud Product Web Ordering and Reporting

Content

1 Overview

1.1 Business Scenario

NoteThis sample scenario is for learning purposes only. It is intended to give you an understanding of the various technical aspects related to extending SAP S/4HANA Cloud. The sample scenario may not always be available in a readily consumable state due to the continuous improvements being made in the underlying products or services. If this is the case, appropriate adaptations based on the latest documentation of the respective products or services are required.

This scenario showcases a simple product-ordering app that allows your customers to display and order products. One-time customers can buy available products without having to register first. With the second analytical sample app, the responsible sales representatives can analyze placed web orders. This includes the geographical distribution of customers, based on their delivery addresses.

This document provides an overview of extension and integration options with the help of sample side-by-side scenarios. In a detailed step-by-step approach, the document explains how to create an initial application on SAP Business Technology Platform and integrate it with SAP S/4HANA Cloud. Additionally, it showcases the combined usage of SAP S/4HANA Cloud in-app extensions options and their usage from within side-by-side applications.

NoteThe sample code that is mentioned in this guide is primarily used for illustration purposes. It is not intended for productive usage. It only shows the basic interaction with an SAP S/4HANA Cloud system. Topics that are related to application development and operation (such as base architecture, reusable components, error handling, transactional correctness, security, caching, versioning, or tests) have been deliberately omitted for the sake of simplicity.

1.2 Extension Scenarios

This guide includes the following extension scenarios:

Example 1: External Product Ordering App

SAP S/4HANA Cloud Product Web Ordering and ReportingOverview PUBLIC 3

Scenario Focal Points Notes and Limitations

You would like to sell products in your portfolio to external users (in this case, to a one-time customer in a simple approach without login and so on). This is why you want to build a small webshop app that is deployed to SAP Business Technology Platform. The app should read data from and write back data to your SAP S/4HANA Cloud system. If a customer places an order, a sales order is created.

● Target group: external users that don't have SAP S/4HANA Cloud users

● Creation of a custom business object and a custom OData service in the SAP S/4HANA Cloud

● Connection set up of the SAP S/4HANA Cloud system and SAP Business Technology Platform

● Creation of a free-style sample Java application (with a simple UI)

● Deployment of the app to SAP Business Technology Platform

● Exposure of standard APIs that are provided by the SAP S/4HANA Cloud for consumption

● Reading data from the SAP S/4HANA Cloud

● Writing back data to the SAP S/4HANA Cloud

● This sample application reads data from the SAP S/4HANA Cloud back-end system. This is why appropriate data is required that is maintained for a sell from stock process (for more information, refer to Sell from Stock (BD9) ).

● Since external users are the target group, no authentication or UI integration is shown.

● A technical user enables communication.

Example 2: Internal Sales Geo Report App


Overview

http://help.sap.com/disclaimer?site=https%3A%2F%2Frapid.sap.com%2Fbp%2Fscopeitems%2FBD9

Scenario Focal Points Notes and Limitations

This scenario is based on the app that is described in example 1 (Product Ordering app).

You would like to create an analytical app that is available to your internal users. Based on the data of the Product Ordering app (that is, the sales orders that have been created and the personal data that has been entered), you want to perform the following analysis: You want to see the overall net amount of sales per month. You would also like to have a geographical map that shows you where a specific sales order has been placed.

● Target group: internal users that have SAP S/4HANA Cloud users

● Creation of a free-style Java application

● Usage of SAPUI5/Fiori as UI to provide a seamless user experience between SAP S/4HANA Cloud and the extension app

● Usage of the SAP S/4HANA Cloud SDK to read data from the SAP S/4HANA Cloud

● Usage of an identity provider to allow single sign-on

● Reading data from the SAP S/4HANA Cloud

● Reusing a third-party map provider (for example, Google Maps)

● Integration of the extension app within the SAP Fiori launchpad

● The app requires appropriate data that is maintained according to the sample app 1 (Product Ordering).

● A technical user enables communication.

SAP S/4HANA Cloud Product Web Ordering and ReportingOverview PUBLIC 5

2 Preparation

2.1 Prerequisites

The sample apps in this scenario use the standard Sales and Distribution (SD) process. Make sure that you have implemented the Sell from Stock (BD9) scope item.

To be able to perform the steps in this document, you need to make sure that the following prerequisites have been met:

Prerequisites Details

SAP S/4HANA Cloud system

You have access to an SAP S/4HANA Cloud system with all the necessary users and authorizations (refer to the following prerequisites).

SAP Business Technology Platform

You have an SAP Business Technology Platform account. For more information on SAP Business Technology Platform accounts, refer to SAP Business Technology Platform Accounts.

NoteFor non-productive/testing purposes, you can use an SAP Business Technology Platform trial account. Find more information on how to get a trial account .

However, if want to try out this sample scenario, you need to have a productive SAP Business Technology Platform Neo subaccount.


Preparation

http://help.sap.com/disclaimer?site=https%3A%2F%2Frapid.sap.com%2Fbp%2F%23%2Fbrowse%2Fscopeitems%2FBD9

https://help.hana.ondemand.com/help/frameset.htm?8ed4a705efa0431b910056c0acdbf377.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdevelopers.sap.com%2Ftutorials%2Fhcp-create-trial-account.html

Prerequisites Details

Personas/users and authorizations

The following personas can be involved in the scenarios. However, depending on your use case, there might be differences.

● SAP S/4HANA Cloud key users: They have the key user authorizations in the SAP S/4HANA Cloud system that are required to create in-app extensions (for example, they can create custom fields and so on). The SAP_BCR_CORE_EXT (Extensibility) business role must have been assigned to these users.

● SAP S/4HANA Cloud administrators: They have the administration authorizations in the SAP S/4HANA Cloud system that are required, for example, to create communication arrangements, or to assign business roles to users. The SAP_BCR_CORE_COM (Communication Management) and the SAP_BCR_CORE_IAM (Identity and Access Management) business roles must have been assigned to these users.

NoteIf the roles mentioned above are not available, make sure that the following business catalogs are assigned to the roles that the users do have. This ensures that users have the necessary authorizations and can access the respective SAP Fiori launchpad apps.○ SAP_CORE_BC_EXT (for the key user)

○ SAP_CORE_BC_COM (for the communication management)

○ SAP_CORE_BC_IAM (for the identity and access management; only if needed)

You can, for example, create a new custom business role if necessary. Use the Maintain Business Roles app. Add the business catalogs on the Assigned Business Catalogs tab.

To access the Manage Product Master Data app in the SAP S/4HANA Cloud system, the following business role is required:

SAP_BR_PRODMASTER_SPECIALIST (Master Data Specialist – Product Data)

Or alternatively:

SAP_BR_PRODMASTER_SPECIALIST (Master Data Specialist – Product Data)

With this app, reviewing data for the whitelisted API and creating new products is possible.

● SAP Business Technology Platform administrators: They have the administration authorizations that are required, for example, to set up the account in general, to add developers as members to the account, or to create destinations.

● Developers: Java and/or SAP Fiori developers who use, for example, Eclipse and/or SAP Web IDE to develop the extension app.

Business data in the SAP S/4HANA Cloud system

Appropriate business data must be available in the SAP S/4HANA Cloud system to make sure that you can follow the examples.

SAP S/4HANA Cloud Product Web Ordering and ReportingPreparation PUBLIC 7

3 Implementation Steps for Example 1 (Ordering Scenario)

The sample app that you're creating in this step describes the following business scenario:

You would like to extend your SAP S/4HANA Cloud to support the product ordering process of some of your products for external customers. Using the extension app, consumers can search for and display a specified number of products. They can order the products and provide their delivery information (for example, name, address and so on).

The order is posted back to the SAP S/4HANA Cloud as a standard sales order and processed within the standard Sales and Distribution (SD) process (for more information, refer to Sell from Stock (BD9) ). The data that customers have entered is written back to SAP S/4HANA Cloud in a custom business object. To make it straightforward for your customers, they don't have to create an account, or register. Sales orders are created in a one-time customer account. The details are stored separately within a custom business object in SAP S/4HANA Cloud.

3.1 Implementation Steps in the SAP S/4HANA Cloud System

3.1.1 Add Custom Field to Master Product Object

For the Product Ordering app scenario, you need to add a custom field to indicate whether the product can be sold or not. If the field value is true, the product can be sold and can be ordered. If the field value is false, this indicates that the product is not for sale.

Prerequisite

The SAP_BCR_CORE_EXT (Extensibility) business role must have been assigned to the user.

Procedure

1. Access the SAP Fiori launchpad.2. To launch the Custom Fields and Logic SAP Fiori app, choose the corresponding SAP Fiori tile.3. To create a new custom field, choose + on the Custom Fields and Logic tab.


Implementation Steps for Example 1 (Ordering Scenario)


4. Choose the Master Data: Product General business context.5. Enter the label of the field: Saleable Product. The Identifier and Tooltip in plural fields are automatically

populated according to the value provided for Label.6. For Type, select Checkbox from the dropdown list.7. Choose Create and Edit to create and edit the custom field.8. In the window, go to the UI and Reports tab and select the OData model for which the field has to be

extended and choose Enable Usage.In this case, the following data sources need to be enabled:○ API_PRODUCT_SRV 0001 (OData extension model for Product API)○ I_Product (Product active core entity)○ MD_C_PRODUCT_MAINTAIN_SRV 0001 (Product Basic Data)

9. Choose Save and Publish.10. Once the extended field has been successfully published, it will be part of the metadata of the OData

service and the corresponding database.

3.1.2 Adapt the Custom Field to the Manage Product Master Data Standard App

The Saleable Product custom field you added previously will be adapted to the Manage Product Master Data SAP S/4HANA Cloud standard app, to make sure that you can set the products to Saleable in a straightforward way.

Prerequisite

The SAP_BR_PRODMASTER_SPECIALIST (Master Data Specialist – Product Data) business role must have been assigned to the user.

Procedure

1. Access the SAP Fiori launchpad.2. Go to the Manage Product Master Data SAP Fiori app.3. Search for a product, for example TG12. Choose the search result.

NoteExisting data must have been maintained in your systems.

4. On the Product screen which shows your selected product, choose the user icon. Choose Adapt UI.

SAP S/4HANA Cloud Product Web Ordering and ReportingImplementation Steps for Example 1 (Ordering Scenario) PUBLIC 9

5. The screen is displayed in the UI Adaption mode. In the Basic Data section, right-click on the Marked for Deletion field to open a context menu. Select Add Field from the context menu.

6. In the dialog box, search for the Saleable Product field and select the corresponding checkbox. Choose OK.



7. The Saleable Product field is now visible (below the Marked for Deletion field). Choose Save & Exit to confirm the UI adaptations.

8. Mark the products as Saleable. Once the Saleable Product custom field has been added, it is false per default.

3.1.2.1 Set Products to Saleable

This section shows how to set products to Saleable.

Prerequisite

● The SAP_BR_PRODMASTER_SPECIALIST (Master Data Specialist – Product Data) business role must have been assigned to the user.

● The Saleable Product custom field has been adapted to the UI of the Manage Product Master Data standard SAP S/4HANA Cloud app.

Procedure

1. Access the SAP Fiori launchpad.2. Go to the Manage Product Master Data SAP Fiori App.3. Search for a product, for example TG12. Choose the search result.


NoteRepeat the steps (starting with step 3) for the products that you want to set to Saleable. As a minimum, step 3 and the following steps have to be performed once to make sure that you will have an executable example later on.

4. On the Product screen, which shows your selected product, choose Edit. The product you selected is now displayed in the Edit mode. Now, you can modify the product.

5. In the Basic Data section, select the Saleable Product checkbox. Choose Save to confirm the changes.

3.1.3 Create a Custom Business Object for Customer Record

In this step, you're creating a custom business object in the SAP S/4HANA Cloud system. A custom business object contains a set of fields that have been designed by the user. In the publishing process, the SAP S/4HANA Cloud system automatically creates respective database tables in the background. A basic maintenance UI is automatically created as well. For more information, refer to How to Create Custom Business Objects.

You can access custom business objects from outside SAP S/4HANA Cloud via an automatically generated OData service.

In this scenario, you're using this service to store your one-time customer's detailed order information on the side-by-side application that runs on SAP Business Technology Platform.

Using custom business objects in this scenario allows you to store data directly next to the standard order data within SAP S/4HANA Cloud. It doesn't have to be stored additionally on SAP Business Technology Platform. If you're storing data on SAP S/4HANA Cloud, you can use the data within custom CDS views, custom business logic, or in-app reports and so on. Depending on the use case in a productive scenario, such data is stored on SAP Business Technology Platform.



https://cp.hana.ondemand.com/dps/d/preview/1a93686c176845f0832a2a73221dd90b/1605%20500/en-US/frameset.htm?c703c5b4e6a24d52a928ea54e8ff5e52.html

https://cp.hana.ondemand.com/dps/d/preview/1a93686c176845f0832a2a73221dd90b/1605%20500/en-US/frameset.htm?c703c5b4e6a24d52a928ea54e8ff5e52.html

Prerequisite

The SAP_BCR_CORE_EXT (Extensibility) business role must have been assigned to the user.

Procedure

1. Access the SAP Fiori launchpad.2. To launch the Custom Business Objects SAP Fiori app, choose the corresponding SAP Fiori tile in the

Extensibility catalog.3. To create a new custom business object, choose New on the Custom Business Objects tab.4. A new window opens for creating a new business object as shown in the table below.5. Enter the name of the business object. The Identifier and Name in plural fields are automatically populated

according to the value provided for Field Name.

Field Name Field Value

Name Customer Record

Identifier CUSTOMERRECORD

Plural name Customer Records

6. To create a new business object, choose Create.7. Select the Determination and Validation, UI Generation and Service Generation checkbox.8. To maintain the fields for the structure, choose Fields.9. To create fields, choose New in the Fields section. Here are some examples:

● Order ID● Last Name● First Name● Phone Number● Shipping Address● Bank Account

NoteUnder Type, select Text. The entry under Length is 20. Select the Key checkbox for each field. The only exception for the length is the field Shipping Address. A typical address requires more than 20 characters. Set the Length of the field Shipping Address in this case to 50 (or even more, depending on your needs). Later on in this scenario, the sample entry Dietmar-Hopp-Allee 16, Walldorf is used as the Shipping Address.


1. To go to the previous screen, choose the return arrow at the top.2. To publish the new custom business object, choose Publish.3. A success message tells you that the business object has been published successfully.

3.1.3.1 Assign the Custom Business Object to a Catalog

NoteThis section is optional. You're assigning the custom business object UI to a catalog to make it easily accessible via the SAP Fiori launchpad.

Procedure

1. Access the SAP Fiori launchpad.2. Navigate to the Custom Business Objects app and choose the business object that you created previously

(for example, YY1_CUSTOMERRECORD).3. On the Custom Business Object screen of the business objects you selected, choose Maintain Catalogs. A

new tab with the Custom Catalog Extensions screen is displayed.

4. Choose Add.



5. In the dialog box, select the catalog that you want to assign your custom business object to. For example, you can choose Extensibility (catalog role ID SAP_CORE_BC_EXT).

6. Once you've selected the catalog, choose OK.7. The catalog that you select is listed in the Used in Business Catalog table. Select the checkbox of the

catalog and choose Publish.

8. Once the status is Published, go back to the first tab with the Custom Business Object screen.9. If Go To Generated UI is grayed out, refresh the browser. Choose Go To Generated UI.

NoteAlternatively, it's possible to access the created and published custom business object from the SAP Fiori launchpad. In this case, the Customer Record tile is located in the Extensibility section. To see a list that contains all records, perform an empty search and choose Go. If there isn't any data, the table remains empty.

3.1.4 Communication Arrangement

In this scenario, a side-by-side application reads product data from our SAP S/4HANA Cloud system and writes back sales orders to the SAP S/4HANA Cloud system. For that purpose, you're using standard, resource-based APIs of SAP S/4HANA Cloud.

To find an overview of all available APIs, refer to the SAP API Business Hub . Navigate to APIs SAP S/4HANA Cloud .

The SAP API Business Hub contains technical documentation and references to business documentation. You can find the technical name of the communication scenario (for example, SAP_COM_0009) and the corresponding scope item in the API Hub.

To allow inbound communication to the SAP S/4HANA Cloud tenant, you need to create a communication arrangement first. The communication arrangement defines which system (communication system) and which user can call which APIs (communication scenarios).

In this example, you're creating a communication arrangement. You're allowing access to the standard product API (SAP_COM_0009), to the sales order API (SAP_COM_0109), and to our custom business object (see above) using a technical user.

Prerequisites

The SAP_BCR_CORE_COM business role must have been assigned to your user.


http://help.sap.com/disclaimer?site=https%3A%2F%2Fapi.sap.com

3.1.4.1 Create a Communication System and a User

Procedure

1. Access the SAP Fiori launchpad.2. Go to the Communication Systemsapp.3. Choose New.4. Enter a system ID (for example, COM_CP_EXTORDERAPP ) and a system name.5. Choose OK.6. On the Communication System screen, enter a host name. Since this communication system is only used

for inbound calls, no host name needs to be specified. Enter localhost as value.7. Make an entry in the Logical System field.8. In the User for Inbound Communication section, choose Add to create a new communication user.9. In the dialog box, choose New User.

Alternatively, you can create a communication user via the Maintain Communication Users app. If you've already created a user, enter the user in the User Name field via the value help icon.

10. On the Create Communication User screen, enter a user name (for example, EXTORDERD_API_USER ) and a description.

11. Enter a password.12. Choose Create.13. On the Communication System screen, the new user is automatically inserted in the User Name field dialog

box. The authentication method is User Name and Password.14. Choose OK.15. In the User for Outbound Communication section, choose Add to create a new user.16. Choose User Name and Password and enter the username and password. Since you don't need an

outbound user in this scenario, use dummy as user name and password.17. Save the new communication system.18. Make sure that the status is Active.

3.1.4.2 Create a Custom Communication Scenario

A communication scenario bundles inbound and outbound communication design-time artifacts. Since it allows communication between systems, each communication arrangement must be based on a communication scenario. For all standard APIs, SAP S/4HANA Cloud provides predefined communication scenarios. Since we want to enable consumption for our Customer Record custom business object, we have to create a custom communication scenario.



Procedure

1. Access the SAP Fiori launchpad.2. Go to the Custom Communication Scenarios app.3. Choose New.4. Enter a communication scenario ID, for example, BO_ONETIMEDATA_ODATA (the ID is

YY1_BO_ONETIMEDATA_ODATA).5. Enter a description, for example, Customer Record.6. Choose New.7. On the Communication Scenario screen, choose Add.8. Search for and select your new custom service (in this case, YY1_CUSTOMERRECORD_CDS ).9. Choose OK.10. You see the custom service in the list.11. Select the newly added entry.12. Choose Publish.13. The status must be Published for further processing.

3.1.4.3 Create Communication Arrangements

Repeat the following steps three times and create arrangements for these communication scenarios:

● SAP_COM_0009 (Standard Product API that is needed to expose and enable reading of the product master data)

● SAP_COM_0109 (Sales Order API that is needed to create the sales order)● YY1_BO_ONETIMEDATA_ODATA (Customer Data Custom Communication Scenario that is needed to store

the entries that the customer maintains via the side-by-side application)

Procedure

1. Access the SAP Fiori launchpad.2. Go to the Communication Arrangements app.3. To create a new communication arrangement, choose New.4. To create a communication arrangement for the standard product API, select SAP_COM_0009.5. Adapt the Arrangement Name if required.6. Choose Create.7. In the Common Data section, select the Communication System that was created in section Create a

Communication System and a User [page ] 16 (COM_CP_EXTORDERAPP) via the value help icon.8. The technical user that was created in the previous step is automatically added to the Inbound

Communication section.9. If this communication scenario has outbound services, deactivate all outbound services.10. Although an outbound user is not relevant in this scenario, you must create an outbound user for the

SAP_COM_0009 communication arrangement. Otherwise, you'll receive an error message.


11. Save your changes.12. Repeat these steps and create a communication arrangement for the one-time Customer Data Custom

Communication scenario (YY1_BO_ONETIMEDATA_ODATA) and for SAP_COM_0109. For these communication arrangements, the outbound service/user is not relevant.

13. Check that the communication arrangements have been activated (the status Active must be visible).

NoteNote down the service URLs for your custom business object. You'll need the URLs later. You find them in the Inbound Communication section of the communication arrangement.



3.2 Implementation Steps on SAP Business Technology Platform

In this step, you're implementing a sample app that showcases the functionality of the scenario that has been set up. The app provides you with a basic sample implementation of how an interaction with the SAP S/4HANA Cloud can be achieved. Everyone can access the app; no login is required.

The app offers you an experience that is like a web shop. Products in the SAP S/4HANA Cloud system are displayed on the UI and can be ordered by an external (one-time) customer (to keep things simple, aspects such as user logon/account haven't been taken into account in this example). When customers select a product that they would like to order, they see more information on the product (for example, a detailed description). They can provide their personal information such as their names, shipping addresses, and so on. Once they've placed an order, the order is posted back to the SAP S/4HANA Cloud as a standard sales order and processed with the SD process (for more information, refer to Sell from Stock (BD9) . A one-time customer ID is assigned to the sales order. The data that the customer has entered is written back to SAP S/4HANA Cloud and stored separately within a custom business object in SAP S/4HANA Cloud.

Prerequisites

● You've installed a JDK 8, which is available on the Oracle Download page . Consider the JAVA_HOME environment variable.

● You've downloaded and installed Maven 3.0, which is available on the Apache Maven Project Download page .

● Optional: You've downloaded and installed the Git Command Line Interface, which is available on the Git Download page .

NoteMake sure that all binaries are maintained in your environment PATH variable. If you're behind a web proxy, configure the proxy settings accordingly (for example, settings.xml for Maven, environment variable HTTPS_PROXY for Git, network settings in Eclipse).

3.2.1 Download the Sample Application

Access the general sample app repository on GitHub .

Procedure

Download and extract the ZIP file that you get from the GitHub repository.



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.oracle.com%2Ftechnetwork%2Fjava%2Fjavase%2Fdownloads%2Findex.html

http://help.sap.com/disclaimer?site=http%3A%2F%2Fmaven.apache.org%2Fdownload.cgi

http://help.sap.com/disclaimer?site=http%3A%2F%2Fmaven.apache.org%2Fdownload.cgi

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgit-scm.com%2Fdownloads

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgit-scm.com%2Fdownloads

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-order-app

Alternatively, you can clone the repository via the command line.

git clone https://github.com/SAP/s4hana-ext-order-app.git cd s4hana-ext-order-app

3.2.2 Create a Destination

The application uses the SAP S/4HANA Cloud SDK to make a connection to the OData APIs of the SAP S/4HANA Cloud system. The SDK, however, uses SAP Business Technology Platform destination service internally to provide a separation code and configuration.

In this step, you're creating a destination to define the outbound communication of the side-by-side application to the SAP S/4HANA Cloud system. To keep things simple, in this app, the actual connection to the SAP S/4HANA Cloud is set up via the communication user. Theoretically, propagation to the SAP S/4HANA Cloud system is possible, but out of scope for this guide.

Procedure

1. Log on to your SAP Business Technology Platform account.

2. In the cockpit, go to Connectivity Destinations .3. Choose New Destination.4. Maintain the properties as follows:

Property Value

Name ErpQueryEndpoint

Type HTTP

Description <for example the name of your communication arrangement>

URL <the base URL to your SAP S/4HANA Cloud system, note the "-api", for example https://myXXXXXX-api.s4hana.ondemand.com>

Proxy type Internet

Authentication BasicAuthentication

User <the user that you created, for example EXTORDERD_API_USER>



Property Value

Password <the password that you created>

NoteThe user and password depend on the communication arrangement that was created in your SAP S/4HANA Cloud.

Leave the Use Default JDK Trustore checkbox selected (if you don’t have any other truststore).

5. Save your changes.

3.2.3 Adapt the Application Configuration

The sample app is designed as a ready-made example. You only need to make modifications in one file in which you should enter, for example, the URL of your SAP S/4HANA Cloud system and the technical user.

Procedure

1. Open the application/src/main/resources/application.properties file.2. You can leave the meta data (the entries after “=”) as it is as long as you named the custom business

object as given here.

CautionBefore packaging the application, make sure that the remaining meta data is adequately maintained (for example, business partner) depending on what you want to display and according to your needs, and that data is available in the system.

# OData service of the Custom Business Object, created in S/4HANA Cloud to store one-time order data s4cld.onetimecustomerrecord_servicepath=/sap/opu/odata/sap/YY1_CUSTOMERRECORD_CDS s4cld.onetimecustomerrecord_resource=YY1_CUSTOMERRECORD #One time Business partner s4cld.onetimebusinesspartner =XXXXXXXXXX #Distribution channel s4cld.distrubutionchannel=10 #Organization Division s4cld.organizationdivision=00 #Product Group s4cld.productgroup=L001 #SalesOrder Type s4cld.salesordertype=OR


You can find s4cld.onetimecustomerrecord_servicepath and s4cld.onetimecustomerrecord_resource in the Communication Arrangements and in the Custom Business Objects app.

In this example, s4cld.onetimecustomerrecord_servicepath should be /sap/opu/odata/sap/YY1_CUSTOMERRECORD_CDS.

s4cld.onetimecustomerrecord_resource should be your custom business object ID that was created in section Create a Custom Business Object for Customer Record [page 12]. You can find it in the app (in this case, Custom Business Objects YY1_CUSTOMERRECORD ).

3.2.4 Build the Application

In this step, you're using Maven to package the application (for more information on Maven, refer to Apache Maven Project ). The package compiles all sources, runs tests, and bundles all assets in a web application archive file (WAR file). This archive is imported to SAP Business Technology Platform.

Procedure

1. To build the application, go to the command console.2. Switch to your project directory, for example C:\your project\extorderapp.3. Enter:

mvn package



http://help.sap.com/disclaimer?site=http%3A%2F%2Fmaven.apache.org%2F


4. After Maven has downloaded all dependencies and successfully compiled the Java source files, you receive a success message:

[INFO] BUILD SUCCESS

5. In the Application/Target folder, you find the WAR file that you created. Here's an example:extorderapp-application.war

3.2.5 Deploy the Application

In this step, you're switching to your SAP Business Technology Platform account and deploying the Java app.

Procedure

1. Log on to your SAP Business Technology Platform cockpit.

2. Go to Java Applications Deploy Application .3. From your file system, select the WAR file that you created in the previous step.4. As Runtime Name, select Java EE 7 Web Profile TomEE 7.5. To upload the application, choose Deploy.


6. After you've successfully uploaded the application, choose Start to open the application.7. Once the app has been started, you see a green Started sign and the application URL that takes you to the

app.



3.3 Run and Test the Application

In this step, you're running and testing the app that is hosted on SAP Business Technology Platform. You're also checking the write back of data to the SAP S/4HANA Cloud system.

Prerequisites

● To test the steps in the SAP S/4HANA Cloud system, the business roles to access the Manage Sales Order app (SAP_BR_INTERNAL_SALES_REP) and the Custom Business Objects app (SAP_BCR_CORE_EXT) must have been assigned to your user.

● To work your way through the app, you must have appropriate business data in your system.

Procedure

1. Access the Product Ordering app in your SAP Business Technology Platform account. You find the application URL under Applications Java Applications <your Java app> .

2. On the overview page of the application, you see a list of products that are maintained in your SAP S/4HANA Cloud system.

3. These products are read live from the SAP S/4HANA Cloud system. The sample code only shows products in the Product Group L001. This filter is hard coded and can be changed in the application.properties file.


4. To view only salable products, select Saleable Products. To order a product, simply choose Order under the saleable product that you would like to order. This takes you to the Order screen.

5. Fill out the form.



6. To submit it, choose Order. The result contains two identification numbers.

7. Go to your SAP S/4HANA Cloud front end.8. Go to the Manage Sales Orders application. You see the 214 sales order that you created. The Customer

Reference field has been defined by our sample application.


9. To get to your One Time Customer Record custom business object, go to the Maintenance UI. You see the entry that you created.

NoteThe Booking Confirmation ID mentioned above is the unique technical ID that the system created.

10. If an error page is displayed, check the troubleshooting section in the README file of the GitHub repository.Alternatively, you can check the application log for exception stack trace. Go to Applications Java Applications Monitoring Logging SAP Business Technology Platform Cockpit .




4 Implementation Steps for Example 2 (Sales Geo Report Scenario)

This sample application showcases an extension to an SAP S/4HANA Cloud system for internal users (for example, management). The extension provides you with a sales order bar chart. It tells you where customers have placed their orders by indicating their location on a geographical map.

The sample app that you're creating in this step describes the following business scenario:

You would like to create an analytical app that is available to your internal users. You want to carry out an analysis that is based on the Product Ordering app data (the sales orders that have been created and the personal data that has been entered). You want to have a bar chart that shows you the net amount of sales per month. At the same time, you want to see the exact locations of the customers who have placed orders. This is why you would like to have a map that indicates your customers' locations.

Since only internal users access the app, you need to have an SAP S/4HANA business user to access the extension app. To create the app, a shared Identity Provider (IdP) in front of your SAP Business Technology Platform and SAP S/4HANA Cloud is used.

Prerequisites

● In general, you walked through example 1. The Product Ordering app is up and running.● You carried out the steps in section Create a Custom Business Object for Customer Record [page 12]and in

section Communication Arrangement [page 15] about the side-by-side extensibility sample app 1 (Product Ordering).

● All SAP S/4HANA Cloud settings for the Product Ordering app (creating a custom business object and a communication arrangement) are prerequisite for the Sales Geo Report app because they fetch data from the same services.

● In a productive case, we recommend that you work with a different communication arrangement for each app to make sure that the apps don't interfere with each other. Otherwise, you might deactivate or even delete a dedicated communication arrangement and block an external app or integration.

● In the Sales Geo Report app (sample app 2), you're using a Google map to indicate geographical locations. Therefore, you need a Google Maps API key. For more information, refer to:○ Adding a Google map○ General information on the API○ Get an API key○ Licensing


Implementation Steps for Example 2 (Sales Geo Report Scenario)

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdevelopers.google.com%2Fmaps%2Fdocumentation%2Fjavascript%2Fadding-a-google-map

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdevelopers.google.com%2Fmaps

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdevelopers.google.com%2Fmaps%2Fdocumentation%2Fjavascript%2Fget-api-key

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdevelopers.google.com%2Fmaps%2Fpricing-and-plans

4.1 Implementation Steps on SAP Business Technology Platform

4.1.1 Configure Single Sign-On

A single sign-on (SSO) configuration between SAP S/4HANA Cloud and SAP Business Technology Platform, and the principal propagation enablement ensure the secure and consistent access for the extension solutions.

In this case, the SAP S/4HANA Cloud system and the SAP Business Technology Platform subaccount must trust each other and use one and the same identity provider.

With the enablement of single sign-on, you make sure that your business user from SAP S/4HANA Cloud can log on to and access the side-by-side application (by using the same identity provider).

Prerequisites

● You have an SAP Business Technology Platform account.● You have an SAP S/4HANA Cloud system and an SAP Identity Authentication tenant. The SAP S/4HANA

Cloud system is already connected to it. For more general information on SAP Business Technology Platform Identity Authentication Service, see SAP Business Technology Platform Identity Authentication Service.

● You have a user with administration authorization for the tenant’s administration console for Identity Authentication.

● A separate “subaccount” for apps is used that is protected by the identity provider (IdP) because the IdP has been configured for a complete “subaccount”.

Procedure

Walk through the implementation steps outlined here: Single Sign-On Configuration in Neo Environment

Result

You have established a trust between Identity Authentication Service and SAP Business Technology Platform. Your business user will be able to log on to and access the side-by-side app later.

SAP S/4HANA Cloud Product Web Ordering and ReportingImplementation Steps for Example 2 (Sales Geo Report Scenario) PUBLIC 31

https://help.sap.com/viewer/6d6d63354d1242d185ab4830fc04feb1/Cloud/en-US/d17a116432d24470930ebea41977a888.html

https://help.sap.com/viewer/6d6d63354d1242d185ab4830fc04feb1/Cloud/en-US/d17a116432d24470930ebea41977a888.html

https://help.sap.com/viewer/233fb3f82e484f75ab3511fccd46d101/Cloud/en-US/f9f85502a2ce4980b6e4ad1191b1cbdb.html

4.1.2 Download the Sample Application

In this step, you're importing a Java app. You're following the procedure described in section Download the Sample Application [page 19].

You can find the app code on GitHub .

Procedure

Download and extract the ZIP file that you get from the GitHub repository.

Alternatively, you can clone the repository via the command line.

git clone https://github.com/SAP/s4hana-ext-geo-report-app cd s4hana-ext-geo-report-app

4.1.3 Create a Destination

The application uses the SAP S/4HANA Cloud SDK to make a connection to the OData APIs of the SAP S/4HANA Cloud system. The SDK, however, uses the SAP Business Technology Platform destination service internally to provide a separation code and configuration.

In this step, you're creating a destination to define the outbound communication of the side-by-side application to the SAP S/4HANA Cloud system. To keep things simple, in this app, the actual connection to the SAP S/4HANA Cloud is set up via the communication user. Principal propagation to the SAP S/4HANA Cloud system is possible, but out of scope for this guide.

Procedure

1. Log on to your SAP Business Technology Platform account.

2. In the cockpit, go to Connectivity Destinations .3. Choose New Destination.4. Maintain the properties as follows:

Property Value

Name S4HANACloudEndpoint

Type HTTP



http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-geo-report-app

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-geo-report-app

Property Value

Description <for example the name of your communication arrangement>

URL <the base URL to your SAP S/4HANA Cloud system, note the “-api”, for example https://myXXXXXX-api.s4hana.ondemand.com>

Proxy type Internet

Authentication BasicAuthentication

User <the user that you created, for example EXTORDERD_API_USER>

Password <the password that you created>

NoteThe user and password depend on the communication arrangement that was created in your SAP S/4HANA Cloud system. Leave the Use Default JDK Trust Store checkbox selected (if you don’t have any other trust store).

5. Save your changes.

4.1.4 Adapt the Application Configuration

The sample app is designed as a ready-made example. You only need to make modifications in one file in which you should enter, for example, the URL of your SAP S/4HANA Cloud system and the technical user.

Procedure

1. Open the src/main/resources/application.properties file.2. Adapt the properties to the scenario. That means:

○ Make sure that you're using the correct name of the destination that you created.○ Use the same names of the custom business object (customer records) from the Product Ordering app

(sample app 1).○ Enter your Google Maps API key. For more information on how to get a key, refer to the Quick Guide to

Getting a Key .○ Make sure that you insert the same business partner as used in the properties file of the Product

Ordering app (sample app 1).




4.1.5 Build the Application

In this step, you're using the Maven tool to build the application (for more information, refer to Apache Maven Project ). It generates a WAR file that you can import to SAP Business Technology Platform. The steps that explain to you how to build the app are similar to those outlined in section Build the Application [page 22].

Procedure

1. To build the application, go to the command console.2. Switch to your project directory, for example C:\your project.3. Enter:

mvn package

4. After Maven has downloaded all dependencies and successfully compiled the Java source files, you receive a success message:

[INFO] BUILD SUCCESS

5. In the Target folder, you find the WAR file that you created. Here's an example:intreportapp-0.0.1.war

4.1.6 Deploy the Application

In this step, you're switching to your SAP Business Technology Platform account and deploying the Java app.

Depending on your SAP Business Technology Platform account, you are entitled to have only one Java app up and running. If that's the case, before you start a new app, stop the app that you've already opened. For more information on managing quotas, refer to the SAP Help Portal.

Procedure

1. Log on to your SAP Business Technology Platform cockpit.

2. Go to Java Applications Deploy Application .3. From your file system, select the WAR file that you created in the previous step.4. As Runtime Name, select Tomcat 8.5. To upload the application, choose Deploy.





https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/e5e8c85fefa44e489838ba85f703e976.html

6. To open the application, choose Start.7. Once the app has been started, you see a green Started sign and the application URL that takes you to the

app.


4.2 Run and Test the Application

In this step, you're running and testing the app that is hosted on SAP Business Technology Platform. You're also testing its functionality.

Prerequisites

● The Product Ordering app (sample app 1) must be up and running.

NoteDepending on your SAP Business Technology Platform account, you're entitled to have only one Java app up and running. If that's the case, before you start a new app, stop the app that you've already opened. For more information on managing quotas, refer to the SAP Help Portal.

● To work your way through the app, you must have appropriate business data in your system.

Procedure

1. Access the Product Ordering app in your SAP Business Technology Platform account. You find the application URL under Applications Applications Java Applications <your Java app> .



https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/e5e8c85fefa44e489838ba85f703e976.html

2. On the overview page of the application, you see a list of products that are maintained in your SAP S/4HANA Cloud system.

3. To go to the Order screen, select one of the products.


4. Fill out the form. For example, under Shipping Address, enter the following address: Dietmar-Hopp-Allee 16, Walldorf.

5. To submit it, choose Order.6. The result contains two identification numbers. Remember the order number since you'll need it later.

7. To access the Sales Geo Report app for internal users (sample app 2) in your SAP Business Technology Platform account, choose the application URL.

8. Depending on your SAP Business Technology Platform account, before you start the Sales Geo Report app, you must stop the first Java app that you've already opened.



9. The log-on screen for your IdP is displayed. Here's an example:

10. Enter the credentials of the SAP S/4HANA Cloud business user and log on.11. The app is displayed. You can see the sales orders per month and the business user in the top right corner.12. If you choose a bar, you see which locations the products have been shipped to. That means, you can see

your one-time customers' shipping addresses and locations.13. To display the shipping address that a customer entered in the Product Ordering app and the respective

sales order, choose the pin on the map.


5 Add a Custom Tile to the SAP Fiori Launchpad

In this step, you're adding a custom tile to your SAP Fiori launchpad. You can integrate external URLs, for example a side-by-side extensibility application that is hosted on SAP Business Technology Platform. With this feature, business users can easily access your side-by-side extensions from within SAP S/4HANA Cloud.

Prerequisite

The Extensibility (SAP_BCR_CORE_EXT) business role must have been assigned to the user.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.2. Choose Customer Tiles.3. To create a new custom tile, choose New.4. In the Create Tile dialog box, enter a title and an ID.5. Choose Create.6. On the Custom Tile Details screen, you can maintain more details, for example subtitle and icon.7. Make sure you maintain the URL (for example, the URL of the internal app from SAP Business Technology

Platform) properly, that means with http* in front.8. Save your changes.9. To determine where the new tile will be displayed, choose Assign Catalogs.10. Choose Add.11. In the Add Business Catalog dialog box, select the catalogs of your choice, for example the Extensibility

business catalog (SAP_CORE_BC_EXT), and choose OK.12. On the Custom Catalog Extensions screen in the Used in Business Catalog section, you see the catalog that

you added. It has the status Unpublished.13. Select the checkbox of the catalog(s) and choose Publish.14. In the Confirmation dialog box, choose OK.15. The status changes to Publishing. It might take some time until it has the status Published.16. Go back to the SAP Fiori launchpad. Once the tile has been successfully published, you find it in the group

to which you added it, for example in the Extensibility group. If you choose the tile, you're navigated to the page you maintained previously. It is displayed in another tab.


Add a Custom Tile to the SAP Fiori Launchpad

6 Appendix

6.1 Issues

Please note that SAP does not offer any official support for the sample code (see the SAP SAMPLE CODE LICENSE AGREEMENT on GitHub). However, feel free to use the Issues section on GitHub if you have any problems. We recommend that you browse through the known issues section before creating a new issue.

Scenario

SAP S/4HANA Cloud Geo Reporting for Product Web Ordering Application

Known Issues New Issue

SAP S/4HANA Cloud Product Web Ordering Application

Known Issues New Issue

6.2 Document History

Revision Date Change

1.0 2018-10-15 Document created.

1.1 2019-02-20 Download the Sample Application [page 19] and Download the Sample Application [page 32] updated.

1.2 2019-06-03 Prerequisites [page 6] updated.

1.3 2019-09-13 Issues [page 41] section added.

1.4 2019-11-27 Adapt the Application Configuration [page 21] and Deploy the Application [page 23] updated.

SAP S/4HANA Cloud Product Web Ordering and ReportingAppendix PUBLIC 41

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-geo-report-app%2Fissues

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-geo-report-app%2Fissues%2Fnew

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-order-app%2Fissues

http://help.sap.com/disclaimer?site=https%3A%2F%2Fgithub.com%2FSAP%2Fs4hana-ext-order-app%2Fissues%2Fnew

Important Disclaimers and Legal Information

HyperlinksSome 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 a 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 PlatformsSome 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 FeaturesExperimental 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 CodeAny 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.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

SAP S/4HANA Cloud Product Web Ordering and ReportingImportant Disclaimers and Legal Information PUBLIC 43

www.sap.com/contactsap

© 2021 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

https://www.sap.com/about/legal/trademark.html

Documents

SAP S/4HANA Cloud Product Web Ordering and Reporting