Basic Configurations for Activate Embedded

Analytics in S/4HANA

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

2356997 - Configuration steps for Design Studio in Distributed S/4HANA Environments with a Remote
Gateway Server with UI5 1.44 or newer

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.
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’
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
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)
1.5 Generate Packages for OData Services

Use transaction SE38 to run report EQ_RS_AUTOSETUP without check mode.

Use transaction SE37 to run function module RSEC_GENERATE_BI_ALL

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.
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

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.
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

https://www.stechies.com/configuration-steps-design-studio-distributed-s4hana-enviro/

Setting up the Default System Alias which should be utilized by the InA service for data access. The
Default System Alias is set by the RSADMIN parameter RSBICS_INA_RFC_DEFAULT_ALIAS.

This can be set by utilizing the Report SAP_RSADMIN_MAINTAIN (on the front-end server).  User
should Simply specify RSBICS_INA_RFC_DEFAULT_ALIAS as OBJECT and the desired System Alias
(from point 2 above) as VALUE.
Provided RSADMIN settings can be seen by calling transaction SE12 with database table RSADMIN and
then viewing the Table contents.

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.
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.
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.

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
Now you can add more Fiori Analytic Apps or even create your own CDS view and create KPI Tile.