SAP Solution Manager

Basis

1
Table of Contents

1. Landscape Details
2. Initial Configuration
3. Maintainence Optimizer
4. Solution Monitoring
5. Central System Administration
6. EarlyWatch Alerts
7. Scot Configuration – To send mails from SAP
8. Trex Installation & Configuration
9. ServiceDesk & Change Request Management – Basis related configuration
10.Solution Manager Security
11.RFC Troubleshooting

2
1. Landscape details

2. Initial configuration

Initial configuration steps are performed from SPRO->Configuration->Basic Settings->

Wizard-based Initial Config.

3
The main aim of the initial config. Task is to create RFC destinations to Satellite systems &
to create a Solution Manager solution, which consists of Solution Manager+Satellite
systems (as show in landscape details screenshot)

Activities done in Initial configuration-:

A.)Initial Configuration Part 1-: In this step, we create the SOLMANADMIN id,
add include SAP support portal ID for communication with SAP.

4
B.)Maintain Profile parameters-: In this step we maintain the following profile
parameters. It is mandatory to include the following entries,
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
icm/host_name_full = shvsolman.supergas.com
icm/server_port_1 = PROT=SMTP,PORT= <> 0 e.g.:25000
login/no_automatic_user_sapstar = 0

C.)Assign Logical systems-: Ensure that all the clients in Solution Manager &
Satellite systems have a logical name assigned.

5
D.) Maintain SAP Customer Numbers-: In order to be able to approve
patches or to send Support messages we need to tell the solution manager
which SAP OSS-id has to be used for communication with SAP, we include the id
in this SPRO step.

E.) Initial Configuration Part II-: This step is performed automatically. In this
step the following activities are performed automatically,
Activate BC Set
Get SAP Components from SAP
Generate Business Partner Screen

Hint-: Before running this step, check SAP-OSS rfc pings with a reply OK, if not
configuration problems occur.

F.) Schedule Background Jobs-: The following SAP Standard jobs need to be
scheduled in solution manager system. This can be done automatically in this
SPRO step.

6
 Complete List of scheduled jobs in SHS

G.) Setup System Landscape-: In this SPRO step we connect the satellite
systems (SHD,SHQ,SHP) to solution manager(SHS) via RFC destinations & we
assign all these systems to logical components.
Pre-requisite-: Ensure that the admin id used during RFC setup, has authorization
objects S_RFC & S_RFCACL included.

The RFC destinations & Logical components are created/assigned in the following
wizard,

System Additon Wizard

7
8
RFC Wizard

9
10
11
Note-: Uncheck this option if it is checked by default, since RFC for system monitoring
must be enabled only during Solution Monitoring scenario configuration.

Logical Component Wizard

12
13
After this step completes, you would successfully added the satellite sytem to the solution
manager Landscape.

H.) Creating a Solution-: Once we have connected all Satellite Systems via
RFC, & included them into a logical component, we have to create a New
SolutionManager solution. This is done from DSWP t-code, as described in the
below steps.

14
Click create & follow the self-explanatory prompts.

Once the solution is created, you have to add the Logical component (defined in Step7),
to the newly created solution. This is how it is done

Adding Logical component to Solution directory

Navigate to DSWP -> <Select your Solution> ->Solution Landscape->Solution Landscape

Maintainence. Then add your logical component to the solution & Save.

15
Note-: The systems for which you require Earlywatch alerts, have to be put in Solution.
The green color in the above screenshot, indicates that the systems, have been put into
the solution.

16
3.) Maintainence Optimizer Configuration/Usage

SAP Patches, require approval before they can be downloaded. This is performed from
Maintainence Optimizer section of DSWP.
a.) Configuration-: In solution manager 7.0 & above all the required BC Sets are
activated by default. The only pre-requisite is to Create a solution. (This is already
done in the above section titled Creating Solution.

b.) Troubleshooting/Checking-: before we start using Maintainence Optimizer

Check if solution is created & ensure that the systems that require patches are part of
the solution.
Check that the Read RFC Destinations for the satellite systm are pinging with reply OK
(For more details to check RFC destination ping see Page#)
Ensure that the admin id, which is used to create the Maintainence Transaction, has a
S-USER ID mapped in AISUSER t-code.

Ensure that SAP-OSS RFC replies ping with OK & the correct S-User ID is maintained

c.) Maintainence Optimizer Usage-:

1)Create a new Maintaince transaction for the system which has to be patched.

17
2)Select the System & click Continue

3)Click Find Download Files & then select the Target Stack version

18
4)Select the files to be downloaded. Note that this is the recommended way to select the list
of patches, since the selection is done automatically by Solution manager, after it reads the
existing configuration of the Satellite systems. If we were to do this manually from SAP
Marketplace, we would risk applying incorrect patches to the system.

19
5)Download basket is selected by default, You just have to click on the Select Download
Type button

7)Now that the files have to added to the basket, its time to approve the. Click on the
Confirm files in Download Basket.
Note-:Without approval its impossible to download patches, which is why M.O. is so
important to maintain a customers SAP Landscape.

20
8)In the Pop-Up window that opens, select the list of files pending approval & hit the
Confirm download button

21
9)Finally click Save.

10)Now go to your SAP Download Manager application. Now the approved patches would
appear in the list. You can then download the patches & apply them suing SPAM/Saint
procedures.

22
 11)After you have successfully applied the patches, Open the maintenance transaction
again, & close the maintainence transaction using the option End Maintainence

4.) Solution Monitoring Configuration

Solution Monitoring in SHV, is configured in such a way that Critical alerts are
triggered to Basis team E-Mail, since they have to be given immediate attention. Non-
critical alerts are monitored from Solution Monitoring section in DSWP. This strategy is
implemented to minimize the no. of alerts that are sent in mail, but at the same time
monitoring non-critical alerts via solution monitoring ensures that non-critical alerts are
also given attention.

I.) CCMS Alert Configuration-:

Solution Manager CCMS Monitoring setup
Login to Solution Manager client 000

23
GO TO RZ21

24
25
Assign password “ init11” and then login this user as dialog then change the password as “
sol123 “ and then change this user as communication user

26
27
28
Create csmconf file

29
30
this file has to be register into all satellite systems
By default in Solution manager Agents for remote systems will not be there

31
Registering CSMCONF file into satellite systems
Login to the Satellite systems as “ <sid>adm “
Create directory sapccm4x in the locations “ d:\usr\sap\PCA\DVEBMGS01\ log\ sapccm4x

32
shvdev:shdadm 20> ls -la SAPCAR
-rwxr-xr-x 1 shdadm sapsys 6087388 Jul 06 2007 SAPCAR
shvdev:shdadm 21> cp SAPCAR /usr/sap/SHD/DVEBMGS00/log/sapccm4x
shvdev:shdadm 22> cd ..
shvdev:shdadm 23> cd ..
shvdev:shdadm 24> cd ..
shvdev:shdadm 25> cd ..
shvdev:shdadm 26> pwd
/
shvdev:shdadm 27> cd /usr/sap/SHD/DVEBMGS00/log/sapccm4x
shvdev:shdadm 28> ls -ltr
total 53960
-rw-r----- 1 shdadm sapsys 887 Mar 16 14:07 csmconf

33
-rw-r----- 1 shdadm sapsys 15436682 Mar 16 14:07 ccmagent_42-10004775.sa
r
-rw-r----- 1 shdadm sapsys 6087388 Mar 16 14:09 SAPCAR.EXE
-rwxr-xr-x 1 shdadm sapsys 6087388 Mar 16 14:14 SAPCAR
shvdev:shdadm 29> SAPCAR
usage:

create a new archive:

SAPCAR -c[vir][f archive] [-P] [-C directory]
[-A filename] [-T filename] [-X filename]
[-p value] [-V] file1 file2 ...

list the contents of an archive:

SAPCAR -t[vs][f archive] [file1 file2....]

extract files from an archive:

SAPCAR -x[v][f archive] [-R directory] [-A filename]
[-V] [file1 file2....]

verify the archive:

SAPCAR -d[v][f archive] [-V] [file1 file2....]

append files to an archive:

SAPCAR -a[v][f archive] file1 [file2....]

merge two archives:

SAPCAR -m[v]f "source target"

check availability of files to be processed:

SAPCAR -l [-A filename][-X filename] [file1 file2...]

34
other options:
-a : append files to an archive
-A FILE : get names to include from file FILE
-backup : run in backup mode: include ACL data
(supported by UNICODE SAPCar on Windows platforms only)
-C DIR : change to directory DIR
-e : redirect output from stdout to file sapcar_output
-f FILE : use archive file FILE (default DEFAULT.SAR)
-flat : don't preserve file path when extracting files
-g : ignore case of of archive names while extracting,
testing or listing archives
-h : do not change permissions of existing directories
during extraction
-i : ignore inaccessible files while creating an archive
-l : check availabilty of files to be processed
-lower : convert filenames to lowercase while extracting
-m : merge two archives
-n : print statistical information
-p octalvalue : set permissions of all files in archive to value
-P : use absolute path-names (use carefully)
-r : do not resolve symbolic links/shortcuts while creating
an archive
-R dir : use dir instead of current directory
-s : do free space check
-T FILE : rename files to be included in FILE
-v : verbosely list files processed
-V : compute or verify checksum (obsolete, always set,
for backward compatibility)
-X FILE : get names to exclude from FILE

35
examples:
create archive with all files and directories in the current directory
including point files:
SAPCAR -cvf MY.SAR .

create archive with all files and directories in the current directory
without point files:
SAPCAR -cvf MY.SAR *
Note that SAPCAR treats "*" and "?" as wildcard characters. The former
matches any character string, while the latter matches any single
character.

create archive with a complete directory and directory rights:

SAPCAR -cvf MY.SAR dir

create archive with all files of a directory without the directory

itself:
SAPCAR -cvf MY.SAR dir/*
if during extraction with SAPCAR -xvf MY.SAR the directory dir does not
exist it will be created with rights 755

create archive with only the files of a directory

SAPCAR -cvf MY.SAR -C dir .
or better
(cd dir; SAPCAR -cvf ../MY.SAR .)

merge two archives:

SAPCAR -mvf "source-archive.sar target-archive.sar"

36
append files to an archive:
SAPCAR -avf archive.sar file1 file2 file3

extracting/verifying files:
If you try to extract files from an archive that is not a valid SAPCAR
archive according to the version 2 specification SAPCAR assumes an archive
of the old format and automatically invokes the appropriate extraction
routine. If it still cannot handle the archive it will stop execution.
Notice that extracting out of old archives only works with the command
options known to the old CAR application.

using absolute pathnames:

If you create an archive with absolute pathnames the files will be
extracted with exactly these pathnames! SAPCAR does not cut the first
slash like the UNIX tool tar.

specifying a list of archives for extracting/verifying/listing:

Enclose the list with double quotes.
If there is no whitespace in any archive path the list must be separated by
space or comma; e.g.
SAPCAR -xvf "ARCHIVE1.SAR ARCHIVE2.SAR"
If at least one archive path contains whitespace the list must be comma
separated; e.g.
SAPCAR -xvf "ARCHIVE WITH BLANK.SAR, ARCHIVE.SAR, ARCHIVE2.SAR"

specifying a single archive path containing whitespace:

Enclose the archive name with double quotes.
creating: You must not append a comma except it is part of the path; e.g.
SAPCAR -cvf "ARCHIVE WITH BLANK.SAR" *
extracting/verifying/listing: You must append a comma; e.g.

37
 SAPCAR -xvf "ARCHIVE WITH BLANK.SAR,"

In order to extract/verify/list more than one archive using wildcards you

have to quote the file name argument in order to bypass wildcard evaluation
by the shell. So a call like
SAPCAR -xvf K*.sar
will result in only one archive beeing extracted,
whereas
SAPCAR -xvf "K*.sar"
will have SAPCAR extracting all archives in the current directory that
match the pattern "K*.sar".

using A, T and X option:

All entries in the specified files are treated relative to the current
working directory unless the entry is an absolute pathname (in this case
the relevant file will be archived with an absolute pathname).
If you want to specify a directory path in these files use the slash ("/")
as path delimiter.

Use the pipe sign ("|") to separate old and new names in a T file when
these names contain whitespaces. If neither the old file name nor the new
one contains any whitespaces you may use whitespaces as delimiter between
old and new name (that means a valid CAR rename file is also a valid SAPCAR
rename file and hence may be given with the -T option).
Note that pattern matching is not supported for entries in -A, -T and -X
files (i.e. "*.cpp" will not result in processing all cpp-files
in the current directory).

Lines starting with "#" as the first non whitespace character will be
ignored by SAPCAR (this also holds true of lines containing only

38
whitespaces).

If you insert a directory name in the specified file the complete

directory with the directory rights will be included in the archive.

If you specify dir/filename only this file will be included in

the archive. During extraction the directory dir will be created if
it does not exist.

using -C option:
All relative filenames in the command line are treated as relative
to the specified directory.

This is sapcar, release 640_REL build 916920

compiled on Jul 5 2007, 20:30:57, 64bit

shvdev:shdadm 30> pwd

/usr/sap/SHD/DVEBMGS00/log/sapccm4x
shvdev:shdadm 31> ls
SAPCAR ccmagent_42-10004775.sar
SAPCAR.EXE csmconf
shvdev:shdadm 32> SAPCAR -xvf ccmagent_42-10004775.sar
SAPCAR: processing archive ccmagent_42-10004775.sar (version 2.01)
x ccmagent_readme.txt
x ccmsping
x dsrlib.o
x libjmon.so
x sapccm4x
x sapccmsr

39
SAPCAR: 6 file(s) extracted
shvdev:shdadm 33> pwd
/usr/sap/SHD/DVEBMGS00/log/sapccm4x
shvdev:shdadm 34> cdpro
shvdev:shdadm 35> ls
DEFAULT.1.PFL SHD_DVEBMGS00_shvdev.29JAN2007
DEFAULT.BAK SHD_DVEBMGS00_shvdev.BAK
DEFAULT.PFL SHD_DVEBMGS00_shvdev190908
SHD_DVEBMGS00_shvdev START_DVEBMGS00_shvdev
SHD_DVEBMGS00_shvdev.08JAN2007 START_DVEBMGS00_shvdev.1
SHD_DVEBMGS00_shvdev.1 dev_dpmon
shvdev:shdadm 36> cd /usr/sap/SHD/DVEBMGS00/log/sapccm4x
shvdev:shdadm 37> ls
SAPCAR ccmsping sapccm4x
SAPCAR.EXE csmconf sapccmsr
ccmagent_42-10004775.sar dsrlib.o
ccmagent_readme.txt libjmon.so
shvdev:shdadm 38> sapccm4x -R pf=/usr/sap/SHD/SYS/profile/SHD_DVEBMGS00_shvdev

INFO: CCMS agent sapccm4x working directory is /usr/sap/SHD/DVEBMGS00/log/sapccm

4x

INFO: CCMS agent sapccm4x config file is /usr/sap/SHD/DVEBMGS00/log/sapccm4x/csm

conf
INFO: Central Monitoring System is [SHS]. (found in config file)

additional CENTRAL system y/[n] ? : y

SAP system ID: : SHS
additional CENTRAL system y/[n] ? : n

40
INFO: creating ini file /usr/sap/SHD/DVEBMGS00/log/sapccm4x/sapccmsr.ini.

INFO:
CCMS version 20040229, 64 bit, multithreaded, Unicode
compiled at Feb 18 2008
systemid 324 (IBM RS/6000 with AIX)
relno 6400
patch text patch collection 2008/1, OSS note 1129577
patchno 221

INFO Runtime:
running on shvdev AIX 3 5 00C88E7B4C00
running with profile /usr/sap/SHD/SYS/profile/SHD_DVEBMGS00_shvdev

INFO profile parameters:

alert/MONI_SEGM_SIZE = 60000000
alert/TRACE =1
SAPSYSTEM = 00
SAPSYSTEMNAME = SHD
SAPLOCALHOST = shvdev
DIR_CCMS = /usr/sap/ccms
DIR_LOGGING = /usr/sap/SHD/DVEBMGS00/log
DIR_PERF = /usr/sap/tmp

INFO:
pid 2662644
INFO: Attached to Shared Memory Key 13 (size 60211232) in pool 10

INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application s

erver shvdev_SHD_00, created with version CCMS version 20040229, 64 bit single t

41
hreaded, compiled at Feb 18 2008, kernel 6400_20020600_221, platform 324 (IBM
RS/6000 with AIX)]
segment status ENABLED
segment started at Tue Jan 13 00:21:17 2009
segment version 20040229

****************************************************

********************** SHS **********************

****************************************************

Please enter the logon info for an admin user of the

central monitoring system [SHS].

The user should have system administrator privileges

client [001]
user [SOLMANADMIN]
language [EN]
trace level [0]
application server [shvsolman]
system number [00]

Logon info ok n/[y] ? :

42
Once it finishes then you can see Agents in remote systems by login in solution manager
RZ21

43
Activate central system dispating in client 000

44
SAP_CCMS_CENSYS_DISPATCHER must be running in client 000

Then select Assign Central auto reaction

45
II.) Solution Monitoring Alert Configuration-:
Non-critical alerts are handled via Solution Monitoring. The configuration is done via
DSWP t-code
Configuration steps are as follows,

46
Go to DSWP->Operations Setup->System Monitoring->Setup System monitoring

Select the Systems for which monitoring is to be enabled

47
Check CCMS Connectivity, If you see any Red icons under the status section (in the
below screen), then you must assign RFC for system Monitoring from SMSY.

48
How to assign RFC for system monitoring from SMSY

49
After fixing the RFC dest. For system monitoring, hit the Save button. Now you will
notice that the systems for which monitoring has been enabled, the icon changes from

to .

Now expand the system & select the Monitoring attributes eg-: Response time,
Tablespaces etc…

50
Checking the Alerts-: This is done via, Operations tab in DSWP

Clicking on the Red Icon takes you the screen, which displays alerts as per the
component.

51
Now, click on the component to see all open alerts that exist for this system,

52
Confirming an Alert-: An alert that has been checked, can be confirmed by selecting
the alert & clicking the Reset button

53
5.) Central System Administration

Central System administration, is used to clearly Catalog the list of basis activities that are
to be performed for a SAP system on a Daily/Weekly/Monthly basis.
Using C.S.A to perform maintainence activities on a SAP systems, is analogous, to using
Tasklist to perform maintainence on an aircraft. Meaning that all maintainence activities
performed on a system are clearly logged, in order to minimize errors during maintainence

How to enable C.S.A for a SAP Satellite system-:

Go to DSWP->Operations Setup->Solution Monitoring->System Administration &
choose Central system administration.
Note-: The same RFCs used for system monitoring are used for C.S.A. also.
For each satellite system, select the list of activities & the Frequencies at which each of
those tasks should be performed.

54
3) Viewing Open Tasks-: The tasks that are to be performed on a particular system, will
appear on the Open tasks status. This is accessible from DSWP-> Operations (as shown in
below screenshot)

55
56
(List of tasks that have to be performed for SHD system)

Clicking on a task, takes you to the Task administration screen. From this screen you can
navigate to the satellite system to perform activities on the task. Once work is complete
you can confirm the task by clicking done. You can also add some notes related to the
task in the TaskNotepad/Logbook.

57
6.) Earlywatch Alerts
The benefit of using solution manager in your SAP landscape, is that Early watch checks
can be performed on demand, rather than sending SDCC data to SAP, & waiting for a
formatted Earlywatch check report.

Activating Earlywatch Alert system in Solution Manager-:

The following activities need to be performed to activate Earlywatch,
1) Ensure that your satellite systems are connected to Solman, & Read RFC
destinations are Pinging OK.
2) Ensure that your satellite systems, have the latest ST* patch levels as in your
solution manager system.
Note-: If you don’t have the latest patch levels, you will notice that your earlywatch
session being pushed from Solman system, don’t appear in your SDCCN task list in
Satellite system.
3) Ensure your satellite system has been put in the solution.

58
 Refer to Page16
4) Deactivate Old SDCC connection from the satellite system.
Hint-: When adding Solution Manager as master system, the system will prompt you
to deactivate old sdcc connection. Confirming the prompt will automatically deactivate
old SDCC data.
4)Add solution manager as master system
Go to SMSY ->Environment->Solman Operations-> Admin SDCCN.
In the pop-up choose Add system & select the system

Now activate SDCCN for the selected satellite system & also assign your solution
manager system as Master system.

59
Scheduling a Earlywatch session from Solution Manager-:
1)Go to DSWP->Ops. Setup->Sol. Monitoring->Earlywatch alert->Setup Earlywatch
alert.
Note-: Since the schedule Earlywatch alert screen is based on Abab Webdynpro, some
time it will take lot of time, before the white screen changes & for you to see the
schedules screen.

In this screen, you can select which day of the week, whether the alert has to be
forwarded to SAP. You can also deactivate schedules for a system from here.

Tracking/Troubleshooting Earlywatch Alerts-:

1)Go to DSWP->Operations->Sol. Monitoring->Earlywatch alert. You will see a list of
schedules.

60
2) Icons in Earlywatch system
, , -> Earlywatch report generated successfully.
-> Earlywatch session has been scheduled. Now the earlywatch job has to run in
the satellite system & after the SDCC data is generated, it is pushed back to the
Solman system.

-> After EWA data is gathered satellite system, the icon changes to . It
means a job has to run in solution manager system, to generate the Earlywatch
report. Once the report is generated successfully you will see the , , icons.
3) To check if any earlywatch sessions are due in a particular satellite system, run the
Refresh session job in the satellite system.
Go to SMSY ->Environment->Solman Operations-> Admin SDCCN

61
Select the satellite system & create a new refresh session task

The task would run for a few mins, then you will see the list of Earlywatch sessions

62
(If you don’t see the Earlywatch sessions, despite running Refresh session task, you
will have to update your ST* Patches)

Troubleshooting EarlyWatch alerts-:

1) Check RFC destination from SDCCN

63
 Warning-: For systems that send there data to SAP, ensure that SDCC_OSS
destination is not flagged as active. This is mandatory since the data is sent to SAP
via the Solman system.

Ensure that the RFC destination to your Solman system

eg-:SM_SHSCLNT001_BACK, returns check OK.

2) Check Background Jobs-:

The following jobs needs to be scheduled, for the Earlywatchs ervice to work
correctly.
SM:EXEC SERVICES & /BDL/TASK_PROCESSOR

For more details on Earlywatch Reporting, refer to the following section of SAP
Marketplace
http://service.sap.com/rkt-solman->Solman 7.0->Technology Consultant/Sys.Admin->Earlywatch & Solution
Reporting Track.

7.) SCOT Configuration

To set the parameters:RZ10

icm/server_port_1 PROT=SMTP,PORT=25000
icm/host_name_full shvsolman.supergas.com

64
Goto SICF

To activate the SMTP service

65
SCOT:

66
Double click on SMTP

67
To Select the Internet
Set *

68
Go to

69
Click on job

70
To scheduled the background job SAPCONNECT INT SEND
Every 5 mints job

71
72
SBWP

73
SOST

74
7.) Trex Installation & Configuration
Trex7.1 has been installed in SHV landscape, in order to enable the search functionality
for Solution Database.
Trex is installed on the SHVSOLMAN machine into folder E:\usr\sap\TX7 folder.
The video file trex71_installation.camrec, clearly outline the sequence of steps performed
during the installation.

Once trex is installed, you will notice the TX7 <sid>, in the SAPMMC,

75
 Starting/Stopping Trex-: Use the standard SAP Start/Stop procedure to control
Trex from MMC. The only condition is that Trex(TX7 instance), has to always
start after SHS system has started completely, else you will notice that
applications depending on Trex (Solution database) will fail.

Administering Trex-: Trex can be administered by running TrexAdmin.bat from the

location E:\usr\sap\TX7\TRX07.

Checking Trex RFC destination-:

RFC connection to Trex is the most common Point of Failure from basis perspective. This can
be monitored in 2 ways,
1) From the Trex admin console, click connect admin tool, now you should see the
screen below.

76
 2) From SM59, check TREX_CONN_TX7 RFC destination (under TCP Connections
section)

Reasons for Trex RFC Failure-:

1) Problem- Trex has started before Solman has started.
Solution1- Try restarting the Trex instance & retry RFC connection check.
Solution2- Ensure that the SAP gateway used for communication between and
Solman<->Trex is active. In SHV the Solution managers systems gateway is used for
communication.

77
 To check if this gateway is active, telnet shvsolman sapgw00 (sapgw00=3300, this
entry is made in etc/services file). The telnet screen response must be

It should not be

2) Trex connection must also be checked from SRMO t-code. This check is to
ensure that Trex connection functionality for indexing & searching is OK.

78
Select RFC dest. For I & selection Connection test as shown in below screen.

The test should return the below screen,

79
 Repeat the steps to do connection test for RFC for S also.

For further understanding of the Trex system, please refer to TREX71InstallSingleHost.pdf

(Sap’s Trex InstGuide).

8.) ServiceDesk & Change Request Management – Basis

related configuration

1)Define Service Desk destination in Satellite system-: Here you define that messages raised
from Satellite system must go to Solution Manager system.
Go to SM30 & enter BCOS_CUST (in Satellite system(

80
Apart from this you must also a mention the client to which the message should be forwarded
to, in the RFC destination as follows,
1) Select the RFC dest. set against the OSS_MSG (in bcos_cust)

81
Finally, do the Authorization check for the RFC. It should give the OK status.

2) Setting authorizations for creating Service desk Messages-:

Ensure that the user-ID used in the RFC destination, example SOLMANSHD (shown
in above screenshot, has the following roles (in Solution Manager).
o Z:SAP_SV_FDB_NOTIF_BC_ADMIN
o Z:SAP_SV_FDB_NOTIF_BC_CREATE

Note-: If these roles are not assigned you will receive error, when end-user creates
a service desk message.

82
 9.) Solution Manager Security
Authorizations for Service Desk & Change Request Management scenarios is handled by using
customized roles create using the following SAP Standard roles.

1.)Service desk Authorizations-:

The following roles, give the authorization to create messages to End-Users & process messages
authorization to support teams
Z_SAP_SUPPDESK_CREATE Role for Support Desk Creator
Z_SAP_SUPPDESK_DISPLAY Role for Support Desk Display User
Z_SAP_SUPPDESK_PROCESS_DEV Role for Support Desk Processor for DEV Specific Authorizaztions
Z_SAP_SUPPDESK_PROCESS_ERPHEAD Contains additional authorizations for ERP Heads
Z_SAP_SUPPDESK_PROCESS_RML Role for Support Desk Processor for RML & Corp Support

The assignment of these roles is the following Matrix

ENDUSE RM CORP DEV ERP SAP
R L SUPP TEAM HEAD HEAD BASIS
Z_SAP_SUPPDESK_CREATE X
Z_SAP_SUPPDESK_PROCESS_RML X X X X X
Z_SAP_SUPPDESK_PROCESS_DEV X X X X
Z_SAP_SUPPDESK_PROCESS_ERPHE
AD X X

The following roles, give access to Division specific ServiceDesk Reports

Z_ZSRVDESK_ABAP_REPORT
Z_ZSRVDESK_ALL_REPORT
Z_ZSRVDESK_BASIS_REPORT
Z_ZSRVDESK_CS_REPORT
Z_ZSRVDESK_FI_REPORT
Z_ZSRVDESK_HR_REPORT
Z_ZSRVDESK_MM_REPORT
Z_ZSRVDESK_PM_REPORT
Z_ZSRVDESK_PS_REPORT
Z_ZSRVDESK_SD_REPORT

The Status Field, is the Key to restricting access in servicedesk messages. This is controlled using Auth.
Object B_USERSTAT.

83
2.)Change Request Authorizations-:
The following roles, give the authorization to create & process change requests.

Requester RML ERPHead SAPHead IThead SAPDevTeam Basis

Z_SAP_SOCM_REQUESTER X X X X X X X
Z_SAP_SOCM_CHANGE_MANAGER_RML X
Z_SAP_SOCM_CHANGE_MANAGER_ERH X
Z_SAP_SOCM_CHANGE_MANAGER_SH X
Z_SAP_SOCM_PRODUCTION_MANAGER X
Z_SAP_SOCM_DEVELOPER X
Z_SAP_SOCM_ADMIN X

The Status Field, is the Key to restricting authorizations in Charm tickets. This is controlled using Auth.
Object B_USERSTAT.

84
10) Troubleshooting RFC issues in Solution Manager
Since solution manager uses RFC destinations to connect to Satellite systems, it is very critical to ensure that
RFC dests are working correctly. Unlike in standard R3, there is a wizard in Solman to create Trusted RFCs,
thereby reducing manual effort & simplifying the troubleshooting process.

Note-: The pre-requisite before running the RFC wizard in Solution Manager, is to assign S_RFC & S_RFCACL &
SAP_ALL objects to Admin users in both solution manager & satellite systems.

To access the RFC Wizard, go to SMSY & drill-down to the system for which you want to check the RFCs,

85
To delete RFCs & re-create them, follow these steps,

1)Click this button

2)From the pop-up that appears, you can delete the RFCs & IDs in Solman system.

86
Note-: This does not clear RFCs & IDs in the satellite system. This has to be done manually. Note the information
highlighted in Blue in the above screen & delete them Manually.

For steps regarding RFC wizard refer to Page#10.

For more info. On Solution Manager Configuration & Troubleshooting, refer to the Videos in the SHS_Captures
folder. These videos have been recorded during the SHS system implementation & hence can be used to
troubleshoot issues with the system.
You may also find troubleshooting tips from the SIM files that can be found at http:/service.sap.com/okp

87