ADM100
SAP Web AS Administration I
SAP NetWeaver
Date
Training Center
Instructors
Education Website
Participant Handbook
Course Version: 2005 Q2
Course Duration: 5 Day(s)
Material Number: 50071643
An SAP course - use it to learn, reference it for work
Copyright
Copyright © 2005 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Trademarks
•
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are
registered trademarks of Microsoft Corporation.
•
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
•
ORACLE® is a registered trademark of ORACLE Corporation.
•
INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks
of Informix Software Incorporated.
•
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
•
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,
VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of
Citrix Systems, Inc.
•
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Massachusetts Institute of Technology.
•
JAVA® is a registered trademark of Sun Microsystems, Inc.
•
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
•
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP
EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all
over the world. All other products mentioned are trademarks or registered trademarks of their
respective companies.
Disclaimer
THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY
DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT
LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT,
GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN
NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL,
CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING
WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM
THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.
About This Handbook
This handbook is intended to complement the instructor-led presentation of this
course, and serve as a source of reference. It is not suitable for self-study.
Typographic Conventions
American English is the standard used in this handbook. The following typographic
conventions are also used.
Type Style
Description
Example text
Words or characters that appear on the screen. These
include field names, screen titles, pushbuttons as well as
menu names, paths, and options.
Also used for cross-references to other documentation
both internal (in this documentation) and external (in
other locations, such as SAPNet).
2005/Q2
Example text
Emphasized words or phrases in body text, titles of
graphics, and tables
EXAMPLE TEXT
Names of elements in the system. These include report
names, program names, transaction codes, table names,
and individual key words of a programming language,
when surrounded by body text, for example SELECT
and INCLUDE.
Example text
Screen output. This includes file and directory names
and their paths, messages, names of variables and
parameters, and passages of the source text of a program.
Example text
Exact user entry. These are words and characters that
you enter in the system exactly as they appear in the
documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you
replace these words and characters with appropriate
entries.
© 2005 SAP AG. All rights reserved.
iii
About This Handbook
ADM100
Icons in Body Text
The following icons are used in this handbook.
Icon
Meaning
For more information, tips, or background
Note or further explanation of previous point
Exception or caution
Procedures
Indicates that the item is displayed in the instructor’s
presentation.
iv
© 2005 SAP AG. All rights reserved.
2005/Q2
Contents
Course Overview .............................................................................. ix
Course Goals................................................................................. ix
Course Objectives ............................................................................ x
Unit 1: Basics....................................................................................1
What Is an SAP System?.................................................................... 2
Process of a System Logon ................................................................. 7
Configuring SAP Logon .................................................................... 11
Analysis Transactions ...................................................................... 24
Unit 2: Starting and Stopping the SAP System........................................ 37
System Start: Process ..................................................................... 38
System Start: Logs ......................................................................... 49
System Shutdown: How and Why? ...................................................... 55
Appendix: Starting and Stopping Under Other Operating Systems.................. 63
Appendix - Database Logs ................................................................ 71
Unit 3: Introduction to System Configuration ......................................... 81
How the System Evaluates its Parameters.............................................. 82
How to Set System Parameters .......................................................... 90
Setting up Operation Modes ............................................................. 101
Unit 4: Access to Help...................................................................... 117
Configuring the Online Documentation ................................................. 118
Unit 5: Fundamentals of Working with the Database ...............................137
Architecture of Database Systems ...................................................... 138
Backing Up the Database Contents ..................................................... 141
Overview: Monitoring the Database..................................................... 150
Unit 6: Basics of User Administration ..................................................159
User Administration Concept............................................................. 160
Authorization Concept .................................................................... 169
Login Parameters and User Info......................................................... 183
Appendix: Advanced User Administration Topics ..................................... 189
2005/Q2
© 2005 SAP AG. All rights reserved.
v
Contents
ADM100
Unit 7: Setting Up Remote Connections ...............................................199
Fundamentals and Types of RFC ....................................................... 200
Setting Up RFC Connections ............................................................ 205
Unit 8: Introduction to System Security................................................221
Security in the SAP Environment ........................................................ 222
Unit 9: Working with the Transport System ...........................................237
Data Structure of SAP Systems and System Landscapes ........................... 238
Performing and Checking Transports ................................................... 245
Unit 10: Support Packages, Plug-Ins, and Add-Ons ................................265
Term Definition: Support Packages ..................................................... 266
Importing Support Packages ............................................................. 271
Updating the Tools......................................................................... 292
Importing SAP Notes ...................................................................... 299
Unit 11: Including Printers in SAP Systems...........................................309
Configuring Printers in SAP Systems ................................................... 310
Concept of Logical Spool Servers ....................................................... 328
Managing Spool Requests ............................................................... 339
Unit 12: Scheduling Background Tasks................................................351
Fundamentals of Background Processing.............................................. 352
Time-Based Scheduling of Jobs ......................................................... 364
Event-Based Scheduling of Jobs ........................................................ 373
Background Processing: Other Topics.................................................. 381
Job Scheduling: Extending the Standard............................................... 395
Unit 13: Archiving ...........................................................................403
Fundamentals of SAP Data Archiving .................................................. 404
Performing Data Archiving................................................................ 411
Accessing Archived Data ................................................................. 425
Unit 14: System Monitoring ...............................................................435
Monitoring Architecture ................................................................... 436
Including Remote Systems ............................................................... 449
Creating Your Own Monitors ............................................................. 457
Properties Variants and Threshold Values ............................................. 466
vi
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Contents
Concept of the SAP Solution Manager ................................................. 476
Unit 15: Structured Troubleshooting ...................................................491
Trace Options .............................................................................. 492
Troubleshooting Procedure............................................................... 505
Appendix: Troubleshooting Example ................................................... 509
Glossary .......................................................................................539
Index ............................................................................................547
2005/Q2
© 2005 SAP AG. All rights reserved.
vii
Contents
viii
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
Course Overview
This SAP course provides a broad insight into the many tasks of SAP system
administrators and creates a solid foundation for the training of SAP system
administrators, based on the knowledge acquired in the SAPTEC course
(Fundamentals of SAP Web AS). The focus of this course is on the SAP Web
Application Server ABAP.
This course is a required prerequisite for attending many advanced courses in the
SAP System Administration curriculum.
Note: This course deals exclusively with SAP Web Application Server
ABAP. For content and instructional reasons, however, the course document
refers to SAP Web Application Server Java at certain points. The ADM200
course provides information about the administration of SAP Web AS Java.
Target Audience
This course is intended for the following audiences:
•
•
•
•
SAP system administrators
Technology Consultants
Those responsible for IT
People involved in the administration of SAP systems
Course Prerequisites
Required Knowledge
•
•
2005/Q2
Attendance of the SAPTEC course or knowledge of the content addressed in
this course
Basic operating system and database knowledge
© 2005 SAP AG. All rights reserved.
ix
Course Overview
ADM100
Course Goals
This course will prepare you to:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Start and stop SAP systems
Configure SAP systems
Configure the online documentation
Perform periodic, automated work with the database
Use basic functions of SAP data archiving
Use transport functions in SAP systems
Import Support Packages, Plug-Ins, and Add-Ons
Use background processing efficiently
Define and include printers
Perform basic user administration tasks
Set up remote connections
Set up system monitoring
Describe the SAP Solution Manager
Perform structured troubleshooting
Explain various system security terms in the SAP environment
Course Objectives
After completing this course, you will be able to:
•
•
•
•
•
•
•
•
•
•
•
•
•
x
Start and stop SAP systems
Set up system parameters
Configure help
Schedule database backups
Use SAP data archiving
Perform and check transports
Import Support Packages, Plug-Ins, and Add-Ons
Schedule background tasks
Configure printers in the SAP system
Create and manage users
Set up remote connections
Monitor the system
Describe the SAP Solution Manager
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Course Overview
•
•
Perform structured troubleshooting
Use system security terms correctly in the SAP environment
SAP Software Component Information
The information in this course pertains to the following SAP Software Components
and releases:
2005/Q2
© 2005 SAP AG. All rights reserved.
xi
Course Overview
xii
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 1
Basics
Unit Overview
This unit introduces basic terms and processes, as well as the structure and architecture
of an SAP system.
In addition to the process of a system logon, you will learn how to set up SAP Logon
and how to use a range of important analysis transactions.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
Outline the structure and the architecture of an SAP system
List the technical components of the SAP Web Application Server
Use the terms system and instance correctly
Describe the process of a system log on
Describe the technology for dialog work process multiplexing
Set up the SAP Logon program
Explain the use of logon groups
Call central administration functions in the system
Unit Contents
Lesson: What Is an SAP System?................................................... 2
Lesson: Process of a System Logon ................................................ 7
Lesson: Configuring SAP Logon................................................... 11
Exercise 1: SAP Logon and Logon Groups.................................. 19
Lesson: Analysis Transactions..................................................... 24
Exercise 2: Common Administration Transactions.......................... 27
2005/Q2
© 2005 SAP AG. All rights reserved.
1
Unit 1: Basics
ADM100
Lesson: What Is an SAP System?
Lesson Overview
In this lesson, you will learn about the structure and architecture of an SAP system,
and how to use the terms system and instance correctly.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Outline the structure and the architecture of an SAP system
List the technical components of the SAP Web Application Server
Use the terms system and instance correctly
Business Example
You want to learn about the architecture of an SAP system.
What Is an SAP System?
An SAP System consists of the components shown in the graphic: Exactly one
database and one or more instances. The instance that, together with the database,
forms a runnable SAP system is known as the central instance. There should be a
central instance configured in every SAP system. A central system exists if the
system contains only a single instance, and this is running together with its database
on one host.
2
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: What Is an SAP System?
Figure 1: The Elements of an SAP System
It is certainly possible to install two instances of a system or even of different systems
on one server. When configuring two systems (or their databases) on one server, you
should ensure that the two systems are clearly differentiated, otherwise a conflict
situation will eventually occur during the use of common resources (such as program
libraries), especially if one system is to be upgraded while the other is to continue to
be used with the same release.
Within a company, no SAP System IDs (SIDs) should be assigned more than once.
You can only perform a meaningful data exchange with two systems with the same
SID only with a great deal of effort (renaming the systems).
Modern SAP systems (based on SAP Web AS 6.40 or higher) also have multiple Java
components, which are known collectively as SAP Web AS Java.
Example: Elements of an ECC 5.0 system
•
•
•
•
•
•
2005/Q2
Database with an ABAP schema and a Java schema
ABAP: central instance
ABAP: Message server, Gateway, Internet Communication Manager (optional)
Java: Central instance (one Java dispatcher, at least one Java server)
Java: Central Services instance - (Java) message server and (Java) enqueue
process
Java: Software Deployment Manager (SDM)
© 2005 SAP AG. All rights reserved.
3
Unit 1: Basics
ADM100
Figure 2: SAP Web Application Server (as of SAP Web AS 6.40)
The SDM is not shown in the figure.
What Is an Instance of an SAP System?
An instance of an SAP system is an administrative unit where the components of an
SAP system, that provide one or more services, are combined. The services provided
are started and stopped together. All components of an (ABAP) instance are provided
with parameters using a common instance profile.
4
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: What Is an SAP System?
Figure 3: The Composition of an (ABAP) Instance
These components currently include the dispatcher, the work processes, the gateway,
the assigned main memory areas, and an Internet Communication Manager (ICM), if
one is configured.
An instance always has exactly one dispatcher. The start of an instance always begins
with the start of the associated dispatcher. An instance requires a minimum of two
dialog work processes. Otherwise it is not possible to start it. Multiple dispatchers can
be configured on one host, but these dispatchers must have different system (instance)
numbers. The default for the instance number of a dispatcher is 00; that is, port 3200
receives communication for this dispatcher. If there are two instances on one machine,
the port numbers 3200 and 3201 are usually assigned, and so on. The dispatcher also
starts the SAP Web AS Java, if, in addition to the ABAP instance, there is a Java
instance (installed) to be used.
An instance is also called the application server in the software-oriented view of the
client-server model. The application server provides the runtime environment for the
business applications of SAP systems.
2005/Q2
© 2005 SAP AG. All rights reserved.
5
Unit 1: Basics
ADM100
Lesson Summary
You should now be able to:
•
Outline the structure and the architecture of an SAP system
•
List the technical components of the SAP Web Application Server
•
Use the terms system and instance correctly
Related Information
•
•
•
SAPTEC – Fundamentals of SAP Web AS
SAP Library
SAP Notes
–
–
6
SAP Note 21960: Several instances/systems on one UNIX computer (and
SAP Notes linked from there)
SAP Note 39412: How many work processes to configure
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Process of a System Logon
Lesson: Process of a System Logon
Lesson Overview
In this lesson, you will learn about the process of a system logon, and about dialog
work process multiplexing.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the process of a system log on
Describe the technology for dialog work process multiplexing
Business Example
You want to understand the process of a system logon.
Process of a System Logon
To be able to create a connection between the front end and an instance of an SAP
system, the sapgui.exe program requires various information in the form of start
parameters. This parameter string is usually generated by the saplogon.exe
program, using information about the system selected for logon. This information
comes partly from the configuration files of SAP Logon, and partly from a direct
request to the message server of the selected system (see steps 1 and 2 in the following
figure). SAP Logon then starts the SAP GUI with these specifications. In this way, an
instance with good performance is selected for log on when log on uses logon groups.
2005/Q2
© 2005 SAP AG. All rights reserved.
7
Unit 1: Basics
ADM100
Figure 4: Process of a System Logon
After the transfer of the logon screen from the dispatcher to the front end (not shown in
the figure), SAP GUI sends the user's logon data to the instance (step 3 in the figure).
After the dispatcher has determined a free work process to process the logon, it
transfers the logon data to this work process (step 4). The work process, in turn, checks
whether the received combination of user ID and password is known to the system
using a request to the database (steps 5-8). A positive response from the database
prompts the work process to return the initial screen of the system to the front end.
During a logon session, the assignment of the user to the instance is unique. Only
during a new logon can the user possibly be assigned to a different instance by the
message server.
Dialog Work Process Multiplexing
The processing of a transaction that consists of multiple screens is usually executed
using multiple, different dialog work processes. This distribution is called work
process multiplexing. Work process multiplexing means that a system function whose
content is logically connected but consists of multiple substeps can be processed
by various dialog work processes. These steps, where the content is connected, are
described as transactions. A transaction that consists of multiple screens, such as
screens 100 and 200 can also be processed by multiple dialog work processes.
8
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Process of a System Logon
Figure 5: Work Process Multiplexing
The figure shows two screens of a transaction (100 and 200), for which the input is
handled by two different dialog work processes. The multiplexing procedure is used
exclusively for dialog work processes. All other work process types process entire
functions; that is, complete business processes.
As dialog work processes may process only parts of transactions that are connected
from a business point of view; the update procedure with the update work process is
widely used in SAP systems (see also the SAPTEC course).
2005/Q2
© 2005 SAP AG. All rights reserved.
9
Unit 1: Basics
ADM100
Lesson Summary
You should now be able to:
•
Describe the process of a system log on
•
Describe the technology for dialog work process multiplexing
10
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
Lesson: Configuring SAP Logon
Lesson Overview
In this lesson, you will learn how to configure the SAP Logon program. The concept
of logon groups will also be introduced.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Set up the SAP Logon program
Explain the use of logon groups
Business Example
You want to use logon groups to restrict user logons to certain application servers of
your system.
Setting Up SAP Logon
The SAP Logon program provides users with a convenient logon to an SAP system
with the SAP GUI for Windows (from Windows-based front ends). SAP Logon
evaluates various configuration files that are stored on the front end. These files can
also be edited using SAP Logon.
In principle, SAP Logon simply starts the SAP GUI for a selected SAP system with
certain parameters (see also SAP GUI connect string).
Figure 6: SAP Logon
2005/Q2
© 2005 SAP AG. All rights reserved.
11
Unit 1: Basics
ADM100
You can make various general settings through the SAP Logon Options (see figure
above). You can, for example, set the trace level for SAP GUI connections in this way.
Passwords can also be written to the the trace file generated in this way, so you should
use this option only with great care; the trace files should be deleted afterwards.
You can use the Groups... button (for group selection) to create a new connection to a
system. This connection uses the logon groups concept, meaning that the message
server always assigns a new logon to the instance with the best performance in the
selected logon group. The configuration file sapmsg.ini is evaluated to display the
systems available for selection. The message server of the selected system is queried
to discover the available logon groups. So that the connection to the message server of
the system specified in sapmsg.ini works, it is necessary for the Microsoft Windows
file services to specify the correct message server communication port for the selected
system ID. A connection is then created to the relevant host and the message server
running on it using the information from sapmsg.ini and services.
You can use the Server... button (for server selection) to create a connection to a
specific instance of an SAP system. As with the Groups... button, information about
the instances that are available for selection is collected from the message server.
Figure 7: Setting Up SAP Logon
With the New Item... button, you can create a connection to an SAP system that need
not be listed in the sapmsg.ini and services files. Therefore, you enter all of the system
information that is relevant for a logon here yourself. The name of the host on which
you want to contact an instance, and its system or instance number are essential, as
12
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
are the SID of the system and a description. The instance number specifies the last
two digits of the 4 digit port address through which the dispatcher of the specified
instance can be contacted. The first two digits are fixed, and are 32. This means that
port numbers between 3200 and 3299 are possible. The ports 3298 and 3299 are,
however, assigned to the niping and saprouter programs by default (although this can
be changed). For more information about this, see the SAP Library for the SAP Web
AS with the search term 3298.
You can use the Change Item... button to change settings for a connection, such as its
name in SAP Logon. Through the Advanced button (on the Properties dialog box),
you can, for example, restrict the amount of data transferred (system to front end),
to take account of slow network connections (see also SAP Note 161053: Using
SAPGUI in WAN).
You can also specify a SAProuter string for SAP GUI connections. A SAProuter is
then assigned the task of transferring data for this connection. SAProuter strings can
also be specified using aliases. These aliases are decoded using the saproute.ini file.
Hint: If you do not want to allow users to edit the system entries, you can
use the SAP Logon Pad program.
Which files are stored where? The following list shows the files with their possible
storage locations; in the case of multiple possible locations, the search sequence is
shown:
•
saplogon.ini, sapmsg.ini, saproute.ini:
•
–
SAP GUI directory
–
Windows directory
services:
–
WINNT → system32 → drivers → etc → Services
(SAP) GUI Connect String
The SAP GUI connect string describes a number of call parameters for the SAP GUI
program. In its simplest form, a SAP GUI call looks like this:
sapgui <host> <instance number>
If a logon group is to be used, the connection structure has a somewhat more complex
structure. Now,
/M/<message server host>
is used to specify the host of the message server of the selected system, and then
2005/Q2
© 2005 SAP AG. All rights reserved.
13
Unit 1: Basics
ADM100
/S/<message server port>
is used to specify the port of the message server, and
/G/<logon group>
is used to specify the name of the logon group to be selected.
This, therefore, results in the following string:
sapgui /M/<message server host>/S/<message server
port>/G/<logon group>
For example:
sapgui /M/twdf200/S/3600/G/SPACE
You can use the command line switch /WAN to declare the connection to be a Low
Speed Connection, with the corresponding savings in network traffic.
Using Logon Groups
SAP systems sometimes have significantly more than just one or two assigned
instances. Each of these instances provides buffer areas for various objects, such as
for programs, dictionary objects, screen structures, and table contents.
These buffers are filled with data and continuously updated during the runtime
of an instance; that is, the system attempts, using various algorithms, to organize
the contents of the buffer so that the frequently queried data is in the buffer. Data
that is used frequently but changes only very rarely is buffered. This means that
a cross-section of all programs called on this instance is collected, especially in the
program buffer (see the following figure).
14
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
Figure 8: Program Buffer Without the Use of Logon Groups
If a large number of different applications are run, old buffer contents may be replaced
with newly requested contents. This means that the next time the older contents are
called, they must be requested from the database again. This reduces the response
time behavior of the system, in some circumstances to an appreciable extent. A
solution would be to create a program buffer that was sufficiently large to contain all
requested programs. An alternative solution is the logon group concept explained in
the following text.
Using logon groups, you can group instances with transaction SMLG (Tools CCMS →
Configuration → Logon Groups). In the example above, four instances are assigned to
the logon group SD, and three instances to the logon group FI. The message server of
the system also has these details within five minutes after the new group definitions are
saved. From now on, you can access these groups using group selection in SAP Logon.
2005/Q2
© 2005 SAP AG. All rights reserved.
15
Unit 1: Basics
ADM100
Figure 9: Program Buffer with the Use of Logon Groups
In the example, the definition of the two logon groups has the following effects:
With a logon using a logon group, the SAP Logon program connects to the message
server of the system, and receives from it the name of the currently best performing
instance of the selected logon group. SAP Logon then starts the SAP GUI program
with the connection parameters for the selected dispatcher.
Within a logon group, end users are, for example, only using a particular application.
In the example, these are the FI and SD applications. Therefore, the buffers on the
instances of each of the logon groups are filled with contents from these applications.
This means that the program buffer of each of the instances shown contains fewer
different programs than they would without the use of logon groups. Consequently,
this has two possible advantages:
1.
2.
The program buffers can be set up more economically (smaller).
Less swapping is performed for the program buffers, which therefore perform
better.
If you are able to set up very large program buffers (>1GB), setting up logon groups
for the purpose described (saving program buffer space), no longer provides any
relevant benefits. This is, of course, due to the fact that, from this sort of size, program
buffers can usually hold many programs from numerous applications simultaneously;
that is, with this type of memory, no “saving effect” is visible any longer.
16
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
SAP recommends the setting up of a single logon group (perhaps with the exception
of the central instance, as implicitly assumed previously), if you want to achieve a
completely different aim (to economically configured program buffers), that is, to
have, as far as possible, comparable response times on all instances that belong
to a logon group.
This logon group is given, for example, the name PUBLIC. If you think that it is
useful, you can decide not to include the central instance of your SAP system in
this logon group.
By default, every instance (therefore, including the central instance) is assigned to
the logon group SPACE. For more information, see the SAP Notes database, with
the search term SMLG.
2005/Q2
© 2005 SAP AG. All rights reserved.
17
Unit 1: Basics
18
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
Exercise 1: SAP Logon and Logon Groups
Exercise Objectives
After completing this exercise, you will be able to:
•
Set up the SAP Logon program
•
Set up logon groups
Business Example
You want to use logon groups to restrict user logons to certain application servers of
your system.
Task 1: Clear Existing SAP Logon Entries
This task depends on the setup of your training front end.
1.
Because there could already be entries in your local SAP Logon from other
training courses, choose the following call, if it exists:
Start → Training → SAPLogon Reset
This call edits your local saplogon.ini file so that there are no system
entries, and perhaps a dummy entry in the file.
Task 2: Set up SAP Logon Using the Groups Button
1.
Choose the Groups... button and create a new entry. Use the data that your
instructor gives you (system ID, host name) for this entry.
Task 3: Set Up Logon Groups
1.
Log on to your system using your new entry in SAP Logon (with the parameters
that your instructor gives you). Call transaction SMLG (Tools → CCMS →
Configuration → Logon Groups).
2.
Choose the Create Assignment button to create a new logon group with any name
(such as DEV_##, where ## is your group number). Assign at least one of the two
instances of your system to your new logon group. Copy and Save your entries.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
19
Unit 1: Basics
ADM100
Task 4: Using Logon Groups through Group Selection in
SAP Logon
20
1.
In SAP Logon, choose the Groups... button again to add a new entry. If the
logon group that you created previously does not yet appear in the display, the
message server has not yet registered the newly created logon group. This is
done automatically every five minutes. You can therefore generate the list again
after a few minutes.
2.
Log on to your system using the new entry in your SAP Logon.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
Solution 1: SAP Logon and Logon Groups
Task 1: Clear Existing SAP Logon Entries
This task depends on the setup of your training front end.
1.
Because there could already be entries in your local SAP Logon from other
training courses, choose the following call, if it exists:
Start → Training → SAPLogon Reset
This call edits your local saplogon.ini file so that there are no system
entries, and perhaps a dummy entry in the file.
a)
Follow the exercise instructions.
Task 2: Set up SAP Logon Using the Groups Button
1.
Choose the Groups... button and create a new entry. Use the data that your
instructor gives you (system ID, host name) for this entry.
a)
Enter the abbreviation for the system that you have been assigned, such
as DEV, in the System ID input field. Note that an entry can already exist
for a system in the sapmsg.ini file. However, this entry does not
point to the training system that you are using. Therefore, under Message
Server, enter the name of the host on which your SAP system is running
(such as twdf9999).
b)
Choose Generate list.
c)
Select a group (such as SPACE) from the list in the Groups field, and then
choose Add. Confirm the following window by choosing OK.
Task 3: Set Up Logon Groups
1.
Log on to your system using your new entry in SAP Logon (with the parameters
that your instructor gives you). Call transaction SMLG (Tools → CCMS →
Configuration → Logon Groups).
a)
Follow the exercise instructions.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
21
Unit 1: Basics
ADM100
2.
Choose the Create Assignment button to create a new logon group with any name
(such as DEV_##, where ## is your group number). Assign at least one of the two
instances of your system to your new logon group. Copy and Save your entries.
a)
In transaction SMLG, you can see a list of the logon groups that exist in
the system and the instances assigned to them.
b)
To create a new assignment, choose the Create assignment button. In the
following dialog box, enter any name for your new logon group in the
Logon Group field. Use the F4 help for the Instance input field to select an
instance that you want to assign to the new logon group. Then choose Copy.
c)
Save the list of logon groups.
d)
You can now assign additional instances to your new logon group, or create
new logon groups. To do this, choose the Create assignment button again.
Remember to Save after making entries.
Task 4: Using Logon Groups through Group Selection in
SAP Logon
1.
In SAP Logon, choose the Groups... button again to add a new entry. If the
logon group that you created previously does not yet appear in the display, the
message server has not yet registered the newly created logon group. This is
done automatically every five minutes. You can therefore generate the list again
after a few minutes.
a)
2.
Log on to your system using the new entry in your SAP Logon.
a)
22
Follow the same procedure as in task 2 and this time, choose the logon
group that you created in task 3.
Follow the exercise instructions.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring SAP Logon
Lesson Summary
You should now be able to:
•
Set up the SAP Logon program
•
Explain the use of logon groups
2005/Q2
© 2005 SAP AG. All rights reserved.
23
Unit 1: Basics
ADM100
Lesson: Analysis Transactions
Lesson Overview
In this lesson, you will obtain an overview of a number of frequently used analysis
transactions for system administration.
Lesson Objectives
After completing this lesson, you will be able to:
•
Call central administration functions in the system
Business Example
You want to obtain an overview of the transactions that help you perform your daily
work as a system administrator.
Common Administration Tasks
The transactions shown in the following figure help you to deal with daily system
administration work. You should already be familiar with the usage and interpretation
of most of these transactions.
Figure 10: Common Administration Transactions
24
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Analysis Transactions
You can use transaction SM51 to display the instances of your SAP system. From
there, it is possible, among other things, to go to the user list (transaction SM04) or the
work process overview (transaction SM50) for a selected instance.
You can use transactions SM04 and AL08 to obtain an overview of the users logged
on to the system. Note that only those users that are logged on to the instance from
which you called this transaction display in transaction SM04. You can use transaction
AL08 to obtain an overview of all users logged on to the system. Unlike SM04,
transaction AL08 provides only display functions.
Transaction SM50 provides an overview of the work processes configured for an
instance. There is also a global equivalent to this transaction (SM66), where you can
display all of the work processes for the entire SAP system. Like transaction SM50,
transaction SM66 provides other functions in addition to purely display functions.
You can use transaction SM37 to obtain an overview of the background jobs in your
SAP system.
You can manage lock entries in the lock table of the enqueue work process using
transaction SM12.
Use transaction SM21 to analyze the system log.
If you want to send all users in your SAP system a message, you can use transaction
SM02 to send a system message. It is also possible to restrict the recipients to users of
a certain client, or users that are logged on to a particular instance. A system message
appears for users when they next perform an action.
You can use transaction RZ20 to monitor the SAP system, or to centrally monitor
multiple SAP systems.
Updating Application Data
The majority of updates in the SAP system are processed by the update work process.
It is the task of the administrator to ensure smooth processing of the update. You can
use transaction SM13 to monitor the update requests.
If an update work process is not able to successfully process an update request, by
default, the end user that created the affected data receives a message from the system.
The affected update request displays in the overview of the update requests with the
status canceled. The administrator's task is to determine the cause of the termination,
and, if necessary, to correct the problem that caused it.
Use the administration data for an update request to find the cause of the termination.
You can display this information by choosing the Update header button in transaction
SM13.
2005/Q2
© 2005 SAP AG. All rights reserved.
25
Unit 1: Basics
ADM100
After you have solved the problem, the end user usually recreates the data that was not
updated. Only in exceptional cases, and then only in agreement with the department
concerned should the administrator reupdate the affected request.
26
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Analysis Transactions
Exercise 2: Common Administration
Transactions
Exercise Objectives
After completing this exercise, you will be able to:
•
Call central administration functions in the system
Business Example
You want to obtain an overview of the transactions that help you perform your daily
work as a system administrator.
Task: Basic Administrative Transactions
2005/Q2
1.
Determine the number of instances available to you in your system and their
names.
2.
How many work processes does your entire SAP system have? Which types?
3.
How many users are currently logged on to the same instance where you are
working?
4.
Call your Own Data (user defaults). In a new session, check the currently active
locks in your system. Use another new session to delete the session holding the
locks. There are two options for doing this. What happens to the locks?
© 2005 SAP AG. All rights reserved.
27
Unit 1: Basics
ADM100
Solution 2: Common Administration
Transactions
Task: Basic Administrative Transactions
1.
Determine the number of instances available to you in your system and their
names.
a)
2.
To do this, call transaction SM51 (alternatively, choose: Tools →
Administration → Monitor → System Monitoring → Servers). Your system
should have two instances, the names of which could be, for example,
twdf9999_DEV_00 and twdf9999_DEV_01.
How many work processes does your entire SAP system have? Which types?
a)
If you make the correct settings for the Process Selection (ensure that
you also display waiting processes), transaction SM66 (SAP Easy Access
menu path: Tools → Administration → Monitor → Performance →
Exceptions/Users → Active Users → Global Process Overview) will show
you that your system has, for example, eight dialog work processes, four
spool work processes, and so on. Unlike transaction SM50, transaction
SM66 shows all work processes of a system.
Hint: In transaction SM66, you can also show the work process
that is currently processing your user request by choosing Settings
and deselecting the option Hide own work processes used for
analysis.
3.
How many users are currently logged on to the same instance where you are
working?
a)
Transaction SM04 (or Tools → Administration → Monitor → System
Monitoring → User Overview) displays the number of users that are logged
on to the same instance as you.
Continued on next page
28
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Analysis Transactions
4.
Call your Own Data (user defaults). In a new session, check the currently active
locks in your system. Use another new session to delete the session holding the
locks. There are two options for doing this. What happens to the locks?
a)
2005/Q2
Choose System → User Profile → Own Data. You can set user defaults
in a new session that opens automatically. Use the call /OSM12 in the
command field to display an overview of currently active locks in your
system. Do not restrict the selection of locks. There should be an active
locks that is connected to changing your user defaults. You can either end
the session that holds the locks using transaction SM04 (Select the user
and choose the Sessions button) or obtain an overview of your sessions by
entering /O, where you can identify and end the session that holds the locks.
© 2005 SAP AG. All rights reserved.
29
Unit 1: Basics
ADM100
Lesson Summary
You should now be able to:
•
Call central administration functions in the system
30
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
Outline the structure and the architecture of an SAP system
•
List the technical components of the SAP Web Application Server
•
Use the terms system and instance correctly
•
Describe the process of a system log on
•
Describe the technology for dialog work process multiplexing
•
Set up the SAP Logon program
•
Explain the use of logon groups
•
Call central administration functions in the system
2005/Q2
© 2005 SAP AG. All rights reserved.
31
Unit Summary
32
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
The instance that, together with the database, creates a runnable SAP system, is
.
called the
Fill in the blanks to complete the sentence.
2.
What types of work processes are there in the SAP system?
Choose the correct answer(s).
□
□
□
□
□
□
3.
A
B
C
D
E
F
Update work process
Spool work process
Dialog work process
ICM work process
Enqueue work process
Instance work process
SAP systems use
technology to process user requests.
Fill in the blanks to complete the sentence.
4.
What button(s) can you use to create new entries in the SAP Logon system list?
Choose the correct answer(s).
□
□
□
□
□
□
5.
A
B
C
D
E
F
Change Item...
New Item...
Log on
Groups...
Server...
Create
What possible advantages does the correct use of logon groups offer?
Choose the correct answer(s).
□
□
□
□
2005/Q2
A
B
C
D
The users are automatically logged on to the correct system
The program buffers can be set up smaller
The instances of a logon group offer comparable response times
The program buffers may now be larger than 1 GB in size
© 2005 SAP AG. All rights reserved.
33
Test Your Knowledge
6.
ADM100
In what transaction can you obtain an overview of the instances of your SAP
system?
Choose the correct answer(s).
□
□
□
□
7.
A
B
C
D
SM50
SM51
SM52
SM04
You can use transaction
system. Transaction
to manage the lock entries of the SAP
is used to manage the update requests.
Fill in the blanks to complete the sentence.
34
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Answers
1.
The instance that, together with the database, creates a runnable SAP system,
is called the central instance.
Answer: central instance
2.
What types of work processes are there in the SAP system?
Answer: A, B, C, E
The ICM (Internet Communication Manager) is not a work process, but rather a
service of the SAP Web Application Server. An instance consists of a dispatcher
and multiple work processes. The instance itself is therefore not a work process.
In addition to the correct work process types listed above, there are also
background work processes.
3.
SAP systems use work process multiplexing technology to process user requests.
Answer: work process multiplexing
Put differently, this means that there is not a one-to-one assignment of user to
dialog work process for the entire duration of the logon.
4.
What button(s) can you use to create new entries in the SAP Logon system list?
Answer: B, D, E
You can use the Change Item... button to display the properties of an entry. You
can use the Logon button to log on the selected system. There is no Create
button in the SAP Logon program.
5.
What possible advantages does the correct use of logon groups offer?
Answer: B, C
The users still need to log on to the system in the normal way after logon groups
have been configured. Creating logon groups is not a prerequisite for setting
buffer sizes of above 1 GB.
2005/Q2
© 2005 SAP AG. All rights reserved.
35
Test Your Knowledge
6.
ADM100
In what transaction can you obtain an overview of the instances of your SAP
system?
Answer: B
Transaction SM50 lists the work processes of an instance. Transaction SM52
does not exist, and transaction SM04 calls the user list for an instance.
7.
You can use transaction SM12 to manage the lock entries of the SAP system.
Transaction SM13 is used to manage the update requests.
Answer: SM12, SM13
Transactions SM12 and SM13 are important tools for the system administrator.
36
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 2
Starting and Stopping the SAP System
Unit Overview
The topic of this lesson is the starting and stopping of an SAP system. These are two
of the basic tasks of system administration. You will also learn about the available log
and trace options, to be able to react correctly if an error occurs.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
Describe the process of the start procedure of an SAP system
Start the entire SAP system or individual instances
Evaluate start logs to analyze problems
Stop the entire SAP System or individual instances
Describe the starting and stopping of an SAP system under different operating
systems
Describe the locations of the log files for various databases
Unit Contents
Lesson: System Start: Process .................................................... 38
Exercise 3: Starting the SAP System ......................................... 45
Lesson: System Start: Logs ........................................................ 49
Lesson: System Shutdown: How and Why? ..................................... 55
Exercise 4: Stopping an SAP System ........................................ 59
Lesson: Appendix: Starting and Stopping Under Other Operating Systems 63
Lesson: Appendix - Database Logs ............................................... 71
2005/Q2
© 2005 SAP AG. All rights reserved.
37
Unit 2: Starting and Stopping the SAP System
ADM100
Lesson: System Start: Process
Lesson Overview
The topic of this lesson is the starting of an SAP system. In addition to the actual start
sequence, the concept of services under Microsoft Windows is discussed in detail.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the process of the start procedure of an SAP system
Start the entire SAP system or individual instances
Business Example
As the administrator of SAP systems, you need to stop the systems for maintenance
purposes or after changing system parameters, and then restart them.
Start Process of the SAP System
The starting of an SAP system is the basic prerequisite for being able to work with
the system. Restarts of SAP systems are also required after maintenance work on the
hardware in use and changes to the SAP system's profile. Starting an SAP system is
an initial process with which every administrator should be familiar.
Note: The start process of SAP Web AS Java is not discussed here.
38
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Process
Figure 11: Start Process of the SAP System
Starting an SAP System is performed in a number of steps and is the task of the
operating system user <sid>adm.
Start the database:
•
2005/Q2
The underlying element of the entire SAP system is the database. Before the
SAP instances are started, this must have operational status. The database is
therefore always started as the first step.
© 2005 SAP AG. All rights reserved.
39
Unit 2: Starting and Stopping the SAP System
ADM100
Start the central instance:
•
Next, the operating system collector SAPOSCOL is started, if it is not already
active. This standalone program runs in the operating system background,
independently of SAP instances. This program collects data about operating
system resources and makes this data available through the shared memory
of all SAP instances.
Note: If you later discover that SAPOSCOL has not been started, you
can start it at any time by calling transaction ST06 and choosing the path
Detail analysis Menu → OS Collector → Start.
•
The central instance with the message server and the dispatcher and its work
processes is then started. If the start up parameters are set correspondingly, the
dispatcher also starts the Internet Communication manager (ICM) and the SAP
Web AS Java (if it is installed). You should only start other (optional) instances
once the message and enqueue servers are active.
•
If the dialog instance is not running on the same host as the central instance,
the SAPOSCOL operating system collector is first started on this host (if it is
not yet running).
The dispatcher is then started with its work processes.
•
The Services Concept under Microsoft Windows
Figure 12: Services Concept
40
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Process
When starting programs in the Microsoft Windows environment, you should note
that these programs are only active as long as the user is logged on to the system.
When a user logs off, all of his or her programs are ended. The SAP system therefore
uses the concept of services to start. These programs are automatically started and
administered by the operating system. Services provide support to other programs
and run even if there are no users logged on to the host.
The Service Control Manager starts the services installed in the registry during the
startup of Microsoft Windows 2000. All services can be configured for automatic
startup.
During the installation of the SAP system, SAP and database services are installed in
addition to the operating system services.
SAP Services:
•
•
SAPOSCOL: Collects performance data for one or more SAP instances and
runs once for each host.
SAP<sid>_<instance no.>: Controls the SAP instances and runs once for each
instance.
Database Services:
•
•
2005/Q2
Create the connection to the database.
Control DB actions
© 2005 SAP AG. All rights reserved.
41
Unit 2: Starting and Stopping the SAP System
ADM100
Starting the SAP System
Figure 13: Starting the SAP System
Under Microsoft Windows 2000/2003, you can start and stop the SAP system with the
Microsoft Management Console (MMC).
To do this, the administrator logs on to the operating system as user <sid>adm, and
opens the Microsoft Management Console.
Choose the node for the central instance in the tree. Call up the context menu with the
right mouse button and choose the Start function. The system first checks whether
the database is active. If not, it is automatically started. If the database is active,
the central instance (message server and dispatcher) is started by SAP Service
SAP<SID>_<Instance no.>. The communication between the Microsoft Management
Console and the SAP Service takes place through a named pipe.
Other instances can then be started.
The status of the SAP system, individual instances, and the message server and
dispatcher are displayed in the Microsoft Management Console in accordance with the
following color legend:
•
•
•
•
42
Gray not running
Yellow is starting
Green active
Red terminated after errors
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Process
Figure 14: Start Sequence of Processes of the SAP System
The specifications of the instances; that is, the type and number of processes, main
memory sizes, and other options are controlled at the start of the instances using
profiles. These are files at operating system level that are stored in the directory
\\<SAPGLOBALHOST>\sapmnt\<SID>\sys\profile.
When the instances are started, SAP Service reads which processes (message server,
dispatcher) are to be started from the instance-specific start profile. The start profile
can be displayed in the Microsoft Management Console by right-clicking the entry for
the instance and selecting the function All tasks → View Start Profile.
The specification of the configuration of the instances is stored in the default profile
and in the instance profile. These profiles are read by the dispatcher, which starts the
work processes and creates the instance-specific configuration.
After the instance has been successfully started, all work processes connect to the
database.
2005/Q2
© 2005 SAP AG. All rights reserved.
43
Unit 2: Starting and Stopping the SAP System
ADM100
44
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: System Start: Process
Exercise 3: Starting the SAP System
Exercise Objectives
After completing this exercise, you will be able to:
•
Start an SAP system
Business Example
As the administrator of SAP systems, you need to stop the systems for maintenance
purposes or after changing system parameters, and then restart them.
Task 1: Starting with the Microsoft Management Console
Start the SAP system using Microsoft Management Console.
1.
Start the SAP system using Microsoft Management Console. Monitor the start of
the processes of your system.
To do this, log on to the server for your training system using the Terminal
Server Client.
2.
What process types are started at operating system level after your system
is started up?
3.
Check whether your system started correctly. To do this, log on to your SAP
system and call the process overview. Compare the list of processes at operating
system level with the process overview in the SAP system.
Task 2: Starting from the Command Line (Optional)
Start the SAP system using a command call.
1.
2005/Q2
Start the SAP instances by entering the command startsap. Start the central
instance first and then the dialog instances.
© 2005 SAP AG. All rights reserved.
45
Unit 2: Starting and Stopping the SAP System
ADM100
Solution 3: Starting the SAP System
Task 1: Starting with the Microsoft Management Console
Start the SAP system using Microsoft Management Console.
1.
Start the SAP system using Microsoft Management Console. Monitor the start of
the processes of your system.
To do this, log on to the server for your training system using the Terminal
Server Client.
a)
Start the Terminal Server Client and enter the physical host name under
Server. Choose the display resolution for the remote connection on your
front end, and choose Connect. Log on to the operating system as user
<sid>adm.
Start the Microsoft Management Console by selecting the appropriate icon.
Choose the node for the central instance in the Microsoft Management
Console tree. Select the desired instance and choose the Start function from
the context menu (right button). Start the dialog instance in the same way.
Hint: You should always start the central instance first.
2.
What process types are started at operating system level after your system
is started up?
a)
You can monitor the processes at operating system level with the Task
Manager or the Quick Slice tool (Start → Run: qslice).
The following process types are started at operating system level after your
system is started up: saposcol.exe, msg_server.exe, gwrd.exe, icman.exe,
and multiple disp+work.exe. There could also be additional java.exe
processes for your SAP instance.
3.
Check whether your system started correctly. To do this, log on to your SAP
system and call the process overview. Compare the list of processes at operating
system level with the process overview in the SAP system.
a)
Log on to your SAP system. The process overview Tools → Administration
→ Monitor → System Monitoring → Process Overview, transaction SM50)
displays a list of work processes for the instance to which you are logged
on. The dispatcher and all work processes are visible at operating system
level as disp+work.exe. An assignment can be made using the process ID.
Continued on next page
46
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Process
Task 2: Starting from the Command Line (Optional)
Start the SAP system using a command call.
1.
Start the SAP instances by entering the command startsap. Start the central
instance first and then the dialog instances.
a)
Start the SAP instances by entering the command startsap.
startsap syntax:
startsap name=<sid> nr=<Instanz-Nr.>
SAPDIAHOST=<Servername>
Start the central instance first and then the dialog instances.
2005/Q2
© 2005 SAP AG. All rights reserved.
47
Unit 2: Starting and Stopping the SAP System
ADM100
Lesson Summary
You should now be able to:
•
Describe the process of the start procedure of an SAP system
•
Start the entire SAP system or individual instances
48
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Logs
Lesson: System Start: Logs
Lesson Overview
In this lesson, you will become familiar with the most important log and trace files,
where the start of an SAP system is logged.
Lesson Objectives
After completing this lesson, you will be able to:
•
Evaluate start logs to analyze problems
Business Example
Problems occurred when starting an SAP system. To correct these problems, the
administrator analyzes logs and trace files that were generated during the system start.
Logging the Start Process
The start process is an especially important phase, which is logged by the operating
system, the SAP system, and the database. If the SAP system does not start up, you
can find the relevant error message in the log files. It may be that there were problems
starting the database, meaning that the SAP system could not subsequently be started.
Figure 15: Logging of the Start Process Under Microsoft Windows
2005/Q2
© 2005 SAP AG. All rights reserved.
49
Unit 2: Starting and Stopping the SAP System
ADM100
All messages that are created by services or the Microsoft Management Console are
recorded at operating system level by an event logging service, the Event Manager.
This Event Viewer writes an event log that contains the following three components:
Components of the Event Log
•
System Log:
Operating system and application messages
•
Application Log:
List of errors, warnings, and information that is generated by application software
•
Security Log:
Events such as log ons and log offs and user access to files
You can call the event log by choosing Start → Programs → Administrative Tools
→ Event Viewer. Choose the relevant component from the menu bar. The system
displays a list of errors, warnings, and information that have been generated. For
detailed information, select a particular log.
Figure 16: Logging of the Start Process in the SAP System
Logs about the start process of the SAP system are stored in the file system. If there
are problems during the start, these logs can provide useful information such as
error messages or problem descriptions. These files are stored in the home directory
(DIR_HOME) of the relevant instance.
50
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Logs
The log files STDERR<n> are created by the SAP service during the start process.
The starting processes write to the individual files, depending on the sequence in
which they are listed in the start profile. The contents of these log files therefore
depend on the individual system setup, and could, for example, be as follows:
•
•
•
STDERR1: Information about the start process of the database system
STDERR2: Information about the start process of the message server
STDERR3: Information about the start process of the dispatcher
You can set the granularity of the logged information to four levels using the profile
parameter rdisp/TRACE . The possible values for this parameter are:
•
•
•
•
0:
1:
2:
3:
Errors only
Error messages and warnings (Default)
Error messages and a short trace
Error messages and a complete trace
The higher the trace level, the larger the amount of logged information, and therefore,
the larger the size of the files. You should only increase the default value for short
periods for problem analysis.
The trace level can be set separately for individual work processes in the process
overview (transaction SM50).
2005/Q2
© 2005 SAP AG. All rights reserved.
51
Unit 2: Starting and Stopping the SAP System
ADM100
Problem Analysis
Figure 17: Problem Analysis
A variety of causes can cause the SAP system not to start correctly. To analyze the
problem, proceed as follows:
•
•
•
•
•
Check the error messages and warnings in the Event Viewer. Check that the
service SAP<SID>_<Instance Number> (such as SAPDEV_00) was started. To
do this, go to the Services window (Start → Programs → Administrative Tools
→ Services).
Check the status of the respective database system using the error log files. For
more information about this, see the lesson: Appendix - Database Logs.
Check the start log in the MMC. To do this, select the affected instance and
choose All Tasks → View Developer Traces in the context menu.
Check the error files stderr<n> that were created by SAP Service.
Check the trace files of the individual SAP work processes:
–
–
–
–
52
dev_ms : Developer trace for the message server
dev_rd : Developer trace for the gateway
dev_disp : Developer trace for the dispatcher
dev_w<m> (m is the work process number): Developer trace for the work
process
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Start: Logs
If you can still log on to the SAP system, check the system log of the SAP system
using transaction SM21.
2005/Q2
© 2005 SAP AG. All rights reserved.
53
Unit 2: Starting and Stopping the SAP System
ADM100
Lesson Summary
You should now be able to:
•
Evaluate start logs to analyze problems
54
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Shutdown: How and Why?
Lesson: System Shutdown: How and Why?
Lesson Overview
This lesson demonstrates the stopping of an SAP system, including the preparatory
activities in the system. Stopping the database is a separate process. The sequence
in which the SAP instances are shut down is important: first the dialog instances,
and finally the central instance.
Lesson Objectives
After completing this lesson, you will be able to:
•
Stop the entire SAP System or individual instances
Business Example
As the administrator of SAP systems, you need to stop the systems for maintenance
purposes or after changing system parameters, and then restart the systems.
Stopping the SAP System
It may be necessary to stop an SAP system for a variety of reasons, for example,
restarting after permanently changing profile parameters, before installing kernel
patches, or allowing hardware upgrades to be carried out.
Figure 18: Before Stopping the SAP System
2005/Q2
© 2005 SAP AG. All rights reserved.
55
Unit 2: Starting and Stopping the SAP System
ADM100
Before you stop the system, you should check the status of the system. This involves,
among other things:
•
Active Users:
Check which users are logged on using the User List (SM04).
•
Background Processing :
Check which jobs are active using the Job Overview (SM37). If jobs are
terminated by the system stop, these jobs must be rescheduled. Jobs that are
scheduled for the time when the system is stopped run automatically once the
system restarts.
•
Batch Input:
The transaction Batch Input: Session Overview (SM35) displays running batch
input jobs.
•
Update:
Use the Update Overview (SM13) to check whether update processes are
terminated by the system stop. These update records are rolled back during
the stop, and these are set to the status “init”. These records are then updated
again during the restart.
Before you stop your system, you should inform users using a system message (SM02).
Figure 19: Stopping the SAP System
56
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Shutdown: How and Why?
The stopping of the SAP system is performed in the opposite order of starting.
Stop the instances:
•
•
In the SAP system itself, in the Computing Center Management System (CCMS)
(transaction RZ03), by choosing Control → Stop SAP instance.
In the Microsoft Management Console, right-click to show the context menu and
choose the Stop function. Depending on whether you have selected an individual
instance or the SAP system, the following are stopped:
–
–
A single instance
Central instance and all dialog instances
The SAP service waits for a stop message from the MMC or from the CCMS and then
stops the SAP system. The service itself does not stop.
The services can be stopped and restarted with the Microsoft Windows Service
Control Manager.
The database is stopped using the relevant database system tools.
2005/Q2
© 2005 SAP AG. All rights reserved.
57
Unit 2: Starting and Stopping the SAP System
ADM100
58
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: System Shutdown: How and Why?
Exercise 4: Stopping an SAP System
Exercise Objectives
After completing this exercise, you will be able to:
•
Stop an SAP system
Business Example
As the administrator of SAP systems, you need to stop the systems for maintenance
purposes or after changing system parameters, and then restart them.
Task 1: Stopping with the Microsoft Management
Console
Stop the SAP system using Microsoft Management Console.
1.
Before you stop the SAP system, check which users are logged on to your
system. Send a system message.
2.
Stop the SAP system using the Microsoft Management Console.
To do this, log on to the server for your training system with the Terminal
Server Client.
Task 2: Stopping from the Command Line (Optional)
Stop the SAP system using a command call.
1.
Log on to the server with the user <sid>adm over a Telnet connection.
2.
Check whether your SAP system is running at operating system level.
3.
Enter the command stopsap to stop an instance. To stop the entire SAP system,
first stop the dialog instance and then the central instance.
The command stopsap only stops the selected instance. If the database is to be
stopped, this must be done using database tools.
2005/Q2
© 2005 SAP AG. All rights reserved.
59
Unit 2: Starting and Stopping the SAP System
ADM100
Solution 4: Stopping an SAP System
Task 1: Stopping with the Microsoft Management
Console
Stop the SAP system using Microsoft Management Console.
1.
Before you stop the SAP system, check which users are logged on to your
system. Send a system message.
a)
You can use the global user overview to display the users logged on to your
SAP system: Tools → Administration → Monitor → Performance →
Exceptions/Users → Active Users → Global Users (transactionAL08). In
this transaction, you will find your own user more than once. Transaction
AL08 uses RFC connections to collect the user information for all
instances. This means that your own user, which initiates the RFC
connections, is displayed once per instance.
To send a system message to the users, choose Tools → Administration →
Administration → System Messages (transaction SM02). Choose Create,
enter the system message text, and choose Save.
2.
Stop the SAP system using the Microsoft Management Console.
To do this, log on to the server for your training system with the Terminal
Server Client.
a)
Start the Terminal Server Client and enter the physical host name under
Server. Choose the display resolution for the remote connection on your
front end, and choose Connect. Log on to the operating system as user
<sid>adm.
Start the Microsoft Management Console by selecting the appropriate
icon. Select the desired instance(s) and choose the Stop function from the
context menu (right button). Depending on whether you have chosen an
individual instance or the SAP system, either an individual instance or the
entire SAP system stops.
Task 2: Stopping from the Command Line (Optional)
Stop the SAP system using a command call.
1.
Log on to the server with the user <sid>adm over a Telnet connection.
a)
Use the tool specified by the instructor to create a Telnet connection to your
server. Log on with the user <sid>adm and password <sid>adm.
Continued on next page
60
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: System Shutdown: How and Why?
2.
Check whether your SAP system is running at operating system level.
a)
3.
To do this, run the command tlist /t | more, to display an overview
of operating system processes.
Enter the command stopsap to stop an instance. To stop the entire SAP system,
first stop the dialog instance and then the central instance.
The command stopsap only stops the selected instance. If the database is to be
stopped, this must be done using database tools.
a)
Enter the command stopsap to stop an instance.
stopsap syntax:
stopsap name=<sid> nr=<Instanz-Nr.>
SAPDIAHOST=<Servername>
To stop the entire SAP system, first stop the dialog instance and then the
central instance.
2005/Q2
© 2005 SAP AG. All rights reserved.
61
Unit 2: Starting and Stopping the SAP System
ADM100
Lesson Summary
You should now be able to:
•
Stop the entire SAP System or individual instances
62
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Starting and Stopping Under Other Operating Systems
Lesson: Appendix: Starting and Stopping Under Other
Operating Systems
Lesson Overview
In this lesson, you receive information about starting and stopping an SAP system
under different operating systems.
Lesson Objectives
After completing this lesson, you will be able to:
•
Describe the starting and stopping of an SAP system under different operating
systems
Business Example
As a system administrator, you need to be able to start and stop the SAP system.
UNIX
Figure 20: UNIX: Starting
Log on in UNIX as a user with SAP administrator authorization (<sid>adm).
2005/Q2
© 2005 SAP AG. All rights reserved.
63
Unit 2: Starting and Stopping the SAP System
ADM100
To start the central instance, call the shell script startsap_<host>_<instance
no> in the home directory of the <sid>adm user. If there is only one
instance for each application server, the alias startsap points to the script
startsap_<host>_<instance no>.
The script startsap first starts the saposcol process which collects statistical data
for the operating system that it provides to the SAP system.
The next step is a check to see if the database is running. If not, the script startdb
is called to start the database.
The final step starts all of the processes for the instance (message server, dispatcher,
work processes, and so on).
After the central instance is started, you can optionally start other instances.
The startsap script can be called with the following options:
DB: starts the database system
R3: starts the instances and associated processes for the instance
ALL: starts the database system and the instance (default setting, can be omitted)
To start the SAP system, the startsap script calls the sapstart process with the
start profile specified in the script in the variable START_FILES.
Figure 21: UNIX: Stopping
64
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Starting and Stopping Under Other Operating Systems
When you stop the SAP system, you should first stop all dialog instances and then
stop the central instance. You have two options for doing this:
From the SAP system using the CCMS Control Panel.
Log on under UNIX as the SAP administrator (<sid>adm) at operating system level
and enter the command stopsap from your home directory.
The stopsap script can be called with the following options:
•
•
•
DB: stops the database system with the help of the stopdb script
R3: stops the instances of the SAP system
ALL: stops the database system and the instance (default setting, can be omitted)
The database can be stopped separately with database tools.
OS/400
Note: The following section refers to AS/400. However, the statements apply
equally to iSeries hosts.
Figure 22: OS/400: Starting
Logon on to the AS/400 system with the SAP user profile for administrators. The
authorizations of the group profile <SID>OPRGRP are required for this user (such as
user profile <SID>OFR or <SID>OPR ).
2005/Q2
© 2005 SAP AG. All rights reserved.
65
Unit 2: Starting and Stopping the SAP System
ADM100
Enter the AS/400 command STARTSAP and request parameters with F4.
Under SAP System ID, enter the name of your system (such as DEV).
Under R/3 Instance, enter the instance number (such as 00). To start all instances on
one or more hosts, choose *ALL.
Under R/3 Instance Host Name, enter the name of the host on which the instance is
to be started. To start all instances on all hosts, choose *ALL. (You must also have
selected *ALL under R/3 Instance.)
Confirm your entries with ENTER. The subsystem R3_nn is then started for each
started instance (<nn> is the instance number). All associated SAP services are started
together with the subsystem (such as dispatcher, work processes, spool processes).
Enter the AS/400 command WRKACTJOB SBS(R3_<nn>) to check whether the
SAP system(s) were started correctly.
The system displays a screen with the column Status at the right-hand side. If an SAP
system was started correctly, the first line of this column should contain the value
RUN (running), SELW (waiting), or DEQW (waiting for completion of unlocking). It
can take a few minutes for the file system to reach this status.
Figure 23: OS/400: Stopping
Logon on to the AS/400 system with the SAP user profile for administrators
(<SID>OFR or <SID>OPR).
66
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Starting and Stopping Under Other Operating Systems
Enter the AS/400 command STOPSAP and request parameters with F4.
Under SAP System ID, enter the name of the SAP system that you want to stop.
Under R/3 Instance, enter the number of the instance that you want to stop, such as 90.
To stop all instances on one or more hosts, choose *ALL.
Under R/3 Instance Host Name enter *LOCAL to stop one or more instances on the
local host. To stop all instances on all hosts, choose *ALL. (You must also have
chosen *ALL under R/3 Instance.)
If you enter *YES under Wait for instance to end, the command STOPSAP waits
until the SAP instance is shut down before stopping the SAP system. (The instance
is regarded as shut down if the number of active instance user jobs in the instance
subsystem, other than the SAPOSCOL job, is zero.)
Under Maximum wait time (seconds), you can enter the maximum time that the
command should wait for the instance to be shut down. The default value is 120
(two minutes). If it takes longer than two minutes for the instance to be shut down,
an exception message is sent.
Confirm your entries with ENTER.
OS/390
Note: The following section refers to S/390. However, the statements apply
equally to zSeries hosts.
2005/Q2
© 2005 SAP AG. All rights reserved.
67
Unit 2: Starting and Stopping the SAP System
ADM100
Figure 24: OS/390: Starting
In an OS/390 environment, an S/390 system serves as a database server. You can use
Microsoft Windows or UNIX systems as application servers.
You must first start processes that allow the SAP work processes to connect to the
database.
Start the DB2 database on the OS/390 system with the appropriate operating system
commands.
Start the Recoverable Resource Manager (RRS) to synchronize all resources supported
by OS/390.
Instances on non-OS/390 systems require the ICLI servers to allow communication
with the database. To allow this, start the ICLI server(s) on the OS/390 system. Use
either the OS/390 JCL operating language or a script which uses the OS/390 UNIX
system services.
To start the SAP system, log on as operating system user <sid>adm on the UNIX or
Microsoft Windows application server.
First, start the central instance. To do this, call the sartsap script under UNIX or
use the Microsoft Management Console under Microsoft Windows. If the saposcol
process has not yet been started, this is started first. The processes of the central
instances are then started.
The work processes then connect to the database.
68
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Starting and Stopping Under Other Operating Systems
Other instances can then optionally be started
Figure 25: OS/390: Stopping
You can stop the SAP system using either the CCMS Control Panel or operating
system resources. At operating system level, under UNIX, run the command
stopsap r3, or use the Microsoft Management Console under Microsoft Windows.
The ICLI servers and the DB2 database are stopped on the S/390 system.
Stop the ICLI servers either on the OS/390 system console with the command
MODIFY BPXINIT, TERM=<PID> or by using the OS/390 UNIX system services
with the command kill <PID>.
Check that the ICLI servers have been stopped.
Stop the database.
2005/Q2
© 2005 SAP AG. All rights reserved.
69
Unit 2: Starting and Stopping the SAP System
ADM100
Lesson Summary
You should now be able to:
•
Describe the starting and stopping of an SAP system under different operating
systems
70
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix - Database Logs
Lesson: Appendix - Database Logs
Lesson Overview
This lesson provides information about the log files of various databases.
Lesson Objectives
After completing this lesson, you will be able to:
•
Describe the locations of the log files for various databases
Business Example
If an error occurs, the system administrator needs to access the database log files to
find the cause of the error.
SAP DB / MaxDB
Note: The following statements apply in the same way for MaxDB-based
SAP systems.
Figure 26: SAP DB
SAP DB logs system messages and error messages in the directory:
<Laufwerk>:\sapdb\data\wrk\<SID>.
2005/Q2
© 2005 SAP AG. All rights reserved.
71
Unit 2: Starting and Stopping the SAP System
ADM100
The system messages are recorded in the kernel log knldiag. This contains the
following messages in chronological order:
•
•
•
•
Database start and stop
Information about the physical storage areas
User processes
System error messages
The log is run as a circular memory file that is overwritten as soon as it reaches
a certain size. A new log file is created after every start of the database system.
A backup copy of the old log (knldiag.old) is created before a restart of the
database system.
All error and warning messages concerning the database system are recorded in the
error log (knldiag.err), including the messages for the system start and stop.
MS SQL Server
Figure 27: MS SQL Server
The MS SQL Server logs all significant events such as starting and stopping the database and error messages in the file <Laufwerk>:...\MSSQL\LOG\ERRORLOG.
A new error log file is written at every start of the MS SQL server. Multiple versions
of these error log files are stored as ERRORLOG.1, ERRORLOG.2, and so on. The
oldest available version is stored as ERRORLOG.6. At every restart of the SQL server,
the oldest file is overwritten. If a serious database problem occurs, you should backup
the oldest file before the restart, so that this information is not lost.
72
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix - Database Logs
These error log files can be displayed in the Enterprise Manager.
Messages of the “SQLServerAgent” service that is required for backups are also
logged in the above directory in the file SQLAGENT.OUT. The last six versions of
this log are also retained.
Oracle
Figure 28: Oracle
The Oracle database logs all significant events such as starting and stopping the database and error messages in the file
<Laufwerk>:\oracle\<SID>\saptrace\background\ALRT.LOG.
Detailed information about errors is logged in the Oracle Trace File:
<Laufwerk>:\oracle\<SID>\saptrace\usertrace\Ora<no>.trc.
If the system administrator administers the database with sapdba, this writes its own
log files in the following directories:
<Laufwerk>:\oracle\<SID>\sapreorg
<Laufwerk>:\oracle\<SID>\sapcheck
<Laufwerk>:\oracle\<SID>\sapbackup
2005/Q2
© 2005 SAP AG. All rights reserved.
73
Unit 2: Starting and Stopping the SAP System
ADM100
DB2 (UDB)
Figure 29: DB2 (UDB)
The DB2 database logs all significant events in the file db2diag.log. The path
under which this file is stored is define with the parameter Diagnostic Directory Data
Path (DIAGPATH). This path is configured in the database manager configuration.
The default value is $DB2INSPROF/DB2INSTANCE.
The db2diag.log file contains the following information:
•
•
•
The place at which the reported error occurred. Application IDs allow the
comparison of entries that belong to one application in the file db2diag.log.
A diagnostic message with the reason for the error. The message usually begins
with “DIA”.
All other available data such as SQLCA data structures and pointers to other
dump or trap files.
Detailed information about errors is logged in the DB2 trace or dump files, which are
also stored in the path defined using parameter DIAGPATH. These files are only
created if a serious internal DB2 error occurs.
You can access the dump directory by calling transaction DB6COCKPIT and choosing
Diagnostics → Dump Directory in the navigation box.
If you want to display the contents of an error log or a trace file, double click the file.
74
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix - Database Logs
Informix
Figure 30: Informix
All significant events, such as starting and stopping the database and
error messages are logged by the INFORMIX database in the file
$INFORMIXDIR/online.<hostname>.<SID>.log.
Detailed information for individual errors is logged in the trace file af.<unique
no>. In certain cases, the content of the shared memory is copied to the files
shmem.<unique no>. The directory in which these files are stored is defined
using the parameter DUMPDIR. The default value of this parameter is /tmp.
2005/Q2
© 2005 SAP AG. All rights reserved.
75
Unit 2: Starting and Stopping the SAP System
ADM100
DB2 (OS/390)
Figure 31: DB2 (OS/390)
ICLI Server Message Reporting:
ICLI Server Messages for one or more ICLI servers are written to one or more ICLI
error log files. The file names follow the naming convention ICLI.<pid>.msg<n>,
where <pid> is the process ID of the ICLI server and <n> identifies multiple error log
files of an ICLI server.
The error log files of the ICLI are either stored in a directory that is specified during
the start of the ICLI servers using the option -LOGDIR, or in the home directory of
the user under which they were started.
ICLI Client Message Reporting:
The ICLI servers also send messages to the communication partners of the client.
These are logged in the developer traces and in the system log of the SAP system.
The DB2 database logs all significant events and errors in the OS/390 system log.
76
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix - Database Logs
Lesson Summary
You should now be able to:
•
Describe the locations of the log files for various databases
2005/Q2
© 2005 SAP AG. All rights reserved.
77
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Describe the process of the start procedure of an SAP system
•
Start the entire SAP system or individual instances
•
Evaluate start logs to analyze problems
•
Stop the entire SAP System or individual instances
•
Describe the starting and stopping of an SAP system under different operating
systems
•
Describe the locations of the log files for various databases
78
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
Which SAP processes are started when the SAP system or an instance is started?
Choose the correct answer(s).
□
□
□
□
□
2.
A
B
C
D
E
SAPOSCOL
START_SAP_NOW
Message Server
Gateway Server
LAUNCH_DB
Log information for the dispatcher is stored in the file
.
You can control the granularity of the logged information using the profile
parameter
. There are
trace levels; error
.
messages and warnings are displayed, by default, at level
Fill in the blanks to complete the sentence.
3.
You can display the users logged on to the SAP system with transactions
(for each instance) and
(system-wide). You can obtain
an overview of the scheduled background jobs with transaction
.
to send a system message to the users
You can use transaction
that are logged on.
Fill in the blanks to complete the sentence.
2005/Q2
© 2005 SAP AG. All rights reserved.
79
Test Your Knowledge
ADM100
Answers
1.
Which SAP processes are started when the SAP system or an instance is started?
Answer: A, C, D
SAPOSCOL is an underlying process that should always be running, even if the
SAP system is shut down. START_SAP_NOW and LAUNCH_DB are made
up. The message server is started once for each SAP system, and the gateway
server is started once for each instance.
2.
Log information for the dispatcher is stored in the file dev_disp. You can
control the granularity of the logged information using the profile parameter
rdisp/TRACE. There are four trace levels; error messages and warnings are
displayed, by default, at level 1.
Answer: dev_disp, rdisp/TRACE, four, 1
3.
You can display the users logged on to the SAP system with transactions SM04
(for each instance) and AL08 (system-wide). You can obtain an overview of the
scheduled background jobs with transaction SM37. You can use transaction
SM02 to send a system message to the users that are logged on.
Answer: SM04, AL08, SM37, SM02
Transaction SM04 is instance-specific, transaction AL08, on the other hand, is
cross-instance. In transaction SM37, you can select by client and user, among
other things. In transaction SM02, you can restrict the sending of the message
to instances or clients.
80
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 3
Introduction to System Configuration
Unit Overview
In this unit, you will learn how you can use profile parameters to configure your
SAP system.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
Determine the configuration of system parameters
Adjust the system parameters using profiles
Set up a dynamic switch of work process types using operation modes
Unit Contents
Lesson: How the System Evaluates its Parameters ............................ 82
Exercise 5: Configuring the System Parameters............................ 87
Lesson: How to Set System Parameters ......................................... 90
Exercise 6: Maintaining the System Parameters............................ 95
Lesson: Setting up Operation Modes ............................................ 101
Exercise 7: Setting up Operation Modes .................................... 109
2005/Q2
© 2005 SAP AG. All rights reserved.
81
Unit 3: Introduction to System Configuration
ADM100
Lesson: How the System Evaluates its Parameters
Lesson Overview
This lesson explains the order in which the system evaluates profile parameters and
where these parameters are stored.
Lesson Objectives
After completing this lesson, you will be able to:
•
Determine the configuration of system parameters
Business Example
You want to determine the system parameters for your SAP system.
Configuring the System Parameters
The configuration of the individual instances, and therefore of the SAP system, is
performed using system parameters. The default values for these parameters are
defined in the program code of the kernel.
Figure 32: Assigning System Parameters
82
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How the System Evaluates its Parameters
You can change these default values using the profile files, which are read when an
instance is started. These profile files that are created during the installation of the
system, can also be edited later.
As the profile files are only read when the system is started, you must restart the
instance or the entire system after changing parameters.
Dynamic switching, that is, while the system is running, is only possible for a small
number of system parameters.
Figure 33: Profile Files at Operating System Level
The profile files are automatically created during installation. After installation
is complete, the profile files are stored at operating system level in the directory:
\usr\sap\<SID>\SYS\profile. This directory can be read by all instances of an SAP
system using the share or mount technique.
The SAP system has three system profiles. These are:
•
•
•
Start profile
Default profile
Instance profile
In principle, you can change these files with operating system resources (editors). In
doing so, the user must ensure that the changes are performed correctly. Incorrectly
set parameters can lead to the system not starting. It is far more convenient and safer
to change the profile parameters using the resources in the SAP system.
2005/Q2
© 2005 SAP AG. All rights reserved.
83
Unit 3: Introduction to System Configuration
ADM100
Figure 34: Profile Files: Overview
The instance-specific start profile (START<instance><instance number>_<host
name>), specifies for each instance which processes are to be started. These are, for
example, the message server and the dispatcher.
There is only one default profile (DEFAULT.PFL) for each SAP system, and it is read
by all instances. It contains system-wide settings, such as the system name, the name
of the database server, the name of the enqueue server, or also the default logon client.
The instance profile (<SID>_<instance><instance number>_<host name>) defines
parameters that apply for one instance, such as the number and type of work processes,
or the definition of the size and allocation of the main memory area used by the SAP
system. The instance profile is therefore instance-specific.
84
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How the System Evaluates its Parameters
Figure 35: Viewing System Parameters
The system can display the current values of the system parameters. There are two
ways to do this. These are: report RSPFPAR and transaction RZ11. Both functions
display the system parameters for the instance to which the user is currently logged
on. Report RSPFPAR displays a list of all instance-specific system parameters, along
with the parameters that apply system-wide. You can restrict this list to specific
parameters. A table displays the system default value for the individual parameters
as it is defined in the program code of the kernel, and, if the default value has been
overridden by a profile parameter, the user-defined value. A short description and,
if required, documentation for the parameters can also be displayed. Transaction
RZ11 displays information and documentation for individual profile parameters. It
also shows, with the Dynamically Switchable indicator, whether the parameter can
be changed while the system is running.
Note: In the TPFYPROPTY table, all dynamically switchable profile
parameters are identified by the Dynamic indicator. You can use transaction
SE16, for example, to display this table.
Outside the SAP system, you can display the values of the profile parameters at
operating system level using the user <sid>adm with the program sappfpar.
You can display the current value of a parameter with sappfpar <parameter
name>. The command sappfpar all returns a list of all parameters. You
can check the parameters that are set using sappfpar check. The command
sappfpar help returns a short overview of possible options.
2005/Q2
© 2005 SAP AG. All rights reserved.
85
Unit 3: Introduction to System Configuration
ADM100
You can also specify an instance profile, an instance number, or the SAP system
name with this command using the options pf=<instance profile>,
nr=<instance number>, or name=<SID>.
Hint: Note that, for the evaluation of profile parameters using the tools
described above, some profile parameters are the same system-wide, while
others can be set differently for each instance. The report RSPFPAR displays
the configuration of the instance on which you run the report.
86
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How the System Evaluates its Parameters
Exercise 5: Configuring the System
Parameters
Exercise Objectives
After completing this exercise, you will be able to:
•
Determine the configuration of system parameters
Business Example
You want to determine the system parameters for your SAP system.
Task: Determine Values of System Parameters
Determine the values of a number of system parameters.
1.
Determine the values of the following system parameters:
Name of the application server, number of work processes on the central instance
(dialog, background, enqueue, update, spool), maximum number of sessions
permitted per logon
2005/Q2
© 2005 SAP AG. All rights reserved.
87
Unit 3: Introduction to System Configuration
ADM100
Solution 5: Configuring the System
Parameters
Task: Determine Values of System Parameters
Determine the values of a number of system parameters.
1.
Determine the values of the following system parameters:
Name of the application server, number of work processes on the central instance
(dialog, background, enqueue, update, spool), maximum number of sessions
permitted per logon
a)
You can determine the values of system parameters by running the report
RSPFPAR. The parameter names are as follows:
Name of the local application server: rdisp/myname.
Number of work processes on the central instance:
Dialog:
rdisp/wp_no_dia
Background:
rdisp/wp_no_btc
Enqueue:
rdisp/wp_no_enq
Update:
rdisp/wp_no_vb
Spool:
rdisp/wp_no_spo
Maximum number of sessions permitted per logon: rdisp/max_alt_modes.
88
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How the System Evaluates its Parameters
Lesson Summary
You should now be able to:
•
Determine the configuration of system parameters
2005/Q2
© 2005 SAP AG. All rights reserved.
89
Unit 3: Introduction to System Configuration
ADM100
Lesson: How to Set System Parameters
Lesson Overview
In this lesson, you will learn how you can change the values of system parameters.
Lesson Objectives
After completing this lesson, you will be able to:
•
Adjust the system parameters using profiles
Business Example
As an administrator, you are to adjust the configuration of the system parameters.
Administering and Maintaining Profiles
If you want to change profile parameters, you can make these changes using operating
system-specific editors. However, this procedure has certain dangers, as the user must
ensure that the changes are performed, and also documented, correctly. Incorrectly
set parameters can prevent an instance starting. The SAP system therefore provides
integrated profile administration and parameter maintenance.
Figure 36: Profile Administration
Profile administration in the SAP system offers a number of advantages to the user.
90
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How to Set System Parameters
Advantages of Profile Administration in the SAP System
•
•
•
•
•
Central administration and maintenance of the instances
Changes in profiles checked for consistency
Administration of multiple versions of a profile
Comparison of the actively used profile and the profile stored in the database
Immediate activation of selected parameters
Figure 37: Profile Maintenance 1/2
After installation, the profile parameters are, at first, only present at operating system
level. To use the profile administration of the SAP system, the profiles must be
imported into the database. During this import, the system performs a consistency
check and a check of the way in which the parameters interact. Changes to profile
parameters can then be performed in the SAP system, with the previously mentioned
advantages. These changes are then stored in the database, and written back to file
level. The changes only take effect when they are read by the system; that is, at
a restart of the system.
You perform the administration and maintenance of profiles in transaction RZ10.
In the first step, you import the profiles into the database by choosing Utilities →
Import Profiles → Of active servers. After selecting the profile to edit, you can
change individual profile parameters. There are three different levels for maintaining
2005/Q2
© 2005 SAP AG. All rights reserved.
91
Unit 3: Introduction to System Configuration
ADM100
the profiles. The administration data contains the type of profile (start, default, or
instance profile), a short description, the path of the file, the name of the instance, and
the time of the last activation.
You can perform the maintenance of the parameters of the individual profiles through
either basic maintenance or extended maintenance. Basic maintenance allows
you to adjust the most important parameters and supports the user through the use
of logical descriptions. Extended maintenance displays the unformatted content
of the profile; that is, the technical names of the profile parameters. In extended
maintenance, you can not only change the values of individual parameters, but also
add new parameters and delete existing parameters.
The changes are stored in two steps. In the first step, the changes are temporarily
copied when you choose Copy. The values are permanently saved to the database in a
second step when you choose Save. The changes are therefore successfully saved to
the database and must now be written at operating system level. This is done either
automatically during saving by confirming the relevant query, or manually from the
menu by choosing Profile → Activate.
Figure 38: Profile Maintenance 2/2
Changes to instance-specific profiles take effect after a restart of the corresponding
instance. Changes to the default profile take effect only after a restart of all instances
in the entire system.
Changes to these files are, however, the exception rather than the rule.
92
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How to Set System Parameters
Consistency Check
Additional functions available in transaction RZ10 are the consistency check and the
comparison of profiles.
Figure 39: Profile Consistency Checks
During a consistency check, the system checks the syntax and the semantics for
individual or for all profiles.
The all profiles option also contains a consistency check between the profiles of a
type. This means that, for example, the system checks for the start profile whether
only one message server is being started for each system.
During the comparison of profiles, the system compares the profile that is in active use
with the profile stored in the database. This comparison is automatically performed
when an instance is started. If the system identifies a difference between the active
profile and the profile stored in the database, the system displays a message in the
Alert Monitor.
2005/Q2
© 2005 SAP AG. All rights reserved.
93
Unit 3: Introduction to System Configuration
ADM100
94
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: How to Set System Parameters
Exercise 6: Maintaining the System
Parameters
Exercise Objectives
After completing this exercise, you will be able to:
•
Adjust the system parameters using profiles
Business Example
As an administrator, you are to adjust the configuration of the system parameters.
Task 1: Save Profile Files
First back up the profile files.
1.
Save your runnable profile files in a backup directory. To do this, create a
Backup<SID> directory under C:\Temp and copy all profile files to this
directory. Replace <SID> with the system ID of your SAP system.
Task 2: Import and Maintain Profiles
Use transaction RZ10 (Tools → CCMS → Configuration → System Profile) to
perform the following tasks.
1.
Import all profiles into your SAP system.
2.
Change the values of the following parameters:
i) Increase the number of dialog work processes for the dialog instance by 2.
ii) Set the value for the maximum number of permitted sessions to 7. To do this,
you need to add a new parameter to a system profile.
Consider in what profiles you are performing changes.
Save and activate your changes.
3.
Check the number of work processes in the process overview and the maximum
number of SAP GUI sessions that can be opened.
4.
i) Check your changes in the profile files at operating system level.
ii) What must you still do, to have your changes take effect in the system?
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
95
Unit 3: Introduction to System Configuration
ADM100
Task 3: Activating the Changed Profile Parameters
Check the changed system parameters after a system restart.
96
1.
Restart the system so that your changes become active.
2.
Check your changes in the system again.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How to Set System Parameters
Solution 6: Maintaining the System
Parameters
Task 1: Save Profile Files
First back up the profile files.
1.
Save your runnable profile files in a backup directory. To do this, create a
Backup<SID> directory under C:\Temp and copy all profile files to this
directory. Replace <SID> with the system ID of your SAP system.
a)
Log on to your server. Copy the profile files from the directory
\usr\sap\<SID>\SYS\profile to the Backup<SID> directory.
Task 2: Import and Maintain Profiles
Use transaction RZ10 (Tools → CCMS → Configuration → System Profile) to
perform the following tasks.
1.
Import all profiles into your SAP system.
a)
2.
All profile files can be imported together by choosing: Utilities → Import
Profiles → Of active servers. A check log displays the result of the import.
Change the values of the following parameters:
i) Increase the number of dialog work processes for the dialog instance by 2.
ii) Set the value for the maximum number of permitted sessions to 7. To do this,
you need to add a new parameter to a system profile.
Consider in what profiles you are performing changes.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
97
Unit 3: Introduction to System Configuration
ADM100
Save and activate your changes.
a)
To change the values of individual parameters, select the corresponding
profile (default or instance profile) and change this in Extended
Maintenance.
If no Change button displays, choose Display <-> Change to switch to
change mode. Select the desired parameter and choose Change.
After making your changes, choose Copy and then Save. Then, in the list
view, choose Copy and then Back. Save the new version of the profile and
confirm the activation of the profile in the dialog box.
To create a new parameter, choose Create under Extended Maintenance.
The required parameters are listed:
•
•
rdisp/wp_no_dia (instance profile)
rdisp/max_alt_modes (default profile)
Confirm the warning when creating the parameter rdisp/max_alt_modes
with the value 7 by choosing Yes.
Hint: The warning displays because the properties for this
parameter include the setting Change generates warning (you can
check this using transaction RZ11).
3.
4.
Check the number of work processes in the process overview and the maximum
number of SAP GUI sessions that can be opened.
a)
Check the number of processes by calling the server overview (Tools →
Administration → Monitor → System Monitoring→ Servers, transaction
SM51), selecting the dialog instance, and then choosing Processes.
b)
Check the maximum number of SAP GUI sessions that can be opened by
displaying the parameter with transaction RZ11. In the Parameter Name
field, enter rdisp/max_alt_modes and choose the Display button.
The Current Value field should still display the previous value 6.
i) Check your changes in the profile files at operating system level.
Continued on next page
98
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: How to Set System Parameters
ii) What must you still do, to have your changes take effect in the system?
a)
Open the profile files at operating system level with an editor and use this
to view the changes that have been made.
b)
Your changes to profile parameters will only take effect after a restart of
the affected instance or the entire system.
Task 3: Activating the Changed Profile Parameters
Check the changed system parameters after a system restart.
1.
Restart the system so that your changes become active.
a)
2.
2005/Q2
Log on to your server in the same way as you did in the exercises for the
Starting and Stopping unit, and then restart the system.
Check your changes in the system again.
a)
Check the number of processes by calling the server overview (Tools →
Administration → Monitor → System Monitoring→ Servers, transaction
SM51), selecting the dialog instance, and then choosing Processes.
b)
Check the maximum number of SAP GUI sessions that can be opened by
displaying the parameter with transaction RZ11. In the Parameter Name
field, enter rdisp/max_alt_modes and choose the Display button.
The Current Value field should now display the value that you entered, 7.
© 2005 SAP AG. All rights reserved.
99
Unit 3: Introduction to System Configuration
ADM100
Lesson Summary
You should now be able to:
•
Adjust the system parameters using profiles
100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting up Operation Modes
Lesson: Setting up Operation Modes
Lesson Overview
In this lesson, you will learn about the concept of operation modes. You will learn
how to set up a dynamic switch of work process types using operation modes.
Lesson Objectives
After completing this lesson, you will be able to:
•
Set up a dynamic switch of work process types using operation modes
Business Example
The configuration of the work processes using the profiles usually meets the
requirements for day operation. The administrator can use operation modes to
optimize the performance of the system for the different requirements during the
day and during the night.
Concept of Operation Modes
The demands of users on the SAP system vary during the course of the day. During
the day, a large number of dialog users, who want to be served with high performance
by the system, are working. Therefore, a large number of dialog work processes
should be available for users during the day. During the night, however, only a small
number of these dialog work processes are used, and the system can be used to a
larger extent to process background jobs.
2005/Q2
© 2005 SAP AG. All rights reserved.
101
Unit 3: Introduction to System Configuration
ADM100
Figure 40: Concept of Operation Modes
The type and number of work processes for each instance is defined in the profiles.
The distribution of work processes in the profiles is optimized for fast dialog response
times; that is, there are usually lots of dialog work processes and a small number of
background work processes. This means that during the night, system resources, such
as the main memory, are tied to the dialog work processes, or are not fully utilized by
the background processes, such as the CPU. It is therefore practical to define different
types and numbers of work processes for these different demands on the SAP system.
This is realized through the concept of operation modes.
102
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting up Operation Modes
Figure 41: Adjusting Instances to the Load Distribution
Using the operation modes, you can adjust the type and distribution of the work
processes to the varying load distribution during the day. You can also adjust the
distribution of the work processes to business requirements that only occur once.
By defining operation modes, you can change not only the total number of work
processes defined in the profiles, but also the type and distribution of the individual
work process types within this total number. The switch between the work process
types is performed dynamically during the runtime of the SAP system. The switch
is triggered using a defined schedule. A reserved work process is not immediately
terminated, but marked for switching. This means that certain delays may occur. This
type change is logged in the system log.
During the switch of the operation modes, neither the instance nor the affected work
processes needs to be restarted. This means that the quality of the buffer of the
SAP system is retained during an operation mode switch, and that the request that
is currently being processed by a work process is completed. The individual work
processes retain their process ID after the switch. You can observe this in the process
overview (SM50).
Setting Up Operation Modes
The operation modes are set up in a number of steps.
2005/Q2
© 2005 SAP AG. All rights reserved.
103
Unit 3: Introduction to System Configuration
ADM100
Steps to Configure Operation Modes
•
•
•
•
First, the operation modes are created as empty containers in transaction RZ04.
Next, all active instances of the system are recorded and the work processes
defined in the instance profile are assigned to the operation modes as default
values.
You can now make allocations for the individual operation modes in the total
number of work processes taken from the instance profile. The allocation should
be made primarily between the dialog and background work processes.
You then specify the periods for which the operation modes are valid and when
the switch between the operation modes should occur in the time table (SM63).
Figure 42: Setting Up Operation Modes
You cannot arbitrarily change the work process distribution.
104
Work Process
Type
Type of Changeability (+ = increase number, - = reduce
number)
Dialog
only indirectly changeable
Background
+: possible, reduces the number of D-WP correspondingly
-: possible, increases the number of D-WP correspondingly
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting up Operation Modes
Class A
specifies the subset of the B-WP that only process
class A background jobs
Update
+: possible, if at least 1 UPD-WP exists,
reduces the number of D-WP correspondingly
-: possible, if at least 1 UPD-WP remains,
increases the number of D-WP correspondingly
V2 Update
+: possible, if at least 1 UPD2-WP exists,
reduces the number of D-WP correspondingly
-: possible, if at least 1 UPD2-WP remains,
increases the number of D-WP correspondingly
Enqueue
+: possible, if at least 1 E-WP exists,
reduces the number of D-WP correspondingly
-: possible, if at least 1 E-WP remains,
increases the number of D-WP correspondingly
You should only increase the number of E-WP if SAP
support advises you to do so.
Spool
cannot be changed
Note: Note: A change to the allocation should be made primarily between the
dialog and background work processes.
The time table (SM63) differentiates between normal operation and exception
operation. A general time definition that applies almost all of the time is set using
normal operation. In rare cases, in which a special distribution of the work processes
for unusual system loads is required, they are defined using exception operation.
2005/Q2
© 2005 SAP AG. All rights reserved.
105
Unit 3: Introduction to System Configuration
ADM100
Figure 43: Scheduling Operation Modes
If you do not define a timetable for normal operation, no switch of operation modes is
made. The configuration in the instance profile remains active.
The exception operation can only be defined as a unique event.
You can trigger an operation mode switch from a program that you have written using
a function module (RZL_PERFORM_BA_SWITCH).
Monitoring and Consistency Check
The Control Panel (RZ03) allows you to monitor the instances and the operation
modes and provides functions to:
•
•
•
•
•
106
Check the status of all instances and of the operation modes
Start and stop the instances
Manually switch operation mode
Display an overview of the work processes
Switch to the Alert Monitor
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting up Operation Modes
Figure 44: Control Panel
You can switch the operation mode either for all instances (Control → Switch
operation mode → All servers) or for a selected instance (Control → Switch operation
mode → Selected servers).
You can first simulate the switch of operation modes (Control → Switch operation
mode → Simulation); that is, the system checks which instances can be switched.
You can display a detailed analysis of the status of the individual instances by
choosing Monitoring → Status Details.
If it is not possible to switch between operation modes, this is usually due to
inconsistencies in the SAP system. These inconsistencies can occur if the number of
work processes is defined differently in different places in the system. These are the
instance profiles at operating system level, the instance profile in the database, and the
definition of the operation modes themselves.
2005/Q2
© 2005 SAP AG. All rights reserved.
107
Unit 3: Introduction to System Configuration
ADM100
Figure 45: Profile Consistency Checks
If, for example, the number of work processes in the profiles is changed, the system
can no longer switch operation modes until after a restart of the instance. It is therefore
necessary to adjust the configuration of the operation modes after a change to the
profiles.
108
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting up Operation Modes
Exercise 7: Setting up Operation Modes
Exercise Objectives
After completing this exercise, you will be able to:
•
Set up a dynamic switch of work process types using operation modes
Business Example
The configuration of the work processes using the profiles usually meets the
requirements for day operation. The administrator can use operation modes to
optimize the performance of the system for the different requirements during the
day and during the night.
Task 1: Create Operation Modes
Create operation modes using transaction RZ04 to perform the following steps.
1.
Create two operation modes, Day and Night.
2.
Now create a definition for the work process distribution for all instances of
your system.
3.
Change the distribution of the work processes of your instances for each of
the operation modes.
Note that there should be at least two dialog and two background work processes
in all operation modes.
Task 2: Schedule Operation Modes
Schedule the operation modes that you have created.
1.
In the timetable, schedule the operation modes that you have created for normal
operation.
Task 3: Manual Switch of Operation Modes
2005/Q2
1.
To observe the change in work process distribution when the operation mode is
switched, switch to the Night operation mode manually in the Control Panel.
2.
How can you observe the change of the work process distribution?
© 2005 SAP AG. All rights reserved.
109
Unit 3: Introduction to System Configuration
ADM100
Solution 7: Setting up Operation Modes
Task 1: Create Operation Modes
Create operation modes using transaction RZ04 to perform the following steps.
1.
Create two operation modes, Day and Night.
a)
You maintain operation modes in transaction RZ04 (Tools → CCMS →
Configuration → Operation Modes/Instances).
You can create operation modes by choosing Create operation mode. Enter
the name of the operation mode and a short description and choose Save.
2.
Now create a definition for the work process distribution for all instances of
your system.
a)
Switch to the Instances/Operation Modes view by choosing
Instances/Operation Modes.
You define work process distribution for all instances of your system by
choosing Settings → Based on current status → New instances → Create.
Choose Save.
3.
Change the distribution of the work processes of your instances for each of
the operation modes.
Note that there should be at least two dialog and two background work processes
in all operation modes.
a)
To change the distribution of the work processes for the operation modes
of the instances, select the operation modes entries. You change and then
save the distribution of the work processes in the dialog box: CCMS:
Work Process Distribution.
To do this, place the cursor in the column of the work process type that
you want to change. You can change the number by choosing + and -.
Then choose Save.
After you have changed the distribution for all operation modes and
instances, choose Save.
Continued on next page
110
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting up Operation Modes
Task 2: Schedule Operation Modes
Schedule the operation modes that you have created.
1.
In the timetable, schedule the operation modes that you have created for normal
operation.
a)
You can schedule operation modes using the operation mode calendar
(Tools → CCMS → Configuration → Operation Mode Calendar,
transaction SM63).
Select Normal Operation and then choose Change.
Select the start and end of the period for operation mode Day. Choose the
Assign button and use the F4 help to select the operation mode Day. Follow
the same procedure to assign the operation mode Night. After you have
assigned the entire 24-hour period to your operation modes, choose Save.
Task 3: Manual Switch of Operation Modes
1.
To observe the change in work process distribution when the operation mode is
switched, switch to the Night operation mode manually in the Control Panel.
a)
You can perform a manual switch of the operation modes in the Control
Panel (Tools → CCMS → Control/Monitoring → Control Panel,
transaction RZ03).
As a first step, select the operation mode where you want to switch, by
choosing Choose operation mode. Select the operation mode and then
Choose.
The switch is performed in a second step, by choosing Control → Switch
Operation Mode → All Servers.
2.
How can you observe the change of the work process distribution?
a)
2005/Q2
Check the changed distribution of the work processes in the process
overview (Tools → Administration → Monitor → System Monitoring →
Process Overview, transaction SM50).
© 2005 SAP AG. All rights reserved.
111
Unit 3: Introduction to System Configuration
ADM100
Lesson Summary
You should now be able to:
•
Set up a dynamic switch of work process types using operation modes
112
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
Determine the configuration of system parameters
•
Adjust the system parameters using profiles
•
Set up a dynamic switch of work process types using operation modes
2005/Q2
© 2005 SAP AG. All rights reserved.
113
Unit Summary
114
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
In what sequence does the system read the system parameters the specified
locations?
Choose the correct answer(s).
□
□
□
□
2.
A
B
C
D
1.
1.
1.
1.
Instance profile 2. Default profile 3. Kernel
start.ini 2. Kernel 2. Default profile 4. Instance profile
Kernel 2. Default profile 3. Instance profile
Kernel 2. start.ini 3. Default profile 4. Instance profile
In what profile can you change the number of background work processes?
Choose the correct answer(s).
□
□
□
□
3.
A
B
C
D
Start profile
Default profile
Background profile
Instance profile
You can use transaction
profiles.
to check the consistency of individual
Fill in the blanks to complete the sentence.
4.
In what sequence should you perform the listed steps when setting up operation
modes?
Choose the correct answer(s).
2005/Q2
□
A
□
B
□
C
1. Create operation modes 2. Assign instances 3. Distribute work
processes 4. Maintain time table
1. Create operation modes 2. Maintain time table 3. Distribute work
processes 4. Assign instances
1. Create operation modes 2. Distribute work processes 3. Maintain
time table 4. Assign instances
© 2005 SAP AG. All rights reserved.
115
Test Your Knowledge
ADM100
Answers
1.
In what sequence does the system read the system parameters the specified
locations?
Answer: C
There is no file called start.ini involved in this context; it has been made up.
2.
In what profile can you change the number of background work processes?
Answer: D
The instance profile is the correct profile in this case, as settings in this profile
only apply to the affected instance, and the number of work processes for
an instance is defined here. The start profile contains information about the
processes to be started during the system start. In the default profile, you
maintain parameters that apply to all instances or for the entire SAP system.
The background profile does not exist.
3.
You can use transaction RZ10 to check the consistency of individual profiles.
Answer: RZ10
In addition to the consistency of the individual profiles, you can use transaction
RZ10 to check all profiles. In this case, the system also checks the consistency
between the profiles.
4.
In what sequence should you perform the listed steps when setting up operation
modes?
Answer: A
You must followthe correct sequence when first setting up the operation modes.
116
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 4
Access to Help
Unit Overview
In this unit, you will learn about the online documentation and the SAP Service
Marketplace. Both addresses are central starting points for obtaining information
about SAP.
Unit Objectives
After completing this unit, you will be able to:
•
•
Set up access to the online documentation
Use the information provided by the SAP Service Marketplace
Unit Contents
Lesson: Configuring the Online Documentation ................................ 118
Exercise 8: Access to Help.................................................... 129
2005/Q2
© 2005 SAP AG. All rights reserved.
117
Unit 4: Access to Help
ADM100
Lesson: Configuring the Online Documentation
Lesson Overview
This lesson covers the setting up of the online documentation. In addition to the work
in the system, activities must also be performed on the front end computer. The SAP
Service Marketplace is also introduced.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Set up access to the online documentation
Use the information provided by the SAP Service Marketplace
Business Example
The administrator has to make the online help available for all users of the system.
Access to the Documentation with the SAP Library
The SAP Library, which is also known as the online documentation, is an important
source of information, and contains information about all relevant topics in the SAP
environment. Installing the online documentation locally or company-wide helps
users to work more effectively with the SAP system.
Figure 46: Access to Documentation with the SAP Library
118
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
By choosing SAP Library in the Help menu, you can display the online documentation.
The terms SAP Library and online documentation are often used synonymously. The
SAP Library of an SAP system always contains the complete online documentation
for the system. In this way, the SAP Library for an SAP Web Application Server, for
example, currently offers access to more than 10,000 documents.
Using the SAP Library, you can easily search the online documentation, access a
glossary, and call an introduction to using SAP systems (“Getting Started”).
The online documentation is provided in various languages and, if the calling of help
has been correctly configured (as explained in the following pages), is called up in the
user's logon language.
The Supported Help Types
Figure 47: The Supported Help Types
2005/Q2
© 2005 SAP AG. All rights reserved.
119
Unit 4: Access to Help
ADM100
HtmlHelpFile
With this help type, the documents are stored in Compiled HTML format
(*.CHM). The files are made available using a file server and are displayed with
the HTML Help Viewer. Compiled HTML is a format developed by Microsoft
for storing HTML files in compressed format. The storage space requirement for
CHM files is around a tenth of the requirement for uncompressed HTML files
and is comparable to the requirement for WinHelp files. Microsoft introduced
the HTML Help Viewer as a successor to WinHelp. It is based on Microsoft
Internet Explorer. This type of help can only be used on Microsoft Windows
32 bit front end platforms. This type of help provides a full text search for all
documents (global search) or in the documents of the current help file (local
search). It is possible to print multiple documents concurrently.
PlainHtmlHttp
With this help type, the documents are stored in the standard HTML format. The
documents are made available using a Web server and are displayed with a
standard Web Browser. This help type can be used on all front end platforms
and the documentation is displayed using a standard Web browser (Microsoft
Internet Explorer or Netscape). This help provides a full text search in all
documents (global search) and allows you to print individual help documents.
PlainHtmlFile
This (most simple) help type also stores the documents in standard HTML
format. The documents are made available using a file server and are displayed
with a standard Web browser. This help variant can be used on all front end
platforms except Microsoft Windows 3.1x (16 bit), and allows you to print
individual help documents.
DynamicHelp
DynamicHelp can be used on all front end platforms. It uses the standard HTML
format for its files; the file access takes place using the Knowledge Warehouse
server. The documents are displayed in a standard Web browser. For more
information, see the online documentation for the Knowledge Warehouse.
120
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
Setup Work in the SAP System: SR13
Figure 48: Setting Up the Documentation in the SAP System
With the IMG activity General Settings → Setting variants for help (SAP Library), you
define which variant(s) of the online help are available to the users of the SAP system.
Caution: Without a corresponding configuration in transaction SR13, it is
not possible to call help successfully. This is true even if there is a correctly
maintained local SAPDOCCD.INI file. In this case, the system displays the
message No documentation available.
As of SAP R/3 4.6C, you no longer need to maintain profile parameters for the online
help. During an upgrade from SAP Basis 4.x to SAP Web Application Server 6.20
or higher, the values stored in the eu/iwb/... profile parameters for help type, storage
location, and language version of the help files are read and copied as a settings
variant by an XPRA program. Since these automatically created settings variants
(GENERATED_BY_XPRA ...) cannot be changed, you must create new settings
variants that copy the specifications for the storage location of the help files from
the automatically created entries, as long as they are still valid, and then delete the
automatically generated settings variants. Use descriptive names when creating new
settings variants.
2005/Q2
© 2005 SAP AG. All rights reserved.
121
Unit 4: Access to Help
ADM100
SR13, an example for the help type HtmlHelpFile:
•
Variant:
Documentation or a different descriptive text
•
Platform:
WN32; This setting is also appropriate for Microsoft Windows NT front ends,
for example (See SAP Note 333584)
•
Area
Documentation (is automatically replaced by iwbhelp)
•
Path
For example: \\twdf9999\Doku\620\ (without language selection)
•
Language
E English, selected using the F4 help (this is automatically replaced with EN).
•
Default
Setting this indicator in this example means that the help type HtmlHelpFile is
the default help in the area Documentation for WN32 front ends.
The above example specifies that on Microsoft Windows NT-based front ends, the
help variant documentation determines the help that is usually called with its settings.
In this case, this means that the online documentation is called from a network drive
\\twdf9999\Doku\620\EN. Note that the language ID was automatically added to
the path.
For front ends of other types (for example, non-Windows based), another help type
can be called by default. For these other front ends, you must also set a separate
settings variant as the default.
By maintaining and providing multiple settings variants, you can make the online help
available in various ways. A settings variant specifies a configuration of help type,
storage location of the help files (server and/or path) and the language version of the
help files for a particular front end platform. If you provide multiple settings variants
for a front end platform, the users can choose between these variants using the menu
Help → Settings (Extended Help tab page).
In every settings variant, you must specify the Area where it applies, in addition to the
front end platform. The area indicates the application area of the SAP Knowledge
Warehouse from which the contents to be displayed are taken. The area IWBHELP
122
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
(documentation) contains the online documentation delivered to all customers.
Customers that use the SAP Knowledge Warehouse can also define settings variants
for the area IWBTRAIN (training).
Setup Work at the Front End: The sapdoccd.ini File
A default setting for the selection of online documentation must be made in the
system for every utilized front end platform. If multiple help types are installed,
the end user can choose between these variants using the menu Help → Settings
(Extended Help tab page).
Figure 49: The sapdoccd.ini File
If it is necessary to set up special settings for the online documentation on certain front
ends, the call of the online documentation can be controlled on Microsoft Windows
front ends with entries in the file sapdoccd.ini (possible storage locations for this
file are shown in the previous figure).
Hint: Up to SAP GUI 6.10 (inclusive), the possible paths for the
sapdoccd.ini file, in addition to \WINNT, are:
Program Files → SAPpc
Program Files → SAPpc → SAPgui
2005/Q2
© 2005 SAP AG. All rights reserved.
123
Unit 4: Access to Help
ADM100
A possible reason for using this option is, for example, that there is a WAN connection
between the front end and the storage location defined in the system for the online
documentation. To avoid increased network load in this case, documentation that
is available over a local network from the front end should be accessed. This
locally available online documentation can be accessed using the information in the
sapdoccd.ini file. If this file exists with valid settings, these override the system
settings for the relevant front end. Possible entries in the sapdoccd.ini file are
shown in the next figure.
Hint: The sapdoccd.ini file is only evaluated if settings for access to the
online documentation exist in the system (transaction SR13). Otherwise, the
system displays the message “No documentation available”.
Figure 50: Contents of sapdoccd.ini
Note: For detailed information about the content and structure of
sapdoccd.ini, see SAP Note 94849: SAPDOCCD.INI - Description.
124
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
Explanation of the parameters and possible values:
•
•
•
•
HelpType: PlainHtmlHttp, PlainHtmlFile, HtmlHelpFile, DynamicHelp,
GetFromR3
<HelpType>Server: Name of the Web server where the files for <HelpType>
are stored
<HelpType>Path-<Language>: Path where the help for the logon language
<Language> is stored: <Language> should be replaced with a two-character
language ID.
<HelpType>Path: Path where the help that is to be displayed if the parameter
<HelpType>Path-<Language> is not defined for the current logon language
is stored.
–
The help type GetFromR3 does not represent a separate help type; it is used
to copy the current valid settings variant of the SAP system. If GetFromR3
is specified as the help type (HelpType=GetFromR3), the settings are
copied from the SAP system. If the server and/or path to the corresponding
help type are also specified in the sapdoccd.ini file, these settings
override the settings from the SAP system.
Caution: Since the online documentation can also be regularly updated as of
SAP Web AS 6.20, there can, for example, be multiple versions of the SAP
Web AS 6.20 documentation. SAP Note 684431: Setting 'OTHER_RELEASE'
in table IWBSETTING describes how you should proceed in this case.
2005/Q2
© 2005 SAP AG. All rights reserved.
125
Unit 4: Access to Help
ADM100
SAP Help Portal
Figure 51: The SAP Help Portal
The SAP Help Portal provides Internet-based access to the available online
documentation for SAP software solutions. The Help Portal can be accessed from
every Web-capable front end without logon. The documentation provided can be
accessed very efficiently using a full text search.
126
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
SAP Service Marketplace
Figure 52: The SAP Service Marketplace
The Web site http://www.sap.com provides information about all SAP Solutions and
about SAP as a company. This information is public and can be accessed by anyone.
In addition to this, SAP provides various services, detailed information, and so on for
customers and partners on the SAP Service Marketplace at http://service.sap.com.
Access to the SAP Service Marketplace (SMP) is free of charge; however, it is
protected by a user name and password logon. There is at least one person with access
to the SMP at every customer. This person can create additional users and assign
certain authorizations to those users.
There are two simple options available to simplify navigation:
•
•
2005/Q2
Personalization of the initial screen
Navigation using Quick Links, such as http://service.sap.com/smp. Quick Links
are simply added to the basic address after a “/”. In this case: “smp”.
© 2005 SAP AG. All rights reserved.
127
Unit 4: Access to Help
ADM100
Important Quick Links:
•
•
•
•
•
•
•
•
•
/user-admin: user administration on the SMP (for your users)
/sscr: You can obtain SAP Software Change Registration keys here
/notes: The online access to SAP Notes is available using this Quick Link
/swdc: You can obtain patches, updates, and other software for your SAP
systems here
/message: This Quick Link allows you to create a message to SAP
/servicecat: The service catalog displays a list of the services offered by SAP
/instguides: You can find installation guides for the various SAP solutions here
/netweaver: This Quick Link leads to the newest information about SAP
NetWeaver™
/education: You can find information about the SAP training courses available
worldwide in an online catalog here
Additional Information
•
•
•
•
SAP Library
http://help.sap.com
http://service.sap.com
SAP Notes
–
–
–
–
–
128
SAP Note 94849: SAPDOCCD.INI - Description
SAP Note 95309: SAPDOCCD.LOG - Description
SAP Note 101481: Collective note: Application help and R/3 library
SAP Note 302459: Setting variants for online help
SAP Note 333584: Frequent errors in settings of the SAP Library
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
Exercise 8: Access to Help
Exercise Objectives
After completing this exercise, you will be able to:
•
Install the online documentation
Business Example
The administrator has to make the online help available for all users of the system.
Task 1: Test the Online Documentation (optional)
Unsuccessful call of the online documentation
1.
Start the call for the online documentation. This should fail.
Task 2: Set Up the Online Documentation
Make settings in transaction SR13.
1.
In your system, call the cross-client maintenance of the online documentation
access. Maintain the settings for the help type HtmlHelpFile in accordance with
the example values in the training material (Note: SR13: An Example).
Note that you cannot specify a correct path to the online documentation files.
The online documentation is not accessible for the servers in the training
environment for administrative training courses. Therefore, the settings in the
sapdoccd.ini file on your front end take precedence, once you have made
settings in SR13.
Task 3: Call the Online Documentation
Perform a successful call of the online documentation.
1.
Start the call for the online documentation. Although the settings in transaction
SR13 do not point to available online documentation, this call should still be
successful because there is a local sapdoccd.ini file on your front end.
This points to help that is available to your front end. If there is no SAP Web
AS 6.20 online documentation available in the training center that you are
attending, you can use the Internet-based help for the rest of this training course,
under http://help.sap.com.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
129
Unit 4: Access to Help
ADM100
Task 4: Use the SAP Service Marketplace
130
1.
Call the URL for the SAP Service Marketplace: http://service.sap.com.
2.
Use your own S user (as an SAP customer, you have a user of this type) to log
on to the SAP Service Marketplace.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
Solution 8: Access to Help
Task 1: Test the Online Documentation (optional)
Unsuccessful call of the online documentation
1.
Start the call for the online documentation. This should fail.
a)
Choose Help → SAP Library. The system displays the message “No
documentation available”.
Task 2: Set Up the Online Documentation
Make settings in transaction SR13.
1.
In your system, call the cross-client maintenance of the online documentation
access. Maintain the settings for the help type HtmlHelpFile in accordance with
the example values in the training material (Note: SR13: An Example).
Note that you cannot specify a correct path to the online documentation files.
The online documentation is not accessible for the servers in the training
environment for administrative training courses. Therefore, the settings in the
sapdoccd.ini file on your front end take precedence, once you have made
settings in SR13.
a)
Start transaction SR13 or follow the path listed in the course manual. Then
enter the example settings from the training material (“Note: SR13: An
Example”) on the HtmlHelpFile tab page. Choose New Entries to make the
fields ready for input, make all of your entries, and then choose Save.
Task 3: Call the Online Documentation
Perform a successful call of the online documentation.
1.
Start the call for the online documentation. Although the settings in transaction
SR13 do not point to available online documentation, this call should still be
successful because there is a local sapdoccd.ini file on your front end.
This points to help that is available to your front end. If there is no SAP Web
AS 6.20 online documentation available in the training center that you are
attending, you can use the Internet-based help for the rest of this training course,
under http://help.sap.com.
a)
Follow the exercise instructions.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
131
Unit 4: Access to Help
ADM100
Task 4: Use the SAP Service Marketplace
1.
Call the URL for the SAP Service Marketplace: http://service.sap.com.
a)
2.
Start the browser on your front end and use the specified address. Confirm
any dialog boxes that appear.
Use your own S user (as an SAP customer, you have a user of this type) to log
on to the SAP Service Marketplace.
a)
Choose the Login Now button on the initial screen of the SAP Service
Marketplace to display the user name and password query.
Explore the SAP Service Marketplace.
132
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring the Online Documentation
Lesson Summary
You should now be able to:
•
Set up access to the online documentation
•
Use the information provided by the SAP Service Marketplace
2005/Q2
© 2005 SAP AG. All rights reserved.
133
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Set up access to the online documentation
•
Use the information provided by the SAP Service Marketplace
134
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
The SAP Library provides you with information about how to partition your
hard disks.
Determine whether this statement is true or false.
□
□
2.
True
False
The SAP Library also offers a glossary of important terms.
Determine whether this statement is true or false.
□
□
3.
True
False
The SAP Library is only available on the Internet at the URL http://help.sap.com.
Determine whether this statement is true or false.
□
□
4.
True
False
The following technical forms of the online help, also known as the SAP
Library, are available:
Choose the correct answer(s).
□
□
□
□
□
□
5.
2005/Q2
A
B
C
D
E
F
Compressed HTML (.comphtml)
PlainHtmlHttp
PlainHtmlFile
StaticHelp
DynamicHelp
SAP HelpKit
The sapdoccd.ini file can be stored in three different places. In which
sequence is the directory tree searched: A) C:\Program Files\SAP\FrontEnd\, B)
C:\WINNT, and C) C:\Program Files\SAP\FrontEnd\SAPgui?
© 2005 SAP AG. All rights reserved.
135
Test Your Knowledge
ADM100
Answers
1.
The SAP Library provides you with information about how to partition your
hard disks.
Answer: False
Partitioning hard disks is not part of the SAP Library.
2.
The SAP Library also offers a glossary of important terms.
Answer: True
Yes, it does.
3.
The SAP Library is only available on the Internet at the URL http://help.sap.com.
Answer: False
The SAP Library can and should also be set up locally, for example, on a file or
Web server.
4.
The following technical forms of the online help, also known as the SAP
Library, are available:
Answer: B, C, E
Compressed HTML does not exist, although Compiled HTML (.chm) does.
Compiled HTML is the recommended format for 32 bit Microsoft Windows front
ends. The other help types are PlainHtmlHttp, PlainHtmlFile, and DynamicHelp.
5.
The sapdoccd.ini file can be stored in three different places. In which
sequence is the directory tree searched: A) C:\Program Files\SAP\FrontEnd\, B)
C:\WINNT, and C) C:\Program Files\SAP\FrontEnd\SAPgui?
Answer: The sequence is: B - C - A.
136
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 5
Fundamentals of Working with the
Database
Unit Overview
This unit provides basic theoretical information about the architecture and
functionality of a relational database. Building on this knowledge, basic database
administrative activities, performed using the database planning calendar (transaction
DB13), are introduced.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
Describe in principle the structure and architecture of database systems
Back up the contents of the database
Check whether your database backups have been successfully performed
Schedule additional periodic checks of the database
Unit Contents
Lesson: Architecture of Database Systems ..................................... 138
Lesson: Backing Up the Database Contents.................................... 141
Exercise 9: Back Up the Database Contents ............................... 147
Lesson: Overview: Monitoring the Database ................................... 150
Exercise 10: Overview: Monitoring the Database.......................... 153
2005/Q2
© 2005 SAP AG. All rights reserved.
137
Unit 5: Fundamentals of Working with the Database
ADM100
Lesson: Architecture of Database Systems
Lesson Overview
This lesson provides basic theoretical information about the architecture and
functionality of a relational database.
Lesson Objectives
After completing this lesson, you will be able to:
•
Describe in principle the structure and architecture of database systems
Business Example
SAP systems store the application data in a relational database. The administrator
regularly backs up this data.
Fundamentals of Database Administration
A database management system (DBMS) includes database processes, a buffer in
the main memory, data files that contain the data, and log files, where changes to
the data are logged.
At the start of an SAP system, all work processes are linked to a database process.
Database queries are passed by SAP work processes to their dedicated database
processes, which perform the query on the database.
The data is stored in the data files: Access to the data always takes place using the
buffer in main memory.
The special database processes are responsible for the exchange of data between the
buffer and the data files. During this exchange, the data is always read and written in
complete pages (which usually contain several data records).
138
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Architecture of Database Systems
Figure 53: Database: Concepts
If changes are made to the data, these are logged in the log file; that is, the log file
contains the status changes of the database. Only the changes, and not the complete
pages, are logged in the log buffer. The entries are written from the log buffer to the
log file, of which there can be one or more than one, depending on the database. For
every database, there is a mechanism that backs up the log information from the log
file to other files or directly to a backup medium. This ensures that the log file does
not become too large. SAP recommends that you mirror the log file. Some databases
provide special software mirrors to allow you to do this.
Caution: This mechanism cannot be deactivated; otherwise, the status
changes could be lost. This would mean that there was a threat of data loss if
a hard disk crash occurred.
A database always also includes structure data that contains essential information for
the database, such as the number of data files, and so on.
2005/Q2
© 2005 SAP AG. All rights reserved.
139
Unit 5: Fundamentals of Working with the Database
ADM100
Lesson Summary
You should now be able to:
•
Describe in principle the structure and architecture of database systems
Related Information
This introductory course to SAP system administration emphasizes the importance
of working in the correct way with the database and provides basic theoretical
knowledge about the functions of a database, such as how to work with the central
transaction for database management in the SAP system, transaction DB13. For more
detailed information, attend database-specific courses run by your database vendor,
and/or attend training course ADM5##.
140
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Backing Up the Database Contents
Lesson: Backing Up the Database Contents
Lesson Overview
This lesson deals with basic concepts for backing up the database. These concepts
include regular backups of data and log information. These backups are performed
with the database planning calendar (transaction DB13).
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Back up the contents of the database
Check whether your database backups have been successfully performed
Business Example
To protect the SAP system against data loss if an error occurs, the administrator
regularly performs backups.
Backup Concept
A backup concept for the database always includes the regular backup of the data
files, the structure data, and also the log information.
The backup of the data files and the log information is performed in different steps.
All data files and the structure data are backed up in one step. In another step, the
ongoing log information (this may include the structure data) is backed up separately.
2005/Q2
© 2005 SAP AG. All rights reserved.
141
Unit 5: Fundamentals of Working with the Database
ADM100
Figure 54: Back Up of the Data and Log Information
You can schedule both of these steps in the SAP system (except for AS400) as regular
actions in the database planning calendar (transaction DB13).
Scenarios for Recovering a Database
Resetting the database (with data loss)
If a disk crash occurs at a point between t1 and t2, all data from the data backup t1 is
imported. If no further action is taken, all data changes that were made after t1 are lost.
142
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Backing Up the Database Contents
Figure 55: Database Recovery 1/2
Recovering the database (without data loss)
All data from data backup t1 is imported. Some databases allow you to import only
the data files that are missing. In this case, the system follows all log information
written since t1 (22, 23, ...). As a final step, the log file is followed. This means
that all data is now once again in the same status as at the point when the disk crash
occurred. Only if all log information since the data backup is available, with no gaps,
will there be no data loss.
2005/Q2
© 2005 SAP AG. All rights reserved.
143
Unit 5: Fundamentals of Working with the Database
ADM100
Figure 56: Database Recovery 2/2
Storing the data and log info backups
The backed-up log information is deleted at operating system level so that no disk
space problems occur. If a disk crash occurs at time t5 and a backup medium for
the backup t3 is defective, an earlier data backup (in this case, t1) must be used. To
recover the database without data loss, it is absolutely necessary to have all log info
backups (in this case: t2 and t4) since the data backup t1 and the log information as of
28. It is, therefore, necessary to keep older data and log info backups.
Other remarks
Some databases also require log information to be able to reset the database. You
should therefore ensure that you perform data and log backups regularly.
Backup Cycle
SAP recommends that the duration of a backup cycle is 28 days. This means that the
backup media for the data and log info backups are overwritten after 28 days, at the
earliest.
144
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Backing Up the Database Contents
Figure 57: Recommended Backup Cycle
SAP strongly recommends that you perform complete data backups every day.
Some databases offer the option of performing differential or incremental data backups
that do not backup the complete data of the database (these data backups are described
in the following as partial data backups). If you use a partial data backup as your daily
backup, you must perform a complete data backup at least once a week. There must
be at least four complete data backups contained in the backup cycle.
The log information should be backed up at least once a day. You should always have
two different backup media containing the same information.
Perform a data and log info backup with verification of the backup media at least
once in the backup cycle.
Scheduling and Monitoring Backups
In the SAP system, you can schedule and monitor regular database backups with
transaction DB13.
Select the data backup procedure for each week day (recommendation: the
database-specific procedure for complete data backup) and enter the repetition period
(such as 1). Choose the start time or immediate start.
If a manual medium swap is required, if you are, for example, using a local tape
station, check which medium is required for the next backup every day, and insert this
medium before the start of the backup.
Enter the log info backup for every week day in the same way as the data backup.
2005/Q2
© 2005 SAP AG. All rights reserved.
145
Unit 5: Fundamentals of Working with the Database
ADM100
Figure 58: Scheduling and Monitoring DB Backups
You can set the display of the planning calendar using the menu path Calendar →
Calendar Display.
Check every day whether your backups have been successfully completed. In the
planning calendar, a successful backup displays with green or yellow (with warnings)
labeling. Red labeling indicates an erroneous (and, therefore, unusable) backup. You
can display additional information with transaction DB12.
You can control and monitor the backups for your entire system landscape with the
central planning calendar (transaction DB13C). The schedules are transferred to the
remote systems using an RFC connection.
146
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Backing Up the Database Contents
Exercise 9: Back Up the Database Contents
Exercise Objectives
After completing this exercise, you will be able to:
•
Perform a number of basic activities in the database backup and database
maintenance environment
Business Example
To protect the SAP system against data loss if an error occurs, the administrator
regularly performs backups.
Task: Back Up the Contents of the Database
Perform a backup of the data files and a log backup.
2005/Q2
1.
Display an overview of the utilized backup media. If you have performed a
successful backup, what must you then consider before you can start the next
backup (Hint: Overwritability)?
2.
Schedule a Log Backup in transaction DB13. Use the device FORLOG as the
backup device. The backup terminates immediately. Attempt to determine the
cause of this error using the logs.
3.
Schedule a Complete data backup with an immediate start in transaction DB13.
Use the device FORDATA as the backup device. If the backup starts successfully,
the label in transaction for the backup run DB13 is yellow (process is running).
The backup takes around 20 minutes.
© 2005 SAP AG. All rights reserved.
147
Unit 5: Fundamentals of Working with the Database
ADM100
Solution 9: Back Up the Database Contents
Task: Back Up the Contents of the Database
Perform a backup of the data files and a log backup.
1.
Display an overview of the utilized backup media. If you have performed a
successful backup, what must you then consider before you can start the next
backup (Hint: Overwritability)?
a)
2.
Schedule a Log Backup in transaction DB13. Use the device FORLOG as the
backup device. The backup terminates immediately. Attempt to determine the
cause of this error using the logs.
a)
3.
The job or action log displays that the database is in a log mode that is
invalid for this backup type.
Schedule a Complete data backup with an immediate start in transaction DB13.
Use the device FORDATA as the backup device. If the backup starts successfully,
the label in transaction for the backup run DB13 is yellow (process is running).
The backup takes around 20 minutes.
a)
148
In transaction DB13 (menu path Tools → CCMS → DB Administration →
Planning Calendar → Local), choose the Backup Media button to obtain
an overview of the available backup media. As the name of the backup
file is a fixed assignment, you can only start the next backup once the
existing backup file has been renamed or moved to a different location, due
to the setting Overwritable = NO.
When you return from your break, the backup should be successfully
completed, and displayed as green in DB13. If the label has not changed
to green, check the time of the last successful backup using transaction
DB12. If the backup that you have just performed is shown here, there is a
display problem in DB13.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Backing Up the Database Contents
Lesson Summary
You should now be able to:
•
Back up the contents of the database
•
Check whether your database backups have been successfully performed
2005/Q2
© 2005 SAP AG. All rights reserved.
149
Unit 5: Fundamentals of Working with the Database
ADM100
Lesson: Overview: Monitoring the Database
Lesson Overview
There may be a large number of periodic checks that need to be performed in addition
to making backups, depending on the database that you are using.
Lesson Objectives
After completing this lesson, you will be able to:
•
Schedule additional periodic checks of the database
Business Example
To ensure good database performance and, therefore, good SAP system performance,
the administrator performs additional checks of the database, which can be regularly
scheduled.
Regular Monitoring of the Database
In addition to the daily monitoring of the database backups, there are a number of
other checks that may have to be performed regularly, depending on the database.
Some of these can be scheduled using the DB planning calendar (transaction DB13).
Figure 59: Database Monitoring
150
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Overview: Monitoring the Database
These checks can, for example, be:
•
•
•
Growth of the database (such as free space)
Generation of statistical data to ensure good performance when accessing data
records
Check for general database problems or errors
For more information about these checks, contact your database vendor, see the
technical literature and documentation, contact an SAP consultant, or attend one of
our administration courses for the database that you are using.
2005/Q2
© 2005 SAP AG. All rights reserved.
151
Unit 5: Fundamentals of Working with the Database
ADM100
152
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Overview: Monitoring the Database
Exercise 10: Overview: Monitoring the
Database
Exercise Objectives
After completing this exercise, you will be able to:
•
Schedule additional periodic checks of the database
Business Example
To ensure good database performance and, therefore, good SAP system performance,
the administrator performs additional checks of the database, which can be regularly
scheduled.
Task: Update the Statistical Data
Schedule the generation of current statistical data in transaction DB13.
2005/Q2
1.
Check the existing Optimizer statistics
2.
Refresh the existing statistical data
© 2005 SAP AG. All rights reserved.
153
Unit 5: Fundamentals of Working with the Database
ADM100
Solution 10: Overview: Monitoring the
Database
Task: Update the Statistical Data
Schedule the generation of current statistical data in transaction DB13.
1.
Check the existing Optimizer statistics
a)
2.
Refresh the existing statistical data
a)
154
Start the Check optimizer statistics action with Immediate start using
transaction DB13. Check its success. Ensure that there are no other active
DB13 actions. You can display today’s DB13 actions, for example, by
choosing the Day line in the scheduling calendar. Estimated runtime: 5
minutes
You can refresh the existing statistical data by choosing Refresh
optimizer/space statistics. This data is a requirement for an efficiently
running SAP system. Estimated runtime: 15 minutes
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Overview: Monitoring the Database
Lesson Summary
You should now be able to:
•
Schedule additional periodic checks of the database
2005/Q2
© 2005 SAP AG. All rights reserved.
155
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Describe in principle the structure and architecture of database systems
•
Back up the contents of the database
•
Check whether your database backups have been successfully performed
•
Schedule additional periodic checks of the database
156
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
Changes to the data are logged by the database in the
files also contain the changes in status of the
. These
.
Fill in the blanks to complete the sentence.
2.
To minimize the risk of data loss, SAP strongly recommends a
complete data backup. If you use a partial data backup as your daily backup, you
.
must perform a complete data backup at least once a
Fill in the blanks to complete the sentence.
2005/Q2
© 2005 SAP AG. All rights reserved.
157
Test Your Knowledge
ADM100
Answers
1.
Changes to the data are logged by the database in the log files. These files also
contain the changes in status of the database.
Answer: log files, database
The log mechanism is essential and must not be deactivated.
2.
To minimize the risk of data loss, SAP strongly recommends a daily complete
data backup. If you use a partial data backup as your daily backup, you must
perform a complete data backup at least once a week.
Answer: daily, week
In addition to a complete data backup, you should, of course, also back up the
log information at least once a day.
158
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 6
Basics of User Administration
Unit Overview
This unit addresses the SAP authorization concept. The focus is on explaining
important terms and creating roles and authorization profiles. System parameters will
be used to demonstrate how relevant settings can be made in the system. The use of
central directory services is also introduced.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
Create users
Copy, create, and maintain roles
Maintain the assignment of roles and users
Set system parameters for user logons
Locate authorization problems
Describe the concept of Central User Administration
Describe connection to directory services
Unit Contents
Lesson: User Administration Concept............................................ 160
Exercise 11: Basics of User Administration ................................. 165
Lesson: Authorization Concept ................................................... 169
Exercise 12: Working with Roles ............................................. 177
Lesson: Login Parameters and User Info........................................ 183
Lesson: Appendix: Advanced User Administration Topics .................... 189
2005/Q2
© 2005 SAP AG. All rights reserved.
159
Unit 6: Basics of User Administration
ADM100
Lesson: User Administration Concept
Lesson Overview
This lesson explores the administration of user master records. Creating, copying, and
maintaining master records of this type will be described in more detail.
Lesson Objectives
After completing this lesson, you will be able to:
•
Create users
Business Example
The users of the SAP system require their own user with appropriate authorizations to
log on. The administrator sets up a user in the system for each user.
Basics of User Administration
The concept of the user master record and the authorization concept are explained in
more detail below. Both of these are important to obtain a better understanding of
SAP systems.
Figure 60: Users in the SAP Environment
160
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: User Administration Concept
The term user usually means user ID here. People log on to an operating system, a
database, or an SAP system using a user/password combination. Operating systems,
databases, and SAP systems usually have different authorization concepts. If a
user/password combination is created in an SAP system for a person, this does not
mean that it is possible to log on to the operating system of a host with the same
user/password combination. However, it is possible that identical user/password
combinations are created for SAP systems and operating systems.
Note: User requests are processed by SAP work processes. These work
processes all use a shared user to access the database.
This unit deals exclusively with SAP users, which people use to log on to a client of
an SAP system. Users and authorization data are client-dependent.
Access to the operating system level of the SAP Web Application Server and the
database server must be protected, or the operation or the data of the SAP systems
could be threatened.
Figure 61: Users and Authorizations
A person can log on to a client of an SAP system if they know the user/password
combination for a user master record.
2005/Q2
© 2005 SAP AG. All rights reserved.
161
Unit 6: Basics of User Administration
ADM100
In the SAP system, there is an authorization check every time a transaction is called. If
a user attempts to start a transaction for which he or she is not authorized, the system
rejects the user with an appropriate error message.
If the user starts a transaction for which he or she has authorization, the system
displays the initial screen of this transaction. Depending on the transaction called, the
user enters data and performs actions on this screen. Additional authorization checks
are made for data and actions that are to be protected.
Users are assigned authorizations using roles. The authorizations are combined in
roles and the roles are entered in the user master record. This is explained in more
detail later in this unit.
Figure 62: User Master Record
The user type is an important property of a user. Different user types are available
for different purposes:
Dialog
A normal dialog user is used for all logon types by exactly one person. During a
dialog logon, the system checks for expired/initial passwords, and the user has
the opportunity to change his or her own password. Multiple dialog logons are
checked and, if appropriate, logged.
162
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: User Administration Concept
System
Use the System user type for dialog-free communication within a system or
for background processing within a system, or also for RFC users for various
applications, such as ALE, Workflow, Transport Management System, Central
User Administration. It is not possible to use this type of user for a dialog logon.
Users of this type are excepted from the usual settings for the validity period of a
password. Only user administrators can change the password.
Note: See also SAP Note 622464.
Communication
Use the communication user type for dialog-free communication between
systems. It is not possible to use this type of user for a dialog logon. The usual
settings for the validity period of a password apply to users of this type.
Service
A user of the type Service is a dialog user that is available to a larger,
anonymous group of users. In general, you should only assign highly restricted
authorizations to users of this type. Service users are used, for example, for
anonymous system accesses using an ITS or ICF service. The system does not
check for expired/initial passwords during logon. Only the user administrator
can change the password. Multiple logons are permitted.
Reference
A reference user is, like the service user, a general non-person-related user. You
cannot use a reference user to log on. A reference user is used only to assign
additional authorizations. You can specify a reference user for a dialog user for
additional authorization on the Roles tab page.
2005/Q2
© 2005 SAP AG. All rights reserved.
163
Unit 6: Basics of User Administration
ADM100
Figure 63: User Types
To start user maintenance (transaction SU01), choose Tools → Administration → User
Maintenance → Users.
You can create a new user master record by copying an existing user master record or
creating a completely new one. The user master record contains all data and settings
that are required to log on to a client of the SAP system. This data is divided into
the following tab pages:
•
•
•
•
•
•
Address: Address data.
Logon Data: Password and validity period of the user, and user type.
Defaults: Default values for a default printer, the logon language, and so on.
Parameters: User-specific values for standard fields in SAP systems.
Roles and Profiles: Roles and profiles that are assigned to the user.
Groups: For the grouping of users for mass maintenance.
You must maintain at least the following input fields when creating a user: Last name
on the Address tab page, initial password and identical repetition of password on
the Logon Data tab page.
164
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: User Administration Concept
Exercise 11: Basics of User Administration
Exercise Objectives
After completing this exercise, you will be able to:
•
Create users
Business Example
As an administrator, you must create new users and lock existing users.
Task 1: Create Users
Create a user with the name ADMIN<##>, where <##> is your group number. Follow
these steps.
1.
Create a user (master record) with the name ADMIN<##>.
2.
Maintain the first and last names of the user.
3.
Assign an initial password to the user (and remember it), and assign the user to
the User Group for Authorization Checks SUPER.
4.
Enter a default value for the logon language for the user (such as EN or DE).
5.
Save the user master record.
Task 2: Copy a User
Create a user with the name MONITOR<##> by copying the user MONITOR, where
<##> is your group number. Follow these steps.
2005/Q2
1.
Create a user with the name MONITOR<##> by copying the user MONITOR.
2.
Assign the initial password monitor.
3.
Save the user master record.
© 2005 SAP AG. All rights reserved.
165
Unit 6: Basics of User Administration
ADM100
Solution 11: Basics of User Administration
Task 1: Create Users
Create a user with the name ADMIN<##>, where <##> is your group number. Follow
these steps.
1.
Create a user (master record) with the name ADMIN<##>.
a)
2.
Maintain the first and last names of the user.
a)
3.
Choose the Logon Data tab page. In the Initial Password field, enter the
password and press the TAB key to move to the Repeat Password field.
Enter the password again in this field. Move the cursor to the User Group
for Authorization Checks input field, and choose the group SUPER using
the F4 help.
Enter a default value for the logon language for the user (such as EN or DE).
a)
5.
Choose the Address tab page. Enter the first and last names in the
appropriate fields.
Assign an initial password to the user (and remember it), and assign the user to
the User Group for Authorization Checks SUPER.
a)
4.
Start transaction SU01. Enter the name ADMIN<##> in the User field
and choose Create.
Choose the Defaults tab page. In the Logon Language field, enter EN for
English, or DE for German.
Save the user master record.
a)
Choose Save.
Task 2: Copy a User
Create a user with the name MONITOR<##> by copying the user MONITOR, where
<##> is your group number. Follow these steps.
1.
Create a user with the name MONITOR<##> by copying the user MONITOR.
a)
Start transaction SU01. Enter the name MONITOR in the User field and
choose Copy.
On the following dialog box, enter the user name MONITOR<##> in the
To field and choose Copy.
Continued on next page
166
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: User Administration Concept
2.
Assign the initial password monitor.
a)
3.
Choose the Logon Data tab page. In the Initial Password field, enter
the password monitor, and press the TAB key to move to the Repeat
Password field. Enter the password again in this field.
Save the user master record.
a)
Choose Save.
Result
You have created the users ADMIN<##> and MONITOR<##>.
2005/Q2
© 2005 SAP AG. All rights reserved.
167
Unit 6: Basics of User Administration
ADM100
Lesson Summary
You should now be able to:
•
Create users
168
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
Lesson: Authorization Concept
Lesson Overview
In this lesson, the terms authorization object, authorization profile, authorization
check, and role are discussed in a common context. The focus here is on role
maintenance; that is, on creating a role.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Copy, create, and maintain roles
Maintain the assignment of roles and users
Business Example
The authorizations for users are created using roles and profiles. The administrator
creates the roles, and the system supports him or her in creating the associated
authorizations.
Authorization Objects and Authorization Checks
Understanding the SAP authorization concept requires knowledge of the authorization
profile and roles in the user master record. This lesson provides you with the necessary
knowledge to be able to create your own roles and authorizations.
2005/Q2
© 2005 SAP AG. All rights reserved.
169
Unit 6: Basics of User Administration
ADM100
Figure 64: Authorization Objects
Actions and the access to data are protected by authorization objects in the SAP
system. The authorization objects are delivered by SAP and are in SAP systems. To
provide a better overview, authorization objects are divided into various object classes.
Authorization objects allow complex checks that involve multiple conditions that
allow a user to perform an action. The conditions are specified in authorization fields
for the authorization objects and are AND linked for the check. Authorization objects
and their fields have descriptive and technical names. In the example in the figure,
the authorization object User master maintenance: User Groups (technical name:
S_USER_GRP) contains the two fields Activity (technical name: ACTVT) and User
Group in User Master Record (technical name: CLASS). The authorization object
S_USER_GRP protects the user master record. An authorization object can include
up to ten authorization fields.
An authorization is always associated with exactly one authorization object and
contains the value for the fields for the authorization object. An authorization is
a permission to perform a certain action in the SAP system. The action is defined
on the basis of the values for the individual fields of an authorization object. For
example: Authorization B in the figure for authorization object S_USER_GRP allows
the display of all user master records that are not assigned to the user group SUPER.
There can be multiple authorizations for one authorization object. Some authorizations
are delivered by SAP, but the majority are created specifically for the customer's
requirements.
170
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
Figure 65: Authorization Check
When a user logs on to a client of an SAP system, his or her authorizations are loaded
in the user context. The user context is in the user buffer (in the main memory) of the
application server.
When the user calls a transaction, the system checks whether the user has an
authorization in the user context that allows him or her to call the selected transaction.
Authorization checks use the authorizations in the user context. If you assign new
authorizations to the user, it can be necessary for this user to log on to the SAP system
again to be able to use these new authorizations (for more information, see SAP Note
452904 and the documentation for the parameter auth/new_buffering).
If the authorization check for calling a transaction was successful, the system displays
the initial screen of the transaction. Depending on the transaction, the user can create
data or select actions. When the user completes his or her dialog step, the data is sent
to the dispatcher, which passes it to a dialog work process for processing. Authority
checks (AUTHORITY-CHECK) that are checked during runtime in the work process
are built into the coding by the ABAP developers for data and actions that are to be
protected. If the user context contains all required authorizations for the checks,
the data and actions are processed and the user receives the next screen. If one
authorization is missing, the data and actions are not processed and the user receives a
message that his or her authorizations are insufficient.
All authorizations are permissions. There are no authorizations for prohibiting.
Everything that is not explicitly allowed is forbidden.
2005/Q2
© 2005 SAP AG. All rights reserved.
171
Unit 6: Basics of User Administration
ADM100
Role Maintenance: Menus and Authorizations
Figure 66: Role Maintenance
Role Maintenance (transaction PFCG, previously also called Profile Generator or
activity groups) simplifies the creation of authorizations and their assignment to users.
In role maintenance, transactions that belong together from the company's point of
view are selected. Role maintenance creates authorizations with the required field
values for the authorization objects that are checked in the selected transactions.
A role can be assigned to various users. Changes to a role therefore have an effect
on multiple users. Users can be assigned various roles.
The user menu contains the entries (transactions, URLs, reports, and so on) that are
assigned to the user through the roles.
172
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
Figure 67: Menu Layout
You can access role maintenance with transaction PFCG or by choosing Tools →
Administration → User Maintenance → Role Administration → Roles. Enter the
name of the role and choose the icon for Create or Change. Choose the Menu tab page.
Select and change functions: The menu tree can be adjusted for the individual roles as
required.
You can insert or delete transactions into or from the tree structure.
By choosing the Report button, you can integrate Reports. In this case, role
maintenance creates transaction codes with which the reports can be called.
By choosing the Other button, you can add Internet addresses or links to files (such
as tables or text files). When integrating files, you must use the storage paths instead
of URLs. You can also specify BW WebReports, and links to external mail systems
and Knowledge Warehouse.
Change menus: You can create, move, delete, and rename directories and
subdirectories as required. You can use the Drag&Drop function in role maintenance.
2005/Q2
© 2005 SAP AG. All rights reserved.
173
Unit 6: Basics of User Administration
ADM100
Figure 68: Generating Authorization Profiles
Role maintenance automatically creates the authorizations that are associated
with the transactions specified in the menu tree. However, all authorization values
must be manually checked and adjusted if required in accordance with the actual
requirements and authorities. The system administrator is responsible for this task,
together with the appropriate user department. If you are using organizational levels,
this significantly simplifies authorization maintenance.
Choose the Authorizations tab page and choose Change Authorization Data. Check
the scope and contents of the authorizations.
In the authorization overview, a green traffic light indicates that the role maintenance
can automatically create an authorization. A yellow traffic light indicates that
the authorization must be manually maintained after it has been created. Role
maintenance does not provide a default value for the authorization. This example
deals with access to files. Role maintenance cannot guess whether data access should
only be read access, or should be read and write access.
Some fields appear in many authorizations. A number of important fields were
therefore combined into organizational levels, such as the company code. If you
maintain the organizational level, you maintain all fields in it. Therefore, a red traffic
light indicates an unmaintained organizational level.
Once all authorizations are maintained as required, the authorization profile can be
generated by choosing Generate. Important: The second character of the profile name
must not be an underscore (“_”) (see SAP Note 16466). After creation, this name
cannot be changed. The authorizations are combined in profiles. The profiles must be
entered in the user master record (by the role maintenance) for the authorizations to
take effect for the user.
174
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
Users and Roles
The assignment of users to roles is performed in the role maintenance transaction
(transaction PFCG) or in the user maintenance transaction (transaction SU01). Select
the User tab page and the user IDs to be maintained there. When selecting user IDs,
the system uses the current date as the start of the validity period of the assignment; it
sets 31.12.9999 as the end date. You can restrict both values.
Figure 69: Assigning Roles to Users
Users can be linked to more than one role. This can be useful if some activities (such
as printing) are to be permissible across roles.
The assignment of roles to users does not automatically grant the corresponding
authorizations to the users. To assign the authorizations, you must first perform a
user master comparison, during which the role's profiles are entered in the user
master record.
2005/Q2
© 2005 SAP AG. All rights reserved.
175
Unit 6: Basics of User Administration
ADM100
Figure 70: Comparing User Master Records
A user master comparison determines whether authorization profiles should be added
to or removed from the current user on the basis of his or her role assignment. During
a comparison, profiles are added to a user master due to roles that have been added.
If role assignments are manually or time-dependently removed, the corresponding
authorization profiles are deleted from the user master record.
The comparison can be performed for every role individually. Select the role in role
maintenance. Choose the Users tab page and choose User Reconciliation. In the
dialog box that the system displays, choose Complete Reconciliation.
If multiple role assignments are to be updated, you can perform a corresponding
comparison in role maintenance by choosing Utilities → Mass comparison
(transaction PFUD ). You can individually specify the desired roles, or update all
assignments by entering the asterisk (*) character.
You can also activate the periodic user master comparison in role maintenance by
choosing Utilities → Mass Comparison. Choose the option Schedule or check job for
full reconciliation. The system then displays a search window for the background job
PFCG_TIME_DEPENDENCY. If it does not find a corresponding job, you can create
a new one. The default value is that all user masters are compared once every day.
Caution: Do not insert profiles generated in role maintenance directly
into the user master using transaction SU01. A user master comparison
deletes all profiles that are not linked to the user master record through the
corresponding roles.
176
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
Exercise 12: Working with Roles
Exercise Objectives
After completing this exercise, you will be able to:
•
Create, copy, and modify roles and assign them to users
Business Example
Use the same scenario as for the last lesson.
Task 1: Copy a Role Template
Copy a role template and assign a user to it.
1.
Select the delivered single role SAP_BC_ENDUSER and copy this completely
to your own role BC_ENDUSER.
2.
Check the transactions assigned for the user menu with this role.
3.
Check the authorizations of the role, and maintain open authorizations if
necessary.
4.
Assign the role to the user ADMIN<##>.
5.
Perform a user comparison.
Task 2: Create Your Own Role (Optional)
Create your own role.
1.
Assign the name MONITORING<##> to the role.
2.
Select transactions SM50, SM51, SM04, and PFUD for the user menu.
3.
Check the authorizations of the role, and maintain open authorizations if
necessary.
4.
Assign the role to the user ADMIN<##>.
5.
Perform a user comparison.
Task 3: Assign a Role with Transaction SU01
Assign a role to user in transaction SU01.
1.
2005/Q2
Check in the user master record ADMIN<##> which roles and profiles are
assigned.
Continued on next page
© 2005 SAP AG. All rights reserved.
177
Unit 6: Basics of User Administration
2.
ADM100
Assign the role ZPFUD to the user ADMIN<##> using transaction SU01. Note
that you are making changes in the user master record.
Task 4: Check User
Check the user ADMIN<##>.
1.
178
Log on to the SAP System as user ADMIN<##>, then check if the user can
execute the transactions you assigned.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
Solution 12: Working with Roles
Task 1: Copy a Role Template
Copy a role template and assign a user to it.
1.
Select the delivered single role SAP_BC_ENDUSER and copy this completely
to your own role BC_ENDUSER.
a)
2.
Check the transactions assigned for the user menu with this role.
a)
3.
Choose the Change role button on the initial screen of transaction PFCG
for the role BC_ENDUSER. Switch to the Menu tab page. Switch to the
display of the transaction codes (choose the magnifying glass) and open the
Functions from Basis folder.
Check the authorizations of the role, and maintain open authorizations if
necessary.
a)
4.
Start transaction PFCG. Place the cursor on the input field for roles. Use the
F4 help to select the delivered single role SAP_BC_ENDUSER. Choose
the Copy Role button. In the dialog box that appears, enter BC_ENDUSER
in the To role field and choose Copy All.
Choose the Authorizations tab page and then choose Change Authorization
Data. Check the authorizations for the role and maintain open
authorizations if necessary, by, for example, choosing the yellow traffic
light icon and confirming the system query as to whether full authorization
should be assigned with Execute. Save your profile settings and confirm
the dialog box by choosing Execute. Choose Generate. Leave the Change
Roles: Authorizations screen by choosing Back.
Assign the role to the user ADMIN<##>.
a)
Choose the User tab page and enter ADMIN<##> in the User ID field.
If user ADMIN<##> does not exist, create a user with this name in
transaction SU01 in a new session.
5.
Perform a user comparison.
a)
Choose User Comparison and then choose Complete comparison.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
179
Unit 6: Basics of User Administration
ADM100
Task 2: Create Your Own Role (Optional)
Create your own role.
1.
Assign the name MONITORING<##> to the role.
a)
2.
Select transactions SM50, SM51, SM04, and PFUD for the user menu.
a)
3.
Choose the Authorizations tab page and then choose Change Authorization
Data. Enter the value 01 in the From Value column for the Plan Version
and save this value. Check the authorizations for the role and maintain
open authorizations if necessary, by, for example, clicking the yellow traffic
light icon and confirming the system query as to whether full authorization
should be assigned with Execute. Choose Generate and confirm the query
by choosing Execute. Save and exit the Change Role: Authorizations
screen by choosing Back.
Assign the role to the user ADMIN<##>.
a)
5.
Choose the Menu tab page. Choose the Transaction button and enter
transactions SM50, SM51, SM04, and PFUD. Then choose Assign
Transactions.
Check the authorizations of the role, and maintain open authorizations if
necessary.
a)
4.
Start transaction PFCG. Enter the name MONITORING<##> in the input
field for roles and choose Create Role.
Choose the User tab page and enter ADMIN<##> in the User ID field.
Perform a user comparison.
a)
Choose User Comparison and then choose Complete comparison.
Task 3: Assign a Role with Transaction SU01
Assign a role to user in transaction SU01.
1.
Check in the user master record ADMIN<##> which roles and profiles are
assigned.
a)
Start transaction SU01. Enter the name ADMIN<##> in the User field, and
choose the Change button. Choose the Roles tab page and check whether
the role BC_ENDUSER is entered. Choose the Profiles tab page, and
check that the corresponding profile is entered.
Continued on next page
180
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Authorization Concept
2.
Assign the role ZPFUD to the user ADMIN<##> using transaction SU01. Note
that you are making changes in the user master record.
a)
Choose the Roles tab page and enter ZPFUD in the Role field and confirm
with ENTER. Save your entries.
Task 4: Check User
Check the user ADMIN<##>.
1.
Log on to the SAP System as user ADMIN<##>, then check if the user can
execute the transactions you assigned.
a)
2005/Q2
Log on to the SAP system with your ADMIN<##> user. Switch to the user
menu and run some of the assigned transactions.
© 2005 SAP AG. All rights reserved.
181
Unit 6: Basics of User Administration
ADM100
Lesson Summary
You should now be able to:
•
Copy, create, and maintain roles
•
Maintain the assignment of roles and users
182
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Login Parameters and User Info
Lesson: Login Parameters and User Info
Lesson Overview
In this lesson, you learn about important system parameters that are important for
user administration, for example, for logon behavior. You can use the information
system to obtain information about any incorrect logon attempts. Failed authorization
checks are analyzed with the system trace. This lesson will also address using central
directory services for maintaining user master record, for example, the address data
contained in the records.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Set system parameters for user logons
Locate authorization problems
Business Example
Users are having problems due to missing authorizations. The administrator can
analyze these using system tools.
Login Parameters
This lesson deals with authorizations in the SAP system from an administrative point
of view. Among other thing, the following questions are considered: Which system
settings can be used to influence logon behavior? How can errors and problems be
analyzed?
Figure 71: System Parameters for User Logons 1/2
2005/Q2
© 2005 SAP AG. All rights reserved.
183
Unit 6: Basics of User Administration
ADM100
You can set the minimum length for passwords with the parameter
login/min_password_lng. You specify the minimum number of digits,
letters, or special characters that must be included in passwords using
the parameters login/min_password_digits, login/min_password_letters, and
login/min_password_specials. The value range is 0 to 8.
The parameter login/password_expiration_time specifies the number of days after
which a user must set a new password. If the parameter is set to 0, the user does
not need to change his or her password.
There are general rules for passwords that cannot be deactivated. A password
•
•
•
•
•
Must be different from the last five passwords
Must be at least three characters long
Must not begin with “?”, “!”, or “ ”
Must not be pass
Must not begin with three identical characters
You can define additional password restrictions in table USR40.
The parameters login/password_max_new_valid and login/password_max_reset_valid
specify the length of time for which an initial password or a password reset by an
administrator is valid.
Caution: Parameters login/password_max_reset_valid and
login/password_max_new_valid may only be used as of SAP Web Application
Server 6.20 Support Package 38. See SAP Note 450452.
Figure 72: System Parameters for User Logons 2/2
184
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Login Parameters and User Info
You can set the number of failed logon attempts after which SAP GUI is terminated
using the parameter login/fails_to_session_end. If the user wants to try again, he
or she must restart SAP GUI.
You can set the number of failed logon attempts after which a user is locked in the
SAP system using the parameter login/fails_to_user_lock. The failed logon counter is
reset after a successful logon attempt. The users locked by failed logon attempts are
automatically unlocked by the system at midnight (server time). You can deactivate
this automatic unlocking with the parameter login/failed_user_auto_unlock= 0. The
administrator can unlock, lock, or assign a new password to users in user maintenance
(transaction SU01).
If the parameter login/disable_multi_gui_login is set to 1, a user cannot logon to
a client more than once. This can be desirable for system security reasons. If the
parameter is set to 1, the user has the following options when he or she logs on again:
Continue with this logon and end any other logons in the system or Terminate this
logon. Users to whom this should not apply should be specified in the parameter
login/multi_login_users, separated with commas, and with no spaces.
Determining User Information
Figure 73: Information System
You can call the Information System (transaction SUIM) in the SAP Menu by
choosing Tools → Administration → User Maintenance → Information System or in
user maintenance (transaction SU01) by choosing Information → Information System.
2005/Q2
© 2005 SAP AG. All rights reserved.
185
Unit 6: Basics of User Administration
ADM100
You can obtain an overview of user master records, authorizations, profiles, roles,
change dates, and so on using the information system.
You can display lists that answer very varied questions. For example:
•
•
•
•
Which users have been locked in the system by administrators or failed logon
attempts?
When did a user last log on to the system?
What changes were made in the authorization profile of a user?
In which roles is a certain transaction contained?
Figure 74: System Trace for Authorizations
You can display the last failed authorization check (transaction SU53) by choosing
System → Utilities → Display Authorization Check. The system displays the
most recently checked authorization object for which the authorization check was
unsuccessful with the checked values. All authorizations that the user has for this
authorization object also display. If a user authorization is displayed that contains
the checked values, the user has not logged on again since new authorizations were
assigned to him or her.
The system administrator can use transaction SU53 to check which authorizations
were missing for a user for the execution of his or her last (unsuccessful) action.
You can record authorization checks in your own and other sessions using the
system trace function Tools → Administration → Monitor → Traces → SAP System
Trace (transaction ST01). All checked authorization objects including the checked
values are recorded here. The system trace is suited to finding multiple missing
186
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Login Parameters and User Info
authorizations. The system trace is activated for the authorization check of a special
user who has all required authorizations for the actions to be checked. The actions are
performed with this special user. The trace records all authorization checks. These
can then be evaluated.
2005/Q2
© 2005 SAP AG. All rights reserved.
187
Unit 6: Basics of User Administration
ADM100
Lesson Summary
You should now be able to:
•
Set system parameters for user logons
•
Locate authorization problems
188
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Advanced User Administration Topics
Lesson: Appendix: Advanced User Administration Topics
Lesson Overview
In this lesson, you will obtain an overview of Central User Administration and
connections to directory services. These topics are dealt with in detail in SAP course
ADM102.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the concept of Central User Administration
Describe connection to directory services
Business Example
You want to structure the user administration in your company more efficiently by
centralizing it.
Central User Administration
Figure 75: Central User Administration
2005/Q2
© 2005 SAP AG. All rights reserved.
189
Unit 6: Basics of User Administration
ADM100
If you are operating multiple SAP systems with a number of clients, and identical
users are created a number of times in different clients, you can significantly reduce
your administrative effort for user administration using Central User Administration
(CUA). You can perform user maintenance centrally from one client with CUA. This
client is then described as the central system. The clients for which user administration
is performed from the central system are called child systems.
You can specify for every user which clients it can log on to. Using CUA does not
mean that all users can be used in all clients of the system landscape.
You can also specify which user data can only be maintained centrally and which data
can also be maintained locally. It is sometimes useful to allow data to be locally
maintained by the users or by an administrator. Local maintenance with distribution
to all other clients is also possible (for example, in the case of address data being
changed).
The user master data is exchanged using ALE. ALE stands for Application
Link Enabling, and is a technology for setting up and operating distributed SAP
applications. ALE allows the process-controlled exchange of business messages
between loosely connected SAP systems. Asynchronous processing of the
communication ensures that application operation is error-free.
Systems that you want to include in a CUA must have at least SAP Basis 4.5.
Figure 76: Which Data Can Be Distributed?
190
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Advanced User Administration Topics
The following data can be distributed using Central User Administration (CUA):
•
•
•
•
User master records: Addresses, logon data, user defaults, and user parameters
Users are assigned the associated single and composite roles and profiles for all
child systems. Using CUA has the advantage that you no longer need to log on
to each individual client to maintain these assignments locally.
Initial password: When users are newly created, an initial password is
transferred to the child systems. This can be changed in the usual way.
Lock status: In addition to the familiar lock reasons (failed logon attempts or
locked by an administrator) there is a new general lock. This takes effect in all
child systems in which the affected user is permitted and can be removed either
centrally or in an individual child system.
You can assign Single or composite roles and authorization profiles from the
central system. However, the authorization profiles are maintained locally rather
than centrally, since different system settings and release statuses require local
administration of authorization profiles.
Note: With central role maintenance, you can define the menu of a role in
an SAP system for a different target system. The authorization profiles are
always to be maintained in the target system. You can implement the CUA
and central role maintenance concepts together or independently.
Central User Administration is discussed in detail in SAP course ADM102 - SAP
Web AS Administration II.
2005/Q2
© 2005 SAP AG. All rights reserved.
191
Unit 6: Basics of User Administration
ADM100
Directory Services
Figure 77: Connection to Directory Services
Directory services allow various applications in an IT landscape to access shared
information at a central location. The information is stored on a central directory
server that the various systems of your IT landscape can access. In this way, the
directory server acts as an “IT address book” for information that is usually used in
common, such as personnel data (name, department, organization), user data, and
information about system resources and system services. You can use directory
services to maintain information in SAP systems for directory-compatible applications
(such as user administration or Business Workplace). The standardized Lightweight
Directory Access Protocol (LDAP) is usually used as the access protocol. Directory
services provide a central information and administration point and therefore simple
shared information usage between various applications. Your SAP system can
exchange data with directory services using the LDAP protocol. You specify the
synchronization direction for each field, that is, whether the SAP system overwrites
the data in the directory, or the directory overwrites the data in the SAP system.
192
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Advanced User Administration Topics
The SAP system can exchange data with directory services from various vendors.
The SAP system may require attributes that are not in the standard schemata of the
directories. SAP usually provides a schema extension for this purpose.
Note: As of SAP Web AS 6.10, SAP systems can easily connect to a directory
service. It was possible to connect to a directory service before SAP Web AS
6.10, although rather more effort was involved.
Hint: A connection to a directory service can extend a Central User
Administration. That is, these two concepts are in no way mutually exclusive,
but rather work together very well.
The topic of central directory services/LDAP is dealt with in detail in SAP course
ADM102 - SAP Web AS Administration II.
2005/Q2
© 2005 SAP AG. All rights reserved.
193
Unit 6: Basics of User Administration
ADM100
Lesson Summary
You should now be able to:
•
Describe the concept of Central User Administration
•
Describe connection to directory services
Related Information
•
SAP courses
–
194
ADM940 - SAP Authorization Concept
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
Create users
•
Copy, create, and maintain roles
•
Maintain the assignment of roles and users
•
Set system parameters for user logons
•
Locate authorization problems
•
Describe the concept of Central User Administration
•
Describe connection to directory services
Related Information
•
SAP courses
–
–
2005/Q2
ADM940 - SAP Authorization Concept
ADM102 - SAP Web AS Administration II
© 2005 SAP AG. All rights reserved.
195
Unit Summary
196
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
How are authorizations assigned to a user?
Choose the correct answer(s).
□
□
□
□
2.
A
B
C
D
Users are assigned authorizations using profiles.
Users are assigned authorizations using roles.
Users are assigned authorizations using user names.
Users are assigned authorizations using a Certification Authority.
The SAP authorization concept is a positive concept because ...
Choose the correct answer(s).
□
□
□
□
3.
A
B
C
D
Every user automatically receives all authorizations.
Authorizations must be explicitly assigned.
The range of features of the authorization check is so large.
The developers programmed it efficiently.
System parameters for the user logon are in the area
. To display
user's incorrect logon attempts, call the Information System with transaction
. The system trace function is called using transaction
.
Fill in the blanks to complete the sentence.
2005/Q2
© 2005 SAP AG. All rights reserved.
197
Test Your Knowledge
ADM100
Answers
1.
How are authorizations assigned to a user?
Answer: A, B
Authorizations are combined into profiles. The roles assigned to users contain
profiles with appropriate authorizations for the role. Authorizations are not
assigned using user names or a CA.
2.
The SAP authorization concept is a positive concept because ...
Answer: B
SAP uses a positive authorization concept. This means that everything that is
not explicitly allowed is automatically forbidden.
3.
System parameters for the user logon are in the area login. To display user's
incorrect logon attempts, call the Information System with transaction SUIM.
The system trace function is called using transaction ST01.
Answer: login, SUIM, ST01
User logon settings are implemented using the login/* parameter. The
Information System is called with transaction SUIM, the system trace function
with ST01.
198
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 7
Setting Up Remote Connections
Unit Overview
In this unit, you will learn about remote connections, also known as Remote Function
Calls (RFC). In addition to the different types of RFC, you will learn about the
technical setting up of connections of this type.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
Explain the principle of the Remote Function Call
List the different types of Remote Function Call
Set up an RFC connection
Monitor RFC connections
Unit Contents
Lesson: Fundamentals and Types of RFC ...................................... 200
Lesson: Setting Up RFC Connections ........................................... 205
Exercise 13: Set up Remote Connections .................................. 209
2005/Q2
© 2005 SAP AG. All rights reserved.
199
Unit 7: Setting Up Remote Connections
ADM100
Lesson: Fundamentals and Types of RFC
Lesson Overview
This lesson provides you with an overview of Remote Function Calls.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Explain the principle of the Remote Function Call
List the different types of Remote Function Call
Business Example
SAP systems can communicate with each other using Remote Function Calls. A
prerequisite for this is that the administrator has set up the relevant interface system.
RFC Fundamentals
Remote Function Calls have been used for many years as the technical interface with
which SAP and non-SAP systems are usually connected. It is irrelevant whether
the data exchange it to be synchronous or asynchronous, periodic or aperiodic, or
transactional. All conceivable variants are supported.
200
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals and Types of RFC
Figure 78: The RFC Interface
A Remote Function Call is a call of a function module that is running in a different
system to the calling program. You can also call a function module in the same system
as an RFC; however, RFCs are usually used when the calling and called function
modules are running in different systems.
In the SAP system, the RFC interface system provides this function. The RFC
interface system allows function calls between two SAP systems or between an SAP
system and an external (non-SAP) system.
RFC is an SAP interface protocol that is based on the Common Programming Interface
for Communication (CPI-C) and allows cross-host communication between programs.
This means that ABAP functions can be called from external applications and tools,
and that external applications can be called from the SAP system.
RFC means that the ABAP programmer does not have to write his or her own
communication routines. For an RFC call, the RFC interface
•
•
•
Converts all parameter data to the format required in the remote system
Calls the communication routines that are required to communicate with the
remote system
Handles errors that occur during the communication
The RFC interface is easy for the ABAP programmer to use. The processing steps for
calling external programs are integrated into the CALL FUNCTION command.
2005/Q2
© 2005 SAP AG. All rights reserved.
201
Unit 7: Setting Up Remote Connections
ADM100
Figure 79: RFC Connections
To call a function module on a remote system, you must define the remote system
as a destination in your calling system. You also require access authorization for
the remote system.
You can administer these remote connections in the calling system. To do this, call the
Display and Maintain RFC Destinations screen, either by choosing the menu path
Tools → Administration → Administration → Network → RFC Destinations or by
calling transaction SM59 directly. The connection types and all existing destinations
display in a tree structure on the initial screen. For details about all available
connection types, see the documentation.
There is a search function for destinations that have already been set up. To search for
a destination, choose Find and enter your selection. The system displays a list of all
matching entries. You can display all available information for each entry.
To change an existing RFC destination, choose the relevant RFC destination in the
menu tree and choose Change.
Overview: Types of RFC
Synchronous RFC (sRFC)
For communication between different systems and between SAP Web AS and
SAP GUI.
202
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals and Types of RFC
asynchronous RFC (aRFC)
For communication between different systems and for parallel processing of
selected tasks.
transactional RFC (tRFC)
A special form of asynchronous RFC. Transactional RFC ensures transaction-like
processing of processing steps that were originally autonomous.
queue(d) RFC (qRFC)
Queued RFC is an extension of tRFC. It also ensures that individual steps are
processed in sequence.
RFC is a superordinate term for various implementation variants. sRFC is the
synchronous call of function modules. This means that the client waits until the server
has completed its processing. In an SAP system, an RFC can also be performed
asynchronously in another work process. This variant is called aRFC.
There is also tRFC, the transactional Remote Function Call. Transactional RFC
is asynchronous and ensures that data that is sent more than once due to network
problems, can be recognized at the server side, by assigning a Transaction Identifier
(TID). This allows you to prevent data being processed more than once, leading
to erroneous information in the application. Due to the asynchronous processing,
however, parameters can only be transferred from the client to the server in this case.
Returning information or status information directly is not possible.
qRFC with Send Queue is an extension of tRFC. It creates a layer between
applications and the tRFC and only allows the tRFC to transfer a Logical Unit of Work
(LUW) to the target server when its predecessors are no longer in the associated wait
queues. After a qRFC LUW is executed, the qRFC manager automatically processes
the next waiting qRFC LUW in accordance with the sequence in the wait queue.
2005/Q2
© 2005 SAP AG. All rights reserved.
203
Unit 7: Setting Up Remote Connections
ADM100
Lesson Summary
You should now be able to:
•
Explain the principle of the Remote Function Call
•
List the different types of Remote Function Call
204
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting Up RFC Connections
Lesson: Setting Up RFC Connections
Lesson Overview
In this lesson, you will learn how to set up a remote connection.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Set up an RFC connection
Monitor RFC connections
Business Example
Functions from different SAP systems must be linked with each other in the context of
an e-commerce scenario, so that, for example, additional processing is performed on
posting documents in another system.
Remote Connections
To create a new RFC destination, choose the Create button in transaction SM59 (Tools
→ Administration → Administration → Network → RFC Destinations). The system
displays a new screen with empty fields that you must fill out.
2005/Q2
© 2005 SAP AG. All rights reserved.
205
Unit 7: Setting Up Remote Connections
ADM100
Figure 80: Setting Up an RFC Connection
The system opens the dialog for creating a new RFC destination. Enter a name for the
destination, the connection type 3, and a short description. Choose Save. The system
stores your entries and switches to the technical settings screen.
Enter the target host and the system number of the system and choose Save
(Control+S).
For a quicker logon, you can specify a client, user name, and password for logon to
the target system in the Logon/Security tab page. Do not use your own user data here,
but rather general user data, as every user (with the appropriate RFC authorizations)
can use the RFC destination that you create.
For security reasons, you should leave these fields empty, or enter a user of the
type Communication with very specific (that is, adjusted to the requirements)
authorizations. In the first case, the system displays an input prompt for logon when
you later create a connection; in the second case, dialog logons to the system are not
possible, although programs can use the connection to communicate.
206
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting Up RFC Connections
Figure 81: Testing RFC Connections
You have two options for testing a destination:
•
•
2005/Q2
You can attempt to log on to the remote system. To do this, choose Remote
Login. A new session opens for the remote system. Enter the client, your user
name, and your password. If you have stored a dialog user with password in the
connection, a dialog logon is performed. If you have stored a communication
user, you can check that the specified password is correct with the function Test
→ Authorization in transaction SM59.
With a connection test (Test Connection button), the system attempts to create a
connection to the target system and displays a table with response times. If an
error message appears, check your settings.
© 2005 SAP AG. All rights reserved.
207
Unit 7: Setting Up Remote Connections
ADM100
208
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Setting Up RFC Connections
Exercise 13: Set up Remote Connections
Exercise Objectives
After completing this exercise, you will be able to:
•
Create and monitor a remote connection
Business Example
As an administrator, you are to set up remote connections to other systems, which are
then to be used, for example, in the context of an ALE integrated system.
Task 1: Create the First Remote Connection
Set up a remote connection.
1.
You are to set up a remote connection to the second system on your server,
to client 100.
The group that is using the DEV system sets up a connection to the QAS system.
The group that is using the QAS system sets up a connection to the DEV system.
Give your connection the name <SID>_100_DATA, where SID is the system
ID of your partner system.
To do this, get the details of a user, Monitor##, with password on the target
system from your partner group. Alternatively, use the user Monitor with the
password monitor.
Result
You have created an RFC connection.
Task 2: Create the Second Remote Connection
Set up another remote connection.
1.
You are to set up a remote connection to the second system on your server,
to client 100.
The group that is using the DEV system sets up a connection to the QAS system.
The group that is using the QAS system sets up a connection to the DEV system.
Give your connection the name <SID>_100_DATA, where SID is the system
ID of your partner system.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
209
Unit 7: Setting Up Remote Connections
ADM100
Do not save any user details for the target system for this connection.
Result
You have created an RFC connection.
Task 3: Test the Remote Connections
Test the remote connections that you have created.
1.
Test the connections <SID>_100_DATA and <SID>_100_ANALYSIS.
2.
Attempt to log on to the remote system. Use the function Test → Authorization.
Result
The RFC connections that you have created work correctly and can be used
later for central system monitoring.
Task 4: Use Load Balancing (Optional)
Use the load balancing for an RFC connection.
1.
Create an additional RFC connection to your partner group's system. Call this
connection <SID>_GROUP. Use the option for load balancing, by logging
on using a logon group, for this connection. To do this, you require the name
of the logon group that your partner group set. Alternatively, you can use the
default group SPACE.
Result
You can now successfully set up an RFC connection using load balancing.
210
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting Up RFC Connections
Solution 13: Set up Remote Connections
Task 1: Create the First Remote Connection
Set up a remote connection.
1.
You are to set up a remote connection to the second system on your server,
to client 100.
The group that is using the DEV system sets up a connection to the QAS system.
The group that is using the QAS system sets up a connection to the DEV system.
Give your connection the name <SID>_100_DATA, where SID is the system
ID of your partner system.
To do this, get the details of a user, Monitor##, with password on the target
system from your partner group. Alternatively, use the user Monitor with the
password monitor.
a)
To set up a remote connection, switch to the Display and Maintain RFC
Destinations window. To do this, choose Administration → Administration
→ Network → RFC Destination (transaction SM59) and choose Create.
The system opens the dialog for creating a new RFC destination. Enter
the following:
Field
Entry
RFC Destination
<SID>_100_DATA, where you use the SID of
your partner system
Connection Type
3
Description 1
Connection for central monitoring, to collect data
Choose Save. The system stores your entries and the technical settings
screen appears.
Field
Entry
Target Host
HOST, choose the server on which your partner
system is running
System Number
00 or 10, depending on the partner system SID
Choose Save (CTRL+S).
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
211
Unit 7: Setting Up Remote Connections
ADM100
Store the following data on the Logon/Security tab page.
Field
Entry
Client
100
User
Monitor##, created by your partner group, or
Monitor
Password
<Password>, to be obtained from your partner group,
or monitor
Save your entries.
Result
You have created an RFC connection.
Task 2: Create the Second Remote Connection
Set up another remote connection.
1.
You are to set up a remote connection to the second system on your server,
to client 100.
The group that is using the DEV system sets up a connection to the QAS system.
The group that is using the QAS system sets up a connection to the DEV system.
Give your connection the name <SID>_100_DATA, where SID is the system
ID of your partner system.
Continued on next page
212
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting Up RFC Connections
Do not save any user details for the target system for this connection.
a)
To set up a remote connection, switch to the window Display and Maintain
RFC Destinations. To do this, choose Administration → Administration →
Network → RFC Destination (transaction SM59) and choose Create.
The system opens the dialog for creating a new RFC destination. Enter
the following:
Field
Entry
RFC Destination
<SID>_100_ANALYSIS, where you use the SID
of your partner system
Connection Type
3
Description 1
Connection for central monitoring, to analyze
problems
Choose Save. The system stores your entries and the technical settings
screen appears.
Field
Entry
Target Host
HOST, choose the server on which your partner
system is running
System Number
00 or 10, depending on the partner system SID
Choose Save (CTRL+S).
Store the following data on the Logon/Security tab page.
Field
Entry
Client
<blank>, do not enter anything here
User
<blank>, do not enter anything here
Password
<blank>, do not enter anything here
Save your entries.
Result
You have created an RFC connection.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
213
Unit 7: Setting Up Remote Connections
ADM100
Task 3: Test the Remote Connections
Test the remote connections that you have created.
1.
Test the connections <SID>_100_DATA and <SID>_100_ANALYSIS.
a)
2.
Choose the Test Connection button for the connections <SID>_100_DATA
and <SID>_100_ANALYSIS. The system attempts to create a connection
to the remote system, and, if the connection is correctly set up and the
target system is accessible, displays a list of response times.
Attempt to log on to the remote system. Use the function Test → Authorization.
a)
Choose the Remote Login button. No logon is performed for the connection
<SID>_100_DATA, since the user that you have specified is not a
dialog-capable user in the remote client. Use the menu to call the function
Test → Authorization. If you have stored the correct logon data, this test is
performed without an error message.
Choose the Remote Login button. No automatic logon is performed for the
connection <SID>_100_ANALYSIS, since you have not stored any
logon data. If you have valid logon data (such as one of the ADM100-##
users), you can enter this data (possibly still with the password init) and
logon successfully.
Result
The RFC connections that you have created work correctly and can be used
later for central system monitoring.
Continued on next page
214
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Setting Up RFC Connections
Task 4: Use Load Balancing (Optional)
Use the load balancing for an RFC connection.
1.
Create an additional RFC connection to your partner group's system. Call this
connection <SID>_GROUP. Use the option for load balancing, by logging
on using a logon group, for this connection. To do this, you require the name
of the logon group that your partner group set. Alternatively, you can use the
default group SPACE.
a)
Call the maintenance transaction for RFC connections (Tools →
Administration → Administration → Network → RFC Destinations,
transaction SM59).
Choose Create. Enter the following values:
•
•
•
•
•
•
•
•
RFC Destination: <SID>_GROUP (replace <SID> with the <SID>
of your partner group's system).
Connection type: 3.
Description: Any documentation.
Choose Enter.
Select the radio button Load distrib.: Yes.
Target host: The host of your partner group.
Choose Enter.
Group: Logon group that your partner group set up or the default
group SPACE.
On the Logon/Security tab page, enter the logon information that you
received from your partner group.
Choose Save.
Result
You can now successfully set up an RFC connection using load balancing.
2005/Q2
© 2005 SAP AG. All rights reserved.
215
Unit 7: Setting Up Remote Connections
ADM100
Lesson Summary
You should now be able to:
•
Set up an RFC connection
•
Monitor RFC connections
216
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
Explain the principle of the Remote Function Call
•
List the different types of Remote Function Call
•
Set up an RFC connection
•
Monitor RFC connections
2005/Q2
© 2005 SAP AG. All rights reserved.
217
Unit Summary
218
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
What Remote Function Call procedures does an SAP system provide?
Choose the correct answer(s).
□
□
□
□
□
□
A
B
C
D
E
F
synchronous RFC
reflexive RFC
looped RFC
transactional RFC
direct RFC
queued RFC
2.
What RFC variant can you use to process work steps in parallel?
3.
To connect two SAP systems by RFC, you require an
in each system (this automatically
exists) and a defined
from one system to the
other.
Fill in the blanks to complete the sentence.
2005/Q2
© 2005 SAP AG. All rights reserved.
219
Test Your Knowledge
ADM100
Answers
1.
What Remote Function Call procedures does an SAP system provide?
Answer: A, D, F
In addition to the three listed in the exercise (synchronous, transactional, and
queued RFC), there is also asynchronous RFC.
2.
What RFC variant can you use to process work steps in parallel?
Answer: You can use asynchronous RFC to process program steps in parallel, as
long as there are work processes available in the system.
3.
To connect two SAP systems by RFC, you require an RFC interface in each
system (this automatically exists) and a defined RFC connection from one
system to the other.
Answer: RFC interface, RFC connection
The basic requirement is the RFC interface, which is in the protocol stack of
every SAP system. You must also set up a connection from the calling system to
the called system (transaction SM59).
220
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 8
Introduction to System Security
Unit Overview
This unit presents a number of aspects of system security. Familiar concepts of users
administration will be briefly repeated with special consideration given to the security
aspects. Approaches for securing data exchange, such as SNC, SSL, and SSF will then
be introduced. Topics such as SAProuter and digital signatures will complete the unit.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
Evaluate basic security aspects of an SAP system
List system parameters that affect security settings in clients or in the system
List implementation areas of Secure Network Communication (SNC), Secure
Socket Layer (SSL), and Secure Store and Forward (SSF)
Describe SAProuter in detail
Describe a central administration server
Unit Contents
Lesson: Security in the SAP Environment....................................... 222
2005/Q2
© 2005 SAP AG. All rights reserved.
221
Unit 8: Introduction to System Security
ADM100
Lesson: Security in the SAP Environment
Lesson Overview
Sensitive business data should always be exchanged using only encrypted data lines.
In this lesson, you will learn about various security measures for an SAP system.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
•
•
Evaluate basic security aspects of an SAP system
List system parameters that affect security settings in clients or in the system
List implementation areas of Secure Network Communication (SNC), Secure
Socket Layer (SSL), and Secure Store and Forward (SSF)
Describe SAProuter in detail
Describe a central administration server
Business Example
You are to implement a security concept in your company that is to protect your
SAP systems against unauthorized accesses. You are now engaged in initial, basic
deliberations.
Clients and Superusers
Encryption mechanisms, system-side security settings, and SAProuter software are
some of the components that support you in implementing your security concept.
However, the best security concept for secure data transfer is put in question if
superusers still have default passwords in your SAP system.
222
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Security in the SAP Environment
Figure 82: Users and Clients
Note: Some of these users (SAP* and DDIC in client 000) may receive new
passwords during the system installation. Consider the passwords of the other
listed users all the more carefully.
Clients 000 and 066 are part of a standard SAP system.
There are two special users in client 000:
•
•
SAP* for initial access to the system
DDIC for working with the Transport Management System (TMS)
To protect SAP* and DDIC against unwanted access, you should change the initial
passwords.
Client 066 is the EarlyWatch client. You should also change the initial password for
the EarlyWatch user. This user does not have any critical authorizations.
If user SAP* exists in a client, a mechanism coded in the kernel allows you to logon
with SAP* and the password pass.
Caution: This mechanism also applies if the proper SAP* user is, for
example, deleted from a client using database methods. That is: Access to the
database means access to the SAP system. This mechanism can be deactivated
using the profile parameter login/no_automatic_user_sapstar. However, it is
then not possible to log on to a newly created client, for example to perform a
client copy. See SAP Note 68048.
To check the initial passwords, you can also call report RSUSR003.
2005/Q2
© 2005 SAP AG. All rights reserved.
223
Unit 8: Introduction to System Security
ADM100
Encrypted Data Transfer: SNC
Figure 83: Secure Network Communication (SNC)
SNC is a software layer in the SAP system architecture that provides an interface to
an external security product. You can increase the security of your SAP system with
SNC by implementing additional security functions that are not directly provided by
SAP systems (such as the use of smart cards for user authentication).
SNC provides security at application level. This means that a secure connection is
guaranteed between the components of an SAP system (for example, between the SAP
GUI and the SAP application server, irrespective of the communication connection
or the transport medium. You therefore have access to a secure network connection
between two communication partners secured with SNC.
224
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Security in the SAP Environment
There are three different protection levels for communication connections secured
with SNC:
•
•
•
Authentication only: With authentication, only the identity of the
communication partner is checked. This is the lowest protection level when
using SNC. (There is no actual data security.)
Integrity protection: If you use the integrity protection, the system recognizes
changes to the data that have been made during the transfer between the sender
and the recipient.
Confidentiality protection: For the confidentiality protection, the transferred
messages are encrypted, meaning that eavesdropping is pointless. This is the
highest SNC protection level. This protection level also includes the integrity
protection and authentication.
Figure 84: Secure Network Communication (SNC): Logon
The steps illustrated in the figure mean the following:
1.
2.
3.
4.
The user logs on to a security product (such as Secude) using Single Sign-On.
When the user then logs on to involved systems (such as SAP R/3), he or she is
not prompted to enter a user name and password.
Instead, the system communicates with the security product.
The logon string is resolved to the user master record using the Access Control
List (ACL), allowing the user to access the system.
The two components of the security product exchange information using SNC.
2005/Q2
© 2005 SAP AG. All rights reserved.
225
Unit 8: Introduction to System Security
ADM100
In some countries, the use of cryptography is legally controlled. If you use SNC, you
should regularly inform yourself about the effects of these laws on your applications,
and ensure that you are aware of all further developments.
Encrypted Data Transfer: HTTPS
Figure 85: Secure Socket Layer (SSL): ICM and HTTPS
Secure Network Communication (SNC) allows you to encrypt the DIAG and RFC
protocols (see figures about SNC). Secure Sockets Layer (SSL) works in exactly the
same way for the HTTP protocol. This creates an HTTPS (“S” for secure) protocol
from the HTTP protocol. In this way, it is possible to exchange confidential data,
for example over the Internet.
Among other places, SAP uses SSL:
•
•
226
For direct communication between the SAP Web AS and the Internet. In this
case, the SAP Web AS speaks in HTTP. This is possible with the Internet
Communication Manager (ICM) component, standard as of SAP Web AS 6.10.
For communication with the Internet using an SAP Internet Transaction Server
(SAP ITS). In this case, the encryption of the HTTP protocol is performed at the
Web server, which is attached to the WGate of the SAP ITS.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Security in the SAP Environment
Encrypted Data Storage: SSF
Figure 86: Secure Store and Forward (SSF)
SSF ensures that SAP data and documents are secure during and beyond dialog
transactions. This is the case if
•
•
•
•
Data leaves the system (electronic orders, invoices, information)
Data is stored on unsecured media (external database, diskettes, archive)
Data is transferred using unsecured networks (Internet)
Data security relates to people and individuals (digital signatures, personal data)
Aims are therefore:
•
•
•
•
Data security
Security of personal data
Authentication
Non-reproducibility
This is achieved using digital signatures (see next figure) and digital envelopes.
Package Key Cryption Standard Number 7 (PCKS#7) is used as the standard format.
2005/Q2
© 2005 SAP AG. All rights reserved.
227
Unit 8: Introduction to System Security
ADM100
Digital Signatures and Envelopes
Figure 87: Digital Signatures and Envelopes
A Certification Authority (CA) issues a certificate and digitizes it. This certificate
contains, among other things, the name of the holder, the name of the issuer, a validity
period, and the public key. The certificate can be passed on as desired.
There is a private key that matches the public key, which only the holder may know.
The private key cannot be calculated from the public key.
People that do not know each other directly (for example, in the case of a query over
the Internet) can communicate authentically with each other with the help of the CA.
SAP uses standard technology for the implementation of digital signatures. Digitally
signed documents are created as PKCS#7 packages.
Possible applications: Orders (B2C, B2B), applications (Public Sector), cross-system
processes, ...
ABAP interface for digital signatures: Secure Store and Forward (SSF).
Signatures can by made by application servers or by users with the SAP GUI or in a
Browser.
For more information, see the SAP Service Marketplace with the Quick Link /security.
228
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Security in the SAP Environment
SAProuter
Figure 88: SAProuter
SAProuter is an SAP program for forwarding SAP system connections through
firewalls. The SAProuter extends the firewall, but does not replace it. SAP
recommends that you use SAProuter together with a firewall.
Caution: Without other security measures (firewall), a SAProuter does not
protect your SAP system network.
Hint: You must use a SAProuter for the SAP Remote Services (SAPNet - R/3
Frontend, Remote Consulting, possibly also Early Watch and other services).
2005/Q2
© 2005 SAP AG. All rights reserved.
229
Unit 8: Introduction to System Security
ADM100
You can also use SAProuter to
•
•
•
•
Control and log connections to your SAP system
Create an indirect connection, if the programs involved in the connection cannot
be reached directly due to the network configuration
Resolve address conflicts when using unregistered IP addresses
Improve network security by:
–
•
Protecting your SAProuter with a password against unauthorized external
accesses
–
Only allowing access from certain SAProuters
–
Only permitting the user of secure connections from a securely
authenticated partner (SNC)
Improve performance and stability by reducing the SAP system workload within
a LAN during communication with a WAN
If you use SAProuter, you only need to open one port on the firewall for a connection
with the port on the server on which SAProuter is running. All SAP GUI, SAPlpd, and
RFC connections must pass this port (default 3299). For more detailed information
about the use of SAProuter, see SAP Note 30289: SAProuter Documentation.
SAProuter Strings
SAProuter strings are built up in a similar way to the SAP GUI connect strings. The
host that is to be addressed next is specified with /H/<HOST>. For example:
/H/twdf000
This part of the router string can (in a simple scenario) be extended with two optional
extensions.
/S/<PORT> and /P/<Password>. The default value for the port is 3299 and for
the password < >, that is, no password is required.
You can repeat these three values after each other as often as desired, as in this
example:
/H/CSRV001/H/CSAPRT/S/8057/P/Secret/H/SAPSERVX/H/OSS/S/3282/P/SAP_Cust
230
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Security in the SAP Environment
In this (fictitious) example, a connection is created through a server CSRV001 to
a SAProuter on the server CSAPRT, which listens at port 8057 and only accepts
connections with the password Secret. A server at SAP (without a password
and using the standard port) is then used to address another server, OSS, at a
password-protected port (please note: the details really are fictitious).
Note: For more information and more complex connection options, see the
documentation for the SAProuter.
2005/Q2
© 2005 SAP AG. All rights reserved.
231
Unit 8: Introduction to System Security
ADM100
Lesson Summary
You should now be able to:
•
Evaluate basic security aspects of an SAP system
•
List system parameters that affect security settings in clients or in the system
•
List implementation areas of Secure Network Communication (SNC), Secure
Socket Layer (SSL), and Secure Store and Forward (SSF)
•
Describe SAProuter in detail
•
Describe a central administration server
Related Information
•
SAP courses
–
–
232
ADM950 - Secure SAP System Management
ADM960 - Security in SAP System Environments
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
Evaluate basic security aspects of an SAP system
•
List system parameters that affect security settings in clients or in the system
•
List implementation areas of Secure Network Communication (SNC), Secure
Socket Layer (SSL), and Secure Store and Forward (SSF)
•
Describe SAProuter in detail
•
Describe a central administration server
2005/Q2
© 2005 SAP AG. All rights reserved.
233
Unit Summary
234
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
Evaluate the following statements.
Choose the correct answer(s).
□
□
□
□
2005/Q2
A
B
C
D
SAP* and DDIC are SAP users with no critical authorizations.
By default, user DDIC exists only in client 000.
HTTP, encrypted using SSL, is called HTTPS.
The ICM can accept encrypted connections.
© 2005 SAP AG. All rights reserved.
235
Test Your Knowledge
ADM100
Answers
1.
Evaluate the following statements.
Answer: B, C, D
SAP* and DDIC certainly do have critical authorizations. The other statements
are true.
236
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 9
Working with the Transport System
Unit Overview
This unit introduces the basics of software logistics. The following points will be deal
with: the data structure of SAP systems, the three-system landscape recommended
by SAP, and transports.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
Describe the data Structure of an SAP system
List the advantages of and requirement for a three-system landscape
Create and release transport requests
Describe the architecture of the SAP transport system
Import transport requests
Unit Contents
Lesson: Data Structure of SAP Systems and System Landscapes.......... 238
Lesson: Performing and Checking Transports .................................. 245
Exercise 14: System Landscapes and Transport Requests .............. 255
2005/Q2
© 2005 SAP AG. All rights reserved.
237
Unit 9: Working with the Transport System
ADM100
Lesson: Data Structure of SAP Systems and System
Landscapes
Lesson Overview
This lesson discusses the data structure of an SAP system. The lesson also introduces
terms such as client, object repository, and cross-client Customizing and describes
three ways to change and create repository objects.
The lesson also discusses the advantages and requirement for a three-system landscape.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the data Structure of an SAP system
List the advantages of and requirement for a three-system landscape
Business Example
SAP software is to be adjusted to company-specific requirements in your company.
How are programs exchanged between SAP systems? As little postprocessing as
possible should be required in the case of a subsequent system upgrade.
Data Structure of the SAP System
Knowing the data structure of an SAP system is equally important for users,
developers, and administrators to understand the way that an SAP system functions.
238
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Data Structure of SAP Systems and System Landscapes
Figure 89: Data Structure of an SAP System
SAP systems have a specific data structure. In addition to business settings
(Customizing) that are only relevant for certain clients of the SAP system, an SAP
system also always contains cross-application settings and objects - cross-client
Customizing and the repository.
The repository is the central store for all development objects of the ABAP
Workbench and is cross-client. The repository objects are stored in packages.
Packages are containers for semantically-linked development objects. They replace
development classes. A package consists of sub-packages and development objects
(programs, tables, screens, function modules, classes, and so on) that are developed
and transported together. Packages are characterized by the properties nesting,
interfaces, visibility and use accesses. Packages are created and managed with the
Package Builder (transaction SPAK). The recording and transport of object changes
are also controlled by the Change and Transport System (CTS) using assignment
to a package.
The settings of an SAP system are described as Customizing. The enterprise-neutral
and industry-specific business functions that are delivered are tailored to the specific
requirements of the enterprise in the Customizing process. Customizing is obligatory
both during the first installation and during an upgrade and is performed in the SAP
system using the Implementation Guide (IMG).
SAP systems differentiate between client-dependent and cross-client Customizing.
Cross-client Customizing includes the public holiday calendar, or settings for the
transport domains and system changeability.
2005/Q2
© 2005 SAP AG. All rights reserved.
239
Unit 9: Working with the Transport System
ADM100
Figure 90: Client
SAP systems are divided into business units, in clients. A client is a self-contained
unit in commercial, organizational, and technical terms in an SAP system and consists
of business settings (Customizing), its own master and transaction data, and its own
user data.
A client's data is described as client-dependent or client-specific data.
Client-dependent data types are closely interdependent. Thus, when application data is
entered, the system checks whether the data matches the client's Customizing settings.
If there are inconsistencies, the application data is rejected. Application data is
therefore only meaningful in business terms in the relevant Customizing environment.
Examples of client-dependent Customizing are company codes and business settings
such as plants, warehouses, and so on.
Client-dependent data is data that is only valid in that client. This includes, for
example, material master records, orders, and invoices.
User data and authorizations are also client-dependent.
Various client roles are used in an SAP system. A Customizing client is required for
the client-dependent Customizing in the development system. In test systems, a client
is created for test purposes (Test role); in production systems, a client is created for
productive work. You can use transaction SCC4 to assign the roles to the clients.
240
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Data Structure of SAP Systems and System Landscapes
Changing the Data Structure
Figure 91: Adjustments to the Data Structure
As well as client-specific and cross-client Customizing, you can make additional
adjustments to the data structure. You can make changes or enhancements in the
repository. These are not necessarily required to use an SAP system. Changes or
enhancements to the repository are possible in a variety of ways:
•
•
•
2005/Q2
Extension of the repository through customer developments. In the SAP
system, you can create your own repository objects such as tables, programs,
transactions, and so on. All customer developments are usually performed in the
customer name space; that is, all objects created by customers have names from
a specified namespace, and must begin with the letter “Y” or the letter “Z”. You
can, however, also request your own namespace that begins and ends with “/”
free of charge from SAP. This must be a maximum of eight characters, including
the “/”, such as “/Firm/”. All of the objects that you write then have a name
beginning with “/Firm”, such as “/Firm/GreatProgram”.
Adjusting the repository with customer enhancements. In this case, customer
objects are added to the repository. The SAP standard programs can be extended
with customer objects at specified points in the coding, called Customer Exits.
Modifications to the standard SAP system: Changes to SAP objects (programs,
table definitions) are described as modification. The repository delivered by
SAP is not only extended, but changed.
© 2005 SAP AG. All rights reserved.
241
Unit 9: Working with the Transport System
ADM100
Three-System Landscape
SAP's recommendation for a three-system landscape is based on the data structure
of an SAP system, in which the object repository only exists once. You must never
develop and work productively in the same SAP system.
Figure 92: The Three-System Landscape
As the repository objects are cross-client, SAP recommends that you do not develop
in a system at the same time as you are working in it productively, as this carries a
danger of possible data inconsistency. If you are making changes to the repository,
SAP recommends that you use at least two, but ideally three separate systems. One
system for development, a second system for tests and quality assurance, and a third
system in which you work productively: a system landscape of three systems.
A three-system landscape allows you to use the following, recommended procedure:
You develop your own programs and perform the required Customizing in the
development system. The Customizing settings that you make and all changes to the
repository (developments, corrections, modifications) are recorded in the development
system and then transported to the quality assurance (or test) system, and are checked
there without influencing production operation. All objects and settings imported into
the test system can then be transported to one or more production systems after a
successful test.
Different clients can be created for different purposes in one system. If you perform
client-dependent Customizing in a development system that you want to check before
transporting it to other systems, a test client in the development system can be useful.
242
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Data Structure of SAP Systems and System Landscapes
Clients with specified roles are usually created in each system: A development client
in the development system, a client for testing in the quality assurance system, and
a client for productive work in the production system. The clients should have an
identical ID, as far as possible, as the following rule applies during transporting:
Source client = Target client.
2005/Q2
© 2005 SAP AG. All rights reserved.
243
Unit 9: Working with the Transport System
ADM100
Lesson Summary
You should now be able to:
•
Describe the data Structure of an SAP system
•
List the advantages of and requirement for a three-system landscape
244
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
Lesson: Performing and Checking Transports
Lesson Overview
In this lesson, you will learn how to perform transports between SAP systems.
Differences between and similarities of workbench and Customizing requests will
be considered.
The lesson explains the export and import of transport requests.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Create and release transport requests
Describe the architecture of the SAP transport system
Import transport requests
Business Example
The changes that the developers make in the development system must be transported
to the quality assurance system for testing, and, after successful testing, to the
production system. Transporting change requests is part of the administrator's task
area.
Workbench Requests
Workbench and Customizing requests are both created with the Transport Organizer
(transaction SE09 or SE10). In the context of a request of this type, a project leader
defines development or Customizing tasks and assigns them to individual employees.
After the individual tasks are released, the request can also be released. After a
successful export, the request can be imported into the target system.
2005/Q2
© 2005 SAP AG. All rights reserved.
245
Unit 9: Working with the Transport System
ADM100
Figure 93: Structure of Workbench Requests
When a development project starts, the development project leader creates a change
request. In doing so, he or she assigns the team members to the change request. The
Transport Organizer (transaction SE09) assigns a number (<sid>K9<nnnnn>, such
as DEVK900050) to the change request. A request should contain objects that are
logically connected and can only be meaningfully executed together. That is, a request
allows you to transport and administer complete, meaningful, and self-contained
developments.
The Transport Organizer creates a task for every involved employee in the request. If
an employee assigns a repository object to the change request, the repository object
is logged in the task of that employee. In this way, all repository objects that an
employee edits during the development project are collected in the task.
When the development project is complete from the point of view of the employee,
he or she releases his or her task. This transfers the objects in the task to the change
request. Once all employees release their tasks, the development project leader can
release the change request and, in doing so, request the export. A change request
therefore combines repository objects that have been created or changed during
a development project.
246
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
Figure 94: Development, Release, and Transport of Repository Objects
If a repository object is edited and included in a change request by a developer, it is
exclusively reserved for processing by this change request. Changes to this object
can only be made by developers that also have a task in this change request. The
development or maintenance of development objects is locked for all other developers
that are not involved in the same change request until the change request is released.
These developers can only display the objects.
Every employee that is involved in the request that edits the object receives a
corresponding entry in the object list of his or her task. In this way, it is possible to
determine which employee actually edited the object.
The object locks are removed when the change request is released. The objects
can then be edited by all developers again. Changes to Customizing data are also
registered in the Transport Organizer, although in the case of Customizing, the tables
are only locked during the actual editing.
The Transport Organizer also ensures that the Repository objects are versioned,
allowing both comparisons and access to earlier versions. In this way, you can
document, and even recreate, the released states before and after a change request or
development project. A version is created when a repository object is changed and
when a change request is released.
2005/Q2
© 2005 SAP AG. All rights reserved.
247
Unit 9: Working with the Transport System
ADM100
Customizing Requests
Figure 95: Structure of Customizing Requests
When a Customizing project starts, the Customizing project administrator creates a
change request for Customizing objects in the Transport Organizer (transaction SE09).
The administrator assigns the employees involved to the Customizing request. The
Transport Organizer assigns a number (<sid>K9<nnnnn>, such as DEVK900055) to
the Customizing request. A Customizing request can only contain client-dependent
Customizing objects. Cross-client Customizing that is to be transported must be
recorded in a Workbench change request, since it is dealing with settings that apply
system-wide.
The Transport Organizer creates a subtask for every involved employee in the request.
If an employee assigns a Customizing object to the Customizing request, the object
is logged in the task of that employee. In this way, all Customizing objects that an
employee edits during the project are collected in the task.
When the Customizing is completed from the point of view of the employee, the
employee releases the subtask. This transfers the objects in the task to the Customizing
request. Once all employees have released their tasks, the Customizing project leader
can release the change request and therefore, export.
248
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
Figure 96: Execution, Release, and Transport of Customizing
The structure of Customizing projects is similar to the structure of development
projects. The involved employees in this case are the Customizing project
administrator, who creates and releases the Customizing requests, and the project team
members, who perform the Customizing and assign it to a Customizing request.
Changes to Customizing data are registered in the Transport Organizer, although
in the case of Customizing, the tables (or table entries) are only locked during the
actual editing.
Transports
The transport of objects is divided into Export and Import phases: Export from the
development system, import of the objects into other target systems, such as the test
system and production system.
2005/Q2
© 2005 SAP AG. All rights reserved.
249
Unit 9: Working with the Transport System
ADM100
Figure 97: Transports in a Three-System Landscape
After they have been released, the changed or newly created objects are stored in data
files in the central transport directory. The successful release and export is stored
in the transport log of a change request.
The import into the target system is usually not automatic, but is triggered by the
transport administrator in the Transport Management System (TMS). The import
logs can then be checked.
In technical terms, a copy of the data from the development system database is written
to the central transport directory during the export of the change request. During the
import, the change request stored in the central transport directory is copied into the
database of the target system.
The central transport directory is physically stored on a server in the system landscape
(the transport host), to which all systems in the system landscape must have access
using a share or mount. The profile parameter DIR_TRANS specifies for each system
where the transport directory to be used, which is called /usr/sap/trans, is stored.
Import
The transport administrator usually starts the import manually in the receiving systems
using the Transport Management System, which you can call with transaction STMS.
250
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
Figure 98: Working with the Import Queue
In the receiving system, you can see which change requests are queued for import into
the system in transaction STMS. From a technical point of view, in a three-system
landscape, the change request is flagged for import into the receiving system (quality
assurance system) during the export from the development system. You can view this
flagging of the change request for import into the receiving system in the Transport
Management System (transaction STMS) by choosing Overview → Imports. This
displays the import queue for the relevant systems. To display details about the
queues, choose Import Queue → Display.
There are a number of methods available to you in the TMS import queue for
importing requests into the target system. The most important import methods are
import all requests (import all) and Import Individual Requests (single import).
You can perform an import in dialog or schedule an import in the background with
any of the methods. The best import method for you to use depends on your system
landscape and your transport strategy.
2005/Q2
© 2005 SAP AG. All rights reserved.
251
Unit 9: Working with the Transport System
ADM100
Figure 99: import
With the import of single requests, you select and then import a single change request
in the queue.
With the import of all requests in the import queue, all requests are imported in the
sequence in which they were exported; that is, in the order in which they are in the
import queue. The import steps are performed successively for all of the requests.
In the SAP System, the transport administrator starts imports using transaction STMS
by displaying the import queue (Overview → Imports), selecting the system into
which he or she wants to import, and then choosing Import Queue → Display. After
you have decided on an import strategy, start the import either by choosing either the
Import all requests button, or Import request.
Technically, the operating system executable program tp is used for the export and
import. The import always uses the data files that were generated and stored in the
central transport directory /usr/sap/trans during the export.
252
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
Checking Transports
Figure 100: Checking Transports
During transporting, the transport steps performed in the various transport phases
are logged. You can use the Transport Organizer to control transports: On the right
side of the initial screen of the Transport Organizer, there is a list of your transports
and repairs.
By choosing the Transports button, you display a hierarchical display of your released
transports and their transport steps, structured by target systems.
You can identify the success or failure of the individual transport steps from the
colored labeling, the comment, and the return code. In the case of erroneous
transports, the transport log contains notes about the cause of the errors. By selecting
a transport step, you display its transport log.
All import steps are also logged during the import, which is performed by the transport
administrator in transaction STMS. In this case, it is also possible to display the
relevant information using the Transport Organizer.
For more information about the import, call the system log for the system to be
monitored by choosing Overview → Imports (or directly with the Import Overview
button) in transaction STMS. To do this, choose the system to be checked in the
import overview and display the system log by choosing Goto → TP System log
from the import queue. From here, you can perform additional error analysis using
other log files.
2005/Q2
© 2005 SAP AG. All rights reserved.
253
Unit 9: Working with the Transport System
ADM100
254
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Performing and Checking Transports
Exercise 14: System Landscapes and
Transport Requests
Exercise Objectives
After completing this exercise, you will be able to:
•
Create and release transport requests
•
Import transport requests
Business Example
The changes that the developers make in the development system must be transported
to the quality assurance system for testing, and, after successful testing, to the
production system. Transporting change requests is part of the administrator's task
area.
Task 1: The Transport Organizer
Work with the Transport Organizer.
Hint: You should log on to the DEV system with your user (such as
ADM100-##) and perform the tasks.
1.
Use the Transport Organizer in system DEV to create a change request with the
type Workbench Request. You can start the Transport Organizer by choosing
Tools → ABAP Workbench → Overview → Transport Organizer or with
transaction code SE09.
2.
Give your change request a meaningful short description and save it.
3.
Display the number of your request and the assigned tasks.
Task 2: Create a Repository Object
Create a repository object.
1.
In the DEV system, create a program with the Object Navigator (SE80).
2.
Assign the name Z_ Program_<##> to your program, where ## is your
group number.
3.
Assign the necessary attributes to the program: Type Executable program,
Status Test program, and Application Cross-application.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
255
Unit 9: Working with the Transport System
ADM100
4.
The system prompts you to assign your newly created program to a package.
Select the package ZADM100.
5.
The system prompts you to assign your newly created repository object to a
Workbench request. Under the Own Requests button, choose the change request
that you created in task 1, and confirm the selection.
6.
Edit the source code of the program and activate it.
Task 3: Release Request
Release the change request and the task.
1.
Check the assignment to your request in the Transport Organizer.
2.
Release your task (the program that you created) in the DEV system in the
Transport Organizer.
3.
Then release your change request.
Task 4: Import the Request
Import the request and check the logs.
1.
256
Import your change request into the system QAS and check the logs.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
Solution 14: System Landscapes and
Transport Requests
Task 1: The Transport Organizer
Work with the Transport Organizer.
Hint: You should log on to the DEV system with your user (such as
ADM100-##) and perform the tasks.
1.
Use the Transport Organizer in system DEV to create a change request with the
type Workbench Request. You can start the Transport Organizer by choosing
Tools → ABAP Workbench → Overview → Transport Organizer or with
transaction code SE09.
a)
2.
Give your change request a meaningful short description and save it.
a)
3.
On the initial screen, choose Create. On the next dialog screen, choose
Workbench request, and then confirm by choosing the green checkmark.
Enter a meaningful short description for your change request and save
it by choosing Save.
Display the number of your request and the assigned tasks.
a)
On the next screen, the system displays the (automatically generated)
number for your transport request (<sid>K9<nnnnn>) and the number(s) of
the assigned task(s).
Task 2: Create a Repository Object
Create a repository object.
1.
In the DEV system, create a program with the Object Navigator (SE80).
a)
You can call the Object Navigator by choosing Tools → ABAP Workbench
→ Overview → Object Navigator. On the initial screen of the Object
Navigator, choose Repository Browser and choose the entry Program in the
dropdown list.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
257
Unit 9: Working with the Transport System
2.
ADM100
Assign the name Z_ Program_<##> to your program, where ## is your
group number.
a)
Since your program does not yet exist, the system asks you if you want to
create it after you press ENTER. Confirm this with Yes.
In the dialog box that then appears, deselect the option With TOP INCL.,
and confirm by choosing Continue.
3.
Assign the necessary attributes to the program: Type Executable program,
Status Test program, and Application Cross-application.
a)
4.
The system prompts you to assign your newly created program to a package.
Select the package ZADM100.
a)
5.
Use the F4 help for the Package field to enter ZADM100, and choose Save.
The system prompts you to assign your newly created repository object to a
Workbench request. Under the Own Requests button, choose the change request
that you created in task 1, and confirm the selection.
a)
6.
Assign the necessary attributes to the program. For the Type field, select
the value Executable program, for the Status field, the value Test
program, and for the Application field, the value Cross-application.
Then choose Save.
The system prompts you to assign your newly created repository object to a
Workbench request. Under the Own Requests button, choose the change
request that you created in task 1, and confirm the selection.
Edit the source code of the program and activate it.
a)
In the navigation area, select the program name and choose the Display
<-> Change button.
In a new line below the existing source code, enter write 'A simple
program.'.. Note that the line must end with a period (.).
Finally, choose the Activate button.
Task 3: Release Request
Release the change request and the task.
1.
Check the assignment to your request in the Transport Organizer.
a)
Display all change requests that you created but that are not yet released
by choosing Display in transaction SE09. There is a task described as
Development/Correction under your change request.
Continued on next page
258
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing and Checking Transports
2.
Release your task (the program that you created) in the DEV system in the
Transport Organizer.
a)
3.
To release your task, switch to your not yet released change requests in the
Transport Organizer by choosing Display. Select the task to be released
(the program that you created is below it), and release this by choosing
Release Directly.
Then release your change request.
a)
To release the entire change request, select it and choose Release Directly.
Task 4: Import the Request
Import the request and check the logs.
1.
2005/Q2
Import your change request into the system QAS and check the logs.
a)
Call transaction STMS and call the import overview by choosing Overview
→ Imports. On the next screen, select the system (QAS), where you want
to import, and display the imports queue for the system by choosing
(Import Queue → Display). Now select your change request and start
the import by choosing Import Request. The change request is to be
imported with the predefined default values (immediately start, execute
asynchronously, and so on). If required, enter the target client (such as
100), and perform the import.
b)
To check the logs, call the Transport Organizer (transaction SE09) and
choose the Transports button on the Global Information tab page on the
right of the screen. The system now displays the change requests that you
have released and imported. You can display the logs by choosing the
Display Log button.
© 2005 SAP AG. All rights reserved.
259
Unit 9: Working with the Transport System
ADM100
Lesson Summary
You should now be able to:
•
Create and release transport requests
•
Describe the architecture of the SAP transport system
•
Import transport requests
260
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
Describe the data Structure of an SAP system
•
List the advantages of and requirement for a three-system landscape
•
Create and release transport requests
•
Describe the architecture of the SAP transport system
•
Import transport requests
Related Information
•
SAP courses
–
2005/Q2
ADM325 - Software Logistics
© 2005 SAP AG. All rights reserved.
261
Unit Summary
262
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
What elements are part of the data structure of an SAP system?
Choose the correct answer(s).
□
□
□
□
□
□
2.
A
B
C
D
E
F
Registry repository
Object repository
Client
Database server
Cross-Client Customizing
SAP Kernel
Decide which of the following statements are correct.
Choose the correct answer(s).
□
□
□
□
3.
A
B
C
D
Entering customer data requires a Customizing request.
A change request contains one or more tasks.
A task can always be assigned to only one developer.
Any Customizing requires a Customizing request.
Which statements are correct?
Choose the correct answer(s).
2005/Q2
□
A
□
B
□
□
C
D
The transport of objects is divided into Export, Storage, and Import
phases.
The import into the target system is performed automatically at
midnight Greenwich Mean Time.
The transport directory is specified by parameter DIR_TRANS.
When transporting, the following rule applies: The target client is the
same as the source client, unless otherwise specified.
© 2005 SAP AG. All rights reserved.
263
Test Your Knowledge
ADM100
Answers
1.
What elements are part of the data structure of an SAP system?
Answer: B, C, E
The object repository, cross-client Customizing, and the clients are part of the
data structure of an SAP system. The database structure is not part of the data
structure; rather, it contains it.
2.
Decide which of the following statements are correct.
Answer: B, C
Entering customer data is not part of Customizing and therefore does not
require a Customizing request. Only client-dependent Customizing requires a
Customizing request; cross-client Customizing, on the other hand, requires
a workbench request.
A change request contains one or more tasks, each of which are assigned to
only one developer.
3.
Which statements are correct?
Answer: C, D
The transport is divided into only two phases, Export and Import. The import
into the database of the target system is never performed automatically.
264
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 10
Support Packages, Plug-Ins, and
Add-Ons
Unit Overview
Basic terms such as Support Package and Industry Solution will be discussed in this
unit. The system tools with which you can “import” these software components into
the SAP system will also be addressed. You will be able to reinforce the knowledge
that you have gained using practical exercises.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
List the differences in principle between Support Packages, Plug-Ins, and
Add-Ons
Import Support Packages with transaction SPAM
Install and update Industry Solutions with transaction SAINT
Update transactions SPAM and SAINT
Describe how to use the SAP Note Assistant
Unit Contents
Lesson: Term Definition: Support Packages .................................... 266
Lesson: Importing Support Packages ............................................ 271
Exercise 15: Import Support Packages...................................... 287
Lesson: Updating the Tools........................................................ 292
Exercise 16: SPAM Update ................................................... 295
Lesson: Importing SAP Notes..................................................... 299
2005/Q2
© 2005 SAP AG. All rights reserved.
265
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Lesson: Term Definition: Support Packages
Lesson Overview
This lesson provides an introduction to the topics of Support Packages, Plug-Ins,
and Add-Ons.
Lesson Objectives
After completing this lesson, you will be able to:
•
List the differences in principle between Support Packages, Plug-Ins, and
Add-Ons
Business Example
After the installation of your SAP system, you want to import functional enhancements
into your system, and correct errors that may occur. SAP makes Support Packages
available for this purpose.
Support Packages and Industry Solutions
An SAP system consists of different software layers, also called software components.
All of these layers are regularly updated using Support Packages; that is, errors are
corrected and new functions are provided using Support Packages.
The SAP system should always be kept at the current correction status so that errors in
the standard release are preventatively removed.
In addition to the standard functions in an SAP system, additional functions are
sometimes required from an Industry Solution (IS).
266
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Term Definition: Support Packages
Figure 101: Which software components have Support Packages?
The following list contains the software components listed in the figure; each
component has its own release cycle. Industry Solutions, Plug-Ins, and Extension
Set are all Add-Ons.
Extension Set
These extensions of the functionally stabilized application components of SAP
ECC (the successor to SAP R/3 Enterprise System) are delivered as a complete
set. The Enterprise Set, release 1.10, was first delivered with SAP R/3 Enterprise
(4.7).
Industry Solution (IS)
Industry Solutions are the technical software realization of industry-specific
requirements. SAP strongly recommends against using multiple Industry
Solutions within one SAP system, since these modify the SAP system in different
ways. You can obtain approval from SAP for using two Industry Solutions
together in certain circumstances.
Plug-In (PI)
An SAP plug-in provides the interfaces between different components of an SAP
solution, such as between SAP CRM and SAP ECC.
Core Application (APPL)
This area contains software for all non-HR application components in SAP ECC.
Human Capital Management (HCM)
This area contains software for HCM applications in SAP ECC.
2005/Q2
© 2005 SAP AG. All rights reserved.
267
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Application Basis (ABA)
This is special software for the Application Basis.
BASIS
This is software for the basis area in the standard SAP system and in the SAP
Web Application Server.
Business Intelligence (BW)
This is software for the Business Intelligence area. This layer is integrated into
SAP Web AS from SAP Web AS 6.40.
Customer Relationship Management (CRM)
This is software for an SAP CRM system.
Note that it is not possible to run APPL/HCM and CRM or other main
components simultaneously on the same SAP Web Application Server (which
consists of ABA and BASIS layers).
What Is a Support Package?
A Support Package is a quantity of corrected SAP objects. Support Packages are
required to correct errors in the various components or to provide new functions or
legal changes. This is done by replacing some objects with corrected versions of
these objects.
268
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Term Definition: Support Packages
Each software component has a separate sequence of Support Packages. The
following list contains the technical names of a number of components and the
notation for their Support Packages:
•
•
•
COP (Component Package):
–
SAP_APPL (SAP APPL Support Package): SAPKH<rel><no>
–
SAP_BASIS (Basis Support Package): SAPKB<rel><no>
–
SAP_ABA (Application Basis SP): SAPKA<rel><no>
–
SAP_HR (SAP HR Support Package) : SAPKE<rel><no>
–
SAP_SCM (SCM Support Package): SAPKY<rel><no>
–
SAP_BW (BW Support Package): SAPKW<rel><no>
–
SAP_CRM (CRM Support Package): SAPKU<rel><no>
CRT (Conflict Resolution Transport): Solves conflicts between Support
Packages and Add-Ons (such as an Industry Solution); can also contain
corrections for the Add-On. Either for each individual Support Package or as
a collective CRT for a range of several Support Packages. SAPKI*, SAPKJ*,
SAPKP*, SAPKG*
PAT: Provides new functions for transactions SPAM and SAINT. There is only
one SPAM/SAINT update for each release, but in different versions. SAPKD<5
digit number>
The following no longer exist since SAP R/3 4.6: FFD: Final Delta Patch for First
Customer Shipment (FCS), HOT: Hot Package, LCP: Legal Change Patch for HR,
BWP: Business Information Warehouse Patch.
2005/Q2
© 2005 SAP AG. All rights reserved.
269
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Lesson Summary
You should now be able to:
•
List the differences in principle between Support Packages, Plug-Ins, and
Add-Ons
270
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Lesson: Importing Support Packages
Lesson Overview
In this lesson, you will learn about the tools that import Support Packages into your
systems. These tools are also used to implement upgrades and installations of Industry
Solutions.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Import Support Packages with transaction SPAM
Install and update Industry Solutions with transaction SAINT
Business Example
Importing Support Packages is a standard task of every SAP administrator. The new
versions of SAP objects in the Support Packages stabilize and extend the functions of
your SAP system.
2005/Q2
© 2005 SAP AG. All rights reserved.
271
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
SPAM and SAINT
Figure 102: SPAM and SAINT
Transaction SPAM allows you to import Support Packages. This applies for Support
Packages for the standard SAP system, for Industry Solutions, and for CRTs.
It is also only possible to import a SPAM/SAINT update using transaction SPAM.
Transaction SAINT allows you to install and upgrade an Add-On, such as an Industry
Solution, from the SAP system. To install or upgrade an Add-On, it can be necessary
to import Add-On Support Packages and CRTs. Transaction SAINT deals with this.
SPAM: Prerequisites and Settings
The SAP system supports you when importing Support Packages. Specific
transactions are used, depending on the software to be updated; that is, whether it is
the standard SAP system or Add-Ons and Industry Solutions.
In terms of transaction SAINT, an Add-On is everything that does not belong to the
standard SAP system. This includes, for example, Industry Solutions, Software
Development Projects (SDPs), and Plug-Ins.
272
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
You must take the following prerequisites and settings into account to import Support
Packages with transaction SPAM:
•
•
•
•
•
•
•
•
•
The required Support Packages must be available.
There must be enough space in the file system.
The import should be performed during a time of low operation.
The newest SPAM/SAINT update is required.
TMS/CTS must be configured.
No aborted Support Packages exist in the system.
Client 000 for importing; in all other clients only a display function is available.
Use a user that has system authorizations for transaction SPAM.
Only the system administrator should have authorization to download and import
Support Packages. The same applies for confirming successfully imported
Support Packages and resetting the status of a Support Package.
In the system, check that the transport tool is working correctly by choosing Utilities
→ Check Transport Tool. Ensure that there is enough space (size of the OCS files
multiplied by 2) in the transport directory (see SAP profile parameter DIR_TRANS
with transaction AL11 or transaction SA38 and report RSPFPAR). You should
especially ensure that there is enough space in the subdirectories trans/EPS/in and
trans/data.
Use the newest SPAM/SAINT update. Check whether the SPAM/SAINT update
provided on the SAP Service Marketplace is newer than the update in your system.
(The version of the SPAM/SAINT update in your system displays in the title bar of
the Support Package Manager.)
There must not be any incompletely imported Support Packages in your system.
Under Directory, select Aborted Supp. Packages, and choose Display. There must
not be any Support Packages displayed.
2005/Q2
© 2005 SAP AG. All rights reserved.
273
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Figure 103: SPAM: Loading Support Packages
Before you can import Support Packages, you must first load the relevant Support
Packages. SAP provides Support Packages on the SAP Service Marketplace, and on
Collection CDs (not always absolutely up-to-date).
There are two important Quick Links on the SAP Service Marketplace in the
context of Support Packages. The Quick Link /patches provides an entry to the
downloading of Support Packages. Under the Quick Link /sp-stacks, you can obtain
information about the recommended Support Package status for the individual
software components of an SAP product. The Support Package Stacks represent
combinations stipulated by SAP for the respective product version; SAP recommends
that you regularly import these.
Loading a Support Package from the SAP Service Marketplace or from CD:
1.
2.
274
Download the Support Packages from the SAP Service Marketplace or copy
them from the relevant CD and decompress them.
Now load the Support Packages into your system by choosing Support Package
→ Load Packages → From application server.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
If the compressed files are on your front end server and are smaller than around 10
MB, you can transfer these files to the application server and decompress them directly
from the Support Package Manager. With files that are larger than 10 MB in size, this
method is inefficient, since it is then significantly slower than the previous method.
1.
2.
3.
Call the Support Package Manager with transaction code SPAM.
Choose Support Package → Load Packages → From frontend.
To decompress the files in the archive, choose Decompress.
Figure 104: SPAM: Settings
Import the the Support Package Queue: The standard scenario is used to import
Support Packages completely; all steps are performed. In this case, you can select
the setting Import Mode: Downtime-minimized (import the report sources inactively)
in the standard scenario, as of SAP Web Application Server 6.10. You can use the
2005/Q2
© 2005 SAP AG. All rights reserved.
275
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
test scenario to determine before the actual import of the Support Package whether a
modification adjustment is required or whether conflicts occur that must be removed
before the import. No data and objects are imported during the test scenario.
Hint: Since SPAM version 6.10/0010 or 6.20/0010, there are new functions
available for importing a defined queue:
1.
2.
3.
4.
Start in Dialog Immediately or Continue in Dialog Immediately
Start in Background Immediately or Continue in Background
Immediately
Start in Background Later or Continue in Background Later
Continue Manually (only offered for subsequent steps after the step
Preparation).
For more information, choose the Changes button in transaction SPAM. The
link to the Online Help, in particular, provides extensive documentation for
the new functions.
Import Queue: Create New Data File /Delete Data File After Import: If you are
operating a multiple system landscape with a shared transport directory, it is useful
only to select these options in the first system where you import the Support Packages.
This saves time when importing into other systems.
ABAP/screen generation: You use this option to define whether the programs and
screens delivered with the Support Packages should be generated during the import.
You have the following options:
•
•
•
276
Never Execute: With no automatic generation, the programs and screens are
generated the first time they are called.
Always Execute: With this option, screens and programs are always generated.
Note that generation can last a very long time, and that this may cause errors.
According to SAP Instructions: In this case, programs and screens are only
generated if the generation during the import of these Support Packages is
allowed by SAP.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Figure 105: SPAM: Define and Import Queue
The Support Package Manager ensures that only Support Packages that match your
system display in the queue. Support Packages that are intended for a different release
or an Industry Solution that is not installed do not appear in the queue, even if you
have loaded them into your SAP system.
Alternatively, you can compile a shared queue for all software components in the
system, by choosing All Components.
The queue contains the Support Packages available for the selected component(s) in
your system and any required Conflict Resolution Transports (CRTs) and associated
Industry Solution (IS) Support Packages.
If Support Packages in the queue have connections to Support Packages for another
software component (other predecessor relationship, required CRT), the queue is
extended with other Support Packages until all predecessor relationships are fulfilled.
Test scenario or standard scenario: To set the desired scenario, choose Extras →
Settings.
2005/Q2
© 2005 SAP AG. All rights reserved.
277
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
SPAM - Modification Adjustment
Figure 106: SPAM: Performing the Modification Adjustment
1.
2.
3.
4.
278
The Support Package Manager stops to allow the modification adjustment
(The Support Package Manager resumes processing at step RUN_SPDD or
RUN_SPAU).
So that your developers can perform the modification adjustment, create a
request in the Transport Organizer for the SPAU adjustment and another for the
SPDD adjustment, and tasks for the developers below these.
Ask the developers to perform the modification adjustment for your objects.
As long as you have not yet confirmed the queue, you can perform a
context-sensitive switch from the initial screen of the Support Package Manager
in transaction SPDD or SPAU by choosing Extras → Adjust Modifications. After
the adjustment is complete, the developers must release the tasks and inform
you. The adjustment can be performed in any client.
If you left the transaction, call the Support Package Manager (transaction
SPAM), and choose Support Package → Import Queue. The system prompts
you again to perform the modification adjustment. As it has already been
completed, ignore the message and choose Continue. The Support Package
Manager completes the processing and displays the status.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Figure 107: SPAM: Checking Logs and Confirming a Queue
The Import logs of the queue function displays logs for steps of the Support Package
Manager that use the transport control program tp. After the queue has been
successfully imported, you should always check these logs. To go to the log display,
choose Goto → Import Logs → Queue on the initial screen of the Support Package
Manager.
Confirm the successful import of the queue into your system. This ensures that
you can import other Support Packages in future. Without this confirmation, it is
not possible to import additional Support Packages. If you have not yet confirmed
successfully imported Support Packages, you are prompted to confirm these packages
during the upgrade of the system.
The procedure for importing Support Packages into additional systems is described as
follows:
Prerequisites:
1.
2.
2005/Q2
The Support Packages were successfully imported into one system, usually the
development system.
You have performed the modification adjustment.
© 2005 SAP AG. All rights reserved.
279
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Procedure:
1.
2.
Load the Support Packages into the next system (quality assurance or production
system). SPAM → Support Package → Load Packages in the target system.
Import the Support Packages in the usual way.
Hint: You can import the transport request for the SPAU modification
adjustment into the successor system.
Caution: SAP recommends that you do not import the transport request for
the SPDD modification adjustment into the successor system.
SAINT - Prerequisites and Settings
Figure 108: What Is an Industry Solution?
Add-Ons are imported with transaction SAINT: In terms of transaction SAINT, an
Add-On is everything that does not belong to the standard SAP system. This includes,
for example, Industry Solutions, SDPs, IBUs, and Plug-Ins. For a complete list of the
Industry Solutions currently offered by SAP, see http://www.sap.com/industries.
280
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
A few examples of Industry Solutions:
•
•
•
•
•
•
•
•
•
•
•
•
SAP for Aerospace & Defense
SAP for Automotive
SAP for Banking
SAP for Consumer Products
SAP for High Tech
SAP for Insurance
SAP for Mining
SAP for Oil & Gas
SAP for Pharmaceuticals
SAP for Public Sector
SAP for Telecommunications
SAP for Utilities
You must take the following prerequisites and settings into account to import Add-Ons
with transaction SAINT:
•
•
•
•
•
•
•
•
The required Industry Solutions, Support Packages, and CRTs must be available.
There must be enough space in the file system.
The import should be performed during a time of low operation.
The newest SPAM/SAINT update is required.
TMS/CTS must be configured.
No aborted Support Packages or IS exist in the system.
Use client 000 for importing; only a display function is available in all other
clients.
System authorizations must exist for SAINT.
Hint: The procedures for an Add-On installation and an Add-On upgrade
are identical.
2005/Q2
© 2005 SAP AG. All rights reserved.
281
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Figure 109: SAINT: Loading an Industry Solution and Settings
The packages are loaded in the same way as in transaction SPAM: Installation
Package → Load Packages.
Settings are made in the same way as in transaction SPAM: Extras → Settings.
Figure 110: SAINT: Importing an Industry Solution
282
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
In principle, transaction SAINT can process two different types of delivery packages;
Add-On installations and Add-On upgrades. Technically, both of these packages are
largely identical. They differ only in their import prerequisites and in the check for
object conflicts with the SAP standard system.
Hint: Ensure that you are working in client 000 and that you have loaded the
relevant installation/upgrade packages into your system.
SAINT - Modification Adjustment
Figure 111: SAINT: Performing the Modification Adjustment
You must only perform the modification adjustment for objects of the Add-On and
its Support Packages. If you have modified SAP objects from the Add-On to be
installed, you must adjust these objects during the import. (ABAP Dictionary objects
are adjusted with transaction SPDD, Repository objects with transaction SPAU.)
2005/Q2
© 2005 SAP AG. All rights reserved.
283
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Procedure:
1.
2.
3.
4.
5.
Interrupt the import of the installation queue with F12. (SAINT resumes
processing at step RUN_SPAU or RUN_SPDD.)
So that your developers can perform the modification adjustment, create a
request in the Transport Organizer and tasks under the request for the developers.
Ask the developers to perform the modification adjustment for your objects. As
long as you have not yet confirmed the installation, you can choose Extras →
Adjust Modifications on the initial screen of transaction SAINT to perform
context-dependent switch to transaction SPDD or transaction SPAU. After the
adjustment is complete, the developers must release the tasks and inform you.
The adjustment can be performed in any client.
After the adjustment is complete, call transaction SAINT. The system
automatically displays the screen that was displayed before you interrupted the
import.
Choose Continue. The system prompts you again to perform the modification
adjustment. As it has already been completed, ignore the message and choose
Continue. SAINT completes the processing and displays the status.
Figure 112: SAINT: Checking the Logs
The Import Logs function (Goto → Import Logs) displays logs for SAINT steps that
use the transport control program tp. After the queue has been successfully imported,
you should always check these logs.
284
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Caution: In the later phases of the import process, the database contents have
already been changed. You should then continue the installation from here.
Inactive Import
Figure 113: Inactive Import
Due to the size and scope of current Support Packages, importing Support Packages
requires longer system downtime. The system is not stopped and restarted during the
import process, but it should also not be used productively during this time. This
restriction is a disadvantage for many production systems. To reduce the downtime
during the import of Support Packages, an import procedure has been developed
that allows you to import a large proportion of the objects to be imported during
production operation. These objects are report sources and report texts. The downtime
can be significantly reduced if a Support Package contains a high proportion of report
sources and report texts. (For BASIS and SAP APPL/HR Support Packages, the
proportion is around 70-80%.) With the inactive import, the objects are imported into
the database in an inactive state and are therefore largely invisible to the system. You
can therefore continue to use the system productively.
2005/Q2
© 2005 SAP AG. All rights reserved.
285
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
The procedure is as follows (see also previous figure):
1.
2.
3.
Import the report sources and report texts in an inactive state. Old versions that
are still active and new, inactive versions exist in parallel in the database.
Active sources and texts that are to be replaced or deleted are set to obsolete.
Inactive sources and texts are set to active.
Actions 2 and 3 must be performed during downtime, but usually last less than
ten minutes.
4.
Deletion of sources and texts marked as obsolete from the database.
Actions 1 and 4, which require large data movements in the database, and are
therefore runtime-intensive, can be performed during uptime.
286
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Exercise 15: Import Support Packages
Exercise Objectives
After completing this exercise, you will be able to:
•
Import Support Packages with transaction SPAM
Business Example
You need to import the most recent Support Packages to update your system.
Task: Import Support Packages
Import two Basis Support Packages.
This exercise must be performed first by the DEV group and then by the QAS group.
In the first step, the Basis Support Packages 83 and 84 are imported in a queue into
the SAP system DEV. After this import is successfully completed, the Basis Support
Packages 83 and 84 are imported into the SAP system QAS.
The files required for the Basis Support Packages have already been requested and are
on your host in the directory G:\Additional_Files\ADM100\SupportPackages.
1.
Check whether Support Packages have already been imported into your system.
Have these been confirmed?
2.
Unpack the files that contain the Basis Support Packages 83 and 84 at operating
system level.
Remember that this step must only be performed once for each transport
directory.
Caution: On the training systems, these patches are called SAPKIXT083
and SAPKIXT084 instead of SAPKA50A83 and SAPKA50A84. This is
only the case on this training systems for technical reasons. The normal
naming conventions apply in real systems.
3.
Log on to the correct client.
4.
Load the Support Packages, that is, inform the SAP system about the files.
5.
Check the settings for the import of the Support Packages in transaction SPAM.
6.
Define the queue for importing Basis Support Packages 83 and 84 in transaction
SPAM.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
287
Unit 10: Support Packages, Plug-Ins, and Add-Ons
288
ADM100
7.
Import the queue for Basis Support Packages 83 and 84 into your system. Note
any possible errors.
8.
Check the log for the import process for errors.
9.
Confirm the imported Support Packages after successful import.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Solution 15: Import Support Packages
Task: Import Support Packages
Import two Basis Support Packages.
This exercise must be performed first by the DEV group and then by the QAS group.
In the first step, the Basis Support Packages 83 and 84 are imported in a queue into
the SAP system DEV. After this import is successfully completed, the Basis Support
Packages 83 and 84 are imported into the SAP system QAS.
The files required for the Basis Support Packages have already been requested and are
on your host in the directory G:\Additional_Files\ADM100\SupportPackages.
1.
Check whether Support Packages have already been imported into your system.
Have these been confirmed?
a)
Transaction SPAM: Select Imported Support Packages and choose Display.
Result: 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.
2.
Unpack the files that contain the Basis Support Packages 83 and 84 at operating
system level.
Remember that this step must only be performed once for each transport
directory.
Caution: On the training systems, these patches are called SAPKIXT083
and SAPKIXT084 instead of SAPKA50A83 and SAPKA50A84. This is
only the case on this training systems for technical reasons. The normal
naming conventions apply in real systems.
a)
Go to operating system level. Copy the files KIXT083.CAR and
KIXT084.CAR from the directory G:\Additional_Files\ADM100\SupportPackages to the directory \usr\sap\trans.
Open a Command Prompt at operating system level. Switch to the directory
\usr\sap\trans and unpack the copied file with the commands sapcar -xvf
KIXT083.CAR and sapcar -xvf KIXT084.CAR. This automatically unpacks
the files in the directory \usr\sap\trans\EPS\in.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
289
Unit 10: Support Packages, Plug-Ins, and Add-Ons
3.
Log on to the correct client.
a)
4.
ADM100
Log on to client 000. It is only possible to import Support Packages from
client 000.
Load the Support Packages, that is, inform the SAP system about the files.
a)
Transaction SPAM: Support Package → Load Packages → From
application server
Confirm the dialog box to upload.
5.
Check the settings for the import of the Support Packages in transaction SPAM.
a)
Transaction SPAM: Extras → Settings
Leave the settings set to their default values.
6.
Define the queue for importing Basis Support Packages 83 and 84 in transaction
SPAM.
a)
Transaction SPAM: Choose the Display/Define Queue button. Select
SAP_BASIS, and choose the queue up to Basis Support Package 84 (the
selection is already correct).
You can Confirm Queue with Enter.
7.
Import the queue for Basis Support Packages 83 and 84 into your system. Note
any possible errors.
a)
In transaction SPAM, import the queue by choosing Support Package →
Import Queue. Confirm the dialog box to import.
Follow the individual steps of the import process, as far as possible, in
the status line.
If errors occur, check these by opening the error log. Repeat the import of
the Support Package. The import process can be repeated.
Confirm the dialog box informing you that the import was successful.
8.
Check the log for the import process for errors.
a)
Check the import logs in transaction SPAM by choosing Goto → Import
Logs → Queue.
No returncodes > 8 should display.
9.
Confirm the imported Support Packages after successful import.
a)
290
Finally, confirm the queue in transaction SPAM by choosing Support
Package → Confirm.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing Support Packages
Lesson Summary
You should now be able to:
•
Import Support Packages with transaction SPAM
•
Install and update Industry Solutions with transaction SAINT
2005/Q2
© 2005 SAP AG. All rights reserved.
291
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Lesson: Updating the Tools
Lesson Overview
In this lesson, you will learn what to consider during a SPAM/SAINT update. An
update of this type may be required before you can import new Support Packages.
Lesson Objectives
After completing this lesson, you will be able to:
•
Update transactions SPAM and SAINT
Business Example
Functional enhancements of the system can affect not only the applications, but also
the tools with which you import the Support Packages.
SPAM/SAINT Update
Figure 114: Importing a SPAM/SAINT Update
You receive enhancements and improvements for SPAM and SAINT with a
SPAM/SAINT Update. There is one update for each correction status. This status
is updated over time. You can find out the version from the short description, for
example: SPAM/SAINT update - version <REL>/0001
292
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Updating the Tools
SAP recommends that you always import the newest version of a SPAM/SAINT
Update before you import other Support Packages.
You can only import a SPAM/SAINT Update with the transaction SPAM.
You can only successfully import a SPAM/SAINT Update if there are no aborted
Support Packages in the system. If there are aborted Support Packages, a dialog box
informs you of this. You then have two options:
•
•
You first import the complete queue and then the SPAM/SAINT update.
You reset the status of the queue, first import the SPAM/SAINT Update and then
the queue. You can reset the status of the queue by choosing Extras → Reset
Status → Queue.
To import the newest SPAM/SAINT Update, choose Support Package → Import
SPAM/SAINT Update. SPAM/SAINT updates are automatically confirmed after a
successful import.
2005/Q2
© 2005 SAP AG. All rights reserved.
293
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
294
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Updating the Tools
Exercise 16: SPAM Update
Exercise Objectives
After completing this exercise, you will be able to:
•
Successfully perform a SPAM update
Business Example
Importing Support Packages often first requires an update of the system programs
used to perform the import, so that all of the control information for the new Support
Packages can be read.
Task: Import a SPAM Update
Import a SPAM update.
Caution: This exercise must be performed by the DEV group first and
then by the QAS group.
In the first step, a SPAM update is imported into the SAP system DEV. After this
import has been successfully completed, the SPAM update is imported into the SAP
system QAS in a second step.
The files required for the SPAM update are on the host of the SAP system in the
directory G:\Additional_Files\ADM100\SPAMUpdate.
1.
Check whether a SPAM update has already been imported into your system. If
yes: which version?
2.
Unpack the file that contains the SPAM update at operating system level.
Remember that this step only needs to be performed once for each transport
directory.
2005/Q2
3.
Log on to the correct client.
4.
Load the patch using transaction SPAM; that is, inform the SAP system about
the file.
5.
Import the SPAM update into your system. Note any possible errors.
6.
Check the log for the import process for errors.
© 2005 SAP AG. All rights reserved.
295
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Solution 16: SPAM Update
Task: Import a SPAM Update
Import a SPAM update.
Caution: This exercise must be performed by the DEV group first and
then by the QAS group.
In the first step, a SPAM update is imported into the SAP system DEV. After this
import has been successfully completed, the SPAM update is imported into the SAP
system QAS in a second step.
The files required for the SPAM update are on the host of the SAP system in the
directory G:\Additional_Files\ADM100\SPAMUpdate.
1.
Check whether a SPAM update has already been imported into your system. If
yes: which version?
a)
Call transaction SPAM. The version of SPAM displays in the title bar, such
as: Support Package Manager - Version 6.40/0016
To see whether SPAM updates have already been imported, select Imported
Support Packages and choose Display. The system displays an overview of
the previously imported SPAM updates.
Note: You can also jump individual SPAM updates, that is, it is
possible to change directly from version 001 to 008.
2.
Unpack the file that contains the SPAM update at operating system level.
Remember that this step only needs to be performed once for each transport
directory.
a)
Go to operating system level. Copy the file KD640<nn>.CAR from the
directory G:\Additional_Files\ADM100\SPAMUpdate to the directory
\usr\sap\trans. <nn> stands for the (newest) version of the SPAM update.
Open a Command Prompt at operating system level. Switch to the
directory \usr\sap\trans and unpack the copied file with the command
sapcar -xvf KD640<nn>.CAR. This unpacks the file in the directory
\usr\sap\trans\EPS\in.
Continued on next page
296
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Updating the Tools
3.
Log on to the correct client.
a)
4.
Load the patch using transaction SPAM; that is, inform the SAP system about
the file.
a)
5.
In transaction SPAM, choose: Support Package → Import SPAM/SAINT
Update. Confirm the dialog box to import. Then call transaction SPAM
again. This takes some time, since the system must regenerate the
underlying programs and so on, due to the SPAM update.
Check the log for the import process for errors.
a)
2005/Q2
Transaction SPAM: Support Package → Load Packages → From
application server. Confirm the dialog box to upload.
Import the SPAM update into your system. Note any possible errors.
a)
6.
Log on to client 000. It is only possible to import the SPAM update from
client 000.
In transaction SPAM, choose: Support Package → Import Logs →
SPAM/SAINT Update. No errors should display.
© 2005 SAP AG. All rights reserved.
297
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Lesson Summary
You should now be able to:
•
Update transactions SPAM and SAINT
298
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing SAP Notes
Lesson: Importing SAP Notes
Lesson Overview
In this lesson, you will learn how to import preliminary corrections from SAP Notes
using the Note Assistant.
Lesson Objectives
After completing this lesson, you will be able to:
•
Describe how to use the SAP Note Assistant
Business Example
A current error correction that is not yet included in any Support Package is to be
imported in accordance with a SAP Note. The administrator performs this correction
using the SAP Note Assistant.
SAP Note Assistant
Figure 115: Introduction to the SAP Note Assistant: Functions
2005/Q2
© 2005 SAP AG. All rights reserved.
299
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
The SAP Note Assistant allows you to automate, control, and document imports
of SAP Notes.
Not all SAP Notes are suitable for the SAP Note Assistant. Check this in individual
cases. The SAP Note must contain technical labels so that the Note Assistant can
recognize the beginning and the end of the documentation and the ABAP coding
in the SAP Note.
The SAP Note Assistant is also available for older SAP releases. For more
information, see the SAP Service Marketplace, Quick Link /noteassistant. It is
contained in the standard SAP system as of SAP Web AS 6.10.
The transaction for the SAP Note Assistant is SNOTE.
Figure 116: Introduction to the SAP Note Assistant: Process
300
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Importing SAP Notes
The following conditions apply in the system for the SAP Note Assistant:
•
•
•
•
•
The SSCR query does not apply for installations using the SAP Note Assistant
The installation of changes is subject to the normal change recording
Changes are recorded in the Modification Assistant (only what was changed,
not how)
There are two new logical transport objects: R3TR NOTE: SAP Note, R3TR
CINS: Correction instructions
Changes are fully transportable, for example, to the quality assurance and
production systems
Note: SAP Notes are not allowed to change DDIC objects. There is therefore
no SPDD modification adjustment during an upgrade or when importing
Support Packages.
2005/Q2
© 2005 SAP AG. All rights reserved.
301
Unit 10: Support Packages, Plug-Ins, and Add-Ons
ADM100
Lesson Summary
You should now be able to:
•
Describe how to use the SAP Note Assistant
302
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Unit Summary
Unit Summary
You should now be able to:
•
List the differences in principle between Support Packages, Plug-Ins, and
Add-Ons
•
Import Support Packages with transaction SPAM
•
Install and update Industry Solutions with transaction SAINT
•
Update transactions SPAM and SAINT
•
Describe how to use the SAP Note Assistant
2005/Q2
© 2005 SAP AG. All rights reserved.
303
Unit Summary
304
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
What are Support Packages and Add-Ons used for?
Choose the correct answer(s).
2.
□
□
A
B
□
□
□
C
D
E
To enter user data.
To import SAP object to maintain the system with a current correction
status.
To implement additional functions in the system.
To transport customer-developed programs.
To import preliminary corrections from SAP.
Support Packages can be imported in any order.
Determine whether this statement is true or false.
□
□
3.
True
False
All SPAM/SAINT updates must always be imported.
Determine whether this statement is true or false.
□
□
4.
True
False
The queue for importing the SPAM update must be manually confirmed.
Determine whether this statement is true or false.
□
□
5.
True
False
A prerequisite for importing a SPAM/SAINT update is that there are no aborted
Support Packages in the system.
Determine whether this statement is true or false.
□
□
6.
True
False
You use transaction
to import individual SAP Notes. Using the
Note Assistant means that you are not queried for an
in
the SAP Service Marketplace.
Fill in the blanks to complete the sentence.
2005/Q2
© 2005 SAP AG. All rights reserved.
305
Test Your Knowledge
ADM100
Answers
1.
What are Support Packages and Add-Ons used for?
Answer: B, C
Support Packages are not used to enter user data. Customer developments are
transported to other systems using transport requests. Preliminary corrections
are imported using the SAP Note Assistant.
2.
Support Packages can be imported in any order.
Answer: False
Support Packages must be imported in ascending order, without any gaps.
3.
All SPAM/SAINT updates must always be imported.
Answer: False
All associated programs are always upgraded during the SPAM/SAINT update.
It is therefore not necessary to follow any particular order.
4.
The queue for importing the SPAM update must be manually confirmed.
Answer: False
It is not necessary either to define a special queue, or to confirm this non-existent
queue.
5.
A prerequisite for importing a SPAM/SAINT update is that there are no aborted
Support Packages in the system.
Answer: True
This is true, there must not be any aborted Support Packages in the system.
306
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
6.
You use transaction SNOTE to import individual SAP Notes. Using the Note
Assistant means that you are not queried for an object key in the SAP Service
Marketplace.
Answer: SNOTE, object key
Individual SAP Notes are imported with SNOTE. It is also not necessary to
request an SSCR key.
2005/Q2
© 2005 SAP AG. All rights reserved.
307
Unit Summary
308
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 11
Including Printers in SAP Systems
Unit Overview
In this unit, you will learn about the output processing architecture in the SAP system.
You will learn how to define printers and spool servers in the system and how to
manage spool and output requests.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
Describe the architecture and data flow of output processing in the SAP system
Create printers and spool servers in the SAP system
List important access methods
Manage spool requests
Describe the concept of logical spool servers
Set up logical spool servers
Manage spool and output requests
Unit Contents
Lesson: Configuring Printers in SAP Systems .................................. 310
Exercise 17: Configure Printers .............................................. 321
Lesson: Concept of Logical Spool Servers ...................................... 328
Exercise 18: Logical Spool Servers .......................................... 335
Lesson: Managing Spool Requests .............................................. 339
Exercise 19: Managing Spool Requests .................................... 345
2005/Q2
© 2005 SAP AG. All rights reserved.
309
Unit 11: Including Printers in SAP Systems
ADM100
Lesson: Configuring Printers in SAP Systems
Lesson Overview
In this lesson, you will learn about the output processing architecture. You will learn
how to set up printers in the SAP system.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
•
Describe the architecture and data flow of output processing in the SAP system
Create printers and spool servers in the SAP system
List important access methods
Manage spool requests
Business Example
The administrator sets up printers in the SAP system and monitors the output of spool
requests.
Printing from SAP Systems
There are various document classes in the SAP system (such as report lists, SAPscript
or SAP Smart Forms documents). Although the way in which documents are created
may be completely different, the output on paper is always performed using the same
mechanism in two steps: First a spool request is created. The spool request contains
device-independent print data and includes administrative information (such as author,
date, number of copies) and the actual print data. Only when the spool request is to be
output on a particular device is an output request created. The device-independent
print data from the spool request is converted to the printer language that the selected
output device understands.
310
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Figure 117: Data Flow During Printing
This procedure allows the user to display a spool request before output. There can
also be several output requests for one spool request. This can avoid the user having
to recreate (possibly with a great deal of effort) a spool request, if, for example, the
toner in a printer is exhausted, or the wrong paper was in the tray. The user can of
course create a spool request and an output request at the same time (immediate print)
by choosing the Print immediately option.
The actual document content of a spool request is stored in TemSe (for temporary
sequential objects), for which you define the storage location with the profile
parameter rspo/store_location.
•
•
Value db (the default value): Spool requests are stored in database table TST03
(Advantage: backup as part of the database).
Value G: Stored at operating system level in the global directory (advantage:
performance).
Note: You can also specify the storage location individually for the output
device in transaction SPAD (menu path Edit → Data Storage).
SAP Note 20176 contains additional possible values for rspo/store_location.
2005/Q2
© 2005 SAP AG. All rights reserved.
311
Unit 11: Including Printers in SAP Systems
ADM100
The creation of an output request prompts the SAP spool system to send a (usually)
printer-dependent, completely formatted data stream to a printer using an operating
system spooler (OS spool). This means that the addressed printer model must be
known to the SAP system. Definitions of this type are described as device types.
If a printer cannot be controlled at operating system level, it cannot be used from
the SAP system, either.
There are many ways in which a spool work process can reach an operating system
spooler. The most important of these connections, described as access methods,
are introduced in the following sections.
Local Printing
Figure 118: Local Printing
A characteristic of local printing is that the spool work process and operating
system spool are running on the same host. It is irrelevant whether the printer is
directly connected to this host, or is reached over a network (and possibly another print
server). The spool work process passes on its data locally, that is on the same host.
•
•
312
On UNIX systems, the print data with access method L is output using operating
system methods (for example, with the commands lp or lpr). The specific syntax
is stored in profile parameters.
Under Microsoft Windows, the data with access method C is passed directly to
the operating system print API.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Local printing is the fastest and most reliable connection from the SAP system to the
operating system. As soon as the spool work process has transferred its data, it can deal
with new output requests - even if the operating system spooler may still be occupied.
You can configure multiple spool work processes for an SAP instance. This has irrespective of the access method - consequences for the output sequence. Different
spool requests for the same printer may be printed in a different order to that in
which they were created. If you require output in sequence, you can specify this for
individual printers. However, a setting of this type reduces the ability to process in
parallel. For more information about this topic, see SAP Note 108799.
Remote Printing
With remote printing, the spool work process and operating system spooler are running
on different hosts. In exactly the same way as with local printing, it is irrelevant from
the SAP system's point of view whether the printer is directly connected to the remote
host, or is reached using another network connection.
Figure 119: Remote Printing
2005/Q2
© 2005 SAP AG. All rights reserved.
313
Unit 11: Including Printers in SAP Systems
ADM100
Typical scenarios for remote printing are:
•
•
•
Network printers provide their own operating system spoolers and are directly
connected to a computer network. Printers of this type are directly addressed
from the SAP system using their names (access method U).
Access method U is also used if the remote host is a UNIX system. SAP Note
39405 describes how access method U can be used for the various UNIX
versions.
SAP provides the program saplpd for all hosts with Microsoft Windows
operating systems. The saplpd transfer program forwards the print output from
the SAP system to the Microsoft Windows output control.
Access method S is usually used here (SAP protocol), but access method U
(UNIX Berkeley protocol) is also supported.
For performance reasons, you should only use remote printing in a LAN environment
(not WAN) and should ensure that the operating system spoolers are available.
Front-End Printing
Figure 120: Front-End Printing
314
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
SAP users can output documents on their local printers using front-end printing.
These local printers do not need to be individually defined in the SAP system. Rather
the system administrator only needs to create a representative output device for each
operating system platform.
The print data stream is transferred to the host where the user's SAP GUI is running
using access method F. This method can be used for front end PCs with different
operating systems:
•
•
In the case of Microsoft Windows operating systems, the saplpd transfer program
receives the data stream and forwards it to the default printer of the Microsoft
Windows output control (or a different printer, if this is configured). If necessary,
saplpd is automatically started.
With other operating systems (UNIX, Apple Macintosh, and so on), the data is
transferred directly to the operating system spooler. In this case, the printer name
(identical for all users) must be specified in the device definition.
The processing of front-end printing is also performed, as with the other output
methods, using a spool work process. There can, therefore, be conflicts between
regular and front-end print requests. You specify the maximum number of spool work
processes that can be used for front-end printing for each SAP instance using the
profile parameter rdisp/wp_no_Fro_max (the default value is 1).
Front-end printing is suitable for output on local printers; however, it is not for
production or mass printing.
Of course, front-end printing requires a connection to the front end PC. However, this
method cannot be used for background processing.
For more information, see SAP Composite Note 114426. SAP Notes 351230 (before
SAP Web AS 6.40) and 771683 (from SAP Web AS 6.40) describe front-end printing
with the (standalone) SAP ITS, or with the integrated ITS when using the SAP GUI
for HTML. SAP Note 150533 contains information about front-end printing when
using Windows Terminal Server.
Creating Output Devices
The configuration of the spool system is a system administration task. The central
tool for this is transaction SPAD (menu path Tools → CCMS → Print → Spool
Administration).
2005/Q2
© 2005 SAP AG. All rights reserved.
315
Unit 11: Including Printers in SAP Systems
ADM100
Creating Output Devices
Device
Attributes
Device Type
Spool Server
Access Method Access Method
Local
Remote
Select the
appropriate
type in each
case
Select the
appropriate
type in each
case
SWIN
S or U
F
Host
Destination Host
–
L (UNIX)
C
(Windows)
Host Printer
Front-end
OS Printer
Name
OS Printer
Name
__DEFAULT
fix
–
–
–
Select
–
To create an output device, choose Output Devices on the Devices / Servers tab page.
If there is already a large number of devices in your system, you can restrict the output
list in the field next to the button (for example, “PR*”). Important information for
a device:
Output device
Name, maximum of 30 characters long (case-sensitive).
Short name
For internal system purposes (can be automatically generated).
Device type
Printer model/family (more information about this below). The device type
SWIN transfers the SAP system format to the Microsoft Windows printer driver.
This is useful, for example, if various printers are used for front-end printing in
a Microsoft Windows environment.
Spool server
SAP application server with spool work processes or logical server.
Location
For example, building and room number (so that users can find their output).
Message
Used to temporarily override the location (such as “Is currently in maintenance”).
316
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Lock printer in SAP system
Output requests for printers for which this indicator is selected are created but not
transferred to the printer. The user receives the message ...no immediate printing.
Host spool access method
How does a spool work process contact the operating system spooler?
Host printer
Name of the printer at operating system level. Note that this name is
case-sensitive. Under Microsoft Windows, there must not be a space in the
printer name, and network printers are addressed using their UNC names (in
the format \\R12345\P42). The specification __DEFAULT calls the default
Microsoft Windows printer (for example, for front-end printing in a Microsoft
Windows environment).
Host
Only for local printing, is calculated automatically from the spool server.
Destination hosts
Only for remote printing. Name of the host where the operating system spooler
(such as lpd or saplpd) is running.
Device Types
The SAP system uses a device type to format the output device-specific print output.
Hint: When reference is made to an output device in the SAP environment,
it does not necessarily mean a printer. An output device can also be, for
example, an Output Management System or an archiving system.
When the spool work process generates an output request, it uses the specifications of
the device type. That is, the device type describes how print data should be formatted
for a particular output device.
The following figure illustrates how a device type is created.
2005/Q2
© 2005 SAP AG. All rights reserved.
317
Unit 11: Including Printers in SAP Systems
ADM100
Figure 121: What Is a Device Type?
The following list explains the terms from the above figure.
Page format
A page format describes the format of a printable page in the SAP system.
A large number of standard page formats are predefined in the system. If a
device is to support additional format that are not delivered, you can define new
formats. Consider when doing so that your output device must, of course, be
able to use the new format.
Format type
A format type describes how output should appear on paper. It primarily contains
the formatting of the page format.
Format
A format is a device-specific implementation of a format type. That is, the SAP
system can use the description in a format to control a device correctly to, for
example, perform an output on a page with the Letter format. A format type is
therefore not device-specific; the format, on the other hand, is a device-specific
implementation of a format type.
318
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Character set
A character set contains the characters that can be output by a particular output
device. That is, to be able to use a particular character set for a selected printer
model in the SAP environment, the device type assigned to this printer model
must contain this character set.
Print control
Print controls allow the control of particular display options of output devices,
such as boldface, changing the font size, changing the font, and so on. Print
controls use device-specific control character sequences. That is, to create a
new device type, the display options offered in the SAP system must be stored
with the control character sequences that the selected printer model supports.
The control character sequences to be used can be found in the device vendor's
documentation.
You can see that using devices for which no suitable device type exists in the SAP
system may mean a significant effort.
Figure 122: Selecting an Appropriate Device Type
2005/Q2
© 2005 SAP AG. All rights reserved.
319
Unit 11: Including Printers in SAP Systems
ADM100
How do you assign the correct device type to your printer?
•
•
•
•
•
320
In the ideal situation, there is already a device type in your SAP system. Note
that a separate device type is not required for every printer model of a vendor,
but just for each model family.
SAP Note 8928 contains a list of all printers supported by SAP. There is an
attachment for this SAP Note containing corresponding device types.
For many printers, you can use a generic format (such as PostScript) for which
device types exist. It is also possible that your printer can be addressed in the
same way as another model that is supported by SAP (compatibility mode).
There are drivers for the Microsoft Windows operating systems for practically
all printers on the market. You can use these printers as output devices with
device type SWIN. The conversion to a print data stream is performed by the
Microsoft Windows driver in this case.
The SAP system contains all of the tools required to create your own device
types or to adjust copies of existing device types. Detailed knowledge of the
SAP spool system and the printer control are required to do this. You should
weigh up the expense against the purchase of supported printers.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Exercise 17: Configure Printers
Exercise Objectives
After completing this exercise, you will be able to:
•
Create printers and spool servers in the SAP system
Business Example
The administrator sets up printers in the SAP system.
Task 1: Check the Print Environment
First check the print environment of your system.
1.
How many spool work processes are set up for the application server to which
you are currently logged on?
2.
How many spool processes are configured in your entire SAP system?
3.
How many spool servers are available in your SAP system?
4.
Make a setting for your SAP user so that an output request is not created
immediately for a spool request.
5.
Which printers are defined at operating system level of your server? Where
do they print?
6.
(If possible) Which printers are defined at operating system level of your front
end PC in the training room? Where do they print?
Task 2: Create a Local Printer
1.
Create a local printer Local<##> (<##> stands for your group number) in your
SAP system that calls one of the previously determined printers.
2.
Output any list (Suggestion: All profile parameters that begin with rspo) without
immediate printing on the printer Local<##>.
Task 3: Create a Remote Printer (Optional)
1.
Create a remote printer Remote<##> in the SAP system that calls a remote
printer that the instructor specifies.
2.
Output any list with immediate printing on the printer Remote<##>.
3.
Check your output.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
321
Unit 11: Including Printers in SAP Systems
ADM100
Task 4: Create a Front-End Printer (Optional)
1.
Create a front-end printer Frontend<##> in the SAP system that calls the default
printer of a Microsoft Windows front end PC.
2.
Output any list with immediate printing on the printer Frontend<##>.
3.
Check your output.
Task 5: Front-End Printing with the SAP GUI for HTML
(Optional)
1.
In the SAP system, create a new printer Webgui## by copying the front-end
printer that you have created. Change the device type to PDF1.
2.
Call the following URL in your local Web Browser (in the training room):
http://<server with path>:<SID ITS Port>/scripts/wgate/webgui/!
For example:
http://twdf9999.wdf.sap.corp:1081/ scripts/wgate/webgui/!
Hint: Do not forget the “!” sign at the end.
3.
322
Log on with your SAP user. Print any list (such as the output of transaction
AL08) on the printer Webgui<##>, and then perform another action (such as
choosing Back in the system). Observe what happens in the new Web browser
window.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Solution 17: Configure Printers
Task 1: Check the Print Environment
First check the print environment of your system.
1.
How many spool work processes are set up for the application server to which
you are currently logged on?
a)
2.
Call transaction SM50 and count the number of work processes of type
SPO.
How many spool processes are configured in your entire SAP system?
a)
This information is provided by transaction SM66. If you do not see any
work processes at first, check the status wait under Select process.
Hint: The number of spool work processes cannot be changed
by operation mode switches.
3.
How many spool servers are available in your SAP system?
a)
4.
Make a setting for your SAP user so that an output request is not created
immediately for a spool request.
a)
5.
To do this, choose System → User Profile → Own Data (transaction SU3
) and the Defaults tab page there. Ensure that Output Immediately is not
checked and save your changes, if necessary.
Which printers are defined at operating system level of your server? Where
do they print?
a)
6.
A (real) spool server is an SAP application server with at least one spool
work process. You can display this information with transaction SM51
more easily than with transaction SM66: All application servers that
provide the service Spool are spool servers.
Call Start → Settings → Printers at operating system level in your server.
There should be printers (such as Printer1 for the group working on the
DEV system and Printer2 for the group working on the QAS system) that
print to a file.
(If possible) Which printers are defined at operating system level of your front
end PC in the training room? Where do they print?
a)
If possible, call Start → Settings → Printers on your front end.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
323
Unit 11: Including Printers in SAP Systems
ADM100
Task 2: Create a Local Printer
1.
Create a local printer Local<##> (<##> stands for your group number) in your
SAP system that calls one of the previously determined printers.
a)
In the SAP system, choose Tools → CCMS → Print → Spool
Administration (transaction SPAD). On the Devices/Servers tab page,
choose Output Devices (leave the field to the right empty). If you cannot
find the button to Create, choose Change to switch to change mode. Now
create the printer Local<##> with the following details:
•
Device Attributes tab page:
–
•
Device Type: Should match the previously determined printer
(HPLJ4)
–
Spool Server: Any spool server from your system
–
Location: Any text
Host Spool Access Method tab page:
–
–
Access Method: C for Windows
Host Printer: Name of the previously determined printer
(Printer1 or Printer2)
Accept the default values for the other values and save. As you can see, the
system specifies the Short Name automatically.
2.
Output any list (Suggestion: All profile parameters that begin with rspo) without
immediate printing on the printer Local<##>.
a)
To create the suggested list, start transaction SA38 enter the report
RSPFPAR, and execute it. Enter the parameter rspo* and choose Execute
again. Alternatively, you can also print the output of transaction SM51.
To Print, choose the appropriate button. Alternatively, you can choose
System → List → Print. Choose the output device Local<##> (enter it
directly or select it using the F4 help). Choose Continue without making
any additional entries.
Task 3: Create a Remote Printer (Optional)
1.
Create a remote printer Remote<##> in the SAP system that calls a remote
printer that the instructor specifies.
a)
The procedure is the same as for the previous exercise, but with different
values. Your instructor will give you the exact information (host name,
printer name, access method).
Continued on next page
324
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
2.
Output any list with immediate printing on the printer Remote<##>.
a)
3.
You can change your user defaults by choosing System → User Profile
→ Own Data (transaction SU3). Check the Immediate Output field on
the Defaults tab page.
Check your output.
a)
Due to the setting made in task 2, print time Output Immediately is now
the default value. The user can make this (and other) settings in the print
dialog box by choosing Properties.
Hint: By choosing Show selected print parameters on initial
screen in the Properties window, you can maintain some
parameters directly on the print dialog box in future.
Task 4: Create a Front-End Printer (Optional)
1.
Create a front-end printer Frontend<##> in the SAP system that calls the default
printer of a Microsoft Windows front end PC.
a)
In the SAP system, choose Tools → CCMS → Print → Spool
Administration (transaction SPAD). On the Devices/Servers tab page,
choose Output Devices (leave the field to the right empty). If you cannot
find the button to Create, choose Change to switch to change mode. Now
create the printer Frontend<##> with the following details:
•
Device Attributes tab page:
•
–
Device Type: SWIN
–
Location: here
Host Spool Access Method tab page:
–
–
Access Method: F
Host Printer: __DEFAULT
Accept the default values for the other values and save. As you can see, the
system specifies the Short Name automatically.
2.
Output any list with immediate printing on the printer Frontend<##>.
a)
The procedure is the same as for the previous task. If it is installed, you
should now see saplpd started on your front end PC and receiving
the print data stream. saplpd then continues running, to receive any
additional print data.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
325
Unit 11: Including Printers in SAP Systems
3.
ADM100
Check your output.
a)
The procedure is the same as for the previous task.
Task 5: Front-End Printing with the SAP GUI for HTML
(Optional)
1.
In the SAP system, create a new printer Webgui## by copying the front-end
printer that you have created. Change the device type to PDF1.
a)
In the SAP system, choose Tools → CCMS → Print → Spool
Administration (transaction SPAD). On the Devices/Servers tab page,
choose Output Devices (leave the field to the right empty). If you cannot
find the button to copy (Create using Template button), choose Change to
switch to change mode. Now select the printer Frontend<##> with the
mouse and choose Create with Template.
Call the new printer Webgui<##> and change the device type to PDF1.
Leave the other values unchanged and save.
2.
Call the following URL in your local Web Browser (in the training room):
http://<server with path>:<SID ITS Port>/scripts/wgate/webgui/!
For example:
http://twdf9999.wdf.sap.corp:1081/ scripts/wgate/webgui/!
Hint: Do not forget the “!” sign at the end.
a)
See exercise text.
The SAP ITS port may not be accessible from your training room. If this is
the case, use the Web browser available on your server.
3.
Log on with your SAP user. Print any list (such as the output of transaction
AL08) on the printer Webgui<##>, and then perform another action (such as
choosing Back in the system). Observe what happens in the new Web browser
window.
a)
If you proceed as described in the exercise, a new Web browser window
appears. A PDF document with the list displays in this window after some
time. This document can now be saved to the user’s computer or printed.
SAP Notes 351230 (before SAP Web AS 6.40) and 771683 (from SAP
Web AS 6.40) explain the procedure and the exact prerequisites for this
print scenario.
326
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Configuring Printers in SAP Systems
Lesson Summary
You should now be able to:
•
Describe the architecture and data flow of output processing in the SAP system
•
Create printers and spool servers in the SAP system
•
List important access methods
•
Manage spool requests
Related Information
•
•
•
SAP Library: SAP NetWeaver → Solution Life Cycle Management → System
Management → SAP Printing Guide
SAP Service Marketplace, Quick Link /output
SAP Notes
–
–
–
–
–
–
–
–
2005/Q2
SAP Note 118057: Flexible Configuration of the Spool Service
SAP Note 108799: How many spool work processes for each instance?
SAP Note 114426: Front-End Printing (Collective Note)
SAP Note 8928: List of supported printers/device types
SAP Note 351230: Front-end printing with HTML GUI/WebGUI
SAP Note 771683: New front-end printing for SAP GUI for HTML
SAP Note 19706: Tuning the spooler
SAP Note 16307: Processing Times when Printing
© 2005 SAP AG. All rights reserved.
327
Unit 11: Including Printers in SAP Systems
ADM100
Lesson: Concept of Logical Spool Servers
Lesson Overview
In this lesson, you will learn about the concept of logical spool servers and learn how
to set up logical spool servers.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the concept of logical spool servers
Set up logical spool servers
Business Example
Concept of Logical Spool Servers
The previous printing concept envisages a fixed assignment of an output device to
a spool server. A spool server, on the other hand, can be assigned multiple output
devices, which raises the risk of this server becoming overloaded. It would therefore
be desirable to have a mechanisms for load balancing across multiple servers. Groups
of spool servers are also advisable with regard to downtime security. Both aspects are
taken into account by introducing logical spool servers.
328
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of Logical Spool Servers
Figure 123: Spool Servers
A spool server is an SAP application server with at least one spool work process.
Every output request is processed on a real spool server of this type.
An output device created in the SAP system can be assigned a spool server directly.
However, there are many advantages associated with an additional logical layer
between the output device and the spool server. You can use logical (spool) servers
for this purpose, that stand for a hierarchy of other logical servers and/or real spool
servers.
You can classify output devices and spool servers, for example, for test printing or
production printing.
The SAP system checks the classifications when saving, and displays a warning
message if there are deviations. For example, the system warns you if you attempt to
assign a high volume printer to a production print server.
Creating a Logical Spool Server
You can maintain the spool server in transaction SPAD by choosing Spool Servers on
the Devices / Servers tab page. Important information for a spool server:
Server Name
Name of the spool server, maximum of 20 characters long (case-sensitive). The
field below the server name is intended for a short description.
2005/Q2
© 2005 SAP AG. All rights reserved.
329
Unit 11: Including Printers in SAP Systems
ADM100
Server Class
Classify the spool server here (for example, for mass printing).
Logical Server
Select this field when you create a logical server.
Mapping
Name of a real or logical server to which this logical server points.
Figure 124: Creating a Logical Server
You can define a spool server (real or logical) specifically for front-end printing by
setting the profile parameter rspo/local_print/server to the server name. If no spool
server is explicitly defined in this way, the local application server is used if this has
at least one spool work process. Otherwise, one of the spool servers in the system
defined in the system that has a minimal load is selected for the processing.
If you expect a significant workload due to front-end printing, you should configure
at least one additional spool work process for each front-end printing spool server
for other tasks.
As already mentioned, you can classify output devices and spool servers. To classify
an output device, select it (in transaction SPAD under Output Devices) and call the
path Edit → Classification in the menu.
330
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of Logical Spool Servers
Advantages of Logical Spool Servers
Downtime Security
When creating a spool server (either a logical server or a spool server), you can
specify an alternative server. If the normal server is not available, the SAP system
attempts to use this alternative.
Figure 125: Breakdown Alternatives
You must ensure that all printers that may be used by a different spool server can
be controlled in the same way by every spool server. For example, if the output
device Test 1 in the example points at operating system level to a printer P42 that
is controlled locally, an operating system printer P42 must be available on servers
twdf5000 and twdf5001.
You cannot store more than two spool servers for a logical server. Since a logical
server can itself point to logical servers, extensive spool server hierarchies are also
possible. You can display hierarchies of this type graphically using transaction SPAD.
Load Balancing
You can allow load balancing for every spool server with an alternative server (to do
this, select the Allow Load Balancing field). The load of a spool server is calculated
from the number of spool work processes, output requests, and printed pages.
2005/Q2
© 2005 SAP AG. All rights reserved.
331
Unit 11: Including Printers in SAP Systems
ADM100
Figure 126: Load Balancing
For an output request for a spool server with load balancing (the setting can be made
for logical servers and spool servers), the system determines the server with the lowest
load. The algorithm is recursive: The same selection criteria are used on the mapping
and the alternative server (both could be logical servers themselves).
Sequential request processing (property of an output device) has priority over the load
balancing shown here (property of a spool server). This means that output requests
for an output device with sequential request processing would not be distributed in
accordance with the current load, although assigned to a spool server with load
balancing.
Transporting the Print Landscape
The concept of logical servers supports you when defining a consistent, transportable
print landscape. Logical servers can - unlike real spool servers - have the same
name in various SAP systems. In this way, you can define a consistent SAP print
architecture in the development system and then transport it to other systems. After
the transport, you must only adjust the mapping of the logical servers to the spool
servers of the new system.
332
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of Logical Spool Servers
Figure 127: Transporting the Print Landscape
There are functions for the manual transport of output devices and spool servers in
transaction SPAD.
2005/Q2
© 2005 SAP AG. All rights reserved.
333
Unit 11: Including Printers in SAP Systems
ADM100
334
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Concept of Logical Spool Servers
Exercise 18: Logical Spool Servers
Exercise Objectives
After completing this exercise, you will be able to:
•
Set up logical spool servers and assign output devices
Business Example
Logical spool servers are to be set up in your SAP system for reasons of load balancing
and downtime security.
Task: Creating a Logical Spool Server
2005/Q2
1.
Create a logical server, Logical<##>. If possible, enter two different spool
servers as mapping and alternative server and activate load distribution. Classify
Logical<##> as a test server.
2.
Change the output device Local<##> so that the logical server Logical<##> is
used as its spool server in the future. Classify Local<##> as a test printer.
3.
Change the specifications for your SAP user so that an output request is created
for a spool request by default.
4.
Output any list (Suggestion: all profile parameters that begin with rspo) without
immediate printing on the printer Local<##>.
5.
Check your output. Which real spool server was used?
© 2005 SAP AG. All rights reserved.
335
Unit 11: Including Printers in SAP Systems
ADM100
Solution 18: Logical Spool Servers
Task: Creating a Logical Spool Server
1.
Create a logical server, Logical<##>. If possible, enter two different spool
servers as mapping and alternative server and activate load distribution. Classify
Logical<##> as a test server.
a)
In the SAP system, choose Tools → CCMS → Print → Spool
Administration (transaction SPAD). On the Devices/Servers tab page,
choose Spool Servers (leave the field to the right empty). If you cannot
find the button to Create, choose Change to switch to change mode. Now
create the logical spool server Logical<##>.
Choose Logical server and enter at least one spool server for Mapping.
Enter the other details as described in the exercise and choose save.
2.
Change the output device Local<##> so that the logical server Logical<##> is
used as its spool server in the future. Classify Local<##> as a test printer.
a)
3.
From transaction SPAD, choose the Output Devices button on the Devices
/ Servers tab page. By selecting Local<##>, you can edit your printer
(switch to change mode, if necessary). Now enter the logical spool server
Logical<##> as the Spool Server on the Device Attributes tab page. To
classify the output device, choose Edit → Classification → Test Print.
Choose Save.
Change the specifications for your SAP user so that an output request is created
for a spool request by default.
a)
You can change your user defaults by choosing System → User Profile →
Own Data (transaction SU3). Check the Immediate Output field on the
Defaults tab page and Save.
Continued on next page
336
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of Logical Spool Servers
4.
Output any list (Suggestion: all profile parameters that begin with rspo) without
immediate printing on the printer Local<##>.
a)
Due to the setting made in the previous task, print time Output Immediately
is now the default value. The user can make this (and other) settings in the
print dialog box by choosing Properties.
Hint: By choosing Show selected print parameters on initial
screen on the Properties window, you can maintain some
parameters directly on the print dialog box in future.
To create the suggested list, start transaction SA38 enter the report
RSPFPAR, and execute it. Enter the parameter rspo* and choose Execute
again. Alternatively, you can also print the output of transaction SM51.
To Print, choose the appropriate button. Alternatively, you can choose
System → List → Print. Choose the output device Local<##> (enter it
directly or select it using the F4 help). Choose Continue without making
any additional entries.
5.
Check your output. Which real spool server was used?
a)
2005/Q2
This time, an output request is created immediately. Transaction SP01
displays its status. For the spool server, select your output request (not
the spool request) and choose Choose Detail. The server name is at the
bottom of the list.
© 2005 SAP AG. All rights reserved.
337
Unit 11: Including Printers in SAP Systems
ADM100
Lesson Summary
You should now be able to:
•
Describe the concept of logical spool servers
•
Set up logical spool servers
Related Information
•
•
•
SAP Library: SAP NetWeaver → Solution Life Cycle Management → System
Management → SAP Printing Guide
SAP Service Marketplace, Quick Link /output
SAP Notes
–
338
SAP Note 118057: Flexible Configuration of the Spool Service
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Managing Spool Requests
Lesson: Managing Spool Requests
Lesson Overview
In this lesson, you will learn about managing spool and output requests.
Lesson Objectives
After completing this lesson, you will be able to:
•
Manage spool and output requests
Business Example
As a spool administrator, you maintain the spool and output requests in your SAP
system.
Managing Spool and Output Requests
To maintain spool and output devices, call the Output Controller (transaction SP01
or choose System → Services → Output Control). If you only want to check the status
of your own spool requests, choose System → Own Spool Requests (transaction SP02).
Transaction SP01 provides many selection criteria for selecting particular spool or
output requests. Every user can individually and easily define the selection criteria
that he or she requires using the Further Selection Criteria... function.
2005/Q2
© 2005 SAP AG. All rights reserved.
339
Unit 11: Including Printers in SAP Systems
ADM100
Figure 128: Selecting Spool or Output Requests
It is even possible to monitor spool and output requests on other SAP systems. To
do this, enter a valid RFC connection in the System Name field. If this field remains
empty, all systems that were selected for remote monitoring using transaction RZ20
(table ALCONSEG) are addressed.
340
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Managing Spool Requests
Figure 129: Monitoring Spool and Output Requests
The displayed list shows all spool or output requests that match your selection criteria.
The list is created using the SAP List Viewer (ALV). This allows you to change the
appearance of the list as you desire. This means that you can show and hide columns,
sort columns, or create variants.
The following indicators specify the status of a spool request:
Not yet sent to the operating system (no output request exists).
+
Spool request is still being created (stored in spool system).
Waiting
The output request has not yet been processed by the spool system.
Proc.
A spool work process is formatting the output request for printing.
Print.
The output request is being printed by the operating system spooler. If the query
at the host spooler is not activated, this status is shown for around a minute.
2005/Q2
© 2005 SAP AG. All rights reserved.
341
Unit 11: Including Printers in SAP Systems
ADM100
Compl.
The output request has been printed. If the query at the host spooler is not
activated, the status changes to Compl. as soon as the output request is
transferred to the host spooler.
<F5>
There are output requests with various statuses.
Problem
Indicates an error not of a serious nature (such as incomplete character set).
This request was still printed.
Error
Indicates a serious error (such as a network error).
Time
A particular time was specified for the output of the request by the request
creator.
If you select the status of a spool request, the system displays the associated output
requests. For the output requests of multiple spool requests, select these and choose
Output Requests (or choose F5).
For every unsuccessful output request, a log is written that you can use for error
analysis.
Figure 130: Maintaining the Spool Database
342
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Managing Spool Requests
Regular deletion of old spool requests and monitoring the consistency of the spool
database are system administration tasks.
To delete old spool requests, schedule the ABAP program RSPO1041 with an
appropriate variant as a periodically running background job. For more information
about RSPO1041, see SAP Note 130978.
To check the consistency of the spool database, schedule the ABAP program
RSPO1043 with an appropriate variant as a daily running background job. For more
information about RSPO1043, see SAP Note 98065.
For information about the reorganization of TemSe and spool, see also SAP Note
48400.
Overview: Other Print Scenarios
Here is an overview of other print scenarios:
Figure 131: Other Print Scenarios
External Output Management Systems (OMS) can be addressed from the SAP
system using a defined interface (BC-XOM) (access method E). This method is of
particular interest if you have a very large volume, or the output of multiple systems
(SAP systems and others) is to be centrally controlled and monitored. For a list of
all certified products, see http://www.sap.com/softwarepartnerdir (Software Partner
and Product Directory).
2005/Q2
© 2005 SAP AG. All rights reserved.
343
Unit 11: Including Printers in SAP Systems
ADM100
Since SAP Basis 4.0B (as of a particular kernel and Support Package status), you can
send print output by e-mail to a user (access method M). The e-mail is sent using
SAPconnect. For more information, see SAP Notes 311037 and 513352.
A user can also be connected to an SAP system from a Web browser through the SAP
GUI for HTML. A connection of this type can be made directly using the SAP system
(with the integrated ITS, as of SAP Web AS 6.40), through the middleware (Web
server and SAP ITS) of the SAP system, or as part of an enterprise portal (such as
the SAP Enterprise Portal). What options does this user have for print output? One
option is the previously described output by e-mail. On the other hand, Web printing
does not require an e-mail client. You can use Web printing as of SAP Basis 4.6B. To
do this, the system administrator must provide a printer with device type PDF1 and
access method F. If the user selects this printer, a PDF document appears in a new
window. The user can then print this PDF document. SAP Note 351230 describes the
exact prerequisites and contains additional information about Web printing.
344
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Managing Spool Requests
Exercise 19: Managing Spool Requests
Exercise Objectives
After completing this exercise, you will be able to:
•
Manage spool and output requests
Business Example
Task:
2005/Q2
1.
Display a spool request.
2.
Create an output request for the spool request.
3.
Check the status of your output request.
4.
(Optional) Display the generated print data. Instead of checking at operating
system level, you can view the file from the SAP system using transaction AL11
(SAP directory DIR_C_TEMP).
© 2005 SAP AG. All rights reserved.
345
Unit 11: Including Printers in SAP Systems
ADM100
Solution 19: Managing Spool Requests
Task:
1.
Display a spool request.
a)
2.
Create an output request for the spool request.
a)
3.
Select a spool request and choose Print Directly.
Check the status of your output request.
a)
4.
Choose System → Services → Output Control (transaction SP01). Restrict
the output to your spool requests from today (this is the default selection).
Your spool request should have status “-”.
Refresh the list of spool requests. Does the status change to complete? If
not, select the Status field and analyze the log.
(Optional) Display the generated print data. Instead of checking at operating
system level, you can view the file from the SAP system using transaction AL11
(SAP directory DIR_C_TEMP).
a)
Both solutions are described here:
•
•
346
At operating system level, you can use, for example, Notepad
(Start → Run, and then enter notepad) to display the file
C:\temp\Print1.prn or C:\temp\Print2.prn. Note that Notepad cannot
display all printer-specific control characters.
In the SAP system, call transaction AL11 and choose the entry
DIR_C_TEMP at the end of the list. Select the file name (Printfile1 or
Printfile2). This displays the file contents.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Managing Spool Requests
Lesson Summary
You should now be able to:
•
Manage spool and output requests
Related Information
•
•
•
SAP Library: SAP NetWeaver → SAP NetWeaver Technical Operations Manual
→ Administration of the SAP Web Application Servers (ABAP) → Management
→ Printing
SAP Service Marketplace, Quick Link /output
SAP Notes
–
–
–
–
–
2005/Q2
SAP Note 130978: RSPO1041 - Deleting old spool requests
SAP Note 98065: Spool Consistency Check with RSPO1043 as of 4.0A
SAP Note 48400: Reorganization of TemSe and Spool
SAP Note 311037: Printing via e-mail
SAP Note 351230: Frontend printing with HTML GUI/WebGUI
© 2005 SAP AG. All rights reserved.
347
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Describe the architecture and data flow of output processing in the SAP system
•
Create printers and spool servers in the SAP system
•
List important access methods
•
Manage spool requests
•
Describe the concept of logical spool servers
•
Set up logical spool servers
•
Manage spool and output requests
348
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
Which of the following access methods exist in the SAP system?
Choose the correct answer(s).
□
□
□
□
2.
A
B
C
D
Remote printing
Front-end printing
Instance printing
Local printing
Which of the listed states can a spool request have?
Choose the correct answer(s).
□
□
□
□
□
□
2005/Q2
A
B
C
D
E
F
Compl.
Canceled
Error
Waiting
Active
Print.
© 2005 SAP AG. All rights reserved.
349
Test Your Knowledge
ADM100
Answers
1.
Which of the following access methods exist in the SAP system?
Answer: A, B, D
Instance printing does not exist.
2.
Which of the listed states can a spool request have?
Answer: A, C, D, F
The incorrect options canceled and active are possible status messages from job
monitoring. Other possible statuses of a spool request are -, +, Proc., <F5>,
Problem, and Time.
350
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 12
Scheduling Background Tasks
Unit Overview
The topics that this unit deals with are the basics of background processing, and the
scheduling and monitoring of jobs. You will also learn about special functions and
extension options of background processing.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
•
Describe the uses of background processing
Schedule and monitor jobs
Schedule time-dependent jobs
Schedule standard jobs
Schedule event-dependent jobs
Define and trigger events
Use additional, special functions of background processing
Describe how to extend job scheduling using Application Programming
Interfaces
Unit Contents
Lesson: Fundamentals of Background Processing ............................ 352
Exercise 20: Fundamentals of Background Processing................... 361
Lesson: Time-Based Scheduling of Jobs ........................................ 364
Exercise 21: Time-Based Scheduling of Jobs .............................. 369
Lesson: Event-Based Scheduling of Jobs ....................................... 373
Exercise 22: Event-Dependent Jobs......................................... 377
Lesson: Background Processing: Other Topics ................................ 381
Exercise 23: External Program: External Command ...................... 389
Lesson: Job Scheduling: Extending the Standard ............................. 395
2005/Q2
© 2005 SAP AG. All rights reserved.
351
Unit 12: Scheduling Background Tasks
ADM100
Lesson: Fundamentals of Background Processing
Lesson Overview
In this lesson, you will learn about the basics of background processing.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Describe the uses of background processing
Schedule and monitor jobs
Business Example
Reports to be run regularly and long-running programs are scheduled as background
jobs in the SAP system. The administrator schedules background jobs and monitors
the correct process of the system's background processing.
Basics
The following questions are answered in the course of this lesson:
•
•
•
•
•
•
Why do you need background processing?
What is a background job?
What can be performed in the background?
What start criteria are there?
How are jobs scheduled and monitored?
What status can a job have?
Dialog work processes should be able to respond to end users' requests quickly.
Dialog resources should therefore not be burdened with long-running programs. This
can lead to bottlenecks in the dialog response time. The system profile parameter
rdisp/max_wprun_time exists for this reason. It limits the maximum runtime of
a dialog step within a dialog work process. This should ensure that dialog work
processes are not blocked by long-running programs, interfering with online operation.
After the maximum runtime has elapsed, the program is terminated.
352
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of Background Processing
Figure 132: Why Background Processing?
You can use the background work processes for long-running tasks. These are
sometimes also called batch work processes.
Normally, background processing is used not only for long-running, but also for
recurrent tasks. Examples of this type of task are the daily database backup or the
month end work for financial accounting.
2005/Q2
© 2005 SAP AG. All rights reserved.
353
Unit 12: Scheduling Background Tasks
ADM100
Figure 133: What Is a Background Job?
A background job consists of one or more steps (job steps). A step can be:
•
•
•
An ABAP program
An external command
An external program
Every job is processed without interruption by one single background work process.
Background jobs can be scheduled with different priorities:
•
•
•
354
Class A (highest priority)
Class B (medium priority)
Class C (normal priority)
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of Background Processing
If a job should be executed on a particular server or server group, it is handled
preferentially compared to other jobs with the same class. This preference only applies
if multiple jobs of various priorities request background processing at the same time,
for example, because they are scheduled for the same time.
Hint: You should ensure that a large share of all background tasks are
normally scheduled as class C without target server specification. This share
can include 90% (or more) of all tasks. System background tasks are also
executed in this way, such as the tasks that you schedule with transaction
DB13.
Figure 134: What Can Be Performed in the Background?
2005/Q2
© 2005 SAP AG. All rights reserved.
355
Unit 12: Scheduling Background Tasks
ADM100
A step within a job can call one of three actions:
1.
2.
3.
Every ABAP program can be scheduled as a step of a job. If the ABAP program
has one or more selection screens, you must create the input required there in
advance in the form of a variant. A variant makes it possible to run an ABAP
program in the background although the program requires input. The values
stored in the variant are then used during the execution of the program. If an
ABAP program has a screen output as its result, this is directed to a spool list.
You can specify an (e-mail) recipient for this spool list during the definition of
the job. This recipient then receives the output of the job by e-mail after the
job has been run. You must also specify a printer for the creation of a spool
list, although there is not necessarily any direct output to a printer as a result
of background processing (this depends on the printer's access method). This
may have to be explicitly started later.
An external command is a call of a predefined script, a command, or a program
outside the SAP system. With external commands, you can mask operating
system calls and store them in the SAP system under a name. The execution of
an external command can be protected using the SAP authorization concept,
so that certain external commands can only be accessed by particular users in
the system.
An external program is any operating system command. The SAP authorization
concept only specifies whether a user can call external programs or not. A more
detailed authorization assignment, for example at the level of program names, is
not provided; use external commands for this.
Figure 135: Start Criteria for a Background Job
356
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of Background Processing
A job can be triggered:
•
•
By scheduling it on a particular date at a particular time (this includes the start
time immediately, if there are no free background work processes available
when the job is scheduled).
By the occurrence of a particular event defined in the SAP system (this includes
jobs that are to start after other jobs or at operation mode changes, or jobs with
immediate start if there are free background work processes available when
the job is scheduled).
Scheduling and Monitoring
Use transaction SM36 to define new jobs. You can also call the Job Wizard
(transaction SM36WIZ) from transaction SM36.
Figure 136: Job Scheduling
Required specifications when defining a job are:
•
•
•
General specifications such as job name, job priority (Default: C) and
(optionally) target server (group)
Definition of one or more job steps
Definition of start conditions (time- or event-controlled)
The Job Wizard supports you when defining jobs, by leading you through the
individual steps.
2005/Q2
© 2005 SAP AG. All rights reserved.
357
Unit 12: Scheduling Background Tasks
ADM100
However, with the Job Wizard - unlike with classical scheduling - you cannot perform
individual steps with different users.
Figure 137: Job Monitoring
Use transaction SM37 to monitor jobs.
You can select jobs using various criteria on the initial screen of this transaction.
In this way, you can display all jobs that contain a particular job step, that have a
particular status, or that react to a defined event (for this, you must select a particular
event or “*”).
You can navigate to other job-specific views from the job overview:
•
•
•
358
The spool list contains the output lists for ABAP programs (if they exist).
The job details contain, among other information, the job definition, duration of
the processing of the job, and the start time of the job. You can adjust the layout
of the displayed list to your requirements by adding or removing additional fields.
All messages output by a background program are stored in the job log. You
can display this log to obtain information about a program that terminated with
errors or to perform a detailed investigation about a background processing run.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of Background Processing
Figure 138: Status of a Job
A job can have the following statuses:
Scheduled
The steps of the job have already been defined; however, the start condition
must still be defined.
Released
The job has been completely defined, including its start condition. A job cannot
be released without a start condition. Only an administrator or a user with the
relevant authorizations for background processing can release a job. This ensures
that unauthorized users cannot execute jobs without approval.
Ready
The start condition of a released job has been fulfilled. A job scheduler has
placed the job in the wait queue for a free background work process.
2005/Q2
© 2005 SAP AG. All rights reserved.
359
Unit 12: Scheduling Background Tasks
ADM100
Active
The job is currently being executed and cannot be deleted or changed.
If an active job does not seem to be running correctly (that is, for example, it is
running for an exceptionally long time), you can terminate it in a background
work process in debugging mode, analyze it, and then either release it again
or completely terminate it. To do this, in transaction SM37, choose Job →
Capture: active job.
Hint: To capture a background job, you must be logged on to the SAP
server where the job is running.
Finished
All steps of this job were successfully completed.
Canceled
The job terminated. This can happen in two ways:
•
•
An administrator deliberately terminates the job in transaction SM37 by
choosing Job → Cancel active job.
A job step is terminated with an error.
You can still change a job as long as the job still has the status Scheduled or Released.
If the execution of the job has already begun, you can monitor the processing in the
job log. If the job contains ABAP programs that create output lists, these are stored
in spool lists.
You can create a new job by copying an existing job by choosing Job → Copy.
360
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of Background Processing
Exercise 20: Fundamentals of Background
Processing
Exercise Objectives
After completing this exercise, you will be able to:
•
Determine the configuration of your SAP system with regard to background
processing.
Business Example
Reports to be run regularly and long-running programs are scheduled as background
jobs in the system. The administrator schedules background jobs and monitors the
correct process of the system's background processing.
Task: Checking the Configuration
Check the configuration of your SAP system with regard to background processing
The following steps will make you familiar with the settings of the SAP system that
are relevant for background processing:
2005/Q2
1.
How many background processes are configured in your SAP system?
2.
What determines the number of available background work processes?
3.
How many background jobs can be processed simultaneously?
4.
Assume that all background work processes in your system are currently
processing and there are, therefore, no free resources for other jobs. Can you set
up additional background work processes without restarting the SAP system?
© 2005 SAP AG. All rights reserved.
361
Unit 12: Scheduling Background Tasks
ADM100
Solution 20: Fundamentals of Background
Processing
Task: Checking the Configuration
Check the configuration of your SAP system with regard to background processing
The following steps will make you familiar with the settings of the SAP system that
are relevant for background processing:
1.
How many background processes are configured in your SAP system?
a)
2.
Using transaction SM66, check how many work processes of type BTC
your system has (to do this, choose Select process and set the indicator
Status → wait).
What determines the number of available background work processes?
a)
The parameter rdisp/wp_no_btc initially specifies the number of available
background work processes on the current instance. You can check the
value of the parameter with either transaction RZ11 or the report RSPFPAR.
If you have defined operation modes (transaction RZ04), this value can be
overwritten. In this case, use the CCMS Control Panel (transaction RZ03)
to specify the current operation mode.
3.
How many background jobs can be processed simultaneously?
a)
4.
Assume that all background work processes in your system are currently
processing and there are, therefore, no free resources for other jobs. Can you set
up additional background work processes without restarting the SAP system?
a)
362
The SAP system process as many jobs concurrently as there are background
work processes available.
Using the concept of operation modes, you can define an operation mode
with additional background work processes in transaction RZ04. You can
then perform a manual operation mode switch using transaction RZ03. You
do not need to restart your system when doing this.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of Background Processing
Lesson Summary
You should now be able to:
•
Describe the uses of background processing
•
Schedule and monitor jobs
Related Information
•
SAP Notes
–
–
2005/Q2
SAP Note 519059: FAQ: Background Processing System
SAP Note 25528: Parameter rdisp/max_wprun_time
© 2005 SAP AG. All rights reserved.
363
Unit 12: Scheduling Background Tasks
ADM100
Lesson: Time-Based Scheduling of Jobs
Lesson Overview
In this lesson, you will learn about time-based scheduling of jobs.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Schedule time-dependent jobs
Schedule standard jobs
Business Example
The administrator schedules background jobs and monitors the correct process of the
system's background processing.
Time-Based Scheduling
Figure 139: Time-Dependent Start of a Job
A job can be started in a time- or event-dependent manner.
364
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Time-Based Scheduling of Jobs
In the case of a time-dependent start of a job, you can choose between the following
options:
•
•
•
The job should be executed immediately
The job should be executed at a particular date/time
The job should be executed on a particular work day
You can choose to make all time-based start conditions for jobs recurrent. This means
that the job is executed again after a defined period of time has elapsed. You can
specify exceptions (such as postponement to the following work day in the case of
holidays in the factory calendar).
The job is started at the specified date and time, in accordance with the job priority
and availability of background work processes.
You can also specify a time period during which the job should be executed. To do
this, you specify a time after which the job should no longer be executed. With this
function, you prevent periodic jobs being executed at an undesirable time, among
other things. For example, a reorganization job that should only be executed at night
is delayed. With a start time window, you can avoid this job being executed during the
day, when the dialog users are active and there are fewer system resources available.
Load Balancing
The profile parameter rdisp/bctime specifies the time period in which the
time-dependent job scheduler is active (see the next figure). The execution of jobs
with the start condition immediate usually avoids the time-based scheduler. In this
case, the dialog work process of the scheduling user performs the job scheduling. Only
if no free resources are found, is the job concerned scheduled in a time-based way. The
scheduled start time then corresponds to the time point at which it should have started.
2005/Q2
© 2005 SAP AG. All rights reserved.
365
Unit 12: Scheduling Background Tasks
ADM100
Figure 140: Scheduling Jobs and Load Balancing
Background work processes can be configured on every instance of the SAP system
using the profile parameter rdisp/wp_no_btc.
The number of background work processes required in the SAP system depends on the
number of tasks to be performed in the background. If the transport system is used,
there must be at least two background work processes in the system.
The combination of job ID and job name define the job uniquely in the system.
On every SAP instance on which background work processes are defined, the
time-dependent job scheduler runs every rdisp/btctime seconds (Default value: 60
seconds). This is an ABAP program (SAPMSSY2 - an Auto ABAP) that automatically
runs in a dialog work process.
366
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Time-Based Scheduling of Jobs
The time-dependent job scheduler checks the job scheduling table in the database for
jobs that are waiting for processing. These jobs are transferred to free background
work processes in the SAP instance, in accordance with their priority and execution
target.
•
•
Jobs that are not assigned any particular execution target can be executed
with any free background work process. This means that the workload is
automatically distributed between the SAP instances.
If a job is explicitly assigned an execution target (such as a selected instance or a
group of instances), the special properties of the execution target can be used
(for example, you can ensure that a job is performed on a particular operating
system, or that the job is executed by a background work process that is running
on the same host as the database). This means, however, that you do not have the
advantages of automatic load balancing.
Standard Jobs
Standard jobs are background jobs that should run regularly in a production SAP
system. These jobs mainly perform certain clean up jobs in the system, such as the
deletion of obsolete spool requests.
Figure 141: Scheduling Standard Jobs
2005/Q2
© 2005 SAP AG. All rights reserved.
367
Unit 12: Scheduling Background Tasks
ADM100
In the job definition transaction (SM36), you can access a selection of important
standard jobs that you can schedule, monitor, and edit by choosing Standard Jobs
(see figure).
•
•
•
368
If you want to schedule all standard jobs, choose Default Scheduling. All
standard jobs that are defined in table REORGJOBS are scheduled with the
specified variant and period. If other jobs exist that execute one of the programs
of the standard jobs, the system informs you of this.
To schedule individual jobs, choose the selected job with the input help and
specify an execution period.
To define an additional standard job that is not yet available in the selection
(table REORGJOBS), choose Predefine new job.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Time-Based Scheduling of Jobs
Exercise 21: Time-Based Scheduling of
Jobs
Exercise Objectives
After completing this exercise, you will be able to:
•
Schedule time-dependent jobs
Business Example
The administrator schedules background jobs and monitors the correct process of the
system's background processing.
Task 1: Check Profile Parameter
1.
Check the frequency with which the time-dependent job scheduler runs.
Task 2: Creating, Scheduling, and Monitoring a Job
Schedule jobs and monitor their execution. Check the job results.
1.
Run report RSPFPAR in dialog (transaction SA38).
2.
Use transaction SA38 to run report RSPFPAR in the background (start time
Execute immediately).
3.
In transaction SM36, define the job SIMPLE_##, where ## is your group
number. The job should have the following properties:
Job class C
Consists of the ABAP program RSPFPAR as the only step
Immediate start
4.
Check whether your job SIMPLE_## has run successfully.
Find data that gives details about the start time, steps, and job details (such as
client and user name).
Is the spool list automatically printed?
5.
2005/Q2
Determine the execution time of your job SIMPLE_## and find out whether it
was executed with a delay.
© 2005 SAP AG. All rights reserved.
369
Unit 12: Scheduling Background Tasks
ADM100
Solution 21: Time-Based Scheduling of Jobs
Task 1: Check Profile Parameter
1.
Check the frequency with which the time-dependent job scheduler runs.
a)
Check the parameter rdisp/btctime. This parameter specifies the frequency
with which the time-dependent job scheduler runs on your background
server. You can check the value of the parameter with either transaction
RZ11 or the report RSPFPAR.
Task 2: Creating, Scheduling, and Monitoring a Job
Schedule jobs and monitor their execution. Check the job results.
1.
2.
Run report RSPFPAR in dialog (transaction SA38).
a)
On the initial screen of transaction SA38, select the report RSPFPAR,
and choose Execute with Variant.
b)
Use the F4 help to select the variant DISPATCHER and then choose
Execute.
c)
On the next screen, check the entered values, and choose Execute.
Use transaction SA38 to run report RSPFPAR in the background (start time
Execute immediately).
a)
3.
On the initial screen of transaction SA38, enter the report RSPFPAR and
choose Background. On the next screen, use the F4 help to enter the variant
DISPATCHER, and choose Execute immediately. To check the job status
and the spool list for this job, choose Job Overview. The system displays
the initial screen of transaction SM37, on which you can display the results
of your job (Execute button).
In transaction SM36, define the job SIMPLE_##, where ## is your group
number. The job should have the following properties:
Job class C
Consists of the ABAP program RSPFPAR as the only step
Continued on next page
370
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Time-Based Scheduling of Jobs
Immediate start
a)
4.
In transaction SM36, enter the job name SIMPLE_##, select job class C
and leave the Execution target field empty. Choose Step. On the following
screen, choose ABAP Program and enter the ABAP program name
RSPFPAR. Select the variant DISPATCHER and save your step. Then
choose Start Condition. Choose Immediately and save the start time values.
Then save your job. The system displays a message in the status line that
your job was saved with the status: released.
Check whether your job SIMPLE_## has run successfully.
Find data that gives details about the start time, steps, and job details (such as
client and user name).
Is the spool list automatically printed?
a)
Use transaction SM37 to check the status of your job, and choose Execute
on the initial screen. To analyze job details, double click the job and choose
Job Details. The details include, for example, the client, the job ID number,
the user that scheduled, changed, and released the job, and the work process
that executed the job. To view the individual steps of the job, choose Step.
Spool lists are only created 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 during the definition of the
job step or in your user defaults.
5.
Determine the execution time of your job SIMPLE_## and find out whether
it was executed with a delay.
a)
2005/Q2
You can display the duration of your job in transaction SM37 (see solution
to exercise 4). You can also see here whether your job was started with a
delay (caused, for example, by a high load on your system or due to the fact
that the time-dependent job scheduler runs periodically).
© 2005 SAP AG. All rights reserved.
371
Unit 12: Scheduling Background Tasks
ADM100
Lesson Summary
You should now be able to:
•
Schedule time-dependent jobs
•
Schedule standard jobs
Related Information
•
372
For more detailed information about standard jobs, see SAP Note 16083.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Event-Based Scheduling of Jobs
Lesson: Event-Based Scheduling of Jobs
Lesson Overview
In this lesson, you learn about event-based scheduling of jobs.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Schedule event-dependent jobs
Define and trigger events
Business Example
The administrator schedules background jobs and monitors the correct process of the
system's background processing.
Event-Based Scheduling
An event is a signal to the background processing system that a particular status has
been achieved in the SAP system. The background processing system receives events
and then starts all jobs that are linked to this event.
2005/Q2
© 2005 SAP AG. All rights reserved.
373
Unit 12: Scheduling Background Tasks
ADM100
Figure 142: Event-Dependent Start of a Job
An application server is specified for the processing of events that are triggered
within the SAP system in profile parameter rdisp/btcname. An event-dependent job
scheduler is started on this server (unlike the time-dependent job scheduler, which
runs periodically on all background servers). This scheduler checks whether a job
is waiting for the event that has been received. Therefore, it is important that the
parameter rdisp/btcname contains the name of an active background server.
Event-dependent jobs can be scheduled with one of the following three start
conditions:
After event
The job starts after a defined event is received by the SAP system.
At operation mode
With this option, you can link a job to the activation of an operation mode when
scheduling the job.
After job
In this way, you can create simple job chains where the execution of the
successor job can be made dependent on the status of the predecessor job.
374
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Event-Based Scheduling of Jobs
Events
New events are defined by the system administrator in CCMS (transaction SM62).
When doing so, the administrator differentiates between system events and user events.
System events are events predefined by SAP that you can neither modify nor trigger.
Figure 143: Definition and Triggering of Events
Events can be triggered in various ways:
•
•
•
Manually in CCMS for test purposes (transaction SM64)
Within an ABAP program (through use of the function module
BP_EVENT_RAISE)
Outside the SAP system at operating system level using the program sapevt.
A parameter can also be transferred when an event is triggered. In this way, you
can define jobs that wait for the occurrence of the event together with the specified
parameter.
The syntax for the program sapevt is:
sapevt
<event> [-p <parameter>] [-t] [pf=<profile>]
| [name=<SID>] [nr=<instance>]
<event> Name of the event, as defined in CCMS (required)
<parameter> specified parameter (optional)
2005/Q2
© 2005 SAP AG. All rights reserved.
375
Unit 12: Scheduling Background Tasks
ADM100
-t generates a trace file called dev_evt in the directory from which sapevt
was called. If sapevt discovers problems, you can find out about these in this
trace file (optional)
<profile> path name of the profile (optional)
If no profile name is specified, the following parameters must be specified:
<SID> SAP system name (optional)
<instance> instance number of the SAP system (optional)
For example: sapevt MYEVENT name=DEV nr=00.
To be able to react to external events, the SAP system must be active. Otherwise an
event triggered by an external program is lost.
376
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Event-Based Scheduling of Jobs
Exercise 22: Event-Dependent Jobs
Exercise Objectives
After completing this exercise, you will be able to:
•
Schedule event-dependent jobs
•
Define and trigger events
Business Example
The administrator schedules background jobs and monitors the correct process of the
system's background processing.
Task: Event-Dependent Jobs
Define a user-defined event and then schedule a job that starts after this event occurs.
Trigger the event in the Computing Center Management System (CCMS) and from
operating system level.
1.
Define the user-defined event MYEVENT_## in the CCMS.
2.
Define a job EVENT_##. The job should have the following properties:
Job class C
Step 1 Execution of ABAP program RSUSR000
Starts after the event MYEVENT_##, event-periodic.
Display your job in the job overview.
2005/Q2
3.
Trigger the event MYEVENT_## in the CCMS in another session and refresh
the job overview.
4.
Trigger the event MYEVENT_## at operating system level and refresh the
job overview.
© 2005 SAP AG. All rights reserved.
377
Unit 12: Scheduling Background Tasks
ADM100
Solution 22: Event-Dependent Jobs
Task: Event-Dependent Jobs
Define a user-defined event and then schedule a job that starts after this event occurs.
Trigger the event in the Computing Center Management System (CCMS) and from
operating system level.
1.
Define the user-defined event MYEVENT_## in the CCMS.
a)
2.
In the SAP Easy Access Menu, choose Tools → CCMS → Background
Processing → Maintain Events (transaction SM62). Do not change any
System events. Choose Maintain under User event names, and press
ENTER. Choose Create. Enter the event name MYEVENT_<##> (where
<##> is your group number), and a description of the event, and then
choose Save.
Define a job EVENT_##. The job should have the following properties:
Job class C
Step 1 Execution of ABAP program RSUSR000
Starts after the event MYEVENT_##, event-periodic.
Display your job in the job overview.
a)
In transaction SM36, enter the job name EVENT_<##> (where <##> is
your group number), select job class C and leave the execution target empty.
Choose Step. On the following screen, choose ABAP Program and enter
the ABAP program name RSUSR000.
Save your step.
Choose Start Condition.
Choose After Event, enter the event MYEVENT_<##> without other
parameters, set the Periodic job indicator, and save the start time values.
Then save your job. The system displays a message in the status line that
your job was saved with the status: released.
Use transaction SM37 to check whether your job was successfully
processed. To do this, you must make an appropriate selection on the
initial screen of SM37 under the Job Start Condition in the field or after
event (such as “*”).
Continued on next page
378
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Event-Based Scheduling of Jobs
3.
Trigger the event MYEVENT_## in the CCMS in another session and refresh
the job overview.
a)
In the SAP Easy Access Menu, choose Tools → CCMS → Background
Processing → Trigger Event (transaction SM64).
Select your event and trigger it without additional parameters.
If you refresh the job overview in transaction SM37, you can see that your
job has been processed (status finished) and has scheduled itself again
(status released).
4.
Trigger the event MYEVENT_## at operating system level and refresh the
job overview.
a)
2005/Q2
Run the command sapevt MYEVENT_<##> name=<SID>
nr=<nr> at operating system level of your application server. If you
refresh the job overview in transaction SM37 again, you can see that your
job has been processed again (status finished) and has scheduled itself
again (status released).
© 2005 SAP AG. All rights reserved.
379
Unit 12: Scheduling Background Tasks
ADM100
Lesson Summary
You should now be able to:
•
Schedule event-dependent jobs
•
Define and trigger events
380
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
Lesson: Background Processing: Other Topics
Lesson Overview
In this lesson, you learn about other, special functions for background processing.
Lesson Objectives
After completing this lesson, you will be able to:
•
Use additional, special functions of background processing
Business Example
You want to use the background processing resources more efficiently.
Reservation for Class A Jobs
In normal operation, every background work process processes jobs of every priority.
You can, however, reserve as many of the configured background work processes as
desired for high priority jobs; that is, class A jobs. The reservation of work processes
for class A jobs does not reserve any particular work processes. Rather it ensures
that a particular number of work processes is always kept free. Jobs of job classes
B and C can only be started if the defined number of work processes remains free
for possible class A jobs.
2005/Q2
© 2005 SAP AG. All rights reserved.
381
Unit 12: Scheduling Background Tasks
ADM100
Figure 144: Reservation for Class A Jobs
To set the number of reserved background work processes for class A, you can
define an operation mode in transaction RZ04 (maintenance of operation modes and
instances) and maintain the work process allocation for this operation mode. When
doing so, you have the option of reserving work processes.
If the class A workload is small, or bottlenecks rarely occur in background processing
- in other words, at least one background work process is usually free - the reservation
of a work process for class A jobs probably provides no advantages. In this case,
reservation will simply mean that a work process is seldom used.
SAP strongly recommends that you do not reserve more than one background work
process for processing class A jobs. It is usually sufficient to reserve one background
work process for processing class A jobs.
Execution Targets
Only instances with background work processes or a job server group can be used for
the targeted scheduling of a background task.
A job server group contains one or more instances with available background work
processes. Groups of this type can be used in the same way as logon groups for dialog
users. It is also possible to process background tasks from different applications on
selected instances.
382
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
Figure 145: Execution Targets and Job Server Groups
You can set up a job server group in transaction SM61 (Path: Tools → CCMS →
Background Processing → Background Objects). To do this, call the transaction
and then choose the Job Server Groups. You can then define your job server group
and assign your instances.
Background Users
With the classic definition of jobs using transaction SM36, you can assign each step of
the job to a user (see the figure). The specified user is used for the authorization checks
during the execution of the step. By default, the name of the logged-on user appears
in this field, and your job is performed using your authorizations. Enter a different
user name, if your job should not be performed using your own authorizations. To be
able to do this, you must, however, have the appropriate authorization (authorization
S_BTCH_NAM) to enter names other than your own in the User field.
2005/Q2
© 2005 SAP AG. All rights reserved.
383
Unit 12: Scheduling Background Tasks
ADM100
Figure 146: Background Users
It is useful to set up background users for various work areas that have the necessary
authorizations for the required activities, and that can be used by users with the same
authorizations to schedule background tasks in this work area (such as for system
administration). Background users have user master records that are specifically
intended for background processing authorizations.
Use the System user type when creating background users. A dialog logon with a
user of this type is not possible. In the same way, users of this type are exempt from
the usual settings for the validity period of a password. The password can only be
changed by user administrators using transaction SU01 (Users → Change Password).
The name of the logged-on user is always used for the authorization check when
a job is defined using the Job Wizard.
Use of External Programs
The background processing system differentiates between external commands for
normal users and external programs for system administrators. The purpose of this
differentiation is to give system administrators the ability to run any required external
program, while normal users are restricted to external commands for which there
are authorization checks. In both cases, the program sapxpg is called at operating
system level and starts the relevant program at operating system level.
384
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
Figure 147: Using External Programs
External commands are host system commands or programs predefined in the SAP
system by an administrator. They are protected by authorizations so that normal users
can only schedule the commands for which the system administrator has assigned
them the authorization. You can, therefore, provide functions outside the SAP system,
at operating system level, for users of the SAP system.
External programs are unrestricted commands that are neither predefined nor
restricted by authorizations. A user with administration authorization can enter any
external program in a job step. No SAP authorization check is performed before
the execution of the command. External programs provide an administrator (user
with administration authorization for external commands (Authorization object
S_RZL_ADM: Background Processing: Background Administrator)) the flexibility
to run any required host system command in the SAP system without administrative
preparation.
2005/Q2
© 2005 SAP AG. All rights reserved.
385
Unit 12: Scheduling Background Tasks
ADM100
Figure 148: Definition and Use of External Commands
386
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
The creation of external command requires the following steps:
1.
2.
3.
4.
5.
6.
7.
8.
Call transaction SM69 (Tools → CCMS → Configuration → Display/Change
External Commands).
Choose Display/Change and then the Create button.
Enter a name for your command. External commands are uniquely identified
with a name (beginning with Y or Z) and an operating system type. The Type
field fills automatically.
Specify an executable operating system command (if required with the complete
path) and specify any additional required or optional parameters.
Select the Additional parameters allowed field if users can specify additional
parameters when they schedule the command in a background job. The
additional parameters are added in parameter strings specified under Parameters
for Operating System Command.
The Trace field should usually be left blank. To follow the execution of
an external command, use the trace parameter for the function module
SXPG_COMMAND_EXECUTE.
If you have defined an additional authorization check, enter the name of the
function module that performs the check under Check Module, usually a
customer copy of the function module SXPG_DUMMY_COMMAND_CHECK.
The system automatically calls the function module if a user tries to schedule the
external command in a background job.
Save the external command both in the previous screen nd in the initial screen
of transaction SM69.
Control Flags
You can make specifications about the task and other runtime options using control
flags. You do not normally need to change the default values.
2005/Q2
© 2005 SAP AG. All rights reserved.
387
Unit 12: Scheduling Background Tasks
ADM100
Figure 149: Control Flags for External Programs/Commands
You can, for example, specify:
•
•
Whether the process is to be logged. The output data is written to the log as it is
output by the external program. The language can differ here from your logon
language. You can also call additional information about the data of an external
program in the job log.
How the SAP control program should end and whether the external program
triggers an event. After you have started service programs with the background
processing system (such as daemons in UNIX systems), they remain active after
the start. They are not ended and do not return to the SAP background processing
system, as is the case with other programs. If you start a service program, you
should not use the control flag setting Job waiting for ext. termination when
scheduling the job.
You can display additional information about the meaning of the control flags using
the F1 field help on the Edit Control Flags for External Programs screen.
388
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
Exercise 23: External Program: External
Command
Exercise Objectives
After completing this exercise, you will be able to:
•
Schedule external commands and external programs as jobs
Business Example
Task 1: Check the Configuration
1.
Find out if background work processes are reserved for class A jobs in your
system.
Task 2: Schedule an External Program
Schedule an external program.
1.
Define the job WHOAMI_<##>, where <##> is your group number. The job
should have the following properties:
Job class C
Execution of the external program whoami (check the control flags for this)
Start in 2 minutes (referring to system time)
Check whether the job was successfully processed.
Task 3: External Command and Job Chain (Optional)
Schedule a job, SUCCESSOR_<##> that executes an external command ZKERNEL
as a job step.
1.
Display a list of external commands. What does the command ZKERNEL do?
2.
Define a job SUCCESSOR_<##>. The job should have the following properties:
Job class C
Execution of the external command ZKERNEL.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
389
Unit 12: Scheduling Background Tasks
ADM100
Start after the job EVENT_<##> from the previous exercise has been
successfully completed.
Display the job in the job overview and view the job log.
3.
390
What must you do so that the job SUCCESSOR_<##> is executed?
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
Solution 23: External Program: External
Command
Task 1: Check the Configuration
1.
Find out if background work processes are reserved for class A jobs in your
system.
a)
You can only check whether you have defined background work processes
for jobs of job class A using transaction RZ04 (Maintain Operation Modes
and Instances). Choose Instances/Operation Modes there and check
column BPA.
Task 2: Schedule an External Program
Schedule an external program.
1.
Define the job WHOAMI_<##>, where <##> is your group number. The job
should have the following properties:
Job class C
Execution of the external program whoami (check the control flags for this)
Start in 2 minutes (referring to system time)
Check whether the job was successfully processed.
a)
In transaction SM36, enter the job name WHOAMI_<##>, select job class
C and leave the execution target field empty.
Choose Step. On the next screen, choose External Program and enter the
program name whoami without parameters. Enter the host name of your
application server as the target host. Check the Control flags and save
the default values. Save your step.
Return to the initial screen of the transaction and choose Start Condition.
Choose Date/Time and enter a time that is approximately two minutes
in the future and save the start time values. Then save your job. The
system displays a message in the status line that your job was saved with
the status: released.
Check in transaction SM37 whether your job was successfully processed.
To do this, display the job log for the job.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
391
Unit 12: Scheduling Background Tasks
ADM100
Task 3: External Command and Job Chain (Optional)
Schedule a job, SUCCESSOR_<##> that executes an external command ZKERNEL
as a job step.
1.
Display a list of external commands. What does the command ZKERNEL do?
a)
To display a list of external commands, choose Tools → CCMS →
Background Processing → Execute External Commands (transaction
SM49) from the SAP Easy Access menu. To execute a command from this
list, select the command, and choose Execute. On the following screen, you
can specify a target host. Choose Execute again.
The external command ZKERNEL displays information about the kernel
(disp+work).
2.
Define a job SUCCESSOR_<##>. The job should have the following properties:
Job class C
Execution of the external command ZKERNEL.
Start after the job EVENT_<##> from the previous exercise has been
successfully completed.
Display the job in the job overview and view the job log.
a)
In transaction SM36, enter the job name SUCCESSOR_<##> (where
<##> is your group number), select job class C and leave the execution
target empty.
Choose Step. On the following screen, choose External Command and
enter the name ZKERNEL with no other parameters.
Use the F4 help to select an operating system and specify the host name of
your application server as the target host. Save your step.
Choose Start Condition. Choose After Job, enter the predecessor job
EVENT_<##>, and choose Start status-dependent. Save your start time
values. Then save your job. The system displays a message in the status
line that your job was saved with the status: released.
Use transaction SM37 to check whether your job was successfully
scheduled. To ensure that your job also displays in the job overview,
choose Extended Job Selection on the initial screen of transaction SM37.
On the following screen, select your predecessor job (or “*”) in the field or
start after job on the Start condition tab page and choose Execute.
Continued on next page
392
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Background Processing: Other Topics
3.
What must you do so that the job SUCCESSOR_<##> is executed?
a)
Trigger the event MYEVENT_<##> in another session, in the same way
as in the previous exercise. Check that your job chain was successfully
executed by refreshing the job overview.
Display the job log for the job.
2005/Q2
© 2005 SAP AG. All rights reserved.
393
Unit 12: Scheduling Background Tasks
ADM100
Lesson Summary
You should now be able to:
•
Use additional, special functions of background processing
Related Information
•
SAP Notes
–
–
394
SAP Note 24092: Distribution of background jobs on application server
SAP Note 101146: Batch: Authorization object S_BTCH_JOB,
S_BTCH_NAM
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Job Scheduling: Extending the Standard
Lesson: Job Scheduling: Extending the Standard
Lesson Overview
In this lesson, you learn about the resources with which you can extend the standard
functions for job scheduling.
Lesson Objectives
After completing this lesson, you will be able to:
•
Describe how to extend job scheduling using Application Programming
Interfaces
Business Example
You want to extend the standard functions available for background processing in the
SAP system.
Extending the Standard
The job scheduling options described in the previous lessons do not cover all possible
requirements. You can implement more complex scenarios in the following ways:
The SAP system has various internal function modules that support you when defining
your own job processes. These function modules are in the function groups BTCH and
BTC2. You can define any complex scenarios with the help of these function modules.
SAP provides a set of interfaces that allow the connection of other system management
environments to the SAP Computing Center Management System (CCMS):
•
•
The eXternal Monitoring Interface API (XMI-API) interface logs the activities
of external users and programs.
The eXternal interface for Background Processing (XBP-API) interface allows
the use of external job scheduling programs.
With these tools, you can schedule background jobs beyond the boundaries of the SAP
system and include non-SAP systems.
2005/Q2
© 2005 SAP AG. All rights reserved.
395
Unit 12: Scheduling Background Tasks
ADM100
Figure 150: Extending the Standard
For a list of certified solutions, see the the software category Job Scheduling in the
Software Partner Directory.
396
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Job Scheduling: Extending the Standard
Lesson Summary
You should now be able to:
•
Describe how to extend job scheduling using Application Programming
Interfaces
2005/Q2
© 2005 SAP AG. All rights reserved.
397
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Describe the uses of background processing
•
Schedule and monitor jobs
•
Schedule time-dependent jobs
•
Schedule standard jobs
•
Schedule event-dependent jobs
•
Define and trigger events
•
Use additional, special functions of background processing
•
Describe how to extend job scheduling using Application Programming
Interfaces
398
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
A background job contains one or more
. An ABAP program or
command or program can be executed in a
of
an
this type. A job can be triggered at a particular
or when a defined
occurs.
Fill in the blanks to complete the sentence.
2.
What status can a job have?
Choose the correct answer(s).
□
□
□
□
□
□
3.
A
B
C
D
E
F
Running
Released
Waiting
Finished
Error
Active
Which of the listed options for time-dependent scheduling of a job can be
implemented with the standard resources of the SAP system?
Choose the correct answer(s).
□
□
□
□
□
4.
A
B
C
D
E
Daily at 1500
The second-last working day of every month
Every nine days, but not on Sundays
Only tomorrow at 2355
Every year on April 1 at 0800
Which of the listed options for event-dependent scheduling of a job can be
implemented with the standard resources of the SAP system?
Choose the correct answer(s).
□
□
□
□
2005/Q2
A
B
C
D
Whenever the system switches to the Night operation mode
After the job Job1 has run successfully
Whenever a particular event has been triggered
Whenever the periodic job Job2 has run successfully
© 2005 SAP AG. All rights reserved.
399
Test Your Knowledge
5.
ADM100
If one of the system's ten background work processes is reserved for class A
jobs, and jobs are being processed in the other nine work processes, the reserved
work process remains free even if a class A job is waiting for execution.
Determine whether this statement is true or false.
□
□
6.
True
False
If a user has authorization to schedule an external program as a step of a
background job, he or she can run any operating system command.
Determine whether this statement is true or false.
□
□
400
True
False
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Answers
1.
A background job contains one or more steps. An ABAP program or an external
command or program can be executed in a step of this type. A job can be
triggered at a particular time or when a defined event occurs.
Answer: steps, external, step, time, event
After the job is triggered, it is processed without interruption by a single
background work process.
2.
What status can a job have?
Answer: B, D, F
In addition to the three correct answers, a job could have the status Scheduled,
Ready, or Canceled.
3.
Which of the listed options for time-dependent scheduling of a job can be
implemented with the standard resources of the SAP system?
Answer: A, B, C, D, E
All of the options listed can be realized by default.
4.
Which of the listed options for event-dependent scheduling of a job can be
implemented with the standard resources of the SAP system?
Answer: A, B, C
Option D cannot be realized in the standard system. However, you can
implement this as one of many additional possibilities by extending the standard
system using function modules.
5.
If one of the system's ten background work processes is reserved for class A
jobs, and jobs are being processed in the other nine work processes, the reserved
work process remains free even if a class A job is waiting for execution.
Answer: False
The work processes that are reserved for class A jobs process class A jobs. The
option to reserve work processes for class A jobs should only prevent all work
processes being occupied with class B or C jobs.
2005/Q2
© 2005 SAP AG. All rights reserved.
401
Test Your Knowledge
6.
ADM100
If a user has authorization to schedule an external program as a step of a
background job, he or she can run any operating system command.
Answer: True
If you do not want, as an administrator, to assign this critical authorization, but
want to enable your users to run a specific operating system command, you can
define an external command in the SAP system.
402
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 13
Archiving
Unit Overview
You can use data archiving in the context of SAP NetWeaver to securely store
application data that is no longer required for day-to-day activities outside the
database. This stored data is stored in archive files, which you can access later.
The result is a slim database, which can be more efficiently and cost-effectively
administered in the long-term.
This unit provides you with an initial insight into the basics of SAP data archiving.
You will perform a simple data archiving task and then use the SAP system to access
the archived data.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
•
Define the term data archiving
Explain the need for data archiving
Outline the technical process of data archiving
List individual steps of data archiving
Perform basic functions to customize SAP data archiving
List different options for accessing archived data
Evaluate options of the SAP Archive Information System
Unit Contents
Lesson: Fundamentals of SAP Data Archiving ................................. 404
Lesson: Performing Data Archiving .............................................. 411
Exercise 24: Perform Data Archiving ........................................ 417
Lesson: Accessing Archived Data ................................................ 425
Exercise 25: Access Archived Data.......................................... 429
2005/Q2
© 2005 SAP AG. All rights reserved.
403
Unit 13: Archiving
ADM100
Lesson: Fundamentals of SAP Data Archiving
Lesson Overview
Data archiving is used to remove large quantities of data that is no longer required in
the system, but which is to be retained in an analyzable format. This lesson defines the
term data archiving, and explains the reasons for implementing an archiving project.
The process of data archiving will also be outlined.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
•
Define the term data archiving
Explain the need for data archiving
Outline the technical process of data archiving
Business Example
The management team of your company has decided to implement SAP data
archiving. As a member of the system administration team, you want to learn about
the fundamentals of data archiving.
Introduction
With current database systems, a large data volume can often lead to performance
bottlenecks, which cause bad performance on the user side, and increased resource
costs on the administration side. Data that is no longer required in the database for
applications should therefore be removed from the database. However, it is often not
possible simply to delete the data, as read access to the data is still frequently required.
The data must therefore be stored outside the database on external storage media so
that it can later be read again.
Definition of Data Archiving
Data Archiving means the consistent removal of data objects from database tables of
the SAP system database, where all table entries that characterize a data object are
written to an archive file outside the database. Business consistency is ensured by
SAP archiving programs that store all relevant table entries together on the basis of
archiving objects.
404
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of SAP Data Archiving
The contents of business objects of the SAP system are distributed across multiple
tables in the database. Archiving objects bundle logically connected tables of business
objects. This ensures, in the context of data archiving, that all information for a
business object is stored outside the database and therefore deleted from the database.
The following figure clarifies the connection between database tables, business
objects, and archiving objects. The application data removed from the SAP system
database is compressed and stored in a different location (such as a file system).
The data is archived in online mode; that is, you do not need to shutdown the system
during the archiving.
Figure 151: What is Data Archiving?
Since the term archiving is used in an undifferentiated way in the IT world, this
section examines a number of other important terms in the data archiving environment
in order to create a distinction between these terms and data archiving. In particular,
data archiving is not
•
•
•
•
2005/Q2
Reorganization
Backup / Restore
Document storage (usually using SAP ArchiveLink)
Deletion of test data
© 2005 SAP AG. All rights reserved.
405
Unit 13: Archiving
ADM100
The term reorganization has a double meaning within the SAP world (historically,
due to SAP R/2). On one hand, this can mean the physical deletion of application data
from the database, on the other - and this is the actual meaning - this term means
the reorganization of the database. During the reorganization of the database, the
data is unloaded from the database and then reloaded, to optimize the physical data
distribution on the hard disk.
A backup is the backing up of the database contents in case of system breakdowns.
The aim is to restore the database status to as close to the status that was current before
the breakdown. Backups are usually performed at fixed time intervals and follow a
fixed procedure. The process of reloading the backed up data is called a restore.
Database backups are independent of the data archiving and should be scheduled and
performed at regular intervals.
Document storage means the general electronic storage and management of
documents on storage systems outside the SAP system. The documents are transferred
to a document storage system. Only a pointer that links to the stored documents and
allows access is administered in the SAP system.
SAP ArchiveLink is a data interface integrated into the SAP Web Application Server
that controls communication with storage systems.
Only data from completed business processes can be archived. Test data rarely
achieves this status.
Reasons for Data Archiving
The larger a database is, the higher the cost for database administration with regard to
recovery or backup. Securing the SAP system services requires ever more resources.
Upgrades of the system or database also become disproportionately more expensive
with an increasing database size.
For end users, an increasing database size means a higher system load for individual
database queries; that is, increasing response times for reporting and access to
individual database records.
Hint: Full table scans, in particular, are accelerated by data archiving, but
access using indexes can also be appreciably accelerated by data archiving.
The main effect in this case is that a reduction of the disk requirement for
an index improves the quality of the database's data buffer. This effect is
especially pronounced for indexes that are likely to be accessed using any of
their fields. This includes all indexes that are not created in a chronologically
sorted format (such as using the document number).
406
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of SAP Data Archiving
The reasons for data archiving are summarized in the following list:
•
•
•
•
Improve response times or ensure good response times
Reduce costs for database administration
Reduce system downtime for software upgrades, recoveries, and (offline) data
backups
Legal requirements and business requirements must be taken into account here,
such as:
–
–
–
Country-specific retention rules
Data must be available to auditors
Potential reusability of data
Data must be archived in a way that means it can be called at any time for queries.
These queries could, for example, be from tax authorities. There are legal data
retention requirements in each country. Also, only data from completed business
processes can be archived.
With data archiving, data is archived independent of the hardware and software
release statuses (metadata is stored). In this way, it is still possible to call archived
data without any problems even after a system upgrade.
Cooperation Between the System Administration and
User Departments
You should begin planning the archiving of application data during the implementation
of SAP software. The volume of transaction and master data can increase very quickly
when live operation is first started.
The system administration's aim is to keep the database as small as possible; that is, to
delete as many data objects as possible to reduce the database load. The aim of user
departments, on the other hand, is to be able to access as many documents as possible
online for queries, lists, and reporting.
The process of data archiving is about finding a compromise between these two
positions that satisfies both sides. The long-term aim must certainly be to maintain as
constant as possible a volume of data in the database and to archive data proactively
instead of reactively.
2005/Q2
© 2005 SAP AG. All rights reserved.
407
Unit 13: Archiving
ADM100
Schematic Process of a Data Archiving Run
The actual data archiving is a process in three steps:
1.
2.
3.
Creating the archive file(s): In the first step, the write program creates one (or
more) archive file(s). The data to be archived is then read from the database and
written to the archive file(s).
Storing the archive file(s): After the write program has completed the creation of
the archive files, these can be stored.
Deleting the data: the delete program first reads the data in the archive file and
then deletes the corresponding records from the database.
Figure 152: The Archiving Process
You must also consider the fact that it is usually not sufficient to write the data to be
archived to archive files and to delete it from the database. The archive files must be
stored securely and be managed to ensure that they are accessible later if required.
408
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Fundamentals of SAP Data Archiving
There are a number of options for the storage of archive files (see step 2):
•
•
•
2005/Q2
Hierarchical Storage Management (HSM) systems: If an HSM system is used, it
is sufficient to maintain the appropriate file path in Customizing (transaction
FILE). It is left to the HSM system to store the files on an appropriate storage
medium, depending on frequency of access and disk space utilization.
Optical archiving: This term refers to electronic storage and management
of documents on storage systems outside the SAP system landscape. These
documents are usually physically stored on optical media, such as CDs. This is
where the name originates.
Manual storage: After the deletion program has processed the relevant archive
file, it can be manually placed on tape.
© 2005 SAP AG. All rights reserved.
409
Unit 13: Archiving
ADM100
Lesson Summary
You should now be able to:
•
Define the term data archiving
•
Explain the need for data archiving
•
Outline the technical process of data archiving
Related Information
For more information about data archiving, see:
•
•
•
410
The online documentation in the Introduction to Data Archiving section
(CA-ARC)
SAP course BIT660 (Data Archiving)
The SAP Service Marketplace under the Quick Links /data-archiving and
/archivelink
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
Lesson: Performing Data Archiving
Lesson Overview
This lesson presents the main features of the Customizing required to perform data
archiving. A simple data archiving is then performed, in which the data to be archived
is written to a file at operating system level.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
List individual steps of data archiving
Perform basic functions to customize SAP data archiving
Business Example
The management team of your company have decided to implement SAP data
archiving. As a member of the system administration team, you want to learn about
the process of data archiving.
The Archiving Object
A central element of data archiving is the archiving object. It defines the smallest unit
that can be completely archived and deleted from the database, and describes which
database objects must be accessed, and how, to completely archive a business object.
An archiving object essentially consists of three components:
•
•
•
Data declaration component
Customizing settings
Programs
All relevant database objects that characterize an application object are described in
the data declaration component.
The archiving object-specific parameters for an archiving run are set using the
Customizing settings.
2005/Q2
© 2005 SAP AG. All rights reserved.
411
Unit 13: Archiving
ADM100
The programs of an archiving object include, among other things:
•
•
•
A write program that writes the data objects sequentially to the archive files
A delete program that deletes all data objects from the database that were first
successfully read in the archive file
A display program that allows the reading of archived data objects
Hint: Transaction DB15 (menu path Tools → CCMS → DB Administration
→ Data Archiving) provides information about which database tables are
associated with which archiving object (and which archiving objects are
associated with which database table).
Customizing Settings
During Archiving Customizing, you set parameters that affect the execution of data
archiving. Customizing is structured into the following areas (examples are given
for each):
•
General Customizing (Basis Customizing)
•
–
Defining logical path and file names
Cross-archiving object Customizing
•
–
Define the server group for background processing
Archiving Object-Specific Customizing
–
–
Size of an archive file
Settings for the delete program
You can call the Customizing settings by choosing the Customizing button on the
initial screen of transaction SARA (Archive Administration, menu path Tools →
Administration → Administration → Data Archiving).
In the general Customizing (Basis Customizing, switch to the transaction FILE), you
first define - if it does not already exist - a logical file path as the global path for data
archiving and assign a physical path to this logical path. The logical path acts only as
a placeholder for the physical path created at runtime.
Hint: The physical path assigned to the logical path can be
maintained separately for each operating system utilized (such as
<P=DIR_GLOBAL>\<FILENAME> for Microsoft Windows NT). The SAP
system automatically identifies which path is actually used at runtime.
412
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
You also maintain a logical file name here for naming the archive file for the archiving
of application data and assign it a physical file name that is generated at runtime
and used as the file name.
In Cross-Archiving Object Customizing, you can specify, among other things,
whether the data archiving monitor in CCMS monitoring (transaction RZ20) should
be active, or which server group is selected for background processing (this setting is
new as of SAP Web Application Server 6.10).
In Archiving Object-Specific Customizing, you maintain a logical file name for the
specific archiving object and settings for the delete program. You can set whether the
delete program is to be automatically executed after the creation of an archive file. In
this area, you also create a variant for the test run and a variant for the production run,
and specify the maximum size of an archive file, among other things.
The following figure illustrates the relationship between the name of the archiving
object and the stored logical and physical file and path name.
Figure 153: Basis Customizing (transaction FILE) and Application-Specific
Customizing (transaction SARA)
2005/Q2
© 2005 SAP AG. All rights reserved.
413
Unit 13: Archiving
ADM100
The Archiving Run
The actual archiving run is scheduled and processed as a background job. It selects
the data objects from the database. When doing this, the integrity conditions that
characterize a data object are taken into account. The system then checks whether
each data object can be archived. If it can be archived, the data object is written to
the archive file. If the Customizing settings specify that the delete program is to run
automatically, the associated deletion run is automatically started when a file is closed.
Hint: If the delete program is scheduled in parallel to the write program,
there should be at least two background work processes configured on the
SAP system.
The delete run must be separately scheduled, if the delete program is not automatically
run by the settings in the archiving object-specific Customizing. When scheduling
separately, you must also select the archive files, from which the data objects are to be
read in the current delete run, and then deleted from the database.
An archiving run is scheduled using transaction SARA by choosing the Write button.
It is divided into four steps:
1.
2.
3.
4.
Create an archiving variant
Specify the execution user
Specify the start time
Definine the spool parameters
The data that is to be archived for the selected archiving object is specified in
archiving variants. In principle, archiving variants can only be reused if the
associated jobs are deleted. The definition of the variant must also specify whether it
is a test run or a production run.
The user under which the archiving program is started requires at least an appropriate
authorization for the authorization object S_ARCHIVE. S_ARCHIVE is the main
authorization object used for data archiving. By selecting the corresponding field
entries for this authorization object, you can restrict the archiving objects to be used.
The user also requires the relevant authorizations for the application transaction
for which data is to be archived. As data archiving runs in the background, the
user also requires authorizations for background processing (authorization object
S_BTCH_JOB).
The start times to be specified for archiving jobs are the same as those for standard
job scheduling.
414
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
Since job logs can become large, it is advisable to set under Spool Parameters that
the log is not immediately output on the output device. The selection options are the
same as the standard background printing parameters.
Monitoring an Archiving Run
There are various system administration tools available to monitor archiving runs:
•
Background processing tools
•
–
Job logs
–
Spool lists (if created)
System monitoring tools
–
Data Archiving Monitor in the CCMS monitor sets
A log is created during an archiving run. If the application creates a specific log, this
is used; otherwise, the standard log is used. The standard logs contains the number
of archived data objects, the affected tables, the number of processed table entries,
and the file sizes. The contents of the archiving can be stored to document level in
application-specific logs.
Note: The archiving logs are deleted by the regular cleaning of spool jobs.
You must therefore consider the destination of these logs. You could, for
example, store the logs on an external storage system.
You can trace the process of an archiving run with the monitoring of the background
work processes using the transaction Simple Job Selection (transaction code SM37).
By choosing Job Overview, you can move directly from the initial screen of
transaction SARA to transaction SM37. By choosing Management (after you have
maintained an appropriate archiving object on the initial screen of transaction SARA),
you can display a short log file of an archiving run from transaction SARA.
In addition, there is a specific data archiving monitor (monitor Data Archiving in the
monitor set SAP CCMS Monitor Templates) in the CCMS monitor sets (transaction
RZ20). It is intended for system administrators, so that they can monitor archiving
runs in their familiar environment, the CCMS monitor. You can use the Data
Archiving monitor to obtain an overview of the archiving objects in the system for
which there are already runs. You can use the cross-archiving object Customizing to
activate or deactivate it.
2005/Q2
© 2005 SAP AG. All rights reserved.
415
Unit 13: Archiving
416
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
Exercise 24: Perform Data Archiving
Exercise Objectives
After completing this exercise, you will be able to:
•
Check basic Customizing settings for SAP data archiving
•
Schedule and monitor a simple archiving run
Business Example
Your company uses SAP data archiving to reduce the size of the database for the SAP
system and therefore to ensure good response times long-term. As a member of the
system administration team, it is your task to schedule an archiving run.
Task 1: Check Archiving Object
To prepare an archiving run, determine what database tables are associated with
what archiving object.
1.
Check the tables from which data is archived for the archiving object
Workitem.
Task 2: Check Customizing Settings
Check the Customizing settings for the archiving run.
1.
In Basis Customizing, ensure that a logical path exists as the global
path for data archiving, note its name, and assign the physical path
<P=DIR_GLOBAL>\<FILENAME> to this logical path for the Microsoft
Windows NT operating system (or assign an appropriate path name if your SAP
system is not running on a Microsoft Windows NT server).
2.
In Basis Customizing, ensure that the logical file name
ARCHIVE_DATA_FILE is assigned the physical file name
<PARAM_1>_<PARAM_3>_<DATE>_<TIME>_<PARAM_2>.ARCHIVE and
the logical path ARCHIVE_GLOBAL_PATH.
3.
In archiving object-specific Customizing for the WORKITEM archiving object,
define a variant for test mode and a variant for production mode (with the names
TEST_## and PROD_##, where ## is your group number), and maintain the
process control appropriately for these variants. Then maintain the attributes of
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
417
Unit 13: Archiving
ADM100
the variants and save the variants. Ensure that the delete job is not scheduled.
You should also ensure that the logical file name ARCHIVE_DATA_FILE is
assigned to the object name WORKITEM.
Task 3: Start the Write Program
From the SAP system, generate an archive file for the archiving object WORKITEM.
To do this, schedule the write program, run it, and monitor its processing.
1.
Create a variant for the write program. Name the variant Write_##, where ##
is your group number. Maintain the process control for the variant so that an
Archive and Delete is executed. Then schedule the write program with the start
time Immediate and the predefined spool parameters.
2.
Display the spool list and the job log of the archive run.
3.
Check whether an archiving file was created at file system level.
Task 4: Start Delete Program
Now delete the objects archived in the previous task from your database. To do this,
schedule the delete program, run it, and monitor its processing.
418
1.
Start the delete program from transaction SARA by running it under your own
user. Maintain the archive selection, the start time, and the spool settings so that
you select the archive you created in task 3, start the delete program immediately,
and leave the spool parameters unchanged.
2.
Monitor the processing of your delete program by displaying the spool list.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
Solution 24: Perform Data Archiving
Task 1: Check Archiving Object
To prepare an archiving run, determine what database tables are associated with
what archiving object.
1.
Check the tables from which data is archived for the archiving object
Workitem.
a)
Call the transaction Tables and Archiving Objects (transaction code DB15
, menu path Tools → CCMS → DB Administration → Data Archiving).
Select Tables From Which Data Is Archived. In the Tables in Object input
field, enter WORKITEM and choose Enter.
The system displays the tables (such as SWP_HEADER) from which
objects are archived.
Task 2: Check Customizing Settings
Check the Customizing settings for the archiving run.
1.
In Basis Customizing, ensure that a logical path exists as the global
path for data archiving, note its name, and assign the physical path
<P=DIR_GLOBAL>\<FILENAME> to this logical path for the Microsoft
Windows NT operating system (or assign an appropriate path name if your SAP
system is not running on a Microsoft Windows NT server).
a)
Call transaction Archive Administration (transaction SARA, menu path
Tools → Administration → Administration → Data Archiving) and
choose Customizing. On the next screen, select the row Cross-Client File
Names/Paths in Basis Customizing. Now choose Execute at the left of the
row. Confirm the dialog box. By doing so, you call transaction FILE. On
the screen Change View Logical File Path Definition: Overview, select
Logical File Path Definition. Then check on the right of the screen whether
the entry with the Name Global path for archiving exists. The
logical file path ARCHIVE_GLOBAL_PATH should be defined for this
entry. Select this row and, in the tree structure on the left of the screen,
choose the path Logical File Path Definition → Assignment of Physical
Paths to Logical Paths, by choosing Assignment of Physical Paths to
Logical Paths. Then select WINDOWS NT on the right of the screen and
ensure (if necessary, by changing the entry) that the Physical path field
contains the entry <P=DIR_GLOBAL>\<FILENAME>.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
419
Unit 13: Archiving
ADM100
2.
In Basis Customizing, ensure that the logical file name
ARCHIVE_DATA_FILE is assigned the physical file name
<PARAM_1>_<PARAM_3>_<DATE>_<TIME>_<PARAM_2>.ARCHIVE and
the logical path ARCHIVE_GLOBAL_PATH.
a)
3.
In the left of the screen in transaction FILE, double click the folder
Logical File Name Definition, Cross-Client. Then double click
the entry ARCHIVE_DATA_FILE in the table on the right of
the screen. On the following screen, check that the logical file
ARCHIVE_DATA_FILE is assigned the physical file
<PARAM_1>_<PARAM_3>_<DATE>_<TIME>_<PARAM_2>.ARCHIVE
and the logical path ARCHIVE_GLOBAL_PATH or adjust the entries as
appropriate. For information about the parameters used, display the F1
help for the Physical File input field.
In archiving object-specific Customizing for the WORKITEM archiving object,
define a variant for test mode and a variant for production mode (with the names
TEST_## and PROD_##, where ## is your group number), and maintain the
process control appropriately for these variants. Then maintain the attributes of
Continued on next page
420
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
the variants and save the variants. Ensure that the delete job is not scheduled.
You should also ensure that the logical file name ARCHIVE_DATA_FILE is
assigned to the object name WORKITEM.
a)
On the initial screen of the transaction Archive Administration: Initial
Screen (transaction SARA), enter the value WORKITEM in the Object
Name input field and then choose Customizing. On the next screen, select
the row Technical Settings in Archive Object-Specific Customizing: and
then choose Execute at the left of the row.
Ensure that the Logical File Name field contains the value
ARCHIVE_DATA_FILE. You should also ensure that the Not Scheduled
radio button is selected in the Delete Jobs group box.
Enter TEST_<##> in the Test Mode Variant field, where <##> is your
group number, choose the Variant button associated with this field, and, if
necessary, choose the Continue button on the next screen.
On the following screen, select Test Mode and choose Variant Attributes.
In the Description field on the following screen, enter a useful short
description of your variant and choose Save. Then return to the screen
Change View Customizing View for Archiving: Details.
Enter PROD_## in the Production Mode Variant field, where ## is your
group number, choose the Variant button associated with this field, and
choose Change Values on the next screen. On the following screen,
Maintain Variant: Report WORKITEM_DEL, Variant PROD_##, select
Production Mode and choose Variant Attributes. In the Description field
on the following screen, enter a useful short description of your variant
and choose Save.
Then return to the screen Change View Customizing View for Archiving:
Details and choose Save again. You have now maintained the archiving
object-specific Customizing settings. On the next screen, select an existing
Workbench request using Own Requests or, if you have not yet created a
new Workbench request, create a new Workbench request by choosing
Create, enter a short description, save it, and choose Continue.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
421
Unit 13: Archiving
ADM100
Task 3: Start the Write Program
From the SAP system, generate an archive file for the archiving object WORKITEM.
To do this, schedule the write program, run it, and monitor its processing.
1.
Create a variant for the write program. Name the variant Write_##, where ##
is your group number. Maintain the process control for the variant so that an
Archive and Delete is executed. Then schedule the write program with the start
time Immediate and the predefined spool parameters.
a)
On the initial screen of transaction SARA, enter the value WORKITEM in
the Object Name field and choose Write. On the following screen, enter
the value Write_## in the Variant field, where ## is your group number,
and choose Maintain. If necessary, confirm the dialog box by choosing
Continue.
On the following screen, Maintain Variant: Report WORKITEM_WRI,
Variant Write_##, select Production Mode in the Process Control group
box. Then choose Variant Attributes. Enter a useful short description in
the Description field and choose Save. This takes you back to the Variant
maintenance overview screen. Choose Back.
On the initial screen Archive Administration: Create Archive Files, choose
Start Date. On the following screen, choose Immediate and then Save.
Simply confirm the spool parameters by choosing Spool Parameters and
then, on the following screen, enter an output device, such as LP01 and
choose Continue. Confirm the dialog box that appears. Finally, choose
Execute and return to the initial screen of transaction SARA.
2.
Display the spool list and the job log of the archive run.
a)
On the initial screen of the archive administration transaction (SARA), enter
the value WORKITEM in the Object Name field and choose Job Overview.
The system displays an overview of the archiving jobs that you have
scheduled. Select the row for the job ARV_WORKITEM_WRI<timestamp>
and choose Display Spool List. On the next screen, select the row for the
spool list and choose Display Contents. Then return to the job overview,
select the job, and choose Display Job Log. Among other things, the
system displays which file is created in which path at operating system
level. Note the file name and file path.
Continued on next page
422
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Performing Data Archiving
3.
Check whether an archiving file was created at file system level.
a)
You have already checked in the Customizing settings that the archive file
is to be written to the directory specified by the parameter DIR_GLOBAL.
Now call the SAP Directories transaction (transaction AL11) and select the
DIR_GLOBAL entry. On the following screen, you can check whether a
file with the name from the last subtask was created.
Task 4: Start Delete Program
Now delete the objects archived in the previous task from your database. To do this,
schedule the delete program, run it, and monitor its processing.
1.
Start the delete program from transaction SARA by running it under your own
user. Maintain the archive selection, the start time, and the spool settings so that
you select the archive you created in task 3, start the delete program immediately,
and leave the spool parameters unchanged.
a)
On the initial screen of transaction SARA, enter the value WORKITEM in
the Object Name field and choose Delete. On the following screen, enter
your SAP user name in the User Name field, if it is not already entered
there. Then choose Select Archive Files (Archive Selection button). On the
next screen, select the displayed file (such as 000001) and choose Continue.
You return to the initial screen Archive Administration: Execute Delete
Program. Choose Start Date here. On the following screen, choose
Immediate and then Save. Simply confirm the spool parameters by choosing
Spool Parameters and then, on the following screen, enter an output device,
such as LP01 and choose Continue. Confirm the dialog box that appears.
Finally, choose Execute. The system displays the information that new
delete jobs were scheduled in the status line and returns you to the initial
screen of transaction SARA.
2.
Monitor the processing of your delete program by displaying the spool list.
a)
2005/Q2
On the initial screen of the archive administration transaction (SARA),
enter the name of the archiving object WORKITEM in the Object Name
field and choose Job Overview. The system displays an overview of
the archiving jobs that you have scheduled. Select the row for the job
ARV_WORKITEM_DEL<timestamp> and choose Display Spool List.
On the next screen, select the row for the spool list and choose Display
Contents.
© 2005 SAP AG. All rights reserved.
423
Unit 13: Archiving
ADM100
Lesson Summary
You should now be able to:
•
List individual steps of data archiving
•
Perform basic functions to customize SAP data archiving
Related Information
For more information about running SAP data archiving, attend SAP course BIT660
(Data Archiving), the SAP Service Marketplace under the Quick Link /data-archiving
or in the online documentation in the area Introduction to Data Archiving (area
CA-ARC).
424
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Accessing Archived Data
Lesson: Accessing Archived Data
Lesson Overview
A significant prerequisite for archiving application data is that this data belongs to
completed business processes or periods and is therefore no longer required for
current business processes. However, it may be necessary to access this data again
even after it has been archived, for example in the case of a complaint, for evaluations,
or for an internal or external audit. In this lesson, you will obtain an overview of
the options for accessing archived data.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
List different options for accessing archived data
Evaluate options of the SAP Archive Information System
Business Example
The user departments of your company want to access archived data. You want to
obtain an overview of the ways in which this is possible.
Access Options
The Archive Development Kit stores data in such a way that a read access to it is
possible at any time. The prerequisite for this is the existence of appropriate read
programs, which are made available by the relevant archiving object. They are used to
read the archived data objects in accordance with the selection criteria and to display it
in a suitable format for the user. In general, two types of access or display are used:
•
•
Sequential access
Direct access
Sequential (reading) access is the simplest form of access to archived data. With
this type of access, the read program first open the archive files from an archiving
run sequentially, read the contents of all data objects, and lists the data that meets the
entered selection criteria sequentially. You can use this method, for example, to list all
data objects for a particular posting period or for a particular document number group.
Direct access to individual archived data objects, such as an order or billing document
can only be achieved using an index table. The data object to be displayed is first
selected in the index table using search terms. If this is successfully achieved, the
archive file that contains the data object concerned is localized and opened using
2005/Q2
© 2005 SAP AG. All rights reserved.
425
Unit 13: Archiving
ADM100
the index. The read program can now directly access and display the data object
for which you have searched. This type of direct access is relatively costly from a
technical point of view, and is, therefore, only offered by a small number of archiving
objects, such as FI_DOCUMNT.
Hint: A simple option for system administrators to obtain read access to
archived data is to enter the relevant archiving object on the initial screen of
transaction SARA and to choose Read.
The SAP Archive Information System provides significantly more extensive and
easier to use functions for quick direct access to archived data objects.
SAP Archive Information System
The SAP Archive Information System (Archive Information System, SAP AS), a tool
for searching in SAP data archives, is fully integrated into the archiving environment.
It offers you support when searching for archived data and provides functions for
displaying this data.
The SAP Archive Information System is a generic tool; that is, the available functions
can be used for all existing archiving objects.
The search for data is always based on archive information structures. These are
transparent database tables that are supplied with data from the archive. To search for
archived data for an archiving object, there must be at least one archive information
structure for this archiving object. An information structure of this type always
includes the structure itself, the corresponding transparent database table, and an
evaluation program.
Before an archive information structure can be created, that is, filled with data from
the archive, it must first be activated. The system generates a transparent database
table and the evaluation program in the background. At the start of the delete run for
an archiving object, all of the active information structures for this archiving object
are filled.
426
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Accessing Archived Data
Figure 154: Automatic Filling of an Information Structure by the Delete Program
When displaying archived data, the user can usually choose between a number of
views in which the data objects can be displayed. Examples of these views are the
technical view and the business view.
2005/Q2
© 2005 SAP AG. All rights reserved.
427
Unit 13: Archiving
428
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Accessing Archived Data
Exercise 25: Access Archived Data
Exercise Objectives
After completing this exercise, you will be able to:
•
Access archived data to read it
Business Example
Your company uses SAP data archiving. It is necessary to access data that has already
been archived in the context of an evaluation that you are to perform.
Task 1: Technical View
As a member of the system administration team, you want to obtain a technical view
of data that has been archived (in this case, work items).
1.
Use transaction SARA to start the read program for archiving object WORKITEM.
Select a suitable archive to read and expand the result of the read program.
Task 2: Business View (Optional)
As a member of a user department, you want to access archived work items to read
them.
1.
2005/Q2
Use transaction SWW_ARCHIV to read work items with an appropriate object
key and period. Expand the displayed workflow log and obtain an overview of
the process of the archived workflow.
© 2005 SAP AG. All rights reserved.
429
Unit 13: Archiving
ADM100
Solution 25: Access Archived Data
Task 1: Technical View
As a member of the system administration team, you want to obtain a technical view
of data that has been archived (in this case, work items).
1.
Use transaction SARA to start the read program for archiving object WORKITEM.
Select a suitable archive to read and expand the result of the read program.
a)
On the initial screen of transaction SARA, enter the value WORKITEM
in the Object Name field and then choose Read. On the following
screen, use the F4 help for the Read Program to select the read program
RSWWARCR. Then choose Execute.
On the following screen, select the displayed file (such as 000001) and
choose Continue. The Read Program for Work Items (for Archiving) screen
appears. You can trace the individual steps of the processing of the work
item on this screen by expanding the tree structure. If you also want to
perform the following optional exercise, note the number of the archived
work item including the leading zeros (that is, for example 0000000001)
and the date of the processing (that is, for example, November 17 2004).
Task 2: Business View (Optional)
As a member of a user department, you want to access archived work items to read
them.
1.
Use transaction SWW_ARCHIV to read work items with an appropriate object
key and period. Expand the displayed workflow log and obtain an overview of
the process of the archived workflow.
a)
Call the transaction Read Workflow from Archive (transaction
SWW_ARCHIV, menu path Tools → Business Workflow → Development
→Administration → Workflow Runtime→ Reorganization → Display
Workflows from Archive). In the Object Category field, select
BOR Object Type, and in the Object Type field, select the entry
FORMABSENC. In the Object Key field, enter the number of the work
item noted from the previous task including the leading zeros (that is, for
example, 0000000001). In the Period group box, select a period that
includes the date from the previous tasks (such as 24.01.2003).
On the next screen, select the displayed file (such as 000001) and choose
Continue. The system displays the log of the selected work item. On this
screen, you can use the Processor and Object buttons to display different
views of the archived workflow and expand each of the views.
430
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Accessing Archived Data
Lesson Summary
You should now be able to:
•
List different options for accessing archived data
•
Evaluate options of the SAP Archive Information System
Related Information
For additional information about accessing archived data, attend SAP course BIT660
(Data Archiving) or see the SAP Service Marketplace, under the Quick Link
/data-archiving. For information about the SAP Archive Information System, see the
online documentation, section Archive Information System in the area Introduction to
Data Archiving (area CA-ARC).
2005/Q2
© 2005 SAP AG. All rights reserved.
431
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Define the term data archiving
•
Explain the need for data archiving
•
Outline the technical process of data archiving
•
List individual steps of data archiving
•
Perform basic functions to customize SAP data archiving
•
List different options for accessing archived data
•
Evaluate options of the SAP Archive Information System
432
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
Every archiving object in the SAP system is connected 1:1 with the content of a
single database table.
Determine whether this statement is true or false.
□
□
2.
True
False
The names of the archive files are determined at runtime. How are these names
generally specified for a specific archiving object?
Choose the correct answer(s).
3.
□
□
A
B
□
C
□
D
By cross-object Customizing settings
By maintaining a local path and assigning the logical path to a
physical path in the Basis Customizing
By assigning a physical file name to a logical file name in Basis
Customizing and assigning a logical file name to an archiving object
in the archiving object-specific Customizing
By the exact time of the archiving run
After data has been archived from the SAP system and deleted from the SAP
system's database, it is no longer possible to access this data with read accesses.
Determine whether this statement is true or false.
□
□
2005/Q2
True
False
© 2005 SAP AG. All rights reserved.
433
Test Your Knowledge
ADM100
Answers
1.
Every archiving object in the SAP system is connected 1:1 with the content of a
single database table.
Answer: False
Different business objects could belong to each archiving object in the SAP
system. The data for these business objects could, in turn, be distributed across
multiple database tables.
2.
The names of the archive files are determined at runtime. How are these names
generally specified for a specific archiving object?
Answer: C
The name of the archive files is determined at runtime by settings in the archiving
object-specific Customizing (assignment of a logical file name for the specific
archiving object) and in the Basis Customizing (assignment of a physical file
name to a logical file name in the Basis Customizing and the assignment of a
logical file name). No specifications about the name of the archive file are made
in cross-object Customizing. The exact time of the archiving run can appear
in the name of the archiving file using a parameter, but the name is generally
not determined by this alone.
3.
After data has been archived from the SAP system and deleted from the SAP
system's database, it is no longer possible to access this data with read accesses.
Answer: False
It is still possible to access data to read it after it has been stored in the archive
and deleted from the SAP system's database. Depending on the archiving object
concerned, the user can choose from a number of views (such as a technical
view and a business view).
434
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 14
System Monitoring
Unit Overview
This unit introduces system monitoring. You will first learn about the basics of the
monitoring architecture and how to use the CCMS Alert Monitor. This unit also
deals with creating your own monitors, including remote systems, and maintaining
threshold values.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
•
•
Explain the concepts of the CCMS Alert Monitoring Infrastructure
Use the CCMS Alert Monitor to monitor your system
Configure the central monitoring of remote systems
Design and create your own monitors
Activate threshold values that are suitable for your system environment
Describe the added value of the SAP Solution Manager in an SAP system
landscape
Unit Contents
Lesson: Monitoring Architecture .................................................. 436
Exercise 26: System Monitoring.............................................. 445
Lesson: Including Remote Systems.............................................. 449
Exercise 27: Include Remote Systems ...................................... 453
Lesson: Creating Your Own Monitors ............................................ 457
Exercise 28: Create Your Own Monitors .................................... 461
Lesson: Properties Variants and Threshold Values ............................ 466
Exercise 29: Properties Variants of Monitors ............................... 471
Lesson: Concept of the SAP Solution Manager ................................ 476
2005/Q2
© 2005 SAP AG. All rights reserved.
435
Unit 14: System Monitoring
ADM100
Lesson: Monitoring Architecture
Lesson Overview
This lesson provides an introduction to monitoring as a significant component of the
Computing Center Management System (CCMS). Terms such as monitoring tree
element (MTE), monitoring object, and monitoring attribute are discussed in detail.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
Explain the concepts of the CCMS Alert Monitoring Infrastructure
Use the CCMS Alert Monitor to monitor your system
Business Example
You want to ensure good performance for the processing of business processes. You
therefore regularly monitor the SAP systems, and take preventative action if required.
Basics
Initial questions about monitoring:
•
Why?
•
–
To ensure the efficient processing of business processes
–
To ensure system security and stability
How?
–
–
–
–
Central and cross-system
With an alert if an error occurs
With help that provides cross-system detailed information if an error occurs
With the help of the CCMS Alert Monitoring Infrastructure and the special
transactions connected to it
Many components are involved in the processing of a business process in the mySAP
Business Suite. These components must be monitored, as both a gradual reduction
in performance and a sudden breakdown of a component could affect the entire
productivity. It is a task of the administrator to monitor the system landscape regularly,
and not only in the case of errors, but to take preventative action.
436
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Monitoring Architecture
For example:
A file system where files of the SAP database are stored is 100% full. The
database can no longer extend the tables in the files. A user performs a business
transaction in the context of which a data record should be asynchronously added
to one of these tables. The insert fails due to the space problem in the file system.
The database error is seen as so serious that the entire asynchronous update
process is automatically deactivated. All user sessions hang with the display of
the hour glass. The SAP system hangs. If the fill level of the file system had
been regularly checked, the administrator could have created space in other file
systems and avoided the system downtime.
Monitoring should be organized as efficiently as possible. There is not enough time
for an administrator to log on to each host component to check its status. An efficient
monitoring structure should be able to display the entire system landscape centrally at
a glance. If an error occurs, the person responsible is automatically notified. Tools
should be provided for the analysis of errors that provide cross-system detailed
information about the problem.
Figure 155: Central Monitoring
The CCMS Alert Monitoring Infrastructure provides you with the possibility of
monitoring a mySAP Business Suite efficiently and centrally.
2005/Q2
© 2005 SAP AG. All rights reserved.
437
Unit 14: System Monitoring
ADM100
The infrastructure must be installed on every component that is to be centrally
monitored. This is automatically the case for SAP R/3 4.x Systems. SAP R/3 3.x
Systems and components on which no SAP system is active are connected using
CCMS agents.
Each component collects its own monitoring data using the infrastructure and stores it
locally in the main memory. This part of the main memory is called the monitoring
segment. You can configure the size of the monitoring segment.
An SAP system is selected as the central monitoring system. It should have as high
a release status as possible (at least SAP R/3 4.6C) and a high level of availability.
In large system landscapes, we recommend that you include a separate system that
is used only special tasks such as central monitoring, Central User Administration,
transport domains controller, or the SAP Solution Manager. From a performance point
of view, the workload of the central monitoring system increases only insignificantly,
as the collection of monitoring data is usually decentralized.
The central monitoring system collects the monitoring data for the components and
displays it in various views. In this way, the administrator has a central view of the
entire system landscape. If errors occur, the administrator can jump directly from the
central monitoring system to the appropriate component to correct a problem in a
detailed analysis.
Details
The CCMS Alert Monitoring Infrastructure consists of three parts: Data collection,
data storage, and administration.
438
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Monitoring Architecture
Figure 156: CCMS Alert Monitoring Infrastructure in Detail
At the data collection level, small subareas of the mySAP Business Suite are
monitored by special programs called data collectors. Data collectors can be ABAP,
C, or Java programs. There are several hundred data collectors in ABAP alone. Each
data collector checks its subcomponent at regular intervals and stores the collected
monitoring data in the main memory of its host.
At the data storage level, the area of the main memory that contains the monitoring
data from the data collector is called the monitoring segment. As the main memory
data is always overwritten, it can be permanently copied to database tables. You can
then analyze the data later. The data collection and storage elements must be present
on every component that is to be centrally monitored.
Caution: Note that every instances of an SAP system has its own monitoring
segment in shared memory. This means that for an SAP system with eight
instances, there are eight different monitoring segments. The number of
monitoring segments is determined by the number of instances. Whether or
not several instances run on the same hardware, for instance, does not play
any role in this.
The administration level allows the display and evaluation of the data from the
monitoring segment. SAP provides an expert tool, the CCMS Alert Monitor
(transaction RZ20) as a display transaction. Alternatively, you can use the SAP
2005/Q2
© 2005 SAP AG. All rights reserved.
439
Unit 14: System Monitoring
ADM100
Solution Manager to display the data in a business process-oriented context. If the
system identifies a problem, it can execute an auto reaction, such as informing the
responsible person. The analysis method then helps you to investigate the problem.
The CCMS Alert Monitoring Infrastructure can be extended. You can integrate your
own components using data collectors that you have written yourself. Third-party
vendors and partners can export the monitoring data from the monitoring segment
using various interfaces.
Figure 157: Monitor Structure
The CCMS Alert Monitor (transaction RZ20) displays the monitoring data from the
monitoring segment in a tree structure. The tree structure allows a clear display when
you are displaying a large number of measured values.
Any node in the tree is called a Monitoring Tree Element (MTE).
The measured values that are collected by the data collectors are displayed at the
lowest level in the leaves of the tree. The leaves are called monitoring attributes.
Threshold values can be stored for a monitoring attribute. SAP delivers default
threshold values. However, in order to customize the monitor as well as possible for
your system environment, you should check these threshold values, and adjust them if
required.
Monitoring attributes are bundled using monitoring objects at the second-lowest
level. For example, the monitoring object program buffer contains, among others,
the attributes hit rate and swap.
440
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Monitoring Architecture
All other nodes in the tree serve to structure the monitoring objects in a logical and
clear way, so that you can easily find the monitoring attribute that you require.
A CCMS monitor displays different subareas of the monitoring data. A monitor can
contain data from multiple SAP systems.
Figure 158: The CCMS Alert Monitor
The CCMS Alert Monitor is started by calling transaction RZ20. From the SAP Easy
Access, choose Tools → CCMS → Control/Monitoring → Alert Monitor.
SAP delivers the Alert Monitor with preconfigured monitor sets that you can use
immediately. Every monitor set bundles monitors that display various parts of the
entire monitoring architecture, by topic area. It is therefore easier, for example, to
find the database area.
The delivered monitor sets can be different for each system. A mySAP CRM system
contains, for example, a special set for monitoring the CRM scenario. There are, of
course, special data collectors connected with this that SAP delivers preconfigured
with a mySAP CRM System.
The monitoring data that monitors display can overlap. This means that the monitoring
attribute hit rate of the program buffer can appear in several monitors. If you change,
for example, the threshold value for this attribute in one of these monitors, it is
changed in all monitors.
2005/Q2
© 2005 SAP AG. All rights reserved.
441
Unit 14: System Monitoring
ADM100
Some monitors, such as the monitor Availability: Selected Systems in the monitor set
SAP CCMS Monitor Templates do not initially display any data. This can be due to the
fact that special settings are required to start the underlying data collectors.
To begin with, you will use the preconfigured monitors. Later, you can also create
your own monitors that display exactly the data that you require for your daily
monitoring work.
You can open a monitor by selecting its name.
Figure 159: Layout of a Monitor
After you have opened a monitor, the corresponding monitoring data displays in the
form of a tree. By clicking the “+” sign beside an MTE, you can expand the tree down
to its leaves; the monitoring attributes.
Alert threshold values for triggering yellow and red alerts are assigned to monitoring
attributes. If the threshold value condition is fulfilled, first a yellow, and then, if there
is further deterioration, a red alert is triggered. The color of the monitoring attribute is
propagated to its parent node in the tree, where the most severe alert is forwarded (red
is more severe than yellow). This means that you can determine whether there is an
alert in the tree from the root of the tree.
442
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Monitoring Architecture
Views
The monitor should support you in your daily work. After you have opened the
monitor, there are two views available to you:
•
•
The Current Status view displays the monitor with the newest reported data.
The Open Alerts view displays the monitor with its history information.
For example, during the previous night there may have been problems that are no
longer occurring. In the Current Status view, the monitoring attribute is green, while
in the Open Alerts view, it is red. After you have ensured that there are currently no
problems, you can then investigate problems that have previously occurred. You
can see the selected view in the upper part of the monitor. You can switch views by
choosing the Current Status or Open Alerts buttons.
Figure 160: The Alert Browser
You can easily process the alerts that occurred in the past in the Open Alerts view. By
double-clicking an MTE in the tree, you open the Alert Browser, which displays a
list of all alerts for the selected MTEs and all alerts below it in the tree. This means
that if you double-click the root of the tree, the system displays a list of all alerts in
the tree, sorted by red and yellow alerts.
2005/Q2
© 2005 SAP AG. All rights reserved.
443
Unit 14: System Monitoring
ADM100
Select an alert that you want to process. Then choose the Start Analysis Method
button. This starts the analysis method that is assigned to the MTE. The analysis
method is a special tool that supports you when investigating problems. It can be
transactions, or specially programmed function modules, or URL calls. You, therefore,
do not need to remember all of the special tools, but simply use the CCMS Alert
Monitor as a central point of entry.
After you have clarified the problem situation, choose F3 to return to the Alert
Browser. Then choose Complete Alerts. The processed alert is removed from the list
and is stored in a database table.
Proceed in the same way with the remaining alerts, until the list is empty. When you
next use your monitor, only the newly-occurred alerts display.
If you want to display completed alerts again, choose Show Alert History in the Alert
Browser. Completed alerts display with the status Done.
444
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Monitoring Architecture
Exercise 26: System Monitoring
Exercise Objectives
After completing this exercise, you will be able to:
•
Evaluate and process alerts in the Alert Monitor
Business Example
You want to ensure good performance for the processing of business processes. You
therefore regularly monitor the SAP systems, and take preventative action if required.
Task: The CCMS Alert Monitor
1.
Start the CCMS Alert Monitor (transaction RZ20).
2.
Open the Entire System monitor from the SAP CCMS Monitor Templates
monitor set.
3.
What is the current average dialog response time?
4.
Switch to the Open Alerts view.
5.
Select all alerts that have occurred in the Dialog area.
6.
Process an alert from this list:
Start the analysis method for an alert.
Return to the Alert Browser and complete the alert. Does the alert still appear in
the list?
How can you display the completed alert again?
2005/Q2
© 2005 SAP AG. All rights reserved.
445
Unit 14: System Monitoring
ADM100
Solution 26: System Monitoring
Task: The CCMS Alert Monitor
1.
Start the CCMS Alert Monitor (transaction RZ20).
a)
2.
Open the Entire System monitor from the SAP CCMS Monitor Templates
monitor set.
a)
3.
Choose Open Alerts.
Select all alerts that have occurred in the Dialog area.
a)
6.
You can find the monitoring attribute for the average dialog response time
by expanding, for example, the branch <SID> → R/3 Services → Dialog
→ <Instance>. Note that the monitor is in the Current Status view.
Switch to the Open Alerts view.
a)
5.
Expand the SAP CCMS Monitor Templates set by choosing the “+” sign
beside the set. Select the Entire System set.
What is the current average dialog response time?
a)
4.
Call the CCMS Alert Monitor (Tools → CCMS → Control/Monitoring →
Alert Monitor, transaction RZ20).
Select the Dialog MTE. All alerts in this area display in the Alert Browser.
Process an alert from this list:
Start the analysis method for an alert.
Return to the Alert Browser and complete the alert. Does the alert still appear in
the list?
Continued on next page
446
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Monitoring Architecture
How can you display the completed alert again?
a)
Select an alert in the list. Then choose the Start Analysis Method button.
The system jumps from the monitor to a function that provides you with
detailed data about the alert.
Return to the monitor. Choose Complete Alerts. The alert is removed
from the list.
To display the alert again, choose Show Alert History. Your completed
alert has the status DONE.
Hint: It is possible that the system displays other alerts with
the status AUTO_COMPLETE. These alerts were completed
automatically by the system to keep the alert area free for new
alerts.
2005/Q2
© 2005 SAP AG. All rights reserved.
447
Unit 14: System Monitoring
ADM100
Lesson Summary
You should now be able to:
•
Explain the concepts of the CCMS Alert Monitoring Infrastructure
•
Use the CCMS Alert Monitor to monitor your system
448
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Including Remote Systems
Lesson: Including Remote Systems
Lesson Overview
In this lesson, you will learn how to include remote system in alert monitoring.
Lesson Objectives
After completing this lesson, you will be able to:
•
Configure the central monitoring of remote systems
Business Example
As an administrator, you want to include remote systems in your alert monitoring.
Including Remote Systems
The monitors delivered by SAP display more detailed monitoring data for the local
SAP system. Central monitoring, on the other hand, has the advantage that you can
monitor the entire system landscape, and not just your local system.
You can centrally monitor all components that have a CCMS Alert Monitoring
Infrastructure. SAP has delivered the infrastructure since SAP R/3 4.0. To include
components that do not have an infrastructure, you can use the CCMS agent programs
SAPCM3X for SAP R/3 3.x and SAPCCMSR for non-SAP components.
Figure 161: Including Remote Systems
2005/Q2
© 2005 SAP AG. All rights reserved.
449
Unit 14: System Monitoring
ADM100
To include an SAP system in a central monitoring architecture, you must define an
RFC connection over which the monitoring data for the SAP system can be transferred
to the central monitoring system. The data collection is performed independently by
the CCMS Alert Monitoring Infrastructure on the remote system.
From a security point of view, it is recommended that you also define a second RFC
connection between the systems, with which the analysis methods can be started in
the remote system from the central monitoring system. If a problem occurs, you can
therefore branch directly from the central monitor to the remote system to analyze the
situation in more detail.
Figure 162: Including Remote Systems: Transaction RZ21
SAP systems are included in the central monitoring system in transaction RZ21.
You can start the transaction from the SAP Easy Access Menu by choosing Tools →
CCMS → Configuration → Alert Monitor.
In RZ21, choose Technical Infrastructure → Create Remote Monitoring Entry.
Enter the SID of the SAP system to be monitored in the Target System ID field.
Now create the two RFC connections from the central monitoring system to the
monitored SAP system. Choose Goto → RFC Connections. The system displays
transaction SM59. Create two RFC connections here. Note that the connection type is
“3” (SAP R/3 - SAP R/3 communication).
450
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Including Remote Systems
In the RFC connection for the transfer of the monitoring data, you can enter a user of
the type Communication with a password that is valid in the monitored SAP system.
This means that when the central monitoring system requests monitoring data from
the monitored SAP system, it is provided without the need for user interaction.
In the RFC connection that is used for the start of the analysis method, do not enter a
user, but rather check the field Current User. If an analysis method is started in the
monitored system from the central monitoring system when problems occur, the caller
must authorize himself or herself in the monitored system.
Return to transaction RZ21 by choosing F3. Enter the RFC connections that you
created under Target System RFC Destination. Choose Save. The SAP system can
now be centrally monitored.
2005/Q2
© 2005 SAP AG. All rights reserved.
451
Unit 14: System Monitoring
452
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Including Remote Systems
Exercise 27: Include Remote Systems
Exercise Objectives
After completing this exercise, you will be able to:
•
Include a remote system
Business Example
As an administrator, you want to include remote systems in your alert monitoring.
Task: Include Remote SAP Systems
Include remote SAP systems in the central monitoring architecture.
1.
Your SAP system is the central monitoring system.
Hint: This exercise has two possible solutions.
On one hand, you can use the RFC connections <SID>_DATA and
<SID>_ANALYSIS from the RFC unit, and on the other, you can
follow the instructions for creating the RFC connections (if you have
not performed the exercise in the RFC unit).
In the first case, you can continue directly with the entering of RFC
connections in transaction RZ21.
Register the SAP system of your partner group in your system. To do this, get
the details of a valid user with password from your partner group. Name the
remote connections <SID>_100_DATA and <SID>_100_ANALYSIS.
Where can you see data from your partner group’s SAP system?
2005/Q2
© 2005 SAP AG. All rights reserved.
453
Unit 14: System Monitoring
ADM100
Solution 27: Include Remote Systems
Task: Include Remote SAP Systems
Include remote SAP systems in the central monitoring architecture.
1.
Your SAP system is the central monitoring system.
Hint: This exercise has two possible solutions.
On one hand, you can use the RFC connections <SID>_DATA and
<SID>_ANALYSIS from the RFC unit, and on the other, you can
follow the instructions for creating the RFC connections (if you have
not performed the exercise in the RFC unit).
In the first case, you can continue directly with the entering of RFC
connections in transaction RZ21.
Register the SAP system of your partner group in your system. To do this, get
the details of a valid user with password from your partner group. Name the
remote connections <SID>_100_DATA and <SID>_100_ANALYSIS.
Where can you see data from your partner group’s SAP system?
a)
To do this, get the details of a valid user with password from your partner
group.
Call the configuration transaction for the CCMS Alert Monitor (Tools →
CCMS → Configuration → Attributes and Methods, transaction RZ21).
Choose Technical Infrastructure → Configure Central System → Create
Entry for Remote System.
Under Target System ID, enter the <SID> of your partner group’s system.
Choose Goto → RFC Connections.
Choose Create. Enter the following values:
•
•
•
•
•
•
454
RFC Destination: <SID>_100_DATA (replace <SID> with the
<SID> of your partner group's system)
Connection type: 3
Description: Any documentation.
Choose Enter.
Target host: The host of your partner group.
System number: The system number of your partner group.
Continued on next page
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Including Remote Systems
On the Logon/Security tab page, enter the logon information that you
received from your partner group.
Choose Save.
Choose Test Connection. If the connection test fails, check the data for
Target Host and System Number with your partner group.
Choose F3 to go back a step, and choose Create again.
Call the second RFC connection <SID>_100_ANALYSIS (replace
<SID> with the <SID> of your partner group’s system). Otherwise,
enter the same data as for the RFC connection <SID>_DATA, with one
exception: On the Logon/Security tab page, select Current User instead
of entering the logon information.
Choose Save.
Perform a connection test again.
Return to transaction RZ21 by choosing F3 twice.
In the Data Collection field, enter the RFC connection <SID>_100_DATA.
In the Analysis Method field, enter the RFC connection
<SID>_100_ANALYSIS.
Choose Save and confirm the information dialog box that appears by
choosing Continue.
The message Entry for monitoring system <SID> saved informs you that
the registration of the SAP system was successful.
You cannot yet see any data for the system of your partner group, as all
monitors delivered by SAP display only local data.
2005/Q2
© 2005 SAP AG. All rights reserved.
455
Unit 14: System Monitoring
ADM100
Lesson Summary
You should now be able to:
•
Configure the central monitoring of remote systems
456
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Creating Your Own Monitors
Lesson: Creating Your Own Monitors
Lesson Overview
In this lesson, you will learn what to consider when designing and creating your
own monitors.
Lesson Objectives
After completing this lesson, you will be able to:
•
Design and create your own monitors
Business Example
As an administrator, you want to create a monitor that is specifically adjusted to
your requirements.
Creating Your Own Monitors
Initial questions about designing your own monitors:
•
Why?
•
–
To display exactly the values that are important for your daily work
–
Cross-system monitoring
How?
•
–
What information do I need?
–
Create own monitor set
–
Create own static monitors
–
Create own rule-based monitors (ADM106)
Tips:
–
–
–
Create monitors for problems
Transfer as little data as possible by RFC
Monitor sets can be transported
SAP recommends that, for your regular work, you create your own monitors that
display precisely the cross-system or local data that you require for your work.
The sets and monitors delivered by SAP cannot be changed. You should therefore
first create your own monitor set. You can then create your own static monitors that
display the required data.
2005/Q2
© 2005 SAP AG. All rights reserved.
457
Unit 14: System Monitoring
ADM100
The second technique for creating your own monitors, rule-based monitors, is
described in detail in SAP course ADM106.
Before you create your own monitor, you should clarify the purpose of the monitor.
The monitor should display as little data as possible in as clear a way as possible. You
must make a selection from the many hundreds of monitoring attributes that meets
your requirements. A system overview monitor, for example, should contain the
status of the last database backup or terminated updates as core indicators, but not
details about the distribution of the dialog response time. You should create another
monitor to display the response time.
Note also that the quantities of data to be transferred quickly become very large,
especially if data from the monitored SAP systems is also to be displayed. A monitor
that displays all monitoring data for multiple remote systems is unusable, as the data
transfer takes too long, especially if the remote systems have a heavy load. As a
global guide value, SAP recommends 10-20 monitoring attributes for each monitored
instance in the central monitor.
Creating a Monitor Set
Figure 163: Creating a Monitor Set
The CCMS Alert Monitor (transaction RZ20) is usually in display mode, where you
can open monitors, but cannot create or change monitors. To activate change mode,
choose Extras → Activate maintenance function in transaction RZ20. Maintenance
functions ON appears in the transaction heading. The system displays new pushbuttons
for creating and changing monitors and sets. Choose the Create button. The system
458
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Creating Your Own Monitors
asks whether you want to create a monitor set or a monitor. Select Monitor Set and
choose Copy. Enter a name for your monitor set. Note the naming convention that
your monitor set should not begin with SAP.
You can choose whether your set can be changed by other users or not. You can also
choose whether the set displays for other users in the CCMS Alert Monitor. After
you have specified the set attributes, choose Enter. You have now created your own
monitor set, into which you can either create new monitors or copy existing monitors.
The monitor sets and monitors delivered by SAP cannot be changed. However,
you can use them as stable templates. You can set whether or not an SAP monitor
set should appear in the display mode of the CCMS Alert Monitor. If you want to
hide an SAP monitor set, select the set and then Change. Remove the selection for
public. The set can now no longer be seen in the display mode. You can change your
selection in the change mode.
Figure 164: Static Monitors
Now create new monitors or copy existing monitors into your monitor set.
To create new monitors in your set, select the set and choose Create. The system
displays a selection screen in which all MTEs for all registered systems display.
Expand the tree structure and choose the MTEs that you want to display in your
monitor by checking them. If an MTE is checked, all MTEs underneath it are
automatically copied to the monitor. Take into account the number of MTEs.
2005/Q2
© 2005 SAP AG. All rights reserved.
459
Unit 14: System Monitoring
ADM100
Choose Save. The system prompts you for a name for the new monitor, which you can
then start by selecting it.
The figure shows a monitor that displays cross-system monitoring data from two SAP
databases. You use this monitor in exactly the same way as the SAP standard monitors
(Current Status, Open Alerts, Alert Browser).
You can organize your monitor more clearly by using virtual nodes when selecting the
MTEs. Virtual nodes allow you to structure your monitor. During the MTE selection,
choose Create and then Virtual Node. You can choose any text for the virtual node. It
should be as descriptive as possible. Complete your entry by choosing Enter. Your
virtual node is inserted. You can now select any MTEs for inclusion in the monitor
under this node. In the final monitor, these MTEs appear under the virtual node.
460
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Creating Your Own Monitors
Exercise 28: Create Your Own Monitors
Exercise Objectives
After completing this exercise, you will be able to:
•
Create your own monitors
Business Example
As an administrator, you want to create a monitor that is specifically adjusted to
your systems.
Task 1: Creating a Monitor Set
1.
Create your own monitor set, System Monitoring.
Task 2: Create a Monitor
Create your own cross-system monitor, Core_information that displays the most
important system monitoring data.
1.
First consider what information is important for monitoring, from your point
of view. Remember that you should not display too many values for each SAP
system.
2.
Now attempt to create the monitor Core_information. The monitor should,
as far as possible, display the desired data for your system and your partner
group’s system.
Task 3: Process Alerts in the Remote System
1.
Open your Core_information monitor. Display all alerts for the entire monitor.
Process an alert from your partner group's system.
a) Start the analysis method for an alert.
b) Return to the Alert Browser and complete the alert. Does the alert still appear
in the list?
c) How can you display the completed alert again?
Result
You have just worked on a cross-system basis with the Alert Monitor.
2005/Q2
© 2005 SAP AG. All rights reserved.
461
Unit 14: System Monitoring
ADM100
Solution 28: Create Your Own Monitors
Task 1: Creating a Monitor Set
1.
Create your own monitor set, System Monitoring.
a)
Call the CCMS Alert Monitor (Tools → CCMS → Control/Monitoring →
Alert Monitor, transaction RZ20).
Activate the maintenance function, by choosing Extras → Activate
Maintenance Function.
Choose the Create button. New Monitor Set is already selected. Choose
Copy.
Enter the name System Monitoring for your monitor set. Maintain
the attributes of your monitor set as you wish.
Choose Copy.
Your monitor set displays under My Favorites. You can now create new
monitors in this set.
Task 2: Create a Monitor
Create your own cross-system monitor, Core_information that displays the most
important system monitoring data.
1.
First consider what information is important for monitoring, from your point
of view. Remember that you should not display too many values for each SAP
system.
a)
Your new monitor, Core_information, should contain the most important
monitoring data for your system landscape.
It could, for example, contain the following data:
•
•
•
•
Terminated updates
Terminated ABAP programs
System log
Average dialog response time
Continued on next page
462
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Creating Your Own Monitors
2.
Now attempt to create the monitor Core_information. The monitor should,
as far as possible, display the desired data for your system and your partner
group’s system.
a)
In maintenance mode of transaction RZ20, place the cursor on your
monitor set and choose Create.
The system displays the currently registered SAP systems.
Expand the tree and search for monitoring attributes that correspond to
the data that you require.
For the proposed monitor from task 1:
•
•
•
•
Terminated updates: Look in the branch <SID> → <Instance> →
R3Services → Update → Update → AbapErrorInUpdate.
Terminated ABAP programs: Look in the branch <SID> →
<Instance> → R3Abap → Shortdumps..
System log: Look in the branch <SID> → <Instance> → R3Syslog
Average dialog response time: Look in the branch <SID> →
<Instance> → R3Services → Dialog → ResponseTime.
Select the MTEs that you require.
Choose Save. Enter Core_information as the name of your monitor.
Open your monitor.
Task 3: Process Alerts in the Remote System
1.
Open your Core_information monitor. Display all alerts for the entire monitor.
Process an alert from your partner group's system.
a) Start the analysis method for an alert.
b) Return to the Alert Browser and complete the alert. Does the alert still appear
in the list?
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
463
Unit 14: System Monitoring
ADM100
c) How can you display the completed alert again?
a)
Open your Core_information monitor .
Switch to the Open Alerts view.
Select an MTE for your partner system. All alerts in this area for your
partner system display in the Alert Browser.
Select an alert in the list. Then choose the Start Analysis Method button.
The logon screen of the partner system appears, as Current User is selected
for the user data in the RFC connection for starting analysis methods.
Log on to your partner system.
In the partner system, you jump to an action that provides you with detailed
data about the alert.
Return to the monitor. Choose Complete Alerts. The alert is removed
from the list.
To display the alert again, choose Show Alert History. Your completed
alert has the status DONE.
Result
You have just worked on a cross-system basis with the Alert Monitor.
464
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Creating Your Own Monitors
Lesson Summary
You should now be able to:
•
Design and create your own monitors
2005/Q2
© 2005 SAP AG. All rights reserved.
465
Unit 14: System Monitoring
ADM100
Lesson: Properties Variants and Threshold Values
Lesson Overview
You can implement targeted monitoring of your systems using your own monitors
that you create yourself. For these monitors to work optimally, you must adjust the
threshold values for the monitoring objects and monitoring attributes in the monitors
for your system landscape. The specific settings can be stored as properties variants.
Lesson Objectives
After completing this lesson, you will be able to:
•
Activate threshold values that are suitable for your system environment
Business Example
Alert monitors can only be meaningfully used if the selected threshold values for
the individual monitoring attributes are set to sensible values. It is not possible to
recommend values that are generally valid, since different values are appropriate
depending on the system or operation mode.
Threshold Values and Properties Variants
Introductory questions about properties variants and threshold values:
•
Why?
–
–
•
So that alerts are not constantly or never triggered
So that the Monitoring Infrastructure is optimized for the customer
environment
How?
•
–
In the central monitoring system in transaction RZ20
–
Transport from there to the monitored SAP systems
Tips:
–
–
First create container for threshold values (properties variants) and activate
Then maintain threshold values for the MTEs in your own monitors
Threshold values can be stored for a monitoring attribute. Threshold values determine
when the monitoring attribute should trigger a yellow or a red alert, and when it
should become green or yellow again. The CCMS Alert Monitoring Infrastructure
is delivered preconfigured with threshold values recommended by SAP. You should,
466
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Properties Variants and Threshold Values
however, check the threshold values, at least for the monitoring attributes that you
consider to be important and that you have included in your own monitors. In this
way, you customize the CCMS Alert Monitor optimally to your system environment.
Otherwise, alerts can be constantly or never triggered, depending on whether the
threshold value is too low or too high for your system environment.
Threshold values must be stored locally in every system. However, instead of
maintaining the same threshold values in every system, SAP recommends that you
maintain the values in the central monitoring system and then distribute them to the
monitored SAP systems using the transport system.
The prerequisite for transporting the threshold values to other SAP systems is that you
have stored them in properties variants.
Properties variants are containers in which CCMS Alert Monitor settings, such as
threshold values, can be stored.
You can create as many properties variants as you like and store CCMS Alert Monitor
settings in them. At any time, exactly one properties variant with your settings is
active.
Properties variants have three advantages:
•
•
•
2005/Q2
You can manually switch from one properties variant to another for test purposes
or to adjust the monitor to a special situation. This means that all monitor settings
are automatically changed in accordance with the current properties variant.
You can connect a properties variant to an operation mode. In this way, the
threshold value for the dialog response time is set to 1s during the day, while
the threshold value is automatically increased to 10s after the switch to night
operation, as there is usually no dialog processing during the night.
You can transport the contents of properties variants to other SAP systems using
the transport system. For example, if you create a variant for production systems
in the central monitoring system, and maintain the threshold values that are to
apply for production systems there, you can then transport the variant to all
production systems and activate the threshold values there.
© 2005 SAP AG. All rights reserved.
467
Unit 14: System Monitoring
ADM100
Figure 165: Creating and Activating Properties Variants
Properties variants are created in transaction RZ21. You can find the important
functions for properties variants by choosing Properties → Variants.
First, create your own properties variant. Choose Properties → Variants → Create.
Enter a name and a description for the properties variant, and save it.
Then choose Properties → Variants → Activate. Select your variant and choose
Enter. Your properties variant that is now active, displays on the initial screen of
transaction RZ21.
You can organize properties variants hierarchically. You can specify a parent
variant when you create variants. If you do not specify another variant, the variant
“*” is implicitly assumed to be the parent variant, whose parent variant, is, in
turn, SAP-DEFAULT. The threshold values recommended by SAP are stored in
SAP-DEFAULT.
If no threshold value is maintained for a monitoring attribute in your variant, the
system checks the parent variant. If this also has no threshold value, its parent variant
is checked, and so on. Your properties variant is empty after it has been created.
Therefore, after activation, the threshold values that are stored in the variant “*” or
SAP-DEFAULT apply.
The connection of properties variants to operation modes is performed in transaction
RZ04. Select the operation mode and choose Operation Mode → Change. You can
enter the desired properties variant in Monitoring Properties Variant. Then save
your entries.
468
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Properties Variants and Threshold Values
Figure 166: Maintain Threshold Values
After you have activated your properties variant, you can check the threshold values
for the monitoring attributes that you regard as important and that you have included
in your own monitors.
To do this, open your monitor in the CCMS Alert Monitor (transaction RZ20). Select
a monitoring attribute and choose Properties. The current tab page displays the valid
threshold value definition.
The thresholds for Change from GREEN to YELLOW and Change from YELLOW to
GREEN are usually defined to change sooner than the thresholds for Change from
RED to YELLOW and Change from YELLOW to GREEN. In this way, you can avoid
your monitor flickering, if the measured value is wavering around the threshold value.
It is useful to give an all clear only once the situation has markedly improved.
Choose Display → Change. You can now adjust the threshold values to your
requirements. Save your settings.
You can now choose, in a dialog box, in which properties variant your changed
threshold values are to be stored. Note that the currently active variant is preselected.
You can change the selection as desired.
You can copy these settings to a transport request and transport them to other SAP
systems. To transport the threshold values, choose Properties → Variants → Overview
of Variants in transaction RZ21. In the overview of variants, choose Variant →
Transport. By doing this, you create a transport request that can be transported to
other SAP systems using the transport management system (TMS).
2005/Q2
© 2005 SAP AG. All rights reserved.
469
Unit 14: System Monitoring
470
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Properties Variants and Threshold Values
Exercise 29: Properties Variants of Monitors
Exercise Objectives
After completing this exercise, you will be able to:
•
Create a properties variant
Business Example
Alert monitors can only be meaningfully used if the selected threshold values for
the individual monitoring attributes are set to sensible values. It is not possible to
recommend values that are generally valid, since different values are appropriate
depending on the system or operation mode.
Task 1: Create a Properties Variant
1.
Create your own properties variant, TEST, in your SAP system.
Activate your properties variant.
Task 2: Maintain Threshold Values
1.
Maintain the threshold values for a monitoring attribute in your monitor. To
do this, find a monitoring attribute from your SAP system, for which you can
maintain the thresholds for:
Green to yellow
Green to red
Red to yellow
Yellow to green
Change these threshold values and save them.
Hint: These threshold values can only be defined for performance
monitoring attributes. There are two other monitoring attribute types, for
which threshold values are specified in a different way.)
Task 3: Switch Properties Variants Manually
1.
2005/Q2
Activate the “*” properties variant in transaction RZ21. What has happened to
the threshold values for the MTE that you set in task 2?
© 2005 SAP AG. All rights reserved.
471
Unit 14: System Monitoring
ADM100
Solution 29: Properties Variants of Monitors
Task 1: Create a Properties Variant
1.
Create your own properties variant, TEST, in your SAP system.
Activate your properties variant.
a)
Call the configuration transaction for the CCMS Alert Monitor (Tools →
CCMS → Configuration → Attributes and Methods, transaction RZ21).
Choose Properties → Variants → Create.
Enter TEST as the variant name and enter a short description.
Choose Save.
Choose Properties → Variants → Activate.
Select your variant TEST and choose Enter. The TEST variant is displayed
as the active variant in the initial screen of transaction RZ21.
Task 2: Maintain Threshold Values
1.
Maintain the threshold values for a monitoring attribute in your monitor. To
do this, find a monitoring attribute from your SAP system, for which you can
maintain the thresholds for:
Green to yellow
Green to red
Red to yellow
Yellow to green
Continued on next page
472
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Properties Variants and Threshold Values
Change these threshold values and save them.
Hint: These threshold values can only be defined for performance
monitoring attributes. There are two other monitoring attribute types, for
which threshold values are specified in a different way.)
a)
To do this, call transaction RZ20 and select your monitor. Show a
description of the symbols that are used in the monitor by choosing Extras
→ Legend. The icon for a performance attributes is a graph.
Search for a performance attribute for your SAP system in your monitor
(such as the average dialog response time). Place the cursor on a
monitoring attribute and choose Properties.
The current threshold values display on the Performance Attribute tab
page. Do you consider the threshold values to be appropriate? Choose
Display <-> Change and change the threshold values.
Choose Save. In the Monitoring: Properties and Methods window, select
your properties variant TEST and confirm by choosing Continue.
The threshold values are successfully adjusted and stored in your properties
variant.
SAP recommends that you perform this check for all monitoring attributes
for your system that are important for you. To activate the threshold values
in other systems, you can transport your properties variant to these systems.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
473
Unit 14: System Monitoring
ADM100
Task 3: Switch Properties Variants Manually
1.
Activate the “*” properties variant in transaction RZ21. What has happened to
the threshold values for the MTE that you set in task 2?
a)
Call the configuration transaction for the CCMS Alert Monitor (Tools →
CCMS → Configuration → Attributes and Methods, transaction RZ21).
Choose Properties → Variants → Activate.
Select the variant “*” and choose Enter. The “*” variant displays as the
active variant in the initial screen of transaction RZ21.
Now open the Core_information monitor in transaction RZ20. Search for
the monitoring attribute where you changed the threshold values in task 2.
The threshold values have returned to their original values, which are
fixed in the “*” properties variant.
If you reactivated your TEST properties variant in transaction RZ21, the
changed settings would become active again.
474
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Properties Variants and Threshold Values
Lesson Summary
You should now be able to:
•
Activate threshold values that are suitable for your system environment
Related Information
For more information about the CCMS Alert Monitoring Infrastructure, see:
•
•
2005/Q2
The SAP Service Marketplace: Quick Link /systemmanagement → System
Monitoring and Alert Management
SAP course ADM106 - Advanced SAP System Monitoring. This course focuses,
in particular, on the configuration of methods (analysis and auto-reaction) and
the use of rule-based monitors.
© 2005 SAP AG. All rights reserved.
475
Unit 14: System Monitoring
ADM100
Lesson: Concept of the SAP Solution Manager
Lesson Overview
The SAP Solution Manager is a tool that provides the administrator with a large
number of functions for administering a complex system landscape. This lesson
provides an overview of these functions.
Lesson Objectives
After completing this lesson, you will be able to:
•
Describe the added value of the SAP Solution Manager in an SAP system
landscape
Business Example
The SAP Solution Manager provides a central service and support portal and therefore,
supports the administrator in his or her daily work.
Introduction
The SAP Solution Manager is a service and support platform for the implementation
and operation of SAP systems. It provides content, tools, and procedures for
implementing, operating and supporting SAP systems.
The SAP Solution Manager...
•
•
•
•
Increases the reliability of your SAP systems
Reduces the Total Cost of Ownership of your SAP solutions
Increases the return on investment provided by your SAP solutions
Is included in the maintenance charges for your SAP systems
The SAP Solution Manager supports customers at the start of the project (to implement
an SAP solution), during functional and technical implementation, during running
operation, and during the optimization of their system landscapes. The SAP Solution
Manager also makes it possible to communicate with SAP and its partners at any time
and therefore, enhances the extensive on-site service.
476
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of the SAP Solution Manager
Figure 167: What Can the SAP Solution Manager Do?
The SAP Solution Manager is the central implementation and operation platform for
SAP solutions. To be able to use this central platform, first maintain the systems in
your solution landscape in the Solution Manager System Landscape (transaction
SMSY) (see also SAP Tutors under the Quick Link rkt-solman → Technology
Consultant/System Administrator on the SAP Service Marketplace).
Connecting your systems to the SAP Solution Manager then provides you, for
example, with central distribution and synchronization of Customizing, central test
management, monitoring, and Incident Management. For clearer monitoring and
documentation, the systems are combined into Solution Landscapes.
Your core business processes, together with the supporting technical components are
documented in these Solution Landscapes. From release 3.2 of the SAP Solution
Manager, the business processes are maintained centrally in the Solution Directory
(transaction SOLMAN_DIRECTORY), to which all SAP Solution Manager functions
have access. For monitoring, you can, however, also create Solution Landscapes
where systems are exclusively monitored on the basis of Early Watch alerts (EWAs)
or the CCMS. A system can be part of multiple landscapes.
The SAP Solution Manager provides many functions for the implementation and
operation of your mySAP Business Suite solution(s).
2005/Q2
© 2005 SAP AG. All rights reserved.
477
Unit 14: System Monitoring
ADM100
Figure 168: Functions of the SAP Solution Manager
Some Functions of the SAP Solution Manager
•
•
•
•
•
•
478
Preventative services: EarlyWatch Alert, GoingLive Check, and GoingLive and
Functional Upgrade Check.
Continuous Improvement Services: Solution Management Review Service
(SMR) and Solution Management Optimization Services (SMO)
Best Practices for the SAP solution that you have implemented: Documents
and services that are based on SAP's experience from production customer
installations.
Application and System Monitoring: Technical monitoring of your SAP solution
including the availability of interfaces, individual system components, business
process monitoring, Service Level and a graphical alert monitor.
SAP Service Desk: Central message management for all SAP solutions
(including attached files or error contexts), interface to the SAP Service
Marketplace, SAP Notes database search and automatic import of SAP Notes
(Note Assistant), and the customer solution database for customer-specific
questions and answers.
SAP Remote Support: Security solution for Microsoft NetMeeting using
SAProuter, remote access through Internet connections, end user desktop
application sharing with SAP experts.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of the SAP Solution Manager
Installation of the SAP Solution Manager
The SAP Solution Manager is installed on a separate system. For the SAP Solution
Manager 3.2, this system is based on SAP CRM, built on SAP Web AS 6.20. For an
overview of the release strategy and the platform requirements, see the SAP Service
Marketplace (http://service.sap.com/solutionmanager → Release Strategy).
The next figure shows the required software components of SAP Solution Manager
3.2.
Figure 169: Software Components of the SAP Solution Manager
The SAP Solution Manager is available free of charge in the context of your
maintenance contract. You can order the installation through the SAP Service
Marketplace (http://service.sap.com/solutionmanager→ Order Information).
Areas of Operation of the SAP Solution Manager
The SAP Solution Manager provides many functions for implementing and operating
SAP solutions. During implementation, project activities are primarily supported with
project planning tools.
2005/Q2
© 2005 SAP AG. All rights reserved.
479
Unit 14: System Monitoring
ADM100
Figure 170: SAP Solution Manager - Implementation Functions
The SAP Solution Manager supports you in performing central activities during the
implementation.
•
•
•
•
480
Project management support with which you can manage scheduling periods,
employees, and other project information.
A Business Process Repository, which provides templates for mapping
processes. These templates are required to define the project scope and the
central enterprise processes.
Tools for implementing the integrated business scenarios.
Integrated Implementation Guides that support you during the Customizing
activities for the business processes.
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of the SAP Solution Manager
Figure 171: SAP Solution Manager - Operation Functions
•
•
•
•
•
Support when monitoring business processes
Central system monitoring
Possibilities for central administration tasks
Best Practices are provided
Remote Services, such as the SAP EarlyWatch Alert Service and others
You can easily order services using the SAP Solution Manager. The process of an
order is outlined in the following figure.
2005/Q2
© 2005 SAP AG. All rights reserved.
481
Unit 14: System Monitoring
ADM100
Figure 172: Service Suggestions and Service Ordering
The SAP Solution Manager can provide you with suggestions for services which,
depending on your system landscape, are useful for your system environment.
Monitoring with the SAP Solution Manager
The SAP Solution Manager provides many options for monitoring your SAP systems
(that are connected to the SAP Solution Manager). You can not only monitor
individual systems, but also check the run times of cross-system business processes.
Many reporting functions are also provided.
482
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of the SAP Solution Manager
Figure 173: System Monitoring with the SAP Solution Manager
The monitoring architecture of the SAP Solution Manager is outlined in the figure.
The satellite systems automatically collect the actual data. The SAP Solution Manager
collects this data, aggregates it, evaluates it, and displays the result graphically.
CCMS Monitoring (RZ20) and the Service Data Control Center (SDCC) act as data
collectors on the satellite system side.
The SAP Solution Manager's system monitoring uses the data from CCMS monitoring
and displays this in a business process-oriented context. You can set up central
monitoring of all components of your SAP systems relevant to operation here, as
in CCMS monitoring. You can also use predefined alert messages, which react to
customizable threshold values.
The business process monitoring allows your departments to obtain a quick overview
of the technical status of your business processes. CCMS and other alerts are
displayed graphically and oriented by business process. This graphical display
helps you to quickly identify the process where a problem has occurred. Detailed
information about the problem, and the possibility to escalate the problem using a
Service Desk message are linked to the warning message.
You can define system status reports yourself using Service Level Management.
These include the EarlyWatch Alert or the Service Level Report, which automatically
provide you with regular reports (in HTML or Microsoft Word format) about the
current status of your mySAP.com solution. You only need to schedule these services
once. They then collect data about your systems regularly, aggregate it, and evaluate it.
2005/Q2
© 2005 SAP AG. All rights reserved.
483
Unit 14: System Monitoring
ADM100
The Service Desk of the SAP Solution Manager
The Service Desk of the SAP Solution Manager provides a complete IT infrastructure
for providing back office support with message handling for your SAP solution in
your company. The system where the SAP Solution Manager is installed acts as a
central collection point for all support messages that are created in your SAP systems
(see following figure).
Figure 174: End User Message Creation
484
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of the SAP Solution Manager
Figure 175: SAP Service Desk
All end users can send a message to your back office from any SAP transaction by
choosing Help → Create Support Message. When they do so, important system
data is automatically attached to the message, which significantly speeds up error
identification and message processing. This message is sent directly to the SAP
Solution Manager using an RFC connection. It is possible to sort the message using
components and to assign an urgency level to the message. External files can, of
course, be included.
The back office department can view and process the messages created by the end
users in the SAP Solution Manager. To solve any end user problems, support has
direct access to all SAP Notes, their own customer solutions database (SAP R/3
4.6C only), and other documents and tools that are provided by SAP on the SAP
Service Marketplace. After a successful search for a problem solution, support can
send the message back to the user with a description of the solution. In urgent cases
or for very special problems, support can forward the error message to SAP through
the SAP Service Marketplace.
2005/Q2
© 2005 SAP AG. All rights reserved.
485
Unit 14: System Monitoring
ADM100
With SAP Solution Manager 3.2, another new function, Change Request Management,
has been added. This provides many functions to control development and
Customizing activities in your SAP systems.
•
•
•
•
•
486
Manage all change requests
Classify change requests
Approver workflow
Status tracing
Complete change history
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Concept of the SAP Solution Manager
Lesson Summary
You should now be able to:
•
Describe the added value of the SAP Solution Manager in an SAP system
landscape
Related Information
•
2005/Q2
On the SAP Service Marketplace under http://service.sap.com/solutionmanager
© 2005 SAP AG. All rights reserved.
487
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
Explain the concepts of the CCMS Alert Monitoring Infrastructure
•
Use the CCMS Alert Monitor to monitor your system
•
Configure the central monitoring of remote systems
•
Design and create your own monitors
•
Activate threshold values that are suitable for your system environment
•
Describe the added value of the SAP Solution Manager in an SAP system
landscape
488
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
What can alert monitoring be used for?
Choose the correct answer(s).
□
□
□
□
2.
A
B
C
D
Database backup
Updating data
Monitoring the database and the SAP system
Configuring and monitoring the firewall
Why include remote systems in your alert monitoring?
Choose the correct answer(s).
□
□
□
□
□
3.
A
B
C
D
E
To transport program code from system to system
To create a local connection to a database backup of remote systems
To monitor these remote systems centrally
To allow file sharing
To connect an LDAP server
What types of monitors are there in the SAP system?
Choose the correct answer(s).
□
□
□
□
□
4.
A
B
C
D
E
Ruled monitors
Statistical monitors
Rule-based monitors
Static monitors
Self-Repairing monitors
Properties variants are used to...
Choose the correct answer(s).
□
□
□
□
2005/Q2
A
B
C
D
Store user master data
Customize transport requests
Store CCMS alert monitoring settings
Store combinations of parameters for calling an ABAP report
© 2005 SAP AG. All rights reserved.
489
Test Your Knowledge
ADM100
Answers
1.
What can alert monitoring be used for?
Answer: C
Monitoring objects are only monitored, not administered using alert monitoring.
The range of objects monitored is very large, since monitors can also be created
for exotic objects.
2.
Why include remote systems in your alert monitoring?
Answer: C
Including remote systems should allow you to monitor these systems centrally.
3.
What types of monitors are there in the SAP system?
Answer: C, D
There are static and rule-based monitors.
4.
Properties variants are used to...
Answer: C
CCMS alert monitoring settings are stored with properties variants.
490
© 2005 SAP AG. All rights reserved.
2005/Q2
Unit 15
Structured Troubleshooting
Unit Overview
One of the tasks of system administrators is to localize and correct errors when they
occur. This unit provides an overview of different trace options in the system and
allows you to perform a number of traces.
Unit Objectives
After completing this unit, you will be able to:
•
•
•
•
List various trace options
Perform simple traces in the SAP system
Develop procedures for structured troubleshooting
Perform troubleshooting if problems occur in front-end printing
Unit Contents
Lesson: Trace Options ............................................................. 492
Exercise 30: Trace Options ................................................... 501
Lesson: Troubleshooting Procedure ............................................. 505
Lesson: Appendix: Troubleshooting Example .................................. 509
Exercise 31: Appendix: Error Analysis for Front-End Printing
(OPTIONAL)..................................................................... 521
2005/Q2
© 2005 SAP AG. All rights reserved.
491
Unit 15: Structured Troubleshooting
ADM100
Lesson: Trace Options
Lesson Overview
In this lesson, you will learn about the different trace options in the SAP system. You
will perform and evaluate a trace yourself.
Lesson Objectives
After completing this lesson, you will be able to:
•
•
List various trace options
Perform simple traces in the SAP system
Business Example
An unexpected, reproducible error situation is occurring in your SAP system. As a
member of the system administration team, it is your task to find the cause of the error.
Introduction
You can follow the process of various operations in your SAP system with trace
functions. This allows you to monitor the system and isolate problems that occur.
There are two types of trace: the performance trace and the system trace. You can
also use developer traces and the system log to correct problems. The following
trace options exist in the system:
•
•
•
•
•
System Log (SM21)
Dump Analysis (ST22)
System Trace (ST01)
Performance Trace (ST05)
Developer Traces (ST11)
You can use the System Log (transaction SM21) to detect and correct errors in your
system and its environment. SAP application servers record events and problems in
system logs. Every SAP application server has a local log that contains the messages
output by this server.
If unpredictable errors occur during runtime when you call an ABAP program, a
runtime error that generates a short dump can occur (transaction ST22).
492
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Trace Options
If you want to record the internal SAP system activities, such as authorization checks,
database accesses, kernel functions, and RFC calls, use the System Trace function
(transaction: ST01).
The Performance Trace (transaction ST05) allows you to record database calls, lock
management calls, and remote calls of reports and transactions in a trace file and to
display the logged measurement results as lists. The Performance Trace also offers
extensive support for a detailed analysis of individual trace records.
Technical information about internal SAP problems is logged in developer traces.
System Log
Events and problems are recorded locally on each application server and displayed in
the system log in the SAP system.
Figure 176: System Log (SM21)
If you are using the UNIX operating system, you can also work with central logging.
In this case, each application server copies its local logs to a central log. Central
logging is not possible on Microsoft Windows NT and AS/400 hosts. Technically, the
system log is written to a ring buffer. If this log file reaches the maximum permitted
size, the system begins to overwrite the oldest data.
Hint: The system does not display a message when an old log file is replaced.
2005/Q2
© 2005 SAP AG. All rights reserved.
493
Unit 15: Structured Troubleshooting
ADM100
To display a log, choose Tools → Administration → Monitor → System Log or call
transaction SM21. By default, the system reads the log for the last one to two hours.
As well as the local system log, you can display system logs for other application
servers in transaction SM21. To do this, choose the menu path System Log → Choose
→ All Remote System Logs or System Log → Choose →Central System Log.
In expert mode (menu path Edit → Expert Mode), you can extend the selection criteria
so that it is possible to search for entries for a particular terminal. To do this, choose
the Attributes button.
In UNIX systems, you can display the status of the send process in the SAP system
with transaction SM21 or by choosing Environment → Process Status.
You can define the path and file names for local and central log files with the following
system profile parameters:
•
•
rslg/local/file: File name for the local log (Default: SLOG<SAP_SYSTEM_NUMBER>)
rslg/central/file: File name for the active central log (Default: SLOGJ); does not
apply for Microsoft Windows NT and AS/400 platforms
By default, the log files for the local system log are stored in the following directory:
/usr/sap/<SID>/<instance_directory>/log. The central system log is stored in
/usr/sap/<SID>/SYS/global
You can also schedule system logging as a background job. There are two ABAP
programs provided to do this:
•
•
RSLG0000: To create the local system log
RSLG0001: To create the central system log (not on Microsoft Windows NT
and AS/400 platforms)
Dump Analysis
ABAP programs are checked statically when they are created and dynamically when
they are running. Error states, which are not statically predictable and only occur at
runtime are dynamically identified by the ABAP runtime environment. States of this
type lead to exceptions. If an exception is not handled or cannot be handled, a runtime
error occurs. If a runtime error occurs, the ABAP runtime environment terminates the
execution of the program, generates a short dump and branches to a special screen for
analyzing the short dump. You can also find short dumps in transaction ST22 or by
choosing the menu path Tools → ABAP Workbench → Test → Dump Analysis.
494
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Trace Options
A short dump is divided into different sections that document the error. The overview
shows what other information is output in the short dump, such as contents of data
objects, active calls, control structures, and so on. You can branch to the ABAP
Debugger at the termination point from the short dump view. The following different
error situations exist:
•
Internal Error
The kernel identifies an error state. In this case, notify SAP.
•
Installation and Environment/Resource Error
In this case, an error occurred that was caused by incorrect system installation or
missing resources (such as the database being shutdown).
•
Error in Application Program
Typical causes of errors are:
–
–
–
–
Content of a numerical field not in the correct format
Arithmetic overrun
An external procedure is not available
Type conflict when transferring parameters to an external procedure
By default, short dumps are stored in the system for 14 days. The transaction for
managing short dumps is ST22. You can delete short dumps in accordance with a time
specification using the Reorganize function, which you can call by choosing Goto →
Reorganize. You can save a short dump without a time limit using the Keep function,
which you can choose under Short Dump → Keep/Release.
If problems that you cannot solve yourself occur with ABAP programs, you can send
an extract of the short dump to SAP. A short dump is the basis on which the SAP
Hotline and remote consulting solve problems.
•
•
•
•
If a runtime error occurs, a short dump is generated. You can use transaction
ST22 to analyze this short dump.
Dump data is stored in the database.
Dump data can be reorganized.
Individual short dumps can be flagged for retention.
SAP System Trace
You can use the system trace to record internal system activities. The system trace is
primarily used if an authorization trace is to be created. SAP recommends that you
use the system log or the developer trace for system monitoring and problem analysis.
2005/Q2
© 2005 SAP AG. All rights reserved.
495
Unit 15: Structured Troubleshooting
ADM100
You can call the SAP System Trace using transaction ST01 or by choosing the menu
path Tools → Administration → Monitor → Traces → System Trace. You can also
use transaction ST01 to display the inactive trace file.
You can use the SAP system trace to monitor the following components:
•
•
•
•
•
•
Authorization checks
Kernel functions
Kernel modules
DB accesses (SQL Trace)
Table buffers
Lock operations (client-side)
You select the components to be logged on the initial screen. If the trace is activated
for the authorization check, all authorization checks performed by the system are
recorded. During the evaluation, you can identify which authorizations the system
checked at which times. The following detail information is also provided: Date,
time, work process number, user, authorization object, program, line, number of
authorization values, authorization values.
You can use the SQL Trace to follow how the Open SQL commands in reports and
transactions are converted to standard SQL commands and the parameters with which
the SQL commands are transferred to the database system in use. The results of the
SQL command are also logged, such as the return code and the number of records
found, inserted, or deleted by the database. Logging the execution time and the
callpoint in the application program allows you to perform more advanced evaluations.
With the enqueue trace, you can follow which lock instructions the SAP system
performs on which lock objects, and which parameters the system uses for these locks.
The program that triggered the lock, the owner of the lock, and the time that the
enqueue server required to release the lock again are all also logged in the trace file.
You can use the RFC trace to follow which remote calls the SAP system executes,
and the instance on which these calls are executed. You can see from the trace which
function modules were called remotely by the program that is to be analyzed, and
whether the RFC was successfully executed. The total time required for the execution
of the remote call and the number of bytes sent and received during the RFC are also
logged in the trace file.
496
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Trace Options
Figure 177: SAP System Trace (ST01) and Performance Trace (ST05)
Performance Trace
The performance trace provides the following functions:
•
•
•
•
•
•
Recording database calls
Recording lock management calls
Table buffers
Recording remote calls of reports and transactions
Detailed analysis of individual trace records
Analysis of an SQL statement
The performance trace provides similar trace options to the system trace. It allows you
to record database calls, calls to lock management, calls to table buffers, and remote
calls of reports and transactions from the SAP system itself in a trace file. You can
call the Performance Trace using transaction ST05 or by choosing the menu path
Tools → Administration → Monitor → Traces → Performance Trace. On the initial
screen of transaction ST05, you can choose the Explain SQL button to analyze an SQL
statement without branching to a specific trace file.
The performance trace is integrated into the ABAP Workbench as a test tool and can
therefore be called there.
2005/Q2
© 2005 SAP AG. All rights reserved.
497
Unit 15: Structured Troubleshooting
ADM100
Configuring the Trace File
You can use system profile parameters to restrict the size of the trace files and to
specify an appropriate path.
The SAP System Trace writes the trace data in its trace files. For performance
reasons, this is not done directly, but rather using a process-internal buffer. The profile
parameter rstr/buffer_size_kB determines the size of the buffer. Since SAP Web AS
6.10, the SAP trace stores the data in multiple files, which are written in turn. The
parameter rstr/filename defines the base name of these files. There is always a file
with exactly this name. When the file becomes full (parameter rstr/max_filesize_MB
), the file is renamed and a new file is generated with the base name. When the file
is renamed, a number between 00 and 99 is added to the file name. The parameter
rstr/max_files determines the maximum total number of files. If this value is
exceeded, the files are overwritten.
Developer Trace
Developer traces are recordings that contain technical information and that are used
if errors occur. This type of process trace is especially useful to investigate host and
internal SAP problems that are affecting your SAP system. Developer traces dev_ *
are written to files in the directory /usr/sap/<SID>/<instance directory>/work of the
SAP application server that generated the trace.
Figure 178: Developer Traces
498
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Trace Options
You can access the developer traces using the operating system, using transaction
AL11, or from transaction SM50 (Work Process Overview). In transaction SM50,
you can switch to the individual dev_* traces by choosing Process → Trace →
Display File. You can display additional details in the displayed traces by expanding
individual entries.
2005/Q2
© 2005 SAP AG. All rights reserved.
499
Unit 15: Structured Troubleshooting
ADM100
500
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Trace Options
Exercise 30: Trace Options
Exercise Objectives
After completing this exercise, you will be able to:
•
Use trace options in the SAP system to analyze the problem if errors occur
•
Use the transactions for the various trace functions
Business Example
You want to use trace functions in the SAP system to correct errors.
Task 1: Traces
Activate traces in the SAP system and evaluate them. Generate a short dump in the
system and analyze it.
1.
In transaction ST01, activate the trace for authorization checks, RFC calls, and
for lock operations for your user. Start the transaction for user maintenance
SU01 and change the title for your own user.
2.
Deactivate the trace again and evaluate the trace file.
3.
In transaction ST05, activate the SQL trace for your user. Start transaction SA38
and run program RSUSR000. Deactivate the trace again and evaluate it.
Task 2: Analyze a Short Dump
Generate a short dump and analyze it.
1.
2005/Q2
Use the Function Builder (transaction SE37) to execute the remote-capable
function module RFC_SYSTEM_INFO with the RFC connection TRACES_ST22.
Analyze the short dump that occurs when you do so.
© 2005 SAP AG. All rights reserved.
501
Unit 15: Structured Troubleshooting
ADM100
Solution 30: Trace Options
Task 1: Traces
Activate traces in the SAP system and evaluate them. Generate a short dump in the
system and analyze it.
1.
2.
3.
In transaction ST01, activate the trace for authorization checks, RFC calls, and
for lock operations for your user. Start the transaction for user maintenance
SU01 and change the title for your own user.
a)
Call transaction ST01 and select authorization check, RFC calls, and lock
operations. In addition, you can choose the General Filters button to restrict
the trace to your own user. Start the trace by choosing the Trace on button.
b)
Call transaction SU01. Select your user and choose the menu entry Users
→ Change. On the Address tab page, change the title, and save your
change.
Deactivate the trace again and evaluate the trace file.
a)
Call transaction ST01 and choose the Trace off button.
b)
To evaluate the generated trace file from transaction ST01, choose Goto →
Analysis and select Authorization Check, RFC Calls, and Lock Operations.
Start the analysis by choosing Start Reporting. You can now jump directly
to the program code by selecting a data record and then choosing the Go
to ABAP Position button.
In transaction ST05, activate the SQL trace for your user. Start transaction SA38
and run program RSUSR000. Deactivate the trace again and evaluate it.
a)
Call transaction ST05 and select SQL Trace. Start the trace by choosing
the Activate Trace with Filter button, and enter your user as the selection
criterion.
b)
Start program RSUSR000 in transaction SA38 and stop the trace in
transaction ST05 by choosing Deactivate Trace.
c)
To evaluate the generated trace file, call transaction ST05, choose the
Display Trace button, and select SQL Trace. You can now display the SQL
commands in plain text by selecting a data record and choosing Explain.
Continued on next page
502
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Trace Options
Task 2: Analyze a Short Dump
Generate a short dump and analyze it.
1.
2005/Q2
Use the Function Builder (transaction SE37) to execute the remote-capable
function module RFC_SYSTEM_INFO with the RFC connection TRACES_ST22.
Analyze the short dump that occurs when you do so.
a)
Call transaction SE37 and enter the remote-capable function module
RFC_SYSTEM_INFO in the Function Module field. Test the function
module by choosing Function Module → Test → Single Test or F8. On
the next screen, enter the following RFC connection in the RFC target sys:
TRACES_ST22. Now choose Function modules → Execute or F8 to start
the function module. A short dump is generated.
b)
Start transaction ST22 and display the short dumps from today by choosing
the Today button. Find the relevant entry and display the details by
double-clicking the entry, or by choosing Short Dump → Display Long
Text. Read the text in the Error Analysis section. The error text partner not
reached (host localhost, service sapgw23) displays, that is, the instance
number 23 is entered in the RFC connection, although this instance does
not exist.
© 2005 SAP AG. All rights reserved.
503
Unit 15: Structured Troubleshooting
ADM100
Lesson Summary
You should now be able to:
•
List various trace options
•
Perform simple traces in the SAP system
504
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Troubleshooting Procedure
Lesson: Troubleshooting Procedure
Lesson Overview
This lesson describes a general procedure for troubleshooting.
Lesson Objectives
After completing this lesson, you will be able to:
•
Develop procedures for structured troubleshooting
Business Example
Unexpected problems are occurring during running operation of your SAP systems.
As a member of the system administration team, you want to learn about the procedure
for structured troubleshooting.
General Approach
It is part of their nature that errors always occur in places that they should not occur. It
is, therefore, only possible to present a general approach. Front-end printing is used to
represent possible errors, for example.
You will run through the steps identified in the next figure “Troubleshooting:
Approach” when troubleshooting.
2005/Q2
© 2005 SAP AG. All rights reserved.
505
Unit 15: Structured Troubleshooting
ADM100
Figure 179: Troubleshooting: Approach
Isolate the problem area: First, attempt to isolate the error. Where does it occur, when
does it occur, and in what context does it occur? “It doesn't print”, would be too
imprecise here. “Front-end printing on front-end xyz does not work with any SAP
system”, is more exact. If you also know that front-end printing works on other front
ends, you have already isolated the problem.
Problem Analysis: Check the scenario to find out whether all required settings, and
so on are correct. Check the application logs, the system log, and the traces (the
developer traces will usually be helpful here), to see whether they provide any clues
for correcting the error.
Gain additional knowledge: To interpret the results from the first problem analysis, it
is, of course, necessary that you are familiar with the processes and functions of the
area in which the error is occurring. If your experience and your previous knowledge
are insufficient, you can start a search in the SAP Notes and on the SAP Service
Marketplace with the keywords from the system log or the trace files. You may find
a problem solution here, or additional information that helps you find and correct
the error. If you have not found any suitable SAP Notes or suitable search terms,
search for composite notes for the topic area. In this case, for example, with the terms
Front-end printing and composite note. For additional background information for
506
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Troubleshooting Procedure
the topic area, see the online documentation and course materials. If you still cannot
solve the problem with this information, use the comparison between the process
with errors, and an error-free process.
Compare error-free and erroneous processes: You can use this to determine where
there are differences between an erroneous and an error-free process. This information
helps you to further isolate the problem area and may help you to solve the problem
or to perform new, more targeted problem analyses. If it is not possible to perform
another problem analysis, create a message for SAP on the SAP Service Marketplace.
Enter the information from your troubleshooting (such as a trace and/or system log
information) when doing so.
2005/Q2
© 2005 SAP AG. All rights reserved.
507
Unit 15: Structured Troubleshooting
ADM100
Lesson Summary
You should now be able to:
•
Develop procedures for structured troubleshooting
508
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
Lesson: Appendix: Troubleshooting Example
Lesson Overview
This lesson is intended as an appendix to the Troubleshooting Procedure lesson. The
troubleshooting procedure is shown using an example of troubleshooting front-end
printing. If problems occur with front-end printing, this lesson will help you to
understand front-end printing better and make it possible to correct the error.
Lesson Objectives
After completing this lesson, you will be able to:
•
Perform troubleshooting if problems occur in front-end printing
Business Example
Unexpected problems are occurring with front-end printing during running operation
of your SAP systems. As a member of the system administration team, you want to
learn about the procedure for structured troubleshooting for front-end printing.
Troubleshooting Front-End Printing
General Conditions
Assume here that there are problems with front-end printing, and you have isolated
them as follows: Problems are occurring with front-end printing for all SAP systems
at some front ends. As an example, you will now analyze the problems between an
SAP system and a front end and correct the error. The error correction can then be
performed on the other SAP systems or front ends in the same way.
Search for Information about the Error:
•
•
•
Checking the system log does not provide any relevant information about the
error
Checking the developer trace does not provide any relevant information about
the error
In transaction SP01, you find the information that SAPLPD cannot be started
Your search in the SAP Notes Database on the SAP Service Marketplace with the
keywords frontend printing and SAPLPD provides, among other things, SAP Note
“379515: Troubleshooting frontend printing”. This SAP Note provides additional
useful information about the process of front-end printing and troubleshooting
2005/Q2
© 2005 SAP AG. All rights reserved.
509
Unit 15: Structured Troubleshooting
ADM100
front-end printing. The following sections “Process of a Front-End Print” and
“Activating the Trace” contain information from this SAP Note that is useful for
additional error analysis.
Process of a Front-End Print
The end user is logged on to an SAP system with SAP GUI. A list is to be printed
using front-end printing (access method F) on the “default” front-end printer.
If the end user has selected the output device for front-end printing and the print
time Print immediately, then the first step is processing by a dialog work process. It
creates a spool request. In the second step, the spool work process is given the task of
outputting the spool request. If a spool work process is running on the application
server (on which the user is logged on), it processes the spool request. Otherwise, a
spool work process on a different application server is used. The spool work process
creates an output request and transfers this to the SAP GUI of the end user in the third
step. In the fourth step, the SAP GUI uses lprintg.dll to start saplpd (if this is not
already running), and the data is transferred to this program. saplpd receives the
data and forwards it to the operating system spooler. In the fifth step, the data is
transferred from the operating system spooler to the printer. See the figure Process
of Front-End Printing 1.
Figure 180: Process of Front-End Printing 1
510
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
During the error analysis, this route is reproduced step-by-step, and checked to find
out whether or which errors occur during it. To do this, it is necessary to activate
the trace options at various points. The following procedure has been successfully
used in practice:
2005/Q2
© 2005 SAP AG. All rights reserved.
511
Unit 15: Structured Troubleshooting
ADM100
Activating the Trace:
•
•
•
•
In transaction SPAD, copy the output device that has problems with front-end
printing and use this new output device for your tests during troubleshooting.
The new short name helps you to locate trace output.
Activate the debugger for the front-end printer in transaction SPAD, by choosing
Edit → Test Tool. The system displays a new tab page where you should activate
a level 2 trace. Trace data is now logged in the processing dialog work process.
In addition, on the tab page, you can choose to log the first 10 KB or 100 KB.
You can then use transaction SP01 to display this data.
On the initial screen of transaction SPAD, choose Settings → Spool System.
On the Frontend Prnt. tab page, set the Trace level for frontend printing to 1.
This means that additional trace data is logged for SAP GUI communication in
the processing spool work process.
Check whether you have the newest version of LPRINTG.DLL on the front
end. To do this, choose the menu entry About SAP Logon in SAP Logon and
then Loaded DLLs.
Caution: LPRINTG.DLL is only loaded once you have logged on
to the SAP system.
If necessary, install the newest version of LPRINTG.DLL and the newest
version of SAPLPD in the SAPgui directory. Use SAP Note 328252 on the SAP
Service Marketplace to do this. You can download the dll directly from there,
from the Attachments tab page (you may have to display additional tab pages
first by choosing the double arrow). After installing the dll, log off all SAP
systems on the front end and log on to the SAP system in which you want to
solve the front-end printing problems.
•
Activate the trace for LPRINTG.DLL by setting the environment variable
DPTRACE to 3. With Microsoft Windows 2000, you set environment variables
under System in the Control Panel. On the Advanced tab page, choose
Environment Variables.... The system then displays a window in which you can
set the environment variables under System Variables.
Caution: After setting the environment variable, you must close and
then restart SAP Logon.
The trace output is written to the file lprintg.log, which is usually in the
SAPworkdir directory of your front end.
512
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
Figure 181: Process of Front-End Printing 2
If all traces are activated, you can perform a test print with the front-end printer (that
you copied for the test) (the figure Process of Front-End Printing 2 shows the process
of the front-end printing and the places in which trace information is written). Since
errors can, of course, also be user-dependent, the test should be performed under the
user with which the problems have occurred.
The first approach describes an error-free print process, which can then be used as a
guide for troubleshooting.
Error-Free Front-End Printing
Perform an error-free front-end print with the additional activated trace information.
Use this trace information when analyzing errors for comparison purposes and to
isolate the problem.
2005/Q2
© 2005 SAP AG. All rights reserved.
513
Unit 15: Structured Troubleshooting
ADM100
Figure 182: SP01 Output Request: 1
You obtain the first information in transaction SP01, for the output request. See the
figure SP01 Output Request: 1. The status provides a first clue about where problems
have occurred. You can view the complete status information by choosing the Output
Request Status button. You obtain more information in the Status Description Request
xxx dialog box by choosing Events.
Check Developer Traces
Figure 183: Dialog Work Process Trace: 1
You now check the traces in the sequence in which the data is processed. The spool
request is created by a dialog work process. Therefore, you check the developer trace
of the dialog work process that processed the request. To do this, you can search all of
the developer traces of the SAP application server where the user is logged on, or, in a
514
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
Command Prompt (in the case of UNIX: in a shell), switch to the SAP application
server's work directory. You can use the command qgrep from the Windows
Resource Kit to search for the trace file here. If the front-end printer has the short name
TFRP, the call is: qgrep -l -e TFRP dev_*. All trace files in which TFRP
(case-sensitive) appears display. The name of the developer trace where the text was
found displays at the start of each line (with UNIX: use the grep command to perform
the equivalent function). You can check the trace files from the operating system or
from transaction SM50 . The line S Send Message (P) to Spoolserver
xxx appears in the Printer Trace in the trace file of the dialog work process.
See also figure Dialog Work Process Trace: 1. A spool work process of the specified
spool server takes over the creation of the output request. You also find information
in the dialog work process trace about the spool number and output request number,
which helps you assign the trace data to the spool request (or output request).
Figure 184: Spool Work Process Trace: 1
In the spool work process trace, search for the location with the TCP_OPEN entries.
Highlighted section 1 in the figure Spool Work Process Trace: 1 shows the spool
number and output request number, with which you can ensure that you are viewing
the correct trace information. Highlighted section 2a shows the TCP_OPEN call to the
front end. The retcode = 2 in highlighted section 2b is the return value and means
that SAPLPD was not started. It is now started (TCP_START). The line in highlighted
section 3 specifies (retcode = 0), that SAPLPD is running and that data can be
transferred. The data transfer now takes place. This is the TCP_WRITE_BINARY
and TCP_READ_BINARY blocks. The line S <- TCP_CLOSE (msg = ,
retcode = 0) is the conclusion of the data transfer.
2005/Q2
© 2005 SAP AG. All rights reserved.
515
Unit 15: Structured Troubleshooting
ADM100
In the same way, you can find the corresponding information for the receiving side
on your front end in the lprintg.log file. The highlighted sections 2a and 2b in
the figure Spool Work Process Trace: 1 corresponds to the highlighted section in
the figure lprintg.log: 1.
Figure 185: lprintg.log: 1
In the first TCP_OPEN call, it is not possible to create a connection to SAPLPD
(message: NiRawConnect failed with code=-10), since it is not started.
SAPLPD is started in the TCP_START block. There is then another TCP_OPEN call,
which is successfully completed with the started SAPLPD. The data transfer now
takes place. This is the TCP_WRITE_BINARY and TCP_READ_BINARY blocks.
The data transfer ends at TCP_CLOSE finished.
516
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
Example 1: SAPLPD Could Not Be Started
Figure 186: SP01 Output Request: 2
You find the first clues to the problem in transaction SP01 (see the figure: SP01
Output Request: 2). Checking the spool trace produces the result that SAPLPD is not
started, and an error occurred when an attempt was made to start it. This is shown in
the TCP_START line by msg = INTERNAL and retcode = 1 (see the figure
Spool Work Process Trace: 2).
Figure 187: Spool Work Process Trace: 2
You find additional information on the front end in the lprintg.log log file (see the
figure: lprintg.log: 2).
2005/Q2
© 2005 SAP AG. All rights reserved.
517
Unit 15: Structured Troubleshooting
ADM100
Figure 188: lprintg.log: 2
The information in highlighted section 2 indicates that saplpd.exe could not be found.
The call path for SAPLPD relative to the SAP GUI directory is specified in the lines of
highlighted section 1. To correct the error, move SAPLPD to the specified directory.
Another test of the front-end printing should now run successfully.
Example 2: Port 515 Is Occupied on the Front End
You find the first clues to the problem in transaction SP01 (see the figure: SP01
Output Request: 3).
Figure 189: SP01 Output Request: 3
Checking the spool trace shows that SAPLPD is already started and that data is
transferred to it (see highlighted section 1 in the figure: Spool Work Process Trace: 3).
518
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
Figure 190: Spool Work Process Trace: 3
However, no SAPLPD was started on the front end. Further down in the spool trace
(highlighted section 2), you now see that an error is occurred during the data transfer
(msg = INTERNAL and retcode = 2). The log file lprintg.log contains the
corresponding entries for the front-end side. These are shown in the figure “lprintg.log:
3” as highlighted sections 1 and 2. Highlighted section 2 shows that an error occurred.
Figure 191: lprintg.log: 3
You can make the following conclusion: A program is listening at port 515 at the front
end (this is the default port, on which SAPLPD runs). The data is transferred to the
SAP GUI and forwarded to the port by lprintg.dll. This is why there are corresponding
entries in the log file lprintg.log. You can now configure a different port for the
program occupying port 515, or assign a different, free port to SAPLPD (follow the
instructions in SAP Note 114426 to do this).
2005/Q2
© 2005 SAP AG. All rights reserved.
519
Unit 15: Structured Troubleshooting
ADM100
520
2005/Q2
© 2005 SAP AG. All rights reserved.
ADM100
Lesson: Appendix: Troubleshooting Example
Exercise 31: Appendix: Error Analysis for
Front-End Printing (OPTIONAL)
Exercise Objectives
After completing this exercise, you will be able to:
•
Set and interpret the required traces to analyze front-end printing
Business Example
Errors are occurring with front-end printing. Your task is to localize and correct these
errors.
Task 1: Preparing the Analysis
Caution: You must perform the following task from the operating system of
your SAP system. This also applies for work that you would normally perform
at the front end. Ensure that you are logged on at operating system level as
<sid>adm. Start the SAP GUI from the operating system of the SAP system.
Prepare your system for analyzing front-end printing problems.
1.
In transaction SPAD, copy (or use Create Using Template) the front-end printer
tfrontendprinter to tfrontendprinter2 and assign the short name TFRP to
this output device. Activate the level 2 trace for this output device.
2.
Set the trace level for front-end printing to 1.
3.
Activate the trace for your user <sid>adm (using an entry in the User variables
for <sid>adm, not in the System variables) for LPRINTG.DLL, by creating
a new environment variable.
4.
For your user <sid>adm, set the environment variable LPRINT_PORT depending
on your <sid> (User variables for <sid>adm, not System variables). If your
<sid>=DEV, set the variable to 516. If your <sid>=QAS, set the variable to 517.
5.
Close all SAP GUIs and SAP Logon.
Caution: The environment variables that you have set only take effect
when you restart SAP Logon and with a new SAP GUI.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
521
Unit 15: Structured Troubleshooting
ADM100
Task 2: Perform a Front-End Print
Perform a front-end print on the server on which your SAP system is running.
1.
Use the front-end printer with the short name TFRP to perform a front-end print.
Print the output of transaction SM51 with immediate output.
2.
Check whether SAPLPD was started.
Check the status of the output request in transaction SP01.
Hint: The processing of the output request is traced step-by-step and
checked in the following tasks.
3.
Find out which dialog work process generated the spool output.
4.
Use the developer trace of the dialog work process to discover which instance
generated the output request.
5.
Identify the spool work process that generated the output request. To do this,
investigate the spool work processes of the instance that you identified in the
previous task.
6.
Check whether SAPLPD was started in the spool work process trace.
7.
Use the lprintg.log log file to check whether SAPLPD was restarted.
8.
Check the port used to start SAPLPD in the lprintg.log log file. This is in the
line: Using port xxx.
9.
Exit your SAPLPD.
Caution: Ending SAPLPD is necessary for the next task. Do not
reset any of the trace files, but rather use the opportunity to compare
the trace files for erroneous front-end print processes with those of an
error-free front-end print process.
Task 3: Example 1: SAPLPD
SAPLPD could not be started.
1.
Start the program ZPRINTERROR in your SAP system.
2.
Perform another front-end print with immediate output. Print the output of
transaction SM51.
Continued on next page
522
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
3.
Analyze the error. To do this, compare the trace information and the information
from transaction SP01 with the information for the successful front-end print
from the previous task.
4.
Correct the error as described in the solution and perform another front-end print.
5.
Exit your SAPLPD.
Caution: Ending SAPLPD is necessary for the next task. Do not
reset any of the trace files, but rather use the opportunity to compare
the trace files for erroneous front-end print processes with those of an
error-free front-end print process.
Task 4: Example 2 (Optional):
Port is occupied.
2005/Q2
1.
Go to the directory g:\Additional_Files\ADM100. In the saprouter
directory, open a command prompt. Start saprouter with the following call for
the DEV group: saprouter -r -S 516 or with the following call for the
QAS group: saprouter -r -S 517
2.
Perform another front-end print.
3.
Analyze the error. To do this, compare the trace information and the information
from transaction SP01 with the information for the successful front-end print
from the previous task.
4.
Correct the error as described in the solution and perform another front-end print.
© 2005 SAP AG. All rights reserved.
523
Unit 15: Structured Troubleshooting
ADM100
Solution 31: Appendix: Error Analysis for
Front-End Printing (OPTIONAL)
Task 1: Preparing the Analysis
Caution: You must perform the following task from the operating system of
your SAP system. This also applies for work that you would normally perform
at the front end. Ensure that you are logged on at operating system level as
<sid>adm. Start the SAP GUI from the operating system of the SAP system.
Prepare your system for analyzing front-end printing problems.
1.
In transaction SPAD, copy (or use Create Using Template) the front-end printer
tfrontendprinter to tfrontendprinter2 and assign the short name TFRP to
this output device. Activate the level 2 trace for this output device.
a)
2.
In transaction SPAD, start output device maintenance and switch to change
mode. Place the cursor on the output device tfrontendprinter and choose
Create Using Template. Assign the new name tfrontendprinter2
and save the output device. Assign the new short name to the output
device at this point. Select the new output device again for maintenance.
Ensure that the access method F is set for the new output device. Activate
debugging by choosing Edit → Test Tool. The system displays a new tab
page, on which you should activate a level 2 trace. Save the output device.
For more detailed information, see the lesson, section Activating the Trace.
Set the trace level for front-end printing to 1.
a)
On the initial screen of transaction SPAD, choose Settings → Spool System.
On the Frontend Prnt. tab page, set the Trace level for frontend printing
to 1. For more detailed information, see the lesson, section Activating
the Trace
Continued on next page
524
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
3.
Activate the trace for your user <sid>adm (using an entry in the User variables
for <sid>adm, not in the System variables) for LPRINTG.DLL, by creating
a new environment variable.
a)
Activate the trace for LPRINTG.DLL by setting the environment variable
DPTRACE to 3. Under Microsoft Windows 2000, you set environment
variables by choosing Start → Settings → Control Panel → System. On the
Advanced tab page, choose Environment Variables.... Choose New... under
User variables and enter the above values. After setting the environment
variable, you must close and then restart SAP Logon. The trace output is
written to the file lprintg.log, which is usually in the SAPworkdir
directory of your front end.
For more detailed information, see the lesson, section Activating the Trace.
4.
For your user <sid>adm, set the environment variable LPRINT_PORT depending
on your <sid> (User variables for <sid>adm, not System variables). If your
<sid>=DEV, set the variable to 516. If your <sid>=QAS, set the variable to 517.
a)
5.
Under Microsoft Windows 2000, you set environment variables by
choosing Start → Settings → Control Panel → System. On the Advanced
tab page, choose Environment Variables.... Choose New... under User
variables and enter LPRINT_PORT and set the value to 516 if you are
administering the DEV system or 517 if you are administering the QAS
system. After setting the environment variable, you must close and then
restart SAP Logon.
Close all SAP GUIs and SAP Logon.
Caution: The environment variables that you have set only take effect
when you restart SAP Logon and with a new SAP GUI.
a)
Follow the instructions in the exercise text.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
525
Unit 15: Structured Troubleshooting
ADM100
Task 2: Perform a Front-End Print
Perform a front-end print on the server on which your SAP system is running.
1.
Use the front-end printer with the short name TFRP to perform a front-end print.
Print the output of transaction SM51 with immediate output.
a)
2.
If necessary, use transaction SU3 to set the test printer tfrontenddruck2
as the default printer for front-end printing and activate immediate
output there. Alternatively, you can choose the Properties button in the
printer selection window when printing to set the print time to Print out
immediately. Print the output list from transaction SM51 with these
settings.
Check whether SAPLPD was started.
Check the status of the output request in transaction SP01.
Hint: The processing of the output request is traced step-by-step and
checked in the following tasks.
a)
SAPLPD was started. In transaction SP01, the status for the output request
is Compl.. The other information is similar to that in figure SP01 Output
Request: 1 in the lesson text. The status gives a clue as to where problems
have occurred. You can view the complete status information by choosing
the Output Request Status button. You obtain more information in the
Status Description Request xxx dialog box by choosing the Events button.
Continued on next page
526
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
3.
Find out which dialog work process generated the spool output.
a)
To do this, you can search all of the developer traces of the SAP application
server on which the user is logged on, or, in a Command Prompt at
operating system level, switch to the SAP application server's work
directory. You can search the trace file with the command qgrep. If the
front-end printer has the short name TFRP, the call is: qgrep -l -e
TFRP dev_*. All trace files in which TFRP (case-sensitive) appears
display. The name of the developer trace in which the text was found
displays at the start of each line. You can check the trace files from the
operating system or from transaction SM50 . In the dialog work process
trace file, you find, in the Printer Trace, the line S sending
frontend job xxxx/y, among other things. xxxx specifies the spool
number and y the output request number. You can use this information to
identify whether the checked spool request was processed by this dialog
work process.
For more detailed information, see the lesson, section Error-Free Front-End
Printing.
4.
Use the developer trace of the dialog work process to discover which instance
generated the output request.
a)
You can check the trace files from the operating system or from transaction
SM50 . In the Printer Trace in the dialog work process trace file, you
find the line S Send Message (P) to Spoolserver xxx. xxx
specifies which instance generated the output request.
Above this, you find the line S sending frontend job xxxx/y.
xxxx specifies the spool number and y the output request number. Use
these to ensure that you are analyzing the trace information for your output
request.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
527
Unit 15: Structured Troubleshooting
5.
Identify the spool work process that generated the output request. To do this,
investigate the spool work processes of the instance that you identified in the
previous task.
a)
6.
ADM100
To do this, you can search all developer traces of the spool work processes
of the SAP applications server identified in the previous task. Alternatively,
open a Command Prompt at operating system level in the work directory
of the instance. You can search the trace file with the command qgrep. If
the front-end printer has the short name TFRP, the call is: qgrep -l -e
TFRP dev_*. All trace files in which TFRP (case-sensitive) appears are
displayed. The name of the developer trace in which the text was found
is displayed at the start of each line. View only the trace files associated
with a spool work process. You can check the trace files from the operating
system or from transaction SM50 . In the dialog work process trace file,
you find, in the Printer Trace, the line S sending frontend
job xxxx/y, among other things. xxxx specifies the spool number and y
the output request number. You can use this information to ensure that you
are analyzing the trace information for your output request.
Check whether SAPLPD was started in the spool work process trace.
a)
In the spool work process trace, search for the location with the TCP_OPEN
entries. Ensure (as in the previous steps) that you are analyzing the trace
information for the output request.
For the first TCP_OPEN, you find the return value retcode = 2.
This means that SAPLPD was not started. It is now started in the line
TCP_START. The return value for this is retcode = 0. This means
that SAPLPD was started. The subsequent TCP_OPEN call is now also
successful with retcode = 0.
Continued on next page
528
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
7.
Use the lprintg.log log file to check whether SAPLPD was restarted.
a)
8.
You can find the lprintg.log log file under c:\Documents and
Settings\<sid>adm\SAPworkdir. SAPLPD was restarted. You
find a TCP_OPEN sequence for this, which follows the TCP_START
sequence. For the DEV system, this should look like this:
TCP_START called
Trying to start SAPLPD\SAPLPD.EXE -I
Trying to start SAPLPD\SAPLPD.EXE -I -r516
Setting lock for SAPLPD
Releasing lock
TCP_START finished
, and for the QAS system:
TCP_START called
Trying to start SAPLPD\SAPLPD.EXE -I
Trying to start SAPLPD\SAPLPD.EXE -I -r517
Setting lock for SAPLPD
Releasing lock
TCP_START finished
Check the port used to start SAPLPD in the lprintg.log log file. This is in the
line: Using port xxx.
a)
The port must be 516 for the DEV group and 517 for the QAS group.
You can find the lprintg.log log file under c:\Documents and
Settings\<sid>adm\SAPworkdir.
The Using port xxx information is in approximately the fifth line of
the TCP_OPEN sequences.
The TCP_START sequence for the start of SAPLPD also contains the
information about the port where it is started. In the following line, 516 is
the specification of the port:
Trying to start SAPLPD\SAPLPD.EXE -I -r516
9.
Exit your SAPLPD.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
529
Unit 15: Structured Troubleshooting
ADM100
Caution: Ending SAPLPD is necessary for the next task. Do not
reset any of the trace files, but rather use the opportunity to compare
the trace files for erroneous front-end print processes with those of an
error-free front-end print process.
a)
See exercise text.
Task 3: Example 1: SAPLPD
SAPLPD could not be started.
1.
Start the program ZPRINTERROR in your SAP system.
a)
2.
Start transaction SA38 and enter the program ZPRINTERROR. Choose
F8 to Execute.
Perform another front-end print with immediate output. Print the output of
transaction SM51.
a)
This time, SAPLPD should not be started, and no print output should be
produced.
The procedure corresponds to task 2.2.. The solution is described there in
detail.
3.
Analyze the error. To do this, compare the trace information and the information
from transaction SP01 with the information for the successful front-end print
from the previous task.
a)
The report ZPRINTERROR entered in the SAP system that the system
should look for SAPLPD in the <SID> directory under the SAPgui
directory. That is, SAPLPD is not found.
The procedure corresponds to tasks 2.3 to 2.6. The solution is described
there in detail. The only difference is that you find the following entry
in lprintg.log:
TCP_START called
Trying to start <SID>\SAPLPD.EXE -I
Trying to start <SID>\SAPLPD.EXE -I -r51x
Setting lock for SAPLPD
Releasing lock
TCP_START finished
(x=6 for the DEV system (<SID>=DEV, x=7 for the QAS system
(<SID>=QAS). The system is therefore searching for SAPLPD in a
directory where it does not exist.
Continued on next page
530
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
4.
Correct the error as described in the solution and perform another front-end print.
a)
On the initial screen of transaction SPAD, choose Settings → Spool
System.. Check the entry for SAPLPD start command for frontend printing.
Enter the default SAPLPD path here (SAPLPD\SAPLPD.EXE -I).
The system now searches for SAPLPD in the directory c:\Program
Files\SAP\FrontEnd\SAPgui\SAPlpd again. The report
ZPRINTERROR had (deliberately) entered a path in which there was no
SAPLPD.
Front-end printing should now work without errors again.
5.
Exit your SAPLPD.
Caution: Ending SAPLPD is necessary for the next task. Do not
reset any of the trace files, but rather use the opportunity to compare
the trace files for erroneous front-end print processes with those of an
error-free front-end print process.
a)
See exercise text.
Task 4: Example 2 (Optional):
Port is occupied.
1.
Go to the directory g:\Additional_Files\ADM100. In the saprouter
directory, open a command prompt. Start saprouter with the following call for
the DEV group: saprouter -r -S 516 or with the following call for the
QAS group: saprouter -r -S 517
a)
2.
You are now occupying the port that SAPLPD should use. For more
detailed information, see the lesson, section “Example 2”.
Perform another front-end print.
a)
This time, SAPLPD should not be started, and no print output should be
produced.
The procedure corresponds to task 2 step 2.. The solution is described
there in detail.
Continued on next page
2005/Q2
© 2005 SAP AG. All rights reserved.
531
Unit 15: Structured Troubleshooting
3.
ADM100
Analyze the error. To do this, compare the trace information and the information
from transaction SP01 with the information for the successful front-end print
from the previous task.
a)
Since the port at which SAPLPD listens is occupied, the system assumes
that SAPLPD is running. However, this is not the case.
The procedure corresponds to tasks 2.3 to 2.8. The solution is described
there in detail.
The information from transaction SP01 is similar to the figure SP01 Output
Request: 3 in the lesson text. The spool trace information is similar to the
figure Spool Work Process Trace: 3.
No SAPLPD was started on the front end. An error occurred during
the data transfer in the spool transfer (msg = INTERNAL and
retcode = 2). You can find this in the log file lprintg.log in the lines
TCP_WRITE_BINARY called ... NiRawWrite failed with
code =-6 .
You can make the following conclusion: A program is listening at port
51x. The data is transferred to the SAP GUI and forwarded to the port
by lprintg.dll. This is why there are corresponding entries in the log file
lprintg.log. You can now configure a different port for the program which
is occupying port 515, or assign a different, free port to SAPLPD (follow
the instructions in SAP Note 114426 if doing this).
4.
Correct the error as described in the solution and perform another front-end print.
a)
Go to the directory g:\Additional_Files\ADM100. Open a
Command Prompt in the saprouter directory. Stop the running saprouter
with the following call for the DEV group: saprouter -s -S 516 or
with the following call for the QAS group: saprouter -s -S 517.
Front-end printing should now be possible again.
This procedure is possible here in the course. In practice, you would, of
course, have to check whether you can configure the program (which is
occupying the port) on another port, or configure SAPLPD on another port.
532
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Lesson: Appendix: Troubleshooting Example
Lesson Summary
You should now be able to:
•
Perform troubleshooting if problems occur in front-end printing
Related Information
The following SAP Notes may help you when analyzing front-end printing errors:
•
•
•
2005/Q2
SAP Note 379515: Troubleshooting Frontend Printing
SAP Note 328252: SAPLPD Patches in SAPNet
SAP Note 114426: Frontend Printing (Collective note)
© 2005 SAP AG. All rights reserved.
533
Unit Summary
ADM100
Unit Summary
You should now be able to:
•
List various trace options
•
Perform simple traces in the SAP system
•
Develop procedures for structured troubleshooting
•
Perform troubleshooting if problems occur in front-end printing
534
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Test Your Knowledge
Test Your Knowledge
1.
In which of the following transactions can you activate a trace for SQL
statements in the SAP system?
Choose the correct answer(s).
□
□
□
□
2.
A
B
C
D
Performance trace
System log
System trace
Database performance analysis
What is the default port for SAPLPD use under Microsoft Windows?
Choose the correct answer(s).
□
□
□
□
□
□
2005/Q2
A
B
C
D
E
F
007
515
516
517
815
The port defined by profile parameter rspo/port
© 2005 SAP AG. All rights reserved.
535
Test Your Knowledge
ADM100
Answers
1.
In which of the following transactions can you activate a trace for SQL
statements in the SAP system?
Answer: A, C
You can analyze SQL statements by activating the trace in transaction ST01
(system trace) or ST05 (performance trace). Transaction SM21 (System Log) is
the system log and ST04 (Database Performance Analysis) is used to analyze
database statistics.
2.
What is the default port for SAPLPD use under Microsoft Windows?
Answer: B
Port 515 is used by default.
536
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Course Summary
Course Summary
You should now be able to:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Start and stop SAP systems
Set up system parameters
Configure help
Schedule database backups
Use SAP data archiving
Perform and check transports
Import Support Packages, Plug-Ins, and Add-Ons
Schedule background tasks
Configure printers in the SAP system
Create and manage users
Set up remote connections
Monitor the system
Describe the SAP Solution Manager
Perform structured troubleshooting
Use system security terms correctly in the SAP environment
Related Information
•
SAP courses
–
–
–
–
–
–
–
–
–
2005/Q2
ADM102 - SAP Web AS Administration II
ADM106 - Advanced SAP System Monitoring
ADM110 - SAP ERP Central Component Installation
ADM325 - Software Logistics
ADM326 - SAP R/3 Enterprise Upgrade
ADM940 - SAP Authorization Concept
ADM950 - Secure SAP System Management
ADM960 - Security in SAP System Environments
ADM315 - Workload Analysis
© 2005 SAP AG. All rights reserved.
537
Course Summary
538
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
Glossary
ABAP
Advanced Business Application Programming. SAP's programming language.
ABAP Workbench
Integrated graphical development environment in the SAP system. The ABAP
Workbench enables you to develop, modify, test, and manage client/server
applications that are written in ABAP.
access method
The access method describes the connection of a spool work process to an
operating system spooler.
activation
Procedure that makes an object available to the runtime environment. During
activation, runtime objects are generated, which the application programs and
screen templates access.
ALE
Application Link Enabling technology to create and operate distributed
applications.
archive information structure
A central element in the SAP Archive Information System (AS). Using data
fields, it enables you to find and display archived data.
archiving object
Logical object of related business data in the database that can be read from
the database using a write program and then deleted from the database by the
associated delete program after successful archiving.
background job
A background job describes steps that are to be executed in the system without
user interaction (in the background). Background jobs are processed by
background work processes.
buffer
Area in the main memory of an instance in which data frequently used by
applications can be temporarily stored.
2005/Q2
© 2005 SAP AG. All rights reserved.
539
Glossary
ADM100
business object
Representation of a business object in the real world, such as an order. SAP
business objects describe entire business processes. This type of encapsulation
reduces the complexity, since the internal structure of the business object remains
hidden.
central system
A central SAP system consists of a single instance that provides all required SAP
services and the associated database. In the case of a central system, these are
usually on the same computer.
change request
Information source in the Transport Organizer that records and manages all
modifications made to repository objects and Customizing settings during a
development project.
client
A client usually corresponds to the mapping of a company in an SAP system.
That is, multiple companies can be mapped and active in parallel in an SAP
system with multiple clients. A key field in the business tables of the database
associated with the SAP system corresponds to the client. From a particular
client, you can only access the data for that client. In this way, clients correspond
to separate business entities.
Software component that uses a server's service (software-oriented view) or a
workstation that is provided with resources by the server (hardware-oriented
view).
Computing Center Management System (CCMS)
Integrated tools for monitoring and administering SAP systems and independent
SAP business components, with which you can, for example, automate operations
such as resource distribution and the management of SAP databases.
CPI-C
The Common Programming Interface for Communication describes data
exchange between different programs. CPI-C can be used to transfer “packaged”
data with various technical protocols, such as TCP/IP or LU6.2.
Customizing
Customizing is the entire procedure of setting up one or more SAP systems. The
procedure aims to adjust the company-neutral and industry-specific functions of
the SAP system to your company's specific business requirements. Customizing
is obligatory both during the first installation and during an upgrade and is
performed in the SAP system using the Implementation Guide (IMG).
540
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Glossary
data archiving
Reading data from the database that is no longer required for online operation,
and storing this data in an archive file. Archived data is usually deleted from
the system. Archiving removes load from the system, meaning that programs,
database accesses, and database backups have shorter runtimes due to the lower
quantity of data in the database.
development object
Component of an ABAP application. Development objects include: Programs
such as transactions, reports, subroutines, and function modules; program
components such as event blocks, screens, and menus; and objects, used by
several programs (such as database fields, field definitions, and program
messages).
DIAG
Dynamic Information and Action Gateway: Protocol for communication between
the SAP GUI and the application server (also known as the SAP GUI protocol).
dispatcher
Central process of an instance. Among other things, it is responsible for starting
work processes and SAP Web AS Java and distributing the translation workload
to the work processes.
Dynpro
DYNamic PROgram. A dynamic program consists of a screen image and its
underlying flow logic, programmed in ABAP.
enqueue server
Enqueue server is a possible description for the instance of an SAP system on
which the enqueue work process manages the lock table in a distributed SAP
system.
F4 help
The F4 help provides you with input help for a field that is ready for input.
front end
Work center computer
gateway
Interface that converts one communication protocol into another communication
protocol.
HTML
HyperText Markup Language (HTML): Document description language for
creating HTML pages in the Internet. HTML documents have a uniform format
and consist only of ASCII text. They can either be stored statically in the file
system of the Web server of be generated dynamically at runtime by special
programs. The Web servers sends them to the Web browser, which interprets
and displays them.
2005/Q2
© 2005 SAP AG. All rights reserved.
541
Glossary
ADM100
HTTP
Application protocol of the World Wide Web (WWW). The HyperText Transfer
Protocol (HTTP) controls communication between the Web browser (the HTTP
client) and the Web server (the HTTP server).
instance
Administrative unit that groups components of an SAP system that provide one
or more services. These services are started and stopped at the same time.
Internet Communication Manager
The Internet Communication Manager (ICM) is the component in the SAP
architecture that allows the SAP system to communicate directly with the
Internet. It is started by the dispatcher of an instance.
job
Closed chain of steps (such as ABAP programs) that can be controlled
successively using certain control commands.
LDAP
Lightweight Directory Access Protocol. A protocol for accessing address
directories, defined in IETF RFC 1777.
lock table
The lock table is a table in the main memory of the enqueue server, which
contains information about which locks currently exist. For each lock that it
exists, it shows the owner, the lock mode, the name, and the fields of the locked
table.
message server (ABAP)
Standalone program that contains a list of all instances that are part of the SAP
system. In the case of a logon using logon groups, the message server determines
the instance that a user logs on to, and organizes the communication between
the instances.
mySAP Business Suite
mySAP Business Suite is a complete package of open, integrated solutions for the
whole value chain. The functions of the mySAP Business Suite bring together
customers, employees, suppliers, and partner companies. Information, orders,
and service requests can be efficiently and directly accessed and processed by
the appropriate person.
Object Navigator
Tools for managing development objects.
output request
An output request contains the data from a spool request in a format for a
particular printer model.
542
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Glossary
package
Container for semantically connected development objects. A package consists
of sub-packages and development objects (programs, tables, screens, function
modules, classes, and so on) that are developed and transported together.
Packages are characterized by the properties nesting, interfaces, visibility and use
accesses. Packages are created and managed with the Package Builder. They
replace development classes.
Quick Link
Navigation technology for quick access to certain areas of the SAP Service
Marketplace. To call a Quick Link, add the Quick Link directly at the end of the
Web address, after a “/” (such as http://service.sap.com/smp).
Repository
Central store for all ABAP Workbench development objects. The development
objects stored in the repository of the SAP system include: Program objects,
function group objects, Dictionary objects, Business Engineering objects, and
other objects.
RFC
Remote Function Call (RFC) is an SAP interface protocol based on CPI-C. This
significantly simplifies the programming of communication processes between
systems.
role
A role is a collection of activities that a person executes to participate in one or
more business scenarios of an organization. User menus are used to access the
transactions, reports, Web-based applications, and so on in the roles.
SAP Archive Information System
Generic tool fully integrated in data archiving for searching SAP data archives.
The search and display of data is based on archive information structures that the
user can define and fill with data from the archive.
SAP ArchiveLink
A service integrated into the SAP system technology that creates a connection
between stored documents and related application documents (business objects)
in the SAP system.
SAP Easy Access
SAP Easy Access is the standard initial screen in SAP systems. The system
displays the menu available to you in a tree structure on the left of the screen.
You can display your own logo on the right of the screen.
SAP GUI
SAP Graphical User Interface; software component with which the user can
exchange information with the computer. With the user interface, you can select
commands, start programs, display files, and choose other options by pressing
function keys or pushbuttons or selecting menu options.
2005/Q2
© 2005 SAP AG. All rights reserved.
543
Glossary
ADM100
SAP GUI for HTML
SAP GUI that runs in the Web browser, and generates HTML pages dynamically
based on SAP screen layouts. Requires an SAP Internet Transaction Server
(SAP ITS).
SAP GUI for Java
Platform-independent SAP GUI, requires a Java environment.
SAP GUI for Windows
Implementation of SAP GUI in a Microsoft Windows environment.
SAP Internet Transaction Server (SAP ITS)
The SAP Internet Transaction Server (SAP ITS) is an interface between the SAP
system and the Internet. It allows users to communicate directly with the SAP
system by starting business transactions, function modules, and reports from a
Web browser. If a user calls an application, the request is forwarded to the Web
server with which the Web browser is connected. The Web server transfers the
request to the SAP ITS, which creates a connection to the SAP system. SAP ITS
then controls the communication and the data exchange between the SAP system
and the Web server. SAP ITS consists of two main components: the WGate (Web
Gateway) and the AGate (Application Gateway).
SAP Logon
When it is started, the SAP Logon program (only available for Microsoft
Windows) provides a list of SAP systems for which the logon process can
be started. This list is taken from the information in a file on the front end:
saplogon.ini. This file is usually preconfigured centrally and provided to end
users. The SAP Logon program also allows logon load balancing across the
resources available for the selected system at logon.
SAP NetWeaver™
SAP NetWeaver™is the comprehensive integration and application platform
from SAP. SAP NetWeaver™ allows you to simplify and co-ordinate user,
information, and business processes across technology and organizations. SAP
NetWeaver™ offers full compatibility with the Microsoft .NET™ and J2EE (z.B.
IBM WebSphere ) standards. SAP NetWeaver™ is divided into the following
areas: People Integration, Information Integration, Process Integration, and
Application Platform.
SAP Notes
An SAP Note is text information about a particular issue, problem, or system
message that can arise in the context of your work with the system. All SAP
Notes are stored at SAP in a database that is available online, and can be called
up by customers from there. A possible question could be, for example: “Which
database versions of database XY are released in combination with my SAP
system release?”
544
© 2005 SAP AG. All rights reserved.
2005/Q2
ADM100
Glossary
SAP Service Marketplace
Central portal (URL http://service.sap.com) with services, information, and other
offerings for SAP customers and partners.
SAP system
An SAP system can be, for example, an SAP ECC, SAP SCM, or SAP CRM
system. SAP systems are the central components of the SAP solutions in the
context of mySAP Business Suite.
SAP Web Application Server
SAP Web Application Server offers full support for platform-independent Web
Services, business Web applications and developments based on key technologies
such as Java conforming to the J2EE standard and ABAP. SAP Web Application
Server provides the infrastructure for many of the solutions and components
of the mySAP Business Suite, such as SAP R/3 Enterprise, or SAP Business
Information Warehouse. It is the development and runtime environment for all
business applications.
server
Software component that provides a service (software-oriented view) or a central
host in a network that provides resources to local computers (hardware-oriented
view).
shared memory
Main memory area that is accessible for all work processes of an instance.
spool request
A spool request contains information about data to be output, its formatting,
and the printer model used.
system log
Analysis option for errors in the system and its environment.
table
Tabular arrangement of data in the ABAP Dictionary. A table consists of columns
(sets of data values of the same type) and rows (data records). Each table row
can be uniquely identified using one or more fields.
TemSe
Abbreviation for Temporary Sequential file; file in which, among other things,
data for spool requests and for background processing job logs is temporarily
stored.
transaction code
A transaction code (also known as T code) is a character string that identifies a
transaction in the SAP system. A transaction code can be up to 20 characters
in length and should always begin with a letter. Permitted characters are letters
from A to Y, digits form 0 to 9, and the underscore. To call a transaction, enter
the transaction code in the command field and choose enter.
2005/Q2
© 2005 SAP AG. All rights reserved.
545
Glossary
ADM100
transport
Transfer of SAP system components from one system to another. The
components to be transported are listed in the object list of a transport request.
Each transport consists of an export and an import process. The export process
reads the objects from the source system and stores them in data files at operating
system level. The import process reads the objects from the data file and writes
them to the database of the target system. The system logs all actions of the
export and import processes.
user context
Data that is assigned specifically to one user. If a user starts a transaction in
the SAP system, the work process processing the request requires the user
context. The user context contains a user-specific area that contains user and
authorization data.
user master record
The user master record contains the definition of a user in the client. Some fields
are, for example: Name, first name, initial password, telephone number, and so
on. The user master record is used to create a user context (see this entry) when
a user logs on to the system.
variant
Preassignment of the input fields of a selection screen for reports, for example to
enable the execution of the report in the background.
work process
Process that processes requests in the SAP system. There are the following types
of work process: Dialog (for executing dialog programs), update (for changing
database entries), background (for executing background jobs), spool (for print
preparation), and enqueue (for executing lock operations).
546
© 2005 SAP AG. All rights reserved.
2005/Q2
Index
A
access method, 312
Archive Development Kit, 425
archive information structure,
426
archiving object, 404, 411
aRFC, 203
authorization object, 170
B
background users, 383
backup, 141
business object, 405
C
central instance, 2, 40
central system, 2
change request, 245
client, 240
CTS, 239
customer development, 241
Customizing, 239
Customizing request, 248
external command, 384
external program, 384
F
front-end printing, 315
H
HtmlHelpFile, 120
I
import, 251
import queue, 251
inactive import, 285
instance, 4
instance profile, 83
J
job class, 354
job server group, 382
Job Wizard, 357
L
local printing, 312
logon groups, 14
D
M
data archiving, 404
data collector, 439
default profile, 83
developer trace, 493
development class, see package
device type, 317
dispatcher, 5
dump analysis, 492
DynamicHelp, 120
message server, 7, 12, 40, 52
modification, 241
modification adjustment
SAINT, 283
SPAM, 278
monitoring segment, 439
monitoring tree element, 440
MTE, see monitoring tree element
N
E
Note Assistant, 299
enhancement, 241
2005/Q2
© 2005 SAP AG. All rights reserved.
547
Index
ADM100
O
rdisp/max_alt_modes, 88
rdisp/max_wprun_time, 352
rdisp/myname, 88
rdisp/TRACE, 51
rdisp/wp_no_btc, 88, 366
rdisp/wp_no_dia, 88
rdisp/wp_no_enq, 88
rdisp/wp_no_Fro_max, 315
rdisp/wp_no_spo, 88
rdisp/wp_no_vb, 88
rslg/central/file, 494
rslg/local/file, 494
rspo/local_print/server, 330
rspo/store_location, 311
rstr/buffer_size_kB, 498
rstr/filename, 498
rstr/max_files, 498
rstr/max_filesize_MB, 498
operation mode, 102
switch, 107
output request, 310
P
package, 239
performance trace, 493
PlainHtmlFile, 120
PlainHtmlHttp, 120
profile parameter
auth/new_buffering, 171
DIR_TRANS, 250
login/disable_multi_gui_login, 185
login/failed_user_auto_unlock=0, 185
login/fails_to_session_end,
185
login/fails_to_user_lock,
185
login/min_password_digits,
184
login/min_password_letters, 184
login/min_password_lng,
184
login/min_password_specials, 184
login/multi_login_users,
185
login/no_automatic_user_sapstar,
223
login/password_expiration_time, 184
login/password_max_new_valid,
184
login/password_max_reset_valid, 184
rdisp/btcname, 374
rdisp/btctime, 365
548
© 2005 SAP AG. All rights reserved.
Q
qRFC, 203
R
remote printing, 313
REORGJOBS, see standard jobs
Repository, 239
role maintenance, 172
S
SAP Archive Information
System, 426
SAP ArchiveLink, 406
SAP Library, 119
SAP Service Marketplace, 127
SAP Solution Manager, 476
SAP Web AS Java, 3
sapdoccd.ini, 123
sapevt, 375
saplpd, 314–315
SAPOSCOL, 40
SAProuter, 229
sapxpg, 384
SNC, 224
spool request, 310
2005/Q2
ADM100
Index
sRFC, 202
SSF, 227
SSL, 226
standard jobs, 367
start profile, 83
system log, 492
system parameter, see profile
parameter
system trace, 493
T
TemSe, 311
time table, 104
tp, 252
transaction code
AL08, 25
DB12, 146
DB13, 145
DB13C, 146
DB15, 412, 419
FILE, 412
PFCG, 172
PFUD, 176
RSPFPAR, 85
RZ03, 106
RZ04, 104, 382
RZ10, 91
RZ11, 85
RZ20, 441
RZ21, 450, 468
SA38, 369–370
SAINT, 280
SARA, 412
SCC4, 240
SE09, 245
SM02, 25
SM04, 25
SM12, 25
SM13, 25
SM21, 25, 492, 494
2005/Q2
SM36, 357
SM36WIZ, 357
SM37, 358
SM49, 392
SM50, 25
SM51, 25
SM59, 205
SM61, 383
SM62, 375
SM63, 104
SM64, 375
SM66, 25
SM69, 387
SMLG, 15
SNOTE, 300
SP01, 339
SPAD, 315, 512, 524, 531
SPAK, 239
SPAM, 272
SR13, 122
ST01, 186, 493, 495
ST05, 493, 497
ST22, 492
STMS, 250, 253
SU01, 164
SU3, 323
SU53, 186
SUIM, 185
SWW_ARCHIV, 429–430
transport directory, 250
Transport Organizer, 245
tRFC, 203
U
update, 25
user master comparison, 176
W
work process multiplexing, 8
workbench request, 245
© 2005 SAP AG. All rights reserved.
549
Index
550
ADM100
© 2005 SAP AG. All rights reserved.
2005/Q2
Feedback
SAP AG has made every effort in the preparation of this course to ensure the accuracy
and completeness of the materials. If you have any corrections or suggestions for
improvement, please record them in the appropriate place in the course evaluation.
2005/Q2
© 2005 SAP AG. All rights reserved.
551