ADM100 EN Col22 ExerciseHandbook A4 PDF
ADM100 EN Col22 ExerciseHandbook A4 PDF
.
.
EXERCISES AND SOLUTIONS
.
Course Version: 22
Course Duration: 7 Hours 30 Minutes
Material Number: 50158320
SAP Copyrights, Trademarks and Disclaimers
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see https://www.sap.com/
corporate/en/legal/copyright.html for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software
vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which
speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
Demonstration
Procedure
Warning or Caution
Hint
Facilitated Discussion
67 Exercise 17: Implement an SAP Note with the SAP Note Assistant
70 Exercise 18: Import a SPAM/SAINT Update
74 Exercise 19: Perform a SUM Prerequisite Check
78 Exercise 20: Import an SAP Support Package
Business Example
You want to log on to an SAP system using SAP GUI for Windows. First, you need to create an
entry for this system in SAP Logon.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In SAP Logon, create a new entry for the SAP system that has been assigned to you in the
class (your instructor will provide you with the data). To log on to the system, use its
respective primary application server (PAS).
2. Test the SAP Logon entry you just created and set a production password.
Business Example
You want to log on to an SAP system using SAP GUI for Windows. First, you need to create an
entry for this system in SAP Logon.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In SAP Logon, create a new entry for the SAP system that has been assigned to you in the
class (your instructor will provide you with the data). To log on to the system, use its
respective primary application server (PAS).
a) On the desktop of the training WTS, start program SAP Logon.
Hint:
Depending on the training environment, SAP Logon may already contain
entries but you should feel free to add your own.
c) In the Create New System Entry dialog window, choose User Specified System
(default).
d) Choose Next..
Hint:
In the SAP training landscape, SIDs are not unique. This is why you need
to enter some system details manually.
f) In the Description field, enter a text that describes which system is involved (for
example, S4D_PAS for the S4D system).
g) In the System ID field, enter the appropriate three-place ID for the system.
System PAS Instance
S4D (Development) 11
S4Q (Test) 21
h) In the Instance Number field, enter the two-digit instance number of the primary
application server (PAS) for this system.
i) In the Application Server field, enter the host name on which the primary application
server is running (for example, s4Xhost.wdf.sap.corp).
Replace “X” by “d”, “q” or “p” depending on the training systems assigned to you.
j) Leave the SAProuter String field blank, unless your instructor tells you otherwise.
k) Choose Next.
l) Leave the default settings in the Secure Network Settings and Network Settings area.
m) Choose Next.
o) Choose Finish.
Result: A new entry with the name you entered in the Description field should now
appear in SAP Logon.
Hint:
Feel free to create additional entries in SAP Logon for other training
systems. Repeat the steps above.
You can also choose Finish directly after you have entered the system ID.
2. Test the SAP Logon entry you just created and set a production password.
a) Test all SAP Logon entries you just created by double-clicking them or by selecting an
entry and then choosing Log On.
If a logon screen appears, you have reached the dispatcher with these settings. If you
see an error message instead of a logon screen, check the SAP Logon entry for that
system.
b) On the logon screen, leave the default value in the Client field.
d) In the Password field, enter the initial password defined by your instructor.
f) Press Enter or use the menu path User → Log on on the top left of the window.
g) In the dialog window, enter your own production password, which you have chosen,
twice.
a) In the system you have just logged on to, choose System → Status from the SAP
system menu.
b) In the System: Status window, check the Server Name field in the Host data area.
This field should contain the following information (syntax): <Host
name>_<SID>_<instance number>. The last two digits correspond to the instance
number of this system that identifies the primary application server (PAS) instance.
Hint:
If different instance number then expected is displayed, check your SAP
Logon entry to see if the correct instance number was entered in the
Instance Number field.
Business Example
As a system administrator, you want to use logon groups to restrict user logons to specific
application servers in your SAP system.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Create a logon group named DIALOG-## that points to the additional application server
(AAS) of your assigned system in transaction SMLG.
Hint:
The name of the logon group (DIALOG-##) hints at its purpose for answering
dialog queries. This is just an example. Feel free to choose other name for the
logon group if it is intended to have a different purpose.
2. Create a new SAP Logon entry for your assigned SAP system. Use the DIALOG-## logon
group you just created.
4. In the SAP system, check which instance you are logged on to.
Business Example
As a system administrator, you want to use logon groups to restrict user logons to specific
application servers in your SAP system.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Create a logon group named DIALOG-## that points to the additional application server
(AAS) of your assigned system in transaction SMLG.
Hint:
The name of the logon group (DIALOG-##) hints at its purpose for answering
dialog queries. This is just an example. Feel free to choose other name for the
logon group if it is intended to have a different purpose.
a) If you have not done so already, log on to your training SAP system using SAP Logon.
b) Enter your user ID (TRAIN-##) and the production password that you defined in the
previous exercise.
d) Choose the menu path Edit → Create Assignment or the Create Assignment button.
e) In the Create Assignment dialog window, enter the name of the logon group in the
Logon Group field: DIALOG-##.
f) In the Instance field, use the input help (F4) to select the AAS instance (for example,
s4dhost_S4D_12 in the S4D system).
Note:
You can only assign one application server instance at a time. If you want to
assign other instances to the same logon group, you need to do the
assignment for every instance separately.
g) Choose Copy.
Result: Your entry should now appear next to the instance name of the AAS in the
Logon Group column.
2. Create a new SAP Logon entry for your assigned SAP system. Use the DIALOG-## logon
group you just created.
a) On the desktop of the training WTS, start program SAP Logon.
c) In the Create New System Entry dialog window, choose User Specified System
(default) and choose Next.
Hint:
In SAP training, SIDs are not unique. This is why you need to enter some
system details manually.
e) In the Description field, enter a text that describes which system is involved. (for
example, S4D_LG for the S4D system).
f) In the System ID field, enter the appropriate three-place ID for the system.
h) Leave the SAProuter String field blank, unless your instructor tells you otherwise.
i) In the Group/Server field, choose the logon group you have created (DIALOG-##).
Hint:
If the expected result fails to display, check if you have saved the
assignment in the SMLG. It might take up to 5 minutes until the group is
displayed in SAP Logon.
j) Choose Finish.
Result: A new entry with the name you entered in the Description field should now
appear in SAP Logon.
b) On the logon screen, leave the default value in the Client field.
d) In the Password field, enter the production password that you have defined in the
previous exercise.
f) Press Enter or use the menu path User → Log on on the top left of the window.
4. In the SAP system, check which instance you are logged on to.
a) In the system you have just logged on to, choose System → Status from the SAP
system menu.
b) In the System: Status window, check the Server Name field in the Host data area.
This field should contain the following information (syntax): <Host
name>_<SID>_<instance number>. The last two digits correspond to the instance
number of this system that identifies the primary application server (PAS) instance.
Hint:
If a different instance number then expected is displayed, check the new
SAP Logon entry and make sure the correct logon group was entered in
the Group/Server field, or use transaction SMLG to check whether your
logon group points to the correct instance.
Business Example
As a system administrator, you want to determine the application server instances, number of
work processes, and active users in your SAP system. To do so, you use transactions in the
system that help you to perform your daily work.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Use transaction SM51 to determine the number of application server instances offering
work processes, available to you in your system, and their types.
Note:
The ASCS instance is not an application server instance and does not offer
work processes. So it does not show up in transaction SM51.
2. Find out how many work processes your entire SAP system has and what types they are.
Use transaction SM50.
3. Use SM04 to find out in which session type your user is logged on to in the SAP system and
when this session type changes.
4. Change your own user data and check the currently active locks in transaction SMENQ.
Think about what the lock entry means.
Business Example
As a system administrator, you want to determine the application server instances, number of
work processes, and active users in your SAP system. To do so, you use transactions in the
system that help you to perform your daily work.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Use transaction SM51 to determine the number of application server instances offering
work processes, available to you in your system, and their types.
Note:
The ASCS instance is not an application server instance and does not offer
work processes. So it does not show up in transaction SM51.
a) If you have not done so already, log on to your training SAP system using SAP Logon.
d) Evaluate how many application server instances your training system contains.
Your system should have two application server instances. The Application Server
Instance field should contain two rows with the names <host
name>_<SID>_<instance number> (for example, s4dhost_S4D_11 and
s4dhost_S4D_12 in the S4D system.
2. Find out how many work processes your entire SAP system has and what types they are.
Use transaction SM50.
a) Start transaction SM50.The number of work processes on all application server
instances in your system is displayed.
c) Locate the total number of dialog, batch, update, and spool work processes your SAP
system provides, and write it down:
_____________________________________________________________________________
3. Use SM04 to find out in which session type your user is logged on to in the SAP system and
when this session type changes.
a) Start transaction SM04.
Here you see the number of users logged on to the same instance as you.
b) Locate the session type for your user in the Type of User Session field and write down
the answer: ____
c) Start transaction SM51 in a new GUI window (for example by entering /OSM51 in the
command field).
Hint:
To find out which instance you are working on, choose the menu path:
System → Status and check the Server name field. Use this information
to log on to the OTHER instance, by double-clicking the instance number
of that instance. This changes the instance.
f) Write down the type of the session you have now: ____
4. Change your own user data and check the currently active locks in transaction SMENQ.
Think about what the lock entry means.
a) In the menu bar, choose the path System → User Profile → User Data.
Result: A new session opens automatically.
Hint:
You can also maintain the data of your user in transaction SU3. However,
it will not automatically open a new session.
d) Choose Search to display the locks currently managed by the enqueue server.
Business Example
As a system administrator, you need to stop SAP systems in your system landscape for
maintenance purposes or after changing system parameters, and then restart them.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Optional: Before you stop the SAP system, check which users are logged on to your
system. Send a system message announcing that the system is going to be stopped.
2. Check which process types are started at the operating system level after your system
has been started up. To do so, make sure that you are logged on to the operating system
of the host on which your SAP system is installed (for example, with the Remote Desktop
Connection).
3. Check in the SAP MC if all processes are running and the system has started correctly.
This has to be done on the training WTS. Additionally, log on to your SAP system.
1. Check whether your SAP system is running at the operating system level. Use, for
example, the Remote Desktop Connection to log on to the host of your SAP system.
2. Use the sapcontrol command in the terminal or XTerm to stop the entire SAP system.
1. Check whether your SAP system has stopped at the operating system level.
2. Use the sapcontrol command in the terminal or XTerm to start the entire SAP system.
Business Example
As a system administrator, you need to stop SAP systems in your system landscape for
maintenance purposes or after changing system parameters, and then restart them.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Optional: Before you stop the SAP system, check which users are logged on to your
system. Send a system message announcing that the system is going to be stopped.
a) In your SAP system, start the transaction SM04.
b) Choose System-Wide List or navigate from the menu to Goto → System-Wide List to
display the users logged on to your SAP system.
Hint:
The transaction uses RFC connections to collect user information for all
instances. Your user initiates the RFC connections to each instance, this
is why your own user is displayed more than once.
c) Start transaction SM02 to send a system message to the users logged on to your SAP
system.
d) Choose Create.
f) Specify until when the system message should be displayed. You can leave the default
value.
g) Choose Save.
Result: You successfully created a system message. It will now be displayed for every
user who is logged on to the system at the next dialog step.
Replace “X” by “d”, “q” or “p” depending on the training systems assigned to you.
Replace “$$” by “11”, “21” or “31” depending on the instance number of the PAS
instance of the training system assigned to you.
Result: The SAP MC applet will open.
c) In the SAP MC, select the system or the individual instances you want to stop.
g) Select Hard shutdown and do not stop the database, even if it were possible.
Note:
If you stop the instances individually, you should always stop them in the
reverse priority order:
● First the instance(s) with priority 3, which is the priority of all instances
with a dispatcher, but without enqueue process (PAS and AAS)
● Then the instance(s) (if any) with priority 2, which have a dispatcher and
an enqueue work process (the PAS has priority 2 if it has an enqueue
work process)
● Finally the instance with priority 1, which is the central services instance
(ASCS)
Result: Depending on whether you selected an individual instance or the entire SAP
system, either an individual instance or the entire system is stopped.
Note:
If you have been logged on to the system you just stopped, an SAP GUI
message is displayed informing you about the application server shutdown.
This is because you have used the hard shutdown option. You can ignore
this during this exercise.
Replace “X” by “d”, “q” or “p” depending on the training systems assigned to you.
Replace “$$” by “11”, “21” or “31” depending on the instance number of the PAS
instance of the training system assigned to you.
Result: The SAP MC applet will open.
c) Right-click the ASCS instance of your system in the SAP Management Console tree.
Hint:
You should always start the instances according to their priorities:
● Central services instances have priority 1.
● The priority of a PAS instance is 2, if an enqueue work process is
configured on the PAS instance.
● The priority of all other instances is 3.
2. Check which process types are started at the operating system level after your system
has been started up. To do so, make sure that you are logged on to the operating system
of the host on which your SAP system is installed (for example, with the Remote Desktop
Connection).
a) Log on to the host of your assigned SAP system with user <sid>adm and the password
(use, for example, the Remote Desktop Connection).
b) At the operating system level, open the System Monitor (from the toolbar:
Applications → Utilities → System Monitor) to check the running processes.
Result: The following kernel processes should be running at the operating system level
after your system has been started: SAP_<SID>_<InstanceNr>_<Process Type> (for
example, SAP_S4P_30_ENQ (enqueue server) or SAP_S4P_31_W10 (work process), if
you are administering the S4P system).
3. Check in the SAP MC if all processes are running and the system has started correctly.
This has to be done on the training WTS. Additionally, log on to your SAP system.
a) In the SAP MC, check the Process List of every instance to see if every process is
running.
b) Open the AS ABAP WP Table to determine the status of the work processes.
e) Log on to your SAP system with your TRAIN-## user and password.
1. Check whether your SAP system is running at the operating system level. Use, for
example, the Remote Desktop Connection to log on to the host of your SAP system.
a) Log on to the host of your assigned training SAP system with user <sid>adm and the
password using, for example, the Remote Desktop Connection.
2. Use the sapcontrol command in the terminal or XTerm to stop the entire SAP system.
a) In the terminal or XTerm, enter the command sapcontrol -nr <instance
number> -function StopSystem ALL to stop your system.
Replace “<instance number>” by “11”, “21” or “31” depending on the instance
number of the PAS instance of the training system assigned to you.
Result: The entire SAP system is stopped.
1. Check whether your SAP system has stopped at the operating system level.
a) Check in the System Monitor if the operating system processes of your SAP system
have been stopped (alternatively you can use the SAP MC).
2. Use the sapcontrol command in the terminal or XTerm to start the entire SAP system.
a) In the terminal or XTerm, enter the command sapcontrol -nr <instance
number> -function StartSystem ALL to start your system.
Replace “<instance number>” by “11”, “21” or “31” depending on the instance
number of the PAS instance of the training system assigned to you.
b) In the System Monitor , check if the kernel processes have been started (alternatively
you can use the SAP MC).
Result: The following kernel processes should be running at the operating system level
after your system has been started: SAP_<SID>_<InstanceNr>_<Process Type> (for
example, SAP_S4P_30_ENQ (enqueue server) or SAP_S4P_31_W10 (work process), if
you are administering the S4P system).
Business Example
As a system administrator, you want to determine set values of profile parameters for your
SAP system.
1. Display all profile parameters (transaction RSPFPAR) and find out which profile parameter
defines the unique name of the application server you are currently logged on to? How is
the value of the profile parameter being created?
2. How many work processes are configured on the primary application server (PAS) of your
training system? Find out the configured number of dialog, background, update, and spool
work processes.
3. What is the maximum number of GUI windows or modes that a user can open during a
single logon session?
Business Example
As a system administrator, you want to determine set values of profile parameters for your
SAP system.
1. Display all profile parameters (transaction RSPFPAR) and find out which profile parameter
defines the unique name of the application server you are currently logged on to? How is
the value of the profile parameter being created?
a) Start transaction RSPFPAR to find out the values of profile parameters.
Alternatively, you can run the report RSPFPAR in transaction SA38.
b) Search for the profile parameter rdisp/myname by entering the name into the search
field.
c) Choose Execute.
Result: The profile parameter and its values are displayed in a table.
This parameter determines the name of the application server/instance you are
working on. That is why it is called local.
In column System Default Value (Unsubstituted Form), you can see that the name is
being created out of the values of two other profile parameters (SAPLOCALHOST and
SAPSYSTEMNAME separated by "_") and a placeholder for the local instance number
($$). It means, that the kernel default references other parameter values.
In column User Value, you see the resolved values. The result might look like follows,
e.g.: s4qhost_S4Q_21.
2. How many work processes are configured on the primary application server (PAS) of your
training system? Find out the configured number of dialog, background, update, and spool
work processes.
a) Make sure you are currently logged on the PAS of your SAP system. If not, user
transaction SM51 to switch instances.
c) Search for the profile parameters that define the number of work processes:
Dialog rdisp/wp_no_dia
Background rdisp/wp_no_btc
Update rdisp/wp_no_vb
Spool rdisp/wp_no_spo
3. What is the maximum number of GUI windows or modes that a user can open during a
single logon session?
a) Start transaction RZ11.
Business Example
As an administrator, you want to adjust the configuration of the entire SAP system and of
single instances.
1. Import the profile files of the PAS, AAS, and ASCS instances into the database of your SAP
system.
1. Check the current number of dialog work processes on the AAS instance.
2. Increase the number of dialog work processes for the AAS instance by 1. Consider in
which profile you would make the changes.
Hint:
Since application servers of your SAP system can be installed on different
hardware providing different hardware resources, you would probably
change the number of work processes in the respective instance profile of an
application server.
3. Check the current maximum number of windows a user can open within the same logon
session.
4. Set the value for the maximum number of windows that a user can open during a logon
session to 8. To do so, you may need to add a new parameter to a profile. Think about in
which profile (or profiles) you would make the changes.
Hint:
In general, you would want the users to open the same maximum number of
modes on all application servers, so you would set the parameter in the global
default profile.
1. Restart the SAP system by using the start/stop tool of your choice
2. After the system is running again, log on to it and check your changes. Check how many
dialog work processes are now configured on the AAS instance.
3. Check how many windows you can open within your logon session.
Result: All changes have become effective.
Business Example
As an administrator, you want to adjust the configuration of the entire SAP system and of
single instances.
1. Import the profile files of the PAS, AAS, and ASCS instances into the database of your SAP
system.
a) In your training SAP system, start transaction RZ10.
b) In the menu bar, choose Utilities → Import profiles → Of active servers to import the
profile files of PAS, AAS, and ASCS instances.
Result: In the profile check log, the import result is displayed. Only profiles that have
changed versions at operating system level are imported. This is the reason why the
log displays results that are highlighted in red color.
1. Check the current number of dialog work processes on the AAS instance.
a) In a new GUI window, start transaction SM51, for example, by entering /o SM51 in the
command field.
b) Select the AAS instance and choose Work Processes to check the current number of
dialog work processes.
2. Increase the number of dialog work processes for the AAS instance by 1. Consider in
which profile you would make the changes.
Hint:
Since application servers of your SAP system can be installed on different
hardware providing different hardware resources, you would probably
change the number of work processes in the respective instance profile of an
application server.
b) In the Profile field, use the F4 value help to choose the instance profile of the AAS
instance (<SID>_<instance name><instance number>_<host name>).
d) Back on the Edit Profiles screen, select the Extended maintenance radio button.
h) Choose Parameter where the tool tip displays Change (F2) or double-click the
parameter to change its value.
i) In the Parameter Value field, increase the number of dialog work processes by 1.
j) Choose Copy.
Result: The system message The changes were applied is displayed in the status bar.
k) Go back to the Maintain Profile where all parameters of the profile are displayed.
o) The system will prompt you in a dialog box to activate the new profile version. Choose
Yes to confirm the activation.
The new profile version has been saved and activated.
p) Choose Continue.
q) A note that appears informs you that you have to restart the system to make profile
changes effective. Choose Continue.
3. Check the current maximum number of windows a user can open within the same logon
session.
a) Start transaction RZ11.
4. Set the value for the maximum number of windows that a user can open during a logon
session to 8. To do so, you may need to add a new parameter to a profile. Think about in
which profile (or profiles) you would make the changes.
Hint:
In general, you would want the users to open the same maximum number of
modes on all application servers, so you would set the parameter in the global
default profile.
b) In the Profile field, use the F4 value help to choose the default profile (DEFAULT or
<SID>_<instance name><instance number>_<host name>).
The system automatically fills the Version field with the most recent version.
f) In the list of profile parameters, select the line where you want to insert the parameter.
Hint:
The parameter will be inserted above the line you have selected.
i) As Parameter Value, enter 8 to limit the maximum number of windows that a user can
open during a logon session.
j) Choose Copy.
Note:
It might be the case that you have to choose the Copy button twice.
Result: The system message The changes were applied is displayed in the status bar.
k) Go back to the Maintain Profile where all parameters of the profile are displayed.
Note:
An error message may occur. You can ignore it.
p) The system will prompt you in a dialog box to activate the new profile version. Choose
Yes to confirm the activation.
The new profile version has been saved and activated.
q) Choose Continue.
r) A note that appears informs you that you have to restart the system to make profile
changes effective. Choose Continue.
1. Restart the SAP system by using the start/stop tool of your choice
a) Restart your training SAP system by using the SAP Management Console or the
command sapcontrol at the operating system level.
Note:
You have to restart the entire SAP system since you have made changes to
the default profile too. If you make changes only to an instance profile, the
restart of only this instance is sufficient.
2. After the system is running again, log on to it and check your changes. Check how many
dialog work processes are now configured on the AAS instance.
a) To check the number of work processes, call transaction SM51.
3. Check how many windows you can open within your logon session.
a) To check the maximum number of windows that users can open during a logon
session, start transaction RZ11.
Business Example
Configuring the work processes using profiles usually meets the requirements for day
operation. As an administrator, you want to make use of the operation modes in the SAP
system to optimize the performance of the system for the different requirements during the
day and during the night.
1. Create two operation modes Daymode and Nightmode in CCMS: Edit Operation Modes
and Instances (transaction RZ04).
2. Create a definition for the work process distribution for all application server instances of
your system.
3. Change the distribution of the work processes for each of the operation modes of one of
the instances in your system.
Note:
There should be at least two dialog and two background work processes in all
operation modes.
1. In the operation mode calendar, schedule the operation modes that you have created.
1. To observe the change in work process distribution when the operation mode is switched,
use the Control Panel to switch to the Nightmode manually.
2. How can you observe the change of the work process distribution?
Business Example
Configuring the work processes using profiles usually meets the requirements for day
operation. As an administrator, you want to make use of the operation modes in the SAP
system to optimize the performance of the system for the different requirements during the
day and during the night.
1. Create two operation modes Daymode and Nightmode in CCMS: Edit Operation Modes
and Instances (transaction RZ04).
a) Start transaction RZ04 to create or edit operation modes.
b) On the CCMS: Maintain Operation Modes and Instances screen, choose Create
operation mode.
c) Enter the name of day operation mode (for example, Daymode) and a short
description.
e) Repeat the procedure for the night operation mode. Enter, for example, Nightmode
and then choose Save.
Result: When you have finished, you should see two operation modes on the CCMS:
Maintain Operation Modes and Instances screen.
2. Create a definition for the work process distribution for all application server instances of
your system.
a) On the CCMS: Maintain Operation Modes and Instances screen, choose Instances/
operation modes to switch to the instances/operation modes view.
Note:
Since this is the initial setup of operation modes, all active AS instances in
the system must be detected first. This is why the table appears empty.
b) To define work process distribution for all instances of your system, choose
Settings → Based on current status → New instances → Generate.
Result: The work processes defined in the instance profiles are assigned to the
operation modes.
3. Change the distribution of the work processes for each of the operation modes of one of
the instances in your system.
Note:
There should be at least two dialog and two background work processes in all
operation modes.
b) In dialog box CCMS: CCMS: Maintain Work Process Distribution, place the cursor in the
number field of the work process type that you want to change.
c) Change the number by choosing + and -. You may need to scroll down a bit.
d) Choose Save.
e) Now double-click operation mode Nightmode to change the distribution of the work
processes for it on the same AS instances (for example, PAS).
f) Change the number by choosing + and -. You may need to scroll down a bit.
g) Choose Save.
h) On the CCMS: Maintain Operation Modes and Instances screen, choose Save in the
bottom right-hand corner.
Result: This saves the new work process distribution for all operation modes.
1. In the operation mode calendar, schedule the operation modes that you have created.
a) In transaction RZ04, go one step back.
b) On the CCMS: Maintain Operation Modes and Instances screen where you create new
modes, select Operation mode → Timetable.
Alternatively, you can start transaction SM63 directly.
c) On the Display/Maintain Operation Mode Set screen, select the radio button Normal
operation (24 hr).
d) Choose Change.
e) Select the start and end of the time interval for the operation mode Daymode by
double-clicking the relevant time line (the time line changes from blue to black).
f) Choose Assign.
g) Use the F4 value help to select operation mode Daymode to assign to it.
h) Choose Continue.
j) Choose Continue.
k) After you have assigned the entire 24-hour period to your operation modes, choose
Save in the bottom right-hand corner.
Result: There is a message in the status bar saying Operation mode set was saved.
1. To observe the change in work process distribution when the operation mode is switched,
use the Control Panel to switch to the Nightmode manually.
a) Start transaction RZ03.
c) Select Nightmode.
d) Click Choose.
Result: On the input screen CCMS Control Panel: Display Server States and Alerts in
the line Active Operation Mode in Accordance with Time Table, Nightmode is now
displayed. In the Configuration alerts column, you can see the message Operation
mode differs for both instances.
e) In the menu bar, choose Control → Switch operation mode → All servers to switch to
the mode manually.
2. How can you observe the change of the work process distribution?
a) Start transaction SM50 to check the changed distribution of the work processes in the
process overview.
Result: You can see that individual work process types have changed according to the
work process distribution in the selected operation mode. If you did not allocate all
configurable work processes during the mode switching, additional dynamic work
processes have been configured (Sum < Con).
Business Example
As an SAP system administrator, you create and run task lists to standardize the way you
make changes to the system.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
3. For the task with the description, Check Profile Parameter (RZ10), add a check parameter
to ensure that the profile parameter login/system_client is set to 100.
Result: You are able to execute and monitor an existing task list.
Task 2: Optional: Create and execute your own task list Z_CHECK_##
1. Create your own task list Z_CHECK_## with Task Manager for Technical Configuration
(transaction STC01). Your task list should contain the steps:
3. Check the logs and monitor your task list run using Task List Run Monitor (transaction
STC02).
You are able to create and run your own task lists.
Business Example
As an SAP system administrator, you create and run task lists to standardize the way you
make changes to the system.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
b) Search for task list SAP_BASIS_SYSTEM_CONFIG_CHECK. You can use the F4 value
help.
d) For some tasks of your choice, choose Show Task Documentation from the Help
column.
3. For the task with the description, Check Profile Parameter (RZ10), add a check parameter
to ensure that the profile parameter login/system_client is set to 100.
a) Select Fill Parameters in the Parameter column for the task with description Check
Profile Parameter (RZ10). This must be the very last in the task list.
b) Select Insert Row (a plus button at the top of the (empty) table of profile parameters).
c) In the Task Overview section, you can select any of the links in column Task Description
to open the details.
Note:
In the training system, you may observe warnings or even errors. In the
context of this training, it is no big deal to ignore them.
Result: You are able to execute and monitor an existing task list.
Task 2: Optional: Create and execute your own task list Z_CHECK_##
1. Create your own task list Z_CHECK_## with Task Manager for Technical Configuration
(transaction STC01). Your task list should contain the steps:
d) The task list does not exist yet, so confirm the dialog box with Yes to create it.
f) On the Restrict Value Range, do not restrict the values and select Start Search.
i) Change the sequence of the tasks by choosing More → Move selected tasks one task
up or More → Move selected tasks one task down so that the consistency check is at
the beginning and the secure store check is at the end of the task list.
j) Choose Save in the bottom right-hand corner. Save the new task list as a local object.
c) The task list run should end with the status Finished successfully. Check the logs for
the tasks by choosing Show Task Log in the Log column.
Result: The task, Consistency Check (SICK) should not report any errors. The
execution of task Secure Store Check (SECSTORE) should be successful.
3. Check the logs and monitor your task list run using Task List Run Monitor (transaction
STC02).
a) Start transaction STC02.
c) Select your last task list run and choose Details for Task List Run. Recheck the logs
from your task list run.
You are able to create and run your own task lists.
Business Example
To protect the SAP system against data loss if an error occurs, the administrator regularly
performs backups.
Note:
Caution:The tasks of this exercise must only be done once per SAP system. If you
work in a group of two students on one system (S4D, S4Q or S4P), please do this
exercise together as a group task. This means that you will jointly carry out the
consistency check on the SAP HANA tenant database of the SAP system assigned
by your instructor.
Task 1: Back Up the SAP HANA tenant database using DBA Cockpit
Perform a complete backup of the tenant database.
1. Schedule a complete data backup of your SAP HANA tenant database in the DBA Cockpit
(transaction DBACOCKPIT). Choose 20:00h as the start time.
The next morning, check the DBA planning calendar to see whether the backup was
performed successfully. The entry should be highlighted in green in the planning calendar.
You should also analyze the logs (DBA Log). In the default configuration, the SAP HANA
DB runs the log backups automatically after carrying out the first complete backup. In the
training landscape, log backups are not enabled.
2. (Optional): Schedule a differential data backup of your SAP HANA tenant database in the
DBA Cockpit (transaction DBACOCKPIT). Choose 06:00h in the next morning as the start
time.
The next morning, check the planning calendar to see whether the backup was performed
successfully. A green colored entry in the planning calender indicates a successful
execution. You should also analyze the logs (DBA Log).
Task 2: Perform a Complete Data Backup of your SAP HANA system database using SAP
HANA Cockpit
Perform a complete data backup of your SAP HANA database system and check if the backup
has finished successfully.
1. Start Google Chrome and log on to the SAP HANA Cockpit using the following credentials.
Field S4D, S4Q and S4P Group Value
2. Perform a complete data backup of your SAP HANA system database with the SAP HANA
cockpit using the following data:
Field S4D Group Value S4Q Group Value S4P Group Value
Business Example
To protect the SAP system against data loss if an error occurs, the administrator regularly
performs backups.
Note:
Caution:The tasks of this exercise must only be done once per SAP system. If you
work in a group of two students on one system (S4D, S4Q or S4P), please do this
exercise together as a group task. This means that you will jointly carry out the
consistency check on the SAP HANA tenant database of the SAP system assigned
by your instructor.
Task 1: Back Up the SAP HANA tenant database using DBA Cockpit
Perform a complete backup of the tenant database.
1. Schedule a complete data backup of your SAP HANA tenant database in the DBA Cockpit
(transaction DBACOCKPIT). Choose 20:00h as the start time.
a) Call the transaction DBACOCKPIT.
b) On the DBA Cockpit: System Configuration Maintenance screen, on the left menu
choose Jobs → DBA Planning Calendar.
c) On the Jobs: DBA Planning Calendar screen, drag and drop the action Complete Data
Backup from the Action Pad to the calendars today’s date at 20:00h.
Result: The Schedule a New Action dialog opens, providing the chosen action and
planned start date/time values.
d) Leave the default settings for the tabs Action Parameters and Recurrence, and choose
the Add button, to schedule the complete data backup for tonight.
The scheduled data backup now appears in the planning calendar as an entry:
DataBackup.
The next morning, check the DBA planning calendar to see whether the backup was
performed successfully. The entry should be highlighted in green in the planning calendar.
You should also analyze the logs (DBA Log). In the default configuration, the SAP HANA
DB runs the log backups automatically after carrying out the first complete backup. In the
training landscape, log backups are not enabled.
2. (Optional): Schedule a differential data backup of your SAP HANA tenant database in the
DBA Cockpit (transaction DBACOCKPIT). Choose 06:00h in the next morning as the start
time.
a) If you have not already done so, call the DBA Cockpit planning calender (transaction
DBACOCKPIT, on the left menu choose Jobs → DBA Planning Calendar).
b) Drag and drop the action Differential Data Backup from the Action Pad to the calendars
tomorrows date at 06:00h in the morning.
Result: The Schedule a New Action dialog opens, providing the chosen action and
planned start date/time values.
c) Leave the default settings for the tabs Action Parameters and Recurrence, and choose
the Add button, to schedule the differential data backup.
The scheduled data backup now appears in the planning calendar as an entry:
DiffBackup.
The next morning, check the planning calendar to see whether the backup was performed
successfully. A green colored entry in the planning calender indicates a successful
execution. You should also analyze the logs (DBA Log).
Task 2: Perform a Complete Data Backup of your SAP HANA system database using SAP
HANA Cockpit
Perform a complete data backup of your SAP HANA database system and check if the backup
has finished successfully.
1. Start Google Chrome and log on to the SAP HANA Cockpit using the following credentials.
Field S4D, S4Q and S4P Group Value
b) If the screen Your connection is not private appears, choose the Advanced button and
in the subsequent screen choose Proceed to wdflbmt0103.wdf.sap.corp (unsafe) link
to continue.
c) In the SAP HANA XS Advanced window, enter the <HANA username> and <HANA
password> credentials from the above table, and select the Log On button.
2. Perform a complete data backup of your SAP HANA system database with the SAP HANA
cockpit using the following data:
Field S4D Group Value S4Q Group Value S4P Group Value
a) On the SAP HANA cockpit Home screen → Monitor Landscape tab, choose the
Database Directory card.
b) On the Database Directory screen, in the Database column, choose <your system
database>.
c) On the Database Overview screen of your system database, in the top left corner,
change the view from Monitoring to Administration.
d) On the Database Overview screen of your system database, enter Backup into the
search field on the top left corner.
Result: The Database Overview screen filters and reduces to the Database Backups
card. Verify the No full data backup available message.
g) On the Create Backup screen, specify the backup settings using the data from the
table above.
i) Choose the Back (<) button on the top left corner, to return to the Backup Catalog
initial screen.
A successful Complete Data Backup should be listed in the Backup Catalog.
j) On the Backup Catalog screen, in the title bar, select the dropdown icon and choose
the Database Overview entry.
Result: Back in the Database Overview screen, look for the Database Backups card and
verify a successful complete data backup of your SAP HANA system database.
k) On the Database Overview screen, in the top left corner, select the User icon, choose
Sign Out and confirm with the OK button to disconnect and exit from the SAP HANA
Cockpit.
Business Example
To protect the SAP HANA database system against inconsistencies, the administrator should
regularly perform pro-active SAP HANA consistency checks. Also, if you already face
symptoms that can indicate SAP HANA inconsistencies and want to check if and to what
extent corruptions exist.
Note:
Caution:This exercise must only be done once per SAP system. If you work in a
group of two students on one system (S4D, S4Q, or S4P), please do this exercise
together as a group task. This means that you will jointly carry out the consistency
check on the SAP HANA tenant database of the SAP system assigned by your
instructor.
1. If you still have the DBA Planning Calendar opened, continue with Step 2.
2. Schedule an SAP HANA column table consistency check using the following information:
Field Value
Action CHECK_COLUMN_TABLES
3. The next morning, examine the planning calendar to see whether the consistency check
was performed successfully. A green colored entry in the planning calendar indicates a
successful execution. You should also analyze the logs (DBA Log).
Business Example
To protect the SAP HANA database system against inconsistencies, the administrator should
regularly perform pro-active SAP HANA consistency checks. Also, if you already face
symptoms that can indicate SAP HANA inconsistencies and want to check if and to what
extent corruptions exist.
Note:
Caution:This exercise must only be done once per SAP system. If you work in a
group of two students on one system (S4D, S4Q, or S4P), please do this exercise
together as a group task. This means that you will jointly carry out the consistency
check on the SAP HANA tenant database of the SAP system assigned by your
instructor.
1. If you still have the DBA Planning Calendar opened, continue with Step 2.
a) Call the transaction DBACOCKPIT.
b) On the DBA Cockpit: System Configuration Maintenance screen, on the left menu
choose Jobs → DBA Planning Calendar.
2. Schedule an SAP HANA column table consistency check using the following information:
Field Value
Action CHECK_COLUMN_TABLES
a) On the Jobs: DBA Planning Calendar screen, in the Action Pad, drag and drop the
action Consistency Check from the Action Pad to the calendars tomorrows date at
03:00h in the very early morning hours.
Result: The Schedule a New Action dialog opens, providing the chosen action and
planned start date/time values.
b) In the Schedule a New Action dialog box, enter the data from the above table. (For the
Action field in the Action Parameters area, you can use the (F4) key to find the value).
c) Leave the Schema and Table fields empty and choose the Add button.
The scheduled consistency check task now appears in the planning calendar as an
entry: Check.
3. The next morning, examine the planning calendar to see whether the consistency check
was performed successfully. A green colored entry in the planning calendar indicates a
successful execution. You should also analyze the logs (DBA Log).
a) On the Jobs: DBA Planning Calendar screen, choose the Refresh (F9) button.
The scheduled and executed Check should now appear in the planning calendar as a
green entry.
c) In the Display Details of Action window, change to the Job Log tab and confirm that No
inconsistencies were found.
Business Example
As a user administrator, you want to create a new user master record so a new hire can start
working in the SAP system. Besides, you want to divide user maintenance among several user
administrators. Only administrators who have the authorization for a certain group should be
able to maintain users of this group.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. In client 100 of your SAP system, go to user maintenance (SU01) and create a user master
record ADMIN-##.
2. Since this is a user for a new hire, switch to the Logon Data tab and select Dialog as user
type.
4. On the Defaults tab, select the default logon language for the user.
Result: A new user master record has been created successfully.
5. Log on to client 100 of your SAP system with the newly created ADMIN-## user.
7. Start any transactions of your choice. Is the user able to execute any function in the
system?
1. In client 100 of your SAP system, call transaction SUGR and create a user group with the
name ADMINTEAM_##.
Result: The user group has been created successfully.
2. In the User Maintenance, assign your training user TRAIN-## to the ADMINTEAM_## user
group.
Business Example
As a user administrator, you want to create a new user master record so a new hire can start
working in the SAP system. Besides, you want to divide user maintenance among several user
administrators. Only administrators who have the authorization for a certain group should be
able to maintain users of this group.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. In client 100 of your SAP system, go to user maintenance (SU01) and create a user master
record ADMIN-##.
a) Log on to client 100 in your SAP system.
d) Choose Create.
Note:
As this exercise is meant for practicing, you should create a classic user
rather than a technical user since for the latter one no address tab page is
displayed.
e) On the Address tab page, enter the last name of your choice in the Last name field.
2. Since this is a user for a new hire, switch to the Logon Data tab and select Dialog as user
type.
a) Switch to the Logon Data tab page.
b) Check if the user type is set to Dialog. If yes, do not change it. If not, select user type
Dialog.
Write down the selected password (note that the password minimum length is 10 and
it is case sensitive): ______________________________
4. On the Defaults tab, select the default logon language for the user.
a) Switch to the Defaults tab page.
b) In the Logon Language field, select the logon language of your choice.
5. Log on to client 100 of your SAP system with the newly created ADMIN-## user.
a) Open the SAP Logon program on your desktop.
c) Enter the user ID ADMIN-## and the initial password you defined in the previous step.
d) Choiose Enter.
7. Start any transactions of your choice. Is the user able to execute any function in the
system?
a) Start any transaction of your choice. What is the result of your action?
Result: The user does not have the authorization to execute the transaction.
1. In client 100 of your SAP system, call transaction SUGR and create a user group with the
name ADMINTEAM_##.
a) Log on to client 100 in your SAP system.
2. In the User Maintenance, assign your training user TRAIN-## to the ADMINTEAM_## user
group.
a) Start transaction SU01.
b) Choose Change to open the user master record of your training user TRAIN-## in the
edit mode.
d) In the field User group, use the F4 value help to select user group ADMINTEAM_##.
Business Example
Authorizations for users are created by providing them with roles and authorization profiles.
As a user administrator, you are responsible for creating roles in SAP systems.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. In client 100 of your SAP system, go to Role Maintenance (transaction PFCG) and search
for the single role SAP_BC_ENDUSER.
3. Edit the role and check the transactions in the role menu.
4. Check the authorizations for the role and maintain open authorizations if necessary.
2. Create a role menu with transactions SM50, SM51, SM04, and SU01 included.
3. Maintain authorizations for the role. Provide the authorizations for administering user
group ADMINTEAM_## by editing authorization object S_USER_GRP.
5. Assign the role to the user ADMIN-## in the user maintenance (transaction SU01).
6. Check if user ADMIN-## has received the authorizations of the new role assigned.
7. Try to change the user master record of TRAIN-## user who you assigned to the
ADMINTEAM_## user group in the previous exercise. Are you able to do that?
Business Example
Authorizations for users are created by providing them with roles and authorization profiles.
As a user administrator, you are responsible for creating roles in SAP systems.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. In client 100 of your SAP system, go to Role Maintenance (transaction PFCG) and search
for the single role SAP_BC_ENDUSER.
a) Log on to client 100 in your SAP system.
c) In the Role field, use the F4 value help to search for a role.
d) In the Role Name dialog box, enter SAP_BC_ENDUSER into the Single Role field.
f) In the search result list, double-click the role that has been found.
b) In the dialog box that appears, enter Z_BC_ENDUSER_## in the to role field and choose
Copy all.
Result: The SAP standard role has been copied to your custom role.
3. Edit the role and check the transactions in the role menu.
a) Back on the Role Maintenance screen, choose Change next to the Role field.
e) Open the Basis Functions folder in the Role Menu and check which entries are included
in the role menu.
Result: You should see transactions SU3, SU53, and web dynpro application
WDHC_HELP_CENTER.
4. Check the authorizations for the role and maintain open authorizations if necessary.
a) Switch to the Authorizations tab page.
b) In the Edit Authorization Data and Generate Profiles, choose Change Authorization
Data.
c) On the Change Role: Authorizations screen, expand the folder structure and check the
authorizations.
You can quickly do so by marking the folder and choosing Expand subtree.
Note:
Since the applications included in the role menu are non-critical and are
usually provided to all end users, only start authorization objects appear in
the structure. For start authorization objects all fields are filled with values
automatically and should not be maintained.
b) The system proposes an automatically generated profile name. You cannot change it.
If necessary, adapt the profile description in the Text field.
c) Choose Execute.
Result: The authorizations profile has been generated for the role.
Hint:
You do not need to Save again, since this was already performed with the
Generate function.
Note:
If user ADMIN-## does not exist, create a user with this user ID in
transaction SU01 in a new session.
c) After the comparison has been completed, choose Cancel to close the dialog box.
Result: You can see the green traffic light for the user comparison. This means that the
user master record has been fully compared with the role and the authorization profile
has been assigned to the user.
b) Start the transaction SU3 and SU53. Are you authorized to do so?
Result: User ADMIN-## has the authorizations to execute the transactions.
2. Create a role menu with transactions SM50, SM51, SM04, and SU01 included.
a) Switch to the Menu tab page.
c) In the Assign Transactions dialog box, enter the following transaction codes:
Table 1: Transactions
Transaction code Text
SM50 Work Processes of AS Instance
SM51 Started AS Instances
SM04 Logons to an AS Instance
SU01 User Maintenance
3. Maintain authorizations for the role. Provide the authorizations for administering user
group ADMINTEAM_## by editing authorization object S_USER_GRP.
a) Switch to the Authorizations tab.
b) In the Edit Authorization Data and Generate Profiles, choose Change Authorization
Data.
Note:
In this exercise, this is done only for simplicity reasons. Normally, you
would provide single authorizations for the organizational levels defined in
your company.
d) Choose Save.
e) On the Change Role: Authorizations screen, expand the folder Object Class BC_A.
j) Choose Transfer.
m) Choose Transfer.
Note:
In this exercise, only for the sake of simplicity you should assign full
authorizations. In “real life”, you should adapt the single authorizations
quite carefully.
b) The system proposes an automatically generated profile name. You cannot change it.
If necessary, adapt the profile description in the Text field.
c) Choose Execute.
Result: The authorizations profile has been generated for the role.
Hint:
You do not need to Save again, since this was already performed with the
Generate function.
5. Assign the role to the user ADMIN-## in the user maintenance (transaction SU01).
a) Start transaction SU01.
b) On the initial screen, look for the user master record of the ADMIN-## and open it in
the edit mode by choosing Change.
Note:
If user ADMIN-## does not exist, create a user with this user ID in
transaction SU01 in a new session.
d) In the Role column, add the MONITORING_## role. If necessary, use the F4 value help
to find it.
6. Check if user ADMIN-## has received the authorizations of the new role assigned.
a) Log on to client 100 of your training SAP system with user ID ADMIN-## and the
production password you have set in the previous exercise.
7. Try to change the user master record of TRAIN-## user who you assigned to the
ADMINTEAM_## user group in the previous exercise. Are you able to do that?
a) On the initial screen, look for the user master record of the TRAIN-## and open it in
the edit mode by choosing Change.
Result: User ADMIN-## is not authorized to change user TRAIN-## because the user is
assigned to user group ADMINTEAM_##. The ADMIN-## user only has display
authorizations.
Business Example
As a user administrator, you want to use User Information System to evaluate information on
users and their authorizations.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. In your assigned SAP system, use the User Information System to determine transactions
that are executable for the Z_BC_ENDUSER_## role.
Business Example
As a user administrator, you want to use User Information System to evaluate information on
users and their authorizations.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. In your assigned SAP system, use the User Information System to determine transactions
that are executable for the Z_BC_ENDUSER_## role.
a) Log on to client 100 in your SAP system.
Business Example
You want to record authorization checks and their values for specific users in the system.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. Start the System Trace for Authorization Checks (transaction STAUTHTRACE) and activate
the trace for your TRAIN-## user.
2. In a new GUI window, start the User Maintenance (transaction SU01) and set the title for
your own user.
3. Deactivate the trace and evaluate the generated system trace for authorization checks.
Which authorization objects have been checked?
___________________________________________
Was the authorization check of S_USER_GRP successful?
___________________________________________
Business Example
You want to record authorization checks and their values for specific users in the system.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. Start the System Trace for Authorization Checks (transaction STAUTHTRACE) and activate
the trace for your TRAIN-## user.
a) Log on to client 100 in your SAP system.
c) In the Trace for user only field, enter your TRAIN-## user.
2. In a new GUI window, start the User Maintenance (transaction SU01) and set the title for
your own user.
a) Call transaction SU01 in a new GUI session (for example, with /oSU01).
c) Choose Change.
3. Deactivate the trace and evaluate the generated system trace for authorization checks.
Which authorization objects have been checked?
___________________________________________
Was the authorization check of S_USER_GRP successful?
___________________________________________
a) Go back to the session with System Trace for Authorization Checks.
c) Filter the results for your user only by entering your user name (TRAIN-##) in the
Restrictions for the Evaluation section.
Business Example
As a system administrator, you want to enable communication between SAP systems in your
system landscape using remote function calls (RFCs). Before you set up an interface system,
you want to check RFC resources on all application servers.
1. In your SAP system, use transaction SARFC to determine the current RFC quotas for all
application server instances.
Result: You can see that the RFC quotas are activated (value set to 1) and the values of the
current quotas are displayed. You can change the values dynamically in the dialog box by
choosing Display/Change.
Business Example
As a system administrator, you want to enable communication between SAP systems in your
system landscape using remote function calls (RFCs). Before you set up an interface system,
you want to check RFC resources on all application servers.
1. In your SAP system, use transaction SARFC to determine the current RFC quotas for all
application server instances.
a) In your training SAP system, start transaction SARFC.
c) View the current parameter values in the Display Assignment dialog box.
Result: You can see that the RFC quotas are activated (value set to 1) and the values of the
current quotas are displayed. You can change the values dynamically in the dialog box by
choosing Display/Change.
Result: Here you see the technical name of profile parameters behind the RFC quotas. You
can see that RFC quotas are activated (rdisp/rfc_use_quotas value is set to 1) and the
values of the current quotas are displayed. However, here you are not able to change the
values dynamically.
Business Example
As a system administrator, you have to set up RFC connections to other systems.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, start transaction SM59 and set up a new RFC connection to the client
100 and the PAS instance of an SAP system in the training landscape.
Note:
The instructor will tell you which system to use.
2. Provide the technical details of the RFC destination from the specifications table. The
destination should connect to client 100 and primary application server instance of the
target system.
3. Perform a connection test to check if the data you have entered is correct and the
connection is working.
1. In your SAP system, set up an RFC connection to the client 100 of an SAP system in the
training landscape and use the load balancing option.
Note:
The instructor will tell you which system to use.
2. Provide the technical details of the RFC destination from the specifications table. The
destination should connect to client 100 and an existing logon group in the target system.
3. Perform a Connection Test to check whether the logon group you entered also exists in
the target system.
Result: If the connection via load balancing has been successful, you will see a table with
the response time of various actions.
4. Provide the logon data for the RFC connection. For details, see the specification table.
Business Example
As a system administrator, you have to set up RFC connections to other systems.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, start transaction SM59 and set up a new RFC connection to the client
100 and the PAS instance of an SAP system in the training landscape.
Note:
The instructor will tell you which system to use.
d) In the Create Destination dialog window, provide a destination name that you find in
the specifications table.
f) Choose Continue.
2. Provide the technical details of the RFC destination from the specifications table. The
destination should connect to client 100 and primary application server instance of the
target system.
a) In the Description 1 field, enter a feasible description for the RFC destination.
b) On the Technical Settings tab, make sure load balancing is not activated by selecting
No.
c) Enter the name of the target host. For details, see the specifications table.
e) On the Logon & Security tab, enter 100 in the Client field.
3. Perform a connection test to check if the data you have entered is correct and the
connection is working.
a) In the application function bar, choose Connection Test.
Result: If the test was successful, you will see the response time for different actions of
the connection. If not, check if the technical data of the connection is correct.
b) On the logon screen of the target system, enter your course user TRAIN-## and
password (which may still be initial).
1. In your SAP system, set up an RFC connection to the client 100 of an SAP system in the
training landscape and use the load balancing option.
Note:
The instructor will tell you which system to use.
d) In the Create Destination dialog window, provide a destination name that you find in
the specifications table.
f) Choose Continue.
2. Provide the technical details of the RFC destination from the specifications table. The
destination should connect to client 100 and an existing logon group in the target system.
a) In the Description 1 field, enter any feasible description for the RFC destination.
b) On the Technical Settings tab, activate the Load Balancing option by selecting Yes.
c) Enter the SID of the target system. For details, see the specifications table.
3. Perform a Connection Test to check whether the logon group you entered also exists in
the target system.
a) In the application function bar, choose Connection Test.
Result: If the connection via load balancing has been successful, you will see a table with
the response time of various actions.
4. Provide the logon data for the RFC connection. For details, see the specification table.
a) In the Logon & Security tab, enter 100 in the Client field.
b) As User, enter your course user TRAIN-## and password (which may still be initial).
Note:
For security reasons, you should never enter a dialog user in the definition
of an RFC connection. This course is an exception.
d) Choose Utilities → Test → Authorization Test to check whether the logon data you
defined is correct.
Result: If the logon data was correct, you will see a table with the response time of
various actions. If not, a logon screen of the target system might appear.
Business Example
To correct the coding of an SAP object, you want to implement an SAP Note.
Caution:
The SAP Note is implemented in the SAP development system S4D with the SAP
Note Assistant. Later on, it can be imported into the SAP quality assurance
system S4Q with the Transport Management System (TMS). At the end, it can be
imported into the SAP production system S4P.
The S4Q groups and the S4P groups work together with their partner S4D
groups in the corresponding SAP development system.
Business Example
To correct the coding of an SAP object, you want to implement an SAP Note.
Caution:
The SAP Note is implemented in the SAP development system S4D with the SAP
Note Assistant. Later on, it can be imported into the SAP quality assurance
system S4Q with the Transport Management System (TMS). At the end, it can be
imported into the SAP production system S4P.
The S4Q groups and the S4P groups work together with their partner S4D
groups in the corresponding SAP development system.
b) Download the SAP Note. To do so, choose Goto → Download SAP Note.
c) Enter the SAP Note number, deselect the Download only if required option and choose
Execute.
b) Select the SAP Note and choose SAP Note → Check SAP Note. Confirm the dialog box
with Continue (Enter).
b) You will now find the SAP Note also on the My In Process SAP Notes tab. Switch to this
tab.
c) Select the line for this SAP Note and choose Implement SAP Note.
Note:
Some SAP Notes require you to download additional SAP Notes before you
can implement them. In this case confirm another popup with Next.
d) If applicable, you may need to choose Yes to confirm that you have read the SAP Note.
f) In the Prompt for transportable Workbench requests dialog box, choose Create
Request. Enter a short description for the transport request and create the transport
request by choosing Save (Enter). Choose Continue (Enter) to confirm the Prompt for
transportable Workbench requests dialog box.
Note:
Depending on the SAP Note you may be prompted that the object can only
be created in an SAP package. In this case confirm with Continue (Enter).
g) On popup SAP Note Implementation, check that the status for all objects to be
changed is Changes can be applied (indicated by a green traffic light).
h) If applicable, activate any inactive items by confirming the Inactive Objects for ... dialog
box with Continue (Enter).
Hint:
In “real life”, you would need to perform the following additional steps:
● release the corresponding transport request via the Transport
Organizer (transaction SE09) in the SAP development system
● import the transport request into the SAP quality assurance system –
imports can be performed via transaction STMS. .
Business Example
To import SAP Support Packages with the Support Package Manager, you should first update
the Support Package Manager itself. For example, this may be necessary to read new
attributes from the SAP Support Packages and interpret them correctly.
Import a SPAM/SAINT update.
Caution:
This exercise must be performed first by the S4D group, then by the S4Q group,
and then by the S4P group.
1. S4D groups only: Check the current SPAM version, then import the SPAM/SAINT update,
using the method SAR Archives from Frontend.
2. S4Q groups only: Check the current SPAM version, then import the SPAM/SAINT update,
using the method EPS Files from Application Server.
3. S4P groups only: Check the current SPAM version, then import the SPAM/SAINT update,
using the method EPS Files from Application Server.
Business Example
To import SAP Support Packages with the Support Package Manager, you should first update
the Support Package Manager itself. For example, this may be necessary to read new
attributes from the SAP Support Packages and interpret them correctly.
Import a SPAM/SAINT update.
Caution:
This exercise must be performed first by the S4D group, then by the S4Q group,
and then by the S4P group.
1. S4D groups only: Check the current SPAM version, then import the SPAM/SAINT update,
using the method SAR Archives from Frontend.
a) Log on to S4D, client 000. Importing a SPAM/SAINT updates is possible from client
000, only.
b) Call transaction SPAM. Here you can see the version of the Support Package Manger in
the title bar, for example Support Package Manager - Version 7.55/0077.
c) To see which SPAM/SAINT updates have already been imported, select the Imported
Support Packages radio button and choose Display. An overview of the imported
SPAM/SAINT updates is displayed, called SAP_OCS (SAP Online Correction System).
d) Call transaction SPAM. Choose Support Package → Load Packages → SAR Archives
from Frontend. In the dialog box Select CAR/SAR archive select the newest file
KD755<nn>.SAR from the directory S:\Maintenance\s4Xhost\SPAM_SAINT. Confirm
with Open. Confirm the following dialog box Content of the compressed file
'kd755<nn>.sar' with Decompress.
Hint:
Remember, that despite the menu path no package was uploaded into the
SAP system or imported here. And the search was not performed on the
front end, but on the host, the front end is running on.
f) In case the importing terminates with an error, simply call SPAM again and continue the
importing by choosing Support Package → Import SPAM/SAINT Update, Import again.
A termination is not unusual, because transaction SPAM is patched by itself.
h) Call transaction SPAM again. Check if the title bar displays the newly imported SPAM/
SAINT version.
2. S4Q groups only: Check the current SPAM version, then import the SPAM/SAINT update,
using the method EPS Files from Application Server.
a) Log on to S4Q, client 000. Importing a SPAM/SAINT updates is possible from client
000, only.
b) Call transaction SPAM. Here you can see the version of the Support Package Manger in
the title bar, for example Support Package Manager - Version 7.55/0077.
c) To see which SPAM/SAINT updates have already been imported, select the Imported
Support Packages radio button and choose Display. An overview of the imported
SPAM/SAINT updates is displayed, called SAP_OCS (SAP Online Correction System).
d) Call transaction SPAM. Choose Support Package → Load packages → EPS Files from
Application Server Confirm the dialog box SPAM: Confirm upload with Yes. Check if the
SPAM/SAINT update was recognized. Go back to the initial screen of transaction
SPAM.
Hint:
Remember, that despite the menu path no package was uploaded or
imported here. And the search was not performed on the application
server, but in the transport directory of the transport host - which is not
even the host of the application server, in this case.
f) If it appears, confirm the screen Errors during Disassembling OCS Packages with
Ignore.
Hint:
For more information on this problem concerning the signed manifest,
see SAP Note 2687814 - Error "There is no signed manifest existing for
OCS Package" in SPAM or SAINT
g) In case the importing terminates with an error, simply call SPAM again and continue the
importing by choosing Support Package → Import SPAM/SAINT Update, Import again.
A termination is not unusual, because transaction SPAM is patched by itself.
i) Call transaction SPAM again. Check if the title bar displays the newly imported SPAM/
SAINT version.
3. S4P groups only: Check the current SPAM version, then import the SPAM/SAINT update,
using the method EPS Files from Application Server.
a) Log on to S4P, client 000. Importing a SPAM/SAINT updates is possible from client
000, only.
b) Call transaction SPAM. Here you can see the version of the Support Package Manger in
the title bar, for example Support Package Manager - Version 7.55/0077.
c) To see which SPAM/SAINT updates have already been imported, select the Imported
Support Packages radio button and choose Display. An overview of the imported
SPAM/SAINT updates is displayed, called SAP_OCS (SAP Online Correction System).
d) Call transaction SPAM. Choose Support Package → Load packages → EPS Files from
Application Server Confirm the dialog box SPAM: Confirm upload with Yes. Check if the
SPAM/SAINT update was recognized. Go back to the initial screen of transaction
SPAM.
Hint:
Remember, that despite the menu path no package was uploaded or
imported here. And the search was not performed on the application
server, but in the transport directory of the transport host - which is not
even the host of the application server, in this case.
f) If it appears, confirm the screen Errors during Disassembling OCS Packages with
Ignore.
Hint:
For more information on this problem concerning the signed manifest,
see SAP Note 2687814 - Error "There is no signed manifest existing for
OCS Package" in SPAM or SAINT
g) In case the importing terminates with an error, simply call SPAM again and continue the
importing by choosing Support Package → Import SPAM/SAINT Update, Import again.
A termination is not unusual, because transaction SPAM is patched by itself.
i) Call transaction SPAM again. Check if the title bar displays the newly imported SPAM/
SAINT version.
Business Example
Before performing a software maintenance with the Software Update Manager (SUM), in
some cases you can first perform a prerequisite check run.
Perform a SUM prerequisite check run.
Caution:
This exercise has to be performed before importing any SAP Support Packages -
otherwise the stack.xml file does not fit!
Note:
This exercise can be performed by the S4D, S4Q, and S4P groups in parallel.
The SUM can be used for different software maintenance tasks for an SAP system. The
newest SUM archive can be downloaded manually from the SAP Support Portal at
support.sap.com/sltoolset - or let the SUM archive be part of the calculated files from the
Maintenance Planner. Before really performing the software maintenance task with the SUM,
in some cases you can first perform a SUM prerequisite check run.
Note:
The string <SID> stands for the SID of your SAP system in capital letters, the
string <sid> in lower letters.
The SUM archive is available on the share on host <sid>host, at /kpstransfer/
Courses/ADM100_22/Software_Maintenance/SUM/Linux_on_x86_64_64bit.
1. S4D, S4Q, and S4P groups: Create the download directory at /usr/sap/<SID> and name
it DD. Copy the corresponding stack XML file from /kpstransfer/Courses/ADM100_22/
Software_Maintenance/Maintenance_Planner/<SID> into the download directory.
Business Example
Before performing a software maintenance with the Software Update Manager (SUM), in
some cases you can first perform a prerequisite check run.
Perform a SUM prerequisite check run.
Caution:
This exercise has to be performed before importing any SAP Support Packages -
otherwise the stack.xml file does not fit!
Note:
This exercise can be performed by the S4D, S4Q, and S4P groups in parallel.
The SUM can be used for different software maintenance tasks for an SAP system. The
newest SUM archive can be downloaded manually from the SAP Support Portal at
support.sap.com/sltoolset - or let the SUM archive be part of the calculated files from the
Maintenance Planner. Before really performing the software maintenance task with the SUM,
in some cases you can first perform a SUM prerequisite check run.
Note:
The string <SID> stands for the SID of your SAP system in capital letters, the
string <sid> in lower letters.
The SUM archive is available on the share on host <sid>host, at /kpstransfer/
Courses/ADM100_22/Software_Maintenance/SUM/Linux_on_x86_64_64bit.
1. S4D, S4Q, and S4P groups: Create the download directory at /usr/sap/<SID> and name
it DD. Copy the corresponding stack XML file from /kpstransfer/Courses/ADM100_22/
Software_Maintenance/Maintenance_Planner/<SID> into the download directory.
a) Log on to host <sid>host with user install.
c) From /kpstransfer/Courses/ADM100_22/Software_Maintenance/
Maintenance_Planner/<SID> copy the file MP_Stack_<number>_<date>_.xml into the
newly created download directory, e.g. by executing the commands
cd /usr/sap/<SID>/DD/
cp /kpstransfer/Courses/ADM100_22/Software_Maintenance/
Maintenance_Planner/<SID>/MP_Stack_<number>_<date>_.xml .
Note:
Here, <nn> represents the SP stack level of SUM, <pp> the patch level.
Your instructor may provide more details.
b) Still at /usr/sap/<SID>, change the owner of the newly extracted SUM directory
(recursively), e.g. by executing the commands
cd /usr/sap/<SID>/
chown <sid>adm:sapsys -R ./SUM/
Hint:
This creates the file sumabap.conf in the directory operations.d in the
directory of the SAP Host Agent (/usr/sap/hostctrl/exe). This file now
contains the path to the SUM folder: Workdir: /usr/sap/$
[SID:#required]/SUM/abap/.
c) On screen SAP System ID, Instance Number, and Database Type Required, enter the
instance number of the primary application server of your SAP system and then
proceed with Next.
d) On screen Welcome to the Software Update Manager, Specify the Scenario Category,
select Scenario using Stack Configuration File. Use he value help to select the stack
file: /usr/sap/<SID>/DD/MP_Stack_<number>_<date>_.xml. Then proceed with
Next.
e) On screen Scenario Strategy, select Prerequisite Check Tool and Prerequisite Check
and then proceed with Next.
g) On screen Required System Passwords, enter the passwords for SAP system user
DDIC in client 000, database user SYSTEM of the tenant database, and database
schema user SAPHANADB. Proceed with Next
Note:
Your instructor will provide details.
h) The procedure now runs for several minutes and ends with the screen Procedure
Completed.
i) Check the results by displaying the messages at the information/error icon – or on the
main screen of the SUM UI after the SUM run has finished. Several information and
error messages may be displayed. In the context of this course, do not go into detail
and do not check or change anything.
j) To end the SUM run: In the very right menu of the SUM UI choose Exit.
k) To end the SUM UI: In the very right menu of the SUM UI, finally choose Exit again and
then close the browser.
Business Example
You want to import the most recent SAP Support Packages to update the SAP system.
Caution:
This exercise must be performed first by the S4D group, then by the S4Q
group, and then by the S4P group. It must not be performed by more than
one group simultaneously.
Note:
Applying this single SAP Support Package in this course takes only a few minutes.
In real life applying SAP Support Packages can take several hours or even days.
Apply the SAP Support Package named by your instructor. For this exercise choose the
option EPS Files from Application Server to register the SAP Support Package in transaction
SPAM.
In the first step, the available SAP Support Package is applied to the SAP development
system.
After this is successfully completed, the SAP Support Package is applied to the SAP quality
assurance system.
In the last step, the SAP Support Package in applied to the SAP production system.
The file you need for the SAP Support Package has already been downloaded. It is located on
the share on the SAP host at /kpstransfer/Courses/ADM100_22/Software_Maintenance/
Test_SAP_Support_Package.
1. S4D groups only: Check which SAP Support Packages have already been imported into
your SAP system. Extract the corresponding file that contains the new SAP Support
Package at file system level to the transport directory. Import the SAP Support Package
into your SAP system. Confirm the imported SAP Support Package after successful
import.
2. S4Q groups only: Check which SAP Support Packages have already been imported into
your SAP system. The corresponding file that contains the new SAP Support Package was
extracted at file system level to the transport directory from the S4D group, already.
Import the SAP Support Package into your SAP system. Confirm the imported SAP
Support Package after successful import.
3. S4P groups only: Check which SAP Support Packages have already been imported into
your SAP system. The corresponding file that contains the new SAP Support Package was
extracted at file system level to the transport directory from the S4D group, already.
Import the SAP Support Package into your SAP system. Confirm the imported SAP
Support Package after successful import.
Business Example
You want to import the most recent SAP Support Packages to update the SAP system.
Caution:
This exercise must be performed first by the S4D group, then by the S4Q
group, and then by the S4P group. It must not be performed by more than
one group simultaneously.
Note:
Applying this single SAP Support Package in this course takes only a few minutes.
In real life applying SAP Support Packages can take several hours or even days.
Apply the SAP Support Package named by your instructor. For this exercise choose the
option EPS Files from Application Server to register the SAP Support Package in transaction
SPAM.
In the first step, the available SAP Support Package is applied to the SAP development
system.
After this is successfully completed, the SAP Support Package is applied to the SAP quality
assurance system.
In the last step, the SAP Support Package in applied to the SAP production system.
The file you need for the SAP Support Package has already been downloaded. It is located on
the share on the SAP host at /kpstransfer/Courses/ADM100_22/Software_Maintenance/
Test_SAP_Support_Package.
1. S4D groups only: Check which SAP Support Packages have already been imported into
your SAP system. Extract the corresponding file that contains the new SAP Support
Package at file system level to the transport directory. Import the SAP Support Package
into your SAP system. Confirm the imported SAP Support Package after successful
import.
a) Log on to your SAP system S4D, client 000. Call transaction SPAM. Select the Imported
Support Packages radio button and choose Display.
Result: Several SAP Support Packages have already been imported. They have also
already been confirmed. You can tell this, for example, from the green traffic light on
the initial screen of transaction SPAM.
b) Check the SAP Support Package level for software component TRAINING: choose
System → Status..., select Details. Software component TRAINING is at release 620,
and there are no (0000) SAP Support Packages imported.
f) In the initial screen of transaction SPAM, choose Support Package → Load Packages
→ EPS Files from Application Server.
Do not be confused by the terms in the menu path. Instead, confirm the dialog box
SPAM: Confirm upload with Yes.
i) In transaction SPAM, choose the Display/define button to define the queue of SAP
Support Packages to be imported.
j) Choose All Components, then choose Calculate Queue. Check that there is an equal
symbol (=) for each software component.
l) There are no transport requests for modification adjustments that you could include,
so you confirm the prompt Add Modification Adjustment Transports to the Queue with
No.
m) Import the queue in transaction SPAM by choosing Support Package → Import Queue.
n) Retain the default values for the start conditions of the four modules and choose
Import.
o) If necessary, confirm the screen Errors during Disassembling OCS Packages with
Ignore.
Hint:
For more information on this problem concerning the signed manifest,
see SAP Note 2687814 - Error "There is no signed manifest existing for
OCS Package" in SPAM or SAINT
p) Follow the individual steps of the import process, as far as possible, displayed on the
screen. If any errors occur, examine them in the error log. If errors occur, you can
repeat the import of the SAP Support Packages from the step where it failed.
q) Confirm the dialog box Information informing you that the import was successful with
Continue (Enter).
r) To check the import logs in transaction SPAM, choose Goto → Import Logs → Queue.
No return codes of 8 or higher should be displayed.
s) To finish, go back, and confirm the queue in transaction SPAM by choosing Support
Package → Confirm.
t) Confirm the dialog box Sending the runtime analysis by choosing Do not send .
u) Check the SAP Support Package level for software component TRAINING, again:
choose System → Status..., select Details. Software component TRAINING is still at
release 620, but there is one (0001) SAP Support Package imported now! So you
successfully imported the Test SAP Support Package!
2. S4Q groups only: Check which SAP Support Packages have already been imported into
your SAP system. The corresponding file that contains the new SAP Support Package was
extracted at file system level to the transport directory from the S4D group, already.
Import the SAP Support Package into your SAP system. Confirm the imported SAP
Support Package after successful import.
a) Log on to your SAP system S4Q, client 000. Call transaction SPAM. Select the
Imported Support Packages radio button and choose Display.
Result: Several SAP Support Packages have already been imported. They have also
already been confirmed. You can tell this, for example, from the green traffic light on
the initial screen of transaction SPAM.
b) Check the SAP Support Package level for software component TRAINING: choose
System → Status..., select Details. Software component TRAINING is at release 620,
and there are no (0000) SAP Support Packages imported.
c) In the initial screen of transaction SPAM, choose Support Package → Load Packages
→ EPS Files from Application Server.
Do not be confused by the terms in the menu path. Instead, confirm the dialog box
SPAM: Confirm upload with Yes.
f) In transaction SPAM, choose the Display/define button to define the queue of SAP
Support Packages to be imported.
g) Choose All Components, then choose Calculate Queue. Check that there is an equal
symbol (=) for each software component.
i) There are no transport requests for modification adjustments that you could include,
so you confirm the prompt Add Modification Adjustment Transports to the Queue with
No.
j) Import the queue in transaction SPAM by choosing Support Package → Import Queue.
k) Retain the default values for the start conditions of the four modules and choose
Import.
l) If necessary, confirm the screen Errors during Disassembling OCS Packages with
Ignore.
Hint:
For more information on this problem concerning the signed manifest,
see SAP Note 2687814 - Error "There is no signed manifest existing for
OCS Package" in SPAM or SAINT
m) Follow the individual steps of the import process, as far as possible, displayed on the
screen. If any errors occur, examine them in the error log. If errors occur, you can
repeat the import of the SAP Support Packages from the step where it failed.
n) Confirm the dialog box Information informing you that the import was successful with
Continue (Enter).
o) To check the import logs in transaction SPAM, choose Goto → Import Logs → Queue.
No return codes of 8 or higher should be displayed.
p) To finish, go back, and confirm the queue in transaction SPAM by choosing Support
Package → Confirm.
q) Confirm the dialog box Sending the runtime analysis by choosing Do not send .
r) Check the SAP Support Package level for software component TRAINING, again:
choose System → Status..., select Details. Software component TRAINING is still at
release 620, but there is one (0001) SAP Support Package imported now! So you
successfully imported the Test SAP Support Package!
3. S4P groups only: Check which SAP Support Packages have already been imported into
your SAP system. The corresponding file that contains the new SAP Support Package was
extracted at file system level to the transport directory from the S4D group, already.
Import the SAP Support Package into your SAP system. Confirm the imported SAP
Support Package after successful import.
a) Log on to your SAP system S4P, client 000. Call transaction SPAM. Select the Imported
Support Packages radio button and choose Display.
Result: Several SAP Support Packages have already been imported. They have also
already been confirmed. You can tell this, for example, from the green traffic light on
the initial screen of transaction SPAM.
b) Check the SAP Support Package level for software component TRAINING: choose
System → Status..., select Details. Software component TRAINING is at release 620,
and there are no (0000) SAP Support Packages imported.
c) In the initial screen of transaction SPAM, choose Support Package → Load Packages
→ EPS Files from Application Server.
Do not be confused by the terms in the menu path. Instead, confirm the dialog box
SPAM: Confirm upload with Yes.
f) In transaction SPAM, choose the Display/define button to define the queue of SAP
Support Packages to be imported.
g) Choose All Components, then choose Calculate Queue. Check that there is an equal
symbol (=) for each software component.
i) There are no transport requests for modification adjustments that you could include,
so you confirm the prompt Add Modification Adjustment Transports to the Queue with
No.
j) Import the queue in transaction SPAM by choosing Support Package → Import Queue.
k) Retain the default values for the start conditions of the four modules and choose
Import.
l) If necessary, confirm the screen Errors during Disassembling OCS Packages with
Ignore.
Hint:
For more information on this problem concerning the signed manifest,
see SAP Note 2687814 - Error "There is no signed manifest existing for
OCS Package" in SPAM or SAINT
m) Follow the individual steps of the import process, as far as possible, displayed on the
screen. If any errors occur, examine them in the error log. If errors occur, you can
repeat the import of the SAP Support Packages from the step where it failed.
n) Confirm the dialog box Information informing you that the import was successful with
Continue (Enter).
o) To check the import logs in transaction SPAM, choose Goto → Import Logs → Queue.
No return codes of 8 or higher should be displayed.
p) To finish, go back, and confirm the queue in transaction SPAM by choosing Support
Package → Confirm.
q) Confirm the dialog box Sending the runtime analysis by choosing Do not send .
r) Check the SAP Support Package level for software component TRAINING, again:
choose System → Status..., select Details. Software component TRAINING is still at
release 620, but there is one (0001) SAP Support Package imported now! So you
successfully imported the Test SAP Support Package!
Business Example
As a system administrator, you want to check the print environment in your SAP system.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
2. Check in the work process overview, how many spool work processes are set up for the
application server to which you are currently logged on?
3. How many spool work processes are configured in your entire SAP system?
4. Configure your TRAIN-## user, so that a spool request does not result in the immediate
creation of an output request.
5. Which printer is defined at the operating system level of the host where your SAP system
runs? Check the details of printer Printer_<hostname>.
6. Which printer is defined at the operating system level of your corresponding feature
server? Check the details of printer Printer_<hostname>.
Use the following allocation:
7. Which printers are defined in your training environment (ADM-WTS)? Check the details of
printer Printer_WTS.
Business Example
As a system administrator, you want to check the print environment in your SAP system.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
2. Check in the work process overview, how many spool work processes are set up for the
application server to which you are currently logged on?
a) Start transaction SM50.
b) Count the number of spool work processes displayed (work processes of type SPO).
3. How many spool work processes are configured in your entire SAP system?
a) In transaction SM50, choose System-Wide List to display all spool work processes
configured in the SAP system.
b) Count the number of spool work processes displayed (work processes of type SPO).
Hint:
When you configure an operation mode, you cannot change the number
of spool work processes.
4. Configure your TRAIN-## user, so that a spool request does not result in the immediate
creation of an output request.
a) In the menu bar, choose System → User Profile → User Data (transaction SU3).
Hint:
This default setting can be overridden in the print dialog at any time.
5. Which printer is defined at the operating system level of the host where your SAP system
runs? Check the details of printer Printer_<hostname>.
a) If you have not done so already, log on to your system host (s4Xhost.wdf.sap.corp) via
Remote Desktop Connection at operating system level with user <sid>adm and
assigned password using the Remote Desktop Connection.
c) Optional: If you like, create a short text document and print it.
b) Print it on Printer_<hostname>.
6. Which printer is defined at the operating system level of your corresponding feature
server? Check the details of printer Printer_<hostname>.
Use the following allocation:
e) On the General tab, note that this printer is a raw printer (Text / Generic Only).
f) On the Ports tab, note that this printer prints to the file C:\Temp
\Printer_<hostname>.txt.
g) Optional: If you like, create a short text document and print it.
b) Print it on Printer_<hostname>.
7. Which printers are defined in your training environment (ADM-WTS)? Check the details of
printer Printer_WTS.
a) You are logged on to ADM-WTS.
b) Open the control panel (by right-clicking the Windows icon, for example).
e) On the General tab, note that this printer is a raw printer ("Text / Generic Only").
f) On the Ports tab, note that this printer prints to the file N:\My Documents
\Printer_WTS.txt.
g) Optional: If you like, create a short text document and print it.
b) Print it on Printer_WTS.
Business Example
As a system administrator, you want to enable local printing in your SAP system. To do so,
you need to create an output device with a local host spool access method.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create a local output device called Local## with short name LO##
that controls the printer you previously identified at server operating system level of your
SAP system.
2. Print a list of all profile parameters that begin with rspo* without immediate printing on the
Local## output device.
Business Example
As a system administrator, you want to enable local printing in your SAP system. To do so,
you need to create an output device with a local host spool access method.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create a local output device called Local## with short name LO##
that controls the printer you previously identified at server operating system level of your
SAP system.
a) In your SAP system, start transaction SPAD.
Alternatively, start transaction SPOOL and navigate to Important Spool Reports /
Transactions → Spool Administration → Spool Administration.
b) On the Devices / servers tab, in the line Output Devices, choose Display (leave the input
field to the left empty).
c) If you cannot find the Create button, choose Change to switch to change mode.
d) Choose Create.
Device Type Select any device type supporting PCL (for example,
HPLJ4)
Spool Server Any spool server from your system (use F4 value help)
Location Any text
Host spool access meth- L
od
Host Printer Name of the printer you identified (Printer_<host-
name>)
2. Print a list of all profile parameters that begin with rspo* without immediate printing on the
Local## output device.
c) Choose Execute.
e) In the dialog box that appears, use the F4 value help to select output device Local##.
f) In the Properties section, choose SAP spool only for now as Print Time. You may have
to confirm a prompt regarding the formatting.
g) Choose Continue.
Result: In the status bar, you see a message that the spool request was created
without immediate printing.
b) On the Output Controller: List of Spool Requests screen, select your most recent spool
request.
d) Choose Output Requests (F5) to check the status of your output request.
Result: The output request should have the status Compl..
Note:
It may take some time until the output request is displayed in status
Complete.
e) Optional: At the operating system level of your server, open file /tmp/
Printer_<hostname> to which the print output was sent with a text editor of your
choice (for example, gedit) and verify the output.
Note:
gedit cannot display all printer-specific control characters.
Business Example
As a system administrator, you want to enable printing in your SAP system using a print
server with Microsoft Windows operating system. To do so, you need to create an output
device in the SAP system with a remote host spool access method. To use the output device,
the installation of the SAPSprint program is required.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Install and check the SAPSprint service at the operating system level of your
corresponding feature server (fsXhost.wdf.sap.corp).
Use the following allocation:
2. In your SAP system, create a remote output device called Remote## with short name
RE## that controls the printer configured on the feature server.
3. Print the list of work processes (transaction SM50) with immediate printing on the
Remote## output device.
Business Example
As a system administrator, you want to enable printing in your SAP system using a print
server with Microsoft Windows operating system. To do so, you need to create an output
device in the SAP system with a remote host spool access method. To use the output device,
the installation of the SAPSprint program is required.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. Install and check the SAPSprint service at the operating system level of your
corresponding feature server (fsXhost.wdf.sap.corp).
Use the following allocation:
a) If you have not done so already, log on at the operating system level of your
corresponding feature server with user install and the assigned password using the
Remote Desktop Connection.
c) Choose the latest installation file offered there to install the SAPSprint program
(naming convention: xSPrint_<Release_PatchLevel-xxxx>.exe).
d) Run through the installation: Select SAP Print Service for installation and retain the
default values for all other prompts.
Note:
If you get a warning message prompting you to reboot your computer to
complete the process, you can ignore it.
e) Use the Services program to verify that an SAPSprint Windows service has been
created and started. In the properties of this Windows service, tab Log On, change Log
on as: to This account and enter the log on information of user .\install with
password.
2. In your SAP system, create a remote output device called Remote## with short name
RE## that controls the printer configured on the feature server.
a) In your SAP system, start transaction SPAD.
Alternatively, start transaction SPOOL and navigate to Important Spool Reports /
Transactions → Spool Administration → Spool Administration.
b) On the Devices / servers tab, in the line Output Devices, choose Display (leave the input
field to the left empty).
c) If you cannot find the Create button, choose Change to switch to change mode.
d) Choose Create.
3. Print the list of work processes (transaction SM50) with immediate printing on the
Remote## output device.
a) Start transaction SM50 in your SAP system.
b) Choose Print.
c) In the dialog box that appears, use the F4 value help to select output device Remote##.
d) In the Properties section, choose Immediately as Print Time. You may have to confirm
a prompt regarding the formatting.
e) Choose Continue.
b) On the Output Controller: List of Spool Requests screen, select your most recent spool
request.
c) Choose Output Requests (F5) to check the status of your output request.
Result: The output request should have the status Compl..
Note:
It may take some time until the output request is displayed in status
Complete.
d) Optional: At the operating system level of the feature server, open file C:\Temp
\Printer_<hostname>.txt to which the print output was sent and verify the output.
Business Example
As a system administrator, you want to enable printing in your SAP system using front-end
printing on printers that are set up on the front end PC of the users with the SAP GUI installed.
To do so, you need to create a generic output device for front-end printing.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create output device Frontend## with the short name FR## that
controls the default printer of the front-end PC where SAP GUI is installed.
2. Print the list of work processes in your instance (transaction SM50) with immediate
printing on the Frontend## output device.
Business Example
As a system administrator, you want to enable printing in your SAP system using front-end
printing on printers that are set up on the front end PC of the users with the SAP GUI installed.
To do so, you need to create a generic output device for front-end printing.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create output device Frontend## with the short name FR## that
controls the default printer of the front-end PC where SAP GUI is installed.
a) In your SAP system, start transaction SPAD.
Alternatively, start transaction SPOOL and navigate to Important Spool Reports /
Transactions → Spool Administration → Spool Administration.
b) On the Devices / servers tab, in the line Output Devices, choose Display (leave the input
field to the left empty).
c) If you cannot find the Create button, choose Change to switch to change mode.
d) Choose Create.
2. Print the list of work processes in your instance (transaction SM50) with immediate
printing on the Frontend## output device.
a) Start transaction SM50 in your SAP system.
b) Choose Print.
c) In the dialog box that appears, use the F4 value help to select output device
Frontend##.
d) In the Properties section, choose Immediately as Print Time. You may have to confirm
a prompt regarding the formatting.
e) Choose Continue.
f) In the Windows print dialog box that appears, choose printer Printer_WTS.
b) On the Output Controller: List of Spool Requests screen, select your most recent spool
request.
c) Choose Output Requests (F5) to check the status of your output request.
Result: The output request should have the status Compl..
Note:
It may take some time until the output request is displayed in status
Complete.
d) On the Output Controller: List of Output Requests screen, select the current output
request.
Business Example
As a system administrator, you want to print Unicode documents in your SAP system. To do
so, you need to enable Unicode Printing Enhancement (UPE) for an output device.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
2. In SP02, export the created spool request as a PDF document and examine it.
4. In transaction SPOOL, print a test form on output device Local## again by repeating the
first step. Make sure that you create a new spool request.
5. In SP02, export the new spool request as a PDF document and examine it.
Business Example
As a system administrator, you want to print Unicode documents in your SAP system. To do
so, you need to enable Unicode Printing Enhancement (UPE) for an output device.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
c) In the Print dialog window, choose Local## as the output device using the F4 value
help.
2. In SP02, export the created spool request as a PDF document and examine it.
a) Start transaction SP02 (your spool requests).
b) Select the row with the spool request you just created.
d) Save the generated PDF document in an appropriate place (for example, under N:\My
Documents).
b) On the Devices / servers tab, in the line Output Devices, choose Display (leave the input
field to the left empty).
Note:
In SAP systems with UPE feature, this button appears only for output
devices that use a PCL5 or a PostScript driver.
e) In the Change Unicode Print Settings dialog window, select any Unicode Reference
Device Type (URDT).
f) Back on the Output Device (Change) screen, a new area Unicode Print Settings appears
in the Device Attributes tab.
g) Choose Supported Languages to analyze the languages that are supported by the
chosen URDT.
4. In transaction SPOOL, print a test form on output device Local## again by repeating the
first step. Make sure that you create a new spool request.
a) Start transaction SPOOL.
c) In the Print dialog window, choose Local## as the output device using the F4 value
help.
5. In SP02, export the new spool request as a PDF document and examine it.
a) Start transaction SP02 (your spool requests).
b) Select the row with the spool request you just created.
d) Save the generated PDF document in an appropriate place (for example, under N:\My
Documents).
Business Example
As a system administrator, you want to set up logical spool servers in your SAP system to
ensure reliability and load balancing. To do so, you need to create a logical server and assign
an existing output device to it.
1. In your SAP system, create a logical server called TestPrint with the mapping to AAS
and PAS as alternative server. Classify it as a Test Server.
2. Change output device Local## so that the logical server TestPrint is used as the spool
server in future. Classify the Local## output device as a test printer.
3. Output any list (for example, all profile parameters that begin with rspo*) with immediate
printing on the Local## output device.
Business Example
As a system administrator, you want to set up logical spool servers in your SAP system to
ensure reliability and load balancing. To do so, you need to create a logical server and assign
an existing output device to it.
1. In your SAP system, create a logical server called TestPrint with the mapping to AAS
and PAS as alternative server. Classify it as a Test Server.
a) In your SAP system, start the transaction SPAD.
Alternatively, start transaction SPOOL and navigate to Important Spool Reports /
Transactions → Spool Administration → Spool Administration.
b) On the Devices / servers tab, in the line Spool Servers, choose Display (leave the input
field to the left empty).
c) If you cannot find the Create button, choose Change to switch to change mode.
d) Choose Create.
2. Change output device Local## so that the logical server TestPrint is used as the spool
server in future. Classify the Local## output device as a test printer.
a) In transaction SPAD, go back to the initial screen.
b) On the Devices / servers tab, in the line Output Devices, choose Display (leave the input
field to the left empty).
d) On the Device Attributes tab page, enter the TestPrint logical spool server as the
Spool Server.
3. Output any list (for example, all profile parameters that begin with rspo*) with immediate
printing on the Local## output device.
a) To create the proposed list, start transaction RSPFPAR.
c) Choose Execute.
e) In the dialog box that appears, use the F4 value help to select output device Local##.
f) In the Properties section, choose Immediately as Print Time. You may have to confirm
a prompt regarding the formatting.
g) Choose Continue.
b) On the Output Controller: List of Spool Requests screen, select your most recent spool
request.
d) In the List of Spool Requests, select the spool request and display the corresponding
output request.
Result: The output request should have the status Compl..
Note:
It may take some time until the output request is displayed in status
Complete.
e) In the List of Output Requests, select Choose detail for the output request.
Result: You can find the name of the real spool server used for the output at the
bottom of the list (Application Server Instance row).
Business Example
As a system administrator, you want to analyze and delete the spool requests that you
generated earlier in your SAP system and that have been already printed.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, display all the spool requests that you generated in the previous
exercises using SP01.
2. Execute the report RSPO1041 (in dialog) to delete all of your spool requests that had
successful output requests.
Business Example
As a system administrator, you want to analyze and delete the spool requests that you
generated earlier in your SAP system and that have been already printed.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, display all the spool requests that you generated in the previous
exercises using SP01.
a) Start transaction SP01.
Alternatively, start transaction SPOOL and navigate to Important Spool Reports /
Transactions → Spool Requests / Output Requests → Display → Display Spool
Requests.
b) Restrict the result list to spool requests generated by your TRAIN-## user.
This is the default selection as well as the creation date and the client.
Hint:
To display the output requests for a spool request, select a spool request
and choose Output Requests (F5).
2. Execute the report RSPO1041 (in dialog) to delete all of your spool requests that had
successful output requests.
a) Start transaction SA38.
e) In the Further conditions area, enter your course user TRAIN-## as Creator.
g) Observe which spool requests were deleted in the Delete Old Spool Requests log.
You can also check in SP02 if the spool requests with the status Completed were
deleted.
Note:
In practice, you will schedule the RSPO1041 report as a periodic
background job with an appropriate variant.
Business Example
Reports that should run on a regular basis and long-running programs are scheduled as
background jobs in the system. It is the responsibility of the system administrator to schedule
jobs and monitor the system's background processing to ensure that it is running correctly.
As a system administrator, you want to check how background processing is configured in
your SAP system.
1. How many background processes are currently configured in your SAP system?
2. How can you change the number of configured background work processes on an
application server instance? What do you need to consider when you want to change the
configuration?
3. Assume that all background work processes in your system are currently processing and
there are, therefore, no free resources for other jobs. Can you make additional
background work processes available without restarting the SAP system?
4. Use the Analysis Tool - Background Processing (Simple Tests) to perform tests on the
background processing configuration in the system.
Business Example
Reports that should run on a regular basis and long-running programs are scheduled as
background jobs in the system. It is the responsibility of the system administrator to schedule
jobs and monitor the system's background processing to ensure that it is running correctly.
As a system administrator, you want to check how background processing is configured in
your SAP system.
1. How many background processes are currently configured in your SAP system?
a) Start transaction SM50.
b) Choose System-Wide List to display all work processes configured in the SAP system.
c) Count the number of background work processes displayed (work processes of type
BTC).
2. How can you change the number of configured background work processes on an
application server instance? What do you need to consider when you want to change the
configuration?
a) You can change the number of batch work processes on an instance by setting the
parameter rdisp/wp_no_btc in the instance profile in transaction RZ10.
You can check the value of the parameter with transaction RZ11 or transaction
RSPFPAR.
To make the changes effective, you need to restart the individual instance or the entire
SAP system.
3. Assume that all background work processes in your system are currently processing and
there are, therefore, no free resources for other jobs. Can you make additional
background work processes available without restarting the SAP system?
a) If you have defined operation modes (transaction RZ04), you can provide your system
with additional background work processes. You can then perform a manual operation
mode switch using CCMS Control Panel (transaction RZ03) or use the time table in
transaction SM63 to specify the current operation mode. In this case, there is no need
to restart your system to make the changes effective.
4. Use the Analysis Tool - Background Processing (Simple Tests) to perform tests on the
background processing configuration in the system.
a) Call the transaction SM65.
c) Select All background servers to perform the tests on all application server instances
where batch work processes are configured.
d) Choose Execute.
Business Example
As a system administrator, you are responsible for scheduling jobs and monitoring the
system's background processing to ensure that it is running correctly. You want to schedule
background jobs that run in the system when a certain start condition is reached.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create a periodic, time-based job with the following properties:
Job Name TIME-JOB-##
Job Class C
Target Server <Leave empty>
Step ABAP Program: RSPFPAR with variant SAP&LOGIN
Hint:
Bear in mind that the system time (System → Status) is the relevant time for
jobs.
2. Find out details for the job you have created, such as the class, client, job ID, user who has
scheduled and released the job, and the work process that has executed the job.
1. Create a variant DISP_## in transaction SA38 for the RSPFPAR report, so that it only
displays profile parameters for the ABAP dispatcher.
2. In transaction SA38, run the RSPFPAR report in the background using the created variant.
3. Display the job in the Job Overview and the check which parameters appear in the spool
list that has been generated.
1. Use the job wizard to schedule a background with the following properties:
Job Name TIME-WIZ-##
Job Class C
Target Leave empty
Step ABAP Program: RSPFPAR with variant DISP_##
Business Example
As a system administrator, you are responsible for scheduling jobs and monitoring the
system's background processing to ensure that it is running correctly. You want to schedule
background jobs that run in the system when a certain start condition is reached.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create a periodic, time-based job with the following properties:
Job Name TIME-JOB-##
Job Class C
Target Server <Leave empty>
Step ABAP Program: RSPFPAR with variant SAP&LOGIN
Hint:
Bear in mind that the system time (System → Status) is the relevant time for
jobs.
c) Choose Step.
f) In the Variant field, choose the F4 value help to select the SAP&LOGIN variant.
g) Choose Save.
k) Enter the actual date and the time <system time + 3 minutes>.
o) In the Start Time dialog box, choose Save to save the start condition.
Note:
A periodic job is always scheduled by its immediate predecessor during
processing, so your periodic jobs will begin to display in the system after
the previous periodic job has started. Therefore, in the Job Overview, only
the next periodic job is displayed.
2. Find out details for the job you have created, such as the class, client, job ID, user who has
scheduled and released the job, and the work process that has executed the job.
a) Select TIME-JOB-## by double-clicking on it.
Hint:
Spool lists are created only for job steps that contain ABAP programs with
output. They are only printed immediately if you have made the
corresponding setting in the printer settings in the definition of the job
step or in your user defaults (transaction SU3).
b) Depending on the settings, you will already see the delay time (in seconds) in the Delay
column.
Hint:
Possible reasons for delays include, for example, occupied background
work processes or the fact that the time-controlled job scheduler ran
periodically, but not at the exact planned start time of the job.
1. Create a variant DISP_## in transaction SA38 for the RSPFPAR report, so that it only
displays profile parameters for the ABAP dispatcher.
a) Start transaction SA38.
c) Choose Execute.
h) Leave the other fields unchanged and choose Save to save the new variant.
Note:
You can also create variants in the ABAP editor (transaction SE38).
2. In transaction SA38, run the RSPFPAR report in the background using the created variant.
a) Start transaction SA38.
d) In the Variant Name field, use the F4 value help to select the DISP_## variant.
3. Display the job in the Job Overview and the check which parameters appear in the spool
list that has been generated.
a) Start transaction SM37.
c) In the Job Overview, double-click on the Spool list button in the row of the RSPFPAR job
to open the spool list.
1. Use the job wizard to schedule a background with the following properties:
Job Name TIME-WIZ-##
Job Class C
Target Leave empty
Step ABAP Program: RSPFPAR with variant DISP_##
b) Choose Continue.
c) Fill the screens as specified in the task description. Use the value help wherever
possible. Where no values are specified, use the default values.
Business Example
As a system administrator, you are responsible for scheduling jobs and monitoring the
system's background processing to ensure that it is running correctly. You want to schedule
background jobs that are triggered by certain events.
1. Copy the time-based background job TIME-JOB-## from the previous exercise and name
it EVENT-JOB-##.
Note:
If your system does not have a job TIME-JOB-##, you can copy another job or
create a new one in SM36 .
1. Trigger customer event EVENT_## in a new session and check if the job has run
successfully in the Job Overview.
2. Optional: Trigger the event EVENT_## with sapevt at the operating system level of the host
where your SAP system is running on. For this you have to be logged on with user
<sid>adm at operating system level. Check if the job has run successfully in the Job
Overview.
Hint:
If the name of the event you defined contains a blank character, you must
specify the event in quotation marks when you call sapevt.
Business Example
As a system administrator, you are responsible for scheduling jobs and monitoring the
system's background processing to ensure that it is running correctly. You want to schedule
background jobs that are triggered by certain events.
c) In the Event field of the Event Definition dialog box, enter EVENT_##.
1. Copy the time-based background job TIME-JOB-## from the previous exercise and name
it EVENT-JOB-##.
Note:
If your system does not have a job TIME-JOB-##, you can copy another job or
create a new one in SM36 .
e) Choose Release.
j) Choose Save to save the start condition and to release the job.
Hint:
If the EVENT-JOB-## job does not appear in the Job Overview after you
have released it, change the selection criteria on the initial screen of
transaction SM37. Here, in the Job Start Condition area, select the entry
EVENT_## or * for field Or after event.
1. Trigger customer event EVENT_## in a new session and check if the job has run
successfully in the Job Overview.
a) Start transaction SM64 in a new GUI window.
c) Choose Trigger....
2. Optional: Trigger the event EVENT_## with sapevt at the operating system level of the host
where your SAP system is running on. For this you have to be logged on with user
<sid>adm at operating system level. Check if the job has run successfully in the Job
Overview.
Hint:
If the name of the event you defined contains a blank character, you must
specify the event in quotation marks when you call sapevt.
a) If you have not already done so, log on to the operating system level of the host where
your SAP system is running on using with user <sid>adm, for example, the Remote
Desktop Connection.
d) Optional: Open the trace file dev_evt that was created in the current directory.
Business Example
As a system administrator, you are responsible for scheduling jobs and monitoring the
system's background processing to ensure that it is running correctly. You want to schedule
background jobs that execute external commands and programs at the operating system
level.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create a background job with the following properties:
Job Name EXT-PROG-##
2. In the Job Overview, check the success of the scheduling and the output in the job log.
1. In your SAP system, create a background job with the following properties:
Job Name EXT-CMD-##
1. Find out if background work processes are reserved for class A jobs in your system.
Business Example
As a system administrator, you are responsible for scheduling jobs and monitoring the
system's background processing to ensure that it is running correctly. You want to schedule
background jobs that execute external commands and programs at the operating system
level.
Note:
In this exercise, when an object name or value contains ##, replace ## by the
number your trainer assigned to you.
1. In your SAP system, create a background job with the following properties:
Job Name EXT-PROG-##
c) Choose Step.
Note:
You can analyze the Control flags. Leave the default values.
f) Choose Save.
2. In the Job Overview, check the success of the scheduling and the output in the job log.
a) Choose Own jobs.
b) Choose Create.
Note:
In contrast to external programs, for external commands you can assign
“name-specific” scheduling authorizations to end users in field Check
Module.
f) Optional: You can test your external command directly. Choose Execute in the
overview of transaction SM69. No additional parameters are needed. Choose Execute
again.
1. In your SAP system, create a background job with the following properties:
Job Name EXT-CMD-##
Period none
c) Choose Step.
e) In the Name field, use the F4 value help to select Z_OSUSER_## command.
f) In the OS field, use the F4 value help to select Linux as operating system.
Note:
You can analyze the Control flags. Leave the default values.
g) Choose Save.
m) Choose Own jobs to see whether the execution of your job EXT-CMD-## was
successful.
1. Find out if background work processes are reserved for class A jobs in your system.
a) Start transaction RZ04.
Business Example
As a system administrator, you want to ensure good performance for business processes.
You therefore regularly monitor the SAP systems in your landscape and take preventative
action when required.
1. In CCMS Monitor Sets (transaction RZ20), open the Entire System monitor from the SAP
CCMS Monitor Templates monitor set.
2. In the Current system status view, find out what is the current average dialog response
time for the instances in your system.
3. In the Open alerts view, select all alerts regarding dialog response time that have occurred
in the past.
5. Complete the alert. Does the completed alert still appear in the list? How can you display
the completed alert again?
Note:
Analysis tools are not assigned to all attributes. If you know of any suitable
analysis functions yourself, you can assign them to the attributes. This option
is not dealt with as part of this course, however.
Business Example
As a system administrator, you want to ensure good performance for business processes.
You therefore regularly monitor the SAP systems in your landscape and take preventative
action when required.
1. In CCMS Monitor Sets (transaction RZ20), open the Entire System monitor from the SAP
CCMS Monitor Templates monitor set.
a) In your SAP system, start transaction RZ20.
b) To expand the SAP CCMS Monitor Templates set, choose the plus sign beside the set.
2. In the Current system status view, find out what is the current average dialog response
time for the instances in your system.
a) Expand branch <SID> → R/3 Services → Dialog → <Instance> to find the monitoring
attribute ResponseTimeDialog.
Examine the ResponseTimeDialog attribute.
3. In the Open alerts view, select all alerts regarding dialog response time that have occurred
in the past.
a) In the application function bar, choose Open alerts.
b) Select the ResponseTimeDialog attribute and choose Display alerts or simply double-
click the ResponseTimeDialog element.
Result: All alerts regarding dialog response time are displayed on the Alert Display
screen.
c) To return to the Alert Display, choose Exit in the upper right-hand corner.
5. Complete the alert. Does the completed alert still appear in the list? How can you display
the completed alert again?
Note:
Analysis tools are not assigned to all attributes. If you know of any suitable
analysis functions yourself, you can assign them to the attributes. This option
is not dealt with as part of this course, however.
Hint:
The alerts that have not been yet completed are displayed with status
ACTIVE.
You might also see other alerts that have the status AUTO_COMPLETE.
These alerts were completed by the system automatically, to leave room
for new alert notifications in the alert area of the monitor segment.
Business Example
As an SAP system administrator in your organization, you want to troubleshoot problems in
the SAP system using trace functions.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. Activate the SQL trace for your user in the Performance Trace (transaction ST05).
2. In a new GUI window, start transaction SA38 and execute the program RSUSR000 that
displays the list of all logged users.
Result: The list of users logged on the application servers is displayed. The information is
retrieved from the database.
3. Go back to the Performance Trace, deactivate the trace and evaluate it.
Business Example
As an SAP system administrator in your organization, you want to troubleshoot problems in
the SAP system using trace functions.
Note:
In this exercise, when the values include ##, replace the characters by the number
your instructor has assigned to you.
1. Activate the SQL trace for your user in the Performance Trace (transaction ST05).
a) Call transaction ST05.
2. In a new GUI window, start transaction SA38 and execute the program RSUSR000 that
displays the list of all logged users.
a) Start transaction SA38 in a new GUI session.
c) Choose Execute.
Result: The list of users logged on the application servers is displayed. The information is
retrieved from the database.
3. Go back to the Performance Trace, deactivate the trace and evaluate it.
a) Back in transaction ST05 choose Deactivate Trace.
d) Choose Execute.
f) Select the line that contains the Object Name with the value USR02.
g) You can display the SAP Dictionary information for this object using the Display DDIC
Information button from the application function bar.
i) You can display the execution plan for the SQL statement with the Display Execution
Plan button.