E2E Monitoring Diagnostics Setup - BI Preparations

Overview

 Apply the SAP note corrections summarized in note 1068152: 1065835,1119686,

1127126, 1140438, 1147564 (transport: SD4K900094)

 create BI client 500 (sap_all copy of 000, users from 010)

 run BI configuration steps
 check/create profile for role SAP_BI_E2E and assign to account SAPSUPPORT

 after execution of Diagnostics setup wizard apply several changes and SAP notes to fix
BI objects

 execute final evaluation as per note 979581

Follow the steps of IMG, part SolMan – Configuration – Scenario specific settings – Solution
Monitoring / Reporting – BI Analysis

E2E Monitoring Diagnostics Setup – BI Preparations page 1 of 26

Creation of BI client

Client number 500

Logical system SD4CLNT500

Copy

If you want to get the existing accounts of SolMan client 010 2nd choose the source client User
Masters 010.

Addon BI_CONT 703

Already exists in system upto patch level 8

E2E Monitoring Diagnostics Setup – BI Preparations page 2 of 26

Creation of logical systems for BI client (BD54)

Transport: SD4K900090: E2E setup: logical systems for Solman BI clients

Assign logical system to BI client (SCC4)

Activate the BI client

Run function module RS_MANDT_UNIQUE_SET by choosing Function Module -> Test ->
Execute Single Test from the menu.
Enter the BI client 500 as the value for parameter "i_mand".
Choose Execute.

Check system changeability

In SE06
Choose Administration -> Set System Change Option.
Check that the namespace/name range with prefixes /BI0/ and /BIC/ is set to Modifiable.
If the namespace is set to Not Modifiable, set it to Modifiable.
Save it.

E2E Monitoring Diagnostics Setup – BI Preparations page 3 of 26

E2E Monitoring Diagnostics Setup – BI Preparations page 4 of 26
Creation of BI account

Follow the instructions of the IMG docu:

For roles and authorization values, see the SAP Solution Manager Security Guide in the Service
Marketplace -> SAP Components -> SAP Solution Manager 4.0.

Activities

Create Background User

1. Create the user ALEREMOTE, of type System User.

2. Assign the profile S_BI-WHM_RFC to it.

Assign Background User

3. Choose the transaction.

o When you first call the transaction RSA1, a dialog box Replicate Metadata is
displayed, as well as Activate Replicated Metadata. Choose: Replicate As Well.

o If another dialog box appears, with the message Unknown data source. Data
source 0BBP_TD_PO_1 is not yet in the BI system. How is the object to be
created in the BI system?, choose: This and the following 16 as 3.x data source.

o If the dialog box Modelling Area Documentation - Start modelling view

navigation documentation in a new window? appears, choose: Do not ask this
question again and Yes.

(You can also access this function from the main menu: Data Warehous
Workbench -> Modelling Documentation).

4. Choose Settings -> Global Settings in the menu

5. Enter the name of the background user created, ALEREMOTE, in the field BW ALE
User.

6. Save

For further information, see SAP note 410952.

Additional accounts created:

Account BI_USER, type dialog, profile SAP_ALL created (s64_report)

Account ALEREMOTE, type system, profile S_BI-WHM_RFC created (s64_inst)

E2E Monitoring Diagnostics Setup – BI Preparations page 5 of 26

E2E Monitoring Diagnostics Setup – BI Preparations page 6 of 26
In transaction RSA1:
(to check / reactivate the datasources:
- Open the source systems
- Open BI – BI client SD4
- Right click and choose Activate

Global settings (for BI background user)

E2E Monitoring Diagnostics Setup – BI Preparations page 7 of 26

Connection of source system

Follow the instructions of the IMG docu:

In this IMG activity, you define the data for communication between the client of the source
system (Solution Manager) and the BI client. You create an RFC connection from the BI client
to the client of the source system and from the client of the source system to the BI client.

Activities

1. In the left-hand screen area, choose Modeling.

2. Choose Source Systems.
3. Select the BI folder in the Source Systems column.
4. Choose Create with the right-hand mouse button.
A dialog box appears in which you define the communication via RFC connections.
Proceed according to your prerequisites:
o As yet there is no RFC connection from BI to the source system

Enter the data for the source system (server; SID; system number), under
Create New Destination.
o There is already an RFC connection to the source system

Choose the RFC connection in the field Existing Destination.

Note: You must specify an RFC connection, even if your production Solution Manager
client is your BI client , e.g.: <SID>CLNT<client>.

5. Enter the name (such as ALEREMOTE) and password for the background user in the
source system, under Background User in Source System.
The background user is automatically created in the source system as a system user
with profile S_BI-WX_RFC and is assigned to the generated RFC connection.

6. Enter the password of the background user that was created in the BI client, under
Background User in BW.
Note: If your production Solution-Manager client is your BI client, specify the user
ALEREMOTE for source and BW system, and assign the profile to it.

7. Choose Continue.

8. Log on with your administration user in the client of the source system.

9. Confirm the dialog box for the user and password.

10. If a dialog box appears for Replicating the Metadata, choose Replicate As Well.

E2E Monitoring Diagnostics Setup – BI Preparations page 8 of 26

 11. In the subsequent dialog boxes, choose these and all subsequent DataSources 3.x
(ISFS) as the DataSources.

12. In the subsequent dialog boxes, choose these and all subsequent 8 DataSources 3.x
(ISFS) as the DataSources.

When the source system is successfully created in the BI client, the system creates the
following RFC connections:
o In the source system: <SID>CLNT<CLNT> With Logon User (such as ALEREMOTE).

o In the BI client: <SID>CLNT<CLNT> With Logon User (such as ALEREMOTE) and

<SID>CLNT<CLNT>_DIALOG

E2E Monitoring Diagnostics Setup – BI Preparations page 9 of 26

Check
Use

After the error message: user DDIC may not do changes …

E2E Monitoring Diagnostics Setup – BI Preparations page 10 of 26

… check the RFC destination SD4CLNT010 and change the logon account from DDIC to
ALEREMOTE

Repeat the step and choose the existing RFC destination now:

Replicate as well

E2E Monitoring Diagnostics Setup – BI Preparations page 11 of 26

E2E Monitoring Diagnostics Setup – BI Preparations page 12 of 26
Change BI authorization concept

Transaction rscustv23

Transport request: SD4K900092 FSCHWEIT E2E setup: BI authorization concept

Roles and Authorizations

Check that role SAP_BI_E2E has an assigned / generated profile and that profile is active and is
assigned to the account SAPSUPPORT.

E2E Monitoring Diagnostics Setup – BI Preparations page 13 of 26

CCMSBISETUP

After the execution of the Diagnsotics Setup Wizzard:

as per SAP note 1107804 some corrections needs to be applied:

Checked in RSA1 if 0SM_SMD_ and 0SMD_PI2D exists: 0SMD_PI2D was missing.

Therefore: perform transaction ccmsbisetup manually

(ressourceintensive)

After this, download the transport SMXK900045 (attachement of note 1107804) and import to
client 500.

Then follow the detailed instructions of the note to adjust the infoprovider:

E2E Monitoring Diagnostics Setup – BI Preparations page 14 of 26

Transfer selection

Then check that in area Modeling – the provider 0SMD_MPIH is active and based on InfoCubes
0SMD_PI2H and 0SMD_PI2D

Transfer the related queries

E2E Monitoring Diagnostics Setup – BI Preparations page 15 of 26

Transfer

In the next screen mark all queries and choose Install

E2E Monitoring Diagnostics Setup – BI Preparations page 16 of 26

Last step:
Transfer the web templates 0TPL_0SMD_XPI*

Transfer

Again: Install:

Done.

E2E Monitoring Diagnostics Setup – BI Preparations page 17 of 26

Next correction:
Since there are many dumps of type NO_DBROUTID_FOUND in the system we need to apply
note 1119766 (inactive BI objects)

Logon to the BI client and call tx. RSD5

If you check for the active object 0DATE (Version: Active/Revised) -> you’ll see nothing
Change Version to: Content and choose Display:

E2E Monitoring Diagnostics Setup – BI Preparations page 18 of 26

The object is defined, but inactive.

To activate the object:

From the main screen choose

Business Content – Copy Infoobjects – Subsequently Activate

E2E Monitoring Diagnostics Setup – BI Preparations page 19 of 26

Note: if the object is active you’ll see a symbol in the same line of the info object:

Done.

E2E Monitoring Diagnostics Setup – BI Preparations page 20 of 26

Follow the same procedure for the objects:
- 0DATE
- 0TIME
- 0REQUID
- 0CALDAY
- 0CALWEEK
- 0CALMONTH
- 0CALQUARTER
- 0CALYEAR

Because object 0DATE was not available in an active version during the setup the dependent
time characteristic objects 0CALDAY, 0CALWEEK, 0CALMONTH, 0CALQUARTER and 0CALYEAR
needs to be activated again.

After the activation the name and a clock symbol will appear:

E2E Monitoring Diagnostics Setup – BI Preparations page 21 of 26

After all activations and since the object 0TIME was not active at the beginning the report
CCMSBI_SETUP_E2E needs to be executed to install the multi-provider 0CCMSMTPH (duration
15-20 minutes).

E2E Monitoring Diagnostics Setup – BI Preparations page 22 of 26

Final checks and validation of correct setup

See note 979581: Installation and Configuration of CCMS BI Content

Follow the steps mentioned in this note.

Check status of the job BI_TCO_ACTIVATION (report RS_TCO_ACTIVATION): cancelled:

Call tx. RSTCO_ADMIN in BI client:

Check the status of the activation:

E2E Monitoring Diagnostics Setup – BI Preparations page 23 of 26

Display Log:

 the content is not yet activated completely

To finalize the setup, click on “Start Installation”:

Check the status of the job and the joblog, additionally you can also check the log status in
transaction RSTCO_ADMIN.

E2E Monitoring Diagnostics Setup – BI Preparations page 24 of 26

Errors:

See note 979581, chapt. 9. for object 0IOBJNM:

Call tx RSD5

Checked object, is active, everything seems to be ok.

Execute RSTCO_ADMIN (job BI_TCO_ACTIVATION) again.

Now everything looks ok:

E2E Monitoring Diagnostics Setup – BI Preparations page 25 of 26

Evaluation of Infoproviders for SM Diagnostics (similar to the check procedure of note 979581
for the CCMS Infoproviders)

RSA1

Each Infoprovider should be active (no white or gray symbols)

E2E Monitoring Diagnostics Setup – BI Preparations page 26 of 26