Preparing SAP BTP Subaccount

Objective

After completing this lesson, you will be able to create destinations and activate SAP Build Work Zone, standard edition

Creation of SAP BTP Destinations

To connect to the SAP S/4HANA system, import the content, and access business data, two destinations need to be created in the SAP Business Technology Platform subaccount:

  • Design-time destination – used by SAP Build Work Zone, standard edition to fetch the exposed content from the SAP S/4HANA system
  • Runtime destination – used during runtime, that is, whenever a user is working on the launchpad and accesses back-end data

Log on to SAP BTP subaccount, navigate to Destinations, and click Create Destination.

Screenshot of the SAP BTP Cockpit Destinations tab, highlighting the “Create Destinations” button.

Design-Time Destination Creation

Clicking New Destination opens a destination template – enter the following information for the Design-Time destination. For name, use the SAP S/4HANA system ID with the suffix "dt" for Design-Time, for example, s4hdt. As the authentication method, use "BasicAuthentication" and enter the credentials of the exposing user.

Note

The destination name must be lower case and must not contain the underscore character (_).

Destination Configuration

NameFor example, s4hdt
TypeHTTP
DescriptionFor example, S4 Design Time Destination
URLhttps://<hostname>:<port>/sap/bc/ui2/cdm3/entities
Proxy TypeOnPremise
AuthenticationBasicAuthentication
Location ID<Location ID defined in the Cloud Connector>
UserSAP S/4HANA User
PasswordPassword of the above user

Additional Properties

sap-client<SAP S/4HANA client> For example, 100

Note

Save the entered information.

Screenshot of an example of a correctly configured design-time destination “s4hdt”.

Runtime Destination Creation

Next, the runtime destination will be created. This destination is required to access the business data of the connected SAP S/4HANA system. It does point to the base host, so apps that are requesting data can add to the path to request the data from specific endpoints.

For the name, use the SAP S/4HANA system ID and the suffix "rt" for runtime, for example, s4hrt.

Note

The destination name must be lower case and must not contain the underscore character (_).

Similar to the Design-Time destination, use the BasicAuthentication for now. Enter the credentials of an SAP S/4HANA user that can be used to perform a first test for the business content. This could either be your own or a dedicated test user that holds authorizations to the business content in the exposed roles.

In the next lesson, the authentication method will be changed from BasicAuthentication to PrincipalPropagation to enable a connection based on the user logged into SAP Build Work Zone, standard edition.

For the other input fields and additional parameters, use the guidance of the following table:

Destination Configuration

NameFor example, s4hrt
TypeHTTP
DescriptionFor example, S4H Runtime Destination
Proxy TypeOnPremise
URLhttps://< hostname>:<port>
AuthenticationBasic Authentication
Location ID<Location ID defined in the Cloud Connector>
User <SAP S/4HANA user> 
Password <Password of respective user>

Additional Properties

HTML5.DynamicDestinationtrue
MobileEnabledtrue
sap-client<client> for example, 100
sap-platformABAP
sap-service32<service number> for example, 3200
sap-sysid<sysID> for example, S4H

Save the entered information.

Note

More information on the parameters is available in the help documentation.

Screenshot of an example of a correctly configured runtime destination “s4hrt”.

Log in to track your progress & complete quizzes