Skip to Content

Hi everyone, in this blog I’m going to talk about the basic configurations for activate Embedded Analytics in S/4HANA On-Premise 1511 version. This blog is mainly focused on the separated installation of the Fiori Frontend System and S/4HANA Backend system. Let’s dive in to it.

Landscape

Frontend system         SAP Fiori for S/4HANA OP 1511

Bakend system           SAP S/4HANA Backend

An additional SAP Web Dispatcher

Prerequisites

You’ve completed the following configurations as mentioned in the Administration Guide for the Implementation of SAP S/4HANA:

Administration Guide for the Implementation of SAP S/4HANA, on premise edition (1511 FPS 2)

SAP S/4HANA Fiori Foundation Configuration

SAP S/4HANA Fiori Basic Network and Security ConfigurationSAP

Related SAP Notes

2289865 Configuration steps for S/4 HANA Analytics

2106016 Configuration steps for Design Studio in Distributed sFin or S/4 HANA Environments with a Remote Gateway Server

A Step-by-Step Configuration

1. On Backend System

1.1 Activate BW Client

Use transaction SE37 to run function module RS_MANDT_UNIQUE_SET, as SAP documents mentioned, it’s not necessary to setup a separate BW client, so we’ll using the production client 800.

/wp-content/uploads/2016/08/010_1016921.jpg

After donw that, check BW client settings by using function module RS_MANDT_UNIQUE_GET, you should be able to see the client information as an value of the export parameter E_UNIQUE_MANDT.

1.2 Setup User Parameters for DDIC user

Use transaction SU01 to set the following parameters for user DDIC in the working client (if in some case the DDIC doesn’t exist, create it manually)

RSWAD_DEV_MDVERSION = ‘072’

RSWAD_SKIP_JAVA = ‘X’

/wp-content/uploads/2016/08/011_1016922.jpg

1.3 Modification of the Admin Cockpit Installation Objects

Use transaction SE38 run report SAP_RSADMIN_MAINTAIN and insert the following object and value

Object                                                                      Value

SKIP_ADMINCOCKPIT_INSTALLATION                    X

RSDDSTAT_GLOBAL_OFF                                        X

/wp-content/uploads/2016/08/012_1016923.jpg

1.4 Activate Technical Content

Use transaction RSTCO_ADMIN to activate install the Analytic Engine in the working client (if the job failed, try to use DDIC user to perform the activity and check the activate log for more detailed information)

/wp-content/uploads/2016/08/013_1016933.jpg

1.5 Generate Packages for OData Services

Use transaction SE38 to run report EQ_RS_AUTOSETUP without check mode.

/wp-content/uploads/2016/08/014_1016934.jpg

Use transaction SE37 to run function module RSEC_GENERATE_BI_ALL

/wp-content/uploads/2016/08/015_1016942.jpg

1.6 Validate InfoObjects

Use transaction RSD5 to validate the InfoObjects, at the bottom of the screen, choose All InfoObjects and click on Display. Everything should have an green icon in the validation field.

/wp-content/uploads/2016/08/016_1016943.jpg

/wp-content/uploads/2016/08/017_1016944.jpg

1.7 Create a ICF Handler Service

Use transaction SICF to create a Sub-Element entry under /sap/bw/ina with the following information:

     Name: GetServerInfo

     Type: Reference to Existing Service

     In the “Target” tab, select /sap/es/ina/GetServerInfo as the target

/wp-content/uploads/2016/08/018_1016954.jpg

/wp-content/uploads/2016/08/019_1016955.jpg

You may also need to configure the ICF service to using anonymous access if you haven’t setup SSO between Frontend system and Backend system.

/wp-content/uploads/2016/08/0010_1016956.jpg

1.8 Activate ICF Services

Use transaction SICF to activate the following ICF services (with all sub-trees):

/sap/bw/ina

/sap/bw/Mime

/default_host/sap/public/icf_info

2 Frontend System Configuration

2.1 Configuration of OData Service

Use transaction /n/IWFND/MAINT_SERVICE to add Local System Alias to OData Service RSAO_ODATA_SRV, and activate ICF Node, then test the configuration by click on “Call Browser”. You should be able to see the XML format odata service output without any error.

/wp-content/uploads/2016/08/0201_1016967.jpg

/wp-content/uploads/2016/08/0202_1016968.jpg

/wp-content/uploads/2016/08/0203_1016975.jpg

2.2 Activate Query Browser

Use transaction SICF to activate the following ICF service (with sub-trees):

/default_host/sap/bc/ui5_ui5/sap

use transaction /n/IWFND/MAINT_SERVICE to add OData Service VDM_CDSVIEW_BROWSER from the Backend system.

/wp-content/uploads/2016/08/0204_1016981.jpg

2.3 Role Assignment

Assign role SAP_BR_EMPLOYEE to the a user through SU01.

2.4 Activate 0ANALYSIS

Use transaction RSOR to install 0ANALYSIS.

/wp-content/uploads/2016/08/0011_1016976.jpg

/wp-content/uploads/2016/08/0012_1016977.jpg

3 Configure SAP Web Dispatcher

Modify the SAP Web Dispatcher instance profile, the following paths should be routed to the S/4HANA backend server:

/sap/bw/ina

/sap/bw/Mime/DS/Content

Example of the Web Dispatcher instance profile parameters:

wdisp/system_0 = SID=<Frontend_SID>, MSHOST=<FQDN_of_Frontend>, MSPORT=<Frontend_Message_Service_Port>, SRCSRV=*:*, SRCURL=/sap/bc/ui2/flp;/sap/opu/;/sap/bc/;/sap/public/;/sap/bc/ui5_ui5/;/sap/saml2/;/ui2/nwbc/;/resources/sap/dfa/help/, CLIENT=430

wdisp/system_1 = SID=<Backend_SID>, MSHOST=<FQDN_of_Backend>, MSPORT=<Backend_Message_Service_Port>, SRCSRV=*:*, SRCURL=/sap/es/;/sap/bw/ina/;/sap/bw/Mime/DS/Content/, CLIENT=800

wdisp/system_conflict_resolution = 2

icm/HTTPS/verify_client = 0

icm/server_port_0 = PROT=HTTPS, PORT=443, TIMEOUT=300, EXTBIND=1

icm/server_port_1 = PROT=HTTP, PORT=80, TIMEOUT=300, EXTBIND=1

Notice, if the BW version on the Front server is lower than in the S/4HANA backend server, you also need to add the following path to the Web Dispatcher configuration profile parameter:

/sap/bc/ui5_ui5/ui2/ushell/resources/sap/zen

4 Access the Query Browser

https://<web_dispatcher_fqdnport>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#Shell-home


/wp-content/uploads/2016/08/0501_1016982.jpg

/wp-content/uploads/2016/08/0502_1016983.jpg

/wp-content/uploads/2016/08/0503_1016987.jpg

/wp-content/uploads/2016/08/0504_1016988.jpg


Now you can add more Fiori Analytic Apps or even create your own CDS view and create KPI Tile.

/wp-content/uploads/2016/08/0507_1016989.jpg

/wp-content/uploads/2016/08/0506_1016990.jpg



Hope this will be useful to you and I’m willing to receive your feedback!


Regards,

Michael

To report this post you need to login first.

15 Comments

You must be Logged on to comment or reply to a post.

  1. Saubhagya Nayak

    Hi Michael,

    Thanks for publishing the document. It’s a great one and very helpful.

    Just one question on the lumira configuration in S4. There are two out of box tiles for SAP Lumira, “SAP Lumira” and “All Stories”S4 Lumira Setup.PNG. When I click on the SAP Lumira, it opens up a new window saying the “Service cannot be reached”.

    What configuration required to make it work?

    Please find the attached screenshot.

    regards

    Saub

    (0) 
    1. Michael Hu Post author

      Hi Saub,

      I think the problem is the relevant ICF service not activated. I just checked my Fiori system, I didn’t see the /sap/bi/launchpad service in SICF, can you give me some more detailed information about which tile/app you used in this case and the full URL?

      Regards,

      Michael

      (0) 
  2. vivek singh

    Hello Michael,

    the 4th image after heading “access query browser” – is Lumira or analytics facility is also available in query browser.

    (0) 
      1. vivek singh

        understood, whats the sap guidance towards users having access to Query browser.

        As you have shown, there are some analytical capabilities within query browser,? can we provide users access to query browser so that they can navigate from the query browser.

        As in case of HANA live views – query browser doesn’t have analytical capabilities.

        (0) 
        1. Michael Hu Post author

          I think the query browser is for developer especially query CDS views which you can create in S/4HANA and make them exposiable, you can create the KPI tile for end user, so that they don’t have to perform the activities like which measure to use, what’s the key field, what kind of layout to use etc. Or think it this way, query browser is for advanced user, and the advanced user can create the KPI tile for the end user to keep things simple.

          You can check the S/4HANA UI Technical guide

          https://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdffee10356f3b43a35e10000000a44538d/1511%20002/en-US/UITECH_OP1511&hellip;

          There’s also a Youtube series about CDS views and KPI tile, you may want to check it too.

          Modeling with S/4HANA CDS – Creating a Sample Virtual Data Model – YouTube

          Regards,

          Michael

          (0) 
    1. Michael Hu Post author

      Hi Adlin,

      Do you have a Web Dispatcher system in your landscape? You need to install one separately if you haven’t done so. Then change your Web Dispatcher instance profile accordingly!

      Michael

      (0) 
  3. Joyce Teow

    Hi Michael,
    I am new to S/4 Hana embedded analytics. I am confused with the separate instance of BW on Hana and the embedded BW client in the blog mentioned above.
    For the use case if BWoH is in another instance which is EDW for BI reporting/dashboard for a company, linking to S/4 and other source systems. I have few questions for this use case:
    1. Will it still possible to implement the S/4 embedded Analytics here?
    2. is it compulsory to have a embedded BW client in S/4 instance? what will happen to the separate BW client which is in BWoH instance?
    3. CDS query view is exposed to Query browser Fiori App, is this query browser has to be supported by a BW client?
    4. Can CDS query view be direct connected to BOBJ reporting tools, e.g Lumira?
    Appreciate your valuable advice. Thanks.

    (0) 
    1. Michael Hu Post author

      Hi Joyce,

       

      I’m not aware of the separated BW configuation, I know you can use a separated BW client inside the same S4 system.

       

      Regarding the CDS view, CDS view is exposed through Odata service, you activate the Odata service on the Front-end system.

      You can use Lumia connect to CDS views, that’s supported.

       

      Regards,

      Michael

      (0) 
  4. Johannes Bacher

    Hello Michael,

    Thanks for this step-by-step guide. I followed the steps, using a S4 1610 system. When i go to the chartofaccounts query, i get  error messages when launching the design studio:

     

    • Could not instantiate data source DS_1 for query 2CCC…
    • Query 2CCCHARTOFACC is unknown

     

    What would that point to ?

    By the way I was not always sure where your steps should be executed, on backend or frontend.

    Help is appreciated! Thank you,

    Johannes

    (1) 
    1. Michael Hu Post author

      Hi Johannes,

       

      The error seems like an CDS view or OData Service related issue, unfortunately I’m not a good developer I’m afraid I can’t help you to overcome this, but a good way to start is to check the relevant Odata service in backend system in SEGW to see if there’s any issue, as sometimes it does.

       

      Regarding the configuration steps, most of them were done in Front-end system or so called Fiori box, but it depends on your landscape, if you just have a single system with embedded Fiori front-end installation them you’ll need to perform the tasks just in that single system, then you may also choose skip the configuration of SAP Web Dispatcher as well.

       

      Regards,

      Michael

      (0) 

Leave a Reply