Importing Content to SAP Build Work Zone, standard edition

Objectives

After completing this lesson, you will be able to:

  • Use business content from SAP S/4HANA Cloud on SAP BTP

Import Content to SAP Build Work Zone, standard edition

The following steps are required to integrate the content that was exposed from SAP S/4HANA Cloud into SAP Build Work Zone, standard edition:

  • Dedicated destinations should be created so that the SAP BTP subaccount can fetch and consume resources from SAP S/4HANA Cloud.
  • A content channel should be created within the Site Manager to work with the content.

The following destinations are required to connect to SAP S/4HANA Cloud from SAP BTP:

  1. Design-time destination for fetching the content:

    The location from which SAP Build Work Zone, standard edition fetches the exposed content

  2. Runtime destination for consuming the content for dynamic tiles:

    The location for retrieving dynamic data from the SAP S/4HANA Cloud tenant’s API to be displayed on dynamic tiles

    Note
    A dynamic tile displays information from a back-end system through a dedicated service (OData or other), which is refreshed on a predefined time interval. The dynamic information pulled from the back-end system overwrites the configuration values given in the tile configuration.
  3. Runtime destination (default) for consuming the content:

    The runtime destination defines the location from which the required resources to run the federated apps in runtime are obtained from

Prerequisites

  • SAP BTP platform admin user with admin access to the SAP BTP subaccount
  • Identity Authentication user, which is set up in Identity Authentication and SAP S/4HANA Cloud. It needs to be maintained with the exact same values for User ID and E-Mail address in both systems and assigned to some business roles on the SAP S/4HANA Cloud system.

Configure Destinations for Fetching and Consuming Business Content

Steps

  1. In the SAP BTP cockpit, log on to your subaccount with the SAP BTP platform admin user.

  2. In the navigation area, choose ConnectivityDestinations.

  3. To create the destination for fetching the content, choose New Destination and enter the following information:

    PropertyDescription/Value
    Name

    Enter <system ID><client>dt

    For example, s4h100dt

    Note:

    The destination name must be unique for the current application. It must contain only alphanumeric characters, underscores, and dashes. The maximum length is 200 characters.

    TypeHTTP
    DescriptionEnter a description, for example, <system ID>_<client> design-time connection
    URLhttps://<SAP S/4HANA Cloud tenant ID>-api.s4hana.ondemand.com/sap/bc/http/sap/aps_flp_content_exposure/entities
    Proxy TypeInternet
    Authentication

    ClientCertificateAuthentication

    Note:

    If you chose Basic Authentication for the initial setup, provide Username and Password instead of Key Store Location and Password.

    Use client-provided certificateKeep unchecked
    Key Store Location

    Select the key store location that stores the relevant keys.

    Note:

    The key store location must be in the PFX format.

    Only public certificate authorities (CA) are supported.

    Key Store PasswordEnter your password.

    HTML5.DynamicDestination

    (additional property)

    true
    Use default JDK truststoreMake sure that it is checked

    Result

  4. To create the destination for consuming the content for dynamic tiles, enter a URL to the SAP S/4HANA Cloud tenant’s API host as follows:

    PropertyDescription/Value
    Name

    Enter <system ID><client>rt_tiles

    For example, s4h100_tiles

    TypeHTTP
    Description

    Enter a description.

    For example, enter <system ID>_<client> runtime for dynamic tiles

    URLhttps://<SAP S/4HANA Cloud tenant ID>-api.s4hana.ondemand.com
    Proxy TypeInternet
    AuthenticationSAMLAssertion
    Audiencehttps://<SAP S/4HANA Cloud tenant ID>.s4hana.ondemand.com
    AuthnContextClassRefurn:oasis:names:tc:SAML:2.0:ac:classes:PreviousSession

    nameIdFormat

    (additional property)

    urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

    HTML5.DynamicDestination

    (additional property)

    true

    Result

  5. To create the runtime destination for launching the federated apps, enter the direct URL to the SAP S/4HANA Cloud tenant’s UI host as follows:

    PropertyDescription
    Name

    Enter <system ID><client>rt_apps.

    For example, s4h100rt_apps

    TypeHTTP
    Description

    Enter a description.

    For example, enter <system ID>_<client> runtime apps.

    URLhttps://<SAP S/4HANA Cloud tenant ID>.s4hana.ondemand.com
    Proxy TypeInternet
    AuthenticationNoAuthentication

    HTML5.DynamicDestination

    (additional property)

    true

    sap-platform

    (additional property)

    ABAP

Result

Note

Ensure the following when defining the entries in the destinations:

  • Do not use any extra "/" or space characters; for example, at the end of the string values
  • Values are case-sensitive; use the values exactly as mentioned in the tables

Related Information

Import Business Content to SAP Build Work Zone, standard edition

The exposed content needs to be imported and managed within the Site Manager by following these steps: 

  1. Create content channel
  2. Manage content
  3. Create site and assign roles
  4. Assign role collections to users
  5. Test the site

Test the Setup

You can now use a browser on the desktop to access the launchpad site on SAP Build Work Zone, standard edition, using end-user credentials that are defined in Identity Authentication and have relevant authorizations in SAP BTP and SAP S/4HANA Cloud. Test a few of the SAP Fiori apps to verify that the connection is working properly.

Log in to track your progress & complete quizzes